From rfc-editor at rfc-editor.org Thu May 8 16:15:00 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 8 May 2008 16:15:00 -0700 (PDT) Subject: [rfc-dist] RFC 5174 on A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU) Message-ID: <20080508231500.6DB1812973A@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5174 Title: A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU) Author: J-P. Evain Status: Informational Date: May 2008 Mailbox: evain at ebu.ch Pages: 8 Characters: 13732 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-evain-ebu-urn-03.txt URL: http://www.rfc-editor.org/rfc/rfc5174.txt This document describes a Uniform Resource Name (URN) namespace for the European Broadcasting Union (EBU) for naming persistent resources defined within EBU technical documentation and Internet resources. Example resources include technical documents and specifications, eXtensible Markup Language (XML) Schemas, classification schemes, XML Document Type Definitions (DTDs), namespaces, style sheets, media assets, and other types of resources produced or managed by the EBU. 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 May 8 16:15:04 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 8 May 2008 16:15:04 -0700 (PDT) Subject: [rfc-dist] RFC 5185 on OSPF Multi-Area Adjacency Message-ID: <20080508231504.5EF2D12973C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5185 Title: OSPF Multi-Area Adjacency Author: S. Mirtorabi, P. Psenak, A. Lindem, Ed., A. Oswal Status: Standards Track Date: May 2008 Mailbox: sina at nuovasystems.com, ppsenak at cisco.com, acee at redback.com, aoswal at redback.com Pages: 11 Characters: 18698 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ospf-multi-area-adj-09.txt URL: http://www.rfc-editor.org/rfc/rfc5185.txt This document describes an extension to the Open Shortest Path First (OSPF) protocol to allow a single physical link to be shared by multiple areas. This is necessary to allow the link to be considered an intra-area link in multiple areas. This would create an intra- area path in each of the corresponding areas sharing the same link. [STANDARDS TRACK] This document is a product of the Open Shortest Path First IGP Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu May 8 16:15:07 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 8 May 2008 16:15:07 -0700 (PDT) Subject: [rfc-dist] RFC 5280 on Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile Message-ID: <20080508231507.F159812973E@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5280 Title: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile Author: D. Cooper, S. Santesson, S. Farrell, S. Boeyen, R. Housley, W. Polk Status: Standards Track Date: May 2008 Mailbox: david.cooper at nist.gov, stefans at microsoft.com, stephen.farrell at cs.tcd.ie, sharon.boeyen at entrust.com, housley at vigilsec.com, wpolk at nist.gov Pages: 151 Characters: 352580 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pkix-rfc3280bis-11.txt URL: http://www.rfc-editor.org/rfc/rfc5280.txt This memo profiles the X.509 v3 certificate and X.509 v2 certificate revocation list (CRL) for use in the Internet. An overview of this approach and model is provided as an introduction. The X.509 v3 certificate format is described in detail, with additional information regarding the format and semantics of Internet name forms. Standard certificate extensions are described and two Internet-specific extensions are defined. A set of required certificate extensions is specified. The X.509 v2 CRL format is described in detail along with standard and Internet-specific extensions. An algorithm for X.509 certification path validation is described. An ASN.1 module and examples are provided in the appendices. [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 Thu May 8 16:24:58 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 8 May 2008 16:24:58 -0700 (PDT) Subject: [rfc-dist] RFC 5000 on Internet Official Protocol Standards Message-ID: <20080508232458.80A7D129742@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5000 Title: Internet Official Protocol Standards Author: RFC Editor Status: Informational Date: May 2008 Mailbox: rfc-editor at rfc-editor.org Pages: 75 Characters: 222566 Obsoletes: RFC3700 See Also: STD0001 I-D Tag: draft-rfc-5000.txt URL: http://www.rfc-editor.org/rfc/rfc5000.txt This document is published by the RFC Editor to provide a summary of the current standards protocols (as of 18 February 2008). It lists those official protocol standards, Best Current Practice, and Experimental RFCs that have not been obsoleted; it is not a complete index to the RFC series. Newly published RFCs and RFCs whose status has changed are starred. For an up-to-date list, see http://www.rfc-editor.org/rfcxx00.html, which is updated daily. 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 May 9 10:38:33 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 9 May 2008 10:38:33 -0700 (PDT) Subject: [rfc-dist] Corrected Announcement: RFC 5280 on Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile Message-ID: <20080509173833.84147129892@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5280 Title: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile Author: D. Cooper, S. Santesson, S. Farrell, S. Boeyen, R. Housley, W. Polk Status: Standards Track Date: May 2008 Mailbox: david.cooper at nist.gov, stefans at microsoft.com, stephen.farrell at cs.tcd.ie, sharon.boeyen at entrust.com, housley at vigilsec.com, wpolk at nist.gov Pages: 151 Characters: 352580 Obsoletes: RFC3280, RFC4325, RFC4630 I-D Tag: draft-ietf-pkix-rfc3280bis-11.txt URL: http://www.rfc-editor.org/rfc/rfc5280.txt This memo profiles the X.509 v3 certificate and X.509 v2 certificate revocation list (CRL) for use in the Internet. An overview of this approach and model is provided as an introduction. The X.509 v3 certificate format is described in detail, with additional information regarding the format and semantics of Internet name forms. Standard certificate extensions are described and two Internet-specific extensions are defined. A set of required certificate extensions is specified. The X.509 v2 CRL format is described in detail along with standard and Internet-specific extensions. An algorithm for X.509 certification path validation is described. An ASN.1 module and examples are provided in the appendices. [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 Fri May 9 14:28:29 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 9 May 2008 14:28:29 -0700 (PDT) Subject: [rfc-dist] RFC 5181 on IPv6 Deployment Scenarios in 802.16 Networks Message-ID: <20080509212829.045FA129C23@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5181 Title: IPv6 Deployment Scenarios in 802.16 Networks Author: M-K. Shin, Ed., Y-H. Han, S-E. Kim, D. Premec Status: Informational Date: May 2008 Mailbox: myungki.shin at gmail.com, yhhan at kut.ac.kr, sekim at kt.co.kr, domagoj.premec at siemens.com Pages: 16 Characters: 36671 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-v6ops-802-16-deployment-scenarios-07.txt URL: http://www.rfc-editor.org/rfc/rfc5181.txt This document provides a detailed description of IPv6 deployment and integration methods and scenarios in wireless broadband access networks in coexistence with deployed IPv4 services. In this document, we will discuss the main components of IPv6 IEEE 802.16 access networks and their differences from IPv4 IEEE 802.16 networks and how IPv6 is deployed and integrated in each of the IEEE 802.16 technologies. 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 Tue May 13 14:38:46 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 13 May 2008 14:38:46 -0700 (PDT) Subject: [rfc-dist] RFC 5193 on Protocol for Carrying Authentication for Network Access (PANA) Framework Message-ID: <20080513213846.8808512A87F@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5193 Title: Protocol for Carrying Authentication for Network Access (PANA) Framework Author: P. Jayaraman, R. Lopez, Y. Ohba, Ed., M. Parthasarathy, A. Yegin Status: Informational Date: May 2008 Mailbox: prakash_jayaraman at net.com, rafa at um.es, yohba at tari.toshiba.com, mohanp at sbcglobal.net, a.yegin at partner.samsung.com Pages: 11 Characters: 24474 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pana-framework-10.txt URL: http://www.rfc-editor.org/rfc/rfc5193.txt This document defines the general Protocol for Carrying Authentication for Network Access (PANA) framework functional elements, high-level call flow, and deployment environments. This memo provides information for the Internet community. This document is a product of the Protocol for carrying Authentication for Network Access 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 Tue May 13 14:38:39 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 13 May 2008 14:38:39 -0700 (PDT) Subject: [rfc-dist] RFC 5179 on Generic Security Service Application Program Interface (GSS-API) Domain-Based Service Names Mapping for the Kerberos V GSS Mechanism Message-ID: <20080513213839.DE7C912A879@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5179 Title: Generic Security Service Application Program Interface (GSS-API) Domain-Based Service Names Mapping for the Kerberos V GSS Mechanism Author: N. Williams Status: Standards Track Date: May 2008 Mailbox: Nicolas.Williams at sun.com Pages: 5 Characters: 8017 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-kitten-krb5-gssapi-domain-based-names-05.txt URL: http://www.rfc-editor.org/rfc/rfc5179.txt This document describes the mapping of Generic Security Service Application Program Interface (GSS-API) domain-name-based service principal names onto Kerberos V principal names. [STANDARDS TRACK] This document is a product of the Kitten (GSS-API Next Generation) 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 May 13 14:38:44 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 13 May 2008 14:38:44 -0700 (PDT) Subject: [rfc-dist] RFC 5192 on DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication Agents Message-ID: <20080513213844.9BF2612A87D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5192 Title: DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication Agents Author: L. Morand, A. Yegin, S. Kumar, S. Madanapalli Status: Standards Track Date: May 2008 Mailbox: lionel.morand at orange-ftgroup.com, a.yegin at partner.samsung.com, surajk at techmahindra.com, syam at samsung.com Pages: 8 Characters: 14986 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-paa-option-05.txt URL: http://www.rfc-editor.org/rfc/rfc5192.txt This document defines new DHCPv4 and DHCPv6 options that contain a list of IP addresses to locate one or more PANA (Protocol for carrying Authentication for Network Access) Authentication Agents (PAAs). This is one of the methods that a PANA Client (PaC) can use to locate PAAs. [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 Tue May 13 14:38:42 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 13 May 2008 14:38:42 -0700 (PDT) Subject: [rfc-dist] RFC 5191 on Protocol for Carrying Authentication for Network Access (PANA) Message-ID: <20080513213842.3A73812A87B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5191 Title: Protocol for Carrying Authentication for Network Access (PANA) Author: D. Forsberg, Y. Ohba, Ed., B. Patil, H. Tschofenig, A. Yegin Status: Standards Track Date: May 2008 Mailbox: dan.forsberg at nokia.com, yohba at tari.toshiba.com, basavaraj.patil at nsn.com, hannes.tschofenig at nsn.com, a.yegin at partner.samsung.com Pages: 46 Characters: 96716 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pana-pana-18.txt URL: http://www.rfc-editor.org/rfc/rfc5191.txt This document defines the Protocol for Carrying Authentication for Network Access (PANA), a network-layer transport for Extensible Authentication Protocol (EAP) to enable network access authentication between clients and access networks. In EAP terms, PANA is a UDP-based EAP lower layer that runs between the EAP peer and the EAP authenticator. [STANDARDS TRACK] This document is a product of the Protocol for carrying Authentication for Network Access 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 May 13 14:38:35 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 13 May 2008 14:38:35 -0700 (PDT) Subject: [rfc-dist] RFC 5178 on Generic Security Service Application Program Interface (GSS-API) Internationalization and Domain-Based Service Names and Name Type Message-ID: <20080513213835.984B912A875@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5178 Title: Generic Security Service Application Program Interface (GSS-API) Internationalization and Domain-Based Service Names and Name Type Author: N. Williams, A. Melnikov Status: Standards Track Date: May 2008 Mailbox: Nicolas.Williams at sun.com, Alexey.Melnikov at isode.com Pages: 9 Characters: 17262 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-kitten-gssapi-domain-based-names-06.txt URL: http://www.rfc-editor.org/rfc/rfc5178.txt This document describes domain-name-based service principal names and the corresponding name type for the Generic Security Service Application Programming Interface (GSS-API). Internationalization of the GSS-API is also covered. Domain-based service names are similar to host-based service names, but using a domain name (not necessarily an Internet domain name) in addition to a hostname. The primary purpose of domain-based names is to provide a measure of protection to applications that utilize insecure service discovery protocols. This is achieved by providing a way to name clustered services after the "domain" which they service, thereby allowing their clients to authorize the service's servers based on authentication of their service names. [STANDARDS TRACK] This document is a product of the Kitten (GSS-API Next Generation) 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 May 19 16:36:15 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 19 May 2008 16:36:15 -0700 (PDT) Subject: [rfc-dist] RFC 5180 on IPv6 Benchmarking Methodology for Network Interconnect Devices Message-ID: <20080519233615.75A4112BB55@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5180 Title: IPv6 Benchmarking Methodology for Network Interconnect Devices Author: C. Popoviciu, A. Hamza, G. Van de Velde, D. Dugatkin Status: Informational Date: May 2008 Mailbox: cpopovic at cisco.com, ahamza at cisco.com, gunter at cisco.com, diego at fastsoft.com Pages: 20 Characters: 41712 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-bmwg-ipv6-meth-05.txt URL: http://www.rfc-editor.org/rfc/rfc5180.txt The benchmarking methodologies defined in RFC 2544 are IP version independent. However, RFC 2544 does not address some of the specificities of IPv6. This document provides additional benchmarking guidelines, which in conjunction with RFC 2544, lead to a more complete and realistic evaluation of the IPv6 performance of network interconnect devices. IPv6 transition mechanisms are outside the scope of this document. This memo provides information for the Internet community. This document is a product of the Benchmarking Methodology 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 May 19 16:36:17 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 19 May 2008 16:36:17 -0700 (PDT) Subject: [rfc-dist] BCP 26, RFC 5226 on Guidelines for Writing an IANA Considerations Section in RFCs Message-ID: <20080519233617.6E7A112BB57@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. BCP 26 RFC 5226 Title: Guidelines for Writing an IANA Considerations Section in RFCs Author: T. Narten, H. Alvestrand Status: Best Current Practice Date: May 2008 Mailbox: narten at us.ibm.com, Harald at Alvestrand.no Pages: 27 Characters: 66160 Obsoletes: RFC2434 See Also: BCP0026 I-D Tag: draft-narten-iana-considerations-rfc2434bis-09.txt URL: http://www.rfc-editor.org/rfc/rfc5226.txt Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA). In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA. This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu May 29 16:30:54 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 29 May 2008 16:30:54 -0700 (PDT) Subject: [rfc-dist] RFC 5183 on Sieve Email Filtering: Environment Extension Message-ID: <20080529233054.3E0A212D82C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5183 Title: Sieve Email Filtering: Environment Extension Author: N. Freed Status: Standards Track Date: May 2008 Mailbox: ned.freed at mrochek.com Pages: 10 Characters: 16950 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-freed-sieve-environment-05.txt URL: http://www.rfc-editor.org/rfc/rfc5183.txt This document describes the "environment" extension to the Sieve email filtering language. The "environment" extension gives a Sieve script access to information about the Sieve interpreter itself, where it is running, and about any transport connection currently involved in transferring the message. [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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu May 29 16:31:00 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 29 May 2008 16:31:00 -0700 (PDT) Subject: [rfc-dist] RFC 5208 on Public-Key Cryptography Standards (PKCS) #8: Private-Key Information Syntax Specification Version 1.2 Message-ID: <20080529233100.09E7A12D830@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5208 Title: Public-Key Cryptography Standards (PKCS) #8: Private-Key Information Syntax Specification Version 1.2 Author: B. Kaliski Status: Informational Date: May 2008 Mailbox: kaliski_burt at emc.com Pages: 8 Characters: 12063 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-kaliski-pkcs8-00.txt URL: http://www.rfc-editor.org/rfc/rfc5208.txt This document represents a republication of PKCS #8 v1.2 from RSA Laboratories' Public Key Cryptography Standard (PKCS) series. Change control is transferred to the IETF. The body of this document, except for the security considerations section, is taken directly from the PKCS #8 v1.2 specification. This document describes a syntax for private-key information. 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu May 29 16:31:03 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 29 May 2008 16:31:03 -0700 (PDT) Subject: [rfc-dist] RFC 5238 on Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP) Message-ID: <20080529233103.4465612D834@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5238 Title: Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP) Author: T. Phelan Status: Standards Track Date: May 2008 Mailbox: tphelan at sonusnet.com Pages: 10 Characters: 24394 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dccp-dtls-06.txt URL: http://www.rfc-editor.org/rfc/rfc5238.txt This document specifies the use of Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP). DTLS provides communications privacy for applications that use datagram transport protocols and allows client/server applications to communicate in a way that is designed to prevent eavesdropping and detect tampering or message forgery. DCCP is a transport protocol that provides a congestion-controlled unreliable datagram service. [STANDARDS TRACK] This document is a product of the Datagram Congestion Control Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu May 29 16:30:58 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 29 May 2008 16:30:58 -0700 (PDT) Subject: [rfc-dist] RFC 5184 on Unified Layer 2 (L2) Abstractions for Layer 3 (L3)-Driven Fast Handover Message-ID: <20080529233058.2EA7812D82E@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5184 Title: Unified Layer 2 (L2) Abstractions for Layer 3 (L3)-Driven Fast Handover Author: F. Teraoka, K. Gogo, K. Mitsuya, R. Shibui, K. Mitani Status: Experimental Date: May 2008 Mailbox: tera at ics.keio.ac.jp, gogo at tera.ics.keio.ac.jp, mitsuya at sfc.wide.ad.jp, shibrie at tera.ics.keio.ac.jp, koki at tera.ics.keio.ac.jp, rajeev_koodli at yahoo.com Pages: 29 Characters: 64137 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-mobopts-l2-abstractions-07.txt URL: http://www.rfc-editor.org/rfc/rfc5184.txt This document proposes unified Layer 2 (L2) abstractions for Layer 3 (L3)-driven fast handovers. For efficient network communication, it is vital for a protocol layer to know or utilize other layers' information, such as the form of L2 triggers. However, each protocol layer is basically designed independently. Since each protocol layer is also implemented independently in current operating systems, it is very hard to exchange control information between protocol layers. This document defines nine kinds of L2 abstractions in the form of "primitives" to achieve fast handovers in the network layer as a means of solving the problem. This mechanism is called "L3-driven fast handovers" because the network layer initiates L2 and L3 handovers by using the primitives. This document is a product of the IP Mobility Optimizations (MobOpts) Research Group. This memo defines an Experimental Protocol for the Internet community. This document is a product of the IRTF Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu May 29 16:31:01 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 29 May 2008 16:31:01 -0700 (PDT) Subject: [rfc-dist] RFC 5243 on OSPF Database Exchange Summary List Optimization Message-ID: <20080529233101.774D412D832@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5243 Title: OSPF Database Exchange Summary List Optimization Author: R. Ogier Status: Informational Date: May 2008 Mailbox: rich.ogier at earthlink.net Pages: 5 Characters: 11029 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ogier-ospf-dbex-opt-03.txt URL: http://www.rfc-editor.org/rfc/rfc5243.txt This document describes a backward-compatible optimization for the Database Exchange process in OSPFv2 and OSPFv3. In this optimization, a router does not list a Link State Advertisement (LSA) in Database Description packets sent to a neighbor, if the same or a more recent instance of the LSA was listed in a Database Description packet already received from the neighbor. This optimization reduces Database Description overhead by about 50% in large networks. This optimization does not affect synchronization, since it only omits unnecessary information from Database Description packets. 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Fri May 30 10:40:17 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 30 May 2008 10:40:17 -0700 (PDT) Subject: [rfc-dist] RFC 5186 on Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction Message-ID: <20080530174017.0883E134654@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5186 Title: Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction Author: B. Haberman, J. Martin Status: Informational Date: UNKNOWN Mailbox: brian at innovationslab.net, jim at wovensystems.com Pages: 6 Characters: 12403 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-magma-igmpv3-and-routing-05.txt URL: http://www.rfc-editor.org/rfc/rfc5186.txt The definitions of the Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) require new behavior within the multicast routing protocols. The additional source information contained in IGMPv3 and MLDv2 messages necessitates that multicast routing protocols manage and utilize the information. This document describes how multicast routing protocols will interact with these source-filtering group management protocols. This memo provides information for the Internet community. This document is a product of the Multicast & Anycast Group Membership 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Fri May 30 14:06:57 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 30 May 2008 14:06:57 -0700 (PDT) Subject: [rfc-dist] Correction: RFC 5186 on Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction Message-ID: <20080530210657.C28E11346E9@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5186 Title: Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction Author: B. Haberman, J. Martin Status: Informational Date: MAY 2008 Mailbox: brian at innovationslab.net, jim at wovensystems.com Pages: 6 Characters: 12403 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-magma-igmpv3-and-routing-05.txt URL: http://www.rfc-editor.org/rfc/rfc5186.txt The definitions of the Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) require new behavior within the multicast routing protocols. The additional source information contained in IGMPv3 and MLDv2 messages necessitates that multicast routing protocols manage and utilize the information. This document describes how multicast routing protocols will interact with these source-filtering group management protocols. This memo provides information for the Internet community. This document is a product of the Multicast & Anycast Group Membership 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu May 29 16:30:58 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 29 May 2008 16:30:58 -0700 (PDT) Subject: [rfc-dist] RFC 5184 on Unified Layer 2 (L2) Abstractions for Layer 3 (L3)-Driven Fast Handover Message-ID: <20080529233058.2EA7812D82E@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5184 Title: Unified Layer 2 (L2) Abstractions for Layer 3 (L3)-Driven Fast Handover Author: F. Teraoka, K. Gogo, K. Mitsuya, R. Shibui, K. Mitani Status: Experimental Date: May 2008 Mailbox: tera at ics.keio.ac.jp, gogo at tera.ics.keio.ac.jp, mitsuya at sfc.wide.ad.jp, shibrie at tera.ics.keio.ac.jp, koki at tera.ics.keio.ac.jp, rajeev_koodli at yahoo.com Pages: 29 Characters: 64137 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-mobopts-l2-abstractions-07.txt URL: http://www.rfc-editor.org/rfc/rfc5184.txt This document proposes unified Layer 2 (L2) abstractions for Layer 3 (L3)-driven fast handovers. For efficient network communication, it is vital for a protocol layer to know or utilize other layers' information, such as the form of L2 triggers. However, each protocol layer is basically designed independently. Since each protocol layer is also implemented independently in current operating systems, it is very hard to exchange control information between protocol layers. This document defines nine kinds of L2 abstractions in the form of "primitives" to achieve fast handovers in the network layer as a means of solving the problem. This mechanism is called "L3-driven fast handovers" because the network layer initiates L2 and L3 handovers by using the primitives. This document is a product of the IP Mobility Optimizations (MobOpts) Research Group. This memo defines an Experimental Protocol for the Internet community. This document is a product of the IRTF Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute _______________________________________________ IETF-Announce mailing list IETF-Announce at ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From rfc-editor at rfc-editor.org Thu May 29 16:31:00 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 29 May 2008 16:31:00 -0700 (PDT) Subject: [rfc-dist] RFC 5208 on Public-Key Cryptography Standards (PKCS) #8: Private-Key Information Syntax Specification Version 1.2 Message-ID: <20080529233100.09E7A12D830@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5208 Title: Public-Key Cryptography Standards (PKCS) #8: Private-Key Information Syntax Specification Version 1.2 Author: B. Kaliski Status: Informational Date: May 2008 Mailbox: kaliski_burt at emc.com Pages: 8 Characters: 12063 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-kaliski-pkcs8-00.txt URL: http://www.rfc-editor.org/rfc/rfc5208.txt This document represents a republication of PKCS #8 v1.2 from RSA Laboratories' Public Key Cryptography Standard (PKCS) series. Change control is transferred to the IETF. The body of this document, except for the security considerations section, is taken directly from the PKCS #8 v1.2 specification. This document describes a syntax for private-key information. 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute _______________________________________________ IETF-Announce mailing list IETF-Announce at ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From rfc-editor at rfc-editor.org Thu May 29 16:30:54 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 29 May 2008 16:30:54 -0700 (PDT) Subject: [rfc-dist] RFC 5183 on Sieve Email Filtering: Environment Extension Message-ID: <20080529233054.3E0A212D82C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5183 Title: Sieve Email Filtering: Environment Extension Author: N. Freed Status: Standards Track Date: May 2008 Mailbox: ned.freed at mrochek.com Pages: 10 Characters: 16950 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-freed-sieve-environment-05.txt URL: http://www.rfc-editor.org/rfc/rfc5183.txt This document describes the "environment" extension to the Sieve email filtering language. The "environment" extension gives a Sieve script access to information about the Sieve interpreter itself, where it is running, and about any transport connection currently involved in transferring the message. [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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute _______________________________________________ IETF-Announce mailing list IETF-Announce at ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From rfc-editor at rfc-editor.org Thu May 29 16:31:01 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 29 May 2008 16:31:01 -0700 (PDT) Subject: [rfc-dist] RFC 5243 on OSPF Database Exchange Summary List Optimization Message-ID: <20080529233101.774D412D832@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5243 Title: OSPF Database Exchange Summary List Optimization Author: R. Ogier Status: Informational Date: May 2008 Mailbox: rich.ogier at earthlink.net Pages: 5 Characters: 11029 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ogier-ospf-dbex-opt-03.txt URL: http://www.rfc-editor.org/rfc/rfc5243.txt This document describes a backward-compatible optimization for the Database Exchange process in OSPFv2 and OSPFv3. In this optimization, a router does not list a Link State Advertisement (LSA) in Database Description packets sent to a neighbor, if the same or a more recent instance of the LSA was listed in a Database Description packet already received from the neighbor. This optimization reduces Database Description overhead by about 50% in large networks. This optimization does not affect synchronization, since it only omits unnecessary information from Database Description packets. 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute _______________________________________________ IETF-Announce mailing list IETF-Announce at ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From rfc-editor at rfc-editor.org Thu May 29 16:31:03 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 29 May 2008 16:31:03 -0700 (PDT) Subject: [rfc-dist] RFC 5238 on Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP) Message-ID: <20080529233103.4465612D834@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5238 Title: Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP) Author: T. Phelan Status: Standards Track Date: May 2008 Mailbox: tphelan at sonusnet.com Pages: 10 Characters: 24394 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dccp-dtls-06.txt URL: http://www.rfc-editor.org/rfc/rfc5238.txt This document specifies the use of Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP). DTLS provides communications privacy for applications that use datagram transport protocols and allows client/server applications to communicate in a way that is designed to prevent eavesdropping and detect tampering or message forgery. DCCP is a transport protocol that provides a congestion-controlled unreliable datagram service. [STANDARDS TRACK] This document is a product of the Datagram Congestion Control Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute _______________________________________________ IETF-Announce mailing list IETF-Announce at ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From rfc-editor at rfc-editor.org Fri May 30 10:40:17 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 30 May 2008 10:40:17 -0700 (PDT) Subject: [rfc-dist] RFC 5186 on Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction Message-ID: <20080530174017.0883E134654@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5186 Title: Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction Author: B. Haberman, J. Martin Status: Informational Date: UNKNOWN Mailbox: brian at innovationslab.net, jim at wovensystems.com Pages: 6 Characters: 12403 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-magma-igmpv3-and-routing-05.txt URL: http://www.rfc-editor.org/rfc/rfc5186.txt The definitions of the Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) require new behavior within the multicast routing protocols. The additional source information contained in IGMPv3 and MLDv2 messages necessitates that multicast routing protocols manage and utilize the information. This document describes how multicast routing protocols will interact with these source-filtering group management protocols. This memo provides information for the Internet community. This document is a product of the Multicast & Anycast Group Membership 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute _______________________________________________ IETF-Announce mailing list IETF-Announce at ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce