[rfc-dist] STD 64, RFC 3550 on RTP: A Transport Protocol for Real-Time Applications

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

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


        STD 64
        RFC 3550

        Title:      RTP: A Transport Protocol for Real-Time
                    Applications
        Author(s):  H. Schulzrinne, S. Casner, R. Frederick,
                    V. Jacobson
        Status:     Standards Track
        Date:       July 2003
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail]
        Pages:      104
        Characters: 259985
        Obsoletes:  1889
        See Also:   STD 64

        I-D Tag:    draft-ietf-avt-rtp-new-12.txt

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


This memorandum describes RTP, the real-time transport protocol.  RTP
provides end-to-end network transport functions suitable for
applications transmitting real-time data, such as audio, video or
simulation data, over multicast or unicast network services.  RTP
does not address resource reservation and does not guarantee
quality-of-service for real-time services.  The data transport is
augmented by a control protocol (RTCP) to allow monitoring of the
data delivery in a manner scalable to large multicast networks, and
to provide minimal control and identification functionality.  RTP and
RTCP are designed to be independent of the underlying transport and
network layers.  The protocol supports the use of RTP-level
translators and mixers.

Most of the text in this memorandum is identical to RFC 1889 which it
obsoletes.  There are no changes in the packet formats on the wire,
only changes to the rules and algorithms governing how the protocol
is used.  The biggest change is an enhancement to the scalable timer
algorithm for calculating when to send RTCP packets in order to
minimize transmission in excess of the intended rate when many
participants join a session simultaneously.

This document is a product of the Audio/Video Transport Working Group
of the IETF.

This document has been elevated to a full 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  Thu Jun  3 14:12:57 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun  3 14:13:18 2004
Subject: [rfc-dist] STD 65,
	RFC 3551 on RTP Profile for Audio and Video Conferences
	with Minimal Control
Message-ID: <[e-mail]>


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


        STD 65
        RFC 3551

        Title:      RTP Profile for Audio and Video Conferences
                    with Minimal Control
        Author(s):  H. Schulzrinne, S. Casner
        Status:     Standards Track
        Date:       July 2003
        Mailbox:    [e-mail], [e-mail]
        Pages:      44
        Characters: 106621
        Obsoletes:  1890
        See Also:   STD 65

        I-D Tag:    draft-ietf-avt-profile-new-13.txt

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


This document describes a profile called "RTP/AVP" for the use of the
real-time transport protocol (RTP), version 2, and the associated
control protocol, RTCP, within audio and video multiparticipant
conferences with minimal control.  It provides interpretations of
generic fields within the RTP specification suitable for audio and
video conferences.  In particular, this document defines a set of
default mappings from payload type numbers to encodings.

This document also describes how audio and video data may be carried
within RTP.  It defines a set of standard encodings and their names
when used within RTP.  The descriptions provide pointers to reference
implementations and the detailed standards.  This document is meant
as an aid for implementors of audio, video and other real-time
multimedia applications.

This memorandum obsoletes RFC 1890.  It is mostly backwards-compatible
except for functions removed because two interoperable implementations
were not found.  The additions to RFC 1890 codify existing practice in
the use of payload formats under this profile and include new payload
formats defined since RFC 1890 was published.

This document is a product of the Audio/Video Transport Working Group
of the IETF.

This document has been elevated to a full 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 Jun  9 16:59:46 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:00:44 2004
Subject: [rfc-dist] RFC 3773 on High-Level Requirements for Internet Voice
	Mail
Message-ID: <[e-mail]>


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


        RFC 3773

        Title:      High-Level Requirements for Internet Voice Mail
        Author(s):  E. Candell
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail]
        Pages:      9
        Characters: 19156
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-vpim-ivm-goals-06.txt

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


This document describes the high-level requirements for Internet
Voice Mail (IVM) and establishes a baseline of desired functionality
against which proposed MIME profiles for Internet Voice Messaging
can be judged.  IVM is an extension of the Voice Profile for Internet
Mail (VPIM) version 2 designed to support interoperability
with desktop clients.  Other goals for this version of VPIM include
expanded interoperability with unified messaging systems,
conformance to Internet standards, and backward compatibility with
voice messaging systems currently running in a VPIM enabled
environment.  This document does not include goals that were met
fully by VPIM version 2.

This document is a product of the Voice Profile for Internet Mail
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 Jun  9 17:01:27 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:01:53 2004
Subject: [rfc-dist] RFC 3809 on Generic Requirements for Provider
	Provisioned Virtual Private Networks (PPVPN)
Message-ID: <[e-mail]>


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


        RFC 3809

        Title:      Generic Requirements for Provider Provisioned
                    Virtual Private Networks (PPVPN)
        Author(s):  A. Nagarajan, Ed.
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail]
        Pages:      25
        Characters: 60576
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-l3vpn-generic-reqts-03.txt

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


This document describes generic requirements for Provider Provisioned
Virtual Private Networks (PPVPN).  The requirements are categorized
into service requirements, provider requirements and engineering 
requirements.  These requirements are not specific to any particular
type of PPVPN technology, but rather apply to all PPVPN technologies.
All PPVPN technologies are expected to meet the umbrella set of
requirements described in this document.

This document is a product of the Layer 3 Virtual Private Networks
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 Jun  9 17:03:14 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:03:43 2004
Subject: [rfc-dist] RFC 3810 on Multicast Listener Discovery Version 2
	(MLDv2) for IPv6
Message-ID: <[e-mail]>


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


        RFC 3810

        Title:      Multicast Listener Discovery Version 2 (MLDv2) for
                    IPv6
        Author(s):  R. Vida, Ed., L. Costa, Ed.
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      62
        Characters: 153579
        Updates:    2710

        I-D Tag:    draft-vida-mld-v2-08.txt

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


This document updates RFC 2710, and it specifies Version 2 of the
Multicast Listener Discovery Protocol (MLDv2).  MLD is used by an
IPv6 router to discover the presence of multicast listeners on
directly attached links, and to discover which multicast addresses
are of interest to those neighboring nodes.  MLDv2 is designed to
be interoperable with MLDv1.  MLDv2 adds the ability for a node to
report interest in listening to packets with a particular multicast
address only from specific source addresses or from all sources
except for specific source addresses.

This document is the product of the Multicast & Anycast Group
Membership 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 Jun  9 17:05:03 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:05:46 2004
Subject: [rfc-dist] RFC 3816 on Definitions of Managed Objects for RObust
	Header Compression (ROHC)
Message-ID: <[e-mail]>


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


        RFC 3816

        Title:      Definitions of Managed Objects for RObust Header
                    Compression (ROHC)
        Author(s):  J. Quittek, M. Stiemerling, H. Hartenstein
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      53
        Characters: 104947
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rohc-mib-rtp-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3816.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 a set of managed objects that allow
monitoring of running instances of RObust Header Compression (ROHC).
The managed objects defined in this memo are grouped into three MIB
modules.  The ROHC-MIB module defines managed objects shared by all
ROHC profiles, the ROHC-UNCOMPRESSED-MIB module defines managed
objects specific to the ROHC uncompressed profile, the ROHC-RTP-MIB
module defines managed objects specific to the ROHC RTP (Real-Time
Transport Protocol) profile, the ROHC UDP (User Datagram Protocol)
profile, the ROHC ESP (Encapsulating Security Payload) profile, and
the ROHC LLA (Link Layer Assisted) profile.

This document is a product of the Robust Header Compression 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 Jun  9 17:17:49 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:18:44 2004
Subject: [rfc-dist] RFC 3753 on Mobility Related Terminology
Message-ID: <[e-mail]>


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


        RFC 3753

        Title:      Mobility Related Terminology
        Author(s):  J. Manner, Ed., M. Kojo, Ed.
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      36
        Characters: 74143
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-seamoby-mobility-terminology-06.txt

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


There is a need for common definitions of terminology in the work to
be done around IP mobility.  This document defines terms for mobility
related terminology.  The document originated out of work done in the
Seamoby Working Group but has broader applicability for terminology
used in IETF-wide discourse on technology for mobility and IP
networks.  Other working groups dealing with mobility may want to take
advantage of this terminology.

This document is a product of the Context Transfer and Handoff
Candidate Discovery 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 Jun  9 17:20:11 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:20:46 2004
Subject: [rfc-dist] RFC 3775 on Mobility Support in IPv6
Message-ID: <[e-mail]>


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


        RFC 3775

        Title:      Mobility Support in IPv6
        Author(s):  D. Johnson, C. Perkins, J. Arkko
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      165
        Characters: 393514
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mobileip-ipv6-24.txt

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


This document specifies a protocol which allows nodes to remain
reachable while moving around in the IPv6 Internet.  Each mobile node
is always identified by its home address, regardless of its current
point of attachment to the Internet.  While situated away from its
home, a mobile node is also associated with a care-of address, which
provides information about the mobile node's current location.  IPv6
packets addressed to a mobile node's home address are transparently
routed to its care-of address.  The protocol enables IPv6 nodes to
cache the binding of a mobile node's home address with its care-of
address, and to then send any packets destined for the mobile node
directly to it at this care-of address.  To support this operation,
Mobile IPv6 defines a new IPv6 protocol and a new destination option.
All IPv6 nodes, whether mobile or stationary, can communicate with
mobile nodes.

This document is a product of the IP Routing for Wireless/Mobile Hosts
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 Jun  9 17:21:51 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:22:51 2004
Subject: [rfc-dist] RFC 3776 on Using IPsec to Protect Mobile IPv6 Signaling
	Between Mobile Nodes and Home Agents
Message-ID: <[e-mail]>


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


        RFC 3776

        Title:      Using IPsec to Protect Mobile IPv6 Signaling
                    Between Mobile Nodes and Home Agents
        Author(s):  J. Arkko, V. Devarapalli, F. Dupont
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      40
        Characters: 87076
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mobileip-mipv6-ha-ipsec-06.txt

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


Mobile IPv6 uses IPsec to protect signaling between the home agent
and the mobile node.  Mobile IPv6 base document defines the main
requirements these nodes must follow.  This document discusses these
requirements in more depth, illustrates the used packet formats,
describes suitable configuration procedures, and shows how
implementations can process the packets in the right order.

This document is a product of the IP Routing for Wireless/Mobile Hosts
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 Jun  9 17:23:33 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:23:50 2004
Subject: [rfc-dist] RFC 3789 on Introduction to the Survey of IPv4 Addresses
	in Currently Deployed IETF Standards Track and Experimental
	Documents
Message-ID: <[e-mail]>


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


        RFC 3789

        Title:      Introduction to the Survey of IPv4 Addresses in
                    Currently Deployed IETF Standards Track and
                    Experimental Documents
        Author(s):  P. Nesser, II, A. Bergstrom, Ed.
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      10
        Characters: 22842
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-v6ops-ipv4survey-intro-06.txt

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


This document is a general overview and introduction to the v6ops IETF
workgroup project of documenting all usage of IPv4 addresses in IETF
standards track and experimental RFCs.  It is broken into seven
documents conforming to the current IETF areas.  It also describes the
methodology used during documentation, which types of RFCs
have been documented, and provides a concatenated summary of results.

This document is a product of the IPv6 Operations 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 Jun  9 17:25:20 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:26:09 2004
Subject: [rfc-dist] RFC 3790 on Survey of IPv4 Addresses in Currently
	Deployed IETF Internet Area Standards Track and Experimental
	Documents
Message-ID: <[e-mail]>


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


        RFC 3790

        Title:      Survey of IPv4 Addresses in Currently Deployed
                    IETF Internet Area Standards Track and
                    Experimental Documents
        Author(s):  C. Mickles, Ed., P. Nesser, II
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      49
        Characters: 102694
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-v6ops-ipv4survey-int-03.txt

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


This document seeks to document all usage of IPv4 addresses in
currently deployed IETF Internet Area documented standards.  In order
to successfully transition from an all IPv4 Internet to an all IPv6
Internet, many interim steps will be taken.  One of these steps is the
evolution of current protocols that have IPv4 dependencies.  It is
hoped that these protocols (and their implementations) will be
redesigned to be network address independent, but failing that will at
least dually support IPv4 and IPv6.  To this end, all Standards (Full,
Draft, and Proposed) as well as Experimental RFCs will be surveyed and
any dependencies will be documented.

This document is a product of the IPv6 Operations 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 Jun  9 17:26:47 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:27:51 2004
Subject: [rfc-dist] RFC 3791 on Survey of IPv4 Addresses in Currently
	Deployed IETF Routing Area Standards Track and Experimental
	Documents
Message-ID: <[e-mail]>


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


        RFC 3791

        Title:      Survey of IPv4 Addresses in Currently Deployed
                    IETF Routing Area Standards Track and Experimental
                    Documents
        Author(s):  C. Olvera, P. Nesser, II
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      15
        Characters: 27567
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-v6ops-ipv4survey-routing-03.txt

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


This investigation work seeks to document all usage of IPv4 addresses
in currently deployed IETF Routing Area documented standards.  In
order to successfully transition from an all IPv4 Internet to an all
IPv6 Internet, many interim steps will be taken.  One of these steps
is the evolution of current protocols that have IPv4 dependencies.  It
is hoped that these protocols (and their implementations) will be
redesigned to be network address independent, but failing that will at
least dually support IPv4 and IPv6.  To this end, all Standards (Full,
Draft, and Proposed) as well as Experimental RFCs will be surveyed and
any dependencies will be documented.

This document is a product of the IPv6 Operations 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 Jun  9 17:28:38 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:28:50 2004
Subject: [rfc-dist] RFC 3792 on Survey of IPv4 Addresses in Currently
	Deployed IETF Security Area Standards Track and Experimental
	Documents
Message-ID: <[e-mail]>


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


        RFC 3792

        Title:      Survey of IPv4 Addresses in Currently Deployed
                    IETF Security Area Standards Track and
                    Experimental Documents
        Author(s):  P. Nesser, II, A. Bergstrom, Ed.
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      25
        Characters: 46398
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-v6ops-ipv4survey-sec-04.txt

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


This document seeks to document all usage of IPv4 addresses in
currently deployed IETF Security Area documented standards.  In order
to successfully transition from an all IPv4 Internet to an all IPv6
Internet, many interim steps will be taken.  One of these steps is the
evolution of current protocols that have IPv4 dependencies.  It is
hoped that these protocols (and their implementations) will be
redesigned to be network address independent, but failing that will at
least dually support IPv4 and IPv6.  To this end, all Standards (Full,
Draft, and Proposed) as well as Experimental RFCs will be surveyed and
any dependencies will be documented. 

This document is a product of the IPv6 Operations 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 Jun  9 17:30:15 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:30:49 2004
Subject: [rfc-dist] RFC 3793 on Survey of IPv4 Addresses in Currently
	Deployed IETF Sub-IP Area Standards Track and Experimental Documents
Message-ID: <[e-mail]>


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


        RFC 3793

        Title:      Survey of IPv4 Addresses in Currently Deployed
                    IETF Sub-IP Area Standards Track and Experimental
                    Documents
        Author(s):  P. Nesser, II, A. Bergstrom, Ed.
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      6
        Characters: 11624
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-v6ops-ipv4survey-subip-04.txt

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


This document seeks to document all usage of IPv4 addresses in
currently deployed IETF Sub-IP Area documented standards.  In order to
successfully transition from an all IPv4 Internet to an all IPv6
Internet, many interim steps will be taken.  One of these steps is the
evolution of current protocols that have IPv4 dependencies.  It is
hoped that these protocols (and their implementations) will be
redesigned to be network address independent, but failing that will at
least dually support IPv4 and IPv6.  To this end, all Standards (Full,
Draft, and Proposed) as well as Experimental RFCs will be surveyed and
any dependencies will be documented.

This document is a product of the IPv6 Operations 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 Jun  9 17:32:15 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:32:45 2004
Subject: [rfc-dist] RFC 3794 on Survey of IPv4 Addresses in Currently
	Deployed IETF Transport Area Standards Track and Experimental
	Documents
Message-ID: <[e-mail]>


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


        RFC 3794

        Title:      Survey of IPv4 Addresses in Currently Deployed
                    IETF Transport Area Standards Track and
                    Experimental Documents
        Author(s):  P. Nesser, II, A. Bergstrom, Ed.
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      31
        Characters: 60001
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-v6ops-ipv4survey-trans-05.txt

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


This document seeks to document all usage of IPv4 addresses in
currently deployed IETF Transport Area documented standards.  In order
to successfully transition from an all IPv4 Internet to an all IPv6 
Internet, many interim steps will be taken.  One of these steps is the
evolution of current protocols that have IPv4 dependencies.  It is
hoped that these protocols (and their implementations) will be
redesigned to be network address independent, but failing that will at
least dually support IPv4 and IPv6.  To this end, all Standards (Full,
Draft, and Proposed) as well as Experimental RFCs will be surveyed and
any dependencies will be documented.

This document is a product of the IPv6 Operations 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 Jun  9 17:33:55 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:35:46 2004
Subject: [rfc-dist] RFC 3795 on Survey of IPv4 Addresses in Currently
	Deployed IETF Application Area Standards Track and
	Experimental Documents
Message-ID: <[e-mail]>


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


        RFC 3795

        Title:      Survey of IPv4 Addresses in Currently Deployed
                    IETF Application Area Standards Track and
                    Experimental Documents
        Author(s):  R. Sofia, P. Nesser, II
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      50
        Characters: 92584
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-v6ops-ipv4survey-apps-04.txt

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


This document describes IPv4 addressing dependencies in an attempt to
clarify the necessary steps in re-designing and re-implementing
specifications to become network address independent, or at least, to
dually support IPv4 and IPv6.  This transition requires several
interim steps, one of them being the evolution of current IPv4
dependent specifications to a format independent of the type of IP
addressing schema used.  Hence, it is hoped that specifications will
be re-designed and re-implemented to become network address
independent, or at least to dually support IPv4 and IPv6.

To achieve that step, it is necessary to survey and document all IPv4
dependencies experienced by current standards (Full, Draft, and
Proposed) as well as Experimental RFCs.  Hence, this document
describes IPv4 addressing dependencies that deployed IETF Application
Area documented Standards may experience.

This document is a product of the IPv6 Operations 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 Jun  9 17:35:48 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:36:51 2004
Subject: [rfc-dist] RFC 3796 on Survey of IPv4 Addresses in Currently
	Deployed IETF Operations & Management Area Standards Track
	and Experimental Documents
Message-ID: <[e-mail]>


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


        RFC 3796

        Title:      Survey of IPv4 Addresses in Currently Deployed
                    IETF Operations & Management Area Standards Track
                    and Experimental Documents
        Author(s):  P. Nesser, II, A. Bergstrom, Ed.
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      43
        Characters: 78400
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-v6ops-ipv4survey-ops-05.txt

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


This document seeks to record all usage of IPv4 addresses in currently
deployed IETF Operations & Management Area accepted standards.  In
order to successfully transition from an all IPv4 Internet to an all
IPv6 Internet, many interim steps will be taken.  One of these steps
is the evolution of current protocols that have IPv4 dependencies.  It
is hoped that these protocols (and their implementations) will be
redesigned to be network address independent, but failing that will at
least dually support IPv4 and IPv6.  To this end, all Standards (Full,
Draft, and Proposed), as well as Experimental RFCs, will be surveyed
and any dependencies will be documented.

This document is a product of the IPv6 Operations 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 Jun  9 17:59:12 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun  9 17:59:59 2004
Subject: [rfc-dist] RFC 3753 on Mobility Related Terminology
Message-ID: <[e-mail]>


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


        RFC 3753

        Title:      Mobility Related Terminology
        Author(s):  J. Manner, Ed., M. Kojo, Ed.
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      36
        Characters: 74143
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-seamoby-mobility-terminology-06.txt

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


There is a need for common definitions of terminology in the work to
be done around IP mobility.  This document defines terms for mobility
related terminology.  The document originated out of work done in the
Seamoby Working Group but has broader applicability for terminology
used in IETF-wide discourse on technology for mobility and IP
networks.  Other working groups dealing with mobility may want to take
advantage of this terminology.

This document is a product of the Context Transfer and Handoff
Candidate Discovery 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 Jun 16 13:30:21 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun 16 13:31:16 2004
Subject: [rfc-dist] 
	BCP 10, RFC 3777 on IAB and IESG Selection, Confirmation,
	and Recall Process: Operation of the Nominating and
	Recall Committees
Message-ID: <[e-mail]>


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


        BCP 10
        RFC 3777

        Title:      IAB and IESG Selection, Confirmation, and Recall
                    Process: Operation of the Nominating and Recall
                    Committees
        Author(s):  J. Galvin, Ed.
        Status:     Best Current Practice
        Date:       June 2004
        Mailbox:    [e-mail]
        Pages:      34
        Characters: 76395
        Obsoletes:  2727
        SeeAlso:    BCP 10

        I-D Tag:    draft-ietf-nomcom-rfc2727bis-09.txt

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


The process by which the members of the IAB and IESG are selected,
confirmed, and recalled is specified.  This document is a
self-consistent, organized compilation of the process as it was known
at the time of publication.

This document is a product of the Operation of the IESG/IAB
Nominating and Recall Committees Working Group of the IETF.

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  Wed Jun 16 13:32:35 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun 16 13:34:27 2004
Subject: [rfc-dist] RFC 3805 on Printer MIB v2
Message-ID: <[e-mail]>


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


        RFC 3805

        Title:      Printer MIB v2
        Author(s):  R. Bergman, H. Lewis, I. McDonald
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail],
        Pages:      171
        Characters: 366952
        Obsoletes:  1759

        I-D Tag:    draft-ietf-printmib-mib-info-15.txt

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


This document provides definitions of models and manageable objects
for printing environments.  The objects included in this MIB apply to
physical, as well as logical entities within a printing device.  This
document obsoletes RFC 1759.

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 Jun 16 13:33:56 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun 16 13:35:49 2004
Subject: [rfc-dist] RFC 3806 on Printer Finishing MIB
Message-ID: <[e-mail]>


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


        RFC 3806

        Title:      Printer Finishing MIB
        Author(s):  R. Bergman, H. Lewis, I. McDonald
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      53
        Characters: 109654
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-printmib-finishing-16.txt

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


This document defines a MIB module for the management of printer
finishing device subunits.  The finishing device subunits applicable
to this MIB are an integral part of the Printer System.  This MIB
applies only to a Finisher Device that is connected to a Printer
System.

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 Jun 16 13:35:16 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun 16 13:37:09 2004
Subject: [rfc-dist] RFC 3808 on IANA Charset MIB
Message-ID: <[e-mail]>


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


        RFC 3808

        Title:      IANA Charset MIB
        Author(s):  I. McDonald
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail]
        Pages:      14
        Characters: 25245
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-mcdonald-iana-charset-mib-02.txt

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


This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet
community.  This IANA Charset MIB is now an IANA registry.  In
particular, a single textual convention 'IANACharset' is defined that
may be used to specify charset labels in MIB objects.  'IANACharset'
was extracted from Printer MIB v2 (RFC 3805).  'IANACharset' was
originally defined (and mis-named) as 'CodedCharSet' in Printer MIB
v1 (RFC 1759).  A tool has been written in C, that may be used by IANA
to regenerate this IANA Charset MIB, when future charsets are
registered in accordance with the IANA Charset Registration Procedures
(RFC 2978).

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 Jun 16 13:37:36 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun 16 13:38:30 2004
Subject: [rfc-dist] RFC 3811 on Definitions of Textual Conventions (TCs) for
	Multiprotocol Label Switching (MPLS) Management
Message-ID: <[e-mail]>


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


        RFC 3811

        Title:      Definitions of Textual Conventions (TCs) for
                    Multiprotocol Label Switching (MPLS) Management
        Author(s):  T. Nadeau, Ed., J. Cucchiara, Ed.
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      20
        Characters: 40353
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mpls-tc-mib-10.txt

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


This memo defines a Management Information Base (MIB) module which
contains Textual Conventions to represent commonly used Multiprotocol
Label Switching (MPLS) management information.  The intent is that
these TEXTUAL CONVENTIONS (TCs) will be imported and used in MPLS
related MIB modules that would otherwise define their own
representations.

This document is a product of the Multiprotocol Label Switching
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  Thu Jun 17 16:04:32 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun 17 16:05:23 2004
Subject: [rfc-dist] RFC 3779 on X.509 Extensions for IP Addresses and AS
	Identifiers
Message-ID: <[e-mail]>


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


        RFC 3779

        Title:      X.509 Extensions for IP Addresses and AS
                    Identifiers
        Author(s):  C. Lynn, S. Kent, K. Seo
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail], [e-mail]
        Pages:      27
        Characters: 60732
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-pkix-x509-ipaddr-as-extn-03.txt

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


This document defines two X.509 v3 certificate extensions.  The first
binds a list of IP address blocks, or prefixes, to the subject of a
certificate.  The second binds a list of autonomous system
identifiers to the subject of a certificate.  These extensions may be
used to convey the authorization of the subject to use the IP
addresses and autonomous system identifiers contained in the
extensions.

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  Thu Jun 17 16:07:04 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun 17 16:07:13 2004
Subject: [rfc-dist] RFC 3788 on Security Considerations for Signaling
	Transport (SIGTRAN) Protocols
Message-ID: <[e-mail]>


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


        RFC 3788

        Title:      Security Considerations for
                    Signaling Transport (SIGTRAN) Protocols
        Author(s):  J. Loughney, M. Tuexen, Ed., J. Pastor-Balbas
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      13
        Characters: 27125
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sigtran-security-03.txt

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


This document discusses how Transport Layer Security (TLS) and IPsec
can be used to secure communication for SIGTRAN protocols.  The main
goal is to recommend the minimum security means that a SIGTRAN node
must implement in order to attain secured communication.  The support
of IPsec is mandatory for all nodes running SIGTRAN protocols.  TLS
support is optional. 

This document is a product of the Signaling Transport 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  Thu Jun 17 16:09:02 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun 17 16:09:54 2004
Subject: [rfc-dist] RFC 3797 on Publicly Verifiable Nominations Committee
	(NomCom) Random Selection
Message-ID: <[e-mail]>


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


        RFC 3797

        Title:      Publicly Verifiable Nominations Committee (NomCom)
                    Random Selection
        Author(s):  D. Eastlake 3rd
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail]
        Pages:      19
        Characters: 39883
        Obsoletes:  2777

        I-D Tag:    draft-eastlake-rfc2777bis-selection-04.txt

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


This document describes a method for making random selections in such
a way that the unbiased nature of the choice is publicly verifiable.
As an example, the selection of the voting members of the IETF 
Nominations Committee (NomCom) from the pool of eligible volunteers is
used.  Similar techniques would be applicable to other cases.

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  Thu Jun 17 16:11:07 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun 17 16:12:13 2004
Subject: [rfc-dist] RFC 3807 on V5.2-User Adaptation Layer (V5UA)
Message-ID: <[e-mail]>


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


        RFC 3807

        Title:      V5.2-User Adaptation Layer (V5UA)
        Author(s):  E. Weilandt, N. Khanchandani, S. Rao
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail],
                    [e-mail],
                    [e-mail]
        Pages:      24
        Characters: 49748
        Updates:    3057

        I-D Tag:    draft-ietf-sigtran-v5ua-04.txt

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


This document defines a mechanism for the backhauling of V5.2 messages
over IP using the Stream Control Transmission Protocol (SCTP).  This
protocol may be used between a Signaling Gateway (SG) and a Media
Gateway controller (MGC).  It is assumed that the SG receives V5.2
signaling over a standard V5.2 interface.

This document builds on the ISDN User Adaptation Layer Protocol
(RFC 3057).  It defines all necessary extensions to the IUA Protocol
needed for the V5UA protocol implementation.

This document is a product of the Signaling Transport Working Group
of the IETF.

This is now a Proposed Protocol Standard.

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  Thu Jun 17 16:13:00 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun 17 16:13:43 2004
Subject: [rfc-dist] RFC 3826 on The Advanced Encryption Standard (AES)
	Cipher Algorithm in the SNMP User-based Security Model
Message-ID: <[e-mail]>


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


        RFC 3826

        Title:      The Advanced Encryption Standard (AES) Cipher
                    Algorithm in the SNMP User-based Security Model
        Author(s):  U. Blumenthal, F. Maino, K. McCloghrie
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      16
        Characters: 32821
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-blumenthal-aes-usm-08.txt

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


This document describes a symmetric encryption protocol that
supplements the protocols described in the User-based Security Model
(USM), which is a Security Subsystem for version 3 of the Simple
Network Management Protocol for use in the SNMP Architecture.  The
symmetric encryption protocol described in this document is based on
the Advanced Encryption Standard (AES) cipher algorithm used in Cipher
FeedBack Mode (CFB), with a key size of 128 bits.

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  Thu Jun 17 16:15:56 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun 17 16:16:12 2004
Subject: [rfc-dist] RFC 3827 on Additional Snoop Datalink Types
Message-ID: <[e-mail]>


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


        RFC 3827

        Title:      Additional Snoop Datalink Types
        Author(s):  K. Sarcar
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail]
        Pages:      4
        Characters: 6344
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-sarcar-snoop-new-types-01.txt

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


The snoop file format provides a way to store and exchange
datalink layer packet traces.  This document describes extensions
to this file format to support new media.

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  Mon Jun 21 11:53:22 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jun 21 11:54:29 2004
Subject: [rfc-dist] RFC 3748 on Extensible Authentication Protocol (EAP)
Message-ID: <[e-mail]>


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


        RFC 3748

        Title:      Extensible Authentication Protocol (EAP)
        Author(s):  B. Aboba, L. Blunk, J. Vollbrecht, J. Carlson,
                    H. Levkowetz, Ed.
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail]
        Pages:      67
        Characters: 157994
        Obsoletes:  2284

        I-D Tag:    draft-ietf-eap-rfc2284bis-09.txt

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


This document defines the Extensible Authentication Protocol (EAP),
an authentication framework which supports multiple authentication
methods.  EAP typically runs directly over data link layers such as
Point-to-Point Protocol (PPP) or IEEE 802, without requiring IP.  EAP
provides its own support for duplicate elimination and retransmission,
but is reliant on lower layer ordering guarantees.  Fragmentation is
not supported within EAP itself; however, individual EAP methods may
support this.

This document obsoletes RFC 2284.  A summary of the changes between
this document and RFC 2284 is available in Appendix A.

This document is a product of the Extensible Authentication 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  Mon Jun 21 11:57:10 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jun 21 11:57:31 2004
Subject: [rfc-dist] RFC 3769 on Requirements for IPv6 Prefix Delegation
Message-ID: <[e-mail]>


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


        RFC 3769

        Title:      Requirements for IPv6 Prefix Delegation
        Author(s):  S. Miyakawa, R. Droms
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      6
        Characters: 10287
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipv6-prefix-delegation-requirement-04.txt

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


This document describes requirements for how IPv6 address prefixes
should be delegated to an IPv6 subscriber's network (or "site").

This document is a product of the IP Version 6 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  Mon Jun 21 11:55:37 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jun 21 11:57:34 2004
Subject: [rfc-dist] RFC 3767 on Securely Available Credentials Protocol
Message-ID: <[e-mail]>


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


        RFC 3767

        Title:      Securely Available Credentials Protocol
        Author(s):  S. Farrell, Ed.
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail]
        Pages:      25
        Characters: 49552
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sacred-protocol-bss-09.txt

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


This document describes a protocol whereby a user can acquire
cryptographic credentials (e.g., private keys, PKCS #15 structures)
from a credential server, using a workstation that has locally
trusted software installed, but with no user-specific
configuration.  The protocol's payloads are described in XML.  This
memo also specifies a Blocks Extensible Exchange Protocol (BEEP)
profile of the protocol.  Security requirements are  met by mandating
support for TLS and/or DIGEST-MD5 (through BEEP). 

This document is a product of the Securely Available Credentials
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  Mon Jun 21 11:59:02 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jun 21 11:59:37 2004
Subject: [rfc-dist] RFC 3784 on Intermediate System to Intermediate System
	(IS-IS) Extensions for Traffic Engineering (TE)
Message-ID: <[e-mail]>


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


        RFC 3784

        Title:      Intermediate System to Intermediate System (IS-IS)
                    Extensions for Traffic Engineering (TE)
        Author(s):  H. Smit, T. Li
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      13
        Characters: 27422
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-isis-traffic-05.txt

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


This document describes extensions to the Intermediate System to
Intermediate System (IS-IS) protocol to support Traffic Engineering
(TE).  This document extends the IS-IS protocol by specifying new
information that an Intermediate System (router) can place in Link
State Protocol (LSP) Data Units.  This information describes
additional details regarding the state of the network that are useful
for traffic engineering computations.

This document is a product of the IS-IS for IP Internets 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  Mon Jun 21 12:00:51 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jun 21 12:01:27 2004
Subject: [rfc-dist] RFC 3812 on Multiprotocol Label Switching (MPLS) Traffic
	Engineering (TE) Management Information Base (MIB)
Message-ID: <[e-mail]>


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


        RFC 3812

        Title:      Multiprotocol Label Switching (MPLS) Traffic
                    Engineering (TE) Management Information Base (MIB)
        Author(s):  C. Srinivasan, A. Viswanathan, T. Nadeau
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      68
        Characters: 136475
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mpls-te-mib-14.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3812.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 Multiprotocol Label Switching (MPLS)
based traffic engineering (TE).

This document is a product of the Multiprotocol Label Switching
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  Mon Jun 21 12:02:30 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jun 21 12:03:34 2004
Subject: [rfc-dist] RFC 3813 on Multiprotocol Label Switching (MPLS) Label
	Switching Router (LSR) Management Information Base (MIB)
Message-ID: <[e-mail]>


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


        RFC 3813

        Title:      Multiprotocol Label Switching (MPLS) Label
                    Switching Router (LSR) Management Information Base
                    (MIB)
        Author(s):  C. Srinivasan, A. Viswanathan, T. Nadeau
        Status:     Standard Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      60
        Characters: 116120
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mpls-lsr-mib-14.txt

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


This memo defines an portion of the Management
Information Base (MIB) for use with network management protocols
in the Internet community.  In particular, it describes managed
objects to configure and/or monitor a Multiprotocol Label
Switching (MPLS) Label Switching Router (LSR).

This document is a product of the Multiprotocol Label Switching
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  Mon Jun 21 12:04:33 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jun 21 12:05:42 2004
Subject: [rfc-dist] RFC 3814 on Multiprotocol Label Switching (MPLS)
	Forwarding Equivalence Class To Next Hop Label Forwarding
	Entry (FEC-To-NHLFE) Management Information Base (MIB)
Message-ID: <[e-mail]>


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


        RFC 3814

        Title:      Multiprotocol Label Switching (MPLS) Forwarding
                    Equivalence Class To Next Hop Label Forwarding
                    Entry (FEC-To-NHLFE) Management Information Base
                    (MIB)
        Author(s):  T. Nadeau, C. Srinivasan, A. Viswanathan
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      42
        Characters: 87518
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mpls-ftn-mib-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3814.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 defining, configuring,
and monitoring Forwarding Equivalence Class (FEC) to Next Hop Label
Forwarding Entry (NHLFE) mappings and corresponding actions for use
with Multiprotocol Label Switching (MPLS).

This document is a product of the Multiprotocol Label Switching
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  Mon Jun 21 12:06:31 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jun 21 12:07:37 2004
Subject: [rfc-dist] RFC 3815 on Definitions of Managed Objects for the
	Multiprotocol Label Switching (MPLS),
	Label Distribution Protocol (LDP)
Message-ID: <[e-mail]>


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


        RFC 3815

        Title:      Definitions of Managed Objects for the
                    Multiprotocol Label Switching (MPLS),
                    Label Distribution Protocol (LDP)
        Author(s):  J. Cucchiara, H. Sjostrand, J. Luciani
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      106
        Characters: 215916
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mpls-ldp-mib-14.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3815.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 the Multiprotocol
Label Switching, Label Distribution Protocol (LDP).

This document is a product of the Multiprotocol Label Switching
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  Mon Jun 21 12:08:06 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jun 21 12:08:35 2004
Subject: [rfc-dist] RFC 3817 on Layer 2 Tunneling Protocol (L2TP) Active
	Discovery Relay for PPP over Ethernet (PPPoE)
Message-ID: <[e-mail]>


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


        RFC 3817

        Title:      Layer 2 Tunneling Protocol (L2TP) Active Discovery
                    Relay for PPP over Ethernet (PPPoE)
        Author(s):  W. Townsley, R. da Silva
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      17
        Characters: 37765
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-dasilva-l2tp-relaysvc-08.txt

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


The Point-to-Point Protocol (PPP) provides a standard method for
transporting multi-protocol datagrams over point-to-point links.
Layer Two Tunneling Protocol (L2TP), facilitates the tunneling of PPP
packets across an intervening packet-switched network.  And yet a
third protocol, PPP over Ethernet (PPPoE) describes how to build PPP
sessions and to encapsulate PPP packets over Ethernet.

L2TP Active Discovery Relay for PPPoE describes a method to relay
Active Discovery and Service Selection functionality from PPPoE over
the reliable control channel within L2TP.  Two new L2TP control
message types and associated PPPoE-specific Attribute Value Pairs
(AVPs) for L2TP are defined.  This relay mechanism provides enhanced
integration of a specific feature in the PPPoE tunneling protocol
with L2TP.

This document is a product of the Layer Two Tunneling Protocol
Extensions 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  Mon Jun 21 12:09:43 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Jun 21 12:10:30 2004
Subject: [rfc-dist] BCP 88,
	RFC 3818 on IANA Considerations for the Point-to-Point
	Protocol (PPP)
Message-ID: <[e-mail]>


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


        BCP 88
        RFC 3818

        Title:      IANA Considerations for the Point-to-Point
                    Protocol (PPP)
        Author(s):  V. Schryver
        Status:     Best Current Practice
        Date:       June 2004
        Mailbox:    [e-mail]
        Pages:      4
        Characters: 6321
        SeeAlso:    BCP 88

        I-D Tag:    draft-schryver-pppext-iana-01.txt

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


The charter of the Point-to-Point Protocol (PPP) Extensions working
group (pppext) includes the responsibility to "actively advance PPP's
most useful extensions to full standard, while defending against
further enhancements of questionable value."  In support of that
charter, the allocation of PPP protocol and other assigned numbers
will no longer be "first come first served."

This document is a product of the Point-to-Point Protocol Extensions
Working Group of the IETF. 

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  Thu Jun 24 14:22:22 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun 24 14:22:43 2004
Subject: [rfc-dist] RFC 3801 on Voice Profile for Internet Mail - version 2
	(VPIMv2)
Message-ID: <[e-mail]>


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


        RFC 3801

        Title:      Voice Profile for Internet Mail - version 2
                    (VPIMv2)
        Author(s):  G. Vaudreuil, G. Parsons
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      55
        Characters: 118122
        Obsoletes:  2421

        I-D Tag:    draft-ietf-vpim-vpimv2r2-05.txt

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


This document specifies a restricted profile of the Internet
multimedia messaging protocols for use between voice processing server
platforms.  The profile is referred to as the Voice Profile for
Internet Mail (VPIM) in this document.  These platforms have
historically been special-purpose computers and often do not have the
same facilities normally associated with a traditional Internet
Email-capable computer.  As a result, VPIM also specifies additional
functionality, as it is needed.  This profile is intended to specify
the minimum common set of features to allow interworking between
conforming systems.

This document obsoletes RFC 2421 and describes version 2 of the
profile with greater precision.  No protocol changes were made in this
revision.  A list of changes from RFC 2421 are noted in Appendix F.
Appendix A summarizes the protocol profiles of this version of VPIM.

This document is a product of the Voice Profile for Internet Mail
Working Group of the IETF.

This is now a Draft 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  Thu Jun 24 14:23:59 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun 24 14:24:45 2004
Subject: [rfc-dist] RFC 3802 on Toll Quality Voice - 32 kbit/s Adaptive
	Differential Pulse Code Modulation (ADPCM) MIME Sub-type
	Registration
Message-ID: <[e-mail]>


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


        RFC 3802

        Title:      Toll Quality Voice - 32 kbit/s Adaptive
                    Differential Pulse Code Modulation (ADPCM) MIME
                    Sub-type Registration
        Author(s):  G. Vaudreuil, G. Parsons
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      7
        Characters: 11686
        Obsoletes:  2422

        I-D Tag:    draft-ietf-vpim-vpimv2r2-32k-03.txt

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


This document describes the registration of the MIME sub-type
audio/32KADPCM Adaptive Differential Pulse Code Modulation for
toll quality audio.  This audio encoding is defined by the ITU-T
in Recommendation G.726.

This document is a product of the Voice Profile for Internet Mail
Working Group of the IETF.

This is now a Draft 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  Thu Jun 24 14:25:49 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun 24 14:26:43 2004
Subject: [rfc-dist] RFC 3803 on Content Duration MIME Header Definition
Message-ID: <[e-mail]>


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


        RFC 3803

        Title:      Content Duration MIME Header Definition
        Author(s):  G. Vaudreuil, G. Parsons
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      5
        Characters: 8213
        Obsoletes:  2424

        I-D Tag:    draft-ietf-vpim-vpimv2r2-dur-03.txt

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


This document describes the MIME header Content-Duration that is
intended for use with any time varying media content (typically
audio/* or video/*).

This document is a product of the Voice Profile for Internet Mail
Working Group of the IETF.

This is now a Draft 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  Thu Jun 24 14:27:43 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun 24 14:29:00 2004
Subject: [rfc-dist] RFC 3804 on Voice Profile for Internet Mail (VPIM)
	Addressing
Message-ID: <[e-mail]>


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


        RFC 3804

        Title:      Voice Profile for Internet Mail (VPIM) Addressing
        Author(s):  G. Parsons
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail]
        Pages:      15
        Characters: 26122
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-vpim-address-03.txt

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


This document lists the various Voice Profile for Internet Mail (VPIM)
email address formats that are currently in common use and defines
several new address formats for special case usage.   Requirements are
imposed on the formats of addresses used in VPIM submission mode.

This documenet is a product of the Voice Profile for Internet Mail
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  Thu Jun 24 14:28:59 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jun 24 14:30:34 2004
Subject: [rfc-dist] RFC 3823 on MIME Media Type for the Systems Biology
	Markup Language (SBML)
Message-ID: <[e-mail]>


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


        RFC 3823

        Title:      MIME Media Type for the Systems Biology Markup
                    Language (SBML)
        Author(s):  B. Kovitz
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail]
        Pages:      8
        Characters: 14577
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-sbml-media-type-02.txt

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


This document registers the MIME sub-type application/sbml+xml, a
media type for SBML, the Systems Biology Markup Language.  SBML is
defined by The SBML Team at the California Institute of Technology
and interested members of the systems biology community.

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 Jun 29 16:17:29 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Jun 29 16:18:07 2004
Subject: [rfc-dist] RFC 3824 on Using E.164 numbers with the Session
	Initiation Protocol (SIP)
Message-ID: <[e-mail]>


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


        RFC 3824

        Title:      Using E.164 numbers with the Session Initiation
                    Protocol (SIP)
        Author(s):  J. Peterson, H. Liu, J. Yu, B. Campbell
        Status:     Informational
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail]
        Pages:      16
        Characters: 36535
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sipping-e164-04.txt

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


There are a number of contexts in which telephone numbers are
employed by Session Initiation Protocol (SIP) applications, many of
which can be addressed by ENUM.  Although SIP was one of the primary
applications for which ENUM was created, there is nevertheless a need
to define procedures for integrating ENUM with SIP
implementations.  This document illustrates how the two protocols
might work in concert, and clarifies the authoring and processing of
ENUM records for SIP applications.  It also provides guidelines for 
instances in which ENUM, for whatever reason, cannot be used to
resolve a telephone number.

This document is a product of the Session Initiation Proposal
Investigation 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 Jun 30 16:24:32 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun 30 16:25:05 2004
Subject: [rfc-dist] RFC 3820 on Internet X.509 Public Key Infrastructure
	(PKI) Proxy Certificate Profile
Message-ID: <[e-mail]>


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


        RFC 3820

        Title:      Internet X.509 Public Key Infrastructure (PKI)
                    Proxy Certificate Profile
        Author(s):  S. Tuecke, V. Welch, D. Engert, L. Pearlman
                    M. Thompson
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail]
        Pages:      37
        Characters: 86374
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-pkix-proxy-10.txt

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


This document forms a certificate profile for Proxy Certificates,
based on X.509 Public Key Infrastructure (PKI) certificates as
defined in RFC 3280, for use in the Internet.  The term Proxy
Certificate is used to describe a certificate that is derived from,
and signed by, a normal X.509 Public Key End Entity Certificate or
by another Proxy Certificate for the purpose of providing
restricted proxying and delegation within a PKI based
authentication system.

This document is a product of the Public-Key Infrastructure (C.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  Wed Jun 30 16:26:08 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun 30 16:27:02 2004
Subject: [rfc-dist] RFC 3843 on RObust Header Compression (ROHC): A
	Compression Profile for IP
Message-ID: <[e-mail]>


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


        RFC 3843

        Title:      RObust Header Compression (ROHC):
                    A Compression Profile for IP
        Author(s):  L-E. Jonsson, G. Pelletier
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail],
                    [e-mail]
        Pages:      16
        Characters: 33549
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rohc-ip-only-05.txt

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


The original RObust Header Compression (ROHC) RFC (RFC 3095) defines
a framework for header compression, along with compression protocols
(profiles) for IP/UDP/RTP, IP/ESP (Encapsulating Security Payload),
IP/UDP, and also a profile for uncompressed packet streams.  However,
no profile was defined for compression of IP only, which has been
identified as a missing piece in RFC 3095.  This document defines a
ROHC compression profile for IP, similar to the IP/UDP profile defined
by RFC 3095, but simplified to exclude UDP, and enhanced to compress
IP header chains of arbitrary length.

This document is a product of the Robust Header Compression 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 Jun 30 16:27:51 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jun 30 16:28:20 2004
Subject: [rfc-dist] RFC 3846 on Mobile IPv4 Extension for Carrying Network
	Access Identifiers
Message-ID: <[e-mail]>


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


        RFC 3846

        Title:      Mobile IPv4 Extension for Carrying Network Access
                    Identifiers
        Author(s):  F. Johansson, T. Johansson
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    [e-mail],
                    [e-mail]
        Pages:      8
        Characters: 16834
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mip4-aaa-nai-02.txt

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


When a mobile node moves between two foreign networks, it has to be
re-authenticated.  If the home network has both multiple
Authentication Authorization and Accounting (AAA) servers and Home
Agents (HAs) in use, the Home AAA server may not have sufficient
information to process the re-authentication correctly (i.e., to
ensure that the same HA continues to be used).  This document defines
a Mobile IP extension that carries identities for the Home AAA and HA
servers in the form of Network Access Identifiers (NAIs).  The
extension allows a Home Agent to pass its identity (and that of the
Home AAA server) to the mobile node, which can then pass it on to the
local AAA server when changing its point of attachment.  This
extension may also be used in other situations requiring
communication of a NAI between Mobile IP nodes.

This document is a product of the Mobility for IPv4 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