[rfc-dist] RFC 3975 on OMA-IETF Standardization Collaboration

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

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


        RFC 3975

        Title:      OMA-IETF Standardization Collaboration
        Author(s):  G. Huston, Ed., I. Leuca, Ed.
        Status:     Informational
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail]
        Pages:      9
        Characters: 16926
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-iab-oma-liaison-00.txt

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


This document describes the standardization collaboration between the
Open Mobile Alliance (OMA) and the Internet Engineering Task Force
(IETF).

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.

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 Feb  2 12:42:06 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Feb  2 12:43:25 2005
Subject: [rfc-dist] RFC 3988 on Maximum Transmission Unit Signalling
	Extensions for the Label Distribution Protocol
Message-ID: <[e-mail]>


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


        RFC 3988

        Title:      Maximum Transmission Unit Signalling Extensions
                    for the Label Distribution Protocol
        Author(s):  B. Black, K. Kompella
        Status:     Experimental
        Date:       January 2005
        Mailbox:    [e-mail], [e-mail]
        Pages:      9
        Characters: 18841
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mpls-ldp-mtu-extensions-03.txt

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


Proper functioning of RFC 1191 path Maximum Transmission Unit (MTU)
discovery requires that IP routers have knowledge of the MTU for each
link to which they are connected.  As currently specified, the Label
Distribution Protocol (LDP) does not have the ability to signal the
MTU for a Label Switched Path (LSP) to the ingress Label Switching
Router (LSR).  In the absence of this functionality, the MTU for each
LSP must be statically configured by network operators or by
equivalent off-line mechanisms.

This document specifies experimental extensions to LDP in support
of LSP MTU discovery.

This document is a product of the Multiprotocol Label Switching
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  Wed Feb  2 12:43:41 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Feb  2 12:44:40 2005
Subject: [rfc-dist] RFC 3994 on Indication of Message Composition for
	Instant Messaging
Message-ID: <[e-mail]>


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


        RFC 3994

        Title:      Indication of Message Composition for
                    Instant Messaging
        Author(s):  H. Schulzrinne
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    [e-mail]
        Pages:      13
        Characters: 27472
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-simple-iscomposing-03.txt

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


In instant messaging (IM) systems, it is useful to know during an IM
conversation whether the other party is composing a message; e.g.,
typing or recording an audio message.  This document defines a new
status message content type and XML namespace that conveys
information about a message being composed.  The status message can
indicate the composition of a message of any type, including text,
voice, or video.  The status messages are delivered to the instant
messaging recipient in the same manner as the instant messages
themselves.

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  Fri Feb  4 16:30:14 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Feb  4 16:30:44 2005
Subject: [rfc-dist] RFC 3984 on RTP Payload Format for H.264 Video
Message-ID: <[e-mail]>


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


        RFC 3984

        Title:      RTP Payload Format for H.264 Video
        Author(s):  S. Wenger, M.M. Hannuksela, T. Stockhammer,
                    M. Westerlund, D. Singer
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    [e-mail], [e-mail],
                    [e-mail],
                    [e-mail], [e-mail]
        Pages:      83
        Characters: 205093
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-avt-rtp-h264-11.txt

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


This memo describes an RTP Payload format for the ITU-T
Recommendation H.264 video codec and the technically identical
ISO/IEC International Standard 14496-10 video codec.  The RTP
payload format allows for packetization of one or more Network
Abstraction Layer Units (NALUs), produced by an H.264 video encoder,
in each RTP payload.  The payload format has wide applicability, as it
supports applications from simple low bit-rate conversational usage,
to Internet video streaming with interleaved transmission, to high
bit-rate video-on-demand.

This document is a product of the Audio/Video 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  Mon Feb  7 16:50:30 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Feb  7 16:50:53 2005
Subject: [rfc-dist] RFC 3980 on T11 Network Address Authority (NAA) Naming
	Format for iSCSI Node Names
Message-ID: <[e-mail]>


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


        RFC 3980

        Title:      T11 Network Address Authority (NAA) Naming Format
                    for iSCSI Node Names
        Author(s):  M. Krueger, M. Chadalapaka, R. Elliott
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      8
        Characters: 14056
        Updates:    3720

        I-D Tag:    draft-ietf-ips-iscsi-name-ext-05.txt

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


Internet Small Computer Systems Interface (iSCSI) is a SCSI transport
protocol that maps the SCSI family of protocols onto TCP/IP.  This
document defines an additional iSCSI node name type
format to enable use of the "Network Address Authority" (NAA)
worldwide naming format defined by the InterNational Committee for
Information Technology Standards (INCITS) T11 - Fibre Channel
(FC) protocols and used by Serial Attached SCSI (SAS).  This
document updates RFC 3720.

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

This is now a Proposed Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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 Feb  9 16:07:33 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Feb  9 16:17:12 2005
Subject: [rfc-dist] RFC 3949 on File Format for Internet Fax
Message-ID: <[e-mail]>


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


        RFC 3949

        Title:      File Format for Internet Fax
        Author(s):  R. Buckley, D. Venable, L. McIntyre, G. Parsons,
                    J. Rafferty
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail]
        Pages:      84
        Characters: 204903
        Obsoletes:  2301

        I-D Tag:    draft-ietf-fax-tiff-fx-14.txt

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


This document is a revised version of RFC 2301.  The revisions,
summarized in the list attached as Annex B, are based
on discussions and suggestions for improvements that have been
made since RFC 2301 was issued in March 1998, and on the results of
independent implementations and interoperability testing.

This RFC 2301 revision describes the Tag Image File Format (TIFF)
representation of image data specified by the International
Telecommunication Union (ITU-T) Recommendations for black-and-white
and color facsimile.  This file format specification is commonly known
as TIFF for Fax eXtended (TIFF-FX).  It formally defines minimal,
extended, and lossless Joint Bi-level Image experts Group (JBIG)
profiles (Profiles S, F, J) for black-and-white fax and base JPEG,
lossless JBIG, and Mixed Raster Content profiles (Profiles C, L, M)
for color and grayscale fax.  These profiles correspond to the content
of the applicable ITU-T Recommendations.

This document is a product of the Internet Fax Working Group of the
IETF.

This is now a Draft Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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 Feb  9 16:09:15 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Feb  9 16:17:36 2005
Subject: [rfc-dist] RFC 3950 on Tag Image File Format Fax eXtended (TIFF-FX)
	- image/tiff-fx MIME Sub-type Registration
Message-ID: <[e-mail]>


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


        RFC 3950

        Title:      Tag Image File Format Fax eXtended (TIFF-FX) -
                    image/tiff-fx MIME Sub-type Registration
        Author(s):  L. McIntyre, G. Parsons, J. Rafferty
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      8
        Characters: 13884
        Obsoletes:  3250

        I-D Tag:    draft-ietf-fax-tiff-fx-reg-v2-01.txt

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


This document describes the registration of the MIME sub-type
image/tiff-fx.  The encodings are defined by File Format for Internet
Fax and its extensions.

This document is a product of the Internet Fax Working Group of the
IETF.

This is now a Draft Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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 Feb  9 16:14:32 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Wed Feb  9 16:17:50 2005
Subject: [rfc-dist] RFC 3302 on Tag Image File Format (TIFF) - image/tiff
	MIME Sub-type Registration
Message-ID: <[e-mail]>



        RFC 3302

        Title:      Tag Image File Format (TIFF) - image/tiff
                    MIME Sub-type Registration
        Author(s):  G. Parsons, J. Rafferty
        Date:       September 2002
        Mailbox:    [e-mail], [e-mail] 
        Pages:      8
        Characters: 15183
        Obsoletes:  2302

        I-D Tag:    draft-ietf-fax-tiff-regbis-05.txt

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


This document describes the registration of the MIME sub-type
image/tiff.  This document refines an earlier sub-type registration in
RFC 1528.

This document obsoletes RFC 2302.

This document has been elevated to a Draft Standard Protocol.

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

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

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

        To: [e-mail]
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

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


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Mon Feb 14 15:45:02 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Feb 14 15:47:49 2005
Subject: [rfc-dist] RFC 4002 on IANA Registration for Enumservice 'web' and
	'ft'
Message-ID: <[e-mail]>


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


        RFC 4002

        Title:      IANA Registration for Enumservice 'web' and 'ft'
        Author(s):  R. Brandner, L. Conroy, R. Stastny
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      10
        Characters: 18072
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-enum-webft-01.txt

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


This document registers the Enumservices 'web' and 'ft' by using the
URI schemes 'http:', 'https:' and 'ftp:' as per the IANA
registration process defined in the ENUM specification (RFC 3761).

This document is a product of the Telephone Number Mapping 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 Feb 14 15:46:37 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Feb 14 15:47:51 2005
Subject: [rfc-dist] RFC 4003 on GMPLS Signaling Procedure for Egress Control
Message-ID: <[e-mail]>


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


        RFC 4003

        Title:      GMPLS Signaling Procedure for Egress Control
        Author(s):  L. Berger
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    [e-mail]
        Pages:      5
        Characters: 10306
        Updates:    3473

        I-D Tag:    draft-ietf-enum-webft-01.txt

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


This document clarifies the procedures for the control of the label
used on an output/downstream interface of the egress node of a Label
Switched Path (LSP).  This control is also known as "Egress Control".
Support for Egress Control is implicit in Generalized Multi-Protocol
Label Switching (GMPLS) Signaling.  This document clarifies the
specification of GMPLS Signaling and does not modify GMPLS signaling
mechanisms and procedures.

This document is a product of the Common Control and Measurement Plane
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 Feb 14 15:48:18 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Feb 14 15:49:16 2005
Subject: [rfc-dist] RFC 3961 on Encryption and Checksum Specifications for
	Kerberos 5
Message-ID: <[e-mail]>


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


        RFC 3961

        Title:      Encryption and Checksum Specifications
                    for Kerberos 5
        Author(s):  K. Raeburn
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    [e-mail]
        Pages:      50
        Characters: 111865
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-krb-wg-crypto-07.txt

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


This document describes a framework for defining encryption and
checksum mechanisms for use with the Kerberos protocol, defining an
abstraction layer between the Kerberos protocol and related
protocols, and the actual mechanisms themselves.  The document also
defines several mechanisms.  Some are taken from RFC 1510,
modified in form to fit this new framework and occasionally modified
in content when the old specification was incorrect.  New mechanisms
are presented here as well.  This document does NOT indicate which
mechanisms may be considered "required to implement".

This document is a product of the Kerberos Working Group 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 Feb 14 15:50:14 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Feb 14 15:51:36 2005
Subject: [rfc-dist] RFC 3962 on Advanced Encryption Standard (AES)
	Encryption for Kerberos 5
Message-ID: <[e-mail]>


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


        RFC 3962

        Title:      Advanced Encryption Standard (AES) Encryption for
                    Kerberos 5
        Author(s):  K. Raeburn
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    [e-mail]
        Pages:      16
        Characters: 32844
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-raeburn-krb-rijndael-krb-07.txt

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


The United States National Institute of Standards and Technology
(NIST) has chosen a new Advanced Encryption Standard (AES), which is
significantly faster and (it is believed) more secure than the old
Data Encryption Standard (DES) algorithm.  This document is a
specification for the addition of this algorithm to the Kerberos
cryptosystem suite.

This document is a product of the Kerberos Working Group 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 Feb 14 15:51:58 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Mon Feb 14 15:53:47 2005
Subject: [rfc-dist] RFC 3990 on Configuration and Provisioning for Wireless
	Access Points (CAPWAP) Problem Statement
Message-ID: <[e-mail]>


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


        RFC 3990

        Title:      Configuration and Provisioning for Wireless Access
                    Points (CAPWAP) Problem Statement
        Author(s):  B. O'Hara, P. Calhoun, J. Kempf
        Status:     Informational
        Date:       February 2005
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      5
        Characters: 11854
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-capwap-problem-statement-02.txt

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


This document describes the Configuration and Provisioning for
Wireless Access Points (CAPWAP) problem statement.

This document is a product of the Control And Provisioning of Wireless
Access Points 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 Feb 15 09:17:02 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Feb 15 09:17:48 2005
Subject: [rfc-dist] Correction: RFC 4003 on GMPLS Signaling Procedure for
	Egress Control
Message-ID: <[e-mail]>


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


        RFC 4003

        Title:      GMPLS Signaling Procedure for Egress Control
        Author(s):  L. Berger
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    [e-mail]
        Pages:      5
        Characters: 10306
        Updates:    3473

        I-D Tag:    draft-ietf-ccamp-gmpls-egress-control-03.txt

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


This document clarifies the procedures for the control of the label
used on an output/downstream interface of the egress node of a Label
Switched Path (LSP).  This control is also known as "Egress Control".
Support for Egress Control is implicit in Generalized Multi-Protocol
Label Switching (GMPLS) Signaling.  This document clarifies the
specification of GMPLS Signaling and does not modify GMPLS signaling
mechanisms and procedures.

This document is a product of the Common Control and Measurement Plane
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 Feb 15 18:18:41 2005
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue, 15 Feb 2005 18:18:41 -0800
Subject: [rfc-dist] RFC 4014 on Remote Authentication Dial-In User Service
	(RADIUS) Attributes Suboption for the Dynamic Host
	Configuration Protocol (DHCP) Relay Agent Information Option
Message-ID: <[e-mail]>

RETRIEVE: rfc
DOC-ID: rfc4014
-------------- next part --------------