From rfc-ed at ISI.EDU  Fri Feb  1 06:22:27 2008
From: rfc-ed at ISI.EDU (rfc-ed)
Date: Fri, 01 Feb 2008 16:22:27 +0200
Subject: [rfc-dist] Le invito a trabajar en una empresa internacional
	concesionaria de coches.
Message-ID: <01ec01c864dd$df5ca580$b36ed551@dsl.static81213110179.ttnet.net.tr>

gpai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.rfc-editor.org/pipermail/rfc-dist/attachments/20080201/71d456a2/attachment-0001.html

From rfc-editor at rfc-editor.org  Thu Feb  7 15:33:31 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu,  7 Feb 2008 15:33:31 -0800 (PST)
Subject: [rfc-dist] BCP0135,
	RFC 5135 on IP Multicast Requirements for a Network Address
	Translator (NAT) and a Network Address Port Translator (NAPT)
Message-ID: <20080207233331.D8F4710DC79@bosco.isi.edu>


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

        BCP 135        
        RFC 5135

        Title:      IP Multicast Requirements for a 
                    Network Address Translator (NAT) and a 
                    Network Address Port Translator (NAPT) 
        Author:     D. Wing, T. Eckert
        Status:     Best Current Practice
        Date:       February 2008
        Mailbox:    dwing at cisco.com, 
                    eckert at cisco.com
        Pages:      16
        Characters: 36528
        Updates:    
        See-Also:   BCP0135

        I-D Tag:    draft-ietf-behave-multicast-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5135.txt

This document specifies requirements for a for a Network Address
Translator (NAT) and a Network Address Port Translator (NAPT) that
support Any Source IP Multicast or Source-Specific IP Multicast.  An
IP multicast-capable NAT device that adheres to the requirements of
this document can optimize the operation of IP multicast applications
that are generally unaware of IP multicast NAT devices.  This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.

This document is a product of the Behavior Engineering for Hindrance 
Avoidance Working Group of the IETF.

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


This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb  7 15:33:43 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu,  7 Feb 2008 15:33:43 -0800 (PST)
Subject: [rfc-dist] RFC 5107 on DHCP Server Identifier Override Suboption
Message-ID: <20080207233343.C0F2810DC7B@bosco.isi.edu>


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

        
        RFC 5107

        Title:      DHCP Server Identifier Override Suboption 
        Author:     R. Johnson, J. Jumarasamy,
                    K. Kinnear, M. Stapp
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    raj at cisco.com, 
                    jayk at cisco.com, 
                    kkinnear at cisco.com,  mjs at cisco.com
        Pages:      7
        Characters: 14837
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-server-override-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5107.txt

This memo defines a new suboption of the DHCP relay information
option that allows the DHCP relay to specify a new value for the
Server Identifier option, which is inserted by the DHCP Server.  This
allows the DHCP relay to act as the actual DHCP server such that
RENEW DHCPREQUESTs will come to the relay instead of going to the
server directly.  This gives the relay the opportunity to include the
Relay Agent option with appropriate suboptions even on DHCP RENEW
messages.  [STANDARDS TRACK]

This document is a product of the Dynamic Host Configuration
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb  7 15:34:05 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu,  7 Feb 2008 15:34:05 -0800 (PST)
Subject: [rfc-dist] RFC 5125 on Reclassification of RFC 3525 to Historic
Message-ID: <20080207233405.C4B8010DC7D@bosco.isi.edu>


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

        
        RFC 5125

        Title:      Reclassification of RFC 3525 to 
                    Historic 
        Author:     T. Taylor
        Status:     Informational
        Date:       February 2008
        Mailbox:    taylor at nortel.com
        Pages:      4
        Characters: 6646
        Obsoletes:  RFC3525
        See-Also:   

        I-D Tag:    draft-taylor-megaco-obsol3525-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5125.txt

This document reclassifies RFC 3525, Gateway Control Protocol Version
1, to Historic Status.  This memo also obsoletes RFC 3525.  This memo provides information for the Internet community.

INFORMATIONAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Fri Feb  8 17:23:31 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri,  8 Feb 2008 17:23:31 -0800 (PST)
Subject: [rfc-dist] RFC 5118 on Session Initiation Protocol (SIP) Torture
	Test Messages for Internet Protocol Version 6 (IPv6)
Message-ID: <20080209012331.61EC910E2B2@bosco.isi.edu>


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


        RFC 5118

        Title:      Session Initiation Protocol (SIP) Torture 
                    Test Messages for Internet Protocol 
                    Version 6 (IPv6) 
        Author:     V. Gurbani, C. Boulton,
                    R. Sparks
        Status:     Informational
        Date:       February 2008
        Mailbox:    vkg at alcatel-lucent.com, 
                    cboulton at ubiquitysoftware.com, 
                    RjS at estacado.net
        Pages:      18
        Characters: 31829
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sipping-ipv6-torture-tests-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5118.txt

This document provides examples of Session Initiation Protocol (SIP)
test messages designed to exercise and "torture" the code of an
IPv6-enabled SIP implementation.  This memo provides information for the 
Internet community.

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


INFORMATIONAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Fri Feb  8 17:23:41 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri,  8 Feb 2008 17:23:41 -0800 (PST)
Subject: [rfc-dist] RFC 5120 on M-ISIS: Multi Topology (MT) Routing in
	Intermediate System to Intermediate Systems (IS-ISs)
Message-ID: <20080209012341.690F710E2B4@bosco.isi.edu>


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

        
        RFC 5120

        Title:      M-ISIS: Multi Topology (MT) Routing 
                    in Intermediate System to Intermediate Systems 
                    (IS-ISs) 
        Author:     T. Przygienda, N. Shen,
                    N. Sheth
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    prz at net4u.ch, 
                    naiming at cisco.com, 
                    nsheth at juniper.net
        Pages:      14
        Characters: 30318
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-wg-multi-topology-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5120.txt

This document describes an optional mechanism within Intermediate
System to Intermediate Systems (IS-ISs) used today
by many ISPs for IGP routing within their clouds.  This document
describes how to run, within a single IS-IS domain, a set of
independent IP topologies that we call Multi-Topologies (MTs).
This MT extension can be used for a variety of purposes, such as an
in-band management network "on top" of the original IGP topology,
maintaining separate IGP routing domains for isolated multicast or
IPv6 islands within the backbone, or forcing a subset of an address
space to follow a different topology.  [STANDARDS TRACK]

This document is a product of the IS-IS for IP Internets
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb  7 15:33:31 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu,  7 Feb 2008 15:33:31 -0800 (PST)
Subject: [rfc-dist] BCP0135,
	RFC 5135 on IP Multicast Requirements for a Network
	Address	Translator (NAT) and a Network Address Port
	Translator (NAPT)
Message-ID: <20080207233331.D8F4710DC79@bosco.isi.edu>


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

        BCP 135        
        RFC 5135

        Title:      IP Multicast Requirements for a 
                    Network Address Translator (NAT) and a 
                    Network Address Port Translator (NAPT) 
        Author:     D. Wing, T. Eckert
        Status:     Best Current Practice
        Date:       February 2008
        Mailbox:    dwing at cisco.com, 
                    eckert at cisco.com
        Pages:      16
        Characters: 36528
        Updates:    
        See-Also:   BCP0135

        I-D Tag:    draft-ietf-behave-multicast-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5135.txt

This document specifies requirements for a for a Network Address
Translator (NAT) and a Network Address Port Translator (NAPT) that
support Any Source IP Multicast or Source-Specific IP Multicast.  An
IP multicast-capable NAT device that adheres to the requirements of
this document can optimize the operation of IP multicast applications
that are generally unaware of IP multicast NAT devices.  This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.

This document is a product of the Behavior Engineering for Hindrance 
Avoidance Working Group of the IETF.

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


This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Tue Feb 12 11:59:33 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 12 Feb 2008 11:59:33 -0800 (PST)
Subject: [rfc-dist] RFC 5136 on Defining Network Capacity
Message-ID: <20080212195933.C813F10F0CB@bosco.isi.edu>


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

        
        RFC 5136

        Title:      Defining Network Capacity 
        Author:     P. Chimento, J. Ishac
        Status:     Informational
        Date:       February 2008
        Mailbox:    Philip.Chimento at jhuapl.edu, 
                    jishac at nasa.gov
        Pages:      14
        Characters: 30682
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ippm-bw-capacity-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5136.txt

Measuring capacity is a task that sounds simple, but in reality can
be quite complex.  In addition, the lack of a unified nomenclature on
this subject makes it increasingly difficult to properly build, test,
and use techniques and tools built around these constructs.  This
document provides definitions for the terms 'Capacity' and 'Available
Capacity' related to IP traffic traveling between a source and
destination in an IP network.  By doing so, we hope to provide a
common framework for the discussion and analysis of a diverse set of
current and future estimation techniques.  This memo provides information
for the Internet community.

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


INFORMATIONAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Tue Feb 12 11:59:16 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 12 Feb 2008 11:59:16 -0800 (PST)
Subject: [rfc-dist] RFC 5130 on A Policy Control Mechanism in IS-IS Using
	Administrative Tags
Message-ID: <20080212195916.02F7C10F0C9@bosco.isi.edu>


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

        
        RFC 5130

        Title:      A Policy Control Mechanism in 
                    IS-IS Using Administrative Tags 
        Author:     S. Previdi, M. Shand, Ed.,
                    C. Martin
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    sprevidi at cisco.com, 
                    mshand at cisco.com, 
                    chris at ipath.net
        Pages:      8
        Characters: 16284
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-admin-tags-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5130.txt

This document describes an extension to the IS-IS protocol to add
operational capabilities that allow for ease of management and
control over IP prefix distribution within an IS-IS domain.  This
document enhances the IS-IS protocol by extending the information
that an Intermediate System (IS) router can place in Link State
Protocol (LSP) Data Units for policy use.  This extension will
provide operators with a mechanism to control IP prefix distribution
throughout multi-level IS-IS domains.  [STANDARDS TRACK]

This document is a product of the IS-IS for IP Internets
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Tue Feb 12 11:59:06 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 12 Feb 2008 11:59:06 -0800 (PST)
Subject: [rfc-dist] RFC 5121 on Transmission of IPv6 via the IPv6
	Convergence Sublayer over IEEE 802.16 Networks
Message-ID: <20080212195906.51D8D10F0C7@bosco.isi.edu>


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

        
        RFC 5121

        Title:      Transmission of IPv6 via the 
                    IPv6 Convergence Sublayer over IEEE 802.16 
                    Networks 
        Author:     B. Patil, F. Xia,
                    B. Sarikaya, JH. Choi,
                    S. Madanapalli
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    basavaraj.patil at nsn.com, 
                    xiayangsong at huawei.com, 
                    sarikaya at ieee.org,  jinchoe at samsung.com, 
                    smadanapalli at gmail.com
        Pages:      22
        Characters: 50092
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-16ng-ipv6-over-ipv6cs-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5121.txt

IEEE Std 802.16 is an air interface specification for fixed and
mobile Broadband Wireless Access Systems.  Service-specific
convergence sublayers to which upper-layer protocols interface are a
part of the IEEE 802.16 MAC (Medium Access Control).  The Packet
convergence sublayer (CS) is used for the transport of all packet-
based protocols such as Internet Protocol (IP) and IEEE 802.3 LAN/MAN
CSMA/CD Access Method (Ethernet).  IPv6 packets can be sent and
received via the IP-specific part of the Packet CS.  This document
specifies the addressing and operation of IPv6 over the IP-specific
part of the Packet CS for hosts served by a network that utilizes the
IEEE Std 802.16 air interface.  It recommends the assignment of a
unique prefix (or prefixes) to each host and allows the host to use
multiple identifiers within that prefix, including support for
randomly generated interface identifiers.  [STANDARDS TRACK]

This document is a product of the IP over IEEE 802.16 Networks
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb 14 18:10:32 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 14 Feb 2008 18:10:32 -0800 (PST)
Subject: [rfc-dist] RFC 5090 on RADIUS Extension for Digest Authentication
Message-ID: <20080215021032.D17DE113E4C@bosco.isi.edu>


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

        
        RFC 5090

        Title:      RADIUS Extension for Digest Authentication 
        Author:     B. Sterman, D. Sadolevsky,
                    D. Schwartz, D. Williams,
                    W. Beck
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    baruch at kayote.com, 
                    dscreat at dscreat.com, 
                    david at kayote.com,  dwilli at cisco.com, 
                    beckw at t-systems.com
        Pages:      33
        Characters: 68299
        Obsoletes:  RFC4590

        I-D Tag:    draft-ietf-radext-rfc4590bis-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5090.txt

This document defines an extension to the Remote Authentication
Dial-In User Service (RADIUS) protocol to enable support of Digest
Authentication, for use with HTTP-style protocols like the Session
Initiation Protocol (SIP) and HTTP.  [STANDARDS TRACK]

This document is a product of the RADIUS EXTensions
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb 14 18:10:41 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 14 Feb 2008 18:10:41 -0800 (PST)
Subject: [rfc-dist] RFC 5106 on The Extensible Authentication
	Protocol-Internet Key Exchange Protocol version 2 (EAP-IKEv2) Method
Message-ID: <20080215021041.50046113E4E@bosco.isi.edu>


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

        
        RFC 5106

        Title:      The Extensible Authentication Protocol-Internet Key 
                    Exchange Protocol version 2 (EAP-IKEv2) Method 
        Author:     H. Tschofenig, D. Kroeselberg,
                    A. Pashalidis, Y. Ohba,
                    F. Bersani
        Status:     Experimental
        Date:       February 2008
        Mailbox:    Hannes.Tschofenig at nsn.com, 
                    Dirk.Kroeselberg at nsn.com, 
                    pashalidis at nw.neclab.eu,  yohba at tari.toshiba.com, 
                    florent.ftrd at gmail.com
        Pages:      33
        Characters: 76645
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-tschofenig-eap-ikev2-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5106.txt

This document specifies EAP-IKEv2, an Extensible Authentication
Protocol (EAP) method that is based on the Internet Key Exchange
(IKEv2) protocol.  EAP-IKEv2 provides mutual authentication and
session key establishment between an EAP peer and an EAP server.  It
supports authentication techniques that are based on passwords,
high-entropy shared keys, and public key certificates.  EAP-IKEv2
further provides support for cryptographic ciphersuite negotiation, hash
function agility, identity confidentiality (in certain modes of
operation), fragmentation, and an optional "fast reconnect" mode.  This 
memo defines an Experimental Protocol for the Internet community.


EXPERIMENTAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb 14 18:10:49 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 14 Feb 2008 18:10:49 -0800 (PST)
Subject: [rfc-dist] RFC 5119 on A Uniform Resource Name (URN) Namespace for
	the Society of Motion Picture and Television Engineers (SMPTE)
Message-ID: <20080215021049.86BF2113E50@bosco.isi.edu>


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

        
        RFC 5119

        Title:      A Uniform Resource Name (URN) 
                    Namespace for the Society of Motion 
                    Picture and Television Engineers (SMPTE) 
        Author:     T. Edwards
        Status:     Informational
        Date:       February 2008
        Mailbox:    thomas.edwards at fox.com
        Pages:      9
        Characters: 17024
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-edwards-urn-smpte-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5119.txt

This document describes a Uniform Resource Name (URN) namespace for
the Society of Motion Picture and Television Engineers (SMPTE) for
naming persistent resources that SMPTE produces or manages.  A
subnamespace for Universal Labels is specifically described.  This memo 
provides information for the Internet community.


INFORMATIONAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb 14 18:10:57 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 14 Feb 2008 18:10:57 -0800 (PST)
Subject: [rfc-dist] RFC 5219 on A More Loss-Tolerant RTP Payload Format for
	MP3 Audio
Message-ID: <20080215021057.F4230113E52@bosco.isi.edu>


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

        
        RFC 5219

        Title:      A More Loss-Tolerant RTP Payload 
                    Format for MP3 Audio 
        Author:     R. Finlayson
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    finlayson at live555.com
        Pages:      22
        Characters: 42830
        Obsoletes:  RFC3119  

        I-D Tag:    draft-ietf-avt-rfc3119bis-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5219.txt

This document describes an RTP (Real-Time Protocol) payload format for
transporting MPEG (Moving Picture Experts Group) 1 or 2, layer III
audio (commonly known as "MP3").  This format is an alternative to
that described in RFC 2250, and performs better if there is packet
loss.  This document obsoletes RFC 3119, correcting
typographical errors in the "SDP usage" section and pseudo-code
appendices.  [STANDARDS TRACK]

This document is a product of the Audio/Video Transport
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Tue Feb 12 11:59:33 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 12 Feb 2008 11:59:33 -0800 (PST)
Subject: [rfc-dist] RFC 5136 on Defining Network Capacity
Message-ID: <20080212195933.C813F10F0CB@bosco.isi.edu>


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

        
        RFC 5136

        Title:      Defining Network Capacity 
        Author:     P. Chimento, J. Ishac
        Status:     Informational
        Date:       February 2008
        Mailbox:    Philip.Chimento at jhuapl.edu, 
                    jishac at nasa.gov
        Pages:      14
        Characters: 30682
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ippm-bw-capacity-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5136.txt

Measuring capacity is a task that sounds simple, but in reality can
be quite complex.  In addition, the lack of a unified nomenclature on
this subject makes it increasingly difficult to properly build, test,
and use techniques and tools built around these constructs.  This
document provides definitions for the terms 'Capacity' and 'Available
Capacity' related to IP traffic traveling between a source and
destination in an IP network.  By doing so, we hope to provide a
common framework for the discussion and analysis of a diverse set of
current and future estimation techniques.  This memo provides information
for the Internet community.

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


INFORMATIONAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Tue Feb 12 11:59:16 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 12 Feb 2008 11:59:16 -0800 (PST)
Subject: [rfc-dist] RFC 5130 on A Policy Control Mechanism in IS-IS Using
	Administrative	Tags
Message-ID: <20080212195916.02F7C10F0C9@bosco.isi.edu>


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

        
        RFC 5130

        Title:      A Policy Control Mechanism in 
                    IS-IS Using Administrative Tags 
        Author:     S. Previdi, M. Shand, Ed.,
                    C. Martin
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    sprevidi at cisco.com, 
                    mshand at cisco.com, 
                    chris at ipath.net
        Pages:      8
        Characters: 16284
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-admin-tags-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5130.txt

This document describes an extension to the IS-IS protocol to add
operational capabilities that allow for ease of management and
control over IP prefix distribution within an IS-IS domain.  This
document enhances the IS-IS protocol by extending the information
that an Intermediate System (IS) router can place in Link State
Protocol (LSP) Data Units for policy use.  This extension will
provide operators with a mechanism to control IP prefix distribution
throughout multi-level IS-IS domains.  [STANDARDS TRACK]

This document is a product of the IS-IS for IP Internets
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Tue Feb 12 11:59:06 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 12 Feb 2008 11:59:06 -0800 (PST)
Subject: [rfc-dist] RFC 5121 on Transmission of IPv6 via the IPv6
	Convergence Sublayer	over IEEE 802.16 Networks
Message-ID: <20080212195906.51D8D10F0C7@bosco.isi.edu>


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

        
        RFC 5121

        Title:      Transmission of IPv6 via the 
                    IPv6 Convergence Sublayer over IEEE 802.16 
                    Networks 
        Author:     B. Patil, F. Xia,
                    B. Sarikaya, JH. Choi,
                    S. Madanapalli
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    basavaraj.patil at nsn.com, 
                    xiayangsong at huawei.com, 
                    sarikaya at ieee.org,  jinchoe at samsung.com, 
                    smadanapalli at gmail.com
        Pages:      22
        Characters: 50092
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-16ng-ipv6-over-ipv6cs-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5121.txt

IEEE Std 802.16 is an air interface specification for fixed and
mobile Broadband Wireless Access Systems.  Service-specific
convergence sublayers to which upper-layer protocols interface are a
part of the IEEE 802.16 MAC (Medium Access Control).  The Packet
convergence sublayer (CS) is used for the transport of all packet-
based protocols such as Internet Protocol (IP) and IEEE 802.3 LAN/MAN
CSMA/CD Access Method (Ethernet).  IPv6 packets can be sent and
received via the IP-specific part of the Packet CS.  This document
specifies the addressing and operation of IPv6 over the IP-specific
part of the Packet CS for hosts served by a network that utilizes the
IEEE Std 802.16 air interface.  It recommends the assignment of a
unique prefix (or prefixes) to each host and allows the host to use
multiple identifiers within that prefix, including support for
randomly generated interface identifiers.  [STANDARDS TRACK]

This document is a product of the IP over IEEE 802.16 Networks
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Fri Feb 22 17:11:25 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:11:25 -0800 (PST)
Subject: [rfc-dist] RFC 5104 on Codec Control Messages in the RTP
	Audio-Visual Profile with Feedback (AVPF)
Message-ID: <20080223011125.8B2E61158D9@bosco.isi.edu>


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

        
        RFC 5104

        Title:      Codec Control Messages in the 
                    RTP Audio-Visual Profile with Feedback (AVPF) 
        Author:     S. Wenger, U. Chandra,
                    M. Westerlund, B. Burman
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    stewe at stewe.org, 
                    Umesh.1.Chandra at nokia.com, 
                    magnus.westerlund at ericsson.com, 
                    bo.burman at ericsson.com
        Pages:      64
        Characters: 158098
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-avpf-ccm-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5104.txt

This document specifies a few extensions to the messages defined in
the Audio-Visual Profile with Feedback (AVPF).  They are helpful
primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use.  However, some are also
usable in smaller multicast environments and point-to-point calls.

The extensions discussed are messages related to the ITU-T Rec. H.271
Video Back Channel, Full Intra Request, Temporary Maximum Media
Stream Bit Rate, and Temporal-Spatial Trade-off.  [STANDARDS TRACK]

This document is a product of the Audio/Video Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Fri Feb 22 17:11:49 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:11:49 -0800 (PST)
Subject: [rfc-dist] RFC 5138 on A Uniform Resource Name (URN) Namespace for
	the Commission for the Management and Application of
	Geoscience Information (CGI)
Message-ID: <20080223011149.1B1661158DD@bosco.isi.edu>


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

        
        RFC 5138

        Title:      A Uniform Resource Name (URN) 
                    Namespace for the Commission for the 
                    Management and Application of Geoscience Information 
                    (CGI) 
        Author:     S. Cox
        Status:     Informational
        Date:       February 2008
        Mailbox:    Simon.Cox at csiro.au
        Pages:      8
        Characters: 15005
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-sjdcox-cgi-urn-00.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5138.txt

This document describes a URN (Uniform Resource Name) namespace that
is engineered by the Commission for the Management and Application of
Geoscience Information (CGI) for naming (i) persistent resources
published by the CGI and (ii) resources published by organizations
that wish them to be used in the context of services conforming to
protocols and agreements issued by CGI.  The formal Namespace
Identifier (NID) is "cgi".  This memo provides information for the 
Internet community.


INFORMATIONAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Fri Feb 22 17:11:38 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:11:38 -0800 (PST)
Subject: [rfc-dist] RFC 5127 on Aggregation of DiffServ Service Classes
Message-ID: <20080223011138.7AF871158DB@bosco.isi.edu>


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

        
        RFC 5127

        Title:      Aggregation of DiffServ Service Classes 
        Author:     K. Chan, J. Babiarz,
                    F. Baker
        Status:     Informational
        Date:       February 2008
        Mailbox:    khchan at nortel.com, 
                    babiarz at nortel.com, 
                    fred at cisco.com
        Pages:      19
        Characters: 43751
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-diffserv-class-aggr-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5127.txt

In the core of a high-capacity network, service differentiation may
still be needed to support applications' utilization of the network.
Applications with similar traffic characteristics and performance
requirements are mapped into Diffserv service classes based on end-
to-end behavior requirements of the applications.  However, some
network segments may be configured in such a way that a single
forwarding treatment may satisfy the traffic characteristics and
performance requirements of two or more service classes.  In these
cases, it may be desirable to aggregate two or more Diffserv service
classes into a single forwarding treatment.  This document provides
guidelines for the aggregation of Diffserv service classes into
forwarding treatments.  This memo provides information for the Internet 
community.

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


INFORMATIONAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Fri Feb 22 17:13:33 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:13:33 -0800 (PST)
Subject: [rfc-dist] RFC 5122 on Internationalized Resource Identifiers
	(IRIs) and Uniform Resource Identifiers (URIs) for the
	Extensible Messaging and Presence Protocol (XMPP)
Message-ID: <20080223011333.EA3571158E5@bosco.isi.edu>


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

        
        RFC 5122

        Title:      Internationalized Resource Identifiers (IRIs) and 
                    Uniform Resource Identifiers (URIs) for the 
                    Extensible Messaging and Presence Protocol (XMPP) 
        Author:     P. Saint-Andre
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    stpeter at jabber.org
        Pages:      26
        Characters: 55566
        Obsoletes:  RFC4622

        I-D Tag:    draft-saintandre-rfc4622bis-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5122.txt

This document defines the use of Internationalized Resource
Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in
identifying or interacting with entities that can communicate via the
Extensible Messaging and Presence Protocol (XMPP).  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Fri Feb 22 17:12:54 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:12:54 -0800 (PST)
Subject: [rfc-dist] RFC 5124 on Extended Secure RTP Profile for Real-time
	Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)
Message-ID: <20080223011254.3A6D11158E1@bosco.isi.edu>


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

        
        RFC 5124

        Title:      Extended Secure RTP Profile for 
                    Real-time Transport Control Protocol (RTCP)-Based 
                    Feedback (RTP/SAVPF) 
        Author:     J. Ott, E. Carrara
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    jo at comnet.tkk.fi, 
                    carrara at kth.se
        Pages:      18
        Characters: 37856
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-profile-savpf-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5124.txt

An RTP profile (SAVP) for secure real-time communications and
another profile (AVPF) to provide timely feedback from the
receivers to a sender are defined in RFC 3711 and RFC 4585,
respectively.  This memo specifies the combination of both profiles
to enable secure RTP communications with feedback.  [STANDARDS TRACK]

This document is a product of the Audio/Video Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Fri Feb 22 17:13:06 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:13:06 -0800 (PST)
Subject: [rfc-dist] BCP 137, RFC 5137 on ASCII Escaping of Unicode Characters
Message-ID: <20080223011306.5B9631158E3@bosco.isi.edu>


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

        BCP 137        
        RFC 5137

        Title:      ASCII Escaping of Unicode Characters 
        Author:     J. Klensin
        Status:     Best Current Practice
        Date:       February 2008
        Mailbox:    john-ietf at jck.com
        Pages:      13
        Characters: 27742
        See Also:   BCP0137

        I-D Tag:    draft-klensin-unicode-escapes-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5137.txt

There are a number of circumstances in which an escape mechanism is
needed in conjunction with a protocol to encode characters that
cannot be represented or transmitted directly.  With ASCII coding,
the traditional escape has been either the decimal or hexadecimal
numeric value of the character, written in a variety of different
ways.  The move to Unicode, where characters occupy two or more
octets and may be coded in several different forms, has further
complicated the question of escapes.  This document discusses some
options now in use and discusses considerations for selecting one for
use in new IETF protocols, and protocols that are now being
internationalized.  This document specifies an Internet Best Current 
Practices for the Internet Community, and requests discussion and 
suggestions for improvements.


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

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Fri Feb 22 17:12:41 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:12:41 -0800 (PST)
Subject: [rfc-dist] RFC 5143 on Synchronous Optical Network/Synchronous
	Digital Hierarchy (SONET/SDH) Circuit Emulation Service over
	MPLS (CEM) Encapsulation
Message-ID: <20080223011241.AFB3E1158DF@bosco.isi.edu>


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

        
        RFC 5143

        Title:      Synchronous Optical Network/Synchronous Digital 
                    Hierarchy (SONET/SDH) Circuit Emulation Service 
                    over MPLS (CEM) Encapsulation 
        Author:     A. Malis, J. Brayley,
                    J. Shirron, L. Martini,
                    S. Vogelsang
        Status:     Historic
        Date:       February 2008
        Mailbox:    andrew.g.malis at verizon.com, 
                    jeremy.brayley at ecitele.com, 
                    john.shirron at ecitele.com,  lmartini at cisco.com, 
                    steve.vogelsang at alcatel-lucent.com
        Pages:      24
        Characters: 52534
        Obsoleted by: RFC4842

        I-D Tag:    draft-malis-sonet-ces-mpls-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5143.txt

This document describes a historical method for encapsulating
Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH)
Path signals for transport across packet-switched networks (PSNs).
The PSNs explicitly supported by this document include MPLS and
IP.  Note that RFC 4842 describes the standards-track protocol for
this functionality, and new implementations must use RFC 4842 rather
than this document except when interoperability with older
implementations is desired.  This memo defines a Historic 
Document for the Internet community.


HISTORIC: This memo defines a Historic Document 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Fri Feb 22 17:13:57 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:13:57 -0800 (PST)
Subject: [rfc-dist] RFC 5139 on Revised Civic Location Format for Presence
	Information Data Format Location Object (PIDF-LO)
Message-ID: <20080223011357.4A3451158E7@bosco.isi.edu>


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

        
        RFC 5139

        Title:      Revised Civic Location Format for 
                    Presence Information Data Format Location Object 
                    (PIDF-LO) 
        Author:     M. Thomson, J. Winterbottom
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    martin.thomson at andrew.com, 
                    james.winterbottom at andrew.com
        Pages:      14
        Characters: 27470
        Updates:    RFC4119

        I-D Tag:    draft-ietf-geopriv-revised-civic-lo-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5139.txt

This document defines an XML format for the representation of civic
location.  This format is designed for use with Presence Information
Data Format Location Object (PIDF-LO) documents and replaces the
civic location format in RFC 4119.  The format is based on the civic
address definition in PIDF-LO, but adds several new elements based on
the civic types defined for Dynamic Host Configuration Protocol
(DHCP), and adds a hierarchy to address complex road identity
schemes.  The format also includes support for the xml:lang language
tag and restricts the types of elements where appropriate.  
[STANDARDS TRACK]

This document is a product of the Geographic Location/Privacy Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Wed Feb 27 11:39:22 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 27 Feb 2008 11:39:22 -0800 (PST)
Subject: [rfc-dist] RFC 5148 on Jitter Considerations in Mobile Ad Hoc
	Networks (MANETs)
Message-ID: <20080227193922.543CB116EB4@bosco.isi.edu>


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

        
        RFC 5148

        Title:      Jitter Considerations in Mobile Ad 
                    Hoc Networks (MANETs) 
        Author:     T. Clausen, C. Dearlove,
                    B. Adamson
        Status:     Informational
        Date:       February 2008
        Mailbox:    T.Clausen at computer.org, 
                    chris.dearlove at baesystems.com, 
                    adamson at itd.nrl.navy.mil
        Pages:      12
        Characters: 26379
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-manet-jitter-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5148.txt

This document provides recommendations for jittering (randomly
modifying timing) of control traffic transmissions in Mobile Ad hoc
NETwork (MANET) routing protocols to reduce the probability of
transmission collisions.  This memo provides information for the 
Internet community.

This document is a product of the Mobile Ad-hoc Networks Working Group of 
the IETF.


INFORMATIONAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Wed Feb 27 11:39:34 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 27 Feb 2008 11:39:34 -0800 (PST)
Subject: [rfc-dist] RFC 5149 on Service Selection for Mobile IPv6
Message-ID: <20080227193934.11247116EB6@bosco.isi.edu>


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

        
        RFC 5149

        Title:      Service Selection for Mobile IPv6 
        Author:     J. Korhonen, U. Nilsson,
                    V. Devarapalli
        Status:     Informational
        Date:       February 2008
        Mailbox:    jouni.korhonen at teliasonera.com, 
                    ulf.s.nilsson at teliasonera.com, 
                    vijay.devarapalli at azairenet.com
        Pages:      9
        Characters: 18746
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-korhonen-mip6-service-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5149.txt

In some Mobile IPv6 deployments, identifying the mobile node or the
mobility service subscriber is not enough to distinguish between
multiple services possibly provisioned to the said mobile node and
its mobility service subscription.  A capability to specify different
services in addition to the mobile node identity can be leveraged to
provide flexibility for mobility service providers on provisioning
multiple services to one mobility service subscription.  This
document describes a Service Selection Mobility Option for both
conventional Mobile IPv6 and Proxy Mobile IPv6 that is intended to
assist home agents to make a specific service selection for the
mobility service subscription during the binding registration
procedure.  This memo provides information for the Internet community.


INFORMATIONAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Wed Feb 27 11:39:46 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 27 Feb 2008 11:39:46 -0800 (PST)
Subject: [rfc-dist] RFC 5188 on RTP Payload Format for the Enhanced Variable
	Rate Wideband Codec (EVRC-WB) and the Media Subtype Updates
	for EVRC-B Codec
Message-ID: <20080227193946.2AB32116EB8@bosco.isi.edu>


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

        
        RFC 5188

        Title:      RTP Payload Format for the 
                    Enhanced Variable Rate Wideband Codec (EVRC-WB) 
                    and the Media Subtype Updates for 
                    EVRC-B Codec 
        Author:     H. Desineni, Q. Xie
        Status:     Standards Track
        Date:       February 2008 
        Mailbox:    hd at qualcomm.com, 
                    Qiaobing.Xie at Gmail.com
        Pages:      25
        Characters: 44821
        Updates:    RFC4788

        I-D Tag:    draft-ietf-avt-rtp-evrc-wb-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5188.txt

This document specifies Real-time Transport Protocol (RTP) payload
formats to be used for the Enhanced Variable Rate Wideband Codec
(EVRC-WB) and updates the media type registrations for EVRC-B codec.
Several media type registrations are included for EVRC-WB RTP payload
formats.  In addition, a file format is specified for transport of
EVRC-WB speech data in storage mode applications such as email.  
[STANDARDS TRACK]

This document is a product of the Audio/Video Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Fri Feb 22 17:12:41 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:12:41 -0800 (PST)
Subject: [rfc-dist] RFC 5143 on Synchronous Optical Network/Synchronous
	Digital Hierarchy	(SONET/SDH) Circuit Emulation Service over
	MPLS (CEM) Encapsulation
Message-ID: <20080223011241.AFB3E1158DF@bosco.isi.edu>


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

        
        RFC 5143

        Title:      Synchronous Optical Network/Synchronous Digital 
                    Hierarchy (SONET/SDH) Circuit Emulation Service 
                    over MPLS (CEM) Encapsulation 
        Author:     A. Malis, J. Brayley,
                    J. Shirron, L. Martini,
                    S. Vogelsang
        Status:     Historic
        Date:       February 2008
        Mailbox:    andrew.g.malis at verizon.com, 
                    jeremy.brayley at ecitele.com, 
                    john.shirron at ecitele.com,  lmartini at cisco.com, 
                    steve.vogelsang at alcatel-lucent.com
        Pages:      24
        Characters: 52534
        Obsoleted by: RFC4842

        I-D Tag:    draft-malis-sonet-ces-mpls-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5143.txt

This document describes a historical method for encapsulating
Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH)
Path signals for transport across packet-switched networks (PSNs).
The PSNs explicitly supported by this document include MPLS and
IP.  Note that RFC 4842 describes the standards-track protocol for
this functionality, and new implementations must use RFC 4842 rather
than this document except when interoperability with older
implementations is desired.  This memo defines a Historic 
Document for the Internet community.


HISTORIC: This memo defines a Historic Document 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Fri Feb 22 17:13:57 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:13:57 -0800 (PST)
Subject: [rfc-dist] RFC 5139 on Revised Civic Location Format for Presence
	Information	Data Format Location Object (PIDF-LO)
Message-ID: <20080223011357.4A3451158E7@bosco.isi.edu>


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

        
        RFC 5139

        Title:      Revised Civic Location Format for 
                    Presence Information Data Format Location Object 
                    (PIDF-LO) 
        Author:     M. Thomson, J. Winterbottom
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    martin.thomson at andrew.com, 
                    james.winterbottom at andrew.com
        Pages:      14
        Characters: 27470
        Updates:    RFC4119

        I-D Tag:    draft-ietf-geopriv-revised-civic-lo-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5139.txt

This document defines an XML format for the representation of civic
location.  This format is designed for use with Presence Information
Data Format Location Object (PIDF-LO) documents and replaces the
civic location format in RFC 4119.  The format is based on the civic
address definition in PIDF-LO, but adds several new elements based on
the civic types defined for Dynamic Host Configuration Protocol
(DHCP), and adds a hierarchy to address complex road identity
schemes.  The format also includes support for the xml:lang language
tag and restricts the types of elements where appropriate.  
[STANDARDS TRACK]

This document is a product of the Geographic Location/Privacy Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Fri Feb 22 17:12:54 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:12:54 -0800 (PST)
Subject: [rfc-dist] RFC 5124 on Extended Secure RTP Profile for Real-time
	Transport	Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)
Message-ID: <20080223011254.3A6D11158E1@bosco.isi.edu>


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

        
        RFC 5124

        Title:      Extended Secure RTP Profile for 
                    Real-time Transport Control Protocol (RTCP)-Based 
                    Feedback (RTP/SAVPF) 
        Author:     J. Ott, E. Carrara
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    jo at comnet.tkk.fi, 
                    carrara at kth.se
        Pages:      18
        Characters: 37856
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-profile-savpf-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5124.txt

An RTP profile (SAVP) for secure real-time communications and
another profile (AVPF) to provide timely feedback from the
receivers to a sender are defined in RFC 3711 and RFC 4585,
respectively.  This memo specifies the combination of both profiles
to enable secure RTP communications with feedback.  [STANDARDS TRACK]

This document is a product of the Audio/Video Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Fri Feb 22 17:11:25 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:11:25 -0800 (PST)
Subject: [rfc-dist] RFC 5104 on Codec Control Messages in the RTP
	Audio-Visual Profile	with Feedback (AVPF)
Message-ID: <20080223011125.8B2E61158D9@bosco.isi.edu>


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

        
        RFC 5104

        Title:      Codec Control Messages in the 
                    RTP Audio-Visual Profile with Feedback (AVPF) 
        Author:     S. Wenger, U. Chandra,
                    M. Westerlund, B. Burman
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    stewe at stewe.org, 
                    Umesh.1.Chandra at nokia.com, 
                    magnus.westerlund at ericsson.com, 
                    bo.burman at ericsson.com
        Pages:      64
        Characters: 158098
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-avpf-ccm-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5104.txt

This document specifies a few extensions to the messages defined in
the Audio-Visual Profile with Feedback (AVPF).  They are helpful
primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use.  However, some are also
usable in smaller multicast environments and point-to-point calls.

The extensions discussed are messages related to the ITU-T Rec. H.271
Video Back Channel, Full Intra Request, Temporary Maximum Media
Stream Bit Rate, and Temporal-Spatial Trade-off.  [STANDARDS TRACK]

This document is a product of the Audio/Video Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Fri Feb 22 17:13:06 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:13:06 -0800 (PST)
Subject: [rfc-dist] BCP 137, RFC 5137 on ASCII Escaping of Unicode Characters
Message-ID: <20080223011306.5B9631158E3@bosco.isi.edu>


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

        BCP 137        
        RFC 5137

        Title:      ASCII Escaping of Unicode Characters 
        Author:     J. Klensin
        Status:     Best Current Practice
        Date:       February 2008
        Mailbox:    john-ietf at jck.com
        Pages:      13
        Characters: 27742
        See Also:   BCP0137

        I-D Tag:    draft-klensin-unicode-escapes-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5137.txt

There are a number of circumstances in which an escape mechanism is
needed in conjunction with a protocol to encode characters that
cannot be represented or transmitted directly.  With ASCII coding,
the traditional escape has been either the decimal or hexadecimal
numeric value of the character, written in a variety of different
ways.  The move to Unicode, where characters occupy two or more
octets and may be coded in several different forms, has further
complicated the question of escapes.  This document discusses some
options now in use and discusses considerations for selecting one for
use in new IETF protocols, and protocols that are now being
internationalized.  This document specifies an Internet Best Current 
Practices for the Internet Community, and requests discussion and 
suggestions for improvements.


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

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Fri Feb 22 17:13:33 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 22 Feb 2008 17:13:33 -0800 (PST)
Subject: [rfc-dist] RFC 5122 on Internationalized Resource Identifiers
	(IRIs) and Uniform	Resource Identifiers (URIs) for the
	Extensible Messaging and	Presence Protocol (XMPP)
Message-ID: <20080223011333.EA3571158E5@bosco.isi.edu>


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

        
        RFC 5122

        Title:      Internationalized Resource Identifiers (IRIs) and 
                    Uniform Resource Identifiers (URIs) for the 
                    Extensible Messaging and Presence Protocol (XMPP) 
        Author:     P. Saint-Andre
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    stpeter at jabber.org
        Pages:      26
        Characters: 55566
        Obsoletes:  RFC4622

        I-D Tag:    draft-saintandre-rfc4622bis-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5122.txt

This document defines the use of Internationalized Resource
Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in
identifying or interacting with entities that can communicate via the
Extensible Messaging and Presence Protocol (XMPP).  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Thu Feb 28 15:49:28 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 28 Feb 2008 15:49:28 -0800 (PST)
Subject: [rfc-dist] RFC 5123 on Considerations in Validating the Path in BGP
Message-ID: <20080228234928.8FE43117429@bosco.isi.edu>


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

        
        RFC 5123

        Title:      Considerations in Validating the Path 
                    in BGP 
        Author:     R. White, B. Akyol
        Status:     Informational
        Date:       February 2008
        Mailbox:    riw at cisco.com, 
                    bora at cisco.com
        Pages:      16
        Characters: 39948
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-white-pathconsiderations-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5123.txt

This document examines the implications of hop-by-hop forwarding,
route aggregation, and route filtering on the concept of validation
within a BGP Autonomous System (AS) Path.  This memo provides information for the Internet community.


INFORMATIONAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb 28 16:31:38 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 28 Feb 2008 16:31:38 -0800 (PST)
Subject: [rfc-dist] RFC 5144 on A Domain Availability Check (DCHK) Registry
	Type for the Internet Registry Information Service (IRIS)
Message-ID: <20080229003138.0A802117444@bosco.isi.edu>


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

        
        RFC 5144

        Title:      A Domain Availability Check (DCHK) 
                    Registry Type for the Internet Registry 
                    Information Service (IRIS) 
        Author:     A. Newton, M. Sanz
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    andy at arin.net, 
                    sanz at denic.de
        Pages:      17
        Characters: 30063
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-crisp-iris-dchk-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5144.txt

This document describes a lightweight domain availability service
using the Internet Registry Information Service (IRIS) framework and
the data model of the IRIS Domain Registry (DREG) service.  [STANDARDS TRACK]

This document is a product of the Cross Registry Information Service Protocol Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb 28 16:31:42 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 28 Feb 2008 16:31:42 -0800 (PST)
Subject: [rfc-dist] RFC 5150 on Label Switched Path Stitching with
	Generalized Multiprotocol Label Switching Traffic Engineering
	(GMPLS TE)
Message-ID: <20080229003142.7EAA4117446@bosco.isi.edu>


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

        
        RFC 5150

        Title:      Label Switched Path Stitching with 
                    Generalized Multiprotocol Label Switching Traffic
                    Engineering (GMPLS TE) 
        Author:     A. Ayyangar, K. Kompella,
                    JP. Vasseur, A. Farrel
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    arthi at juniper.net, 
                    kireeti at juniper.net, 
                    jpv at cisco.com,  adrian at olddog.co.uk
        Pages:      19
        Characters: 47099
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-lsp-stitching-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5150.txt

In certain scenarios, there may be a need to combine several
Generalized Multiprotocol Label Switching (GMPLS) Label Switched
Paths (LSPs) such that a single end-to-end (e2e) LSP is realized and
all traffic from one constituent LSP is switched onto the next LSP.
We will refer to this as "LSP stitching", the key requirement being
that a constituent LSP not be allocated to more than one e2e LSP.
The constituent LSPs will be referred to as "LSP segments" (S-LSPs).

This document describes extensions to the existing GMPLS signaling
protocol (Resource Reservation Protocol-Traffic Engineering
(RSVP-TE)) to establish e2e LSPs created from S-LSPs, and
describes how the LSPs can be managed using the GMPLS signaling and
routing protocols.

It may be possible to configure a GMPLS node to switch the traffic
from an LSP for which it is the egress, to another LSP for which it is
the ingress, without requiring any signaling or routing extensions
whatsoever and such that the operation is completely transparent to
other nodes.  This will also result in LSP stitching in the data
plane.  However, this document does not cover this scenario of LSP
stitching.  [STANDARDS TRACK]

This document is a product of the Common Control and Measurement Plane Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb 28 16:32:02 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 28 Feb 2008 16:32:02 -0800 (PST)
Subject: [rfc-dist] BCP 37,
	RFC 5237 on IANA Allocation Guidelines for the Protocol Field
Message-ID: <20080229003202.AC9B411744A@bosco.isi.edu>


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

        BCP 37        
        RFC 5237

        Title:      IANA Allocation Guidelines for the 
                    Protocol Field 
        Author:     J. Arkko, S. Bradner
        Status:     Best Current Practice
        Date:       February 2008
        Mailbox:    jari.arkko at piuha.net, 
                    sob at harvard.edu
        Pages:      5
        Characters: 9303
        Updates:    RFC2780
        See Also:   BCP0037

        I-D Tag:    draft-arkko-rfc2780-proto-update-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5237.txt

This document revises the IANA guidelines for allocating new Protocol
field values in IPv4 header.  It modifies the rules specified in RFC
2780 by removing the Expert Review option.  The change will also
affect the allocation of Next Header field values in IPv6.  This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 


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

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb 28 16:31:58 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 28 Feb 2008 16:31:58 -0800 (PST)
Subject: [rfc-dist] RFC 5152 on A Per-Domain Path Computation Method for
	Establishing Inter-Domain Traffic Engineering (TE) Label
	Switched Paths (LSPs)
Message-ID: <20080229003158.47C2C117448@bosco.isi.edu>


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

        
        RFC 5152

        Title:      A Per-Domain Path Computation Method 
                    for Establishing Inter-Domain Traffic Engineering (TE) 
                    Label Switched Paths (LSPs) 
        Author:     JP. Vasseur, Ed.,
                    A. Ayyangar, Ed.,
                      R. Zhang
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    jpv at cisco.com, 
                    arthi at juniper.net, 
                    raymond.zhang at bt.com
        Pages:      21
        Characters: 50563
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-inter-domain-pd-path-comp-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5152.txt

This document specifies a per-domain path computation technique for
establishing inter-domain Traffic Engineering (TE) Multiprotocol
Label Switching (MPLS) and Generalized MPLS (GMPLS) Label Switched
Paths (LSPs).  In this document, a domain refers to a collection of
network elements within a common sphere of address management or path
computational responsibility such as Interior Gateway Protocol (IGP)
areas and Autonomous Systems.

Per-domain computation applies where the full path of an inter-domain
TE LSP cannot be or is not determined at the ingress node of the TE
LSP, and is not signaled across domain boundaries.  This is most
likely to arise owing to TE visibility limitations.  The signaling
message indicates the destination and nodes up to the next domain
boundary.  It may also indicate further domain boundaries or domain
identifiers.  The path through each domain, possibly including the
choice of exit point from the domain, must be determined within the
domain.  [STANDARDS TRACK]

This document is a product of the Common Control and Measurement Plane Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Thu Feb 28 16:36:49 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 28 Feb 2008 16:36:49 -0800 (PST)
Subject: [rfc-dist] RFC 5151 on Inter-Domain MPLS and GMPLS Traffic
	Engineering -- Resource Reservation Protocol-Traffic
	Engineering (RSVP-TE) Extensions
Message-ID: <20080229003649.205DE117450@bosco.isi.edu>


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

        
        RFC 5151

        Title:      Inter-Domain MPLS and GMPLS Traffic 
                    Engineering -- Resource Reservation Protocol-Traffic
                    Engineering (RSVP-TE) Extensions 
        Author:     A. Farrel, Ed.,
                    A. Ayyangar, JP. Vasseur
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    adrian at olddog.co.uk, 
                    arthi at juniper.net, 
                    jpv at cisco.com
        Pages:      25
        Characters: 56663
        Updates:    RFC3209, RFC3473

        I-D Tag:    draft-ietf-ccamp-inter-domain-rsvp-te-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5151.txt

This document describes procedures and protocol extensions for the
use of Resource Reservation Protocol-Traffic Engineering (RSVP-TE)
signaling in Multiprotocol Label Switching-Traffic Engineering
(MPLS-TE) packet networks and Generalized MPLS (GMPLS) packet and
non-packet networks to support the establishment and maintenance of
Label Switched Paths that cross domain boundaries.

For the purpose of this document, a domain is considered to be any
collection of network elements within a common realm of address space
or path computation responsibility.  Examples of such domains include
Autonomous Systems, Interior Gateway Protocol (IGP) routing areas, and
GMPLS overlay networks.  [STANDARDS TRACK]

This document is a product of the Common Control and Measurement Plane Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



From rfc-editor at rfc-editor.org  Fri Feb 29 18:38:33 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 29 Feb 2008 18:38:33 -0800 (PST)
Subject: [rfc-dist] RFC 5098 on Signaling MIB for PacketCable and IPCablecom
	Multimedia Terminal Adapters (MTAs)
Message-ID: <20080301023833.8BC16117840@bosco.isi.edu>


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

        
        RFC 5098

        Title:      Signaling MIB for PacketCable and 
                    IPCablecom Multimedia Terminal Adapters (MTAs) 
        Author:     G. Beacham, S. Kumar,
                    S. Channabasappa
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    gordon.beacham at motorola.com, 
                    satish.kumar at ti.com, 
                    Sumanth at cablelabs.com
        Pages:      79
        Characters: 159415
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipcdn-pktc-signaling-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5098.txt

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines a basic set of managed objects for Simple
Network Management Protocol (SNMP)-based management of PacketCable-
and IPCablecom-compliant Multimedia Terminal Adapter devices.  
[STANDARDS TRACK]

This document is a product of the IP over Cable Data Network Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...