From wwwrun@core3.amsl.com Fri May 1 09:59:18 2009 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id DB3333A6C0C; Fri, 1 May 2009 09:59:18 -0700 (PDT) X-idtracker: yes To: IETF-Announce From: The IESG Message-Id: <20090501165918.DB3333A6C0C@core3.amsl.com> Date: Fri, 1 May 2009 09:59:18 -0700 (PDT) Cc: dime@ietf.org Subject: [Dime] Last Call: draft-ietf-dime-mip6-split (Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction) to Proposed Standard X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: ietf@ietf.org List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 May 2009 16:59:19 -0000 The IESG has received a request from the Diameter Maintenance and Extensions WG (dime) to consider the following document: - 'Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2009-05-15. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-17.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14871&rfc_flag=0 From wwwrun@core3.amsl.com Fri May 1 10:18:40 2009 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 3243A3A70FF; Fri, 1 May 2009 10:18:40 -0700 (PDT) X-idtracker: yes To: IETF-Announce From: The IESG Message-Id: <20090501171840.3243A3A70FF@core3.amsl.com> Date: Fri, 1 May 2009 10:18:40 -0700 (PDT) Cc: dime@ietf.org Subject: [Dime] Last Call: draft-ietf-dime-mip6-split (Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction) to Proposed Standard X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: ietf@ietf.org List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 May 2009 17:18:40 -0000 The IESG has received a request from the Diameter Maintenance and Extensions WG (dime) to consider the following document: - 'Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. The document includes references to RFC 4285 and RFC 5149 which are Informational RFCs. Please send substantive comments to the ietf@ietf.org mailing lists by 2009-05-15. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-17.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14871&rfc_flag=0 From Hannes.Tschofenig@gmx.net Wed May 6 11:32:13 2009 Return-Path: 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 9762E3A6E9A for ; Wed, 6 May 2009 11:32:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.115 X-Spam-Level: X-Spam-Status: No, score=-1.115 tagged_above=-999 required=5 tests=[AWL=-0.931, BAYES_40=-0.185, HTML_MESSAGE=0.001] 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 iGNl2kH80FRr for ; Wed, 6 May 2009 11:32:06 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 078D73A6B5B for ; Wed, 6 May 2009 11:23:49 -0700 (PDT) Received: (qmail invoked by alias); 06 May 2009 18:25:15 -0000 Received: from a91-154-108-144.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.108.144] by mail.gmx.net (mp012) with SMTP; 06 May 2009 20:25:15 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX1/fVhkYppHfVl4nGtYq1oCfX9GJwJN9+T7nLZA5re S8vG1TURfz5fRF From: "Hannes Tschofenig" To: Date: Wed, 6 May 2009 21:26:54 +0300 Message-ID: <018701c9ce78$3bb45080$0301a8c0@nsnintra.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0188_01C9CE91.61018880" X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcnOeDr83sKhjGnPSfu6Q57GjA/Hsg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Y-GMX-Trusted: 0 X-FuHaFi: 0.71,0.72 Subject: [Dime] DIME Interim Teleconference X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 18:32:13 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0188_01C9CE91.61018880 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wednesday, June 3, 2009, 8:00-9:30 EDT (12:00-13:30 GMT), DIME will be having a teleconference interim meeting. The agenda, slides and dial-in information for this meeting will be posted to the DIME wiki page at: http://trac.tools.ietf.org/wg/dime/trac/wiki ------=_NextPart_000_0188_01C9CE91.61018880 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable DIME Interim Teleconference

On Wednesday, June 3, 2009, = 8:00-9:30 EDT (12:00-13:30 GMT), DIME will be having a teleconference = interim meeting.

The agenda, slides and dial-in = information for this meeting will be posted to the DIME wiki page = at:
http://trac.tools.ietf.org/wg/dime/trac/wiki

------=_NextPart_000_0188_01C9CE91.61018880-- From root@core3.amsl.com Wed May 6 12:45:01 2009 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 458443A6898; Wed, 6 May 2009 12:45:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090506194501.458443A6898@core3.amsl.com> Date: Wed, 6 May 2009 12:45:01 -0700 (PDT) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-rfc3588bis-17.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 19:45:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter Base Protocol Author(s) : V. Fajardo, et al. Filename : draft-ietf-dime-rfc3588bis-17.txt Pages : 159 Date : 2009-05-06 The Diameter base protocol is intended to provide an Authentication, Authorization and Accounting (AAA) framework for applications such as network access or IP mobility in both local and roaming situations. This document specifies the message format, transport, error reporting, accounting and security services used by all Diameter applications. The Diameter base protocol as defined in this document must be supported by all Diameter implementations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-rfc3588bis-17.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-rfc3588bis-17.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-05-06123936.I-D@ietf.org> --NextPart-- From root@core3.amsl.com Thu May 7 09:30:01 2009 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 6B02628C2E1; Thu, 7 May 2009 09:30:01 -0700 (PDT) From: IESG Secretary To: ietf-announce@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20090507163001.6B02628C2E1@core3.amsl.com> Date: Thu, 7 May 2009 09:30:01 -0700 (PDT) Cc: dime@ietf.org Subject: [Dime] DIME Interim Teleconference X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 16:30:01 -0000 On Wednesday, June 3, 2009, 8:00-9:30 EDT (12:00-13:30 GMT), DIME will be having a teleconference interim meeting. The agenda, slides and dial-in information for this meeting will be posted to the DIME wiki page at: http://trac.tools.ietf.org/wg/dime/trac/wiki From root@core3.amsl.com Thu May 7 10:15:01 2009 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id CE0DA3A6C97; Thu, 7 May 2009 10:15:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090507171501.CE0DA3A6C97@core3.amsl.com> Date: Thu, 7 May 2009 10:15:01 -0700 (PDT) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-diameter-qos-08.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 17:15:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter Quality of Service Application Author(s) : D. Sun, et al. Filename : draft-ietf-dime-diameter-qos-08.txt Pages : 58 Date : 2009-05-07 This document describes the framework, messages and procedures for the Diameter Quality of Service (QoS) application. The Diameter QoS application allows network elements to interact with Diameter servers when allocating QoS resources in the network. In particular, two modes of operation -- Pull and Push -- are defined. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-diameter-qos-08.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-diameter-qos-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-05-07100422.I-D@ietf.org> --NextPart-- From root@core3.amsl.com Sun May 10 11:45:01 2009 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 4EEEF3A6ED9; Sun, 10 May 2009 11:45:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090510184501.4EEEF3A6ED9@core3.amsl.com> Date: Sun, 10 May 2009 11:45:01 -0700 (PDT) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-nai-routing-02.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 May 2009 18:45:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter User-Name and Realm Based Request Routing Clarifications Author(s) : J. Korhonen, et al. Filename : draft-ietf-dime-nai-routing-02.txt Pages : 10 Date : 2009-05-10 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-nai-routing-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-nai-routing-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-05-10113748.I-D@ietf.org> --NextPart-- From Hannes.Tschofenig@gmx.net Mon May 18 06:41:17 2009 Return-Path: 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 2B9F23A7037 for ; Mon, 18 May 2009 06:41:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.078 X-Spam-Level: ** X-Spam-Status: No, score=2.078 tagged_above=-999 required=5 tests=[BAYES_50=0.001, SUBJ_ALL_CAPS=2.077] 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 C0SxQW3RtQag for ; Mon, 18 May 2009 06:41:16 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 4A1CC3A6F97 for ; Mon, 18 May 2009 06:40:50 -0700 (PDT) Received: (qmail invoked by alias); 18 May 2009 13:42:24 -0000 Received: from 207.47.37.41.static.nextweb.net (EHLO 4FIL42860) [207.47.37.41] by mail.gmx.net (mp062) with SMTP; 18 May 2009 15:42:24 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX1/K0p4OnxjKet6ycCEZcUOXrNw8otcA0HpB/8O037 oPDmH8sCINNi9c From: "Hannes Tschofenig" To: Date: Mon, 18 May 2009 16:44:06 +0300 Message-ID: <000501c9d7be$b86ab9d0$1d00a8c0@nsnintra.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcnXvrZi2MKccSSxQf+Oi60VKb2fUA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Y-GMX-Trusted: 0 X-FuHaFi: 0.51 Subject: [Dime] DIME WG STATUS UPDATE (MAY 2009) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2009 13:41:17 -0000 On Wednesday, June 3, 2009, 8:00-9:30 EDT (12:00-13:30 GMT), DIME will be having a teleconference interim meeting. draft-ietf-dime-diameter-api - Victor helped Dave to update the document and a new version got submitted. Document is in "Waiting for AD Go-Ahead::AD Followup" state. Next step: Dan will put the document on the next telechat (June 4th) after checking the resolved comments. draft-ietf-dime-nai-routing - Very recently updated and ready to submitted. Hannes is PROTO shepherd. Next step: Hannes to submit the document to the IESG. draft-ietf-dime-rfc3588bis - Victor updated the document to reflect discussion during the IETF meeting on Diameter versioning. Next step: Group to review outcome and confirm made changes. IANA allocation for draft-ietf-dime-rfc3588bis - Next step: Hannes to write a document ASAP. draft-ietf-dime-qos-attributes - Document is in AD Evaluation. Next step: IESG to perform reviews. draft-ietf-dime-diameter-qos - Victor did a PROTO shepherd review and posted review comments. Comments have been addressed with recent draft update. Next step: Victor to confirm that he is OK with the updated draft. draft-ietf-dime-qos-parameters - Responded to the DISCUSS by Adrian Farrel Next step: Adrian to decide whether the provided resolution fulfills his expectations. draft-ietf-dime-app-design-guide - Still pending a draft update. Next step: Hannes to update the draft. draft-ietf-dime-erp - Waiting for HOKEY to conclude their architectural discussions. Next step: Hannes to ping HOKEY group for status update. draft-ietf-dime-pmip6 - Latest document addressed all the comments. Next step: Hannes to submit document to the IESG. Check dependency from 3GPP. draft-ietf-dime-mip6-split - New IETF LC again. Finished by now (2009-05-15) Pasi cleared his discuss. Document is technically through the IESG. Next step: It is on Dan' todo-list for today. Group confirmed that the following documents should be added to DIME charter: 1) draft-brockners-diameter-nat-control-00.txt 2) draft-zorn-dime-capablities-update-00 3) draft-zorn-dime-diameter-base-protocol-mib-05 4) draft-zorn-dime-diameter-cc-appl-mib-05.txt Next step: Hannes to ask the group for interest in reviewing and contributing to these documents. Dan suggests to add the MIB work immediately to the charter. Next step: Glen to re-submit the documents with draft-ietf-dime-... filename. Item (1) and (2) will be added as re-chartering and they will be discussed as a charter update. Next step: Hannes to write an updated charter text. From wwwrun@core3.amsl.com Tue May 19 06:42:10 2009 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id D01A128C381; Tue, 19 May 2009 06:42:10 -0700 (PDT) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20090519134210.D01A128C381@core3.amsl.com> Date: Tue, 19 May 2009 06:42:10 -0700 (PDT) Cc: Internet Architecture Board , dime mailing list , dime chair , RFC Editor Subject: [Dime] Protocol Action: 'Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction' to Proposed Standard X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 13:42:10 -0000 The IESG has approved the following document: - 'Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction ' 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-mip6-split-17.txt Technical Summary This document specifies the interactions between the Mobile IP Home Agent and the Diameter server (AAA) in the case where the network access service and the mobility service is not in the same administrative domain. The purpose of the interactions is to bootstrap the mobile node from the MSP as part of the authentication and/or authorization process. The document defines new diameter applications to support IKEv2 and MIPv6 authentication protocol. It defines diameter messages, AVPs and command codes to carry the authentication, authorization and bootstrapping attributes. Working Group Summary There was consensus in the WG to publish the document. Document Quality The document has been sent for review to MEXT. This document is part of the solution for Mobile IPv6 bootstrapping problem defined in RFC 4640. It has received extensive reviews from DIME WG members. Donald Eastlake pwerformed the Security Review. Personnel Victor Fajardo is the document shepherd, Dan Romascanu the Shepherding AD. From dromasca@avaya.com Tue May 19 07:42:13 2009 Return-Path: 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 934633A69C5 for ; Tue, 19 May 2009 07:42:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.499 X-Spam-Level: X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 3osh9XVeGQa2 for ; Tue, 19 May 2009 07:42:12 -0700 (PDT) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 93D193A67C0 for ; Tue, 19 May 2009 07:42:12 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,215,1241409600"; d="scan'208";a="171319431" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 19 May 2009 10:43:47 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 19 May 2009 10:43:47 -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: Tue, 19 May 2009 16:43:39 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dime] Protocol Action: 'Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction' to Proposed Standard Thread-Index: AcnYh+6i0X9xZOIyR6mz3rRr3XHf6QACBdRw From: "Romascanu, Dan (Dan)" To: Subject: [Dime] FW: Protocol Action: 'Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction' to Proposed Standard X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 14:42:13 -0000 Congratulations to the editors, shepherd, chairs and to the whole working group for the approval of this standard. Dan =20 -----Original Message----- From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of The IESG Sent: Tuesday, May 19, 2009 4:42 PM To: IETF-Announce Cc: Internet Architecture Board; dime mailing list; dime chair; RFC Editor Subject: [Dime] Protocol Action: 'Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction' to Proposed Standard The IESG has approved the following document: - 'Diameter Mobile IPv6: Support for Home Agent to Diameter Server=20 Interaction ' as a Proposed Standard This document is the product of the Diameter Maintenance and Extensions Working Group.=20 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-mip6-split-17.txt Technical Summary This document specifies the interactions between the Mobile IP Home Agent and the Diameter server (AAA) in the case where the network access service and the mobility service is not in the same administrative domain. The purpose of the interactions is to bootstrap the mobile node from the MSP as part of the authentication and/or authorization process. The document defines new diameter applications to support IKEv2 and MIPv6 authentication protocol. It defines diameter messages, AVPs and command codes to carry the authentication, authorization and bootstrapping attributes. Working Group Summary There was consensus in the WG to publish the document. Document Quality The document has been sent for review to MEXT. This document is part of the solution for Mobile IPv6 bootstrapping problem defined in RFC 4640. It has received extensive reviews from DIME WG members. Donald Eastlake pwerformed the Security Review.=20 Personnel Victor Fajardo is the document shepherd, Dan Romascanu the Shepherding AD. _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime From Hannes.Tschofenig@gmx.net Tue May 19 12:08:04 2009 Return-Path: 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 84EF53A69F6 for ; Tue, 19 May 2009 12:08:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001] 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 vFFkmTWQ739a for ; Tue, 19 May 2009 12:08:04 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id E47AC3A65A5 for ; Tue, 19 May 2009 12:08:03 -0700 (PDT) Received: (qmail invoked by alias); 19 May 2009 19:02:40 -0000 Received: from w229.z065106072.sjc-ca.dsl.cnc.net (EHLO 4FIL42860) [65.106.72.229] by mail.gmx.net (mp066) with SMTP; 19 May 2009 21:02:40 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX183sc5qb4o3HYouPOOh2tI8AbcxLQJZItDQI5yxH/ Te2fjYnALsQqrQ From: "Hannes Tschofenig" To: Date: Tue, 19 May 2009 22:04:11 +0300 Message-ID: <018e01c9d8b4$aa05f5c0$1d00a8c0@nsnintra.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Thread-Index: AcnYtJg8tUGbvDaCRgq/O05HcE68UQ== X-Y-GMX-Trusted: 0 X-FuHaFi: 0.76 Cc: dime@ietf.org Subject: [Dime] Diameter ERP - Status X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 19:08:04 -0000 Dear Hokey Group, I would like to learn more about the status of your architectural investigations to make progress on the Diameter ERP document. A few months back I was told that the Hokey group will do a write-up of the architectural aspects. Ciao Hannes From fqhuang@huawei.com Wed May 20 20:11:52 2009 Return-Path: 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 A4B0A3A6E97 for ; Wed, 20 May 2009 20:11:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.111 X-Spam-Level: X-Spam-Status: No, score=0.111 tagged_above=-999 required=5 tests=[AWL=0.850, BAYES_20=-0.74, HTML_MESSAGE=0.001] 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 Z0s068lu2jAp for ; Wed, 20 May 2009 20:11:48 -0700 (PDT) Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id DAB083A6A89 for ; Wed, 20 May 2009 20:11:47 -0700 (PDT) Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJZ00IN74YB0K@szxga03-in.huawei.com> for dime@ietf.org; Thu, 21 May 2009 11:13:23 +0800 (CST) Received: from huawei.com ([172.24.1.33]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJZ002I04YBEA@szxga03-in.huawei.com> for dime@ietf.org; Thu, 21 May 2009 11:13:23 +0800 (CST) Received: from h36145c ([10.70.39.73]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJZ00HMR4YBFV@szxml06-in.huawei.com> for dime@ietf.org; Thu, 21 May 2009 11:13:23 +0800 (CST) Date: Thu, 21 May 2009 11:13:23 +0800 From: Fortune HUANG To: dime@ietf.org Message-id: <005001c9d9c2$19739da0$4927460a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Office Outlook 11 Content-type: multipart/alternative; boundary="Boundary_(ID_l4d72QMS5AihEXrw+pDkeA)" Thread-index: AcnZwhlBQxKfTw+pTPiqBwj2CrgQ1g== Subject: [Dime] one Diameter application or two for the Rr reference point? X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2009 03:11:52 -0000 This is a multi-part message in MIME format. --Boundary_(ID_l4d72QMS5AihEXrw+pDkeA) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Dear all, In ETSI TISPAN RACS architecture, we have a Diameter based Rr reference point between two x-RACFs. The Rr reference point supports two models: 1) Request Model: where one x-RACF instance solicits the admission decision and resource reservation (e.g. initial reservation, modification, release) from another x-RACF instance that is also responsible for the admission control of those resources within that network segment. The request model can only operate with the per-request level, and doesn't require an explicit pre-delegation process of responsabilities. 2) Delegated model: where one x-RACF instance explicitly delegates responsibility for a bulk of resources to another x-RACF instance, which thereby becomes responsible for the admission control for those resources without the need to further involve the other instance. Each pair of x-RACFs can only have the Rr reference point supporting either the Request Model or the Delegated model but not both. For the Request Model, the Rr reference point should be SESSION_STATE_MAINTAINED, but for the Delegated model, the Rr reference point should be SESSION_STATE_NOT_MAINTAINED. And the messages and parameters will be very different between the two models. My question is: should we have only one Diameter application supporting both models or two different Diameter applications for each model of the Rr reference point? I would be very grateful if someone here can give me some guidance on this question. BTW, I also had a look at draft-ietf-dime-app-design-guide-08, but couldn't find the answer. Maybe we could abstract some guideline on how to solve this kind of questions and add them to draft-ietf-dime-app-design-guide after this question is well solved. Best Regards, Fortune --Boundary_(ID_l4d72QMS5AihEXrw+pDkeA) Content-type: text/html; charset=US-ASCII Content-transfer-encoding: 7BIT
Dear all,
 
In ETSI TISPAN RACS architecture, we have a Diameter based Rr reference point between two x-RACFs.
The Rr reference point supports two models:
1) Request Model: where one x-RACF instance solicits the admission decision and resource reservation (e.g. initial reservation, modification, release) from another x-RACF instance that is also responsible for the admission control of those resources within that network segment. The request model can only operate with the per-request level, and doesn’t require an explicit pre-delegation process of responsabilities.
2) Delegated model: where one x-RACF instance explicitly delegates responsibility for a bulk of resources to another x-RACF instance, which thereby becomes responsible for the admission control for those resources without the need to further involve the other instance.
 
Each pair of x-RACFs can only have the Rr reference point supporting either the Request Model or the Delegated model but not both.
For the Request Model, the Rr reference point should be SESSION_STATE_MAINTAINED, but for the Delegated model, the Rr reference point should be SESSION_STATE_NOT_MAINTAINED. And the messages and parameters will be very different between the two models.
 
My question is: should we have only one Diameter application supporting both models or two different Diameter applications for each model of the Rr reference point?
 
I would be very grateful if someone here can give me some guidance on this question.
 
BTW, I also had a look at draft-ietf-dime-app-design-guide-08, but couldn't find the answer. Maybe we could abstract some guideline on how to solve this kind of questions and add them to draft-ietf-dime-app-design-guide after this question is well solved.
 
 
Best Regards,
Fortune
 
 
 
 
 
 
 
 
 
 
 
 
 
--Boundary_(ID_l4d72QMS5AihEXrw+pDkeA)-- From vfajardo@tari.toshiba.com Fri May 22 05:14:00 2009 Return-Path: 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 5E9543A7021; Fri, 22 May 2009 05:14:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.841 X-Spam-Level: X-Spam-Status: No, score=-3.841 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001] 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 ED-qLJzY7kUY; Fri, 22 May 2009 05:13:59 -0700 (PDT) Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by core3.amsl.com (Postfix) with ESMTP id D11623A6F8A; Fri, 22 May 2009 05:13:58 -0700 (PDT) Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp with ESMTP id n4MCFX9j019860; Fri, 22 May 2009 21:15:33 +0900 (JST) Received: (from root@localhost) by arc11.toshiba.co.jp id n4MCFWCd000178; Fri, 22 May 2009 21:15:32 +0900 (JST) Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id XAA00177; Fri, 22 May 2009 21:15:32 +0900 Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp with ESMTP id n4MCFWhd022854; Fri, 22 May 2009 21:15:32 +0900 (JST) Received: from ivp1.toshiba.co.jp by toshiba.co.jp id n4MCFWT3001461; Fri, 22 May 2009 21:15:32 +0900 (JST) Received: from ext-gw.toshiba.co.jp by ivp1.toshiba.co.jp with ESMTP id n4MCFVXS011706; Fri, 22 May 2009 21:15:31 +0900 (JST) Received: from toshi17.tari.toshiba.com (tari-gw [172.30.24.10]) by ext-gw.toshiba.co.jp with ESMTP id n4MCFUGx002966; Fri, 22 May 2009 21:15:30 +0900 (JST) Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10]) by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id n4MCHJ53059193; Fri, 22 May 2009 08:17:20 -0400 (EDT) (envelope-from vfajardo@tari.toshiba.com) Message-ID: <4A169760.5010400@tari.toshiba.com> Date: Fri, 22 May 2009 08:15:28 -0400 From: Victor Fajardo User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: OPS ADs , IETF-IESG-Support via RT Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "dime@ietf.org" Subject: [Dime] PROTO Writeup for draft-ietf-dime-diameter-qos-08.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2009 12:14:00 -0000 PROTO WRITEUP for draft-ietf-dime-diameter-qos-08.txt ====================================================== (1.a) Who is the Document Shepherd for this document? Has the Document Shepherd personally reviewed this version of the document and, in particular, does he or she believe this version is ready for forwarding to the IESG for publication? The document shepherd is Victor Fajardo. I have personally reviewed the document and I believe it is ready for publication. (1.b) Has the document had adequate review both from key WG members and from key non-WG members? Does the Document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? This document defines a new Diameter QoS application. It is designed to provide a general method for signaling QoS authorization decisions and associated QoS parameters. Since it encompasses a very visible and highly used aspect of the core network, it has had thorough review from WG members as well as participants from other SDOs who maybe impacted by the work. The document shepherd has no concerns about the depth of the reviews. (1.c) Does the Document Shepherd have concerns that the document needs more review from a particular or broader perspective, e.g., security, operational complexity, someone familiar with AAA, internationalization, or XML? There are no concerns with this document. (1.d) Does the Document Shepherd have any specific concerns or issues with this document that the Responsible Area Director and/or the IESG should be aware of? For example, perhaps he or she is uncomfortable with certain parts of the document, or has concerns whether there really is a need for it. In any event, if the WG has discussed those issues and has indicated that it still wishes to advance the document, detail those concerns here. Has an IPR disclosure related to this document been filed? If so, please include a reference to the disclosure and summarize the WG discussion and conclusion on this issue. There are no concerns with this document. (1.e) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? There is consensus in the WG behind the document. The problem space is well understood and the solution is acceptable to the WG, as well as other interested SDOs. (1.f) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarize the areas of conflict in separate email messages to the Responsible Area Director. (It should be in a separate email because this questionnaire is entered into the ID Tracker.) There is no opposition to this document. (1.g) Has the Document Shepherd personally verified that the document satisfies all ID nits? (See http://www.ietf.org/ID-Checklist.html and http://tools.ietf.org/tools/idnits/.) Boilerplate checks are not enough; this check needs to be thorough. Has the document met all formal review criteria it needs to, such as the MIB Doctor, media type, and URI type reviews? If the document does not already indicate its intended status at the top of the first page, please indicate the intended status here. The document does not contain nits. (1.h) Has the document split its references into normative and informative? Are there normative references to documents that are not ready for advancement or are otherwise in an unclear state? If such normative references exist, what is the strategy for their completion? Are there normative references that are downward references, as described in [RFC3967]? If so, list these downward references to support the Area Director in the Last Call procedure for them [RFC3967]. The document has been split into normative and informative references. There are normative references that are work in progress. These are the following: [I-D.ietf-dime-qos-attributes] Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M., and A. Lior, "Quality of Service Attributes for Diameter", draft-ietf-dime-qos-attributes-08 (work in progress), October 2008. [I-D.ietf-dime-qos-parameters] Korhonen, J. and H. Tschofenig, "Quality of Service Parameters for Usage with the AAA Framework", draft-ietf-dime-qos-parameters-07 (work in progress), November 2008. It is expected that these referenced documents will complete standardization well before the diameter-qos application document. There are no normative references that are downward referenced. (1.i) Has the Document Shepherd verified that the document's IANA Considerations section exists and is consistent with the body of the document? If the document specifies protocol extensions, are reservations requested in appropriate IANA registries? Are the IANA registries clearly identified? If the document creates a new registry, does it define the proposed initial contents of the registry and an allocation procedure for future registrations? Does it suggest a reasonable name for the new registry? See [RFC2434]. If the document describes an Expert Review process, has the Document Shepherd conferred with the Responsible Area Director so that the IESG can appoint the needed Expert during IESG Evaluation? The document has an IANA considerations section that is consistent with the body. The document only request allocations of new Application-Id, Command codes and AVP codes in the IETF namespace. Following RFC 3588, IETF consensus is required for the block allocations needed in this doc. The consensus process given to this doc by the DIME WG serves as consensus for IANA allocation requirements. (1.j) Has the Document Shepherd verified that sections of the document that are written in a formal language, such as XML code, BNF rules, MIB definitions, etc., validate correctly in an automated checker? The document contains ABNF rules specified in RFC 3588. The ABNF content has been validated. (1.k) The IESG approval announcement includes a Document Announcement Write-Up. Please provide such a Document Announcement Write-Up. Recent examples can be found in the "Action" announcements for approved documents. The approval announcement contains the following sections: Technical Summary The document specifies a framework, messages and AVPs for performing QoS authorization operations. It defines a QoS Diameter application that allows network elements (QoS aware routers) to interact with Diameter servers to authorize QoS request. It has been designed to operate in both 'Push' or 'Pull' mode where QoS authorization state is either sent to the network element pro-actively (Push) or the network element directly request QoS authorization from the Diameter server. A set of commands and AVPs has been defined to support both operating modes. A supplemental state machine that augments the Diameter base protocol (RFC3588) state machine has also been defined to cleanly support Push mode operations. The document also describes QoS authorization session establishment as well as re-authorization. It provides examples and call flows that describes how QoS authorization can be used other applications (e.g. NSLP, SIP). Working Group Summary There was consensus in the WG to publish the document. Document Quality The document has been sent for review to NSIS and relevant QoS folks. This document defines a core component of a Network Operators QoS architecture and thus have gone through a long review process both within DIME WG and outside of it. It has also traversed several re-start iteration before its current acceptable state. Personnel Victor Fajardo is the document shepherd for this document. From glenzorn@comcast.net Tue May 19 21:03:14 2009 Return-Path: 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 AA6013A683B for ; Tue, 19 May 2009 21:03:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.402 X-Spam-Level: X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[AWL=0.197, 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 DKqrj8xGCIDY for ; Tue, 19 May 2009 21:03:07 -0700 (PDT) Received: from QMTA06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by core3.amsl.com (Postfix) with ESMTP id 636F33A6D74 for ; Tue, 19 May 2009 21:03:06 -0700 (PDT) Received: from OMTA08.westchester.pa.mail.comcast.net ([76.96.62.12]) by QMTA06.westchester.pa.mail.comcast.net with comcast id tPSc1b0070Fqzac56g4kdt; Wed, 20 May 2009 04:04:44 +0000 Received: from gwzPC ([124.121.210.197]) by OMTA08.westchester.pa.mail.comcast.net with comcast id tg4P1b0034G5J6s3Ug4YgT; Wed, 20 May 2009 04:04:42 +0000 From: "Glen Zorn" To: "'Hannes Tschofenig'" , References: <018e01c9d8b4$aa05f5c0$1d00a8c0@nsnintra.net> In-Reply-To: <018e01c9d8b4$aa05f5c0$1d00a8c0@nsnintra.net> Date: Wed, 20 May 2009 11:02:40 +0700 Message-ID: <005a01c9d8ff$de3560b0$9aa02210$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcnYtJg8tUGbvDaCRgq/O05HcE68UQASi9Xg Content-Language: en-us X-Mailman-Approved-At: Sat, 23 May 2009 10:34:33 -0700 Cc: dime@ietf.org Subject: Re: [Dime] [HOKEY] Diameter ERP - Status X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2009 04:03:14 -0000 Hannes Tschofenig [mailto://Hannes.Tschofenig@gmx.net] writes: > Dear Hokey Group, > Dear Hannes. > I would like to learn more about the status of your architectural > investigations to make progress on the Diameter ERP document. > > A few months back I was told that the Hokey group will do a write-up of > the architectural aspects. A few months back (& several times since) I have told you that this would be carried out (if adopted by the WG) after rechartering (if any) and that the rechartering discussions will begin once all the existing hokey work items are complete. This is expected to be between now and IETF 75. > > Ciao > Hannes > > _______________________________________________ > HOKEY mailing list > HOKEY@ietf.org > https://www.ietf.org/mailman/listinfo/hokey From Hannes.Tschofenig@gmx.net Sat May 23 10:18:03 2009 Return-Path: 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 B88C63A6C5E for ; Sat, 23 May 2009 10:18:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.852 X-Spam-Level: X-Spam-Status: No, score=-1.852 tagged_above=-999 required=5 tests=[AWL=-0.123, BAYES_00=-2.599, SARE_MLH_Stock1=0.87] 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 nUVai9aAXJHY for ; Sat, 23 May 2009 10:18:03 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 8A9163A6BF8 for ; Sat, 23 May 2009 10:18:02 -0700 (PDT) Received: (qmail invoked by alias); 23 May 2009 16:51:39 -0000 Received: from a91-154-108-144.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.108.144] by mail.gmx.net (mp015) with SMTP; 23 May 2009 18:51:39 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX19WiZsddmZWmQo2hvCRD9AVlFXoJjFX5T3xrSOn5Y Iz05zRbHjPZlr0 From: "Hannes Tschofenig" To: "Hannes Tschofenig" Date: Sat, 23 May 2009 19:53:25 +0300 Message-ID: <020601c9dbc6$ff1a96f0$9402020a@nsnintra.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcnZarQ2i0+iNOKESDS/pgVv6JxJaACW7vXg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Y-GMX-Trusted: 0 X-FuHaFi: 0.57 X-Mailman-Approved-At: Sat, 23 May 2009 10:34:33 -0700 Subject: [Dime] FW: Stockholm IETF Code Sprint X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2009 17:18:04 -0000 Hi all, Is there interest to get together on the Saturday before the IETF meeting (in relationship to the IETF Code Sprint) todo some coding/interop testing? Ciao Hannes >-----Original Message----- >From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On >Behalf Of IETF Chair >Sent: 20 May, 2009 18:00 >To: IETF Announcement list >Cc: ietf@ietf.org >Subject: Stockholm IETF Code Sprint > >Stockholm IETF Code Sprint > >When: July 15, 2009, begining at 9:30 AM > >Where: IETF Hotel in Stockholm > >What: A bunch of hackers get together to work on code for the IETF web > site. Some people may be porting of existing functionality to > the new framework; some people may be adding exciting new > functionality. All code will become part of the open source > IETF tools. > >Who: Hopefully you can help > >Chris Newman will be helping with advance planning. Henrik >Levkowetz will be coordinating the event in Stockholm. You >will hear more from them shortly. Many of the results of the >last code sprint are being used every day. > >Please support the tools development effort, > Russ > >_______________________________________________ >Ietf mailing list >Ietf@ietf.org >https://www.ietf.org/mailman/listinfo/ietf > From maxb@openet.com Wed May 20 06:40:38 2009 Return-Path: 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 685A43A6CB7 for ; Wed, 20 May 2009 06:40:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.79 X-Spam-Level: X-Spam-Status: No, score=-3.79 tagged_above=-999 required=5 tests=[AWL=2.809, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 gwvNIEjTJ54l for ; Wed, 20 May 2009 06:40:37 -0700 (PDT) Received: from mail169.messagelabs.com (mail169.messagelabs.com [85.158.138.179]) by core3.amsl.com (Postfix) with ESMTP id 3669728C22C for ; Wed, 20 May 2009 06:40:36 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: maxb@openet.com X-Msg-Ref: server-8.tower-169.messagelabs.com!1242826924!16548100!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [212.187.194.139] Received: (qmail 19716 invoked from network); 20 May 2009 13:42:06 -0000 Received: from unknown.level3.net (HELO dubhbca01.openet-dublin) (212.187.194.139) by server-8.tower-169.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2009 13:42:06 -0000 Received: from [10.0.2.161] (10.0.2.161) by dubhbca01.openet-dublin (10.0.3.82) with Microsoft SMTP Server id 8.1.340.0; Wed, 20 May 2009 14:42:04 +0100 Message-ID: <4A1408AB.2050301@openet.com> Date: Wed, 20 May 2009 14:42:03 +0100 From: Max Bacik User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 23 May 2009 10:34:41 -0700 Subject: [Dime] Multiple transport connections between peers X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2009 13:41:37 -0000 Hi All, =============================================================================== * RFC 3588, Section 2.1: * A given Diameter instance of the peer state machine MUST NOT use more than one transport connection to communicate with a given peer, unless multiple instances exist on the peer in which case a separate connection per process is allowed. =============================================================================== A previous conversation (http://www.ietf.org/mail-archive/web/dime/current/msg00803.html) seems to conclude that the above statement means that multiple Diameter nodes may reside on the same host, each using a different alias to that host as their Origin-Host and each using its own port (only one could use 3868). However, this seems to conflict with the RFC, firstly because the use of port 3868 is mandated, and secondly because of the wording of the statement. It says "a given Diameter instance of the peer state machine... ...unless multiple instances exist *on the peer*...". This seems to imply that it is multiple transport connections between two Diameter nodes - which seems to present quite a few problems for the peer state machine and for message routing. The above wording also still exists in the latest BIS draft (17) of the RFC. Can anyone shed some light on this topic? Thanks, Max From root@core3.amsl.com Sat May 23 14:00:02 2009 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 0915E3A6DA0; Sat, 23 May 2009 14:00:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090523210002.0915E3A6DA0@core3.amsl.com> Date: Sat, 23 May 2009 14:00:02 -0700 (PDT) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-diameter-cc-appl-mib-00.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2009 21:00:02 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter Credit Control Application MIB Author(s) : G. Zorn, S. Comerica Filename : draft-ietf-dime-diameter-cc-appl-mib-00.txt Pages : 20 Date : 2009-05-18 Along with providing support for certain basic authentication, authorization and accounting functions, the Diameter base protocol is intended to provide a framework for AAA applications. This document defines the Management Information Base (MIB) module which describes the minimum set of objects needed to manage an implementation of the Diameter Credit Control application. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-diameter-cc-appl-mib-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-diameter-cc-appl-mib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-05-23134631.I-D@ietf.org> --NextPart-- From root@core3.amsl.com Sat May 23 14:00:02 2009 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 10EAB3A6DF2; Sat, 23 May 2009 14:00:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090523210002.10EAB3A6DF2@core3.amsl.com> Date: Sat, 23 May 2009 14:00:02 -0700 (PDT) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-diameter-base-protocol-mib-00.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2009 21:00:02 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter Base Protocol MIB Author(s) : G. Zorn, S. Comerica Filename : draft-ietf-dime-diameter-base-protocol-mib-00.txt Pages : 52 Date : 2009-05-18 Along with providing support for certain basic authentication, authorization and accounting functions, the Diameter protocol is designed to provide a framework for AAA applications. This document defines the Management Information Base (MIB) module which describes the minimum set of objects needed to manage an implementation of the Diameter protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-diameter-base-protocol-mib-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-diameter-base-protocol-mib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-05-23134642.I-D@ietf.org> --NextPart-- From root@core3.amsl.com Mon May 25 03:00:01 2009 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 6B1E13A6E23; Mon, 25 May 2009 03:00:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090525100001.6B1E13A6E23@core3.amsl.com> Date: Mon, 25 May 2009 03:00:01 -0700 (PDT) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-qos-parameters-11.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 10:00:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Quality of Service Parameters for Usage with Diameter Author(s) : J. Korhonen, et al. Filename : draft-ietf-dime-qos-parameters-11.txt Pages : 11 Date : 2009-05-25 This document defines a number of Quality of Service (QoS) parameters that can be reused for conveying QoS information within Diameter. The defined QoS information includes data traffic parameters for describing a token bucket filter, a bandwidth parameter, and a per- hop behavior class object. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-qos-parameters-11.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-qos-parameters-11.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-05-25025535.I-D@ietf.org> --NextPart-- From dromasca@avaya.com Tue May 26 06:59:10 2009 Return-Path: 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 8D35F3A6B23 for ; Tue, 26 May 2009 06:59:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.349 X-Spam-Level: X-Spam-Status: No, score=-1.349 tagged_above=-999 required=5 tests=[AWL=-1.050, BAYES_00=-2.599, MANGLED_PENIS=2.3] 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 8d5Tk10vbgME for ; Tue, 26 May 2009 06:59:03 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 5C41528C213 for ; Tue, 26 May 2009 06:59:03 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,251,1241409600"; d="scan'208";a="146768722" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 26 May 2009 09:59:54 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 26 May 2009 09:59:53 -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: Tue, 26 May 2009 15:59:35 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AD review of draft-ietf-dime-qos-attributes-11.txt Thread-Index: AcneCjORJ9rC1V8fTg6MsLb7F0ex4w== From: "Romascanu, Dan (Dan)" To: Subject: [Dime] AD review of draft-ietf-dime-qos-attributes-11.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 13:59:10 -0000 Please find below my AD review of draft-ietf-dime-qos-attributes-11.txt T are Technical comments, E are editorial.=20 I believe that the document is in reasonable shape. Function of the responses to the review we may decide to do a revised ID or send it to IETF Last Call and consider the comments below as IETF LC comments.=20 Thanks and Regards, Dan T1. IP-Address in 4.15 and 4.16 should not include also a type AVP? (IPv4 and IPv6) As written the specification and examples seem to deal with IPv4 only. SO I miss something?=20 T2. Was this specification sent for review to IEEE 802.1? I believe that it should - maybe during the IETF Last Call, especially because of the VLAN and priority AVPs semantics. For example one of the questions to ask is about the usage of the values 0 and 4095 for VLAN-IDs. These usually have special semantics in IEEE 802.1 headers and I would suggest that we get expert assessment about their usage in filters.=20 T3. In Section 5.1=20 0: drop 1: shape 2: police 2: mark Should be 3: mark I guess T4. Why is not the list of actions in 5.7 (Excess-Traffic-Action) consistent with the list of actions in 5.1?=20 E1. In section 3.3 the last sentence in the paragraph ('The lower the numerical value of Rule-Precedence AVP, the higher the rule precedence.') should come second in the paragraph.=20 E2. Under fig.1 the text speaks about one Unmanaged Terminal, while the figure represents multiple Unmanaged Terminals.=20 E3. Section 4.1.4 s/both direction/both directions/ E4. The term ETH priority in 4.1.8.23, 4.1.8.24, and 4.1.8.25 is slightly mis-leading. There is no such thing as Ethernet Priority, on an Ethernet there is no priority, and tagged packets are prioritized in the routers or switches. I suggest to drop ETH from the names and to use either 8021 or nothing.=20 E5. in Section 5.3 - Private Enterprise Number (PEN) is a preferred term to SMI Network Management Private Enterprise Code E6. The registry policies in the IANA considerations section should be expressed in terms and with reference to RFC 5226.=20 From Marco.Liebsch@nw.neclab.eu Wed May 27 08:58:12 2009 Return-Path: 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 CAFF33A6BE9 for ; Wed, 27 May 2009 08:58:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.949 X-Spam-Level: X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650, 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 aATAK0YEHPPl for ; Wed, 27 May 2009 08:58:11 -0700 (PDT) Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id 8909E3A6F3B for ; Wed, 27 May 2009 08:58:11 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 9342D2C019196; Wed, 27 May 2009 17:59:02 +0200 (CEST) X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office) Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2arKzuGFV8XS; Wed, 27 May 2009 17:59:02 +0200 (CEST) Received: from VENUS.office (mx2.office [192.168.24.15]) by smtp0.neclab.eu (Postfix) with ESMTP id 5E19D2C01918D; Wed, 27 May 2009 17:58:52 +0200 (CEST) Received: from [10.1.2.175] ([10.1.2.175]) by VENUS.office with Microsoft SMTPSVC(6.0.3790.3959); Wed, 27 May 2009 17:58:53 +0200 Message-ID: <4A1D633B.5000006@nw.neclab.eu> Date: Wed, 27 May 2009 17:58:51 +0200 From: Marco Liebsch User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: dime@ietf.org, jouni korhonen Content-Type: multipart/mixed; boundary="------------040101090909080902020808" X-OriginalArrivalTime: 27 May 2009 15:58:53.0313 (UTC) FILETIME=[087D9F10:01C9DEE4] Subject: [Dime] Diameter PMIPv6 X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 15:58:12 -0000 This is a multi-part message in MIME format. --------------040101090909080902020808 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Jouni, all, please find a few thoughts about the current version of draft-ietf-dime-pmip6-02 attached. And sorry for the huge delay in providing comments. Hope the comments style is clear. Anyway, proposed changes are optional :-) Hope it helps. Best regards, marco --------------040101090909080902020808 Content-Type: text/plain; name="comments.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="comments.txt" Editorial for clarification: ============================ 1. Introduction "..Dynamic assignment and downloading of PMIPv6 policy profile information is a desirable feature to ease the deployment and network maintenance of larger PMIPv6 deployments. " > you probably mean "..maintenance of larger PMIPv6 domains." --- "..The Diameter server in the Mobility Service authorizer's (MSA) network may return these parameters to the Network Access Server (NAS). " > you may add ".. to the Network Access Server (NAS) during access authentication." -- "..Once the MN authenticates to the network the MAG sends.." > Isn't it vice versa that the network authenticates the MN? You may change to "..Once the network has authenticated the MN, the MAG sends.." or "..Once the MN has identified to the network and the network has authenticated the MN..." -- "..The NAS functionality of the MAG may be co-located or an integral part of the MAG.." > I'd consider the NAS and the MAG as functional entities, which may be colocated on an access router. So, the proposed alternative may be "..The NAS functionality may be colocated with the MAG function on the network's access router.." -- 3. Solution Overview "..This document defines Diameter based AAA interactions between the MAG and the HAAA, and between the LMA and the HAAA." > Hmm, since the extension is generic for any interface between a Diameter Client and Diameter Server, I'd consider such operation also useful with a AAA in the visited network. So, why limiting this to the HAAA? I'd suggest to write simply AAA. Loading profile info is anyway transparent, as the AAAvisited contacts the AAAhome. -- 4.2 PMIP6-IPv4-Home-Address AVP > Would it make sense to include a BNF of this AVP as well? Or provide a reference here to the document where the type Address is defined. -- Section 5.1 > Some text as you have it at the beginning of Section 5.1 I'd propose to have much earlier to understand what the document is about, which problem it addresses and which protocol extensions it proposes to solve the problem. General comments: ================ As the spec does not define a new application for PMIPv6 anymore, can the text or even the title reflect that it's in fact a Generic Extension to Diameter Applications for Proxy MIPv6? So far it says it's Diameter Support for Proxy Mobile IPv6. I'd be more precise and clear in 1. Introduction and the beginning of 3. Solution Overview about what the specification does. Well, the intro says what PMIPv6 demands and what NAS does. Then it says that the spec defines the Diameter support for PMIPv6 (to do what?) and that the NAS may be colocated with the MAG.. The Intro looks very unsystematic to me. All this is ok if you (as reader) know the details of why and how you're doing this. I'd recommend that in the Intro you're precise with describing the problem, the existing protocols you can re-use and extend and with what you specify in this document to solve the problem. Then it should be ok for most readers to understand the rest. One feature of the LMA-AAA interface should be HNP delegation, where the LMA can request an HNP for the MN from the AAA during mobility session authorization. As far as I remember, this was in some time ago (? maybe not..). Would be good to have this feature mentioned in the spec, e.g. Section 1 and Secion 5.2. --------------040101090909080902020808--