From rfc-editor at rfc-editor.org Fri Jan 4 16:06:11 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 4 Jan 2008 16:06:11 -0800 (PST) Subject: [rfc-dist] RFC 5039 on The Session Initiation Protocol (SIP) and Spam Message-ID: <20080105000611.322751070D8@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5039 Title: The Session Initiation Protocol (SIP) and Spam Author: J. Rosenberg, C. Jennings Status: Informational Date: January 2008 Mailbox: jdrosen at cisco.com, fluffy at cisco.com Pages: 28 Characters: 73341 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sipping-spam-05.txt URL: http://www.rfc-editor.org/rfc/rfc5039.txt Spam, defined as the transmission of bulk unsolicited messages, has plagued Internet email. Unfortunately, spam is not limited to email. It can affect any system that enables user-to-user communications. The Session Initiation Protocol (SIP) defines a system for user-to- user multimedia communications. Therefore, it is susceptible to spam, just as email is. In this document, we analyze the problem of spam in SIP. We first identify the ways in which the problem is the same and the ways in which it is different from email. We then examine the various possible solutions that have been discussed for email and consider their applicability to SIP. This memo provides information for the Internet community. This document is a product of the Session Initiation Proposal Investigation Working Group of the IETF INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Mon Jan 7 17:14:07 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 7 Jan 2008 17:14:07 -0800 (PST) Subject: [rfc-dist] RFC 5012 on Requirements for Emergency Context Resolution with Internet Technologies Message-ID: <20080108011407.CACD41075B2@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5012 Title: Requirements for Emergency Context Resolution with Internet Technologies Author: H. Schulzrinne, R. Marshall, Ed. Status: Informational Date: January 2008 Mailbox: hgs+ecrit at cs.columbia.edu, rmarshall at telecomsys.com Pages: 23 Characters: 54599 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ecrit-requirements-13.txt URL: http://www.rfc-editor.org/rfc/rfc5012.txt This document defines terminology and enumerates requirements for the context resolution of emergency calls placed by the public using voice-over-IP (VoIP) and general Internet multimedia systems, where Internet protocols are used end to end. This memo provides information for the Internet community. This document is a product of the Emergency Context Resolution with Internet Technologies Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Mon Jan 7 17:14:21 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 7 Jan 2008 17:14:21 -0800 (PST) Subject: [rfc-dist] RFC 5031 on A Uniform Resource Name (URN) for Emergency and Other Well-Known Services Message-ID: <20080108011421.0CF1A1075B4@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5031 Title: A Uniform Resource Name (URN) for Emergency and Other Well-Known Services Author: H. Schulzrinne Status: Standards Track Date: January 2008 Mailbox: hgs+ecrit at cs.columbia.edu Pages: 14 Characters: 32960 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ecrit-service-urn-07.txt URL: http://www.rfc-editor.org/rfc/rfc5031.txt The content of many communication services depends on the context, such as the user's location. We describe a 'service' URN that allows well-known context-dependent services that can be resolved in a distributed manner to be identified. Examples include emergency services, directory assistance, and call-before-you-dig hot lines. [STANDARDS TRACK] This document is a product of the Emergency Context Resolution with Internet Technologies Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Mon Jan 7 17:14:32 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 7 Jan 2008 17:14:32 -0800 (PST) Subject: [rfc-dist] RFC 5069 on Security Threats and Requirements for Emergency Call Marking and Mapping Message-ID: <20080108011432.8038B1075B6@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5069 Title: Security Threats and Requirements for Emergency Call Marking and Mapping Author: T. Taylor, Ed., H. Tschofenig, H. Schulzrinne, M. Shanmugam Status: Informational Date: January 2008 Mailbox: tom.taylor at rogers.com, Hannes.Tschofenig at nsn.com, hgs+ecrit at cs.columbia.edu, murugaraj.shanmugam at detecon.com Pages: 12 Characters: 26230 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ecrit-security-threats-05.txt URL: http://www.rfc-editor.org/rfc/rfc5069.txt This document reviews the security threats associated with the marking of signalling messages to indicate that they are related to an emergency, and with the process of mapping locations to Universal Resource Identifiers (URIs) that point to Public Safety Answering Points (PSAPs). This mapping occurs as part of the process of routing emergency calls through the IP network. Based on the identified threats, this document establishes a set of security requirements for the mapping protocol and for the handling of emergency-marked calls. This memo provides information for the Internet community. This document is a product of the Emergency Context Resolution with Internet Technologies Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Mon Jan 7 17:14:42 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 7 Jan 2008 17:14:42 -0800 (PST) Subject: [rfc-dist] RFC 5088 on OSPF Protocol Extensions for Path Computation Element (PCE) Discovery Message-ID: <20080108011442.C69A21075B8@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5088 Title: OSPF Protocol Extensions for Path Computation Element (PCE) Discovery Author: JL. Le Roux, Ed., JP. Vasseur, Ed., Y. Ikejiri, R. Zhang Status: Standards Track Date: January 2008 Mailbox: jeanlouis.leroux at orange-ftgroup.com, jpv at cisco.com, y.ikejiri at ntt.com, raymond.zhang at bt.com Pages: 20 Characters: 40936 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pce-disco-proto-ospf-08.txt URL: http://www.rfc-editor.org/rfc/rfc5088.txt There are various circumstances where it is highly desirable for a Path Computation Client (PCC) to be able to dynamically and automatically discover a set of Path Computation Elements (PCEs), along with information that can be used by the PCC for PCE selection. When the PCE is a Label Switching Router (LSR) participating in the Interior Gateway Protocol (IGP), or even a server participating passively in the IGP, a simple and efficient way to announce PCEs consists of using IGP flooding. For that purpose, this document defines extensions to the Open Shortest Path First (OSPF) routing protocol for the advertisement of PCE Discovery information within an OSPF area or within the entire OSPF routing domain. [STANDARDS TRACK] This document is a product of the Path Computation Element Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Mon Jan 7 17:15:06 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 7 Jan 2008 17:15:06 -0800 (PST) Subject: [rfc-dist] RFC 5089 on IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery Message-ID: <20080108011506.6EEE51075BA@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5089 Title: IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery Author: JL. Le Roux, Ed., JP. Vasseur, Ed., Y. Ikejiri, R. Zhang Status: Standards Track Date: January 2008 Mailbox: jeanlouis.leroux at orange-ftgroup.com, jpv at cisco.com, y.ikejiri at ntt.com, raymond.zhang at bt.com Pages: 17 Characters: 34257 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pce-disco-proto-isis-08.txt URL: http://www.rfc-editor.org/rfc/rfc5089.txt There are various circumstances where it is highly desirable for a Path Computation Client (PCC) to be able to dynamically and automatically discover a set of Path Computation Elements (PCEs), along with information that can be used by the PCC for PCE selection. When the PCE is a Label Switching Router (LSR) participating in the Interior Gateway Protocol (IGP), or even a server participating passively in the IGP, a simple and efficient way to announce PCEs consists of using IGP flooding. For that purpose, this document defines extensions to the Intermediate System to Intermediate System (IS-IS) routing protocol for the advertisement of PCE Discovery information within an IS-IS area or within the entire IS-IS routing domain. [STANDARDS TRACK] This document is a product of the Path Computation Element Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jan 9 17:20:18 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 9 Jan 2008 17:20:18 -0800 (PST) Subject: [rfc-dist] RFC 5111 on Experiment in Exploratory Group Formation within the Internet Engineering Task Force (IETF) Message-ID: <20080110012018.64079107A50@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5111 Title: Experiment in Exploratory Group Formation within the Internet Engineering Task Force (IETF) Author: B. Aboba, L. Dondeti Status: Experimental Date: January 2008 Mailbox: bernarda at microsoft.com, ldondeti at qualcomm.com Pages: 8 Characters: 16740 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-aboba-sg-experiment-04.txt URL: http://www.rfc-editor.org/rfc/rfc5111.txt This document describes an RFC 3933 experiment in the Working Group formation process, known as the Exploratory Group. Exploratory Groups may be created as the first step toward Working Group formation, or as an intermediate step between a Birds of a Feather (BOF) session and Working Group creation. Exploratory Groups are focused on completion of prerequisites for Working Group formation, and as a result they have a short life-time, with limited opportunities for milestone extension. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Mon Jan 14 16:55:09 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 14 Jan 2008 16:55:09 -0800 (PST) Subject: [rfc-dist] RFC 5112 on The Presence-Specific Static Dictionary for Signaling Compression (Sigcomp) Message-ID: <20080115005509.37AFF1087E0@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5112 Title: The Presence-Specific Static Dictionary for Signaling Compression (Sigcomp) Author: M. Garcia-Martin Status: Standards Track Date: January 2008 Mailbox: miguel.garcia at nsn.com Pages: 25 Characters: 67257 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-garcia-simple-presence-dictionary-06.txt URL: http://www.rfc-editor.org/rfc/rfc5112.txt The Session Initiation Protocol (SIP) is a text-based protocol for initiating and managing communication sessions. The protocol is extended by the SIP-events notification framework to provide subscriptions and notifications of SIP events. One example of such event notification mechanism is presence, which is expressed in XML documents called presence documents. SIP can be compressed by using Signaling Compression (SigComp), which is enhanced by using the SIP/ Session Description Protocol (SDP) dictionary to achieve better compression rates. However, the SIP/SDP dictionary is not able to increase the compression factor of (typically lengthy) presence documents. This memo defines the presence-specific static dictionary that SigComp can use in order to compress presence documents to achieve higher efficiency. The dictionary is compression-algorithm independent. [STANDARDS TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jan 16 11:50:37 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 16 Jan 2008 11:50:37 -0800 (PST) Subject: [rfc-dist] RFC 5134 on A Uniform Resource Name Namespace for the EPCglobal Electronic Product Code (EPC) and Related Standards Message-ID: <20080116195037.DE26D109217@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5134 Title: A Uniform Resource Name Namespace for the EPCglobal Electronic Product Code (EPC) and Related Standards Author: M. Mealling Status: Informational Date: January 2008 Mailbox: michael at refactored-networks.com Pages: 10 Characters: 18352 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-mealling-epc-urn-02.txt URL: http://www.rfc-editor.org/rfc/rfc5134.txt This document describes URN namespaces that will identify various objects within the EPCglobal system for identifying products within ecommerce and supply chain management applications. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jan 16 11:51:03 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 16 Jan 2008 11:51:03 -0800 (PST) Subject: [rfc-dist] RFC 5115 on Telephony Routing over IP (TRIP) Attribute for Resource Priority Message-ID: <20080116195103.0ED42109219@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5115 Title: Telephony Routing over IP (TRIP) Attribute for Resource Priority Author: K. Carlberg, P. O'Hanlon Status: Standards Track Date: January 2008 Mailbox: carlberg at g11.org.uk, p.ohanlon at cs.ucl.ac.uk Pages: 8 Characters: 17194 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-carlberg-trip-attribute-rp-04.txt URL: http://www.rfc-editor.org/rfc/rfc5115.txt This document defines a new attribute for the Telephony Routing over IP (TRIP) protocol. The attribute associates protocols/services in the PSTN offering authorized prioritization during call setup that are reachable through a TRIP gateway. Current examples of preferential service in the Public Switched Telephone Network (PSTN) are Government Emergency Telecommunications Service (GETS) in the U.S. and Government Telephone Preference Scheme (GTPS) in the U.K. The proposed attribute for TRIP is based on the NameSpace.Value tuple defined for the SIP Resource-Priority field. [STANDARDS TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jan 16 11:51:17 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 16 Jan 2008 11:51:17 -0800 (PST) Subject: [rfc-dist] RFC 5228 on Sieve: An Email Filtering Language Message-ID: <20080116195117.0F1A810921B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5228 Title: Sieve: An Email Filtering Language Author: P. Guenther, Ed., T. Showalter, Ed. Status: Standards Track Date: January 2008 Mailbox: guenther at sendmail.com, tjs at psaux.com Pages: 42 Characters: 87531 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sieve-3028bis-13.txt URL: http://www.rfc-editor.org/rfc/rfc5228.txt This document describes a language for filtering email messages at time of final delivery. It is designed to be implementable on either a mail client or mail server. It is meant to be extensible, simple, and independent of access protocol, mail architecture, and operating system. It is suitable for running on a mail server where users may not be allowed to execute arbitrary programs, such as on black box Internet Message Access Protocol (IMAP) servers, as the base language has no variables, loops, or ability to shell out to external programs. [STANDARDS TRACK] This document is a product of the Sieve Mail Filtering Language Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jan 16 11:51:37 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 16 Jan 2008 11:51:37 -0800 (PST) Subject: [rfc-dist] RFC 5230 on Sieve Email Filtering: Vacation Extension Message-ID: <20080116195137.0B60B10921F@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5230 Title: Sieve Email Filtering: Vacation Extension Author: T. Showalter, N. Freed, Ed. Status: Standards Track Date: January 2008 Mailbox: tjs at psaux.com, ned.freed at mrochek.com Pages: 16 Characters: 29822 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sieve-vacation-06.txt URL: http://www.rfc-editor.org/rfc/rfc5230.txt This document describes an extension to the Sieve email filtering language for an autoresponder similar to that of the Unix "vacation" command for replying to messages. Various safety features are included to prevent problems such as message loops. [STANDARDS TRACK] This document is a product of the Sieve Mail Filtering Language Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jan 16 11:51:28 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 16 Jan 2008 11:51:28 -0800 (PST) Subject: [rfc-dist] RFC 5229 on Sieve Email Filtering: Variables Extension Message-ID: <20080116195128.539C910921D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5229 Title: Sieve Email Filtering: Variables Extension Author: K. Homme Status: Standards Track Date: January 2008 Mailbox: kjetilho at ifi.uio.no Pages: 11 Characters: 20023 Updates: RFC5228 See-Also: I-D Tag: draft-ietf-sieve-variables-08.txt URL: http://www.rfc-editor.org/rfc/rfc5229.txt In advanced mail filtering rule sets, it is useful to keep state or configuration details across rules. This document updates the Sieve filtering language (RFC 5228) with an extension to support variables. The extension changes the interpretation of strings, adds an action to store data in variables, and supplies a new test so that the value of a string can be examined. [STANDARDS TRACK] This document is a product of the Sieve Mail Filtering Language Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jan 16 11:51:45 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 16 Jan 2008 11:51:45 -0800 (PST) Subject: [rfc-dist] RFC 5231 on Sieve Email Filtering: Relational Extension Message-ID: <20080116195145.C31C5109221@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5231 Title: Sieve Email Filtering: Relational Extension Author: W. Segmuller, B. Leiba Status: Standards Track Date: January 2008 Mailbox: werewolf at us.ibm.com, leiba at watson.ibm.com Pages: 9 Characters: 15243 Obsoletes: RFC3431 See-Also: I-D Tag: draft-ietf-sieve-3431bis-04.txt URL: http://www.rfc-editor.org/rfc/rfc5231.txt This document describes the RELATIONAL extension to the Sieve mail filtering language defined in RFC 3028. This extension extends existing conditional tests in Sieve to allow relational operators. In addition to testing their content, it also allows for testing of the number of entities in header and envelope fields. This document obsoletes RFC 3431. [STANDARDS TRACK] This document is a product of the Sieve Mail Filtering Language Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jan 16 11:52:12 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 16 Jan 2008 11:52:12 -0800 (PST) Subject: [rfc-dist] RFC 5233 on Sieve Email Filtering: Subaddress Extension Message-ID: <20080116195212.D46DF109225@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5233 Title: Sieve Email Filtering: Subaddress Extension Author: K. Murchison Status: Standards Track Date: January 2008 Mailbox: murch at andrew.cmu.edu Pages: 7 Characters: 12448 Obsoletes: RFC3598 See-Also: I-D Tag: draft-ietf-sieve-rfc3598bis-05.txt URL: http://www.rfc-editor.org/rfc/rfc5233.txt On email systems that allow for 'subaddressing' or 'detailed addressing' (e.g., "ken+sieve at example.org"), it is sometimes desirable to make comparisons against these sub-parts of addresses. This document defines an extension to the Sieve Email Filtering Language that allows users to compare against the user and detail sub-parts of an address. [STANDARDS TRACK] This document is a product of the Sieve Mail Filtering Language Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jan 16 11:52:02 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 16 Jan 2008 11:52:02 -0800 (PST) Subject: [rfc-dist] RFC 5232 on Sieve Email Filtering: Imap4flags Extension Message-ID: <20080116195202.34069109223@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5232 Title: Sieve Email Filtering: Imap4flags Extension Author: A. Melnikov Status: Standards Track Date: January 2008 Mailbox: alexey.melnikov at isode.com Pages: 12 Characters: 21964 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sieve-imapflags-05.txt URL: http://www.rfc-editor.org/rfc/rfc5232.txt Recent discussions have shown that it is desirable to set different IMAP (RFC 3501) flags on message delivery. This can be done, for example, by a Sieve interpreter that works as a part of a Mail Delivery Agent. This document describes an extension to the Sieve mail filtering language for setting IMAP flags. The extension allows setting of both IMAP system flags and IMAP keywords. [STANDARDS TRACK] This document is a product of the Sieve Mail Filtering Language Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jan 16 11:52:31 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 16 Jan 2008 11:52:31 -0800 (PST) Subject: [rfc-dist] RFC 5235 on Sieve Email Filtering: Spamtest and Virustest Extensions Message-ID: <20080116195231.7C976109227@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5235 Title: Sieve Email Filtering: Spamtest and Virustest Extensions Author: C. Daboo Status: Standards Track Date: January 2008 Mailbox: cyrus at daboo.name Pages: 13 Characters: 25957 Obsoletes: RFC3685 See-Also: I-D Tag: draft-ietf-sieve-spamtestbis-05.txt URL: http://www.rfc-editor.org/rfc/rfc5235.txt The Sieve email filtering language "spamtest", "spamtestplus", and "virustest" extensions permit users to use simple, portable commands for spam and virus tests on email messages. Each extension provides a new test using matches against numeric "scores". It is the responsibility of the underlying Sieve implementation to do the actual checks that result in proper input to the tests. [STANDARDS TRACK] This document is a product of the Sieve Mail Filtering Language Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Jan 25 16:35:12 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 25 Jan 2008 16:35:12 -0800 (PST) Subject: [rfc-dist] RFC 5077 on Transport Layer Security (TLS) Session Resumption without Server-Side State Message-ID: <20080126003512.9576B10AFCC@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5077 Title: Transport Layer Security (TLS) Session Resumption without Server-Side State Author: J. Salowey, H. Zhou, P. Eronen, H. Tschofenig Status: Standards Track Date: January 2008 Mailbox: jsalowey at cisco.com, hzhou at cisco.com, pasi.eronen at nokia.com, Hannes.Tschofenig at nsn.com Pages: 20 Characters: 41989 Obsoletes: RFC4507 See-Also: I-D Tag: draft-salowey-tls-rfc4507bis-01.txt URL: http://www.rfc-editor.org/rfc/rfc5077.txt This document describes a mechanism that enables the Transport Layer Security (TLS) server to resume sessions and avoid keeping per-client session state. The TLS server encapsulates the session state into a ticket and forwards it to the client. The client can subsequently resume a session using the obtained ticket. This document obsoletes RFC 4507. [STANDARDS TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Jan 25 16:35:21 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 25 Jan 2008 16:35:21 -0800 (PST) Subject: [rfc-dist] RFC 5097 on MIB for the UDP-Lite protocol Message-ID: <20080126003521.ABC8610AFCE@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5097 Title: MIB for the UDP-Lite protocol Author: G. Renker, G. Fairhurst Status: Standards Track Date: January 2008 Mailbox: gerrit at erg.abdn.ac.uk, gorry at erg.abdn.ac.uk Pages: 23 Characters: 48944 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tsvwg-udplite-mib-03.txt URL: http://www.rfc-editor.org/rfc/rfc5097.txt This document specifies a Management Information Base (MIB) module for the Lightweight User Datagram Protocol (UDP-Lite). It defines a set of new MIB objects to characterise the behaviour and performance of transport layer endpoints deploying UDP-Lite. UDP-Lite resembles UDP, but differs from the semantics of UDP by the addition of a single option. This adds the capability for variable-length data checksum coverage, which can benefit a class of applications that prefer delivery of (partially) corrupted datagram payload data in preference to discarding the datagram. [STANDARDS TRACK] This document is a product of the Transport Area Working Group Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Jan 25 16:36:04 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 25 Jan 2008 16:36:04 -0800 (PST) Subject: [rfc-dist] RFC 5113 on Network Discovery and Selection Problem Message-ID: <20080126003604.210F910AFD4@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5113 Title: Network Discovery and Selection Problem Author: J. Arkko, B. Aboba, J. Korhonen, Ed., F. Bari Status: Informational Date: January 2008 Mailbox: jari.arkko at ericsson.com, bernarda at microsoft.com, jouni.korhonen at teliasonera.com, farooq.bari at att.com Pages: 39 Characters: 93250 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-eap-netsel-problem-09.txt URL: http://www.rfc-editor.org/rfc/rfc5113.txt When multiple access networks are available, users may have difficulty in selecting which network to connect to and how to authenticate with that network. This document defines the network discovery and selection problem, dividing it into multiple sub- problems. Some constraints on potential solutions are outlined, and the limitations of several solutions (including existing ones) are discussed. This memo provides information for the Internet community. This document is a product of the Extensible Authentication Protocol Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Jan 25 16:35:51 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 25 Jan 2008 16:35:51 -0800 (PST) Subject: [rfc-dist] RFC 5129 on Explicit Congestion Marking in MPLS Message-ID: <20080126003551.9840910AFD2@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5129 Title: Explicit Congestion Marking in MPLS Author: B. Davie, B. Briscoe, J. Tay Status: Standards Track Date: January 2008 Mailbox: bsd at cisco.com, bob.briscoe at bt.com, june.tay at bt.com Pages: 21 Characters: 49496 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tsvwg-ecn-mpls-02.txt URL: http://www.rfc-editor.org/rfc/rfc5129.txt RFC 3270 defines how to support the Diffserv architecture in MPLS networks, including how to encode Diffserv Code Points (DSCPs) in an MPLS header. DSCPs may be encoded in the EXP field, while other uses of that field are not precluded. RFC 3270 makes no statement about how Explicit Congestion Notification (ECN) marking might be encoded in the MPLS header. This document defines how an operator might define some of the EXP codepoints for explicit congestion notification, without precluding other uses. [STANDARDS TRACK] This document is a product of the Transport Area Working Group Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Jan 25 16:36:15 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 25 Jan 2008 16:36:15 -0800 (PST) Subject: [rfc-dist] RFC 5060 on Protocol Independent Multicast MIB Message-ID: <20080126003615.A9D1210AFD6@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5060 Title: Protocol Independent Multicast MIB Author: R. Sivaramu, J. Lingard, D. McWalter, B. Joshi, A. Kessler Status: Standards Track Date: January 2008 Mailbox: raghava at cisco.com, jchl at arastra.com, dmcw at dataconnection.com, bharat_joshi at infosys.com, kessler at cisco.com Pages: 90 Characters: 170123 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pim-mib-v2-10.txt URL: http://www.rfc-editor.org/rfc/rfc5060.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing the Protocol Independent Multicast (PIM) protocols: PIM-SM (Sparse Mode), BIDIR-PIM (Bidirectional), and PIM-DM (Dense Mode). This document is part of work in progress to obsolete RFC 2934, and is to be preferred where the two documents overlap. This document does not obsolete RFC 2934. [STANDARDS TRACK] This document is a product of the Protocol Independent Multicast Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Jan 25 16:36:28 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 25 Jan 2008 16:36:28 -0800 (PST) Subject: [rfc-dist] RFC 5059 on Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM) Message-ID: <20080126003628.447DD10AFD8@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5059 Title: Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM) Author: N. Bhaskar, A. Gall, J. Lingard, S. Venaas Status: Standards Track Date: January 2008 Mailbox: nidhi at arastra.com, alexander.gall at switch.ch, jchl at arastra.com, venaas at uninett.no Pages: 42 Characters: 100749 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pim-sm-bsr-12.txt URL: http://www.rfc-editor.org/rfc/rfc5059.txt This document specifies the Bootstrap Router (BSR) mechanism for the class of multicast routing protocols in the PIM (Protocol Independent Multicast) family that use the concept of a Rendezvous Point as a means for receivers to discover the sources that send to a particular multicast group. BSR is one way that a multicast router can learn the set of group-to-RP mappings required in order to function. The mechanism is dynamic, largely self-configuring, and robust to router failure. [STANDARDS TRACK] This document is a product of the Protocol Independent Multicast Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Jan 25 16:35:40 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 25 Jan 2008 16:35:40 -0800 (PST) Subject: [rfc-dist] RFC 5114 on Additional Diffie-Hellman Groups for Use with IETF Standards Message-ID: <20080126003540.D6FD410AFD0@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5114 Title: Additional Diffie-Hellman Groups for Use with IETF Standards Author: M. Lepinski, S. Kent Status: Informational Date: January 2008 Mailbox: mlepinski at bbn.com, kent at bbn.com Pages: 23 Characters: 49565 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-lepinski-dh-groups-03.txt URL: http://www.rfc-editor.org/rfc/rfc5114.txt This document describes eight Diffie-Hellman groups that can be used in conjunction with IETF protocols to provide security for Internet communications. The groups allow implementers to use the same groups with a variety of security protocols, e.g., SMIME, Secure SHell (SSH), Transport Layer Security (TLS), and Internet Key Exchange (IKE). All of these groups comply in form and structure with relevant standards from ISO, ANSI, NIST, and the IEEE. These groups are compatible with all IETF standards that make use of Diffie-Hellman or Elliptic Curve Diffie-Hellman cryptography. These groups and the associated test data are defined by NIST on their web site [EX80056A], but have not yet (as of this writing) been published in a formal NIST document. Publication of these groups and associated test data, as well as describing how to use Diffie-Hellman and Elliptic Curve Diffie-Hellman for key agreement in all of the protocols cited below, in one RFC, will facilitate development of interoperable implementations and support the Federal Information Processing Standard (FIPS) validation of implementations that make use of these groups. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Mon Jan 28 17:28:04 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 28 Jan 2008 17:28:04 -0800 (PST) Subject: [rfc-dist] RFC 5142 on Mobility Header Home Agent Switch Message Message-ID: <20080129012804.5554110B6DA@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5142 Title: Mobility Header Home Agent Switch Message Author: B. Haley, V. Devarapalli, H. Deng, J. Kempf Status: Standards Track Date: January 2008 Mailbox: brian.haley at hp.com, vijay.devarapalli at azairenet.com, kempf at docomolabs-usa.com, denghui at chinamobile.com Pages: 13 Characters: 27460 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip6-ha-switch-06.txt URL: http://www.rfc-editor.org/rfc/rfc5142.txt This document specifies a new Mobility Header message type that can be used between a home agent and mobile node to signal to a mobile node that it should acquire a new home agent. [STANDARDS TRACK] This document is a product of the Mobility for IPv6 Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Jan 31 16:32:23 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 31 Jan 2008 16:32:23 -0800 (PST) Subject: [rfc-dist] RFC 5110 on Overview of the Internet Multicast Routing Architecture Message-ID: <20080201003223.EF61710C789@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5110 Title: Overview of the Internet Multicast Routing Architecture Author: P. Savola Status: Informational Date: January 2008 Mailbox: psavola at funet.fi Pages: 25 Characters: 56217 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mboned-routingarch-12.txt URL: http://www.rfc-editor.org/rfc/rfc5110.txt This document describes multicast routing architectures that are currently deployed on the Internet. This document briefly describes those protocols and references their specifications. This memo also reclassifies several older RFCs to Historic. These RFCs describe multicast routing protocols that were never widely deployed or have fallen into disuse. This memo provides information for the Internet community. This document is a product of the MBONE Deployment Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Jan 31 17:23:48 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 31 Jan 2008 17:23:48 -0800 (PST) Subject: [rfc-dist] RFC 5116 on An Interface and Algorithms for Authenticated Encryption Message-ID: <20080201012348.0E3BF10C7A7@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5116 Title: An Interface and Algorithms for Authenticated Encryption Author: D. McGrew Status: Standards Track Date: January 2008 Mailbox: mcgrew at cisco.com Pages: 22 Characters: 50539 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-mcgrew-auth-enc-05.txt URL: http://www.rfc-editor.org/rfc/rfc5116.txt This document defines algorithms for Authenticated Encryption with Associated Data (AEAD), and defines a uniform interface and a registry for such algorithms. The interface and registry can be used as an application-independent set of cryptoalgorithm suites. This approach provides advantages in efficiency and security, and promotes the reuse of crypto implementations. [STANDARDS TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Jan 31 17:24:23 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 31 Jan 2008 17:24:23 -0800 (PST) Subject: [rfc-dist] RFC 5117 on RTP Topologies Message-ID: <20080201012423.6F6CE10C7AB@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5117 Title: RTP Topologies Author: M. Westerlund, S. Wenger Status: Informational Date: January 2008 Mailbox: magnus.westerlund at ericsson.com, stewe at stewe.org Pages: 21 Characters: 50293 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-topologies-07.txt URL: http://www.rfc-editor.org/rfc/rfc5117.txt This document discusses multi-endpoint topologies used in Real-time Transport Protocol (RTP)-based environments. In particular, centralized topologies commonly employed in the video conferencing industry are mapped to the RTP terminology. This memo provides information for the Internet community. This document is a product of the Audio/Video Transport Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Jan 31 17:24:14 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 31 Jan 2008 17:24:14 -0800 (PST) Subject: [rfc-dist] STD 68, RFC 5234 on Augmented BNF for Syntax Specifications: ABNF Message-ID: <20080201012414.CDB2910C7A9@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. STD 68 RFC 5234 Title: Augmented BNF for Syntax Specifications: ABNF Author: D. Crocker, Ed., P. Overell Status: Standards Track Date: January 2008 Mailbox: dcrocker at bbiw.net, paul.overell at thus.net Pages: 16 Characters: 26359 Obsoletes: RFC4234 See Also: STD0068 I-D Tag: draft-crocker-rfc4234bis-01.txt URL: http://www.rfc-editor.org/rfc/rfc5234.txt Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS TRACK] This is now a Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Jan 31 17:24:56 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 31 Jan 2008 17:24:56 -0800 (PST) Subject: [rfc-dist] RFC 5103 on Bidirectional Flow Export Using IP Flow Information Export (IPFIX) Message-ID: <20080201012456.1599B10C7B3@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5103 Title: Bidirectional Flow Export Using IP Flow Information Export (IPFIX) Author: B. Trammell, E. Boschi Status: Standards Track Date: January 2008 Mailbox: bht at cert.org, elisa.boschi at hitachi-eu.com Pages: 24 Characters: 53534 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipfix-biflow-05.txt URL: http://www.rfc-editor.org/rfc/rfc5103.txt This document describes an efficient method for exporting bidirectional flow (Biflow) information using the IP Flow Information Export (IPFIX) protocol, representing each Biflow using a single Flow Record. [STANDARDS TRACK] This document is a product of the IP Flow Information Export Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Jan 31 17:24:31 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 31 Jan 2008 17:24:31 -0800 (PST) Subject: [rfc-dist] RFC 5176 on Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS) Message-ID: <20080201012431.B67F010C7AD@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5176 Title: Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS) Author: M. Chiba, G. Dommety, M. Eklund, D. Mitton, B. Aboba Status: Informational Date: January 2008 Mailbox: mchiba at cisco.com, gdommety at cisco.com, meklund at cisco.com, david at mitton.com, bernarda at microsoft.com Pages: 34 Characters: 79541 Obsoletes: RFC3576 See-Also: I-D Tag: draft-ietf-radext-rfc3576bis-13.txt URL: http://www.rfc-editor.org/rfc/rfc5176.txt This document describes a currently deployed extension to the Remote Authentication Dial In User Service (RADIUS) protocol, allowing dynamic changes to a user session, as implemented by network access server products. This includes support for disconnecting users and changing authorizations applicable to a user session. This memo provides information for the Internet community. This document is a product of the RADIUS EXTensions Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Jan 31 17:24:48 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 31 Jan 2008 17:24:48 -0800 (PST) Subject: [rfc-dist] RFC 5102 on Information Model for IP Flow Information Export Message-ID: <20080201012448.8CAA310C7B1@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5102 Title: Information Model for IP Flow Information Export Author: J. Quittek, S. Bryant, B. Claise, P. Aitken, J. Meyer Status: Standards Track Date: January 2008 Mailbox: quittek at netlab.nec.de, stbryant at cisco.com, bclaise at cisco.com, paitken at cisco.com, jemeyer at paypal.com Pages: 171 Characters: 335617 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipfix-info-15.txt URL: http://www.rfc-editor.org/rfc/rfc5102.txt This memo defines an information model for the IP Flow Information eXport (IPFIX) protocol. It is used by the IPFIX protocol for encoding measured traffic information and information related to the traffic Observation Point, the traffic Metering Process, and the Exporting Process. Although developed for the IPFIX protocol, the model is defined in an open way that easily allows using it in other protocols, interfaces, and applications. [STANDARDS TRACK] This document is a product of the IP Flow Information Export Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Jan 31 17:24:40 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 31 Jan 2008 17:24:40 -0800 (PST) Subject: [rfc-dist] RFC 5101 on Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information Message-ID: <20080201012440.88CC210C7AF@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5101 Title: Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information Author: B. Claise, Ed. Status: Standards Track Date: January 2008 Mailbox: bclaise at cisco.com Pages: 63 Characters: 147196 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipfix-protocol-26.txt URL: http://www.rfc-editor.org/rfc/rfc5101.txt This document specifies the IP Flow Information Export (IPFIX) protocol that serves for transmitting IP Traffic Flow information over the network. In order to transmit IP Traffic Flow information from an Exporting Process to an information Collecting Process, a common representation of flow data and a standard means of communicating them is required. This document describes how the IPFIX Data and Template Records are carried over a number of transport protocols from an IPFIX Exporting Process to an IPFIX Collecting Process. [STANDARDS TRACK] This document is a product of the IP Flow Information Export Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ...