[Dime] FW: Protocol Action: 'Diameter User-Name and Realm Based RequestRouting Clarifications' to Proposed Standard
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 26 October 2009 15:56 UTC
Return-Path: <dromasca@avaya.com>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E8E5A3A685D for <dime@core3.amsl.com>; Mon, 26 Oct 2009 08:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.394
X-Spam-Level:
X-Spam-Status: No, score=-2.394 tagged_above=-999 required=5 tests=[AWL=0.205, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ROikYsQfC0P for <dime@core3.amsl.com>; Mon, 26 Oct 2009 08:56:01 -0700 (PDT)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 5522D3A683E for <dime@ietf.org>; Mon, 26 Oct 2009 08:56:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,626,1249272000"; d="scan'208";a="178193050"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 26 Oct 2009 11:56:06 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 26 Oct 2009 11:56:06 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 26 Oct 2009 16:55:45 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401B4C44A@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Dime] Protocol Action: 'Diameter User-Name and Realm Based RequestRouting Clarifications' to Proposed Standard
Thread-Index: AcpWVEyvVpYh3iaYQUC/OjuSZyvBrwAAGFCA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: dime@ietf.org
Subject: [Dime] FW: Protocol Action: 'Diameter User-Name and Realm Based RequestRouting Clarifications' to Proposed Standard
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2009 15:56:02 -0000
Congratulations to the editors, chairs and the whole WG for achieving this milestone. Regards, Dan -----Original Message----- From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of The IESG Sent: Monday, October 26, 2009 5:47 PM To: IETF-Announce Cc: Internet Architecture Board; dime mailing list; dime chair; RFC Editor Subject: [Dime] Protocol Action: 'Diameter User-Name and Realm Based RequestRouting Clarifications' to Proposed Standard The IESG has approved the following document: - 'Diameter User-Name and Realm Based Request Routing Clarifications ' <draft-ietf-dime-nai-routing-04.txt> as a Proposed Standard This document is the product of the Diameter Maintenance and Extensions Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-nai-routing-04.txt Technical Summary 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. Working Group Summary The document fixes a small technical aspect and hence it sailed smoothly through the DIME group. Document Quality This document is the product of the DIME working group. The current implementation status of this specification is, however, unknown. Implementations are expected to arrive to arrive when larger Diameter deployments utilize the RFC 4282 based NAI format. Personnel Hannes Tschofenig is the document shepherd for this document. Dan Romascanu is the responsible AD. RFC Editor Note Please remove RFC3588bis from the Updates line in the header of the document. _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime
- [Dime] FW: Protocol Action: 'Diameter User-Name a… Romascanu, Dan (Dan)