[rfc-dist] (no subject)

[rfc-editor at rfc-editor.org (Rfc-editor)]

An HTML attachment was scrubbed...
URL: http://www.postel.org/pipermail/rfc-dist/attachments/20040809/e176b9c8/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: price_08.zip
Type: application/octet-stream
Size: 5932 bytes
Desc: not available
Url : http://www.postel.org/pipermail/rfc-dist/attachments/20040809/e176b9c8/price_08.obj
From rfc-editor at rfc-editor.org  Tue Aug 17 17:18:24 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 17 17:19:12 2004
Subject: [rfc-dist] RFC 3845 on DNS Security (DNSSEC) NextSECure (NSEC)
	RDATA Format
Message-ID: <[e-mail]>


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


        RFC 3845

        Title:      DNS Security (DNSSEC) NextSECure (NSEC) RDATA
                    Format
        Author(s):  J. Schlyter, Ed.
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail]
        Pages:      7
        Characters: 14793
        Updates:    3755, 2535

        I-D Tag:    draft-ietf-dnsext-nsec-rdata-06.txt

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


This document redefines the wire format of the "Type Bit Map" field
in the DNS NextSECure (NSEC) resource record RDATA format to cover the
full resource record (RR) type space.

This document is a product of the DNS Extensions Working Group of the
IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Aug 17 17:21:38 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 17 17:22:29 2004
Subject: [rfc-dist] RFC 3860 on Common Profile for Instant Messaging (CPIM)
Message-ID: <[e-mail]>


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


        RFC 3860

        Title:      Common Profile for Instant Messaging (CPIM)
        Author(s):  J. Peterson
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail]
        Pages:      13
        Characters: 26486
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-impp-im-04.txt

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


At the time this document was written, numerous instant messaging
protocols were in use, and little interoperability between services
based on these protocols has been achieved.  This specification
defines common semantics and data formats for instant messaging to
facilitate the creation of gateways between instant messaging
services.

This document is a product of the Instant 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.echo 
Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Aug 17 17:20:08 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 17 17:22:32 2004
Subject: [rfc-dist] RFC 3859 on Common Profile for Presence (CPP)
Message-ID: <[e-mail]>


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


        RFC 3859

        Title:      Common Profile for Presence (CPP)
        Author(s):  J. Peterson
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail]
        Pages:      15
        Characters: 30537
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-impp-pres-04.txt

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


At the time this document was written, numerous presence protocols
were in use (largely as components of commercial instant messaging
services), and little interoperability between services based on
these protocols has been achieved.  This specification defines common
semantics and data formats for presence to facilitate the creation of
gateways between presence services.

This document is a product of the Instant 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.echo 
Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Aug 17 17:23:15 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 17 17:24:25 2004
Subject: [rfc-dist] RFC 3861 on Address Resolution for Instant Messaging and
	Presence
Message-ID: <[e-mail]>


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


        RFC 3861

        Title:      Address Resolution for Instant Messaging and
                    Presence
        Author(s):  J. Peterson
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail]
        Pages:      8
        Characters: 15764
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-impp-srv-04.txt

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


Presence and instant messaging are defined in RFC 2778.  The Common
Profiles for Presence and Instant Messaging define two Universal
Resource Identifier (URI) schemes: \'im' for INSTANT INBOXes and
'pres' for PRESENTITIES.  This document provides guidance for locating
the resources associated with URIs that employ these schemes.

This document is a product of the Instant 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.echo 
Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Aug 17 17:24:54 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 17 17:25:29 2004
Subject: [rfc-dist] RFC 3862 on Common Presence and Instant Messaging
	(CPIM): Message Format
Message-ID: <[e-mail]>


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


        RFC 3862

        Title:      Common Presence and Instant Messaging (CPIM):
                    Message Format
        Author(s):  G. Klyne, D. Atkins
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      30
        Characters: 56133
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-impp-cpim-msgfmt-09.txt

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


This memo defines the MIME content type 'Message/CPIM', a message
format for protocols that conform to the Common Profile for Instant
Messaging (CPIM) specification.

This document is a product of the Instant 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.echo 
Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Aug 17 17:26:29 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 17 17:27:12 2004
Subject: [rfc-dist] RFC 3863 on Presence Information Data Format (PIDF)
Message-ID: <[e-mail]>


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


        RFC 3863

        Title:      Presence Information Data Format (PIDF)
        Author(s):  H. Sugano, S. Fujimoto, G. Klyne, A. Bateman,
                    W. Carr, J. Peterson
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail]
        Pages:      28
        Characters: 56956
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-impp-cpim-pidf-08.txt

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


This memo specifies the Common Profile for Presence (CPP) Presence
Information Data Format (PIDF) as a common presence data format for
CPP-compliant Presence protocols, and also defines a new media type
"application/pidf+xml" to represent the XML MIME entity for PIDF.

This document is a product of the Instant 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.echo 
Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Aug 24 16:57:41 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 24 16:57:48 2004
Subject: [rfc-dist] RFC 3833 on Threat Analysis of the Domain Name System
	(DNS)
Message-ID: <[e-mail]>


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


        RFC 3833

        Title:      Threat Analysis of the Domain Name System (DNS)
        Author(s):  D. Atkins, R. Austein
        Status:     Informational
        Date:       August 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      16
        Characters: 39303
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-dnsext-dns-threats-07.txt

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


Although the DNS Security Extensions (DNSSEC) have been under
development for most of the last decade, the IETF has never written
down the specific set of threats against which DNSSEC is designed to
protect.  Among other drawbacks, this cart-before-the-horse situation
has made it difficult to determine whether DNSSEC meets its design
goals, since its design goals are not well specified.  This note
attempts to document some of the known threats to the DNS, and, in
doing so, attempts to measure to what extent (if any) DNSSEC is a
useful tool in defending against these threats.

This document is a product of the DNS Extensions Working Group of the
IETF.  

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Aug 24 16:59:26 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 24 17:00:29 2004
Subject: [rfc-dist] RFC 3869 on IAB Concerns and Recommendations Regarding
	Internet Research and Evolution
Message-ID: <[e-mail]>


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


        RFC 3869

        Title:      IAB Concerns and Recommendations
                    Regarding Internet Research and Evolution
        Author(s):  R. Atkinson, Ed., S. Floyd, Ed., IAB
        Status:     Informational
        Date:       August 2004
        Mailbox:    [e-mail]
        Pages:      30
        Characters: 78250
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-iab-research-funding-03.txt

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


This document discusses IAB concerns that ongoing research is needed
to further the evolution of the Internet infrastructure, and that
consistent, sufficient non-commercial funding is needed to enable
such research.

This document is a product of the Internet Architecture Board.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Wed Aug 25 16:42:48 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Aug 25 16:43:27 2004
Subject: [rfc-dist] RFC 3834 on Recommendations for Automatic Responses to
	Electronic Mail
Message-ID: <[e-mail]>


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


        RFC 3834

        Title:      Recommendations for Automatic Responses to
                    Electronic Mail
        Author(s):  K. Moore
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail]
        Pages:      22
        Characters: 53119
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-moore-auto-email-response-05.txt

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


This memo makes recommendations for software that automatically
responds to incoming electronic mail messages, including "out of the
office" or "vacation" response generators, mail filtering software,
email-based information services, and other automatic responders.  The
purpose of these recommendations is to discourage undesirable behavior
which is caused or aggravated by such software, to encourage uniform
behavior (where appropriate) among automatic mail responders, and to
clear up some sources of confusion among implementors of automatic
email responders.

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 Aug 27 16:55:27 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Aug 27 16:56:21 2004
Subject: [rfc-dist] RFC 3830 on MIKEY: Multimedia Internet KEYing
Message-ID: <[e-mail]>


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


        RFC 3830

        Title:      MIKEY: Multimedia Internet KEYing
        Author(s):  J. Arkko, E. Carrara, F. Lindholm, M. Naslund,
                    K. Norrman
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail],
                    [e-mail],
                    [e-mail],
                    [e-mail],
                    [e-mail]
        Pages:      66
        Characters: 145238
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-msec-mikey-08.txt

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


This document describes a key management scheme that can be used for
real-time applications (both for peer-to-peer communication and group
communication).  In particular, its use to support the Secure
Real-time Transport Protocol is described in detail.

Security protocols for real-time multimedia applications have started
to appear.  This has brought forward the need for a key management
solution to support these protocols.

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

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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 Aug 27 16:57:21 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Aug 27 16:58:14 2004
Subject: [rfc-dist] RFC 3844 on IETF Problem Resolution Process
Message-ID: <[e-mail]>


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


        RFC 3844

        Title:      IETF Problem Resolution Process
        Author(s):  E. Davies, J. Hofmann, Eds.
        Status:     Informational
        Date:       August 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      20
        Characters: 44841
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-problem-process-04.txt

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


This Informational document records the history of discussions
in the Problem WG during 2003 of how to resolve the problems
described in the IETF Problem Statement. It decomposes each of the
problems described into a few areas for improvement and categorizes
them as either problems affecting the routine processes used to create
standards or problems affecting the fundamental structure and
practices of the IETF.  Expeditious and non-disruptive solutions are
proposed for the problems affecting routine processes.

The document also lists suggested ways to handle the development
of solutions for the structure and practices problems proposed
in IETF discussions.  Neither the working group nor the wider
IETF has reached consensus on a recommendation for any of the
proposals. This document therefore has no alternative
but to suggest that the search for structure and
practices solutions be handed back to the control of the
IESG.

While there was working group consensus on the processes for
short-term and medium term improvements, there was no working
group consensus on the proposals for longer-term
improvements.  This document therefore includes longer-term
improvement proposals only as a matter of record; they must
not be regarded as recommendations from the working group.

This document is a product of the Problem Statement 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 Aug 31 08:41:17 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 31 08:41:34 2004
Subject: [rfc-dist] RFC 3840 on Indicating User Agent Capabilities in the
	Session Initiation Protocol (SIP)
Message-ID: <[e-mail]>


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


        RFC 3840

        Title:      Indicating User Agent Capabilities in
                    the Session Initiation Protocol (SIP)
        Author(s):  J. Rosenberg, H. Schulzrinne, P. Kyzivat
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail],
                    [e-mail], [e-mail]
        Pages:      36
        Characters: 81360
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-callee-caps-03.txt

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


This specification defines mechanisms by which a Session Initiation
Protocol (SIP) user agent can convey its capabilities and
characteristics to other user agents and to the registrar for its
domain.  This information is conveyed as parameters of the Contact
header field.

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 Aug 31 08:43:03 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 31 08:43:33 2004
Subject: [rfc-dist] RFC 3841 on Caller Preferences for the Session
	Initiation Protocol (SIP)
Message-ID: <[e-mail]>


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


        RFC 3841

        Title:      Caller Preferences for the Session Initiation
                    Protocol (SIP)
        Author(s):  J. Rosenberg, H. Schulzrinne, P. Kyzivat
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail],
                    [e-mail], [e-mail]
        Pages:      26
        Characters: 61382
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-callerprefs-10.txt

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


This document describes a set of extensions to the Session Initiation
Protocol (SIP) which allow a caller to express preferences about
request handling in servers.  These preferences include the ability to
select which Uniform Resource Identifiers (URI) a request gets routed
to, and to specify certain request handling directives in proxies and
redirect servers.  It does so by defining three new request header
fields, Accept-Contact, Reject-Contact, and Request-Disposition,
which specify the caller's preferences.

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 Aug 31 08:44:29 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 31 08:45:46 2004
Subject: [rfc-dist] RFC 3842 on A Message Summary and Message Waiting
	Indication Event Package for the Session Initiation Protocol (SIP)
Message-ID: <[e-mail]>


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


        RFC 3842

        Title:      A Message Summary and Message Waiting Indication
                    Event Package for the Session Initiation Protocol
                    (SIP)
        Author(s):  R. Mahy
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail]
        Pages:      19
        Characters: 36877
        Updates/Obsoletes/SeeAlso:    None

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

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


This document describes a Session Initiation Protocol (SIP) event
package to carry message waiting status and message summaries from a
messaging system to an interested User Agent.

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 Aug 31 08:47:04 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 31 08:47:45 2004
Subject: [rfc-dist] Correction: RFC 3842 on A Message Summary and Message
	Waiting Indication Event Package for the Session Initiation
	Protocol (SIP)
Message-ID: <[e-mail]>


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


        RFC 3842

        Title:      A Message Summary and Message Waiting Indication
                    Event Package for the Session Initiation Protocol
                    (SIP)
        Author(s):  R. Mahy
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail]
        Pages:      19
        Characters: 36877
        Updates/Obsoletes/SeeAlso:    None

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

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


This document describes a Session Initiation Protocol (SIP) event
package to carry message waiting status and message summaries from a
messaging system to an interested User Agent.

This document is a product of the Session Initiation Proposal
Investigation Working Group of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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 Aug 31 08:49:20 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 31 08:49:32 2004
Subject: [rfc-dist] RFC 3856 on A Presence Event Package for the Session
	Initiation Protocol (SIP)
Message-ID: <[e-mail]>


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


        RFC 3856

        Title:      A Presence Event Package for the Session
                    Initiation Protocol (SIP)
        Author(s):  J. Rosenberg
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail]
        Pages:      27
        Characters: 62956
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-simple-presence-10.txt

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


This document describes the usage of the Session Initiation Protocol
(SIP) for subscriptions and notifications of presence.  Presence is
defined as the willingness and ability of a user to communicate with
other users on the network.  Historically, presence has been limited
to "on-line" and "off-line" indicators; the notion of presence here
is broader.  Subscriptions and notifications of presence are supported
by defining an event package within the general SIP event
notification framework.  This protocol is also compliant with the
Common Presence Profile (CPP) framework.

This document is a product of the SIP for Instant Messaging and
Presence Leveraging Extensions 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 Aug 31 08:51:33 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 31 08:54:02 2004
Subject: [rfc-dist] RFC 3857 on A Watcher Information Event Template-Package
	for the Session Initiation Protocol (SIP)
Message-ID: <[e-mail]>


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


        RFC 3857

        Title:      A Watcher Information Event Template-Package for
                    the Session Initiation Protocol (SIP)
        Author(s):  J. Rosenberg
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail]
        Pages:      20
        Characters: 46221
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-simple-winfo-package-05.txt

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


This document defines the watcher information template-package for the
Session Initiation Protocol (SIP) event framework.  Watcher
information refers to the set of users subscribed to a particular
resource within a particular event package.  Watcher information
changes dynamically as users subscribe, unsubscribe, are approved, or
are rejected.  A user can subscribe to this information, and therefore
learn about changes to it.  This event package is a template-package
because it can be applied to any event package, including itself.

This document is a product of the SIP for Instant Messaging and
Presence Leveraging Extensions 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 Aug 31 08:53:25 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 31 08:55:08 2004
Subject: [rfc-dist] RFC 3858 on An Extensible Markup Language (XML) Based
	Format for Watcher Information
Message-ID: <[e-mail]>


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


        RFC 3858

        Title:      An Extensible Markup Language (XML) Based Format
                    for Watcher Information
        Author(s):  J. Rosenberg
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [e-mail]
        Pages:      13
        Characters: 26416
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-simple-winfo-format-04.txt

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


Watchers are defined as entities that request (i.e., subscribe to)
information about a resource.  There is fairly complex state
associated with these subscriptions.  The union of the state for all
subscriptions to a particular resource is called the watcher
information for that resource.  This state is dynamic, changing as
subscribers come and go.  As a result, it is possible, and indeed
useful, to subscribe to the watcher information for a particular
resource.  In order to enable this, a format is needed to describe the
state of watchers on a resource.  This specification describes an
Extensible Markup Language (XML) document format for such state.

This document is a product of the SIP for Instant Messaging and
Presence Leveraging Extensions 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 Aug 31 16:44:44 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 31 16:45:39 2004
Subject: [rfc-dist] RFC 3835 on An Architecture for Open Pluggable Edge
	Services (OPES)
Message-ID: <[e-mail]>


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


        RFC 3835

        Title:      An Architecture for Open Pluggable Edge Services
                    (OPES)
        Author(s):  A. Barbir, R. Penno, R. Chen, M. Hofmann, H. Orman
        Status:     Informational
        Date:       August 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail]
        Pages:      17
        Characters: 36113
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-opes-architecture-04.txt

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


This memo defines an architecture that enables the creation of an
application service in which a data provider, a data consumer, and
zero or more application entities cooperatively implement a data
stream service.

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 Aug 31 16:46:10 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 31 16:46:36 2004
Subject: [rfc-dist] RFC 3836 on Requirements for Open Pluggable Edge
	Services (OPES) Callout Protocols
Message-ID: <[e-mail]>


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


        RFC 3836

        Title:      Requirements for Open Pluggable Edge Services
                    (OPES) Callout Protocols
        Author(s):  A. Beck, M. Hofmann, H. Orman, R. Penno, A. Terzis
        Status:     Informational
        Date:       August 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail]
        Pages:      13
        Characters: 28438
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-opes-protocol-reqs-03.txt

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


This document specifies the requirements that the OPES (Open
Pluggable Edge Services) callout protocol must satisfy in order to
support the remote execution of OPES services.  The requirements are
intended to help evaluate possible protocol candidates, as well as
to guide the development of such protocols.

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 Aug 31 16:47:39 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 31 16:48:41 2004
Subject: [rfc-dist] RFC 3837 on Security Threats and Risks for Open
	Pluggable Edge Services (OPES)
Message-ID: <[e-mail]>


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


        RFC 3837

        Title:      Security Threats and Risks for Open Pluggable Edge
                    Services (OPES)
        Author(s):  A. Barbir, O. Batuner, B. Srinivas, M. Hofmann,
                    H. Orman
        Status:     Informational
        Date:       August 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail],
                    [e-mail], [e-mail]
        Pages:      14
        Characters: 31883
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-opes-threats-03.txt

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


The document investigates the security threats associated with
the Open Pluggable Edge Services (OPES) and discusses the
effects of security threats on the underlying architecture.  The main
goal of this document is threat discovery and analysis.  The document
does not specify or recommend any solutions.

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 Aug 31 16:49:11 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Aug 31 16:49:38 2004
Subject: [rfc-dist] RFC 3838 on Policy, Authorization,
	and Enforcement Requirements of the Open Pluggable Edge
	Services (OPES)
Message-ID: <[e-mail]>


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


        RFC 3838

        Title:      Policy, Authorization, and Enforcement
                    Requirements of the Open Pluggable Edge Services
                    (OPES)
        Author(s):  A. Barbir, O. Batuner, A. Beck, T. Chan, H. Orman
        Status:     Informational
        Date:       August 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail]
        Pages:      17
        Characters: 38739
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-opes-authorization-03.txt

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


This document describes policy, authorization, and enforcement
requirements for the selection of the services to be applied to a
given Open Pluggable Edge Services (OPES) flow.

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