[rfc-dist] test -- please ignore

[falk at ISI.EDU (Aaron Falk)]

This is a test of the rfc-dist mailman service.  Please ignore.

--aaron
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.postel.org/pipermail/rfc-dist/attachments/20040318/7a642acf/PGP.bin
From rfc-editor at rfc-editor.org  Fri Mar 19 14:52:52 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Mar 19 14:54:49 2004
Subject: [rfc-dist] BCP 84,
	RFC 3704 on Ingress Filtering for Multihomed Networks
Message-ID: <[e-mail]>


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


        BCP 84
        RFC 3704

        Title:      Ingress Filtering for Multihomed Networks
        Author(s):  F. Baker, P. Savola
        Status:     Best Current Practice
        Date:       March 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      16
        Characters: 35942
        Updates:    2827
        SeeAlso:    BCP 84

        I-D Tag:    draft-savola-bcp38-multihoming-update-03.txt

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


BCP 38, RFC 2827, is designed to limit the impact of distributed
denial of service attacks, by denying traffic with spoofed addresses
access to the network, and to help ensure that traffic is traceable
to its correct source network.  As a side effect of protecting the
Internet against such attacks, the network implementing the solution
also protects itself from this and other attacks, such as spoofed
management access to networking equipment.  There are cases when this
may create problems, e.g., with multihoming.  This document describes
the current ingress filtering operational mechanisms, examines
generic issues related to ingress filtering, and delves into the
effects on multihoming in particular.  This memo updates RFC 2827.

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.echo 
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  Fri Mar 19 14:55:29 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Mar 19 14:56:15 2004
Subject: [rfc-dist] RFC 3739 on Internet X.509 Public Key Infrastructure:
	Qualified Certificates Profile
Message-ID: <[e-mail]>


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


        RFC 3739

        Title:      Internet X.509 Public Key Infrastructure:
                    Qualified Certificates Profile
        Author(s):  S. Santesson, M. Nystrom, T. Polk
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      34
        Characters: 67436
        Obsoletes:  3039

        I-D Tag:    draft-ietf-pkix-sonof3039-06.txt

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


This document forms a certificate profile, based on RFC 3280, for
identity certificates issued to natural persons.

The profile defines specific conventions for certificates that are
qualified within a defined legal framework, named Qualified
Certificates.  However, the profile does not define any legal
requirements for such Qualified Certificates.

The goal of this document is to define a certificate profile that
supports the issuance of Qualified Certificates independent of local
legal requirements.  The profile is however not limited to Qualified
Certificates and further profiling may facilitate specific local
needs.

This document is a product of the Public-Key Infrastructure (X.509)
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.echo 
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  Fri Mar 26 17:16:57 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Mar 26 17:17:21 2004
Subject: [rfc-dist] RFC 3716 on The IETF in the Large: Administration and
	Execution
Message-ID: <[e-mail]>


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


        RFC 3716

        Title:      The IETF in the Large:
                    Administration and Execution
        Author(s):  IAB Advisory Committee
        Status:     Informational
        Date:       March 2004
        Mailbox:    [e-mail]
        Pages:      40
        Characters: 91326
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-iab-advcomm-01.txt

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


In the fall of 2003, the IETF Chair and the IAB Chair formed an IAB
Advisory Committee (AdvComm), with a mandate to review the existing
IETF administrative structure and relationships (RFC Editor, IETF
Secretariat, IANA) and to propose changes to the IETF management
process or structure to improve the overall functioning of the IETF.
The AdvComm mandate did not include the standards process itself.

This memo documents the AdvComm's findings and proposals.

This document is a product of the IAB.

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.echo 
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  Fri Mar 26 17:15:30 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Mar 26 17:17:24 2004
Subject: [rfc-dist] RFC 3714 on IAB Concerns Regarding Congestion Control
	for Voice Traffic in the Internet
Message-ID: <[e-mail]>


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


        RFC 3714

        Title:      IAB Concerns Regarding Congestion Control for
                    Voice Traffic in the Internet
        Author(s):  S. Floyd, J. Kempf, Eds.
        Status:     Informational
        Date:       March 2004
        Mailbox:    [e-mail]
        Pages:      32
        Characters: 81368
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-iab-congestion-02.txt

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


This document discusses IAB concerns about effective end-to-end
congestion control for best-effort voice traffic in the Internet.
These concerns have to do with fairness, user quality, and with the
dangers of congestion collapse.  The concerns are particularly
relevant in light of the absence of a widespread Quality of Service
(QoS) deployment in the Internet, and the likelihood that this
situation will not change much in the near term.  This document is not
making any recommendations about deployment paths for Voice over
Internet Protocol (VoIP) in terms of QoS support, and is not claiming
that best-effort service can be relied upon to give acceptable
performance for VoIP.  We are merely observing that voice traffic is
occasionally deployed as best-effort traffic over some links in the
Internet, that we expect this occasional deployment to continue, and
that we have concerns about the lack of effective end-to-end
congestion control for this best-effort voice traffic. 

This document is a product of the IAB.

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.echo 
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  Fri Mar 26 17:18:48 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Mar 26 17:19:20 2004
Subject: [rfc-dist] RFC 3730 on Extensible Provisioning Protocol (EPP)
Message-ID: <[e-mail]>


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


        RFC 3730

        Title:      Extensible Provisioning Protocol (EPP)
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    [e-mail]
        Pages:      69
        Characters: 134337
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3730.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 is a product of the Provisioning Registry 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.echo 
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  Fri Mar 26 17:23:42 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Mar 26 17:24:21 2004
Subject: [rfc-dist] RFC 3731 on Extensible Provisioning Protocol (EPP)
	Domain Name Mapping
Message-ID: <[e-mail]>


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


        RFC 3731

        Title:      Extensible Provisioning Protocol (EPP) Domain Name
                    Mapping
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    [e-mail]
        Pages:      45
        Characters: 92527
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-domain-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3731.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 is a product of the Provisioning Registry 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.echo 
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  Fri Mar 26 17:25:28 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Mar 26 17:26:24 2004
Subject: [rfc-dist] RFC 3732 on Extensible Provisioning Protocol (EPP) Host
	Mapping
Message-ID: <[e-mail]>


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


        RFC 3732

        Title:      Extensible Provisioning Protocol (EPP) Host
                    Mapping
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    [e-mail]
        Pages:      28
        Characters: 57082
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-host-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3732.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 is a product of the Provisioning Registry 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.echo 
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  Fri Mar 26 17:33:18 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Mar 26 17:34:21 2004
Subject: [rfc-dist] RFC 3733 on Extensible Provisioning Protocol (EPP)
	Contact Mapping
Message-ID: <[e-mail]>


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


        RFC 3733

        Title:      Extensible Provisioning Protocol (EPP) Contact
                    Mapping
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    [e-mail]
        Pages:      41
        Characters: 83091
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-contact-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3733.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 is a product of the Provisioning Registry 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.echo 
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  Fri Mar 26 17:34:59 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Mar 26 17:35:52 2004
Subject: [rfc-dist] RFC 3734 on Extensible Provisioning Protocol (EPP)
	Transport Over TCP
Message-ID: <[e-mail]>


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


        RFC 3734

        Title:      Extensible Provisioning Protocol (EPP) Transport
                    Over TCP
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    [e-mail]
        Pages:      9
        Characters: 19550
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-tcp-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3734.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 is a product of the Provisioning Registry 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.echo 
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  Fri Mar 26 17:36:34 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Mar 26 17:38:06 2004
Subject: [rfc-dist] RFC 3735 on Guidelines for Extending the Extensible
	Provisioning Protocol (EPP)
Message-ID: <[e-mail]>


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


        RFC 3735

        Title:      Guidelines for Extending the Extensible
                    Provisioning Protocol (EPP)
        Author(s):  S. Hollenbeck
        Status:     Informational
        Date:       March 2004
        Mailbox:    [e-mail]
        Pages:      13
        Characters: 27326
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-ext-03.txt

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


The Extensible Provisioning Protocol (EPP) is 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 presents guidelines for use of EPP's extension mechanisms to
define new features and object management capabilities.

This document is a product of the Provisioning Registry Working Group
of the IETF.

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.echo 
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 Mar 30 16:56:19 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Mar 30 16:57:15 2004
Subject: [rfc-dist] RFC 3742 on Limited Slow-Start for TCP with Large
	Congestion Windows
Message-ID: <[e-mail]>


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


        RFC 3742

        Title:      Limited Slow-Start for TCP with Large Congestion
                    Windows
        Author(s):  S. Floyd
        Status:     Experimental
        Date:       March 2004
        Mailbox:    [e-mail]
        Pages:      7
        Characters: 14840
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-tsvwg-slowstart-00.txt

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


This document describes an optional modification for TCP's slow-start
for use with TCP connections with large congestion windows.  For TCP
connections that are able to use congestion windows of thousands (or
tens of thousands) of MSS-sized segments (for MSS the sender's MAXIMUM
SEGMENT SIZE), the current slow-start procedure can result in
increasing the congestion window by thousands of segments in a single
round-trip time.  Such an increase can easily result in thousands of
packets being dropped in one round-trip time.  This is often
counter-productive for the TCP flow itself, and is also hard on the
rest of the traffic sharing the congested link.  This note describes
Limited Slow-Start as an optional mechanism for limiting the number of
segments by which the congestion window is increased for one window of
data during slow-start, in order to improve performance for TCP
connections with large congestion windows.

This document is a product of the Transport Area 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.echo 
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 Mar 31 17:01:53 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Mar 31 17:02:31 2004
Subject: [rfc-dist] RFC 3680 on A Session Initiation Protocol (SIP) Event
	Package for Registrations
Message-ID: <[e-mail]>


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


        RFC 3680

        Title:      A Session Initiation Protocol (SIP) Event Package
                    for Registrations
        Author(s):  J. Rosenberg
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    [e-mail]
        Pages:      26
        Characters: 35403
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sipping-reg-event-00.txt

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


This document defines a Session Initiation Protocol (SIP) event
package for registrations.  Through its REGISTER method, SIP allows a
user agent to create, modify, and delete registrations.  Registrations
can also be altered by administrators in order to enforce policy.  As
a result, these registrations represent a piece of state in the
network that can change dynamically.  There are many cases where a
user agent would like to be notified of changes in this state.  This
event package defines a mechanism by which those user agents can
request and obtain such notifications.

This document is a product of the Session Initiation Proposal
Investigation 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.echo 
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 Mar 31 17:05:12 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Mar 31 17:05:36 2004
Subject: [rfc-dist] RFC 3724 on The Rise of the Middle and the Future of
	End-to-End: Reflections on the Evolution of the Internet
	Architecture
Message-ID: <[e-mail]>


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


        RFC 3724

        Title:      The Rise of the Middle and the Future of
                    End-to-End: Reflections on the Evolution of the
                    Internet Architecture
        Author(s):  J. Kempf, R. Austein, Eds., IAB
        Status:     Informational
        Date:       March 2004
        Mailbox:    [e-mail]
        Pages:      14
        Characters: 37206
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-iab-e2e-futures-05.txt

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


The end-to-end principle is the core architectural guideline of the
Internet.  In this document, we briefly examine the development of the
end-to-end principle as it has been applied to the Internet
architecture over the years.  We discuss current trends in the
evolution of the Internet architecture in relation to the end-to-end
principle, and try to draw some conclusion about the evolution of the
end-to-end principle, and thus for the Internet architecture which it
supports, in light of these current trends.

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.echo 
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 Mar 31 17:07:03 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Mar 31 17:07:32 2004
Subject: [rfc-dist] RFC 3740 on The Multicast Group Security Architecture
Message-ID: <[e-mail]>


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


        RFC 3740

        Title:      The Multicast Group Security Architecture
        Author(s):  T. Hardjono, B. Weis
        Status:     Informational
        Date:       March 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      26
        Characters: 65531
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-msec-arch-05.txt

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


This document provides an overview and rationale of the multicast
security architecture used to secure data packets of large multicast
groups.  The document begins by introducing a Multicast Security
Reference Framework, and proceeds to identify the security services
that may be part of a secure multicast solution.

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

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.echo 
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 Mar 31 17:09:38 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Mar 31 17:10:38 2004
Subject: [rfc-dist] RFC 3741 on Exclusive XML Canonicalization, Version 1.0
Message-ID: <[e-mail]>


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


        RFC 3741

        Title:      Exclusive XML Canonicalization, Version 1.0
        Author(s):  J. Boyer, D. Eastlake 3rd, J. Reagle
        Status:     Informational
        Date:       March 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      16
        Characters: 35403
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-xmldsig-xc14n-02.txt

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


Canonical XML specifies a standard serialization of XML
that, when applied to a subdocument, includes the subdocument's
ancestor context including all of the namespace declarations and
attributes in the "xml:" namespace.  However, some applications
require a method which, to the extent practical, excludes ancestor
context from a canonicalized subdocument.  For example, one might
require a digital signature over an XML payload (subdocument) in an
XML message that will not break when that subdocument is removed from
its original message and/or inserted into a different context.  This
requirement is satisfied by Exclusive XML Canonicalization.

This document is a product of the XML Digital Signatures Working Group
of the IETF.

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.echo 
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