[rfc-dist] BCP 97, RFC 3967 on Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level

[rfc-editor at rfc-editor.org ([e-mail])]

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


        RFC 3967

        Title:      Clarifying when Standards Track Documents may
                    Refer Normatively to Documents at a Lower Level
        Author(s):  R. Bush, T. Narten
        Status:     Best Current Practice
        Date:       December 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      6
        Characters: 12251
        SeeAlso:    BCP 97

        I-D Tag:    draft-ymbk-downref-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3967.txt


IETF procedures generally require that a standards track RFC may not
have a normative reference to another standards track document at a
lower maturity level or to a non standards track specification (other
than specifications from other standards bodies).  For example, a
standards track document may not have a normative reference to an
informational RFC.  Exceptions to this rule are sometimes needed as
the IETF uses informational RFCs to describe non-IETF standards or
IETF-specific modes of use of such standards.  This
document clarifies and updates the procedure used in these
circumstances.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Wed Jan  5 17:04:55 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jan  5 17:06:10 2005
Subject: [rfc-dist] RFC 3947 on Negotiation of NAT-Traversal in the IKE
Message-ID: <[e-mail]>


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


        RFC 3947

        Title:      Negotiation of NAT-Traversal in the IKE
        Author(s):  T. Kivinen, B. Swander, A. Huttunen, V. Volpe
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail],
                    [e-mail], [e-mail],
                    [e-mail]
        Pages:      16
        Characters: 34759
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipsec-nat-t-ike-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3947.txt


This document describes how to detect one or more network address
translation devices (NATs) between IPsec hosts, and how to negotiate
the use of UDP encapsulation of IPsec packets through NAT boxes in
Internet Key Exchange (IKE).

This document is a product of IP Security Protocol Working Group of
the IETF.

This is now a Proposed Standard Protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Wed Jan  5 17:07:20 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jan  5 17:10:39 2005
Subject: [rfc-dist] RFC 3948 on UDP Encapsulation of IPsec ESP Packets
Message-ID: <[e-mail]>


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


        RFC 3948

        Title:      UDP Encapsulation of IPsec ESP Packets
        Author(s):  A. Huttunen, B. Swander, V. Volpe, L. DiBurro,
                    M. Stenberg
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail]
        Pages:      15
        Characters: 30366
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipsec-udp-encaps-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3948.txt


This protocol specification defines methods to encapsulate and
decapsulate IP Encapsulating Security Payload (ESP) packets inside
UDP packets for traversing Network Address
Translators.  ESP encapsulation, as defined in this document,
can be used in both IPv4 and IPv6 scenarios.  Whenever negotiated,
encapsulation is used with Internet Key Exchange (IKE).

This document is a product of the IP Security Protocol Working Group
of the IETF.

This is now a Proposed Standard Protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Wed Jan  5 17:09:29 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jan  5 17:11:41 2005
Subject: [rfc-dist] RFC 3970 on A Traffic Engineering (TE) MIB
Message-ID: <[e-mail]>


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


        RFC 3970

        Title:      A Traffic Engineering (TE) MIB
        Author(s):  K. Kompella
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail]
        Pages:      44
        Characters: 88833
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-tewg-mib-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3970.txt


This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for Traffic Engineered
(TE) Tunnels; for example, Multi-Protocol Label Switched Paths.

This document is a product of the Internet Traffic Engineering Working
Group of the IETF.

This is now a Proposed Standard Protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Thu Jan  6 17:04:24 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jan  6 17:06:38 2005
Subject: [rfc-dist] RFC 3958 on Domain-Based Application Service Location
	Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)
Message-ID: <[e-mail]>


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


        RFC 3958

        Title:      Domain-Based Application Service Location Using
                    SRV RRs and the Dynamic Delegation Discovery
                    Service (DDDS)
        Author(s):  L. Daigle, A. Newton
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail]
        Pages:      25
        Characters: 54568
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-daigle-snaptr-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3958.txt


This memo defines a generalized mechanism for application service
naming that allows service location without relying on rigid domain
naming conventions (so-called name hacks).  The proposal defines a
Dynamic Delegation Discovery System (DDDS) Application to map domain
name, application service name, and application protocol dynamically
to target server and port.

This is now a Proposed Standard Protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Thu Jan  6 17:06:17 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jan  6 17:07:28 2005
Subject: [rfc-dist] RFC 3981 on IRIS: The Internet Registry Information
	Service (IRIS) Core Protocol
Message-ID: <[e-mail]>


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


        RFC 3981

        Title:      IRIS: The Internet Registry Information Service
                    (IRIS) Core Protocol
        Author(s):  A. Newton, M. Sanz
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail]
        Pages:      52
        Characters: 101359
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-crisp-iris-core-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3981.txt


This document describes an application layer client-server protocol
for a framework to represent the query and result operations of
the information services of Internet registries.  Specified in the
Extensible Markup Language (XML), the protocol defines generic query
and result operations and a mechanism for extending these operations
for specific registry service needs.

This document is a product of the Cross Registry Information Service
Protocol Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Thu Jan  6 17:07:54 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jan  6 17:10:47 2005
Subject: [rfc-dist] RFC 3982 on IRIS: A Domain Registry (dreg) Type for the
	Internet Registry Information Service (IRIS)
Message-ID: <[e-mail]>


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


        RFC 3982

        Title:      IRIS:  A Domain Registry (dreg) Type for the
                    Internet Registry Information Service (IRIS)
        Author(s):  A. Newton, M. Sanz
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail]
        Pages:      50
        Characters: 90901
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-crisp-iris-dreg-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3982.txt


This document describes an Internet Registry Information Service
(IRIS) registry schema for registered DNS information.  The schema
extends the necessary query and result operations of IRIS to provide
the functional information service needs for syntaxes and results used
by domain registries and registrars.

This document is a product of the Cross Registry Information Service
Protocol Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Thu Jan  6 17:09:32 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jan  6 17:11:55 2005
Subject: [rfc-dist] RFC 3983 on Using the Internet Registry Information
	Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)
Message-ID: <[e-mail]>


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


        RFC 3983

        Title:      Using the Internet Registry Information Service
                    (IRIS) over the Blocks Extensible Exchange
                    Protocol (BEEP)
        Author(s):  A. Newton, M. Sanz
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail]
        Pages:      12
        Characters: 23466
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-crisp-iris-beep-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3983.txt


This document specifies how to use the Blocks Extensible Exchange
Protocol (BEEP) as the application transport substrate for the
Internet Registry Information Service (IRIS).

This document is a product of the Cross Registry Information Service
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Thu Jan 20 10:37:43 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jan 20 10:38:50 2005
Subject: [rfc-dist] RFC 3974 on SMTP Operational Experience in Mixed IPv4/v6
	Environments
Message-ID: <[e-mail]>


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


        RFC 3974

        Title:      SMTP Operational Experience in Mixed IPv4/v6
                    Environments
        Author(s):  M. Nakamura, J. Hagino
        Status:     Informational
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail]
        Pages:      10
        Characters: 22729
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-motonori-dualstack-smtp-requirement-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3974.txt


This document discusses SMTP operational experiences in IPv4/v6 dual
stack environments.  As IPv6-capable SMTP servers are deployed, it has
become apparent that certain configurations of MX records are
necessary for stable dual-stack (IPv4 and IPv6) SMTP operation.  This
document clarifies the existing problems in the transition period
between IPv4 SMTP and IPv6 SMTP.  It also defines operational
requirements for stable IPv4/v6 SMTP operation.

This document does not define any new protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Thu Jan 20 10:39:42 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jan 20 10:40:38 2005
Subject: [rfc-dist] RFC 3976 on Interworking SIP and Intelligent Network
	(IN) Applications
Message-ID: <[e-mail]>


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


        RFC 3976

        Title:      Interworking SIP and Intelligent Network (IN)
                    Applications
        Author(s):  V. K. Gurbani, F. Haerens, V. Rastogi
        Status:     Informational
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      25
        Characters: 60191
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-gurbani-sin-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3976.txt


Public Switched Telephone Network (PSTN) services such as 800-number
routing (freephone), time-and-day routing, credit-card calling,
and virtual private network (mapping a private network number into a
public number) are realized by the Intelligent Network (IN).  This
document addresses means to support existing IN services from Session
Initiation Protocol (SIP) endpoints for an IP-host-to-phone call.
The call request is originated on a SIP endpoint, but the services to
the call are provided by the data and procedures resident in the
PSTN/IN.  To provide IN services in a transparent manner to SIP
endpoints, this document describes the mechanism for interworking SIP
and Intelligent Network Application Part (INAP).

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Mon Jan 24 15:54:08 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jan 24 15:56:20 2005
Subject: [rfc-dist] RFC 3953 on Telephone Number Mapping (ENUM) Service
	Registration for Presence Services
Message-ID: <[e-mail]>


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


        RFC 3953

        Title:      Telephone Number Mapping (ENUM) Service
                    Registration for Presence Services
        Author(s):  J. Peterson
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail]
        Pages:      7
        Characters: 13875
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-enum-pres-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3953.txt


This document registers a Telephone Number Mapping (ENUM) service for
presence.  Specifically, this document focuses on provisioning pres
URIs in ENUM.

This document is a product of the Telephone Number Mapping Working
Group of the IETF.

This is now a Proposed Standard Protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Mon Jan 24 15:55:46 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jan 24 15:56:21 2005
Subject: [rfc-dist] RFC 3963 on Network Mobility (NEMO) Basic Support
	Protocol
Message-ID: <[e-mail]>


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


        RFC 3963

        Title:      Network Mobility (NEMO) Basic Support Protocol
        Author(s):  V. Devarapalli, R. Wakikawa, A. Petrescu,
                    P. Thubert
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail],
                    [e-mail],
                    [e-mail]
        Pages:      33
        Characters: 75955
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-nemo-basic-support-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3963.txt


This document describes the Network Mobility (NEMO) Basic Support
protocol that enables Mobile Networks to attach to different points
in the Internet.  The protocol is an extension of Mobile IPv6 and
allows session continuity for every node in the Mobile Network as
the network moves.  It also allows every node in the Mobile Network
to be reachable while moving around.  The Mobile Router, which
connects the network to the Internet, runs the NEMO Basic Support
protocol with its Home Agent.  The protocol is designed so
that network mobility is transparent to the nodes inside the Mobile
Network.

This document is a product of the Network Mobility Working Group of
the IETF.

This is now a Proposed Standard Protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Mon Jan 24 15:57:42 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jan 24 15:58:26 2005
Subject: [rfc-dist] RFC 3973 on Protocol Independent Multicast - Dense Mode
	(PIM-DM): Protocol Specification (Revised)
Message-ID: <[e-mail]>


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


        RFC 3973

        Title:      Protocol Independent Multicast - Dense Mode
                    (PIM-DM): Protocol Specification (Revised)
        Author(s):  A. Adams, J. Nicholas, W. Siadak
        Status:     Experimental
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      61
        Characters: 136708
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-pim-dm-new-v2-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3973.txt


This document specifies Protocol Independent Multicast - Dense Mode
(PIM-DM).  PIM-DM is a multicast routing protocol that uses the
underlying unicast routing information base to flood multicast
datagrams to all multicast routers.  Prune messages are used to
prevent future messages from propagating to routers without group
membership information.

This document is a product of the Protocol Independent Multicast
Working Group of the IETF.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  Distribution of this memo
is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Jan 25 17:32:04 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Jan 25 17:33:47 2005
Subject: [rfc-dist] STD 66,
	RFC 3986 on Uniform Resource Identifier (URI): Generic Syntax
Message-ID: <[e-mail]>


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


        STD 66
        RFC 3986

        Title:      Uniform Resource Identifier (URI): Generic Syntax
        Author(s):  T. Berners-Lee, R. Fielding, L. Masinter
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail], [e-mail]
        Pages:      61
        Characters: 141811
        Updates:    1738
        Obsoletes:  2732, 2396, 1808

        I-D Tag:    draft-fielding-uri-rfc2396bis-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3986.txt


A Uniform Resource Identifier (URI) is a compact sequence of
characters that identifies an abstract or physical resource.  This
specification defines the generic URI syntax and a process for
resolving URI references that might be in relative form, along with
guidelines and security considerations for the use of URIs on the
Internet.  The URI syntax defines a grammar that is a superset of all
valid URIs, allowing an implementation to parse the common
components of a URI reference without knowing the scheme-specific
requirements of every possible identifier.  This specification does
not define a generative grammar for URIs; that task is performed by
the individual specifications of each URI scheme.

This is now a Standard Protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Jan 25 17:33:20 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Jan 25 17:37:45 2005
Subject: [rfc-dist] RFC 3987 on Internationalized Resource Identifiers (IRIs)
Message-ID: <[e-mail]>


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


        RFC 3987

        Title:      Internationalized Resource Identifiers (IRIs)
        Author(s):  M. Duerst, M. Suignard
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail]
        Pages:      46
        Characters: 111190
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-duerst-iri-11.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3987.txt


This document defines a new protocol element, the Internationalized
Resource Identifier (IRI), as a complement to the Uniform Resource
Identifier (URI).  An IRI is a sequence of characters from the
Universal Character Set (Unicode/ISO 10646).  A mapping from IRIs to
URIs is defined, which means that IRIs can be used instead of URIs,
where appropriate, to identify resources.

The approach of defining a new protocol element was chosen instead
of extending or changing the definition of URIs.  This was done in
order to allow a clear distinction and to avoid incompatibilities with
existing software.  Guidelines are provided for the use and deployment
of IRIs in various protocols, formats, and software components that
currently deal with URIs.

This is now a Proposed Standard Protocol.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative