From rfc-editor at rfc-editor.org Thu Sep 6 08:55:17 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 6 Sep 2007 08:55:17 -0700 (PDT) Subject: [rfc-dist] RFC 4964 on The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular Message-ID: <20070906155517.0C73DE0FB8@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4964 Title: The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular Author: A. Allen, Ed., J. Holm, T. Hallin Status: Informational Date: September 2007 Mailbox: aallen at rim.com, Jan.Holm at ericsson.com, thallin at motorola.com Pages: 32 Characters: 67505 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-allen-sipping-poc-p-answer-state-header-05.txt URL: http://www.rfc-editor.org/rfc/rfc4964.txt This document describes a private Session Initiation Protocol (SIP) header (P-header) used by the Open Mobile Alliance (OMA) for Push to talk over Cellular (PoC) along with its applicability, which is limited to the OMA PoC application. The P-Answer-State header is used for indicating the answering mode of the handset, which is particular to the PoC application. 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 Thu Sep 6 08:55:50 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 6 Sep 2007 08:55:50 -0700 (PDT) Subject: [rfc-dist] RFC 5003 on Attachment Individual Identifier (AII) Types for Aggregation Message-ID: <20070906155550.00117E0FBC@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5003 Title: Attachment Individual Identifier (AII) Types for Aggregation Author: C. Metz, L. Martini, F. Balus, J. Sugimoto Status: Standards Track Date: September 2007 Mailbox: chmetz at cisco.com, lmartini at cisco.com, florin.balus at alcatel-lucent.com, sugimoto at nortel.com Pages: 7 Characters: 14559 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pwe3-aii-aggregate-02.txt URL: http://www.rfc-editor.org/rfc/rfc5003.txt The signaling protocols used to establish point-to-point pseudowires include type-length-value (TLV) fields that identify pseudowire endpoints called attachment individual identifiers (AIIs). This document defines AII structures in the form of new AII TLV fields that support AII aggregation for improved scalability and Virtual Private Network (VPN) auto-discovery. It is envisioned that this would be useful in large inter-domain virtual private wire service networks where pseudowires are established between selected local and remote provider edge (PE) nodes based on customer need. [STANDARDS TRACK] This document is a product of the Pseudo Wire Emulation Edge to Edge 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 Sep 6 08:55:27 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 6 Sep 2007 08:55:27 -0700 (PDT) Subject: [rfc-dist] RFC 4990 on Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks Message-ID: <20070906155527.C944BE0FBA@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4990 Title: Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks Author: K. Shiomoto, R. Papneja, R. Rabbat Status: Informational Date: September 2007 Mailbox: shiomoto.kohei at lab.ntt.co.jp, rabbat at alum.mit.edu, rpapneja at isocore.com Pages: 23 Characters: 50908 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-gmpls-addressing-08.txt URL: http://www.rfc-editor.org/rfc/rfc4990.txt This document clarifies the use of addresses in Generalized Multiprotocol Label Switching (GMPLS) networks. The aim is to facilitate interworking of GMPLS-capable Label Switching Routers (LSRs). The document is based on experience gained in implementation, interoperability testing, and deployment. The document describes how to interpret address and identifier fields within GMPLS protocols, and how to choose which addresses to set in those fields for specific control plane usage models. It also discusses how to handle IPv6 sources and destinations in the MPLS and GMPLS Traffic Engineering (TE) Management Information Base (MIB) modules. This document does not define new procedures or processes. Whenever this document makes requirements statements or recommendations, these are taken from normative text in the referenced RFCs. This memo provides information for the Internet community. This document is a product of the Common Control and Measurement Plane 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 Sep 6 08:56:07 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 6 Sep 2007 08:56:07 -0700 (PDT) Subject: [rfc-dist] RFC 5011 on Automated Updates of DNS Security (DNSSEC) Trust Anchors Message-ID: <20070906155607.6D12FE0FBE@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5011 Title: Automated Updates of DNS Security (DNSSEC) Trust Anchors Author: M. StJohns Status: Standards Track Date: September 2007 Mailbox: mstjohns at comcast.net Pages: 14 Characters: 30138 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dnsext-trustupdate-timers-06.txt URL: http://www.rfc-editor.org/rfc/rfc5011.txt This document describes a means for automated, authenticated, and authorized updating of DNSSEC "trust anchors". The method provides protection against N-1 key compromises of N keys in the trust point key set. Based on the trust established by the presence of a current anchor, other anchors may be added at the same place in the hierarchy, and, ultimately, supplant the existing anchor(s). This mechanism will require changes to resolver management behavior (but not resolver resolution behavior), and the addition of a single flag bit to the DNSKEY record. [STANDARDS TRACK] This document is a product of the DNS Extensions 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 Sep 6 08:56:19 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 6 Sep 2007 08:56:19 -0700 (PDT) Subject: [rfc-dist] RFC 5032 on WITHIN Search Extension to the IMAP Protocol Message-ID: <20070906155619.B71BCE0FC0@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5032 Title: WITHIN Search Extension to the IMAP Protocol Author: E. Burger, Ed. Status: Standards Track Date: September 2007 Mailbox: eric.burger at bea.com Pages: 5 Characters: 8921 Updates: RFC3501 See-Also: I-D Tag: draft-ietf-lemonade-search-within-05.txt URL: http://www.rfc-editor.org/rfc/rfc5032.txt This document describes the WITHIN extension to IMAP SEARCH. IMAP SEARCH returns messages whose internal date is within or outside a specified interval. The mechanism described here, OLDER and YOUNGER, differs from BEFORE and SINCE in that the client specifies an interval, rather than a date. WITHIN is useful for persistent searches where either the device does not have the capacity to perform the search at regular intervals or the network is of limited bandwidth and thus there is a desire to reduce network traffic from sending repeated requests and redundant responses. [STANDARDS TRACK] This document is a product of the Enhancements to Internet email to support diverse service environments 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 Sep 7 17:40:04 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 7 Sep 2007 17:40:04 -0700 (PDT) Subject: [rfc-dist] RFC 5010 on The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption Message-ID: <20070908004004.DBCA7E11BC@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5010 Title: The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption Author: K. Kinnear, M. Normoyle, M. Stapp Status: Standards Track Date: September 2007 Mailbox: kkinnear at cisco.com, mnormoyle at cisco.com, mjs at cisco.com Pages: 7 Characters: 13834 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-relay-agent-flags-03.txt URL: http://www.rfc-editor.org/rfc/rfc5010.txt This memo defines a new suboption of the Dynamic Host Configuration Protocol (DHCP) relay agent information option that allows the DHCP relay to specify flags for the forwarded packet. One flag is defined to indicate whether the DHCP relay received the packet via a unicast or broadcast packet. This information may be used by the DHCP server to better serve clients based on whether their request was originally broadcast or unicast. [STANDARDS TRACK] This document is a product of the Dynamic Host Configuration 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 Sep 7 17:39:48 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 7 Sep 2007 17:39:48 -0700 (PDT) Subject: [rfc-dist] RFC 4981 on Survey of Research towards Robust Peer-to-Peer Networks: Search Methods Message-ID: <20070908003948.61424E11BA@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4981 Title: Survey of Research towards Robust Peer-to-Peer Networks: Search Methods Author: J. Risson, T. Moors Status: Informational Date: September 2007 Mailbox: jr at tuffit.com, t.moors at unsw.edu.au Pages: 91 Characters: 239752 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-p2prg-survey-search-01.txt URL: http://www.rfc-editor.org/rfc/rfc4981.txt The pace of research on peer-to-peer (P2P) networking in the last five years warrants a critical survey. P2P has the makings of a disruptive technology -- it can aggregate enormous storage and processing resources while minimizing entry and scaling costs. Failures are common amongst massive numbers of distributed peers, though the impact of individual failures may be less than in conventional architectures. Thus, the key to realizing P2P's potential in applications other than casual file sharing is robustness. P2P search methods are first couched within an overall P2P taxonomy. P2P indexes for simple key lookup are assessed, including those based on Plaxton trees, rings, tori, butterflies, de Bruijn graphs, and skip graphs. Similarly, P2P indexes for keyword lookup, information retrieval and data management are explored. Finally, early efforts to optimize range, multi-attribute, join, and aggregation queries over P2P indexes are reviewed. Insofar as they are available in the primary literature, robustness mechanisms and metrics are highlighted throughout. However, the low-level mechanisms that most affect robustness are not well isolated in the literature. Recommendations are given for future research. 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 Fri Sep 7 17:40:31 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 7 Sep 2007 17:40:31 -0700 (PDT) Subject: [rfc-dist] RFC 5022 on Media Server Control Markup Language (MSCML) and Protocol Message-ID: <20070908004031.27470E11BE@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5022 Title: Media Server Control Markup Language (MSCML) and Protocol Author: J. Van Dyke, E. Burger, Ed., A. Spitzer Status: Informational Date: September 2007 Mailbox: jvandyke at cantata.com, eburger at standardstrack.com, woof at pingtel.com Pages: 81 Characters: 184482 Obsoletes: RFC4722 See-Also: I-D Tag: none URL: http://www.rfc-editor.org/rfc/rfc5022.txt Media Server Control Markup Language (MSCML) is a markup language used in conjunction with SIP to provide advanced conferencing and interactive voice response (IVR) functions. MSCML presents an application-level control model, as opposed to device-level control models. One use of this protocol is for communications between a conference focus and mixer in the IETF SIP Conferencing Framework. 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 Fri Sep 7 17:41:00 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 7 Sep 2007 17:41:00 -0700 (PDT) Subject: [rfc-dist] RFC 5005 on Feed Paging and Archiving Message-ID: <20070908004100.53CAFE11C2@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5005 Title: Feed Paging and Archiving Author: M. Nottingham Status: Standards Track Date: September 2007 Mailbox: mnot at pobox.com Pages: 15 Characters: 28937 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-nottingham-atompub-feed-history-11.txt URL: http://www.rfc-editor.org/rfc/rfc5005.txt This specification defines three types of syndicated Web feeds that enable publication of entries across one or more feed documents. This includes "paged" feeds for piecemeal access, "archived" feeds that allow reconstruction of the feed's contents, and feeds that are explicitly "complete". [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 Sep 7 17:40:48 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 7 Sep 2007 17:40:48 -0700 (PDT) Subject: [rfc-dist] RFC 5004 on Avoid BGP Best Path Transitions from One External to Another Message-ID: <20070908004048.48888E11C0@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5004 Title: Avoid BGP Best Path Transitions from One External to Another Author: E. Chen, S. Sangli Status: Standards Track Date: September 2007 Mailbox: enkechen at cisco.com, rsrihari at cisco.com Pages: 6 Characters: 11437 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-idr-avoid-transition-05.txt URL: http://www.rfc-editor.org/rfc/rfc5004.txt In this document, we propose an extension to the BGP route selection rules that would avoid unnecessary best path transitions between external paths under certain conditions. The proposed extension would help the overall network stability, and more importantly, would eliminate certain BGP route oscillations in which more than one external path from one BGP speaker contributes to the churn. [STANDARDS TRACK] This document is a product of the Inter-Domain Routing 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 Sep 14 17:24:12 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 14 Sep 2007 17:24:12 -0700 (PDT) Subject: [rfc-dist] RFC 5008 on Suite B in Secure/Multipurpose Internet Mail Extensions (S/MIME) Message-ID: <20070915002412.E0719E2D6D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5008 Title: Suite B in Secure/Multipurpose Internet Mail Extensions (S/MIME) Author: R. Housley, J. Solinas Status: Informational Date: September 2007 Mailbox: housley at vigilsec.com, jasolin at orion.ncsc.mil Pages: 15 Characters: 32869 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-housley-smime-suite-b-02.txt URL: http://www.rfc-editor.org/rfc/rfc5008.txt This document specifies the conventions for using the United States National Security Agency's Suite B algorithms in Secure/Multipurpose Internet Mail Extensions (S/MIME) as specified in RFC 3851. 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 Fri Sep 14 17:24:05 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 14 Sep 2007 17:24:05 -0700 (PDT) Subject: [rfc-dist] RFC 5007 on DHCPv6 Leasequery Message-ID: <20070915002405.720E2E2D6B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5007 Title: DHCPv6 Leasequery Author: J. Brzozowski, K. Kinnear, B. Volz, S. Zeng Status: Standards Track Date: September 2007 Mailbox: john_brzozowski at cable.comcast.com, kkinnear at cisco.com, volz at cisco.com, szeng at cisco.com Pages: 23 Characters: 47186 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-dhcpv6-leasequery-01.txt URL: http://www.rfc-editor.org/rfc/rfc5007.txt This document specifies a leasequery exchange for the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) that can be used to obtain lease information about DHCPv6 clients from a DHCPv6 server. This document specifies the scope of data that can be retrieved as well as both DHCPv6 leasequery requestor and server behavior. This document extends DHCPv6. [STANDARDS TRACK] This document is a product of the Dynamic Host Configuration 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 Sep 14 17:24:26 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 14 Sep 2007 17:24:26 -0700 (PDT) Subject: [rfc-dist] RFC 5017 on MIB Textual Conventions for Uniform Resource Identifiers (URIs) Message-ID: <20070915002426.C4FC8E2D6F@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5017 Title: MIB Textual Conventions for Uniform Resource Identifiers (URIs) Author: D. McWalter, Ed. Status: Standards Track Date: September 2007 Mailbox: dmcw at dataconnection.com Pages: 7 Characters: 14826 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-mcwalter-uri-mib-04.txt URL: http://www.rfc-editor.org/rfc/rfc5017.txt This MIB module defines textual conventions to represent STD 66 Uniform Resource Identifiers (URIs). The intent is that these textual conventions will be imported and used in MIB modules that would otherwise define their own representation(s). [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 Sep 20 08:53:46 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 20 Sep 2007 08:53:46 -0700 (PDT) Subject: [rfc-dist] RFC 4994 on DHCPv6 Relay Agent Echo Request Option Message-ID: <20070920155346.EE461E35C7@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4994 Title: DHCPv6 Relay Agent Echo Request Option Author: S. Zeng, B. Volz, K. Kinnear, J. Brzozowski Status: Standards Track Date: September 2007 Mailbox: szeng at cisco.com, volz at cisco.com, kkinnear at cisco.com, john_brzozowski at cable.comcast.com Pages: 6 Characters: 10978 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-dhcpv6-ero-01.txt URL: http://www.rfc-editor.org/rfc/rfc4994.txt This memo defines a Relay Agent Echo Request option for the Dynamic Host Configuration Protocol for IPv6 (DHCPv6). The option allows a DHCPv6 relay agent to request a list of relay agent options that the server echoes back to the relay agent. [STANDARDS TRACK] This document is a product of the Dynamic Host Configuration 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 Sep 20 08:54:03 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 20 Sep 2007 08:54:03 -0700 (PDT) Subject: [rfc-dist] RFC 5014 on IPv6 Socket API for Source Address Selection Message-ID: <20070920155403.445AFE35C9@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5014 Title: IPv6 Socket API for Source Address Selection Author: E. Nordmark, S. Chakrabarti, J. Laganier Status: Informational Date: September 2007 Mailbox: Erik.Nordmark at Sun.com, samitac2 at gmail.com, julien.IETF at laposte.net Pages: 24 Characters: 53601 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-chakrabarti-ipv6-addrselect-api-07.txt URL: http://www.rfc-editor.org/rfc/rfc5014.txt The IPv6 default address selection document (RFC 3484) describes the rules for selecting source and destination IPv6 addresses, and indicates that applications should be able to reverse the sense of some of the address selection rules through some unspecified API. However, no such socket API exists in the basic (RFC 3493) or advanced (RFC 3542) IPv6 socket API documents. This document fills that gap partially by specifying new socket-level options for source address selection and flags for the getaddrinfo() API to specify address selection based on the source address preference in accordance with the socket-level options that modify the default source address selection algorithm. The socket API described in this document will be particularly useful for IPv6 applications that want to choose between temporary and public addresses, and for Mobile IPv6 aware applications that want to use the care-of address for communication. It also specifies socket options and flags for selecting Cryptographically Generated Address (CGA) or non-CGA source addresses. 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 Thu Sep 20 08:54:14 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 20 Sep 2007 08:54:14 -0700 (PDT) Subject: [rfc-dist] RFC 5029 on Definition of an IS-IS Link Attribute Sub-TLV Message-ID: <20070920155414.84284E35CB@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5029 Title: Definition of an IS-IS Link Attribute Sub-TLV Author: JP. Vasseur, S. Previdi Status: Standards Track Date: September 2007 Mailbox: jpv at cisco.com, sprevidi at cisco.com Pages: 6 Characters: 9887 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-link-attr-03.txt URL: http://www.rfc-editor.org/rfc/rfc5029.txt This document defines a sub-TLV called "Link-attributes" carried within the TLV 22 and used to flood some link characteristics. [STANDARDS TRACK] This document is a product of the IS-IS for IP Internets 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 Sep 21 15:21:03 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Sep 2007 15:21:03 -0700 (PDT) Subject: [rfc-dist] RFC 4959 on IMAP Extension for Simple Authentication and Security Layer (SASL) Initial Client Response Message-ID: <20070921222103.F334EE3E83@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4959 Title: IMAP Extension for Simple Authentication and Security Layer (SASL) Initial Client Response Author: R. Siemborski, A. Gulbrandsen Status: Standards Track Date: September 2007 Mailbox: robsiemb at google.com, arnt at oryx.com Pages: 7 Characters: 12284 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-siemborski-imap-sasl-initial-response-06.txt URL: http://www.rfc-editor.org/rfc/rfc4959.txt To date, the Internet Message Access Protocol (IMAP) has used a Simple Authentication and Security Layer (SASL) profile which always required at least one complete round trip for an authentication, as it did not support an initial client response argument. This additional round trip at the beginning of the session is undesirable, especially when round-trip costs are high. This document defines an extension to IMAP which allows clients and servers to avoid this round trip by allowing an initial client response argument to the IMAP AUTHENTICATE command. [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 Sep 21 15:21:15 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Sep 2007 15:21:15 -0700 (PDT) Subject: [rfc-dist] RFC 4965 on CableLabs - IETF Standardization Collaboration Message-ID: <20070921222115.D2D6DE3E85@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4965 Title: CableLabs - IETF Standardization Collaboration Author: J-F. Mule, W. Townsley Status: Informational Date: September 2007 Mailbox: jf.mule at cablelabs.com, mark at townsley.net Pages: 10 Characters: 20885 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-mule-ietf-cablelabs-collaboration-03.txt URL: http://www.rfc-editor.org/rfc/rfc4965.txt This document describes the collaboration and liaison relationship between the Internet Engineering Task Force (IETF) and the Cable Television Laboratories, Inc. (CableLabs). 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 Fri Sep 21 15:21:56 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Sep 2007 15:21:56 -0700 (PDT) Subject: [rfc-dist] RFC 5061 on Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration Message-ID: <20070921222156.1D797E3E87@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5061 Title: Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration Author: R. Stewart, Q. Xie, M. Tuexen, S. Maruyama, M. Kozuka Status: Standards Track Date: September 2007 Mailbox: rrs at cisco.com, Qiaobing.Xie at motorola.com, tuexen at fh-muenster.de, mail at marushin.gr.jp, ma-kun at kozuka.jp Pages: 41 Characters: 91851 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tsvwg-addip-sctp-22.txt URL: http://www.rfc-editor.org/rfc/rfc5061.txt A local host may have multiple points of attachment to the Internet, giving it a degree of fault tolerance from hardware failures. Stream Control Transmission Protocol (SCTP) (RFC 4960) was developed to take full advantage of such a multi-homed host to provide a fast failover and association survivability in the face of such hardware failures. This document describes an extension to SCTP that will allow an SCTP stack to dynamically add an IP address to an SCTP association, dynamically delete an IP address from an SCTP association, and to request to set the primary address the peer will use when sending to an endpoint. [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 Sep 21 15:22:05 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Sep 2007 15:22:05 -0700 (PDT) Subject: [rfc-dist] RFC 5062 on Security Attacks Found Against the Stream Control Transmission Protocol (SCTP) and Current Countermeasures Message-ID: <20070921222205.6ABFFE3E89@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5062 Title: Security Attacks Found Against the Stream Control Transmission Protocol (SCTP) and Current Countermeasures Author: R. Stewart, M. Tuexen, G. Camarillo Status: Informational Date: September 2007 Mailbox: rrs at cisco.com, tuexen at fh-muenster.de, Gonzalo.Camarillo at ericsson.com Pages: 14 Characters: 29704 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tsvwg-sctpthreat-05.txt URL: http://www.rfc-editor.org/rfc/rfc5062.txt This document describes certain security threats to SCTP. It also describes ways to mitigate these threats, in particular by using techniques from the SCTP Specification Errata and Issues memo (RFC 4460). These techniques are included in RFC 4960, which obsoletes RFC 2960. It is hoped that this information will provide some useful background information for many of the newest requirements spelled out in the SCTP Specification Errata and Issues and included in RFC 4960. This memo provides information for the Internet community. This document is a product of the Transport Area Working Group 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 Sep 21 15:22:17 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Sep 2007 15:22:17 -0700 (PDT) Subject: [rfc-dist] RFC 4960 on Stream Control Transmission Protocol Message-ID: <20070921222217.9D44CE3E8B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4960 Title: Stream Control Transmission Protocol Author: R. Stewart, Ed. Status: Standards Track Date: September 2007 Mailbox: rrs at cisco.com Pages: 152 Characters: 346022 Obsoletes: RFC2960, RFC3309 See-Also: I-D Tag: draft-ietf-tsvwg-2960bis-05.txt URL: http://www.rfc-editor.org/rfc/rfc4960.txt This document obsoletes RFC 2960 and RFC 3309. It describes the Stream Control Transmission Protocol (SCTP). SCTP is designed to transport Public Switched Telephone Network (PSTN) signaling messages over IP networks, but is capable of broader applications. SCTP is a reliable transport protocol operating on top of a connectionless packet network such as IP. It offers the following services to its users: -- acknowledged error-free non-duplicated transfer of user data, -- data fragmentation to conform to discovered path MTU size, -- sequenced delivery of user messages within multiple streams, with an option for order-of-arrival delivery of individual user messages, -- optional bundling of multiple user messages into a single SCTP packet, and -- network-level fault tolerance through supporting of multi-homing at either or both ends of an association. The design of SCTP includes appropriate congestion avoidance behavior and resistance to flooding and masquerade attacks. [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 Mon Sep 24 15:32:35 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 24 Sep 2007 15:32:35 -0700 (PDT) Subject: [rfc-dist] RFC 5006 on IPv6 Router Advertisement Option for DNS Configuration Message-ID: <20070924223235.2FBE6E43C9@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5006 Title: IPv6 Router Advertisement Option for DNS Configuration Author: J. Jeong, Ed., S. Park, L. Beloeil, S. Madanapalli Status: Experimental Date: September 2007 Mailbox: jjeong at cs.umn.edu, soohong.park at samsung.com, luc.beloeil at orange-ftgroup.com, smadanapalli at gmail.com Pages: 12 Characters: 26136 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-jeong-dnsop-ipv6-dns-discovery-12.txt URL: http://www.rfc-editor.org/rfc/rfc5006.txt This document specifies a new IPv6 Router Advertisement option to allow IPv6 routers to advertise DNS recursive server addresses to IPv6 hosts. 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 Sep 24 15:33:36 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 24 Sep 2007 15:33:36 -0700 (PDT) Subject: [rfc-dist] RFC 5018 on Connection Establishment in the Binary Floor Control Protocol (BFCP) Message-ID: <20070924223336.EC525E43D5@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5018 Title: Connection Establishment in the Binary Floor Control Protocol (BFCP) Author: G. Camarillo Status: Standards Track Date: September 2007 Mailbox: Gonzalo.Camarillo at ericsson.com Pages: 9 Characters: 20244 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-xcon-bfcp-connection-05.txt URL: http://www.rfc-editor.org/rfc/rfc5018.txt This document specifies how a Binary Floor Control Protocol (BFCP) client establishes a connection to a BFCP floor control server outside the context of an offer/answer exchange. Client and server authentication are based on Transport Layer Security (TLS). [STANDARDS TRACK] This document is a product of the Centralized Conferencing 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 Sep 24 15:33:17 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 24 Sep 2007 15:33:17 -0700 (PDT) Subject: [rfc-dist] RFC 4942 on IPv6 Transition/Co-existence Security Considerations Message-ID: <20070924223317.9C331E43D1@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4942 Title: IPv6 Transition/Co-existence Security Considerations Author: E. Davies, S. Krishnan, P. Savola Status: Informational Date: September 2007 Mailbox: elwynd at dial.pipex.com, suresh.krishnan at ericsson.com, psavola at funet.fi Pages: 41 Characters: 102878 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-v6ops-security-overview-06.txt URL: http://www.rfc-editor.org/rfc/rfc4942.txt The transition from a pure IPv4 network to a network where IPv4 and IPv6 coexist brings a number of extra security considerations that need to be taken into account when deploying IPv6 and operating the dual-protocol network and the associated transition mechanisms. This document attempts to give an overview of the various issues grouped into three categories: o issues due to the IPv6 protocol itself, o issues due to transition mechanisms, and o issues due to IPv6 deployment. This memo provides information for the Internet community. This document is a product of the IPv6 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 Sep 24 15:32:57 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 24 Sep 2007 15:32:57 -0700 (PDT) Subject: [rfc-dist] RFC 4862 on IPv6 Stateless Address Autoconfiguration Message-ID: <20070924223257.B19C9E43CD@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4862 Title: IPv6 Stateless Address Autoconfiguration Author: S. Thomson, T. Narten, T. Jinmei Status: Standards Track Date: September 2007 Mailbox: sethomso at cisco.com, narten at us.ibm.com, jinmei at isl.rdc.toshiba.co.jp Pages: 30 Characters: 72482 Obsoletes: RFC2462 See-Also: I-D Tag: draft-ietf-ipv6-rfc2462bis-08.txt URL: http://www.rfc-editor.org/rfc/rfc4862.txt This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes generating a link-local address, generating global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure to verify the uniqueness of the addresses on a link. [STANDARDS TRACK] This document is a product of the IP Version 6 Working Group Working Group of the IETF. This is now a Draft 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 Sep 24 15:32:48 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 24 Sep 2007 15:32:48 -0700 (PDT) Subject: [rfc-dist] RFC 4861 on Neighbor Discovery for IP version 6 (IPv6) Message-ID: <20070924223248.A2B17E43CB@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4861 Title: Neighbor Discovery for IP version 6 (IPv6) Author: T. Narten, E. Nordmark, W. Simpson, H. Soliman Status: Standards Track Date: September 2007 Mailbox: narten at us.ibm.com, erik.nordmark at sun.com, william.allen.simpson at gmail.com, hesham at elevatemobile.com Pages: 97 Characters: 235106 Obsoletes: RFC2461 See-Also: I-D Tag: draft-ietf-ipv6-2461bis-11.txt URL: http://www.rfc-editor.org/rfc/rfc4861.txt This document specifies the Neighbor Discovery protocol for IP Version 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link-layer addresses, to find routers, and to maintain reachability information about the paths to active neighbors. [STANDARDS TRACK] This document is a product of the IP Version 6 Working Group Working Group of the IETF. This is now a Draft 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 Sep 24 15:33:59 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 24 Sep 2007 15:33:59 -0700 (PDT) Subject: [rfc-dist] RFC 5019 on The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments Message-ID: <20070924223359.6B004E43DB@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5019 Title: The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments Author: A. Deacon, R. Hurst Status: Standards Track Date: September 2007 Mailbox: alex at verisign.com, rmh at microsoft.com Pages: 22 Characters: 46371 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pkix-lightweight-ocsp-profile-11.txt URL: http://www.rfc-editor.org/rfc/rfc5019.txt This specification defines a profile of the Online Certificate Status Protocol (OCSP) that addresses the scalability issues inherent when using OCSP in large scale (high volume) Public Key Infrastructure (PKI) environments and/or in PKI environments that require a lightweight solution to minimize communication bandwidth and client-side processing. [STANDARDS TRACK] This document is a product of the Public-Key Infrastructure (X.509) 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 Sep 24 15:33:26 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 24 Sep 2007 15:33:26 -0700 (PDT) Subject: [rfc-dist] RFC 4943 on IPv6 Neighbor Discovery On-Link Assumption Considered Harmful Message-ID: <20070924223326.BDACAE43D3@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4943 Title: IPv6 Neighbor Discovery On-Link Assumption Considered Harmful Author: S. Roy, A. Durand, J. Paugh Status: Informational Date: September 2007 Mailbox: sebastien.roy at sun.com, alain_durand at cable.comcast.com, jim.paugh at nominum.com Pages: 8 Characters: 16719 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-v6ops-onlinkassumption-04.txt URL: http://www.rfc-editor.org/rfc/rfc4943.txt This document describes the historical and background information behind the removal of the "on-link assumption" from the conceptual host sending algorithm defined in Neighbor Discovery for IP Version 6 (IPv6). According to the algorithm as originally described, when a host's default router list is empty, the host assumes that all destinations are on-link. This is particularly problematic with IPv6-capable nodes that do not have off-link IPv6 connectivity (e.g., no default router). This document describes how making this assumption causes problems and how these problems outweigh the benefits of this part of the conceptual sending algorithm. This memo provides information for the Internet community. This document is a product of the IPv6 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 Sep 24 15:33:47 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 24 Sep 2007 15:33:47 -0700 (PDT) Subject: [rfc-dist] RFC 5072 on IP Version 6 over PPP Message-ID: <20070924223347.05D93E43D7@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5072 Title: IP Version 6 over PPP Author: S.Varada, Ed., D. Haskins, E. Allen Status: Standards Track Date: September 2007 Mailbox: varada at txc.com Pages: 16 Characters: 33910 Obsoletes: RFC2472 See-Also: I-D Tag: draft-ietf-ipv6-over-ppp-v2-03.txt URL: http://www.rfc-editor.org/rfc/rfc5072.txt The Point-to-Point Protocol (PPP) provides a standard method of encapsulating network-layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the method for sending IPv6 packets over PPP links, the NCP for establishing and configuring the IPv6 over PPP, and the method for forming IPv6 link-local addresses on PPP links. It also specifies the conditions for performing Duplicate Address Detection on IPv6 global unicast addresses configured for PPP links either through stateful or stateless address autoconfiguration. This document obsoletes RFC 2472. [STANDARDS TRACK] This document is a product of the IP Version 6 Working Group Working Group of the IETF. This is now a Draft 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 Sep 24 15:33:09 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 24 Sep 2007 15:33:09 -0700 (PDT) Subject: [rfc-dist] RFC 4941 on Privacy Extensions for Stateless Address Autoconfiguration in IPv6 Message-ID: <20070924223309.B47D1E43CF@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4941 Title: Privacy Extensions for Stateless Address Autoconfiguration in IPv6 Author: T. Narten, R. Draves, S. Krishnan Status: Standards Track Date: September 2007 Mailbox: narten at us.ibm.com, richdr at microsoft.com, suresh.krishnan at ericsson.com Pages: 23 Characters: 56699 Obsoletes: RFC3041 See-Also: I-D Tag: draft-ietf-ipv6-privacy-addrs-v2-05.txt URL: http://www.rfc-editor.org/rfc/rfc4941.txt Nodes use IPv6 stateless address autoconfiguration to generate addresses using a combination of locally available information and information advertised by routers. Addresses are formed by combining network prefixes with an interface identifier. On an interface that contains an embedded IEEE Identifier, the interface identifier is typically derived from it. On other interface types, the interface identifier is generated through other means, for example, via random number generation. This document describes an extension to IPv6 stateless address autoconfiguration for interfaces whose interface identifier is derived from an IEEE identifier. Use of the extension causes nodes to generate global scope addresses from interface identifiers that change over time, even in cases where the interface contains an embedded IEEE identifier. Changing the interface identifier (and the global scope addresses generated from it) over time makes it more difficult for eavesdroppers and other information collectors to identify when different addresses used in different transactions actually correspond to the same node. [STANDARDS TRACK] This document is a product of the IP Version 6 Working Group Working Group of the IETF. This is now a Draft 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 Sep 25 15:32:22 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 25 Sep 2007 15:32:22 -0700 (PDT) Subject: [rfc-dist] RFC 4975 on The Message Session Relay Protocol (MSRP) Message-ID: <20070925223222.43F52E4E75@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4975 Title: The Message Session Relay Protocol (MSRP) Author: B. Campbell, Ed., R. Mahy, Ed., C. Jennings, Ed. Status: Standards Track Date: September 2007 Mailbox: ben at estacado.net, rohan at ekabal.com, fluffy at cisco.com Pages: 63 Characters: 144254 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-simple-message-sessions-19.txt URL: http://www.rfc-editor.org/rfc/rfc4975.txt This document describes the Message Session Relay Protocol, a protocol for transmitting a series of related instant messages in the context of a session. Message sessions are treated like any other media stream when set up via a rendezvous or session creation protocol such as the Session Initiation Protocol. [STANDARDS TRACK] This document is a product of the SIP for Instant Messaging and Presence Leveraging Extensions 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 Sep 25 15:32:43 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 25 Sep 2007 15:32:43 -0700 (PDT) Subject: [rfc-dist] RFC 5009 on Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media Message-ID: <20070925223243.EEAF3E4E79@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5009 Title: Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media Author: R. Ejza Status: Informational Date: September 2007 Mailbox: ejzak at alcatel-lucent.com Pages: 15 Characters: 36092 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ejzak-sipping-p-em-auth-04.txt URL: http://www.rfc-editor.org/rfc/rfc5009.txt This document describes a private Session Initiation Protocol (SIP) header field (P-header) to be used by the European Telecommunications Standards Institute (ETSI) Telecommunications and Internet-converged Services and Protocols for Advanced Networks (TISPAN) for the purpose of authorizing early media flows in Third Generation Partnership Project (3GPP) IP Multimedia Subsystems (IMS). This header field is useful in any SIP network that is interconnected with other SIP networks and needs to control the flow of media in the early dialog state. 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 Tue Sep 25 15:32:57 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 25 Sep 2007 15:32:57 -0700 (PDT) Subject: [rfc-dist] RFC 4944 on Transmission of IPv6 Packets over IEEE 802.15.4 Networks Message-ID: <20070925223257.699F1E4E7B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4944 Title: Transmission of IPv6 Packets over IEEE 802.15.4 Networks Author: G. Montenegro, N. Kushalnagar, J. Hui, D. Culler Status: Standards Track Date: September 2007 Mailbox: gabriel.montenegro at microsoft.com, nandakishore.kushalnagar at intel.com, jhui at archrock.com, dculler at archrock.com Pages: 30 Characters: 67232 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-6lowpan-format-13.txt URL: http://www.rfc-editor.org/rfc/rfc4944.txt This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE 802.15.4 networks. Additional specifications include a simple header compression scheme using shared context and provisions for packet delivery in IEEE 802.15.4 meshes. [STANDARDS TRACK] This document is a product of the IPv6 over Low power WPAN 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 Sep 25 15:32:32 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 25 Sep 2007 15:32:32 -0700 (PDT) Subject: [rfc-dist] RFC 4976 on Relay Extensions for the Message Sessions Relay Protocol (MSRP) Message-ID: <20070925223232.6E19CE4E77@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4976 Title: Relay Extensions for the Message Sessions Relay Protocol (MSRP) Author: C. Jennings, R. Mahy, A. B. Roach Status: Standards Track Date: September 2007 Mailbox: fluffy at cisco.com, rohan at ekabal.com, adam at estacado.net Pages: 36 Characters: 84244 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-simple-msrp-relays-10.txt URL: http://www.rfc-editor.org/rfc/rfc4976.txt Two separate models for conveying instant messages have been defined. Page-mode messages stand alone and are not part of a Session Initiation Protocol (SIP) session, whereas session-mode messages are set up as part of a session using SIP. The Message Session Relay Protocol (MSRP) is a protocol for near real-time, peer-to-peer exchanges of binary content without intermediaries, which is designed to be signaled using a separate rendezvous protocol such as SIP. This document introduces the notion of message relay intermediaries to MSRP and describes the extensions necessary to use them. [STANDARDS TRACK] This document is a product of the SIP for Instant Messaging and Presence Leveraging Extensions 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 Sep 27 15:33:55 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 27 Sep 2007 15:33:55 -0700 (PDT) Subject: [rfc-dist] RFC 4984 on Report from the IAB Workshop on Routing and Addressing Message-ID: <20070927223355.65D26E5262@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4984 Title: Report from the IAB Workshop on Routing and Addressing Author: D. Meyer, Ed., L. Zhang, Ed., K. Fall, Ed. Status: Informational Date: September 2007 Mailbox: dmm at 1-4-5.net, lixia at cs.ucla.edu, kfall at intel.com Pages: 39 Characters: 96153 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-raws-report-02.txt URL: http://www.rfc-editor.org/rfc/rfc4984.txt This document reports the outcome of the Routing and Addressing Workshop that was held by the Internet Architecture Board (IAB) on October 18-19, 2006, in Amsterdam, Netherlands. The primary goal of the workshop was to develop a shared understanding of the problems that the large backbone operators are facing regarding the scalability of today's Internet routing system. The key workshop findings include an analysis of the major factors that are driving routing table growth, constraints in router technology, and the limitations of today's Internet addressing architecture. It is hoped that these findings will serve as input to the IETF community and help identify next steps towards effective solutions. Note that this document is a report on the proceedings of the workshop. The views and positions documented in this report are those of the workshop participants and not of the IAB. Furthermore, note that work on issues related to this workshop report is continuing, and this document does not intend to reflect the increased understanding of issues nor to discuss the range of potential solutions that may be the outcome of this ongoing work. 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 ...