[rfc-dist] RFC 3825 on Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information

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

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


        RFC 3825

        Title:      Dynamic Host Configuration Protocol Option for
                    Coordinate-based Location Configuration
                    Information
        Author(s):  J. Polk, J. Schnizlein, M. Linsner
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      15
        Characters: 31715
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-geopriv-dhcp-lci-option-03.txt

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


This document specifies a Dynamic Host Configuration Protocol Option
for the coordinate-based geographic location of the client.  The
Location Configuration Information (LCI) includes latitude,
longitude, and altitude, with resolution indicators for each.  The
reference datum for these values is also included.

This document is a product of the Geographic Location/Privacy 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 Jul  8 14:40:22 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jul  8 14:41:04 2004
Subject: [rfc-dist] RFC 3829 on Lightweight Directory Access Protocol (LDAP)
	Authorization Identity Request and Response Controls
Message-ID: <[e-mail]>


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


        RFC 3829

        Title:      Lightweight Directory Access Protocol (LDAP)
                    Authorization Identity Request and Response
                    Controls
        Author(s):  R. Weltman, M. Smith, M. Wahl
        Status:     Informational
        Date:       July 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      6
        Characters: 11986
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-weltman-ldapv3-auth-response-09.txt

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


This document extends the Lightweight Directory Access Protocol
(LDAP) bind operation with a mechanism for requesting and returning
the authorization identity it establishes.  Specifically, this
document defines the Authorization Identity Request and Response
controls for use with the Bind operation.

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 Jul  8 14:42:14 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jul  8 14:42:37 2004
Subject: [rfc-dist] RFC 3847 on Restart Signaling for Intermediate System to
	Intermediate System (IS-IS)
Message-ID: <[e-mail]>


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


        RFC 3847

        Title:      Restart Signaling for
                    Intermediate System to Intermediate System (IS-IS)
        Author(s):  M. Shand, L. Ginsberg
        Status:     Informational
        Date:       July 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      21
        Characters: 50023
        Updates/Obsoletes/SeeAlso:    None

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

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


This document describes a mechanism for a restarting router to signal
to its neighbors that it is restarting, allowing them to
reestablish their adjacencies without cycling through the down
state, while still correctly initiating database synchronization.

This document additionally describes a mechanism for a restarting
router to determine when it has achieved LSP database
synchronization with its neighbors and a mechanism to optimize LSP
database synchronization, while minimizing transient routing
disruption when a router starts. 

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  Tue Jul 13 13:45:25 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Jul 13 13:45:49 2004
Subject: [rfc-dist] BCP 89,
	RFC 3819 on Advice for Internet Subnetwork Designers
Message-ID: <[e-mail]>


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


        BCP 89
        RFC 3819

        Title:      Advice for Internet Subnetwork Designers
        Author(s):  P. Karn, Ed., C. Bormann, G. Fairhurst,
                    D. Grossman, R. Ludwig, J. Mahdavi, G. Montenegro,
                    J. Touch, L. Wood
        Status:     Best Current Practice
        Date:       July 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail]
        Pages:      60
        Characters: 152174
        SeeAlso:    BCP 89

        I-D Tag:    draft-ietf-pilc-link-design-15.txt

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


This document provides advice to the designers of digital
communication equipment, link-layer protocols, and packet-switched
local networks (collectively referred to as subnetworks), who wish to
support the Internet protocols but may be unfamiliar with the
Internet architecture and the implications of their design choices on
the performance and efficiency of the Internet.

This document is a product of the Performance Implications of Link
Characteristics 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  Tue Jul 13 13:48:55 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Jul 13 13:49:53 2004
Subject: [rfc-dist] RFC 3828 on The Lightweight User Datagram Protocol
	(UDP-Lite)
Message-ID: <[e-mail]>


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


        RFC 3828

        Title:      The Lightweight User Datagram Protocol (UDP-Lite)
        Author(s):  L-A. Larzon, M. Degermark, S. Pink,
                    L-E. Jonsson, Ed., G. Fairhurst, Ed.
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail],
                    [e-mail],
                    [e-mail]
        Pages:      12
        Characters: 27193
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-tsvwg-udp-lite-02.txt

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


This document describes the Lightweight User Datagram Protocol
(UDP-Lite), which is similar to the User Datagram Protocol (UDP) (RFC
768), but can also serve applications in error-prone network
environments that prefer to have partially damaged payloads delivered
rather than discarded.  If this feature is not used, UDP-Lite is
semantically identical to UDP.

This document is a product of the Transport Area 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  Tue Jul 13 13:51:30 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Jul 13 13:52:23 2004
Subject: [rfc-dist] RFC 3839 on MIME Type Registrations for 3rd Generation
	Partnership Project (3GPP) Multimedia files
Message-ID: <[e-mail]>


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


        RFC 3839

        Title:      MIME Type Registrations for
                    3rd Generation Partnership Project (3GPP)
                    Multimedia files
        Author(s):  R. Castagno, D. Singer
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      7
        Characters: 15645
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-singer-avt-3gpp-mime-01.txt

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


This document serves to register and document the standard MIME types
associated with the 3GPP multimedia file format, which is part of the
family based on the ISO Media File Format.

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 Jul 21 16:42:47 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jul 21 16:43:31 2004
Subject: [rfc-dist] RFC 3821 on Fibre Channel Over TCP/IP (FCIP)
Message-ID: <[e-mail]>


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


        RFC 3821

        Title:      Fibre Channel Over TCP/IP (FCIP)
        Author(s):  M. Rajagopal, E. Rodriguez, R. Weber
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail],
                    [e-mail], [e-mail]
        Pages:      74
        Characters: 165907
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ips-fcovertcpip-12.txt

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


Fibre Channel Over TCP/IP (FCIP) describes mechanisms that allow the
interconnection of islands of Fibre Channel storage area networks
over IP-based networks to form a unified storage area network in a
single Fibre Channel fabric.  FCIP relies on IP-based network
services to provide the connectivity between the storage area
network islands over local area networks, metropolitan area
networks, or wide area networks.  

This document is a product of the IP Storage 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 Jul 21 16:45:41 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jul 21 16:46:34 2004
Subject: [rfc-dist] RFC 3822 on Finding Fibre Channel over TCP/IP (FCIP)
	Entities Using Service Location Protocol version 2 (SLPv2)
Message-ID: <[e-mail]>


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


        RFC 3822

        Title:      Finding Fibre Channel over TCP/IP (FCIP) Entities
                    Using Service Location Protocol version 2 (SLPv2)
        Author(s):  D. Peterson
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail]
        Pages:      11
        Characters: 22859
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ips-fcip-slp-09.txt

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


This document defines the use of Service Location Protocol version 2
(SLPv2) by Fibre Channel over TCP/IP (FCIP) Entities.

This document is a product of the IP Storage 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 Jul 21 16:47:51 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jul 21 16:48:28 2004
Subject: [rfc-dist] RFC 3850 on Secure/Multipurpose Internet Mail Extensions
	(S/MIME) Version 3.1 Certificate Handling
Message-ID: <[e-mail]>


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


        RFC 3850

        Title:      Secure/Multipurpose Internet Mail Extensions
                    (S/MIME) Version 3.1 Certificate Handling
        Author(s):  B. Ramsdell, Editor
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail]
        Pages:      16
        Characters: 37446
        Obsoletes:  2632

        I-D Tag:    draft-ietf-smime-rfc2632bis-07.txt

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


This document specifies conventions for X.509 certificate usage by
Secure/Multipurpose Internet Mail Extensions (S/MIME) agents.  S/MIME
provides a method to send and receive secure MIME messages, and
certificates are an integral part of S/MIME agent processing.  S/MIME
agents validate certificates as described in RFC 3280, the Internet
X.509 Public Key Infrastructure Certificate and CRL Profile.  S/MIME
agents must meet the certificate processing requirements in this
document as well as those in RFC 3280.

This document is a product of the S/MIME Mail Security 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 Jul 21 16:49:42 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jul 21 16:50:28 2004
Subject: [rfc-dist] RFC 3851 on Secure/Multipurpose Internet Mail Extensions
	(S/MIME) Version 3.1 Message Specification
Message-ID: <[e-mail]>


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


        RFC 3851

        Title:      Secure/Multipurpose Internet Mail Extensions
                    (S/MIME) Version 3.1 Message Specification
        Author(s):  B. Ramsdell, Editor
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail]
        Pages:      36
        Characters: 53328
        Obsoletes:  2633

        I-D Tag:    draft-ietf-smime-rfc2633bis-09.txt

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


This document defines Secure/Multipurpose Internet Mail Extensions
(S/MIME) version 3.1.  S/MIME provides a consistent way to send and
receive secure MIME data.  Digital signatures provide authentication,
message integrity, and non-repudiation with proof of origin.
Encryption provides data confidentiality.  Compression can be used to
reduce data size.  This document obsoletes RFC 2633.

This document is a product of the S/MIME Mail Security 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 Jul 21 16:51:28 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jul 21 16:52:28 2004
Subject: [rfc-dist] RFC 3852 on Cryptographic Message Syntax (CMS)
Message-ID: <[e-mail]>


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


        RFC 3852

        Title:      Cryptographic Message Syntax (CMS)
        Author(s):  R. Housley
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail]
        Pages:      56
        Characters: 15541
        Obsoletes:  3369

        I-D Tag:    draft-ietf-smime-rfc3369bis-04.txt

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


This document describes the Cryptographic Message Syntax (CMS).  This
syntax is used to digitally sign, digest, authenticate, or encrypt
arbitrary message content.

This document is a product of the S/MIME Mail Security 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 Jul 21 16:53:20 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jul 21 16:54:32 2004
Subject: [rfc-dist] RFC 3853 on S/MIME Advanced Encryption Standard (AES)
	Requirement for the Session Initiation Protocol (SIP)
Message-ID: <[e-mail]>


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


        RFC 3853

        Title:      S/MIME Advanced Encryption Standard (AES)
                    Requirement for the Session Initiation Protocol
                    (SIP)
        Author(s):  J. Peterson
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail]
        Pages:      6
        Characters: 10687
        Updates:    3261

        I-D Tag:    draft-ietf-sip-smime-aes-01.txt

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


RFC 3261 currently specifies 3DES as the mandatory-to-implement
ciphersuite for implementations of S/MIME in the Session Initiation
Protocol (SIP).  This document updates the normative guidance of RFC
3261 to require the Advanced Encryption Standard (AES) for S/MIME.

This document is a product of the Session Initiation 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  Wed Jul 21 16:54:43 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jul 21 16:55:59 2004
Subject: [rfc-dist] RFC 3866 on Language Tags and Ranges in the Lightweight
	Directory Access Protocol (LDAP)
Message-ID: <[e-mail]>


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


        RFC 3866

        Title:      Language Tags and Ranges in the
                    Lightweight Directory Access Protocol (LDAP)
        Author(s):  K. Zeilenga, Ed.
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail]
        Pages:      15
        Characters: 31501
        Obsoletes:  2596

        I-D Tag:    draft-zeilenga-ldap-rfc2596-05.txt

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


It is often desirable to be able to indicate the natural language
associated with values held in a directory and to be able to query the
directory for values which fulfill the user's language needs.  This
document details the use of Language Tags and Ranges in the
Lightweight Directory Access Protocol (LDAP).

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Jul 23 17:45:06 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Jul 23 17:45:39 2004
Subject: [rfc-dist] RFC 3831 on Transmission of IPv6 Packets over Fibre
	Channel
Message-ID: <[e-mail]>


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


        RFC 3831

        Title:      Transmission of IPv6 Packets over Fibre Channel
        Author(s):  C. DeSanti
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail]
        Pages:      24
        Characters: 53328
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-imss-ipv6-over-fibre-channel-02.txt

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


This document specifies the way of encapsulating IPv6 packets over
Fibre Channel, and the method of forming IPv6 link-local addresses
and statelessly autoconfigured addresses on Fibre Channel networks.

This document is a product of the Internet and Management Support for
Storage Working Group of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Jul 23 17:47:09 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Jul 23 17:49:09 2004
Subject: [rfc-dist] RFC 3848 on ESMTP and LMTP Transmission Types
	Registration
Message-ID: <[e-mail]>


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


        RFC 3848

        Title:      ESMTP and LMTP Transmission Types Registration
        Author(s):  C. Newman
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail]
        Pages:      4
        Characters: 7916
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-newman-esmtpsa-01.txt

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


This registers seven new mail transmission types (ESMTPA, ESMTPS,
ESMTPSA, LMTP, LMTPA, LMTPS, LMTPSA) for use in the "with" clause of
a Received header in an Internet message.

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 Jul 28 17:21:30 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jul 28 17:22:57 2004
Subject: [rfc-dist] RFC 3849 on IPv6 Address Prefix Reserved for
	Documentation
Message-ID: <[e-mail]>


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


        RFC 3849

        Title:      IPv6 Address Prefix Reserved for Documentation
        Author(s):  G. Huston, A. Lord, P. Smith
        Status:     Informational
        Date:       July 2004
        Mailbox:    [e-mail], [e-mail], [e-mail]
        Pages:      4
        Characters: 7872
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-huston-ipv6-documentation-prefix-03.txt

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


To reduce the likelihood of conflict and confusion when relating
documented examples to deployed systems, an IPv6 unicast address
prefix is reserved for use in examples in RFCs, books, documentation,
and the like.  Since site-local and link-local unicast addresses have
special meaning in IPv6, these addresses cannot be used in many
example situations.  The document describes the use of the IPv6
address prefix 2001:DB8::/32 as a reserved prefix for use in
documentation.

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 Jul 28 17:23:11 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jul 28 17:23:57 2004
Subject: [rfc-dist] RFC 3854 on Securing X.400 Content with
	Secure/Multipurpose Internet Mail Extensions (S/MIME)
Message-ID: <[e-mail]>


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


        RFC 3854

        Title:      Securing X.400 Content with Secure/Multipurpose
                    Internet Mail Extensions (S/MIME)
        Author(s):  P. Hoffman, C. Bonatti, A. Eggen
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      15
        Characters: 32801
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-smime-x400wrap-09.txt

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


This document describes a protocol for adding cryptographic signature
and encryption services to X.400 content with Secure/Multipurpose
Internet Mail Extensions (S/MIME).

This document is a product of the S/MIME Mail Security 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 Jul 28 17:26:15 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Jul 28 17:27:04 2004
Subject: [rfc-dist] RFC 3855 on Transporting Secure/Multipurpose Internet
	Mail Extensions (S/MIME) Objects in X.400
Message-ID: <[e-mail]>


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


        RFC 3855

        Title:      Transporting Secure/Multipurpose Internet Mail
                    Extensions (S/MIME) Objects in X.400
        Author(s):  P. Hoffman, C. Bonatti
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      12
        Characters: 25774
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-smime-x400transport-09.txt

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


This document describes protocol options for conveying objects that
have been protected using the Cryptographic Message Syntax (CMS) and
Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.1
over an X.400 message transfer system.

This document is a product of the S/MIME Mail Security 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 Jul 29 15:44:56 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Jul 29 15:46:14 2004
Subject: [rfc-dist] RFC 3832 on Remote Service Discovery in the Service
	Location Protocol (SLP) via DNS SRV
Message-ID: <[e-mail]>


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


        RFC 3832

        Title:      Remote Service Discovery in the
                    Service Location Protocol (SLP) via DNS SRV
        Author(s):  W. Zhao, H. Schulzrinne, E. Guttman, C. Bisdikian,
                    W. Jerome
        Status:     Experimental
        Date:       July 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail]
        Pages:      8
        Characters: 15602
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-zhao-slp-remote-da-discovery-06.txt


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


Remote service discovery refers to discovering desired services in
given remote (i.e., non-local) DNS domains.  This document describes
remote service discovery in the Service Location Protocol (SLP) via
DNS SRV.  It defines the DNS SRV Resource Records for SLP Directory
Agent services, discusses various issues in using SLP and DNS SRV
together for remote service discovery, and gives the steps for
discovering desired services in remote DNS domains.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Jul 30 17:06:00 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Jul 30 17:06:46 2004
Subject: [rfc-dist] RFC 3700 on Internet Official Protocol Standards
Message-ID: <[e-mail]>


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


        RFC 3700

        Title:      Internet Official Protocol Standards
        Author(s):  J. Reynolds, Ed., S. Ginoza, Ed.
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      54
        Characters: 148273
        Obsoletes:  3600

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


This memo contains a snapshot of the state of standardization of
protocols used in the Internet as of July 22, 2004.  It lists
official protocol standards and Best Current Practice RFCs; it is not
a complete index to the RFC series.  The latest version of this memo
is designated STD 1.

This is now a Standard Protocol.

This memo is an Internet Standard.  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