From rfc-editor at rfc-editor.org Wed Jun 13 10:33:05 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 13 Jun 2007 10:33:05 -0700 Subject: [rfc-dist] RFC 4904 on Representing Trunk Groups in tel/sip Uniform Resource Identifiers (URIs) Message-ID: <200706131733.l5DHX5BE010674@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4904 Title: Representing Trunk Groups in tel/sip Uniform Resource Identifiers (URIs) Author: V. Gurbani, C. Jennings Status: Standards Track Date: June 2007 Mailbox: vkg at alcatel-lucent.com, fluffy at cisco.com Pages: 19 Characters: 41027 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-iptel-trunk-group-10.txt URL: http://www.rfc-editor.org/rfc/rfc4904.txt This document describes a standardized mechanism to convey trunk group parameters in sip and tel Uniform Resource Identifiers (URIs). An extension to the tel URI is defined for this purpose. [STANDARDS TRACK] This document is a product of the IP Telephony 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 Jun 13 10:32:55 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 13 Jun 2007 10:32:55 -0700 Subject: [rfc-dist] BCP0097 RFC 4897 on Handling Normative References to Standards-Track Documents Message-ID: <200706131732.l5DHWtV2010669@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. BCP 97 RFC 4897 Title: Handling Normative References to Standards-Track Documents Author: J. Klensin, S. Hartman Status: Best Current Practice Date: June 2007 Mailbox: john-ietf at jck.com, hartmans-ietf at mit.edu Pages: 6 Characters: 13023 I-D Tag: draft-klensin-norm-ref-04.txt URL: http://www.rfc-editor.org/rfc/rfc4897.txt The Internet Engineering Task Force (IETF) and Request for Comments (RFC) Editor have a long-standing rule that a document at a given maturity level cannot be published until all of the documents that it references as normative are at that maturity level or higher. This rule has sometimes resulted in very long publication delays for documents and some claims that it was a major obstruction to advancing documents in maturity level. The IETF agreed on a way to bypass this rule with RFC 3967. This document describes a simpler procedure for downward references to Standards-Track and Best Current Practice (BCP) documents, namely "note and move on". The procedure in RFC 3967 still applies for downward references to other classes of documents. In both cases, annotations should be added to such References. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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 Jun 15 11:03:29 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 15 Jun 2007 11:03:29 -0700 Subject: [rfc-dist] RFC 4857 on Mobile IPv4 Regional Registration Message-ID: <200706151803.l5FI3TVM001840@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4857 Title: Mobile IPv4 Regional Registration Author: E. Fogelstroem, A. Jonsson, C. Perkins Status: Experimental Date: June 2007 Mailbox: eva.fogelstrom at ericsson.com, annika.jonsson at ericsson.com, charles.perkins at nsn.com Pages: 35 Characters: 79939 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip4-reg-tunnel-04.txt URL: http://www.rfc-editor.org/rfc/rfc4857.txt Using Mobile IP, a mobile node registers with its home agent each time it changes care-of address. This document describes a new kind of "regional registrations", i.e., registrations local to the visited domain. The regional registrations are performed via a new network entity called a Gateway Foreign Agent (GFA) and introduce a layer of hierarchy in the visited domain. Regional registrations reduce the number of signaling messages to the home network, and reduce the signaling delay when a mobile node moves from one foreign agent to another within the same visited domain. This document is an optional extension to the Mobile IPv4 protocol. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Mobility for IPv4 Working Group of the IETF. 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 Fri Jun 15 11:03:45 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 15 Jun 2007 11:03:45 -0700 Subject: [rfc-dist] RFC 4896 on Signaling Compression (SigComp) Corrections and Clarifications Message-ID: <200706151803.l5FI3jxf001845@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4896 Title: Signaling Compression (SigComp) Corrections and Clarifications Author: A. Surtees, M. West, A.B. Roach Status: Standards Track Date: June 2007 Mailbox: abigail.surtees at roke.co.uk, mark.a.west at roke.co.uk, adam at estacado.net Pages: 28 Characters: 58435 Updates: RFC3320, RFC3321, RFC3485 See-Also: I-D Tag: draft-ietf-rohc-sigcomp-impl-guide-10.txt URL: http://www.rfc-editor.org/rfc/rfc4896.txt This document describes common misinterpretations and some ambiguities in the Signaling Compression Protocol (SigComp), and offers guidance to developers to resolve any resultant problems. SigComp defines a scheme for compressing messages generated by application protocols such as the Session Initiation Protocol (SIP). This document updates the following RFCs: RFC 3320, RFC 3321, and RFC 3485. [STANDARDS TRACK] This document is a product of the Robust Header Compression 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 Jun 15 11:03:57 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 15 Jun 2007 11:03:57 -0700 Subject: [rfc-dist] RFC 4901 on Protocol Extensions for Header Compression over MPLS Message-ID: <200706151803.l5FI3vsO001850@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4901 Title: Protocol Extensions for Header Compression over MPLS Author: J. Ash, Ed., J. Hand, Ed., A. Malis, Ed. Status: Standards Track Date: June 2007 Mailbox: gash5107 at yahoo.com, jameshand at att.com, andrew.g.malis at verizon.com Pages: 34 Characters: 78801 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-hc-over-mpls-protocol-08.txt URL: http://www.rfc-editor.org/rfc/rfc4901.txt This specification defines how to use Multi-Protocol Label Switching (MPLS) to route Header-Compressed (HC) packets over an MPLS label switched path. HC can significantly reduce packet-header overhead and, in combination with MPLS, can also increases bandwidth efficiency and processing scalability in terms of the maximum number of simultaneous compressed flows that use HC at each router). Here we define how MPLS pseudowires are used to transport the HC context and control messages between the ingress and egress MPLS label switching routers. This is defined for a specific set of existing HC mechanisms that might be used, for example, to support voice over IP. This specification also describes extension mechanisms to allow support for future, as yet to be defined, HC protocols. In this specification, each HC protocol operates independently over a single pseudowire instance, very much as it would over a single point-to-point link. [STANDARDS TRACK] This document is a product of the Audio/Video Transport 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 Jun 15 11:04:10 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 15 Jun 2007 11:04:10 -0700 Subject: [rfc-dist] RFC 4907 on Architectural Implications of Link Indications Message-ID: <200706151804.l5FI4AID001855@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4907 Title: Architectural Implications of Link Indications Author: B. Aboba, Ed. Status: Informational Date: June 2007 Mailbox: bernarda at microsoft.com Pages: 62 Characters: 160604 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-link-indications-10.txt URL: http://www.rfc-editor.org/rfc/rfc4907.txt A link indication represents information provided by the link layer to higher layers regarding the state of the link. This document describes the role of link indications within the Internet architecture. While the judicious use of link indications can provide performance benefits, inappropriate use can degrade both robustness and performance. This document summarizes current proposals, describes the architectural issues, and provides examples of appropriate and inappropriate uses of link indications. This memo provides information for the Internet community. This document is a product of the Internet Architecture Board. 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-ed at ISI.EDU Sat Jun 16 21:10:37 2007 From: rfc-ed at ISI.EDU (rfc-ed@ISI.EDU) Date: Jan, 17 Jun 2007 16:10:37 +1200 Subject: [rfc-dist] Stop gaining weight and get the figure you want Message-ID: <119521558220235289.19906301048842645@ISI.EDU> Are you trying to lose weight but you are too concerned about your health? Anatrim has the perfect suggestion for you. It is 100% natural and safe and it will help you fight off the hunger and food cravings in a way that will not damage your health. Order here http://www.piollsa.com/?nanemc From rfc-editor at rfc-editor.org Wed Jun 20 17:28:03 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 20 Jun 2007 17:28:03 -0700 (PDT) Subject: [rfc-dist] RFC 4784 on Verizon Wireless Dynamic Mobile IP Key Update for cdma2000(R) Networks Message-ID: <20070621002803.ED319D6BAE@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4784 Title: Verizon Wireless Dynamic Mobile IP Key Update for cdma2000(R) Networks Author: C. Carroll, F. Quick Status: Informational Date: June 2007 Mailbox: Christopher.Carroll at ropesgray.com, fquick at qualcomm.com Pages: 45 Characters: 102856 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-carroll-dynmobileip-cdma-05.txt URL: http://www.rfc-editor.org/rfc/rfc4784.txt The Verizon Wireless Dynamic Mobile IP Key Update procedure is a mechanism for distributing and updating Mobile IP (MIP) cryptographic keys in cdma2000(R) networks (including High Rate Packet Data, which is often referred to as 1xEV-DO). The Dynamic Mobile IP Key Update (DMU) procedure occurs between the MIP Mobile Node (MN) and RADIUS Authentication, Authorization and Accounting (AAA) Server via a cdma2000(R) Packet Data Serving Node (PDSN) that is acting as a Mobile IP Foreign Agent (FA). cdma2000(R) is a registered trademark of the Telecommunications Industry Association (TIA). 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 Jun 20 17:28:34 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 20 Jun 2007 17:28:34 -0700 (PDT) Subject: [rfc-dist] RFC 4905 on Encapsulation Methods for Transport of Layer 2 Frames over MPLS Networks Message-ID: <20070621002834.EDA1DD6BB2@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4905 Title: Encapsulation Methods for Transport of Layer 2 Frames over MPLS Networks Author: L. Martini, Ed., E. Rosen, Ed., N. El-Aawar, Ed. Status: Historic Date: June 2007 Mailbox: lmartini at cisco.com, erosen at cisco.com, nna at level3.net Pages: 20 Characters: 40020 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-martini-l2circuit-encap-mpls-12.txt URL: http://www.rfc-editor.org/rfc/rfc4905.txt This document describes methods for encapsulating the Protocol Data Units (PDUs) of layer 2 protocols such as Frame Relay, Asynchronous Transfer Mode (ATM), or Ethernet for transport across an MPLS network. This document describes the so-called "draft-martini" protocol, which has since been superseded by the Pseudowire Emulation Edge to Edge Working Group specifications described in RFC 4447 and related documents. This memo defines a Historic Document for the Internet community. HISTORIC: This memo defines a Historic Document 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 Jun 20 17:28:24 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 20 Jun 2007 17:28:24 -0700 (PDT) Subject: [rfc-dist] RFC 4916 on Connected Identity in the Session Initiation Protocol (SIP) Message-ID: <20070621002824.08838D6BB0@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4916 Title: Connected Identity in the Session Initiation Protocol (SIP) Author: J. Elwell Status: Standards Track Date: June 2007 Mailbox: john.elwell at siemens.com Pages: 24 Characters: 42924 Updates: RFC3261 See-Also: I-D Tag: draft-ietf-sip-connected-identity-05.txt URL: http://www.rfc-editor.org/rfc/rfc4916.txt This document provides a means for a Session Initiation Protocol (SIP) User Agent (UA) that receives a dialog-forming request to supply its identity to the peer UA by means of a request in the reverse direction, and for that identity to be signed by an Authentication Service. Because of retargeting of a dialog-forming request (changing the value of the Request-URI), the UA that receives it (the User Agent Server, UAS) can have a different identity from that in the To header field. The same mechanism can be used to indicate a change of identity during a dialog, e.g., because of some action in the Public Switched Telephone Network (PSTN) behind a gateway. This document normatively updates RFC 3261 (SIP). [STANDARDS TRACK] This document is a product of the Session Initiation Protocol 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 Jun 20 17:28:49 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 20 Jun 2007 17:28:49 -0700 (PDT) Subject: [rfc-dist] RFC 4906 on Transport of Layer 2 Frames Over MPLS Message-ID: <20070621002849.9F7B4D6BB4@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4906 Title: Transport of Layer 2 Frames Over MPLS Author: L. Martini, Ed., E. Rosen, Ed., N. El-Aawar, Ed. Status: Historic Date: June 2007 Mailbox: lmartini at cisco.com, erosen at cisco.com, nna at level3.net Pages: 22 Characters: 47403 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-martini-l2circuit-trans-mpls-19.txt URL: http://www.rfc-editor.org/rfc/rfc4906.txt This document describes methods for transporting the Protocol Data Units (PDUs) of layer 2 protocols such as Frame Relay, Asynchronous Transfer Mode (ATM) Adaption Layer 5 (AAL5), and Ethernet, and for providing a Synchronized Optical Network (SONET) circuit emulation service across an MPLS network. This document describes the so-called "draft-martini" protocol, which has since been superseded by the Pseudowire Emulation Edge to Edge Working Group specifications described in RFC 4447 and related documents. This memo defines a Historic Document for the Internet community. HISTORIC: This memo defines a Historic Document 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 Jun 20 17:29:15 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 20 Jun 2007 17:29:15 -0700 (PDT) Subject: [rfc-dist] RFC 4892 on Requirements for a Mechanism Identifying a Name Server Instance Message-ID: <20070621002915.7EF27D6BB6@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4892 Title: Requirements for a Mechanism Identifying a Name Server Instance Author: S. Woolf, D. Conrad Status: Informational Date: June 2007 Mailbox: woolf at isc.org, david.conrad at icann.org Pages: 8 Characters: 17605 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dnsop-serverid-08.txt URL: http://www.rfc-editor.org/rfc/rfc4892.txt With the increased use of DNS anycast, load balancing, and other mechanisms allowing more than one DNS name server to share a single IP address, it is sometimes difficult to tell which of a pool of name servers has answered a particular query. A standardized mechanism to determine the identity of a name server responding to a particular query would be useful, particularly as a diagnostic aid for administrators. Existing ad hoc mechanisms for addressing this need have some shortcomings, not the least of which is the lack of prior analysis of exactly how such a mechanism should be designed and deployed. This document describes the existing convention used in some widely deployed implementations of the DNS protocol, including advantages and disadvantages, and discusses some attributes of an improved mechanism. This memo provides information for the Internet community. This document is a product of the Domain Name System Operations 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 Jun 25 17:21:38 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 25 Jun 2007 17:21:38 -0700 (PDT) Subject: [rfc-dist] RFC 4903 on Multi-Link Subnet Issues Message-ID: <20070626002138.B104DD884C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4903 Title: Multi-Link Subnet Issues Author: D. Thaler Status: Informational Date: June 2007 Mailbox: dthaler at microsoft.com Pages: 17 Characters: 39671 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-multilink-subnet-issues-03.txt URL: http://www.rfc-editor.org/rfc/rfc4903.txt There have been several proposals around the notion that a subnet may span multiple links connected by routers. This memo documents the issues and potential problems that have been raised with such an approach. This memo provides information for the Internet community. This document is a product of the Internet Architecture Board. 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 Jun 25 17:21:34 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 25 Jun 2007 17:21:34 -0700 (PDT) Subject: [rfc-dist] RFC 4917 on Mobile IPv4 Message String Extension Message-ID: <20070626002134.BDFCAD884A@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4917 Title: Mobile IPv4 Message String Extension Author: V. Sastry, K. Leung, A. Patel Status: Standards Track Date: June 2007 Mailbox: venkat.s at samsung.com, kleung at cisco.com, alpesh at cisco.com Pages: 7 Characters: 13302 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip4-message-string-ext-03.txt URL: http://www.rfc-editor.org/rfc/rfc4917.txt This document specifies a new extension for use in Mobile IPv4. This extension can be added by the Home Agent and the Foreign Agent to Registration Reply messages. This extension carries a text string that is intended for the user of the Mobile Node. [STANDARDS TRACK] This document is a product of the Mobility for IPv4 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 Tue Jun 26 16:03:28 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 26 Jun 2007 16:03:28 -0700 (PDT) Subject: [rfc-dist] BCP0129 RFC 4929 on Change Process for Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Protocols and Procedures Message-ID: <20070626230328.9A2C5D8AAA@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. BCP 129 RFC 4929 Title: Change Process for Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Protocols and Procedures Author: L. Andersson, Ed., A. Farrel, Ed. Status: Best Current Practice Date: June 2007 Mailbox: loa at pi.se, adrian at olddog.co.uk Pages: 23 Characters: 56742 Updates: See-Also: BCP0129 I-D Tag: draft-andersson-rtg-gmpls-change-08.txt URL: http://www.rfc-editor.org/rfc/rfc4929.txt This document provides guidelines for applying or extending the MPLS or GMPLS ((G)MPLS) protocol suites and clarifies the IETF's (G)MPLS working groups' responsibility for the (G)MPLS protocols. This document is directed to multi-vendor fora and Standards Development Organizations (SDOs) to provide an understanding of (G)MPLS work in the IETF and documents the requisite use of IETF review procedures when considering (G)MPLS applications or protocol extensions in their work. This document does not modify IETF processes. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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 Tue Jun 26 16:03:32 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 26 Jun 2007 16:03:32 -0700 (PDT) Subject: [rfc-dist] RFC 4908 on Multi-homing for small scale fixed network Using Mobile IP and NEMO Message-ID: <20070626230332.F2A9ED8AAC@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4908 Title: Multi-homing for small scale fixed network Using Mobile IP and NEMO Author: K. Nagami, S. Uda, N. Ogashiwa, H. Esaki, R. Wakikawa, H. Ohnishi Status: Experimental Date: June 2007 Mailbox: nagami at inetcore.com, zin at jaist.ac.jp, ogashiwa at wide.ad.jp, hiroshi at wide.ad.jp, ryuji at sfc.wide.ad.jp, ohnishi.hiroyuki at lab.ntt.co.jp Pages: 10 Characters: 20230 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-nagami-mip6-nemo-multihome-fixed-network-04.txt URL: http://www.rfc-editor.org/rfc/rfc4908.txt Multihoming technology improves the availability of host and network connectivity. Since the behaviors of fixed and mobile networks differ, distinct architectures for each have been discussed and proposed. This document proposes a common architecture for both mobile and fixed networking environments, using mobile IP (RFC 3775) and Network Mobility (NEMO; RFC 3963). The proposed architecture requires a modification of mobile IP and NEMO so that multiple Care-of Addresses (CoAs) can be used. In addition, multiple Home Agents (HAs) that are located in different places are required for redundancy. 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 Tue Jun 26 16:03:36 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 26 Jun 2007 16:03:36 -0700 (PDT) Subject: [rfc-dist] RFC 4927 on Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering Message-ID: <20070626230336.BC05ED8AAE@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4927 Title: Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering Author: J.-L. Le Roux, Ed. Status: Informational Date: June 2007 Mailbox: jeanlouis.leroux at orange-ftgroup.com Pages: 12 Characters: 25016 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pce-pcecp-interarea-reqs-05.txt URL: http://www.rfc-editor.org/rfc/rfc4927.txt For scalability purposes, a network may comprise multiple Interior Gateway Protocol (IGP) areas. An inter-area Traffic Engineered Label Switched Path (TE-LSP) is an LSP that transits through at least two IGP areas. In a multi-area network, topology visibility remains local to a given area, and a head-end Label Switching Router (LSR) cannot compute an inter-area shortest constrained path. One key application of the Path Computation Element (PCE)-based architecture is the computation of inter-area TE-LSP paths. The PCE Communication Protocol (PCECP) is used to communicate computation requests from Path Computation Clients (PCCs) to PCEs, and to return computed paths in responses. This document lists a detailed set of PCECP-specific requirements for support of inter-area TE-LSP path computation. It complements the generic requirements for a PCE Communication Protocol. This memo provides information for the Internet community. This document is a product of the Path Computation Element 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 Wed Jun 27 17:25:59 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 27 Jun 2007 17:25:59 -0700 (PDT) Subject: [rfc-dist] RFC 4909 on Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport Message-ID: <20070628002559.DD312D8ECC@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4909 Title: Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport Author: L. Dondeti, Ed., D. Castleford, F. Hartung Status: Informational Date: June 2007 Mailbox: ldondeti at qualcomm.com, david.castleford at orange-ftgroup.com, frank.hartung at ericsson.com Pages: 7 Characters: 12228 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-dondeti-msec-mikey-genext-oma-04.txt URL: http://www.rfc-editor.org/rfc/rfc4909.txt This document specifies a new Multimedia Internet KEYing (MIKEY) General Extension payload (RFC 3830) to transport the short-term key message (STKM) and long-term key message (LTKM) payloads defined in the Open Mobile Alliance's (OMA) Browser and Content (BAC) Broadcast (BCAST) group's Service and Content protection specification. 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 Jun 27 17:26:03 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 27 Jun 2007 17:26:03 -0700 (PDT) Subject: [rfc-dist] BCP0128 RFC 4928 on Avoiding Equal Cost Multipath Treatment in MPLS Networks Message-ID: <20070628002603.8A6E6D8ECE@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. BCP 128 RFC 4928 Title: Avoiding Equal Cost Multipath Treatment in MPLS Networks Author: G. Swallow, S. Bryant, L. Andersson Status: Best Current Practice Date: June 2007 Mailbox: stbryant at cisco.com, swallow at cisco.com, loa at pi.se Pages: 8 Characters: 18376 Updates: See-Also: BCP0128 I-D Tag: draft-ietf-mpls-ecmp-bcp-03.txt URL: http://www.rfc-editor.org/rfc/rfc4928.txt This document describes the Equal Cost Multipath (ECMP) behavior of currently deployed MPLS networks. This document makes best practice recommendations for anyone defining an application to run over an MPLS network that wishes to avoid the reordering that can result from transmission of different packets from the same flow over multiple different equal cost paths. These recommendations rely on inspection of the IP version number field in packets. Despite the heuristic nature of the recommendations, they provide a relatively safe way to operate MPLS networks, even if future allocations of IP version numbers were made for some purpose. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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 Jun 27 17:25:59 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 27 Jun 2007 17:25:59 -0700 (PDT) Subject: [rfc-dist] RFC 4909 on Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport Message-ID: <20070628002559.DD312D8ECC@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4909 Title: Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport Author: L. Dondeti, Ed., D. Castleford, F. Hartung Status: Informational Date: June 2007 Mailbox: ldondeti at qualcomm.com, david.castleford at orange-ftgroup.com, frank.hartung at ericsson.com Pages: 7 Characters: 12228 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-dondeti-msec-mikey-genext-oma-04.txt URL: http://www.rfc-editor.org/rfc/rfc4909.txt This document specifies a new Multimedia Internet KEYing (MIKEY) General Extension payload (RFC 3830) to transport the short-term key message (STKM) and long-term key message (LTKM) payloads defined in the Open Mobile Alliance's (OMA) Browser and Content (BAC) Broadcast (BCAST) group's Service and Content protection specification. 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 .. _______________________________________________ IETF-Announce mailing list IETF-Announce at ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ From rfc-editor at rfc-editor.org Sat Jun 30 14:37:40 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 30 Jun 2007 14:37:40 -0700 (PDT) Subject: [rfc-dist] RFC 4937 on IANA Considerations for PPP over Ethernet (PPPoE) Message-ID: <20070630213740.0458AD9368@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4937 Title: IANA Considerations for PPP over Ethernet (PPPoE) Author: P. Arberg, V. Mammoliti Status: Informational Date: June 2007 Mailbox: parberg at redback.com, vince at cisco.com Pages: 6 Characters: 11070 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-arberg-pppoe-iana-03.txt URL: http://www.rfc-editor.org/rfc/rfc4937.txt This document describes the IANA considerations for the PPP over Ethernet (PPPoE) protocol. 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 Sat Jun 30 14:37:51 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 30 Jun 2007 14:37:51 -0700 (PDT) Subject: [rfc-dist] RFC 4938 on PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics Message-ID: <20070630213751.A68FDD936A@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4938 Title: PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics Author: B. Berry, H. Holgate Status: Informational Date: June 2007 Mailbox: bberry at cisco.com, hholgate at cisco.com Pages: 17 Characters: 38288 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-bberry-pppoe-credit-06.txt URL: http://www.rfc-editor.org/rfc/rfc4938.txt This document extends the Point-to-Point over Ethernet (PPPoE) Protocol with a credit-based flow control mechanism and Link Quality Metric report. This optional extension should improve the performance of PPPoE over media with variable bandwidth and limited buffering, such as mobile radio links. 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 Sat Jun 30 14:38:00 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 30 Jun 2007 14:38:00 -0700 (PDT) Subject: [rfc-dist] RFC 4915 on Multi-Topology (MT) Routing in OSPF Message-ID: <20070630213800.7791BD936C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4915 Title: Multi-Topology (MT) Routing in OSPF Author: P. Psenak, S. Mirtorabi, A. Roy, L. Nguyen, P. Pillay-Esnault Status: Standards Track Date: June 2007 Mailbox: ppsenak at cisco.com, sina at force10networks.com, akr at cisco.com, lhnguyen at cisco.com, ppe at cisco.com Pages: 20 Characters: 43115 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ospf-mt-08.txt URL: http://www.rfc-editor.org/rfc/rfc4915.txt This document describes an extension to Open Shortest Path First (OSPF) in order to define independent IP topologies called Multi- Topologies (MTs). The Multi-Topologies extension can be used for computing different paths for unicast traffic, multicast traffic, different classes of service based on flexible criteria, or an in- band network management topology. An optional extension to exclude selected links from the default topology is also described. [STANDARDS TRACK] This document is a product of the Open Shortest Path First IGP 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 Sat Jun 30 14:38:14 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 30 Jun 2007 14:38:14 -0700 (PDT) Subject: [rfc-dist] RFC 4918 on HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) Message-ID: <20070630213814.0647AD936E@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4918 Title: HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) Author: L. Dusseault, Ed. Status: Standards Track Date: June 2007 Mailbox: ldusseault at commerce.net Pages: 127 Characters: 276352 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-webdav-rfc2518bis-18.txt URL: http://www.rfc-editor.org/rfc/rfc4918.txt Web Distributed Authoring and Versioning (WebDAV) consists of a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, URL namespace manipulation, and resource locking (collision avoidance). RFC 2518 was published in February 1999, and this specification obsoletes RFC 2518 with minor revisions mostly due to interoperability experience. [STANDARDS TRACK] This document is a product of the WWW Distributed Authoring and Versioning 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 Sat Jun 30 14:38:31 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 30 Jun 2007 14:38:31 -0700 (PDT) Subject: [rfc-dist] RFC 4881 on Low-Latency Handoffs in Mobile IPv4 Message-ID: <20070630213831.3652AD9370@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4881 Title: Low-Latency Handoffs in Mobile IPv4 Author: K. El Malki, Ed. Status: Experimental Date: June 2007 Mailbox: karim at athonet.com Pages: 64 Characters: 151124 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mobileip-lowlatency-handoffs-v4-11.txt URL: http://www.rfc-editor.org/rfc/rfc4881.txt Mobile IPv4 describes how a Mobile Node can perform IPv4-layer handoffs between subnets served by different Foreign Agents. In certain cases, the latency involved in these handoffs can be above the threshold required for the support of delay-sensitive or real-time services. The aim of this document is to present two methods to achieve low-latency Mobile IPv4 handoffs. In addition, a combination of these two methods is described. The described techniques allow greater support for real-time services on a Mobile IPv4 network by minimizing the period of time when a Mobile Node is unable to send or receive IPv4 packets due to the delay in the Mobile IPv4 Registration process. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Mobility for IPv4 Working Group of the IETF. 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 Sat Jun 30 14:38:40 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 30 Jun 2007 14:38:40 -0700 (PDT) Subject: [rfc-dist] RFC 4878 on Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces Message-ID: <20070630213840.9C5B7D9372@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4878 Title: Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces Author: M. Squire Status: Standards Track Date: June 2007 Mailbox: msquire at hatterasnetworks.com Pages: 58 Characters: 130067 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hubmib-efm-mib-06.txt URL: http://www.rfc-editor.org/rfc/rfc4878.txt This document defines objects for managing Operations, Administration, and Maintenance (OAM) capabilities on Ethernet-like interfaces conformant to the Ethernet OAM functionality defined in the Ethernet in the First Mile (EFM) clauses of the Ethernet standards. The Ethernet OAM functionality is complementary to the Simple Network Management Protocol (SNMP) in that it is focused on a small set of link-specific functions for directly connected Ethernet interfaces. This document defines objects for controlling those link OAM functions and for providing results and status of the OAM functions to management entities. [STANDARDS TRACK] This document is a product of the Ethernet Interfaces and Hub MIB 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 ...