[rfc-dist] RFC 3870 on application/rdf+xml Media Type Registration

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

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


        RFC 3870

        Title:      application/rdf+xml Media Type Registration
        Author(s):  A. Swartz
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      8
        Characters: 14195
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-swartz-rdfcore-rdfxml-mediatype-05.txt

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


This document describes a media type (application/rdf+xml) for use
with the Extensible Markup Language (XML) serialization of the
Resource Description Framework (RDF).  RDF is a language designed to
support the Semantic Web, by facilitating resource description and
data exchange on the Web.  RDF provides common structures that can be
used for interoperable data exchange and follows the World Wide Web
Consortium (W3C) design principles of interoperability, evolution, and
decentralization.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Sep 14 17:30:06 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 14 17:31:25 2004
Subject: [rfc-dist] RFC 3871 on Operational Security Requirements for Large
	Internet Service Provider (ISP) IP Network Infrastructure
Message-ID: <[e-mail]>


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


        RFC 3871

        Title:      Operational Security Requirements for Large
                    Internet Service Provider (ISP) IP Network
                    Infrastructure
        Author(s):  G. Jones, Ed.
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      81
        Characters: 151101
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-jones-opsec-06.txt

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


This document defines a list of operational security requirements for
the infrastructure of large Internet Service Provider (ISP) IP
networks (routers and switches).  A framework is defined for
specifying "profiles", which are collections of requirements
applicable to certain network topology contexts (all, core-only,
edge-only...).  The goal is to provide network operators a clear,
concise way of communicating their security requirements to vendors.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Sep 14 17:31:43 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 14 17:33:29 2004
Subject: [rfc-dist] RFC 3874 on A 224-bit One-way Hash Function: SHA-224
Message-ID: <[e-mail]>


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


        RFC 3874

        Title:      A 224-bit One-way Hash Function: SHA-224
        Author(s):  R. Housley
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      6
        Characters: 11600
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-pkix-sha224-01.txt

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


This document specifies a 224-bit one-way hash function, called
SHA-224.  SHA-224 is based on SHA-256, but it uses a different
initial value and the result is truncated to 224 bits.

This document is a product of the Public-Key Infrastructure (X.509)
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.

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 Sep 14 17:33:00 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 14 17:34:23 2004
Subject: [rfc-dist] RFC 3876 on Returning Matched Values with the
	Lightweight Directory Access Protocol version 3 (LDAPv3)
Message-ID: <[e-mail]>


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


        RFC 3876

        Title:      Returning Matched Values with the
                    Lightweight Directory Access Protocol version 3
                    (LDAPv3)
        Author(s):  D. Chadwick, S. Mullan
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      12
        Characters: 24233
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ldapext-matchedval-07.txt

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


This document describes a control for the Lightweight Directory
Access Protocol version 3 that is used to return a subset of
attribute values from an entry.  Specifically, only those values that
match a "values return" filter.  Without support for this control, a
client must retrieve all of an attribute's values and search for
specific values locally.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Sep 14 17:34:42 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 14 17:36:02 2004
Subject: [rfc-dist] RFC 3879 on Deprecating Site Local Addresses
Message-ID: <[e-mail]>


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


        RFC 3879

        Title:      Deprecating Site Local Addresses
        Author(s):  C. Huitema, B. Carpenter
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      10
        Characters: 24142
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipv6-deprecate-site-local-03.txt

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


This document describes the issues surrounding the use of IPv6
site-local unicast addresses in their original form, and formally
deprecates them.  This deprecation does not prevent their continued
use until a replacement has been standardized and implemented.

This document is a product of the IP Version 6 Working Group of the
IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Sep 17 17:45:20 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Sep 17 17:47:15 2004
Subject: [rfc-dist] BCP 90,
	RFC 3864 on Registration Procedures for Message Header Fields
Message-ID: <[e-mail]>


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


        BCP 90
        RFC 3864

        Title:      Registration Procedures for Message Header Fields
        Author(s):  G. Klyne, M. Nottingham, J. Mogul
        Status:     Best Current Practice
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      17
        Characters: 36231
        SeeAlso:    BCP 90

        I-D Tag:    draft-klyne-msghdr-registry-07.txt

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


This specification defines registration procedures for the message
header fields used by Internet mail, HTTP, Netnews and other
applications.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Sep 17 17:47:06 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Sep 17 17:47:17 2004
Subject: [rfc-dist] RFC 3865 on A No Soliciting Simple Mail Transfer
	Protocol (SMTP) Service Extension
Message-ID: <[e-mail]>


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


        RFC 3865

        Title:      A No Soliciting Simple Mail Transfer Protocol
                    (SMTP) Service Extension
        Author(s):  C. Malamud
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      19
        Characters: 40717
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-malamud-no-soliciting-07.txt

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


This document proposes an extension to Soliciting Simple Mail Transfer
Protocol (SMTP) for an electronic mail equivalent to the real-world
"No Soliciting" sign.  In addition to the service extension, a new
message header and extensions to the existing "received" message
header are described.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Sep 17 17:49:04 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Sep 17 17:49:10 2004
Subject: [rfc-dist] RFC 3872 on Management Information Base for Telephony
	Routing over IP (TRIP)
Message-ID: <[e-mail]>


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


        RFC 3872

        Title:      Management Information Base
                    for Telephony Routing over IP (TRIP)
        Author(s):  D. Zinman, D. Walker, J. Jiang
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail],
                    [e-mail],
                    [e-mail]
        Pages:      53
        Characters: 98614
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-iptel-trip-mib-10.txt

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


This memo defines a portion of the Management Information Base (MIB)
module for use with network management protocols in the Internet
community.  In particular, it describes a set of managed objects that
are used to manage Telephony Routing over IP (TRIP) devices.

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

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Sep 17 17:55:11 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Sep 17 17:57:16 2004
Subject: [rfc-dist] RFC 3873 on Stream Control Transmission Protocol (SCTP)
	Management Information Base (MIB)
Message-ID: <[e-mail]>


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


        RFC 3873

        Title:      Stream Control Transmission Protocol (SCTP)
                    Management Information Base (MIB)
        Author(s):  J. Pastor, M. Belinchon
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail],
                    [e-mail]
        Pages:      46
        Characters: 82403
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sigtran-sctp-mib-10.txt

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


The Stream Control Transmission Protocol (SCTP) is a reliable
transport protocol operating on top of a connectionless packet network
such as IP.  It is designed to transport public switched telephone
network (PSTN) signaling messages over the connectionless packet
network, but is capable of broader applications.

This memo defines the Management Information Base (MIB) module which
describes the minimum set of objects needed to manage the
implementation of the SCTP.

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.

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 Sep 17 17:59:14 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Sep 17 18:00:16 2004
Subject: [rfc-dist] RFC 3890 on A Transport Independent Bandwidth Modifier
	for the Session Description Protocol (SDP)
Message-ID: <[e-mail]>


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


        RFC 3890

        Title:      A Transport Independent Bandwidth Modifier
                    for the Session Description Protocol (SDP)
        Author(s):  M. Westerlund
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      22
        Characters: 49894
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mmusic-sdp-bwparam-06.txt

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


This document defines a Session Description Protocol (SDP) Transport
Independent Application Specific Maximum (TIAS) bandwidth modifier
that does not include transport overhead; instead an additional packet
rate attribute is defined.  The transport independent bit-rate value
together with the maximum packet rate can then be used to calculate
the real bit-rate over the transport actually used.

The existing SDP bandwidth modifiers and their values include the
bandwidth needed for the transport and IP layers.  When using SDP with
protocols like the Session Announcement Protocol (SAP), the Session
Initiation Protocol (SIP), and the Real-Time Streaming Protocol
(RTSP), and when the involved hosts has different transport overhead,
for example due to different IP versions, the interpretation of what
lower layer bandwidths are included is not clear.

This document is a product of the Multiparty Multimedia Session
Control Working Group of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Sep 21 08:42:56 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 21 08:43:48 2004
Subject: [rfc-dist] RFC 3877 on Alarm Management Information Base (MIB)
Message-ID: <[e-mail]>


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


        RFC 3877

        Title:      Alarm Management Information Base (MIB)
        Author(s):  S. Chisholm, D. Romascanu
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      75
        Characters: 149783
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-disman-alarm-mib-18.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3877.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 management objects used for modelling
and storing alarms.

This document is a product of the Distributed Management Working Group
of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Sep 24 09:23:00 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Sep 24 09:24:00 2004
Subject: [rfc-dist] RFC 3895 on Definitions of Managed Objects for the DS1,
	E1, DS2, and E2 Interface Types
Message-ID: <[e-mail]>


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


        RFC 3895

        Title:      Definitions of Managed Objects
                    for the DS1, E1, DS2, and E2 Interface Types
        Author(s):  O. Nicklass, Ed.
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      84
        Characters: 163841
        Obsoletes:  2495

        I-D Tag:    draft-ietf-atommib-rfc2495bis-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3895.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 objects used for managing DS1, E1, DS2 
and E2 interfaces.  This document is a companion to the documents
that define Managed Objects for the DS0, DS3/E3 and Synchronous
Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface
Types.  This document obsoletes RFC 2495.

This document is a product of the AToM MIB Working Group of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Sep 24 09:26:16 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Sep 24 09:27:05 2004
Subject: [rfc-dist] RFC 3896 on Definitions of Managed Objects for the
	DS3/E3 Interface Type
Message-ID: <[e-mail]>


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


        RFC 3896

        Title:      Definitions of Managed Objects for the
                    DS3/E3 Interface Type
        Author(s):  O. Nicklass, Ed.
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      63
        Characters: 129547
        Obsoletes:  2496

        I-D Tag:    draft-ietf-atommib-rfc2496bis-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3896.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 objects used for managing DS3 and E3
interfaces.  This document is a companion to the documents that
define Managed Objects for the DS0, DS1/E1/DS2/E2 and Synchronous
Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface
Types.  This document obsoletes RFC 2496.

This document is a product of the AToM MIB Working Group of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Sep 24 09:28:50 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Sep 24 09:30:02 2004
Subject: [rfc-dist] RFC 3897 on Open Pluggable Edge Services (OPES) Entities
	and End Points Communication
Message-ID: <[e-mail]>


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


        RFC 3897

        Title:      Open Pluggable Edge Services (OPES) Entities
                    and End Points Communication
        Author(s):  A. Barbir
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      14
        Characters: 33890
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-opes-end-comm-08.txt

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


This memo documents tracing and non-blocking (bypass) requirements
for Open Pluggable Edge Services (OPES).

This document is a product of the Open Pluggable Edge Services 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.

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 Sep 24 09:30:50 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Sep 24 09:30:59 2004
Subject: [rfc-dist] BCP 91,
	RFC 3901 on DNS IPv6 Transport Operational Guidelines
Message-ID: <[e-mail]>


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


        BCP 91
        RFC 3901

        Title:      DNS IPv6 Transport Operational Guidelines
        Author(s):  A. Durand, J. Ihren
        Status:     Best Current Practice
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      5
        Characters: 10025
        SeeAlso:    BCP 91

        I-D Tag:    draft-ietf-dnsop-ipv6-transport-guidelines-02.txt

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


This memo provides guidelines and Best Current Practice for operating
DNS in a world where queries and responses are carried in a mixed
environment of IPv4 and IPv6 networks.

This document is a product of the Domain Name System Operations
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.

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 Sep 24 09:35:12 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Sep 24 09:35:58 2004
Subject: [rfc-dist] RFC 3905 on A Template for IETF Patent Disclosures and
	Licensing Declarations
Message-ID: <[e-mail]>


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


        RFC 3905

        Title:      A Template for IETF Patent Disclosures and
                    Licensing Declarations
        Author(s):  V. See, Ed.
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      9
        Characters: 16110
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipr-template-09.txt

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


This document describes a proposal for one form of a template for
IETF patent disclosures and licensing declarations.  The optional use
of this template is meant to simplify the process of such disclosures
and licensing declarations and to assist disclosers in providing the
necessary information to meet the obligations documented in RFC 3668.

This document is a product of the Intellectual Property Rights 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.

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 Sep 24 09:37:38 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Sep 24 09:38:31 2004
Subject: [rfc-dist] RFC 3912 on WHOIS Protocol Specification
Message-ID: <[e-mail]>


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


        RFC 3912

        Title:      WHOIS Protocol Specification
        Author(s):  L. Daigle
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      4
        Characters: 7770
        Obsoletes:  954, 812

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

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


This document updates the specification of the WHOIS protocol,
thereby obsoleting RFC 954.  The update is intended to remove the
material from RFC 954 that does not have to do with the on-the-wire
protocol, and is no longer applicable in today's Internet.  This
document does not attempt to change or update the protocol per se, or
document other uses of the protocol that have come into existence
since the publication of RFC 954.

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.

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 Sep 28 14:58:36 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 28 15:00:01 2004
Subject: [rfc-dist] RFC 3902 on The "application/soap+xml" media type
Message-ID: <[e-mail]>


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


        RFC 3902

        Title:      The "application/soap+xml" media type
        Author(s):  M. Baker, M. Nottingham
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      5
        Characters: 10575
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-baker-soap-media-reg-06.txt

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


This document defines the "application/soap+xml" media type which can
be used to describe SOAP 1.2 messages serialized as XML 1.0.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Sep 28 14:59:53 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 28 15:02:24 2004
Subject: [rfc-dist] RFC 3884 on Use of IPsec Transport Mode for Dynamic
	Routing
Message-ID: <[e-mail]>


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


        RFC 3884

        Title:      Use of IPsec Transport Mode for Dynamic Routing
        Author(s):  J. Touch, L. Eggert, Y. Wang
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      25
        Characters: 59437
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-touch-ipsec-vpn-07.txt

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


IPsec can secure the links of a multihop network to protect
communication between trusted components, e.g., for a secure virtual
network (VN), overlay, or virtual private network (VPN). Virtual links
established by IPsec tunnel mode can conflict with routing and
forwarding inside VNs because IP routing depends on references to
interfaces and next-hop IP addresses. The IPsec tunnel mode
specification is ambiguous on this issue, so even compliant
implementations cannot be trusted to avoid conflicts.  An
alternative to tunnel mode uses non-IPsec IPIP encapsulation together
with IPsec transport mode, which we call IIPtran.  IPIP encapsulation
occurs as a separate initial step, as the result of a forwarding
lookup of the VN packet. IPsec transport mode processes the resulting
(tunneled) IP packet with an SA determined through a security
association database (SAD) match on the tunnel header.  IIPtran
supports dynamic routing inside the VN without changes to the current
IPsec architecture.  IIPtran demonstrates how to configure any
compliant IPsec implementation to avoid the aforementioned conflicts.
IIPtran is also compared to several alternative mechanisms for VN
routing and their respective impact on IPsec, routing, policy
enforcement, and interactions with the Internet Key Exchange (IKE).

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Sep 28 15:55:01 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 28 15:55:24 2004
Subject: [rfc-dist] RFC 3878 on Alarm Reporting Control Management
	Information Base (MIB)
Message-ID: <[e-mail]>


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


        RFC 3878

        Title:      Alarm Reporting Control
                    Management Information Base (MIB)
        Author(s):  H. Lam, A. Huynh, D. Perkins
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      16
        Characters: 31093
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-disman-conditionmib-10.txt

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


This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for controlling the reporting of
alarm conditions.

This document is a product of the Distributed Management Working Group
of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Sep 28 15:57:15 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 28 15:57:26 2004
Subject: [rfc-dist] RFC 3891 on The Session Initiation Protocol (SIP)
	"Replaces" Header
Message-ID: <[e-mail]>


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


        RFC 3891

        Title:      The Session Initiation Protocol (SIP)
                    "Replaces" Header
        Author(s):  R. Mahy, B. Biggs, R. Dean
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail], [e-mail]
        Pages:      16
        Characters: 34180
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-replaces-05.txt

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


This document defines a new header for use with Session Initiation
Protocol (SIP) multi-party applications and call control.  The
Replaces header is used to logically replace an existing SIP dialog
with a new SIP dialog.  This primitive can be used to enable a variety
of features, for example: "Attended Transfer" and "Call Pickup".  Note
that the definition of these example features is non-normative.

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.

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 Sep 28 15:59:19 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 28 16:01:14 2004
Subject: [rfc-dist] RFC 3892 on The Session Initiation Protocol (SIP)
	Referred-By Mechanism
Message-ID: <[e-mail]>


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


        RFC 3892

        Title:      The Session Initiation Protocol (SIP)
                    Referred-By Mechanism
        Author(s):  R. Sparks
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      25
        Characters: 52441
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-referredby-05.txt

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


The Session Initiation Protocol (SIP) REFER method provides a
mechanism where one party (the referrer) gives a second party (the
referee) an arbitrary URI to reference.  If that URI is a SIP URI, the
referee will send a SIP request, often an INVITE, to that URI (the
refer target).  This document extends the REFER method, allowing the
referrer to provide information about the REFER request to the refer
target using the referee as an intermediary.  This information
includes the identity of the referrer and the URI to which the
referrer referred.  The mechanism utilizes S/MIME to help protect this
information from a malicious intermediary.  This protection is
optional, but a recipient may refuse to accept a request unless it is
present.

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.

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 Sep 28 16:01:04 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 28 16:01:25 2004
Subject: [rfc-dist] RFC 3893 on Session Initiation Protocol (SIP)
	Authenticated Identity Body (AIB) Format
Message-ID: <[e-mail]>


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


        RFC 3893

        Title:      Session Initiation Protocol (SIP)
                    Authenticated Identity Body (AIB) Format
        Author(s):  J. Peterson
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      13
        Characters: 28500
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-authid-body-03.txt

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


RFC 3261 introduces the concept of adding an S/MIME body to a Session
Initiation Protocol (SIP) request or response in order to provide
reference integrity over its headers.  This document provides a more
specific mechanism to derive integrity and authentication properties
from an 'authenticated identity body', a digitally-signed SIP
message, or message fragment.  A standard format for such bodies
(known as Authenticated Identity Bodies, or AIBs) is given in this
document.  Some considerations for the processing of AIBs by
recipients of SIP messages with such bodies are also given.

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.

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 Sep 28 16:03:12 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 28 16:04:44 2004
Subject: [rfc-dist] RFC 3904 on Evaluation of IPv6 Transition Mechanisms for
	Unmanaged Networks
Message-ID: <[e-mail]>


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


        RFC 3904

        Title:      Evaluation of IPv6 Transition Mechanisms for
                    Unmanaged Networks
        Author(s):  C. Huitema, R. Austein, S. Satapati,
                    R. van der Pol
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail]
        Pages:      19
        Characters: 46844
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-v6ops-unmaneval-03.txt

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


This document analyzes issues involved in the transition of
"unmanaged networks" from IPv4 to IPv6.  Unmanaged networks
typically correspond to home networks or small office networks.  A
companion paper analyzes out the requirements for mechanisms needed
in various transition scenarios of these networks to IPv6.
Starting from this analysis, we evaluate the suitability of
mechanisms that have already been specified, proposed, or deployed.

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.

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 Sep 28 16:05:02 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Sep 28 16:05:38 2004
Subject: [rfc-dist] RFC 3913 on Border Gateway Multicast Protocol (BGMP):
	Protocol Specification
Message-ID: <[e-mail]>


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


        RFC 3913

        Title:      Border Gateway Multicast Protocol (BGMP):
                    Protocol Specification
        Author(s):  D. Thaler
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      41
        Characters: 97443
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-bgmp-spec-06.txt

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


This document describes the Border Gateway Multicast Protocol (BGMP),
a protocol for inter-domain multicast routing.  BGMP builds shared
trees for active multicast groups, and optionally allows receiver
domains to build source-specific, inter-domain, distribution branches
where needed.  BGMP natively supports "source-specific multicast"
(SSM).  To also support "any-source multicast" (ASM), BGMP requires
that each multicast group be associated with a single root (in BGMP it
is referred to as the root domain).  It requires that different ranges
of the multicast address space are associated (e.g., with 
Unicast-Prefix-Based Multicast addressing) with different domains.
Each of these domains then becomes the root of the shared domain-trees
for all groups in its range.  Multicast participants will generally
receive better multicast service if the session initiator's address
allocator selects addresses from its own domain's part of the space,
thereby causing the root domain to be local to at least one of the
session participants.

This document is a product of the Border Gateway Multicast Protocol
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.

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 Sep 29 16:12:48 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Sep 29 16:21:47 2004
Subject: [rfc-dist] RFC 3885 on SMTP Service Extension for Message Tracking
Message-ID: <[e-mail]>


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


        RFC 3885

        Title:      SMTP Service Extension for Message Tracking
        Author(s):  E. Allman, T. Hansen
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      9
        Characters: 17458
        Updates:    3461

        I-D Tag:    draft-ietf-msgtrk-smtpext-05.txt

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


This memo defines an extension to the SMTP service whereby a
client may mark a message for future tracking.

This document is a product of the Message Tracking Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Wed Sep 29 16:14:37 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Sep 29 16:21:50 2004
Subject: [rfc-dist] RFC 3886 on An Extensible Message Format for Message
	Tracking Responses
Message-ID: <[e-mail]>


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


        RFC 3886

        Title:      An Extensible Message Format for Message Tracking
                    Responses
        Author(s):  E. Allman
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      11
        Characters: 21746
        Updates:    3463

        I-D Tag:    draft-ietf-msgtrk-trkstat-05.txt

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


Message Tracking is expected to be used to determine the
status of undelivered e-mail upon request.  Tracking is used in
conjunction with Delivery Status Notifications (DSN) and Message
Disposition Notifications (MDN); generally, a message tracking request
will be issued only when a DSN or MDN has not been received within a
reasonable timeout period.

This memo defines a MIME content-type for message tracking
status in the same spirit as RFC 3464, "An Extensible Message Format
for
Delivery Status Notifications".  It is to be issued upon a request as
described in "Message Tracking Query Protocol".  This memo defines
only the format of the status information.  An extension to SMTP
to label messages for further tracking and request tracking status is
defined in a separate memo.

This document is a product of the Message Tracking Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Wed Sep 29 16:16:19 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Sep 29 16:21:52 2004
Subject: [rfc-dist] RFC 3887 on Message Tracking Query Protocol
Message-ID: <[e-mail]>


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


        RFC 3887

        Title:      Message Tracking Query Protocol
        Author(s):  T. Hansen
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      23
        Characters: 42763
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-msgtrk-mtqp-12.txt

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


Customers buying enterprise message systems often ask: Can I track the
messages?  Message tracking is the ability to find out the path that a
particular message has taken through a messaging system and the
current routing status of that message.  This document describes the
Message Tracking Query Protocol that is used in conjunction with
extensions to the ESMTP protocol to provide a complete message
tracking solution for the Internet.

This document is a product of the Message Tracking Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Wed Sep 29 16:17:54 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Sep 29 16:21:55 2004
Subject: [rfc-dist] RFC 3888 on Message Tracking Model and Requirements
Message-ID: <[e-mail]>


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


         RFC 3888

         Title:      Message Tracking Model and Requirements
         Author(s):  T. Hansen
         Status:     Informational
         Date:       September 2004
         Mailbox:    [e-mail]
         Pages:      11
         Characters: 20950
         Updates/Obsoletes/SeeAlso:    None

         I-D Tag:    draft-ietf-msgtrk-model-07.txt

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


Customers buying enterprise message systems often ask: Can I track the
messages?  Message tracking is the ability to find out the path that a
particular message has taken through a messaging system and the
current routing status of that message.  This document provides a
model of message tracking that can be used for understanding the
Internet-wide message infrastructure and to further enhance those
capabilities to include message tracking, as well as requirements for
proposed message tracking solutions.

This document is a product of the Message Tracking Protocol 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.

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