[rfc-dist] RFC 3881 on Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications

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

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


        RFC 3881

        Title:      Security Audit and Access Accountability Message
                    XML Data Definitions for Healthcare Applications
        Author(s):  G. Marshall
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      47
        Characters: 86130
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-marshall-security-audit-12.txt

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


This document defines the format of data to be collected and minimum
set of attributes that need to be captured for security auditing in
healthcare application systems.  The format is defined as an XML
schema, which is intended as a reference for healthcare standards
developers and application designers.  It consolidates several
previous documents on security auditing of healthcare data.

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 Oct  1 13:13:14 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct  1 13:14:27 2004
Subject: [rfc-dist] RFC 3915 on Domain Registry Grace Period Mapping for the
	Extensible Provisioning Protocol (EPP)
Message-ID: <[e-mail]>


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


        RFC 3915

        Title:      Domain Registry Grace Period Mapping for the
                    Extensible Provisioning Protocol (EPP)
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      23
        Characters: 45467
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-hollenbeck-epp-rgp-04.txt

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


This document describes an Extensible Provisioning Protocol (EPP)
extension mapping for the management of Domain Name System (DNS)
domain names subject to "grace period" policies defined by the
Internet Corporation for Assigned Names and Numbers (ICANN).  Grace
period policies exist to allow protocol actions to be reversed or
otherwise revoked during a short period of time after the protocol
action has been performed.  Specified in XML, this mapping extends
the EPP domain name mapping to provide additional features required
for grace period processing.

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 Oct  1 13:14:33 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct  1 13:15:03 2004
Subject: [rfc-dist] RFC 3916 on Requirements for Pseudo-Wire Emulation
	Edge-to-Edge (PWE3)
Message-ID: <[e-mail]>


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


        RFC 3916

        Title:      Requirements for Pseudo-Wire Emulation
                    Edge-to-Edge (PWE3)
        Author(s):  X. Xiao, Ed., D. McPherson, Ed., P. Pate, Ed.
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      19
        Characters: 43856
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-pwe3-requirements-08.txt

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


This document describes base requirements for the Pseudo-Wire
Emulation Edge to Edge Working Group (PWE3 WG).  It provides
guidelines for other working group documents that will define
mechanisms for providing pseudo-wire emulation of Ethernet, ATM, and
Frame Relay.  Requirements for pseudo-wire emulation of TDM (i.e.,
"synchronous bit streams at rates defined by ITU G.702") are defined
in another document.  It should be noted that the PWE3 WG standardizes
mechanisms that can be used to provide PWE3 services, but not the
services themselves.

This document is a product of the Pseudo Wire Emulation Edge to Edge
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 Oct  1 16:33:23 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct  1 16:34:31 2004
Subject: [rfc-dist] RFC 3882 on Configuring BGP to Block Denial-of-Service
	Attacks
Message-ID: <[e-mail]>


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


        RFC 3882

        Title:      Configuring BGP to Block Denial-of-Service Attacks
        Author(s):  D. Turk
        Status:     Informational
        Date:       September 2004
        Mailbox:    [e-mail]
        Pages:      8
        Characters: 19637
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-turk-bgp-dos-07.txt

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


This document describes an operational technique that uses BGP
communities to remotely trigger black-holing of a particular
destination network to block denial-of-service attacks.  Black-holing
can be applied on a selection of routers rather than all BGP-speaking
routers in the network.  The document also describes a sinkhole tunnel
technique using BGP communities and tunnels to pull traffic into a
sinkhole router for analysis.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Mon Oct  4 16:59:02 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Oct  4 16:59:47 2004
Subject: [rfc-dist] RFC 3894 on Sieve Extension: Copying Without Side Effects
Message-ID: <[e-mail]>


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


        RFC 3894

        Title:      Sieve Extension: Copying Without Side Effects
        Author(s):  J. Degener
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      5
        Characters: 9018
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-degener-sieve-copy-03.txt

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


The Sieve scripting language allows users to control
handling and disposal of their incoming e-mail.  By default,
an e-mail message that is processed by a Sieve script is saved
in the owner's "inbox".  Actions such as "fileinto" and
"redirect" cancel this default behavior.

This document defines a new keyword parameter, ":copy", to be
used with the Sieve "fileinto" and "redirect" actions.  Adding
":copy" to an action suppresses cancellation of the default
"inbox" save.  It allows users to add commands to an existing
script without changing the meaning of the rest of the script.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Mon Oct  4 17:00:30 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Oct  4 17:01:19 2004
Subject: [rfc-dist] RFC 3918 on Methodology for IP Multicast Benchmarking
Message-ID: <[e-mail]>


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


        RFC 3918

        Title:      Methodology for IP Multicast Benchmarking
        Author(s):  D. Stopp, B. Hickman
        Status:     Informational
        Date:       October 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      31
        Characters: 64652
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-bmwg-mcastm-14.txt

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


The purpose of this document is to describe methodology specific to
the benchmarking of multicast IP forwarding devices.  It builds upon
the tenets set forth in RFC 2544, RFC 2432 and other IETF
Benchmarking Methodology Working Group (BMWG) efforts.  This
document seeks to extend these efforts to the multicast paradigm.

The BMWG produces two major classes of documents: Benchmarking
Terminology documents and Benchmarking Methodology documents.  The
Terminology documents present the benchmarks and other related
terms.  The Methodology documents define the procedures required to
collect the benchmarks cited in the corresponding Terminology
documents.

This document is a product of the Benchmarking Methodology 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  Mon Oct  4 17:02:19 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Oct  4 17:03:29 2004
Subject: [rfc-dist] RFC 3920 on Extensible Messaging and Presence Protocol
	(XMPP): Core
Message-ID: <[e-mail]>


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


        RFC 3920

        Title:      Extensible Messaging and Presence Protocol (XMPP):
                    Core
        Author(s):  P. Saint-Andre, Ed.
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      90
        Characters: 194313
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-xmpp-core-24.txt

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


This memo defines the core features of the Extensible Messaging and
Presence Protocol (XMPP), a protocol for streaming Extensible Markup
Language (XML) elements in order to exchange structured information
in close to real time between any two network endpoints.  While XMPP
provides a generalized, extensible framework for exchanging XML data,
it is used mainly for the purpose of building instant messaging and
presence applications that meet the requirements of RFC 2779.

This document is a product of the Extensible Messaging and Presence
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  Mon Oct  4 17:03:58 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Oct  4 17:04:16 2004
Subject: [rfc-dist] RFC 3921 on Extensible Messaging and Presence Protocol
	(XMPP): Instant Messaging and Presence
Message-ID: <[e-mail]>


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


        RFC 3921

        Title:      Extensible Messaging and Presence Protocol (XMPP):
                    Instant Messaging and Presence
        Author(s):  P. Saint-Andre, Ed.
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      107
        Characters: 217527
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-xmpp-im-22.txt

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


This memo describes extensions to and applications of the core
features of the Extensible Messaging and Presence Protocol (XMPP)
that provide the basic instant messaging (IM) and presence
functionality defined in RFC 2779.

This document is a product of the Extensible Messaging and Presence
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  Mon Oct  4 17:05:34 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Oct  4 17:06:20 2004
Subject: [rfc-dist] RFC 3922 on Mapping the Extensible Messaging and
	Presence Protocol (XMPP) to Common Presence and Instant
	Messaging (CPIM)
Message-ID: <[e-mail]>


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


        RFC 3922

        Title:      Mapping the Extensible Messaging and Presence
                    Protocol (XMPP) to Common Presence and Instant
                    Messaging (CPIM)
        Author(s):  P. Saint-Andre
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      34
        Characters: 70790
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-xmpp-cpim-05.txt

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


This memo describes a mapping between the Extensible Messaging and
Presence Protocol (XMPP) and the Common Presence and Instant
Messaging (CPIM) specifications.

This document is a product of the Extensible Messaging and Presence
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  Mon Oct  4 17:07:57 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Oct  4 17:08:16 2004
Subject: [rfc-dist] RFC 3923 on End-to-End Signing and Object Encryption for
	the Extensible Messaging and Presence Protocol (XMPP)
Message-ID: <[e-mail]>


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


        RFC 3923

        Title:      End-to-End Signing and Object Encryption for the
                    Extensible Messaging and Presence Protocol (XMPP)
        Author(s):  P. Saint-Andre
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      27
        Characters: 51828
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-xmpp-e2e-09.txt

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


This memo defines methods of end-to-end signing and object
encryption for the Extensible Messaging and Presence Protocol (XMPP).

This document is a product of the Extensible Messaging and Presence
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 Oct  5 16:19:48 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Oct  5 16:20:24 2004
Subject: [rfc-dist] RFC 3883 on Detecting Inactive Neighbors over OSPF
	Demand Circuits (DC)
Message-ID: <[e-mail]>


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


        RFC 3883

        Title:      Detecting Inactive Neighbors over OSPF Demand
                    Circuits (DC)
        Author(s):  S. Rao, A. Zinin, A. Roy
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail], [e-mail], [e-mail]
        Pages:      6
        Characters: 13100
        Updates:    1793

        I-D Tag:    draft-ietf-ospf-dc-07.txt

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


OSPF is a link-state intra-domain routing protocol used in IP
networks.  OSPF behavior over demand circuits (DC) is optimized in RFC
1793 to minimize the amount of overhead traffic.  A part of the OSPF
demand circuit extensions is the Hello suppression mechanism.  This
technique allows a demand circuit to go down when no interesting
traffic is going through the link.  However, it also introduces a
problem, where it becomes impossible to detect an OSPF-inactive
neighbor over such a link.  This memo introduces a new mechanism
called "neighbor probing" to address the above problem.

This document is a product of the Open Shortest Path First IGP 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 Oct  5 16:28:05 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Oct  5 16:28:19 2004
Subject: [rfc-dist] RFC 3914 on Open Pluggable Edge Services (OPES)
	Treatment of IAB Considerations
Message-ID: <[e-mail]>


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


        RFC 3883

        Title:      Detecting Inactive Neighbors over OSPF Demand
                    Circuits (DC)
        Author(s):  S. Rao, A. Zinin, A. Roy
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail], [e-mail], [e-mail]
        Pages:      6
        Characters: 13100
        Updates:    1793

        I-D Tag:    draft-ietf-ospf-dc-07.txt

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


IETF Internet Architecture Board (IAB) expressed nine
architecture-level considerations for the Open Pluggable Edge
Services (OPES) framework.  This document describes how OPES
addresses those considerations.

This document is a prodcut of the Open Pluggable Edge Services Working
Group.

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 Oct  5 16:30:10 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Oct  5 16:30:19 2004
Subject: [rfc-dist] Corrected: RFC 3914 on Open Pluggable Edge Services
	(OPES) Treatment of IAB Considerations
Message-ID: <[e-mail]>


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


        RFC 3914

        Title:      Open Pluggable Edge Services (OPES) Treatment of
                    IAB Considerations
        Author(s):  A. Barbir, A. Rousskov
        Status:     Informational
        Date:       October 2004
        Mailbox:    [e-mail],
                    [e-mail]
        Pages:      16
        Characters: 37411
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-opes-iab-05.txt

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


IETF Internet Architecture Board (IAB) expressed nine
architecture-level considerations for the Open Pluggable Edge
Services (OPES) framework.  This document describes how OPES
addresses those considerations.

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  Tue Oct  5 16:31:36 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Oct  5 16:32:22 2004
Subject: [rfc-dist] RFC 3926 on FLUTE - File Delivery over Unidirectional
	Transport
Message-ID: <[e-mail]>


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


        RFC 3926

        Title:      FLUTE - File Delivery over Unidirectional
                    Transport
        Author(s):  T. Paila, M. Luby, R. Lehtonen, V. Roca, R. Walsh
        Status:     Experimental
        Date:       October 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail],
                    [e-mail], [e-mail]
        Pages:      35
        Characters: 81224
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rmt-flute-08.txt

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


This document defines FLUTE, a protocol for the unidirectional
delivery of files over the Internet, which is particularly suited to
multicast networks.  The specification builds on Asynchronous Layered
Coding, the base protocol designed for massively scalable multicast
distribution.

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

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Thu Oct  7 16:29:43 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Oct  7 16:30:34 2004
Subject: [rfc-dist] RFC 3868 on Signalling Connection Control Part User
	Adaptation Layer (SUA)
Message-ID: <[e-mail]>


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


        RFC 3868

        Title:      Signalling Connection Control Part User Adaptation
                    Layer (SUA)
        Author(s):  J. Loughney, Ed., G. Sidebottom, L. Coene,
                    G. Verwimp, J. Keller, B. Bidulock
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail],
                    [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail]
        Pages:      131
        Characters: 294116
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sigtran-sua-16.txt

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


This document defines a protocol for the transport of any Signalling
Connection Control Part-User signalling over IP using the Stream
Control Transmission Protocol.  The protocol is designed to be modular
and symmetric, to allow it to work in diverse architectures, such as a
Signalling Gateway to IP Signalling Endpoint architecture as well as a
peer-to-peer IP Signalling Endpoint architecture.

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  Thu Oct  7 16:32:02 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Oct  7 16:32:38 2004
Subject: [rfc-dist] RFC 3910 on The SPIRITS (Services in PSTN requesting
	Internet Services) Protocol
Message-ID: <[e-mail]>


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


        RFC 3910

        Title:      The SPIRITS (Services in PSTN requesting Internet
                    Services) Protocol
        Author(s):  V. Gurbani, Ed., A. Brusilovsky, I. Faynberg,
                    J. Gato, H. Lu, M. Unmehopa
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail]
        Pages:      50
        Characters: 110515
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-spirits-protocol-08.txt

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


This document describes the Services in PSTN (Public Switched
Telephone Network) requesting Internet Services (SPIRITS) protocol.
The purpose of the SPIRITS protocol is to support services that
originate in the cellular or wireline PSTN and necessitate
interactions between the PSTN and the Internet.  On the PSTN side, the
SPIRITS services are most often initiated from the Intelligent Network
(IN) entities.  Internet Call Waiting and Internet Caller-ID Delivery
are examples of SPIRITS services, as are location-based services on
the cellular network.  The protocol defines the building blocks from
which many other services can be built.

This document is a product of the Service in the PSTN/IN Requesting
InTernet Service Working Group.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Thu Oct  7 16:33:30 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Oct  7 16:34:38 2004
Subject: [rfc-dist] RFC 3917 on Requirements for IP Flow Information Export
	(IPFIX)
Message-ID: <[e-mail]>


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


        RFC 3917

        Title:      Requirements for IP Flow Information Export
                    (IPFIX)
        Author(s):  J. Quittek, T. Zseby, B. Claise, S. Zander
        Status:     Informational
        Date:       October 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail]
        Pages:      33
        Characters: 81615
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipfix-reqs-16.txt

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


This memo defines requirements for the export of measured IP flow
information out of routers, traffic measurement probes, and
middleboxes.

This document is a product of the IP Flow Information Export 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 Oct  8 16:38:17 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct  8 16:38:56 2004
Subject: [rfc-dist] RFC 3898 on Network Information Service (NIS)
	Configuration Options for Dynamic Host Configuration Protocol
	for IPv6 (DHCPv6)
Message-ID: <[e-mail]>


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


        RFC 3898

        Title:      Network Information Service (NIS)
                    Configuration Options for Dynamic
                    Host Configuration Protocol for IPv6 (DHCPv6)
        Author(s):  V. Kalusivalingam
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      7
        Characters: 13955
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt

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


This document describes four options for Network Information Service
(NIS) related configuration information in Dynamic Host Configuration
Protocol for IPv6 (DHCPv6): NIS Servers, NIS+ Servers, NIS Client
Domain Name, NIS+ Client Domain name.

This document is a product of the Dynamic Host Configuration 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 Oct  8 16:39:39 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct  8 16:41:24 2004
Subject: [rfc-dist] RFC 3909 on Lightweight Directory Access Protocol (LDAP)
	Cancel Operation
Message-ID: <[e-mail]>


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


        RFC 3909

        Title:      Lightweight Directory Access Protocol (LDAP)
                    Cancel Operation
        Author(s):  K. Zeilenga
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      7
        Characters: 13423
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-zeilenga-ldap-cancel-11.txt

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


This specification describes a Lightweight Directory Access Protocol
(LDAP) extended operation to cancel (or abandon) an outstanding
operation.  Unlike the LDAP Abandon operation, but like the X.511
Directory Access Protocol (DAP) Abandon operation, this operation has
a response which provides an indication of its outcome.

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 Oct  8 16:42:00 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct  8 16:42:39 2004
Subject: [rfc-dist] RFC 3919 on Remote Network Monitoring (RMON) Protocol
	Identifiers for IPv6 and Multi Protocol Label Switching (MPLS)
Message-ID: <[e-mail]>


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


        RFC 3919

        Title:      Remote Network Monitoring (RMON) Protocol
                    Identifiers for IPv6 and Multi Protocol Label
                    Switching (MPLS)
        Author(s):  E. Stephan, J. Palet
        Status:     Informational
        Date:       October 2004
        Mailbox:    [e-mail],
                    [e-mail]
        Pages:      8
        Characters: 14228
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rmonmib-pi-ipv6-04.txt

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


This memo defines additional (to those in RFC 2896) protocol
identifier examples for IP version 6 and MPLS protocols.  These can
be used to produce valid protocolDirTable INDEX encodings, as defined
by the Remote Network Monitoring MIB (Management Information Base)
Version 2 (RFC2021) and the RMON Protocol Identifier Reference
(RFC2895).

This document contains additional (to those in RFC 2896) protocol
identifier macros for well-known protocols.  A conformant
implementation of the RMON-2 MIB (RFC2021) can be accomplished
without the use of these protocol identifiers, and accordingly, this
document does not specify any IETF standard.  It is published to
encourage better interoperability between RMON-2 agent
implementations, by providing RMON related IPv6 and MPLS protocol
information.

This document is a product of the Remote Network Monitoring 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 Oct  8 16:43:50 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct  8 16:45:24 2004
Subject: [rfc-dist] BCP 92, RFC 3932 on The IESG and RFC Editor Documents:
	Procedures
Message-ID: <[e-mail]>


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


        BCP 92
        RFC 3932

        Title:      The IESG and RFC Editor Documents: Procedures
        Author(s):  H. Alvestrand
        Status:     Best Current Practice
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      8
        Characters: 17093
        Updates:    3710, 2026

        I-D Tag:    draft-iesg-rfced-documents-03.txt

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


This document describes the IESG's procedures for handling documents
submitted for RFC publication via the RFC Editor, subsequent to the
changes proposed by the IESG at the Seoul IETF, March 2004.

This document updates procedures described in RFC 2026 and RFC 3710.

This document is a product of the Internet Engineering Steering Group.

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  Mon Oct 11 15:55:27 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Oct 11 15:55:55 2004
Subject: [rfc-dist] RFC 3906 on Calculating Interior Gateway Protocol (IGP)
	Routes Over Traffic Engineering Tunnels
Message-ID: <[e-mail]>


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


        RFC 3906

        Title:      Calculating Interior Gateway Protocol (IGP) Routes
                    Over Traffic Engineering Tunnels
        Author(s):  N. Shen, H. Smit
        Status:     Informational
        Date:       October 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      8
        Characters: 18410
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rtgwg-igp-shortcut-01.txt

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


This document describes how conventional hop-by-hop link-state routing
protocols interact with new Traffic Engineering capabilities to create
Interior Gateway Protocol (IGP) shortcuts.  In particular, this
document describes how Dijkstra's Shortest Path First (SPF) algorithm
can be adapted so that link-state IGPs will calculate IP routes to
forward traffic over tunnels that are set up by Traffic Engineering.

This document is a product of the Routing Area 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 Oct 22 14:36:48 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct 22 14:37:45 2004
Subject: [rfc-dist] RFC 3911 on The Session Initiation Protocol (SIP) "Join"
	Header
Message-ID: <[e-mail]>


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


        RFC 3911

        Title:      The Session Initiation Protocol (SIP)
                    "Join" Header
        Author(s):  R. Mahy, D. Petrie
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      17
        Characters: 35373
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-join-03.txt

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


This document defines a new header for use with SIP multi-party
applications and call control.  The Join header is used to logically
join an existing SIP dialog with a new SIP dialog.  This primitive
can be used to enable a variety of features, for example: "Barge-In",
answering-machine-style "Message Screening" and "Call Center
Monitoring".  Note that 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  Fri Oct 22 14:38:35 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct 22 14:39:54 2004
Subject: [rfc-dist] RFC 3925 on Vendor-Identifying Vendor Options for
	Dynamic Host Configuration Protocol version 4 (DHCPv4)
Message-ID: <[e-mail]>


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


        RFC 3925

        Title:      Vendor-Identifying Vendor Options for
                    Dynamic Host Configuration Protocol version 4
                    (DHCPv4)
        Author(s):  J. Littlefield
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      9
        Characters: 17999
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-dhc-vendor-03.txt

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


The Dynamic Host Configuration Protocol (DHCP) options for Vendor
Class and Vendor-Specific Information can be limiting or ambiguous
when a DHCP client represents multiple vendors.  This document defines
two new options, modeled on the IPv6 options for vendor class and
vendor-specific information, that contain Enterprise Numbers to
remove ambiguity.

This document is a product of the Dynamic Host Configuration 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 Oct 22 14:40:21 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct 22 14:40:34 2004
Subject: [rfc-dist] RFC 3928 on Lightweight Directory Access Protocol (LDAP)
	Client Update Protocol (LCUP)
Message-ID: <[e-mail]>


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


        RFC 3928

        Title:      Lightweight Directory Access Protocol (LDAP)
                    Client Update Protocol (LCUP)
        Author(s):  R. Megginson, Ed., M. Smith, O. Natkovich,
                    J. Parham
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail]
        Pages:      30
        Characters: 36892
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ldup-lcup-06.txt

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


This document defines the Lightweight Directory Access Protocol
(LDAP) Client Update Protocol (LCUP).  The protocol is intended to
allow an LDAP client to synchronize with the content of a directory
information tree (DIT) stored by an LDAP server and to be notified
about the changes to that content.

This document is a product of the LDAP Duplication/Replication/Update
Protocols 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 Oct 22 14:41:34 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct 22 14:43:10 2004
Subject: [rfc-dist] RFC 3929 on Alternative Decision Making Processes for
	Consensus-Blocked Decisions in the IETF
Message-ID: <[e-mail]>


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


        RFC 3929

        Title:      Alternative Decision Making Processes
                    for Consensus-Blocked Decisions in the IETF
        Author(s):  T. Hardie
        Status:     Experimental
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      11
        Characters: 26493
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-hardie-alt-consensus-02.txt

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


This document proposes an experimental set of alternative
decision-making processes for use in IETF working groups.  There
are a small number of cases in IETF working groups in which the
group has come to consensus that a particular decision must be made
but cannot agree on the decision itself.  This document describes
alternative mechanisms for reaching a decision in those cases.  This
is not meant to provide an exhaustive list, but to provide a known set
of tools that can be used when needed.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Oct 22 14:42:38 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct 22 14:44:16 2004
Subject: [rfc-dist] BCP 94,
	RFC 3934 on Updates to RFC 2418 Regarding the Management
	of IETF Mailing Lists
Message-ID: <[e-mail]>


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


        BCP 94
        RFC 3934

        Title:      Updates to RFC 2418 Regarding the Management of
                    IETF Mailing Lists
        Author(s):  M. Wasserman
        Status:     Best Current Practice
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      5
        Characters: 8488
        SeeAlso:    BCP 94

        I-D Tag:    draft-wasserman-rfc2418-ml-update-01.txt

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


This document is an update to RFC 2418 that gives WG chairs explicit
responsibility for managing WG mailing lists.  In particular, it
gives WG chairs the authority to temporarily suspend the mailing list
posting privileges of disruptive individuals.

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 Oct 22 14:43:41 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct 22 14:45:28 2004
Subject: [rfc-dist] BCP 95, RFC 3935 on A Mission Statement for the IETF
Message-ID: <[e-mail]>


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


        BCP 95
        RFC 3935

        Title:      A Mission Statement for the IETF
        Author(s):  H. Alvestrand
        Status:     Best Current Practice
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      7
        Characters: 16639
        SeeAlso:    BCP 95

        I-D Tag:    draft-alvestrand-ietf-mission-02.txt

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


This memo gives a mission statement for the IETF, tries to define the
terms used in the statement sufficiently to make the mission
statement understandable and useful, argues why the IETF needs a
mission statement, and tries to capture some of the debate that led
to this point.

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 Oct 22 14:45:05 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct 22 14:46:28 2004
Subject: [rfc-dist] BCP 96, RFC 3936 on Procedures for Modifying the Resource
	reSerVation Protocol (RSVP)
Message-ID: <[e-mail]>


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


        BCP 96
        RFC 3936

        Title:      Procedures for Modifying the Resource reSerVation
                    Protocol (RSVP)
        Author(s):  K. Kompella, J. Lang
        Status:     Best Current Practice
        Date:       October 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      7
        Characters: 15314
        Updates:    3209, 2205
        SeeAlso:    BCP 96

        I-D Tag:    draft-kompella-rsvp-change-02.txt

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


This memo specifies procedures for modifying the Resource reSerVation
Protocol (RSVP).  This memo also lays out new assignment guidelines
for number spaces for RSVP messages, object classes, class-types, and
sub-objects.

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 Oct 22 14:46:24 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct 22 14:47:38 2004
Subject: [rfc-dist] RFC 3938 on Video-Message Message-Context
Message-ID: <[e-mail]>


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


        RFC 3938

        Title:      Video-Message Message-Context
        Author(s):  T. Hansen
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      4
        Characters: 6224
        Updates:    3458

        I-D Tag:    draft-hansen-lemonade-msgctxt-videomsg-01.txt

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


The Message-Context header defined in RFC 3458 describes the context
of a message (for example: fax-message or voice-message).  This
specification extends the Message-Context header with one additional
context value: "video-message".

A receiving user agent (UA) may use this information as a hint to
optimally present the 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.

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 Oct 22 15:22:28 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Oct 22 15:23:12 2004
Subject: [rfc-dist] RFC 3930 on The Protocol versus Document Points of View
	in Computer Protocols
Message-ID: <[e-mail]>


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


        RFC 3930

        Title:      The Protocol versus Document Points of View in
                    Computer Protocols
        Author(s):  D. Eastlake 3rd
        Status:     Informational
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      15
        Characters: 36892
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-eastlake-proto-doc-pov-05.txt

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


This document contrasts two points of view: the "document" point of
view, where digital objects of interest are like pieces of paper
written and viewed by people, and the "protocol" point of view where
objects of interest are composite dynamic network messages.  Although
each point of view has a place, adherence to a document point of view
can be damaging to protocol design.  By understanding both points of
view, conflicts between them may be clarified and reduced.

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 Oct 26 15:29:50 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Oct 26 15:30:38 2004
Subject: [rfc-dist] RFC 3875 on The Common Gateway Interface (CGI) Version
	1.1
Message-ID: <[e-mail]>


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


        RFC 3975

        Title:      The Common Gateway Interface (CGI) Version 1.1
        Author(s):  D. Robinson, K. Coar
        Status:     Informational
        Date:       October 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      36
        Characters: 80728
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-coar-cgi-v11-04.txt

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


The Common Gateway Interface (CGI) is a simple interface for running
external programs, software or gateways under an information server
in a platform-independent manner.  Currently, the supported
information servers are HTTP servers.

The interface has been in use by the World-Wide Web (WWW) since 1993.
This specification defines the 'current practice' parameters of the
'CGI/1.1' interface developed and documented at the U.S. National
Centre for Supercomputing Applications.  This document also defines
the use of the CGI/1.1 interface on UNIX(R) and other, similar
systems.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Thu Oct 28 10:45:32 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Oct 28 10:46:54 2004
Subject: [rfc-dist] RFC 3954 on Cisco Systems NetFlow Services Export
	Version 9
Message-ID: <[e-mail]>


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


        RFC 3954

        Title:      Cisco Systems NetFlow Services Export Version 9
        Author(s):  B. Claise, Ed.
        Status:     Informational
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      33
        Characters: 76360
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-claise-netflow-9-08.txt

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


This document specifies the data export format for version 9 of
Cisco Systems' NetFlow services, for use by implementations on the
network elements and/or matching collector programs.  The version 9
export format uses templates to provide access to observations
of IP packet flows in a flexible and extensible manner.  A template
defines a collection of fields, with corresponding descriptions of
structure and semantics.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Thu Oct 28 10:47:47 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Thu Oct 28 10:48:11 2004
Subject: [rfc-dist] RFC 3955 on Evaluation of Candidate Protocols for IP
	Flow Information Export (IPFIX)
Message-ID: <[e-mail]>


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


        RFC 3955

        Title:      Evaluation of Candidate Protocols for
                    IP Flow Information Export (IPFIX)
        Author(s):  S. Leinen
        Status:     Informational
        Date:       October 2004
        Mailbox:    [e-mail]
        Pages:      23
        Characters: 55143
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-leinen-ipfix-eval-contrib-03.txt

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


This document contains an evaluation of the five candidate protocols
for an IP Flow Information Export (IPFIX) protocol, based on the
requirements document produced by the IPFIX Working Group.  The
protocols are characterized and grouped in broad categories, and
evaluated against specific requirements.  Finally, a recommendation
is made to select the NetFlow v9 protocol as the basis for the IPFIX
specification.

This document is a product of the IP Flow Information Export 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