From rfc-editor at rfc-editor.org  Fri May  4 15:59:21 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 4 May 2007 15:59:21 -0700
Subject: [rfc-dist] RFC 4868 on Using HMAC-SHA-256, HMAC-SHA-384,
	and HMAC-SHA-512 with IPsec
Message-ID: <200705042259.l44MxL6a016662@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4868

        Title:      Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 
                    with IPsec 
        Author:     S. Kelly, S. Frankel
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    scott at hyperthought.com, 
                    sheila.frankel at nist.gov
        Pages:      21
        Characters: 41432
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-kelly-ipsec-ciph-sha2-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4868.txt

This specification describes the use of Hashed Message Authentication
Mode (HMAC) in conjunction with the SHA-256, SHA-384, and SHA-512
algorithms in IPsec.  These algorithms may be used as the basis for
data origin authentication and integrity verification mechanisms for
the Authentication Header (AH), Encapsulating Security Payload (ESP),
Internet Key Exchange Protocol (IKE), and IKEv2 protocols, and also
as Pseudo-Random Functions (PRFs) for IKE and IKEv2.  Truncated
output lengths are specified for the authentication-related variants,
with the corresponding algorithms designated as HMAC-SHA-256-128,
HMAC-SHA-384-192, and HMAC-SHA-512-256.  The PRF variants are not
truncated, and are called PRF-HMAC-SHA-256, PRF-HMAC-SHA-384, and
PRF-HMAC-SHA-512.  [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 May  4 15:59:37 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 4 May 2007 15:59:37 -0700
Subject: [rfc-dist] RFC 4860 on Generic Aggregate Resource ReSerVation
	Protocol (RSVP) Reservations
Message-ID: <200705042259.l44MxbtC016687@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4860

        Title:      Generic Aggregate Resource ReSerVation Protocol 
                    (RSVP) Reservations 
        Author:     F. Le Faucheur, B. Davie,
                    P. Bose, C. Christou,
                    M. Davenport
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    flefauch at cisco.com, 
                    bds at cisco.com, 
                    pratik.bose at lmco.com,  christou_chris at bah.com, 
                    davenport_michael at bah.com
        Pages:      32
        Characters: 73010
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-rsvp-ipsec-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4860.txt

RFC 3175 defines aggregate Resource ReSerVation Protocol (RSVP)
reservations allowing resources to be reserved in a Diffserv network
for a given Per Hop Behavior (PHB), or given set of PHBs, from a
given source to a given destination.  RFC 3175 also defines how
end-to-end RSVP reservations can be aggregated onto such aggregate
reservations when transiting through a Diffserv cloud.  There are
situations where multiple such aggregate reservations are needed for
the same source IP address, destination IP address, and PHB (or set of
PHBs).  However, this is not supported by the aggregate reservations
defined in RFC 3175.  In order to support this, the present document
defines a more flexible type of aggregate RSVP reservations, referred
to as generic aggregate reservation.  Multiple such generic aggregate
reservations can be established for a given PHB (or set of PHBs) from
a given source IP address to a given destination IP address.  The
generic aggregate reservations may be used to aggregate end-to-end
RSVP reservations.  This document also defines the procedures for such
aggregation.  The generic aggregate reservations may also be used
end-to-end directly by end-systems attached to a Diffserv network.  
[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 May  4 16:00:01 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 4 May 2007 16:00:01 -0700
Subject: [rfc-dist] RFC 4869 on Suite B Cryptographic Suites for IPsec
Message-ID: <200705042300.l44N018e016734@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4869

        Title:      Suite B Cryptographic Suites for 
                    IPsec 
        Author:     L. Law, J. Solinas
        Status:     Informational
        Date:       May 2007
        Mailbox:    lelaw at orion.ncsc.mil, 
                    jasolin at orion.ncsc.mil
        Pages:      9
        Characters: 17043
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-solinas-ui-suites-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4869.txt

This document proposes four optional cryptographic user interface
suites ("UI suites") for IPsec, similar to the two suites specified
in RFC 4308.  The four new suites provide compatibility with the
United States National Security Agency's Suite B specifications.  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  4 15:59:47 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 4 May 2007 15:59:47 -0700
Subject: [rfc-dist] RFC 4851 on The Flexible Authentication via Secure
	Tunneling Extensible Authentication Protocol Method (EAP-FAST)
Message-ID: <200705042259.l44MxlfH016706@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4851

        Title:      The Flexible Authentication via Secure 
                    Tunneling Extensible Authentication Protocol Method 
                    (EAP-FAST) 
        Author:     N. Cam-Winget, D. McGrew,
                    J. Salowey, H. Zhou
        Status:     Informational
        Date:       May 2007
        Mailbox:    ncamwing at cisco.com, 
                    mcgrew at cisco.com, 
                    jsalowey at cisco.com,  hzhou at cisco.com
        Pages:      64
        Characters: 131460
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-cam-winget-eap-fast-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4851.txt

This document defines the Extensible Authentication Protocol (EAP)
based Flexible Authentication via Secure Tunneling (EAP-FAST)
protocol.  EAP-FAST is an EAP method that enables secure
communication between a peer and a server by using the Transport
Layer Security (TLS) to establish a mutually authenticated tunnel.
Within the tunnel, Type-Length-Value (TLV) objects are used to convey
authentication related data between the peer and the EAP server.  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 May  8 14:47:46 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 8 May 2007 14:47:46 -0700
Subject: [rfc-dist] RFC 4872 on RSVP-TE Extensions in Support of End-to-End
	Generalized Multi-Protocol Label Switching (GMPLS) Recovery
Message-ID: <200705082147.l48Llksf024602@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4872

        Title:      RSVP-TE Extensions in Support of 
                    End-to-End Generalized Multi-Protocol Label Switching 
(GMPLS) 
                    Recovery 
        Author:     J.P. Lang, Ed.,
                    Y. Rekhter, Ed.,
                      D. Papadimitriou, Ed.
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    jplang at ieee.org, 
                    yakov at juniper.net, 
                    dimitri.papadimitriou at alcatel-lucent.be
        Pages:      47
        Characters: 111882
        Updates:    RFC3471
        See-Also:   

        I-D Tag:    draft-ietf-ccamp-gmpls-recovery-e2e-signaling-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4872.txt

This document describes protocol-specific procedures and extensions
for Generalized Multi-Protocol Label Switching (GMPLS) Resource
ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling to
support end-to-end Label Switched Path (LSP) recovery that denotes
protection and restoration.  A generic functional description of
GMPLS recovery can be found in a companion document, RFC 4426.  [STANDARDS TRACK]

This document is a product of the Common Control and Measurement Plane
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  8 14:52:04 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 8 May 2007 14:52:04 -0700
Subject: [rfc-dist] RFC 4873 on MPLS Segment Recovery
Message-ID: <200705082152.l48Lq47X024636@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4873

        Title:      MPLS Segment Recovery 
        Author:     L. Berger, I. Bryskin,
                    D. Papadimitriou, A. Farrel
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    lberger at labn.net, 
                    IBryskin at advaoptical.com, 
                    dimitri.papadimitriou at alcatel-lucent.be,  
                    adrian at olddog.co.uk
        Pages:      25
        Characters: 56919
        Updates:    RFC3473, RFC4872
        See-Also:   

        I-D Tag:    draft-ietf-ccamp-gmpls-segment-recovery-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4873.txt

This document describes protocol specific procedures for GMPLS
(Generalized Multi-Protocol Label Switching) RSVP-TE (Resource
ReserVation Protocol - Traffic Engineering) signaling extensions to
support label switched path (LSP) segment protection and restoration.
These extensions are intended to complement and be consistent with
the RSVP-TE Extensions for End-to-End GMPLS Recovery (RFC 4872).
Implications and interactions with fast reroute are also addressed.
This document also updates the handling of NOTIFY_REQUEST objects.  
[STANDARDS-TRACK]

This document is a product of the Common Control and Measurement Plane
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  8 14:52:00 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 8 May 2007 14:52:00 -0700
Subject: [rfc-dist] RFC 4872 on RSVP-TE Extensions in Support of End-to-End
	Generalized Multi-Protocol Label Switching (GMPLS) Recovery
Message-ID: <200705082152.l48Lq0dF024631@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4872

        Title:      RSVP-TE Extensions in Support of 
                    End-to-End Generalized Multi-Protocol Label Switching 
                    (GMPLS) Recovery 
        Author:     J.P. Lang, Ed.,
                    Y. Rekhter, Ed.,
                    D. Papadimitriou, Ed.
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    jplang at ieee.org, 
                    yakov at juniper.net, 
                    dimitri.papadimitriou at alcatel-lucent.be
        Pages:      47
        Characters: 111882
        Updates:    RFC3471
        See-Also:   

        I-D Tag:    draft-ietf-ccamp-gmpls-recovery-e2e-signaling-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4872.txt

This document describes protocol-specific procedures and extensions
for Generalized Multi-Protocol Label Switching (GMPLS) Resource
ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling to
support end-to-end Label Switched Path (LSP) recovery that denotes
protection and restoration.  A generic functional description of
GMPLS recovery can be found in a companion document, RFC 4426.  
[STANDARDS TRACK]

This document is a product of the Common Control and Measurement Plane
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Wed May  9 15:55:25 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 9 May 2007 15:55:25 -0700
Subject: [rfc-dist] RFC 4858 on Document Shepherding from Working Group Last
	Call to Publication
Message-ID: <200705092255.l49MtPsH028559@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4858

        Title:      Document Shepherding from Working Group 
                    Last Call to Publication 
        Author:     H. Levkowetz, D. Meyer,
                    L. Eggert, A. Mankin
        Status:     Informational
        Date:       May 2007
        Mailbox:    henrik at levkowetz.com, 
                    dmm at 1-4-5.net, 
                    lars.eggert at nokia.com,  mankin at psg.com
        Pages:      21
        Characters: 48572
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-proto-wgchair-doc-shepherding-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4858.txt

This document describes methodologies that have been designed to
improve and facilitate IETF document flow processing.  It specifies a
set of procedures under which a working group chair or secretary
serves as the primary Document Shepherd for a document that has been
submitted to the IESG for publication.  Before this, the Area
Director responsible for the working group has traditionally filled
the shepherding role.  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 11 14:04:21 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 11 May 2007 14:04:21 -0700
Subject: [rfc-dist] RFC 4866 on Enhanced Route Optimization for Mobile IPv6
Message-ID: <200705112104.l4BL4LJC005265@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4866

        Title:      Enhanced Route Optimization for Mobile 
                    IPv6 
        Author:     J. Arkko, C. Vogt,
                    W. Haddad
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    jari.arkko at ericsson.com, 
                    chvogt at tm.uka.de, 
                    wassim.haddad at ericsson.com
        Pages:      54
        Characters: 145757
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mipshop-cga-cba-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4866.txt

This document specifies an enhanced version of Mobile IPv6 route
optimization, providing lower handoff delays, increased security, and
reduced signaling overhead.  [STANDARDS TRACK]

This document is a product of the MIPv6 Signaling and Handoff Optimization
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 11 14:04:05 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 11 May 2007 14:04:05 -0700
Subject: [rfc-dist] RFC 4863 on Wildcard Pseudowire Type
Message-ID: <200705112104.l4BL45AK005260@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4863

        Title:      Wildcard Pseudowire Type 
        Author:     L. Martini, G. Swallow
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    lmartini at cisco.com, 
                    swallow at cisco.com
        Pages:      6
        Characters: 11321
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pwe3-wildcard-pw-type-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4863.txt

Pseudowire signaling requires that the Pseudowire Type (PW Type) be
identical in both directions.  For certain applications the
configuration of the PW Type is most easily accomplished by
configuring this information at just one PW endpoint.  In any form of
LDP-based signaling, each PW endpoint must initiate the creation of a
unidirectional LSP.  In order to allow the initiation of these two
LSPs to remain independent, a means is needed for allowing the PW endpoint
(lacking a priori knowledge of the PW Type) to initiate the creation of
an LSP.  This document defines a Wildcard PW Type to
satisfy this 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  Fri May 11 14:04:49 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 11 May 2007 14:04:49 -0700
Subject: [rfc-dist] RFC 4890 on Recommendations for Filtering ICMPv6
	Messages in Firewalls
Message-ID: <200705112104.l4BL4n0k005275@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4890

        Title:      Recommendations for Filtering ICMPv6 Messages 
                    in Firewalls 
        Author:     E. Davies, J. Mohacsi
        Status:     Informational
        Date:       May 2007
        Mailbox:    elwynd at dial.pipex.com, 
                    mohacsi at niif.hu
        Pages:      38
        Characters: 83479
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-icmpv6-filtering-recs-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4890.txt

In networks supporting IPv6, the Internet Control Message Protocol
version 6 (ICMPv6) plays a fundamental role with a large number of
functions, and a correspondingly large number of message types and
options.  ICMPv6 is essential to the functioning of IPv6, but there
are a number of security risks associated with uncontrolled
forwarding of ICMPv6 messages.  Filtering strategies designed for the
corresponding protocol, ICMP, in IPv4 networks are not directly
applicable, because these strategies are intended to accommodate a
useful auxiliary protocol that may not be required for correct
functioning.

This document provides some recommendations for ICMPv6 firewall
filter configuration that will allow propagation of ICMPv6 messages
that are needed to maintain the functioning of the network but drop
messages that are potential security risks.  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  Fri May 11 14:04:37 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 11 May 2007 14:04:37 -0700
Subject: [rfc-dist] RFC 4875 on Extensions to Resource Reservation Protocol
	- Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
	Label Switched Paths (LSPs)
Message-ID: <200705112104.l4BL4bLn005270@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4875

        Title:      Extensions to Resource Reservation Protocol 
                    - Traffic Engineering (RSVP-TE) for Point-to-Multipoint 
                    TE Label Switched Paths (LSPs) 
        Author:     R. Aggarwal, Ed.,
                    D. Papadimitriou, Ed.,
                    S. Yasukawa, Ed.
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    rahul at juniper.net, 
                    yasukawa.seisho at lab.ntt.co.jp, 
                    Dimitri.Papadimitriou at alcatel-lucent.be
        Pages:      53
        Characters: 125394
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-rsvp-te-p2mp-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4875.txt

This document describes extensions to Resource Reservation Protocol -
Traffic Engineering (RSVP-TE) for the set up of Traffic Engineered
(TE) point-to-multipoint (P2MP) Label Switched Paths (LSPs) in Multi-
Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
networks.  The solution relies on RSVP-TE without requiring a
multicast routing protocol in the Service Provider core.  Protocol
elements and procedures for this solution are described.

There can be various applications for P2MP TE LSPs such as IP
multicast.  Specification of how such applications will use a P2MP TE
LSP is outside the scope of this document.  [STANDARDS TRACK]

This document is a product of the Multiprotocol Label Switching
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 11 14:05:03 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 11 May 2007 14:05:03 -0700
Subject: [rfc-dist] RFC 4891 on Using IPsec to Secure IPv6-in-IPv4 Tunnels
Message-ID: <200705112105.l4BL537J005284@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4891

        Title:      Using IPsec to Secure IPv6-in-IPv4 
                    Tunnels 
        Author:     R. Graveman, M. Parthasarathy,
                    P. Savola, H. Tschofenig
        Status:     Informational
        Date:       May 2007
        Mailbox:    rfg at acm.org, 
                    mohanp at sbcglobal.net, 
                    psavola at funet.fi,  Hannes.Tschofenig at nsn.com
        Pages:      23
        Characters: 46635
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-ipsec-tunnels-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4891.txt

This document gives guidance on securing manually configured IPv6-in-
IPv4 tunnels using IPsec in transport mode.  No additional protocol
extensions are described beyond those available with the IPsec
framework.  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  Fri May 18 17:23:56 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 18 May 2007 17:23:56 -0700
Subject: [rfc-dist] RFC 4876 on A Configuration Profile Schema for
	Lightweight Directory Access Protocol (LDAP)-Based Agents
Message-ID: <200705190023.l4J0NuQY015182@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4876

        Title:      A Configuration Profile Schema for 
                    Lightweight Directory Access Protocol (LDAP)-Based 
Agents 
        Author:     B. Neal-Joslin, Ed.,
                    L. Howard, M. Ansari
        Status:     Informational
        Date:       May 2007
        Mailbox:    bob_joslin at hp.com, 
                    lukeh at padl.com, 
                    morteza at infoblox.com
        Pages:      39
        Characters: 73468
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-joslin-config-schema-17.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4876.txt

This document consists of two primary components, a schema for agents
that make use of the Lightweight Directory Access protocol (LDAP) and
a proposed use case of that schema, for distributed configuration of
similar directory user agents.  A set of attribute types and an
object class are proposed.  In the proposed use case, directory user
agents (DUAs) can use this schema to determine directory data
location and access parameters for specific services they support.
In addition, in the proposed use case, attribute and object class
mapping allows DUAs to reconfigure their expected (default) schema to
match that of the end user's environment.  This document is intended
to be a skeleton for future documents that describe configuration of
specific DUA services.  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 18 17:32:36 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 18 May 2007 17:32:36 -0700
Subject: [rfc-dist] RFC 4893 on BGP Support for Four-octet AS Number Space
Message-ID: <200705190032.l4J0Waxg015254@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4893

        Title:      BGP Support for Four-octet AS 
                    Number Space 
        Author:     Q. Vohra, E. Chen
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    quaizar.vohra at gmail.com, 
                    enkechen at cisco.com
        Pages:      10
        Characters: 21520
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-idr-as4bytes-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4893.txt

Currently the Autonomous System (AS) number is encoded as a two-octet
entity in BGP.  This document describes extensions to BGP to carry the
Autonomous System number as a four-octet entity.  [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 May 18 17:32:19 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 18 May 2007 17:32:19 -0700
Subject: [rfc-dist] RFC 4864 on Local Network Protection for IPv6
Message-ID: <200705190032.l4J0WJOx015249@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4864

        Title:      Local Network Protection for IPv6 
        Author:     G. Van de Velde, T. Hain,
                    R. Droms, B. Carpenter,
                    E. Klein
        Status:     Informational
        Date:       May 2007
        Mailbox:    gunter at cisco.com, 
                    alh-ietf at tndh.net, 
                    rdroms at cisco.com,  brc at zurich.ibm.com, 
                    ericlklein.ipv6 at gmail.com
        Pages:      36
        Characters: 95448
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-nap-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4864.txt

Although there are many perceived benefits to Network Address
Translation (NAT), its primary benefit of "amplifying" available
address space is not needed in IPv6.  In addition to NAT's many
serious disadvantages, there is a perception that other benefits
exist, such as a variety of management and security attributes that
could be useful for an Internet Protocol site.  IPv6 was designed
with the intention of making NAT unnecessary, and this document shows
how Local Network Protection (LNP) using IPv6 can provide the same or
more benefits without the need for address translation.  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  Fri May 18 17:32:49 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 18 May 2007 17:32:49 -0700
Subject: [rfc-dist] RFC 4876 on A Configuration Profile Schema for
	Lightweight Directory Access Protocol (LDAP)-Based Agents
Message-ID: <200705190032.l4J0WnWu015259@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4876

        Title:      A Configuration Profile Schema for 
                    Lightweight Directory Access Protocol (LDAP)-Based 
                    Agents 
        Author:     B. Neal-Joslin, Ed.,
                    L. Howard, M. Ansari
        Status:     Informational
        Date:       May 2007
        Mailbox:    bob_joslin at hp.com, 
                    lukeh at padl.com, 
                    morteza at infoblox.com
        Pages:      39
        Characters: 73468
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-joslin-config-schema-17.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4876.txt

This document consists of two primary components, a schema for agents
that make use of the Lightweight Directory Access protocol (LDAP) and
a proposed use case of that schema, for distributed configuration of
similar directory user agents.  A set of attribute types and an
object class are proposed.  In the proposed use case, directory user
agents (DUAs) can use this schema to determine directory data
location and access parameters for specific services they support.
In addition, in the proposed use case, attribute and object class
mapping allows DUAs to reconfigure their expected (default) schema to
match that of the end user's environment.  This document is intended
to be a skeleton for future documents that describe configuration of
specific DUA services.  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 May 22 16:41:02 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 22 May 2007 16:41:02 -0700
Subject: [rfc-dist] RFC 4825 on The Extensible Markup Language (XML)
	Configuration Access Protocol (XCAP)
Message-ID: <200705222341.l4MNf2sD026479@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4825

        Title:      The Extensible Markup Language (XML) 
                    Configuration Access Protocol (XCAP) 
        Author:     J. Rosenberg
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    jdrosen at cisco.com
        Pages:      71
        Characters: 166627
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-simple-xcap-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4825.txt

This specification defines the Extensible Markup Language (XML)
Configuration Access Protocol (XCAP).  XCAP allows a client to read,
write, and modify application configuration data stored in XML format
on a server.  XCAP maps XML document sub-trees and element attributes
to HTTP URIs, so that these components can be directly accessed by
HTTP.  [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 May 22 16:41:26 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 22 May 2007 16:41:26 -0700
Subject: [rfc-dist] RFC 4827 on An Extensible Markup Language (XML)
	Configuration Access Protocol (XCAP) Usage for Manipulating
	Presence Document Contents
Message-ID: <200705222341.l4MNfQqM026489@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4827

        Title:      An Extensible Markup Language (XML) 
                    Configuration Access Protocol (XCAP) Usage for 
                    Manipulating Presence Document Contents 
        Author:     M. Isomaki, E. Leppanen
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    markus.isomaki at nokia.com, 
                    eva-maria.leppanen at nokia.com
        Pages:      11
        Characters: 22896
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-simple-xcap-pidf-manipulation-usage-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4827.txt

This document describes a usage of the Extensible Markup Language
(XML) Configuration Access Protocol (XCAP) for manipulating the
contents of Presence Information Data Format (PIDF) based presence
documents.  It is intended to be used in Session Initiation Protocol
(SIP) based presence systems, where the Event State Compositor can
use the XCAP-manipulated presence document as one of the inputs on
which it builds the overall presence state for the presentity.  
[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 May 22 16:41:14 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 22 May 2007 16:41:14 -0700
Subject: [rfc-dist] RFC 4826 on Extensible Markup Language (XML) Formats for
	Representing Resource Lists
Message-ID: <200705222341.l4MNfES3026484@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4826

        Title:      Extensible Markup Language (XML) Formats 
                    for Representing Resource Lists 
        Author:     J. Rosenberg
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    jdrosen at cisco.com
        Pages:      31
        Characters: 68850
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-simple-xcap-list-usage-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4826.txt

In multimedia communications, presence, and instant messaging
systems, there is a need to define Uniform Resource Identifiers
(URIs) that represent services that are associated with a group of
users.  One example is a resource list service.  If a user sends a
Session Initiation Protocol (SIP) SUBSCRIBE message to the URI
representing the resource list service, the server will obtain the
state of the users in the associated group, and provide it to the
sender.  To facilitate definition of these services, this
specification defines two Extensible Markup Language (XML) documents.
One document contains service URIs, along with their service
definition and a reference to the associated group of users.  The
second document contains the user lists that are referenced from the
first.  This list of users can be utilized by other applications and
services.  Both documents can be created and managed with the XML
Configuration Access Protocol (XCAP).  [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 May 22 17:06:47 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 22 May 2007 17:06:47 -0700
Subject: [rfc-dist] RFC 4870 on Domain-Based Email Authentication Using
	Public Keys Advertised in the DNS (DomainKeys)
Message-ID: <200705230006.l4N06lQD026544@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4870

        Title:      Domain-Based Email Authentication Using Public 
                    Keys Advertised in the DNS (DomainKeys) 
        Author:     M. Delany
        Status:     Historic
        Date:       May 2007
        Mailbox:    markd+domainkeys at yahoo-inc.com
        Pages:      41
        Characters: 87378
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-delany-domainkeys-base-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4870.txt

"DomainKeys" creates a domain-level authentication framework for email
by using public key technology and the DNS to prove the provenance and
contents of an email.

This document defines a framework for digitally signing email on a
per-domain basis.  The ultimate goal of this framework is to
unequivocally prove and protect identity while retaining the semantics
of Internet email as it is known today.

Proof and protection of email identity may assist in the global
control of "spam" and "phishing".  This memo defines a Historic Document 
for the Internet community.


HISTORIC: This memo defines a Historic Document for the Internet 
community.  It does not specify an Internet standard of any kind. 
Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Tue May 22 17:06:55 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 22 May 2007 17:06:55 -0700
Subject: [rfc-dist] RFC 4871 on DomainKeys Identified Mail (DKIM) Signatures
Message-ID: <200705230006.l4N06tdi026549@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4871

        Title:      DomainKeys Identified Mail (DKIM) Signatures 
        Author:     E. Allman, J. Callas,
                    M. Delany, M. Libbey,
                    J. Fenton, M. Thomas
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    eric+dkim at sendmail.org, 
                    jon at pgp.com, 
                    markd+dkim at yahoo-inc.com,  
                    mlibbeymail-mailsig at yahoo.com, 
                    fenton at cisco.com,  mat at cisco.com
        Pages:      71
        Characters: 166054
        Obsoletes:  RFC4870
        See-Also:   

        I-D Tag:    draft-ietf-dkim-base-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4871.txt

DomainKeys Identified Mail (DKIM) defines a domain-level
authentication framework for email using public-key cryptography and
key server technology to permit verification of the source and
contents of messages by either Mail Transfer Agents (MTAs) or Mail
User Agents (MUAs).  The ultimate goal of this framework is to permit
a signing domain to assert responsibility for a message, thus
protecting message signer identity and the integrity of the messages
they convey while retaining the functionality of Internet email as it
is known today.  Protection of email identity may assist in the
global control of "spam" and "phishing".  [STANDARDS TRACK]

This document is a product of the Domain Keys Identified Mail
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 22 17:08:38 2007
From: rfc-editor at rfc-editor.org (RFC Editor)
Date: Tue, 22 May 2007 17:08:38 -0700
Subject: [rfc-dist] Correction - Re: RFC 4870 on Domain-Based Email
	Authentication Using Public Keys Advertised in the DNS (DomainKeys)
In-Reply-To: <200705230006.l4N06lQD026544@nit.isi.edu>
References: <200705230006.l4N06lQD026544@nit.isi.edu>
Message-ID: <20070523000838.GG16866@isi.edu>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 4870

        Title:      Domain-Based Email Authentication Using Public 
                    Keys Advertised in the DNS (DomainKeys) 
        Author:     M. Delany
        Status:     Historic
        Date:       May 2007
        Mailbox:    markd+domainkeys at yahoo-inc.com
        Pages:      41
        Characters: 87378
        Obsoleted By: RFC 4871

        I-D Tag:    draft-delany-domainkeys-base-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4870.txt

"DomainKeys" creates a domain-level authentication framework for email
by using public key technology and the DNS to prove the provenance and
contents of an email.

This document defines a framework for digitally signing email on a
per-domain basis.  The ultimate goal of this framework is to
unequivocally prove and protect identity while retaining the semantics
of Internet email as it is known today.

Proof and protection of email identity may assist in the global
control of "spam" and "phishing".  This memo defines a Historic Document 
for the Internet community.


HISTORIC: This memo defines a Historic Document for the Internet 
community.  It does not specify an Internet standard of any kind. 
Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


From rfc-editor at rfc-editor.org  Fri May 25 14:19:49 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 25 May 2007 14:19:49 -0700
Subject: [rfc-dist] RFC 4882 on IP Address Location Privacy and Mobile IPv6:
	Problem Statement
Message-ID: <200705252119.l4PLJn2s013281@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4882

        Title:      IP Address Location Privacy and 
                    Mobile IPv6: Problem Statement 
        Author:     R. Koodli
        Status:     Informational
        Date:       May 2007
        Mailbox:    rajeev.koodli at nokia.com
        Pages:      11
        Characters: 24987
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip6-location-privacy-ps-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4882.txt

In this document, we discuss location privacy as applicable to Mobile
IPv6.  We document the concerns arising from revealing a Home Address
to an onlooker and from disclosing a Care-of Address to a
correspondent.  This memo provides information for the Internet community.

This document is a product of the Mobility for IPv6
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 May 25 14:19:58 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 25 May 2007 14:19:58 -0700
Subject: [rfc-dist] RFC 4902 on Integrity, Privacy,
	and Security in Open Pluggable Edge Services (OPES) for SMTP
Message-ID: <200705252119.l4PLJw32013286@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4902

        Title:      Integrity, Privacy, and Security in 
                    Open Pluggable Edge Services (OPES) for 
                    SMTP 
        Author:     M. Stecher
        Status:     Informational
        Date:       May 2007
        Mailbox:    martin.stecher at webwasher.com
        Pages:      14
        Characters: 30120
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opes-smtp-security-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4902.txt

The Open Pluggable Edge Services (OPES) framework is application
agnostic.  Application-specific adaptations extend that framework.
Previous work has focused on HTTP and work for SMTP is in progress.
These protocols differ fundamentally in the way data flows, and it
turns out that existing OPES requirements and IAB considerations for
OPES need to be reviewed with regards to how well they fit for SMTP
adaptation.  This document analyzes aspects about the integrity of
SMTP and mail message adaptation by OPES systems and about privacy and
security issues when the OPES framework is adapted to SMTP.  It also lists
requirements that must be considered when creating the "SMTP
adaptation with OPES" document.

The intent of this document is to capture this information before the
current OPES working group shuts down.  This is to provide input for
subsequent working groups or individual contributors that may pick up
the OPES/SMTP work at a later date.  This memo provides information for 
the Internet community.

This document is a product of the Open Pluggable Edge Services
Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Wed May 30 16:50:24 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 30 May 2007 16:50:24 -0700
Subject: [rfc-dist] RFC 4898 on TCP Extended Statistics MIB
Message-ID: <200705302350.l4UNoO0b000328@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4898

        Title:      TCP Extended Statistics MIB 
        Author:     M. Mathis, J. Heffner,
                    R. Raghunarayan
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    mathis at psc.edu, 
                    jheffner at psc.edu, 
                    raraghun at cisco.com
        Pages:      75
        Characters: 153768
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-tcp-mib-extension-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4898.txt

This document describes extended performance statistics for TCP.  They are
designed to use TCP's ideal vantage point to diagnose performance problems
in both the network and the application.  If a network-based application 
is performing poorly, TCP can determine if the bottleneck is in the 
sender, the receiver, or the network itself.  If the bottleneck is in the 
network, TCP can provide specific information about its nature.  
[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  Wed May 30 16:50:59 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 30 May 2007 16:50:59 -0700
Subject: [rfc-dist] RFC 4932 on Extensible Provisioning Protocol (EPP) Host
	Mapping
Message-ID: <200705302350.l4UNoxfc000343@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4932

        Title:      Extensible Provisioning Protocol (EPP) Host 
                    Mapping 
        Author:     S. Hollenbeck
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    shollenbeck at verisign.com
        Pages:      30
        Characters: 57623
        Obsoletes:  RFC3732
        See-Also:   

        I-D Tag:    draft-hollenbeck-epp-rfc3732bis-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4932.txt

This document describes an Extensible Provisioning Protocol (EPP)
mapping for the provisioning and management of Internet host names
stored in a shared central repository.  Specified in XML, the mapping
defines EPP command syntax and semantics as applied to host names.
This document obsoletes RFC 3732.  [STANDARDS TRACK]

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  Wed May 30 16:50:39 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 30 May 2007 16:50:39 -0700
Subject: [rfc-dist] RFC 4934 on Extensible Provisioning Protocol (EPP)
	Transport Over TCP
Message-ID: <200705302350.l4UNoddA000333@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4934

        Title:      Extensible Provisioning Protocol (EPP) Transport 
                    Over TCP 
        Author:     S. Hollenbeck
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    shollenbeck at verisign.com
        Pages:      10
        Characters: 22914
        Obsoletes:  RFC3734
        See-Also:   

        I-D Tag:    draft-hollenbeck-epp-rfc3734bis-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4934.txt

This document describes how an Extensible Provisioning Protocol (EPP)
session is mapped onto a single Transmission Control Protocol (TCP)
connection.  This mapping requires use of the Transport Layer
Security (TLS) protocol to protect information exchanged between an
EPP client and an EPP server.  This document obsoletes RFC 3734. [STANDARDS TRACK]

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  Wed May 30 16:50:48 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 30 May 2007 16:50:48 -0700
Subject: [rfc-dist] RFC 4933 on Extensible Provisioning Protocol (EPP)
	Contact Mapping
Message-ID: <200705302350.l4UNomH2000338@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4933

        Title:      Extensible Provisioning Protocol (EPP) Contact 
                    Mapping 
        Author:     S. Hollenbeck
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    shollenbeck at verisign.com
        Pages:      43
        Characters: 82254
        Obsoletes:  RFC3733
        See-Also:   

        I-D Tag:    draft-hollenbeck-epp-rfc3733bis-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4933.txt

This document describes an Extensible Provisioning Protocol (EPP)
mapping for the provisioning and management of individual or
organizational social information identifiers (known as "contacts")
stored in a shared central repository.  Specified in Extensible
Markup Language (XML), the mapping defines EPP command syntax and
semantics as applied to contacts.  This document obsoletes RFC 3733.  
[STANDARDS TRACK]

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  Wed May 30 16:51:08 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 30 May 2007 16:51:08 -0700
Subject: [rfc-dist] RFC 4931 on Extensible Provisioning Protocol (EPP)
	Domain Name Mapping
Message-ID: <200705302351.l4UNp8ic000348@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4931

        Title:      Extensible Provisioning Protocol (EPP) Domain 
                    Name Mapping 
        Author:     S. Hollenbeck
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    shollenbeck at verisign.com
        Pages:      46
        Characters: 88729
        Obsoletes:  RFC3731
        See-Also:   

        I-D Tag:    draft-hollenbeck-epp-rfc3731bis-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4931.txt

This document describes an Extensible Provisioning Protocol (EPP)
mapping for the provisioning and management of Internet domain names
stored in a shared central repository.  Specified in XML, the mapping
defines EPP command syntax and semantics as applied to domain names.
This document obsoletes RFC 3731.  [STANDARDS TRACK]

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  Wed May 30 16:51:18 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 30 May 2007 16:51:18 -0700
Subject: [rfc-dist] RFC 4930 on Extensible Provisioning Protocol (EPP)
Message-ID: <200705302351.l4UNpIwJ000353@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4930

        Title:      Extensible Provisioning Protocol (EPP) 
        Author:     S. Hollenbeck
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    shollenbeck at verisign.com
        Pages:      72
        Characters: 135648
        Obsoletes:  RFC3730
        See-Also:   

        I-D Tag:    draft-hollenbeck-epp-rfc3730bis-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4930.txt

This document describes an application layer client-server protocol
for the provisioning and management of objects stored in a shared
central repository.  Specified in XML, the protocol defines generic
object management operations and an extensible framework that maps
protocol operations to objects.  This document includes a protocol
specification, an object mapping template, and an XML media type
registration.  This document obsoletes RFC 3730.  [STANDARDS TRACK]

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  Thu May 31 17:40:05 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 31 May 2007 17:40:05 -0700
Subject: [rfc-dist] RFC 4894 on Use of Hash Algorithms in Internet Key
	Exchange (IKE) and IPsec
Message-ID: <200706010040.l510e5Wh004024@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4894

        Title:      Use of Hash Algorithms in 
                    Internet Key Exchange (IKE) and IPsec 
        Author:     P. Hoffman
        Status:     Informational
        Date:       May 2007
        Mailbox:    paul.hoffman at vpnc.org
        Pages:      11
        Characters: 22899
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-hoffman-ike-ipsec-hash-use-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4894.txt

This document describes how the IKEv1 (Internet Key Exchange version
1), IKEv2, and IPsec protocols use hash functions, and explains the
level of vulnerability of these protocols to the reduced collision
resistance of the MD5 and SHA-1 hash algorithms.  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 31 17:40:09 2007
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 31 May 2007 17:40:09 -0700
Subject: [rfc-dist] RFC 4865 on SMTP Submission Service Extension for Future
	Message Release
Message-ID: <200706010040.l510e9Fl004029@nit.isi.edu>


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4865

        Title:      SMTP Submission Service Extension for 
                    Future Message Release 
        Author:     G. White, G. Vaudreuil
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    g.a.white at comcast.net, 
                    GregV at ieee.org
        Pages:      11
        Characters: 21495
        Updates:    RFC3463, RFC3464
        See-Also:   

        I-D Tag:    draft-vaudreuil-futuredelivery-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4865.txt

This memo defines an extension to the SMTP submission protocol for a
client to indicate a future time for the message to be released for
delivery.  This extension permits a client to use server-based
storage for a message that should be held in queue until an
appointed time in the future.  This is useful for clients which do
not have local storage or are otherwise unable to release a message
for delivery at an appointed time.  [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

...