Subject: Forward: RFC 5729 on Clarifications on the Routing of Diameter Requests Based on the Username and the Realm

From: RFC Editor <[email-masked]>
Date: Tue, 23 Feb 2010 16:21:16 -0800

Greetings All,

Please note that we are resending this RFC announcement because were
notified that it did not appear in the ietf-announce archives. 	Please
note that the date of publication is December 2009.

Please let us know if you have any questions.

Thank you.

RFC Editor/sg

On Wed, Dec 23, 2009 at 10:46:03AM -0800, RFC Editor wrote:
> 
> A new Request for Comments is now available in online RFC libraries.
> 
>         
>         RFC 5729
> 
>         Title:      Clarifications on the Routing of 
>                     Diameter Requests Based on the Username 
>                     and the Realm 
>         Author:     J. Korhonen, Ed.,
>                     M. Jones, L. Morand,
>                       T. Tsou
>         Status:     Standards Track
>         Date:       December 2009
>         Mailbox:    [email-masked], 
>                     [email-masked], 
>                     [email-masked],  [email-masked]
>         Pages:      11
>         Characters: 23482
>         Updates:    RFC3588
> 
>         I-D Tag:    draft-ietf-dime-nai-routing-04.txt
> 
>         URL:        http://www.rfc-editor.org/rfc/rfc5729.txt
> 
> This specification defines the behavior required of Diameter agents
> to route requests when the User-Name Attribute Value Pair contains a
> Network Access Identifier formatted with multiple realms.  These
> multi-realm, or "Decorated", Network Access Identifiers are used in
> order to force the routing of request messages through a predefined
> list of mediating realms.  [STANDARDS TRACK]
> 
> This document is a product of the Diameter Maintanence and 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-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   http://www.ietf.org/mailman/listinfo/ietf-announce
>   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to [email-masked].  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> USC/Information Sciences Institute
>