From dromasca@avaya.com Thu Dec 1 04:28:26 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B73D21F8BBB for ; Thu, 1 Dec 2011 04:28:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.285 X-Spam-Level: X-Spam-Status: No, score=-103.285 tagged_above=-999 required=5 tests=[AWL=0.314, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CBae-BU4Be5S for ; Thu, 1 Dec 2011 04:28:25 -0800 (PST) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 60DDD21F8BB8 for ; Thu, 1 Dec 2011 04:28:25 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArgAAPFx107GmAcF/2dsb2JhbAA6CppVkB2BBYFyAQEBAQMBAQEPHgoNJxcGAQgNBAQBAQsGCQIBCwEHJh8HAQEFBAEEEwgah22YE4QUjUuOEgSHbBgYgiFjBJo6jDA X-IronPort-AV: E=Sophos;i="4.71,277,1320642000"; d="scan'208";a="279962360" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 01 Dec 2011 07:28:23 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 Dec 2011 07:26:20 -0500 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: Thu, 1 Dec 2011 13:28:21 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Secdir review of draft-ietf-dime-priority-avps-05 Thread-Index: AcxHTu34hXvg7biARZewSRVBSgbUbxoYjJ/wABzk3SA= From: "Romascanu, Dan (Dan)" To: Subject: [Dime] FW: Secdir review of draft-ietf-dime-priority-avps-05 X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 01 Dec 2011 12:28:26 -0000 -----Original Message----- From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Stephen Hanna Sent: Thursday, December 01, 2011 1:14 AM To: ietf@ietf.org; secdir@ietf.org; draft-ietf-dime-priority-avps.all@tools.ietf.org Subject: Secdir review of draft-ietf-dime-priority-avps-05 I have reviewed this document as part of the security directorate's=20 ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the=20 security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. This standards track document defines Diameter AVPs that can be used to convey a variety of priority parameters. In July 2011, I conducted a secdir review of a previous revision of this document (-04) and found that the Security Considerations section was inadequate because it did not include any analysis of the specific security issues related to priority systems. I'm pleased to say that the authors have attempted to address this issue in their new draft. They added a reference to the Security Considerations section of RFC 5866, which is thorough and sound. In addition, they explicitly identify one threat: unauthorized changes to QoS parameters in transit. However, the countermeasure proposed is confusing. The document now says "integrity protected values SHOULD be ignored". I would expect the reverse. Values that are not integrity protected SHOULD be ignored. Am I wrong? I'm concerned that the other threats described in RFC 5866 are not addressed in this document. Lack of authentication and confidentiality protection for QoS parameters can have serious negative impacts, as described in RFC 5866. In the IETF spirit of "send text", I suggest the following paragraph be added to the Security Considerations section of this draft: As described in [RFC5866], failure to provide adequate authentication and confidentiality protection for QoS parameters may result in serious failures that undermine the very purpose of QoS. Countermeasures such as Diameter communication security should be employed as appropriate. I will supply a further optional suggestion to clarify the text recently added regarding integrity. I recommend that the first paragraph of the Security Considerations section be stripped to just its first sentence and that the following paragraph be used in place of the new text that was added at the end of that paragraph: The values in the AVPs defined in this draft are not supposed to be changed by any of the Diameter servers or any other intermediaries. In fact, changes to these AVPs in transit could result in serious problems such as inability to complete high-priority emergency phone calls. Therefore, source integrity protection SHOULD be employed for those AVPs (e.g., the use of S/MIME with the SIP RPH, or an INTEGRITY object within a POLICY_DATA object). The text that I wrote may well be incorrect or misguided. I'm just trying to provide helpful suggestions from a security perspective. If the authors would like to have a further chat about this topic, I'd be glad to do so. And if they want to keep the text that they added on integrity protection, that's OK. I just found it a bit lacking in describing the threat and its consequences and in providing an effective countermeasure. Thanks, Steve _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf From lionel.morand@orange.com Thu Dec 1 10:59:28 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 027F51F0C54 for ; Thu, 1 Dec 2011 10:59:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vKg0OXVVrVDe for ; Thu, 1 Dec 2011 10:59:27 -0800 (PST) Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by ietfa.amsl.com (Postfix) with ESMTP id 79DA21F0C4A for ; Thu, 1 Dec 2011 10:59:27 -0800 (PST) Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 4F233858003; Thu, 1 Dec 2011 20:10:01 +0100 (CET) Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id 465E8858001; Thu, 1 Dec 2011 20:10:01 +0100 (CET) Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Thu, 1 Dec 2011 19:59:26 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 1 Dec 2011 19:59:25 +0100 Message-ID: In-Reply-To: <6A3D0DF3-3D5F-4753-984F-52F88B689192@gmx.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: fate of draft-ietf-dime-app-design-guide Thread-Index: AcyoLqn8QkU4x4TcSr2zYOsM+P9CEgILDTmQ References: <1ECBE0F0-5658-4DAD-B7EC-B06DFAF02E9F@gmail.com> <6A3D0DF3-3D5F-4753-984F-52F88B689192@gmx.net> From: To: , X-OriginalArrivalTime: 01 Dec 2011 18:59:26.0552 (UTC) FILETIME=[58D13580:01CCB05B] Cc: dime@ietf.org Subject: Re: [Dime] fate of draft-ietf-dime-app-design-guide X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 01 Dec 2011 18:59:28 -0000 Give me a last chance! :) 8 months is not so long. And we were waiting anyway the publication of = the 3588 Bis-version. I will initiate a mail with at least the points that I would like to see = clarified with this document. And we can use it to set-up after that a = confcall. Is it OK? Lionel -----Message d'origine----- De=A0: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]=20 Envoy=E9=A0: lundi 21 novembre 2011 10:19 =C0=A0: jouni korhonen Cc=A0: Hannes Tschofenig; dime@ietf.org; MORAND Lionel RD-CORE-ISS; = Victor Fajardo Objet=A0: Re: fate of draft-ietf-dime-app-design-guide=20 Hi Jouni,=20 I believe the document is valuable but I suggest that the authors = schedule a conference call to make a proposal to the group on how to = finish it.=20 Ciao Hannes On Nov 21, 2011, at 10:43 AM, jouni korhonen wrote: > Folks, >=20 > Anyone has something against it if we withdrawn = draft-ietf-dime-app-design-guide ? The I-D expired 8 months ago and has = been in the WG since August 2007.=20 >=20 > Voice your opinion *against* the withdrawn by 2nd Dec. Silence will be = counted as 'yes' for withdrawn. >=20 > - Jouni From jouni.nospam@gmail.com Thu Dec 1 12:41:11 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB67621F9435 for ; Thu, 1 Dec 2011 12:41:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Xdu9vX616ar for ; Thu, 1 Dec 2011 12:41:10 -0800 (PST) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3818321F9427 for ; Thu, 1 Dec 2011 12:41:10 -0800 (PST) Received: by lahj13 with SMTP id j13so1086845lah.31 for ; Thu, 01 Dec 2011 12:41:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=3YKumc8ymnQWcDwjmWdJFv/nKMGZfy/0FGF4zO+qQcE=; b=PlmC2k7E/ggLBUV89FXPbzBHtB3IM0o8gcs7TVtd8Co3kvFNH+fUzX4bpfy9Hs3sPD tJ0TVVRhEbxq7qJmKKyHGfs/02zZuHCYSkguxqXEh8Xa7QBnHDfWxzUD0TUDC6VGLnir d2528HkSDkdGk0VIG3TMRUtiIa2v3zCCISEaw= Received: by 10.152.105.132 with SMTP id gm4mr5830610lab.39.1322772069119; Thu, 01 Dec 2011 12:41:09 -0800 (PST) Received: from a88-112-207-66.elisa-laajakaista.fi (a88-112-207-66.elisa-laajakaista.fi. [88.112.207.66]) by mx.google.com with ESMTPS id hh9sm6220725lab.1.2011.12.01.12.41.06 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Dec 2011 12:41:07 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: <0D212BD466921646B58854FB79092CEC072BE54B@XMB-AMS-106.cisco.com> Date: Thu, 1 Dec 2011 22:41:05 +0200 Content-Transfer-Encoding: 7bit Message-Id: <693ABBDE-B6D5-4178-BA58-86D134943CA2@gmail.com> References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> <0D212BD466921646B58854FB79092CEC072BE54B@XMB-AMS-106.cisco.com> To: Frank Brockners (fbrockne) X-Mailer: Apple Mail (2.1084) Cc: dime@ietf.org Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 01 Dec 2011 20:41:11 -0000 Frank, hanks for the comments. See some stuff inline. On Nov 30, 2011, at 12:39 PM, Frank Brockners (fbrockne) wrote: > Thanks for the updated version. Two minor comments: > > - typo: s/for a bulk/for bulk/ Ack. > > - On "and an appropriate use of the Diameter protocol". > Do we have a clear description of what "an appropriate > use of the Diameter protocol" is? Unless we have this, Appropriate being what fits under RFC3588(bis) umbrella. > wouldn't the "require verification that the proposed > extension is needed" provide the justification > and evaluation that the extension would make sense? > In which case wouldn't it make sense to drop > "and an appropriate use of the Diameter protocol"? > > Thoughts? Hmm.. good point. I don't myself have a firm opinion. - Jouni > > Thanks, Frank > > > >> -----Original Message----- >> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf > Of >> jouni korhonen >> Sent: Wednesday, November 30, 2011 10:40 AM >> To: dime@ietf.org >> Subject: Re: [Dime] re-chartering >> >> Folks, >> >> The next revision of the new charter proposal. I added Mark's & >> Lothar's comments. I recall someone had concerns on the intended >> "extension for a bulk and group signaling" solution space the current >> text directs to. If so, just propose changes to the text. >> >> - Jouni >> >> >> >> 2011-xx-yy charter >> Diameter Maintenance and Extensions (dime) >> ------------------------------------------ >> >> Charter >> >> Current Status: Active >> >> Chairs: >> Lionel Morand >> Jouni Korhonen >> >> Operations and Management Area Directors: >> Dan Romascanu >> Ronald Bonica >> >> Operations and Management Area Advisor: >> Dan Romascanu >> >> Mailing Lists: >> General Discussion: dime@ietf.org >> To Subscribe: https://www.ietf.org/mailman/listinfo/dime >> Archive: http://www.ietf.org/mail- >> archive/web/dime/current/maillist.html >> >> >> Description of Working Group: >> >> The Diameter Maintenance and Extensions WG will focus on maintenance >> and extensions to the Diameter protocol required to enable its use >> for >> authentication, authorization, accounting, charging in network >> access, >> provisioning configuration information within the network, and other >> signaling purposes. >> >> The DIME working group plans to address the following items: >> >> - Maintaining and/or progressing, along the standards track, the >> Diameter Base protocol and Diameter Applications. This includes >> extensions to Diameter Base protocol that can be considered as >> enhanced >> features or bug fixes. >> >> - Diameter application design guideline. This document will provide >> guidelines for design of Diameter extensions. It will detail when to >> consider reusing an existing application and when to develop a new >> application. >> >> - Protocol extensions for the management of Diameter entities. This >> work >> focuses on the standardization of Management Information Bases > (MIBs) >> to configure Diameter entities (such as the Diameter Base protocol > or >> Diameter Credit Control nodes). The usage of other management >> protocols >> for configuring Diameter entities may be future work within the >> group. >> >> - Protocol extension for a bulk and group signaling. The aim of this >> work is to study and standardize a solution for handling a group of >> sessions within the Diameter base protocol context. The solution >> would >> define how to identify and handle grouped sessions as a one combined >> entity for commands and operations. >> >> Additionally, Diameter-based systems require interoperability in >> order >> to work. The working group, along with the AD, will need to evaluate >> any potential extensions and require verification that the proposed >> extension is needed and an appropriate use of the Diameter protocol. >> Coordination with other IETF working groups and other SDOs will be >> used to ensure this. >> >> >> Goals and Milestones: >> Done - Submit the following two Diameter Mobility documents to >> the IESG for consideration as a Proposed Standards:* 'Diameter Mobile >> IPv6: Support for Home Agent to Diameter Server Interaction' * >> 'Diameter Mobile IPv6: Support for Network Access Server to Diameter >> Server Interaction' >> Done - Submit 'Diameter API' to the IESG for consideration as an >> Informational RFC >> Done - Submit 'Quality of Service Parameters for Usage with >> Diameter' to the IESG for consideration as a Proposed Standard. >> Done - Submit 'Diameter QoS Application' to the IESG for >> consideration as a Proposed Standard >> Done - Submit 'Diameter Support for EAP Re-authentication >> Protocol' as DIME working group item >> Done - Submit 'Diameter User-Name and Realm Based Request > Routing >> Clarifications' as DIME working group item >> Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group >> item >> Done - Submit 'Quality of Service Attributes for Diameter' to > the >> IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for >> consideration as a Proposed Standard >> Done - Submit 'Diameter User-Name and Realm Based Request > Routing >> Clarifications' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter NAT Control Application' as DIME working >> group item >> Done - Submit 'Diameter Capabilities Update' as DIME working >> group item >> Done - Submit ' Diameter Credit Control Application MIB' to the >> IESG for consideration as an Informational RFC >> Done - Submit 'Diameter Base Protocol MIB' to the IESG for >> consideration as an Informational RFC >> Done - Submit 'Diameter Capabilities Update' to the IESG for >> consideration as a Proposed Standard >> Done - Submit 'Diameter Extended NAPTR' as DIME working group >> item >> Done - Submit 'Realm-Based Redirection In Diameter' as DIME >> working group item >> Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized >> Routing' as DIME working group item >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic >> Key Transport' as DIME working group item >> Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME >> working group item >> Done - Submit 'Diameter IKEv2 PSK' as DIME working group item >> Done - Submit Revision of 'Diameter Base Protocol' to the IESG >> for consideration as a Proposed Standard >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic >> Key Transport' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Priority Attribute Value Pairs' to the >> IESG for consideration as a Proposed Standard >> Done - Submit Revision of 'Diameter Network Access Server >> Application - RFC 4005bis' as DIME working group item >> Sep 201x - Submit 'Diameter Application Design Guidelines' to the >> IESG for consideration as a BCP document >> Done - Submit 'Diameter NAT Control Application' to the IESG for >> consideration as a Proposed Standard >> Sep 201x - Submit 'Realm-Based Redirection In Diameter' to the IESG >> for consideration as a Proposed Standard >> Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration >> as a Proposed Standard >> Done - Submit 'Diameter Extended NAPTR' to the IESG for >> consideration as a Proposed Standard >> Nov 2011 - Submit 'Diameter Support for Proxy Mobile IPv6 Localized >> Routing' to the IESG for consideration as a Proposed Standard >> Jul 201x - Submit 'Diameter Support for EAP Re-authentication >> Protocol' to the IESG for consideration as a Proposed Standard >> Sep 201x - Submit Revision of 'Diameter Network Access Server >> Application - RFC 4005bis' to the IESG for consideration as a Proposed >> Standard >> >> >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Thu Dec 1 12:49:45 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47A2811E80D6 for ; Thu, 1 Dec 2011 12:49:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qpbze4rRYYVj for ; Thu, 1 Dec 2011 12:49:44 -0800 (PST) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id A1A3A11E80C8 for ; Thu, 1 Dec 2011 12:49:43 -0800 (PST) Received: by lahj13 with SMTP id j13so1090662lah.31 for ; Thu, 01 Dec 2011 12:49:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=qDSHO51hBpx6tYm76agnZ8fpNDIitAXSoB19bClBcvo=; b=uG0rUQ5ILzbh+1oq9GFIjjBNmeEuWRvlwyYG5Jl0xnwuEGSSjzJ4zY8E42x9a556dY C/5HLPEIjKr5/WYyC2WleX0hqX756f+uFHmiuJ+P8VAE1XAlb+N/2JzUAZ2MKQ4X8bpC godC6a5dPsXh+aJjc/9R0t67vWdpgsP6a84Uk= Received: by 10.152.104.6 with SMTP id ga6mr5882168lab.45.1322772582531; Thu, 01 Dec 2011 12:49:42 -0800 (PST) Received: from a88-112-207-66.elisa-laajakaista.fi (a88-112-207-66.elisa-laajakaista.fi. [88.112.207.66]) by mx.google.com with ESMTPS id ni5sm6235109lab.3.2011.12.01.12.49.39 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Dec 2011 12:49:40 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: <69756203DDDDE64E987BC4F70B71A26D24D156CD@Polydeuces.office.hd> Date: Thu, 1 Dec 2011 22:49:37 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <524F99B4-8224-47CF-93AD-F8FF52F106FE@gmail.com> References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> <69756203DDDDE64E987BC4F70B71A26D24D156CD@Polydeuces.office.hd> To: Marco Liebsch X-Mailer: Apple Mail (2.1084) Cc: "dime@ietf.org" Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 01 Dec 2011 20:49:45 -0000 Hi Marco, Thanks for the input. See inline. On Nov 30, 2011, at 1:33 PM, Marco Liebsch wrote: > Hi Jouni, > thanks for the updated charter proposal. Please find some minor = comments > and proposals inline. >=20 > The Diameter Maintenance and Extensions WG will focus on maintenance > and extensions to the Diameter protocol required to enable its use = for > authentication, authorization, accounting, charging in network = access, > provisioning /+ of +/ configuration information within the network, = and other > signaling purposes. Ack. >=20 > .. >=20 > Original text about the bulk operations work item:=20 > - Protocol extension for a bulk and group signaling. The aim of this > work is to study and standardize a solution for handling a group of > sessions within the Diameter base protocol context. The solution = would > define how to identify and handle grouped sessions as a one combined > entity for commands and operations. >=20 > If we plan to look at bulk operation use cases also for NASREQ and = Credit Control applications, > we may not refer to '..Diameter base protocol context', which I = understand as RFC3588. >=20 > Also, the last sentence about '..as a one combined entity' is not so = clear to me. Right. Bad wording. What I meant by "handle grouped sessions as a one = combined entity" is merely like being able to name a group of session = with a single name/identity and use that in signaling. In that sense one = message would be targeted to one combine set (=3Dentity) of session. >=20 > What about the following: >=20 > - Protocol extension for /- a -/ bulk and group signaling. The aim of = this > work is to study and standardize a solution for handling /-a-/ = group/+s+/ of So multiple groups..? > sessions within /-the Diameter base protocol -/ /+ Diameter = applications' +/ context. So you would not extend the base protocol, rather each application = separately using some well-defined rule? Would this them imply that a = new application need explicitly stated & described support for = bulk/group signaling? > The solution would define how to identify and handle grouped sessions=20= > /-as a one combined entity for commands and operations-/ > /+and how to signal and perform Diameter operations on these = groups+/.=20 - Jouni >=20 > Thanks, > marco >=20 >=20 >=20 >=20 >=20 >> -----Original Message----- >> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf = Of >> jouni korhonen >> Sent: Mittwoch, 30. November 2011 10:40 >> To: dime@ietf.org >> Subject: Re: [Dime] re-chartering >>=20 >> Folks, >>=20 >> The next revision of the new charter proposal. I added Mark's & = Lothar's >> comments. I recall someone had concerns on the intended "extension = for a >> bulk and group signaling" solution space the current text directs to. = If so, just >> propose changes to the text. >>=20 >> - Jouni >>=20 >>=20 >>=20 >> 2011-xx-yy charter >> Diameter Maintenance and Extensions (dime) >> ------------------------------------------ >>=20 >> Charter >>=20 >> Current Status: Active >>=20 >> Chairs: >> Lionel Morand >> Jouni Korhonen >>=20 >> Operations and Management Area Directors: >> Dan Romascanu >> Ronald Bonica >>=20 >> Operations and Management Area Advisor: >> Dan Romascanu >>=20 >> Mailing Lists: >> General Discussion: dime@ietf.org >> To Subscribe: https://www.ietf.org/mailman/listinfo/dime >> Archive: http://www.ietf.org/mail- >> archive/web/dime/current/maillist.html >>=20 >>=20 >> Description of Working Group: >>=20 >> The Diameter Maintenance and Extensions WG will focus on maintenance >> and extensions to the Diameter protocol required to enable its use = for >> authentication, authorization, accounting, charging in network = access, >> provisioning configuration information within the network, and other >> signaling purposes. >>=20 >> The DIME working group plans to address the following items: >>=20 >> - Maintaining and/or progressing, along the standards track, the >> Diameter Base protocol and Diameter Applications. This includes >> extensions to Diameter Base protocol that can be considered as = enhanced >> features or bug fixes. >>=20 >> - Diameter application design guideline. This document will provide >> guidelines for design of Diameter extensions. It will detail when to >> consider reusing an existing application and when to develop a new >> application. >>=20 >> - Protocol extensions for the management of Diameter entities. This = work >> focuses on the standardization of Management Information Bases = (MIBs) >> to configure Diameter entities (such as the Diameter Base protocol = or >> Diameter Credit Control nodes). The usage of other management = protocols >> for configuring Diameter entities may be future work within the = group. >>=20 >> - Protocol extension for a bulk and group signaling. The aim of this >> work is to study and standardize a solution for handling a group of >> sessions within the Diameter base protocol context. The solution = would >> define how to identify and handle grouped sessions as a one combined >> entity for commands and operations. >>=20 >> Additionally, Diameter-based systems require interoperability in = order >> to work. The working group, along with the AD, will need to evaluate >> any potential extensions and require verification that the proposed >> extension is needed and an appropriate use of the Diameter protocol. >> Coordination with other IETF working groups and other SDOs will be >> used to ensure this. >>=20 >>=20 >> Goals and Milestones: >> Done - Submit the following two Diameter Mobility documents to = the >> IESG for consideration as a Proposed Standards:* 'Diameter Mobile = IPv6: >> Support for Home Agent to Diameter Server Interaction' * 'Diameter = Mobile >> IPv6: Support for Network Access Server to Diameter Server = Interaction' >> Done - Submit 'Diameter API' to the IESG for consideration as an >> Informational RFC >> Done - Submit 'Quality of Service Parameters for Usage with = Diameter' to >> the IESG for consideration as a Proposed Standard. >> Done - Submit 'Diameter QoS Application' to the IESG for = consideration as >> a Proposed Standard >> Done - Submit 'Diameter Support for EAP Re-authentication = Protocol' as >> DIME working group item >> Done - Submit 'Diameter User-Name and Realm Based Request = Routing >> Clarifications' as DIME working group item >> Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group = item >> Done - Submit 'Quality of Service Attributes for Diameter' to = the IESG for >> consideration as a Proposed Standard >> Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for = consideration >> as a Proposed Standard >> Done - Submit 'Diameter User-Name and Realm Based Request = Routing >> Clarifications' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter NAT Control Application' as DIME working = group >> item >> Done - Submit 'Diameter Capabilities Update' as DIME working = group item >> Done - Submit ' Diameter Credit Control Application MIB' to the = IESG for >> consideration as an Informational RFC >> Done - Submit 'Diameter Base Protocol MIB' to the IESG for = consideration >> as an Informational RFC >> Done - Submit 'Diameter Capabilities Update' to the IESG for = consideration >> as a Proposed Standard >> Done - Submit 'Diameter Extended NAPTR' as DIME working group = item >> Done - Submit 'Realm-Based Redirection In Diameter' as DIME = working >> group item >> Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized = Routing' >> as DIME working group item >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key >> Transport' as DIME working group item >> Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME = working >> group item >> Done - Submit 'Diameter IKEv2 PSK' as DIME working group item >> Done - Submit Revision of 'Diameter Base Protocol' to the IESG = for >> consideration as a Proposed Standard >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key >> Transport' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Priority Attribute Value Pairs' to the = IESG for >> consideration as a Proposed Standard >> Done - Submit Revision of 'Diameter Network Access Server = Application - >> RFC 4005bis' as DIME working group item >> Sep 201x - Submit 'Diameter Application Design Guidelines' to the = IESG for >> consideration as a BCP document >> Done - Submit 'Diameter NAT Control Application' to the IESG for >> consideration as a Proposed Standard >> Sep 201x - Submit 'Realm-Based Redirection In Diameter' to the IESG = for >> consideration as a Proposed Standard >> Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration = as a >> Proposed Standard >> Done - Submit 'Diameter Extended NAPTR' to the IESG for = consideration >> as a Proposed Standard >> Nov 2011 - Submit 'Diameter Support for Proxy Mobile IPv6 Localized >> Routing' to the IESG for consideration as a Proposed Standard >> Jul 201x - Submit 'Diameter Support for EAP Re-authentication = Protocol' to >> the IESG for consideration as a Proposed Standard >> Sep 201x - Submit Revision of 'Diameter Network Access Server = Application - >> RFC 4005bis' to the IESG for consideration as a Proposed Standard >>=20 >>=20 >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Thu Dec 1 12:51:59 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF82111E80D6 for ; Thu, 1 Dec 2011 12:51:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kty5aJhanmLg for ; Thu, 1 Dec 2011 12:51:59 -0800 (PST) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 821EE11E80C8 for ; Thu, 1 Dec 2011 12:51:58 -0800 (PST) Received: by lahj13 with SMTP id j13so1091612lah.31 for ; Thu, 01 Dec 2011 12:51:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:x-priority:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=1UImkG1TrSk17pTVJbsw7ENNlfibZzJfUTAewiPr9YU=; b=TLbmzJynDYMAPw4Z4XvXnyjL/vrxEz6InB5lF7OILKEKoWHPBmfCmFZmEmGk+2WdIG bkBEYJ3ys7OgmzG/yt+0X7M31BFZQ6v5gynmf/+8HOXleE+YfJGmJ5EVYKCXASKOr9br 5MV9WAkMRzNDST8CUf3UWwyM9KSbiagjDW0XY= Received: by 10.152.102.173 with SMTP id fp13mr6000491lab.24.1322772717501; Thu, 01 Dec 2011 12:51:57 -0800 (PST) Received: from a88-112-207-66.elisa-laajakaista.fi (a88-112-207-66.elisa-laajakaista.fi. [88.112.207.66]) by mx.google.com with ESMTPS id hm12sm6226317lab.9.2011.12.01.12.51.54 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Dec 2011 12:51:55 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen X-Priority: 3 In-Reply-To: Date: Thu, 1 Dec 2011 22:51:52 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> To: Qin Wu X-Mailer: Apple Mail (2.1084) Cc: dime@ietf.org Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 01 Dec 2011 20:51:59 -0000 Hi Qin, Regarding your question, see my latest reply to Marco. The "combined = entity" being a signle name/identification for a group of sessions. I = admit the wording is not the best one ;) - Jouni On Dec 1, 2011, at 4:28 AM, Qin Wu wrote: > This version looks good to me. One minor comment: > It is not clear to what "one combined entity" is in the bulk and group = sigaling item? functinality entity or physical entity? > How about change it into "one single association"? >=20 > Regards! > -Qin > ----- Original Message -----=20 > From: "jouni korhonen" > To: > Sent: Wednesday, November 30, 2011 5:39 PM > Subject: Re: [Dime] re-chartering >=20 >=20 >> Folks, >>=20 >> The next revision of the new charter proposal. I added Mark's & = Lothar's comments. I recall someone had concerns on the intended = "extension for a bulk and group signaling" solution space the current = text directs to. If so, just propose changes to the text. >>=20 >> - Jouni >>=20 >>=20 >>=20 >> 2011-xx-yy charter >> Diameter Maintenance and Extensions (dime) >> ------------------------------------------ >>=20 >> Charter >>=20 >> Current Status: Active >>=20 >> Chairs: >> Lionel Morand >> Jouni Korhonen >>=20 >> Operations and Management Area Directors: >> Dan Romascanu >> Ronald Bonica >>=20 >> Operations and Management Area Advisor: >> Dan Romascanu >>=20 >> Mailing Lists: >> General Discussion: dime@ietf.org >> To Subscribe: https://www.ietf.org/mailman/listinfo/dime >> Archive: = http://www.ietf.org/mail-archive/web/dime/current/maillist.html >>=20 >>=20 >> Description of Working Group: >>=20 >> The Diameter Maintenance and Extensions WG will focus on maintenance >> and extensions to the Diameter protocol required to enable its use = for >> authentication, authorization, accounting, charging in network = access, >> provisioning configuration information within the network, and other >> signaling purposes. >>=20 >> The DIME working group plans to address the following items: >>=20 >> - Maintaining and/or progressing, along the standards track, the >> Diameter Base protocol and Diameter Applications. This includes >> extensions to Diameter Base protocol that can be considered as = enhanced >> features or bug fixes. >>=20 >> - Diameter application design guideline. This document will provide >> guidelines for design of Diameter extensions. It will detail when to >> consider reusing an existing application and when to develop a new >> application. >>=20 >> - Protocol extensions for the management of Diameter entities. This = work >> focuses on the standardization of Management Information Bases (MIBs) >> to configure Diameter entities (such as the Diameter Base protocol or >> Diameter Credit Control nodes). The usage of other management = protocols >> for configuring Diameter entities may be future work within the = group. >>=20 >> - Protocol extension for a bulk and group signaling. The aim of this >> work is to study and standardize a solution for handling a group of >> sessions within the Diameter base protocol context. The solution = would >> define how to identify and handle grouped sessions as a one combined >> entity for commands and operations. >>=20 >> Additionally, Diameter-based systems require interoperability in = order >> to work. The working group, along with the AD, will need to evaluate >> any potential extensions and require verification that the proposed >> extension is needed and an appropriate use of the Diameter protocol. >> Coordination with other IETF working groups and other SDOs will be >> used to ensure this. >>=20 >>=20 >> Goals and Milestones: >> Done - Submit the following two Diameter Mobility documents to = the IESG for consideration as a Proposed Standards:* 'Diameter Mobile = IPv6: Support for Home Agent to Diameter Server Interaction' * 'Diameter = Mobile IPv6: Support for Network Access Server to Diameter Server = Interaction' >> Done - Submit 'Diameter API' to the IESG for consideration as an = Informational RFC >> Done - Submit 'Quality of Service Parameters for Usage with = Diameter' to the IESG for consideration as a Proposed Standard. >> Done - Submit 'Diameter QoS Application' to the IESG for = consideration as a Proposed Standard >> Done - Submit 'Diameter Support for EAP Re-authentication = Protocol' as DIME working group item >> Done - Submit 'Diameter User-Name and Realm Based Request Routing = Clarifications' as DIME working group item >> Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group = item >> Done - Submit 'Quality of Service Attributes for Diameter' to the = IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for = consideration as a Proposed Standard >> Done - Submit 'Diameter User-Name and Realm Based Request Routing = Clarifications' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter NAT Control Application' as DIME working = group item >> Done - Submit 'Diameter Capabilities Update' as DIME working = group item >> Done - Submit ' Diameter Credit Control Application MIB' to the = IESG for consideration as an Informational RFC >> Done - Submit 'Diameter Base Protocol MIB' to the IESG for = consideration as an Informational RFC >> Done - Submit 'Diameter Capabilities Update' to the IESG for = consideration as a Proposed Standard >> Done - Submit 'Diameter Extended NAPTR' as DIME working group = item >> Done - Submit 'Realm-Based Redirection In Diameter' as DIME = working group item >> Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized = Routing' as DIME working group item >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key Transport' as DIME working group item >> Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME = working group item >> Done - Submit 'Diameter IKEv2 PSK' as DIME working group item >> Done - Submit Revision of 'Diameter Base Protocol' to the IESG = for consideration as a Proposed Standard >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key Transport' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Priority Attribute Value Pairs' to the = IESG for consideration as a Proposed Standard >> Done - Submit Revision of 'Diameter Network Access Server = Application - RFC 4005bis' as DIME working group item >> Sep 201x - Submit 'Diameter Application Design Guidelines' to the = IESG for consideration as a BCP document >> Done - Submit 'Diameter NAT Control Application' to the IESG for = consideration as a Proposed Standard >> Sep 201x - Submit 'Realm-Based Redirection In Diameter' to the IESG = for consideration as a Proposed Standard >> Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration = as a Proposed Standard >> Done - Submit 'Diameter Extended NAPTR' to the IESG for = consideration as a Proposed Standard >> Nov 2011 - Submit 'Diameter Support for Proxy Mobile IPv6 Localized = Routing' to the IESG for consideration as a Proposed Standard >> Jul 201x - Submit 'Diameter Support for EAP Re-authentication = Protocol' to the IESG for consideration as a Proposed Standard >> Sep 201x - Submit Revision of 'Diameter Network Access Server = Application - RFC 4005bis' to the IESG for consideration as a Proposed = Standard >>=20 >>=20 >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime >>=20 From bill.wu@huawei.com Thu Dec 1 17:08:10 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 794C621F9894 for ; Thu, 1 Dec 2011 17:08:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.41 X-Spam-Level: X-Spam-Status: No, score=-6.41 tagged_above=-999 required=5 tests=[AWL=0.189, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DcK1UzSnfbRU for ; Thu, 1 Dec 2011 17:08:09 -0800 (PST) Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 41D3421F9893 for ; Thu, 1 Dec 2011 17:08:09 -0800 (PST) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVJ003T7XTETX@szxga04-in.huawei.com> for dime@ietf.org; Fri, 02 Dec 2011 09:08:03 +0800 (CST) Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVJ0067IXTEAU@szxga04-in.huawei.com> for dime@ietf.org; Fri, 02 Dec 2011 09:08:02 +0800 (CST) Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AFJ54204; Fri, 02 Dec 2011 09:07:08 +0800 Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 02 Dec 2011 09:06:41 +0800 Received: from w53375q (10.138.41.130) by szxeml410-hub.china.huawei.com (10.82.67.137) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 02 Dec 2011 09:06:37 +0800 Date: Fri, 02 Dec 2011 09:06:34 +0800 From: Qin Wu X-Originating-IP: [10.138.41.130] To: jouni korhonen Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 X-Mailer: Microsoft Outlook Express 6.00.2900.5931 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal X-CFilter-Loop: Reflected References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> Cc: dime@ietf.org Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 02 Dec 2011 01:08:10 -0000 That address my concern. Thanks. -Qin ----- Original Message ----- From: "jouni korhonen" To: "Qin Wu" Cc: Sent: Friday, December 02, 2011 4:51 AM Subject: Re: [Dime] re-chartering Hi Qin, Regarding your question, see my latest reply to Marco. The "combined entity" being a signle name/identification for a group of sessions. I admit the wording is not the best one ;) - Jouni On Dec 1, 2011, at 4:28 AM, Qin Wu wrote: > This version looks good to me. One minor comment: > It is not clear to what "one combined entity" is in the bulk and group sigaling item? functinality entity or physical entity? > How about change it into "one single association"? > > Regards! > -Qin > ----- Original Message ----- > From: "jouni korhonen" > To: > Sent: Wednesday, November 30, 2011 5:39 PM > Subject: Re: [Dime] re-chartering > > >> Folks, >> >> The next revision of the new charter proposal. I added Mark's & Lothar's comments. I recall someone had concerns on the intended "extension for a bulk and group signaling" solution space the current text directs to. If so, just propose changes to the text. >> >> - Jouni >> >> >> >> 2011-xx-yy charter >> Diameter Maintenance and Extensions (dime) >> ------------------------------------------ >> >> Charter >> >> Current Status: Active >> >> Chairs: >> Lionel Morand >> Jouni Korhonen >> >> Operations and Management Area Directors: >> Dan Romascanu >> Ronald Bonica >> >> Operations and Management Area Advisor: >> Dan Romascanu >> >> Mailing Lists: >> General Discussion: dime@ietf.org >> To Subscribe: https://www.ietf.org/mailman/listinfo/dime >> Archive: http://www.ietf.org/mail-archive/web/dime/current/maillist.html >> >> >> Description of Working Group: >> >> The Diameter Maintenance and Extensions WG will focus on maintenance >> and extensions to the Diameter protocol required to enable its use for >> authentication, authorization, accounting, charging in network access, >> provisioning configuration information within the network, and other >> signaling purposes. >> >> The DIME working group plans to address the following items: >> >> - Maintaining and/or progressing, along the standards track, the >> Diameter Base protocol and Diameter Applications. This includes >> extensions to Diameter Base protocol that can be considered as enhanced >> features or bug fixes. >> >> - Diameter application design guideline. This document will provide >> guidelines for design of Diameter extensions. It will detail when to >> consider reusing an existing application and when to develop a new >> application. >> >> - Protocol extensions for the management of Diameter entities. This work >> focuses on the standardization of Management Information Bases (MIBs) >> to configure Diameter entities (such as the Diameter Base protocol or >> Diameter Credit Control nodes). The usage of other management protocols >> for configuring Diameter entities may be future work within the group. >> >> - Protocol extension for a bulk and group signaling. The aim of this >> work is to study and standardize a solution for handling a group of >> sessions within the Diameter base protocol context. The solution would >> define how to identify and handle grouped sessions as a one combined >> entity for commands and operations. >> >> Additionally, Diameter-based systems require interoperability in order >> to work. The working group, along with the AD, will need to evaluate >> any potential extensions and require verification that the proposed >> extension is needed and an appropriate use of the Diameter protocol. >> Coordination with other IETF working groups and other SDOs will be >> used to ensure this. >> >> >> Goals and Milestones: >> Done - Submit the following two Diameter Mobility documents to the IESG for consideration as a Proposed Standards:* 'Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction' * 'Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction' >> Done - Submit 'Diameter API' to the IESG for consideration as an Informational RFC >> Done - Submit 'Quality of Service Parameters for Usage with Diameter' to the IESG for consideration as a Proposed Standard. >> Done - Submit 'Diameter QoS Application' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Support for EAP Re-authentication Protocol' as DIME working group item >> Done - Submit 'Diameter User-Name and Realm Based Request Routing Clarifications' as DIME working group item >> Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group item >> Done - Submit 'Quality of Service Attributes for Diameter' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter User-Name and Realm Based Request Routing Clarifications' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter NAT Control Application' as DIME working group item >> Done - Submit 'Diameter Capabilities Update' as DIME working group item >> Done - Submit ' Diameter Credit Control Application MIB' to the IESG for consideration as an Informational RFC >> Done - Submit 'Diameter Base Protocol MIB' to the IESG for consideration as an Informational RFC >> Done - Submit 'Diameter Capabilities Update' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Extended NAPTR' as DIME working group item >> Done - Submit 'Realm-Based Redirection In Diameter' as DIME working group item >> Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized Routing' as DIME working group item >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic Key Transport' as DIME working group item >> Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME working group item >> Done - Submit 'Diameter IKEv2 PSK' as DIME working group item >> Done - Submit Revision of 'Diameter Base Protocol' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic Key Transport' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Priority Attribute Value Pairs' to the IESG for consideration as a Proposed Standard >> Done - Submit Revision of 'Diameter Network Access Server Application - RFC 4005bis' as DIME working group item >> Sep 201x - Submit 'Diameter Application Design Guidelines' to the IESG for consideration as a BCP document >> Done - Submit 'Diameter NAT Control Application' to the IESG for consideration as a Proposed Standard >> Sep 201x - Submit 'Realm-Based Redirection In Diameter' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Extended NAPTR' to the IESG for consideration as a Proposed Standard >> Nov 2011 - Submit 'Diameter Support for Proxy Mobile IPv6 Localized Routing' to the IESG for consideration as a Proposed Standard >> Jul 201x - Submit 'Diameter Support for EAP Re-authentication Protocol' to the IESG for consideration as a Proposed Standard >> Sep 201x - Submit Revision of 'Diameter Network Access Server Application - RFC 4005bis' to the IESG for consideration as a Proposed Standard >> >> >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime >> From jouni.nospam@gmail.com Thu Dec 1 23:18:09 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEE7A21F98B7 for ; Thu, 1 Dec 2011 23:18:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nDHFlPjkALyO for ; Thu, 1 Dec 2011 23:18:09 -0800 (PST) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 00A6421F98AE for ; Thu, 1 Dec 2011 23:18:08 -0800 (PST) Received: by lahj13 with SMTP id j13so1252916lah.31 for ; Thu, 01 Dec 2011 23:18:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=WQcsPRnFt6kkOOhYUCf/hDc6h3EOBkg6nS3H5VeWVyc=; b=IzbkyXm+GldaSbQJ8AlD6loKjdNmebeO9e+zHDM36Go3COJsUsk4IAGMU4JJGoujCS rafLcPGA2+W4D7uNhFmQ4l3izWwJdNvwh4cVIargyrfj9UooNjpy6MMU6FqX4lRAMAX3 lhlS+P6En7iD3KAkHGAzyMZTvD7wgvhceTZLc= Received: by 10.152.109.199 with SMTP id hu7mr6962108lab.16.1322810287775; Thu, 01 Dec 2011 23:18:07 -0800 (PST) Received: from a88-112-207-66.elisa-laajakaista.fi (a88-112-207-66.elisa-laajakaista.fi. [88.112.207.66]) by mx.google.com with ESMTPS id hm12sm7470112lab.9.2011.12.01.23.18.05 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Dec 2011 23:18:06 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=iso-8859-1 From: jouni korhonen In-Reply-To: Date: Fri, 2 Dec 2011 09:18:04 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1ECBE0F0-5658-4DAD-B7EC-B06DFAF02E9F@gmail.com> <6A3D0DF3-3D5F-4753-984F-52F88B689192@gmx.net> To: dime@ietf.org X-Mailer: Apple Mail (2.1084) Subject: Re: [Dime] fate of draft-ietf-dime-app-design-guide X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 02 Dec 2011 07:18:09 -0000 Folks, We got two voices for preserving the design guidelines and apart from = the discussion during the Taipei meeting none against. We'll keep the = I-D still for a while in charter. - Jouni On Dec 1, 2011, at 8:59 PM, = wrote: > Give me a last chance! :) > 8 months is not so long. And we were waiting anyway the publication of = the 3588 Bis-version. > I will initiate a mail with at least the points that I would like to = see clarified with this document. And we can use it to set-up after that = a confcall. Is it OK? >=20 > Lionel >=20 > -----Message d'origine----- > De : Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]=20 > Envoy=E9 : lundi 21 novembre 2011 10:19 > =C0 : jouni korhonen > Cc : Hannes Tschofenig; dime@ietf.org; MORAND Lionel RD-CORE-ISS; = Victor Fajardo > Objet : Re: fate of draft-ietf-dime-app-design-guide=20 >=20 > Hi Jouni,=20 >=20 > I believe the document is valuable but I suggest that the authors = schedule a conference call to make a proposal to the group on how to = finish it.=20 >=20 > Ciao > Hannes >=20 > On Nov 21, 2011, at 10:43 AM, jouni korhonen wrote: >=20 >> Folks, >>=20 >> Anyone has something against it if we withdrawn = draft-ietf-dime-app-design-guide ? The I-D expired 8 months ago and has = been in the WG since August 2007.=20 >>=20 >> Voice your opinion *against* the withdrawn by 2nd Dec. Silence will = be counted as 'yes' for withdrawn. >>=20 >> - Jouni >=20 From Marco.Liebsch@neclab.eu Fri Dec 2 00:41:00 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94CA421F939B for ; Fri, 2 Dec 2011 00:41:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id diV591GMURjM for ; Fri, 2 Dec 2011 00:40:59 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 20E8121F9398 for ; Fri, 2 Dec 2011 00:40:59 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 1CB6A28000080; Fri, 2 Dec 2011 09:40:58 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas1.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0AyK+-HpmhzH; Fri, 2 Dec 2011 09:40:58 +0100 (CET) Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id F12B42800017C; Fri, 2 Dec 2011 09:40:47 +0100 (CET) Received: from Polydeuces.office.hd ([169.254.3.40]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Fri, 2 Dec 2011 09:40:47 +0100 From: Marco Liebsch To: jouni korhonen Thread-Topic: [Dime] re-chartering Thread-Index: AQHMqbWhX5qzDvK+tUWyVr3a+tBLeZXCdymAgAKsrQCAACdn4IACJg6AgADUxgA= Date: Fri, 2 Dec 2011 08:40:47 +0000 Message-ID: <69756203DDDDE64E987BC4F70B71A26D24D15F22@Polydeuces.office.hd> References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> <69756203DDDDE64E987BC4F70B71A26D24D156CD@Polydeuces.office.hd> <524F99B4-8224-47CF-93AD-F8FF52F106FE@gmail.com> In-Reply-To: <524F99B4-8224-47CF-93AD-F8FF52F106FE@gmail.com> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.6.212] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dime@ietf.org" Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 02 Dec 2011 08:41:00 -0000 Hi Jouni, please see my feedback inline. > -----Original Message----- > From: jouni korhonen [mailto:jouni.nospam@gmail.com] > Sent: Donnerstag, 1. Dezember 2011 21:50 > To: Marco Liebsch > Cc: dime@ietf.org > Subject: Re: [Dime] re-chartering >=20 > Hi Marco, >=20 > Thanks for the input. See inline. >=20 > On Nov 30, 2011, at 1:33 PM, Marco Liebsch wrote: >=20 > > Hi Jouni, > > thanks for the updated charter proposal. Please find some minor > > comments and proposals inline. > > > > The Diameter Maintenance and Extensions WG will focus on maintenance > > and extensions to the Diameter protocol required to enable its use for > > authentication, authorization, accounting, charging in network access, > > provisioning /+ of +/ configuration information within the network, > > and other signaling purposes. >=20 > Ack. >=20 > > > > .. > > > > Original text about the bulk operations work item: > > - Protocol extension for a bulk and group signaling. The aim of this > > work is to study and standardize a solution for handling a group of > > sessions within the Diameter base protocol context. The solution would > > define how to identify and handle grouped sessions as a one combined > > entity for commands and operations. > > > > If we plan to look at bulk operation use cases also for NASREQ and > > Credit Control applications, we may not refer to '..Diameter base proto= col > context', which I understand as RFC3588. > > > > Also, the last sentence about '..as a one combined entity' is not so cl= ear to > me. >=20 > Right. Bad wording. What I meant by "handle grouped sessions as a one > combined entity" is merely like being able to name a group of session wit= h a > single name/identity and use that in signaling. In that sense one message > would be targeted to one combine set (=3Dentity) of session. Sure, that's the optimal case. But does the charter text need to comprise t= his as requirement? Why not opt for group operation by identifying the group of users with a list of Session-IDs? No strong opinion here, so if you thin= k the text is clear, fine. >=20 > > > > What about the following: > > > > - Protocol extension for /- a -/ bulk and group signaling. The aim of > > this work is to study and standardize a solution for handling /-a-/ > > group/+s+/ of >=20 > So multiple groups..? Not within the same operation. But separate bulk operations could be done in the context of different groups. So, multiple groups. If the text points= to a single bulk operation, then it's one group. >=20 > > sessions within /-the Diameter base protocol -/ /+ Diameter applicati= ons' > +/ context. >=20 > So you would not extend the base protocol, rather each application > separately using some well-defined rule? Would this them imply that a new > application need explicitly stated & described support for bulk/group > signaling? If we can extend the base with a mechanism for bulk operation that can be applied by individual applications, that would be a good choice. My only concerns with the written text was to limit bulk operation to messages of the base protocol (3588) and to exclude other applications' messages fro= m being bulk-operation enabled. marco >=20 >=20 > > The solution would define how to identify and handle grouped sessions > > /-as a one combined entity for commands and operations-/ /+and how to > > signal and perform Diameter operations on these groups+/. >=20 >=20 > - Jouni >=20 > > > > Thanks, > > marco > > > > > > > > > > > >> -----Original Message----- > >> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf > >> Of jouni korhonen > >> Sent: Mittwoch, 30. November 2011 10:40 > >> To: dime@ietf.org > >> Subject: Re: [Dime] re-chartering > >> > >> Folks, > >> > >> The next revision of the new charter proposal. I added Mark's & > >> Lothar's comments. I recall someone had concerns on the intended > >> "extension for a bulk and group signaling" solution space the current > >> text directs to. If so, just propose changes to the text. > >> > >> - Jouni > >> > >> > >> > >> 2011-xx-yy charter > >> Diameter Maintenance and Extensions (dime) > >> ------------------------------------------ > >> > >> Charter > >> > >> Current Status: Active > >> > >> Chairs: > >> Lionel Morand > >> Jouni Korhonen > >> > >> Operations and Management Area Directors: > >> Dan Romascanu > >> Ronald Bonica > >> > >> Operations and Management Area Advisor: > >> Dan Romascanu > >> > >> Mailing Lists: > >> General Discussion: dime@ietf.org > >> To Subscribe: https://www.ietf.org/mailman/listinfo/dime > >> Archive: http://www.ietf.org/mail- > >> archive/web/dime/current/maillist.html > >> > >> > >> Description of Working Group: > >> > >> The Diameter Maintenance and Extensions WG will focus on > maintenance > >> and extensions to the Diameter protocol required to enable its use > >> for authentication, authorization, accounting, charging in network > >> access, provisioning configuration information within the network, > >> and other signaling purposes. > >> > >> The DIME working group plans to address the following items: > >> > >> - Maintaining and/or progressing, along the standards track, the > >> Diameter Base protocol and Diameter Applications. This includes > >> extensions to Diameter Base protocol that can be considered as > >> enhanced features or bug fixes. > >> > >> - Diameter application design guideline. This document will provide > >> guidelines for design of Diameter extensions. It will detail when to > >> consider reusing an existing application and when to develop a new > >> application. > >> > >> - Protocol extensions for the management of Diameter entities. This > >> work focuses on the standardization of Management Information Bases > >> (MIBs) to configure Diameter entities (such as the Diameter Base > >> protocol or Diameter Credit Control nodes). The usage of other > >> management protocols for configuring Diameter entities may be future > work within the group. > >> > >> - Protocol extension for a bulk and group signaling. The aim of this > >> work is to study and standardize a solution for handling a group of > >> sessions within the Diameter base protocol context. The solution > >> would define how to identify and handle grouped sessions as a one > >> combined entity for commands and operations. > >> > >> Additionally, Diameter-based systems require interoperability in > >> order to work. The working group, along with the AD, will need to > >> evaluate any potential extensions and require verification that the > >> proposed extension is needed and an appropriate use of the Diameter > protocol. > >> Coordination with other IETF working groups and other SDOs will be > >> used to ensure this. > >> > >> > >> Goals and Milestones: > >> Done - Submit the following two Diameter Mobility documents to th= e > >> IESG for consideration as a Proposed Standards:* 'Diameter Mobile IPv6= : > >> Support for Home Agent to Diameter Server Interaction' * 'Diameter > >> Mobile > >> IPv6: Support for Network Access Server to Diameter Server Interaction= ' > >> Done - Submit 'Diameter API' to the IESG for consideration as an > >> Informational RFC > >> Done - Submit 'Quality of Service Parameters for Usage with Diame= ter' > to > >> the IESG for consideration as a Proposed Standard. > >> Done - Submit 'Diameter QoS Application' to the IESG for consider= ation > as > >> a Proposed Standard > >> Done - Submit 'Diameter Support for EAP Re-authentication Protoco= l' as > >> DIME working group item > >> Done - Submit 'Diameter User-Name and Realm Based Request Routing > >> Clarifications' as DIME working group item > >> Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group > item > >> Done - Submit 'Quality of Service Attributes for Diameter' to the= IESG > for > >> consideration as a Proposed Standard > >> Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for > consideration > >> as a Proposed Standard > >> Done - Submit 'Diameter User-Name and Realm Based Request Routing > >> Clarifications' to the IESG for consideration as a Proposed Standard > >> Done - Submit 'Diameter NAT Control Application' as DIME working > group > >> item > >> Done - Submit 'Diameter Capabilities Update' as DIME working grou= p > item > >> Done - Submit ' Diameter Credit Control Application MIB' to the I= ESG for > >> consideration as an Informational RFC > >> Done - Submit 'Diameter Base Protocol MIB' to the IESG for > consideration > >> as an Informational RFC > >> Done - Submit 'Diameter Capabilities Update' to the IESG for > consideration > >> as a Proposed Standard > >> Done - Submit 'Diameter Extended NAPTR' as DIME working group ite= m > >> Done - Submit 'Realm-Based Redirection In Diameter' as DIME worki= ng > >> group item > >> Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized > Routing' > >> as DIME working group item > >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic K= ey > >> Transport' as DIME working group item > >> Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME w= orking > >> group item > >> Done - Submit 'Diameter IKEv2 PSK' as DIME working group item > >> Done - Submit Revision of 'Diameter Base Protocol' to the IESG fo= r > >> consideration as a Proposed Standard > >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic K= ey > >> Transport' to the IESG for consideration as a Proposed Standard > >> Done - Submit 'Diameter Priority Attribute Value Pairs' to the IE= SG for > >> consideration as a Proposed Standard > >> Done - Submit Revision of 'Diameter Network Access Server Applica= tion > - > >> RFC 4005bis' as DIME working group item Sep 201x - Submit 'Diameter > >> Application Design Guidelines' to the IESG for consideration as a BCP > >> document > >> Done - Submit 'Diameter NAT Control Application' to the IESG for > >> consideration as a Proposed Standard > >> Sep 201x - Submit 'Realm-Based Redirection In Diameter' to the IESG > >> for consideration as a Proposed Standard > >> Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration = as a > >> Proposed Standard > >> Done - Submit 'Diameter Extended NAPTR' to the IESG for > consideration > >> as a Proposed Standard > >> Nov 2011 - Submit 'Diameter Support for Proxy Mobile IPv6 Localized > >> Routing' to the IESG for consideration as a Proposed Standard Jul > >> 201x - Submit 'Diameter Support for EAP Re-authentication Protocol' > >> to the IESG for consideration as a Proposed Standard Sep 201x - > >> Submit Revision of 'Diameter Network Access Server Application - RFC > >> 4005bis' to the IESG for consideration as a Proposed Standard > >> > >> > >> _______________________________________________ > >> DiME mailing list > >> DiME@ietf.org > >> https://www.ietf.org/mailman/listinfo/dime From dromasca@avaya.com Mon Dec 5 02:59:47 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 610D421F8B1D for ; Mon, 5 Dec 2011 02:59:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.374 X-Spam-Level: X-Spam-Status: No, score=-103.374 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jbyKI-cCnuYQ for ; Mon, 5 Dec 2011 02:59:46 -0800 (PST) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 73F8921F8B1F for ; Mon, 5 Dec 2011 02:59:46 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AoQAACyj3E6HCzI1/2dsb2JhbABEmhKQKYEFgXIBAQEBAwEBAQ8eOAYXBAIBCA0EBAEBAQoGDAsBBgEmHwkIAQEEARIIEQmHbZoxmyAEij5jBId5kkqMMg X-IronPort-AV: E=Sophos;i="4.71,298,1320642000"; d="scan'208";a="280436902" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 05 Dec 2011 05:59:44 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 05 Dec 2011 05:47:48 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 5 Dec 2011 11:59:41 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dime] fate of draft-ietf-dime-app-design-guide Thread-Index: Acywwo5KXIbuV2WeSc2s85oia/JkSwCeTl/w References: <1ECBE0F0-5658-4DAD-B7EC-B06DFAF02E9F@gmail.com><6A3D0DF3-3D5F-4753-984F-52F88B689192@gmx.net> From: "Romascanu, Dan (Dan)" To: "jouni korhonen" , Subject: Re: [Dime] fate of draft-ietf-dime-app-design-guide X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 05 Dec 2011 10:59:47 -0000 Hi, After the list has spoken I will add my opinion as AD and contributor - = I believe that this work is important, as other SDOs and vendors are = doing work that extends Diameter by modifying and/or deriving from = existing applications or creating new applications, and they providing = them with the guidance that this document contains is important.=20 I suggest that Lionel starts in parallel with the mail with the points = for clarification by also bringing back to life this document (even = without significant content changes) so that everybody has in front of = us the point that we reached.=20 Thanks and Regards, Dan > -----Original Message----- > From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf = Of > jouni korhonen > Sent: Friday, December 02, 2011 9:18 AM > To: dime@ietf.org > Subject: Re: [Dime] fate of draft-ietf-dime-app-design-guide >=20 > Folks, >=20 > We got two voices for preserving the design guidelines and apart from > the discussion during the Taipei meeting none against. We'll keep the > I-D still for a while in charter. >=20 > - Jouni >=20 >=20 >=20 > On Dec 1, 2011, at 8:59 PM, > wrote: >=20 > > Give me a last chance! :) > > 8 months is not so long. And we were waiting anyway the publication > of the 3588 Bis-version. > > I will initiate a mail with at least the points that I would like to > see clarified with this document. And we can use it to set-up after > that a confcall. Is it OK? > > > > Lionel > > > > -----Message d'origine----- > > De : Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net] > > Envoy=E9 : lundi 21 novembre 2011 10:19 > > =C0 : jouni korhonen > > Cc : Hannes Tschofenig; dime@ietf.org; MORAND Lionel RD-CORE-ISS; > Victor Fajardo > > Objet : Re: fate of draft-ietf-dime-app-design-guide > > > > Hi Jouni, > > > > I believe the document is valuable but I suggest that the authors > schedule a conference call to make a proposal to the group on how to > finish it. > > > > Ciao > > Hannes > > > > On Nov 21, 2011, at 10:43 AM, jouni korhonen wrote: > > > >> Folks, > >> > >> Anyone has something against it if we withdrawn = draft-ietf-dime-app- > design-guide ? The I-D expired 8 months ago and has been in the WG > since August 2007. > >> > >> Voice your opinion *against* the withdrawn by 2nd Dec. Silence will > be counted as 'yes' for withdrawn. > >> > >> - Jouni > > >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From glenzorn@gmail.com Tue Dec 6 01:27:35 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA39821F8A7E for ; Tue, 6 Dec 2011 01:27:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DEKXU+4spaQa for ; Tue, 6 Dec 2011 01:27:35 -0800 (PST) Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id F022021F8B50 for ; Tue, 6 Dec 2011 01:27:34 -0800 (PST) Received: by qcsf15 with SMTP id f15so2371856qcs.31 for ; Tue, 06 Dec 2011 01:27:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=UiEvekpd26DiqfLLrW6/RjriCUv+b+6iPCoc2toI1TA=; b=BgQVcneQT1tns6PH35IftbDm4VR3Mr0scblFSpSXBIR4DH4/XycTW/kCWHhUuxB6tT Ho86E454jb1pTOEsD9ehbgjV0haGpvuaaBVR2QiUxApq58b2FlDbkbSvImvlbUj3+njN acIqFAvA0YFap0SI7iO5XhlVSByK445AhrdJw= Received: by 10.50.194.229 with SMTP id hz5mr14254613igc.36.1323163654253; Tue, 06 Dec 2011 01:27:34 -0800 (PST) Received: from [192.168.1.98] (ppp-124-122-181-87.revip2.asianet.co.th. [124.122.181.87]) by mx.google.com with ESMTPS id dd36sm87431797ibb.7.2011.12.06.01.27.28 (version=SSLv3 cipher=OTHER); Tue, 06 Dec 2011 01:27:32 -0800 (PST) Message-ID: <4EDDDFFD.7060005@gmail.com> Date: Tue, 06 Dec 2011 16:27:25 +0700 From: Glen Zorn User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: jouni korhonen References: <1ECBE0F0-5658-4DAD-B7EC-B06DFAF02E9F@gmail.com> <6A3D0DF3-3D5F-4753-984F-52F88B689192@gmx.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: dime@ietf.org Subject: Re: [Dime] fate of draft-ietf-dime-app-design-guide X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 06 Dec 2011 09:27:36 -0000 On 12/2/2011 2:18 PM, jouni korhonen wrote: > Folks, > > We got two voices for preserving the design guidelines and apart from the discussion during the Taipei meeting none against. We'll keep the I-D still for a while in charter. > Interesting way to measure WG "consensus". How many people are on the dime mailing list? According to your conditions, all but 2 of those people are considered to be "voting" no, but apparently those 2 override the rest... > - Jouni > > > > On Dec 1, 2011, at 8:59 PM, wrote: > >> Give me a last chance! :) >> 8 months is not so long. The draft _expired_ 8 months ago; this means that nobody has bothered to update even the version # & date in more than a year. OTOH, if "8 months is not so long", that may explain why it is considered acceptable for 4 months (instead of 4 minutes) to elapse between the end of WGLC and the creation of a 1 page proto write-up... > And we were waiting anyway the publication of the 3588 Bis-version. I did you expect that 3588bis was going to change so drastically as to invalidate your work? >> I will initiate a mail with at least the points that I would like to see clarified with this document. And we can use it to set-up after that a confcall. Is it OK? >> >> Lionel >> >> -----Message d'origine----- >> De : Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net] >> Envoyé : lundi 21 novembre 2011 10:19 >> À : jouni korhonen >> Cc : Hannes Tschofenig; dime@ietf.org; MORAND Lionel RD-CORE-ISS; Victor Fajardo >> Objet : Re: fate of draft-ietf-dime-app-design-guide >> >> Hi Jouni, >> >> I believe the document is valuable but I suggest that the authors schedule a conference call to make a proposal to the group on how to finish it. >> >> Ciao >> Hannes >> >> On Nov 21, 2011, at 10:43 AM, jouni korhonen wrote: >> >>> Folks, >>> >>> Anyone has something against it if we withdrawn draft-ietf-dime-app-design-guide ? The I-D expired 8 months ago and has been in the WG since August 2007. >>> >>> Voice your opinion *against* the withdrawn by 2nd Dec. Silence will be counted as 'yes' for withdrawn. >>> >>> - Jouni >> > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Tue Dec 6 01:36:08 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 398A321F8B3B for ; Tue, 6 Dec 2011 01:36:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.524 X-Spam-Level: X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8YJsmcsHEqyp for ; Tue, 6 Dec 2011 01:36:07 -0800 (PST) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 460C221F8B36 for ; Tue, 6 Dec 2011 01:36:07 -0800 (PST) Received: by laap9 with SMTP id p9so139402laa.31 for ; Tue, 06 Dec 2011 01:36:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=snR14n421Vp5VcTMKcwk/srqTCjFaPENqt7p4o2C+N8=; b=doOE53OnTfuuPsG8SXg9f/I6ClsAlc68u43xWCZRySy2pkjM3mv7FZNCkUHLTAqVsb iQRVGJXoM6mA6JwZKiXAKsrgvz+WrH1o4fCyfkWl1uG0bRssg+DavvPuJCZTxEySmHVS Uqs44e4m+Y5qHLFujwnpIUlcbNDzu4Xp3nk4g= Received: by 10.152.134.179 with SMTP id pl19mr8518657lab.13.1323164166060; Tue, 06 Dec 2011 01:36:06 -0800 (PST) Received: from [188.117.15.109] ([188.117.15.109]) by mx.google.com with ESMTPS id nj4sm20352952lab.12.2011.12.06.01.36.04 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 06 Dec 2011 01:36:04 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: Jouni In-Reply-To: <4EDDDFFD.7060005@gmail.com> Date: Tue, 6 Dec 2011 11:36:03 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <0DC0C827-7510-4163-B89A-5921E0299793@gmail.com> References: <1ECBE0F0-5658-4DAD-B7EC-B06DFAF02E9F@gmail.com> <6A3D0DF3-3D5F-4753-984F-52F88B689192@gmx.net> <4EDDDFFD.7060005@gmail.com> To: Glen Zorn X-Mailer: Apple Mail (2.1251.1) Cc: dime@ietf.org Subject: Re: [Dime] fate of draft-ietf-dime-app-design-guide X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 06 Dec 2011 09:36:08 -0000 Glen, The "voices" we got for preserving the I-D for yet another round came = from the authors. If the authors still want to give it another try, let = them have it. - Jouni On Dec 6, 2011, at 11:27 AM, Glen Zorn wrote: > On 12/2/2011 2:18 PM, jouni korhonen wrote: >> Folks, >>=20 >> We got two voices for preserving the design guidelines and apart from = the discussion during the Taipei meeting none against. We'll keep the = I-D still for a while in charter. >>=20 >=20 > Interesting way to measure WG "consensus". How many people are on the > dime mailing list? According to your conditions, all but 2 of those > people are considered to be "voting" no, but apparently those 2 = override > the rest... >=20 >> - Jouni >>=20 >>=20 >>=20 >> On Dec 1, 2011, at 8:59 PM, = wrote: >>=20 >>> Give me a last chance! :) >>> 8 months is not so long.=20 >=20 > The draft _expired_ 8 months ago; this means that nobody has bothered = to > update even the version # & date in more than a year. OTOH, if "8 > months is not so long", that may explain why it is considered = acceptable > for 4 months (instead of 4 minutes) to elapse between the end of WGLC > and the creation of a 1 page proto write-up... >=20 >> And we were waiting anyway the publication of the 3588 Bis-version. >=20 > I did you expect that 3588bis was going to change so drastically as to > invalidate your work? >=20 >>> I will initiate a mail with at least the points that I would like to = see clarified with this document. And we can use it to set-up after that = a confcall. Is it OK? >>>=20 >>> Lionel >>>=20 >>> -----Message d'origine----- >>> De : Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]=20 >>> Envoy=E9 : lundi 21 novembre 2011 10:19 >>> =C0 : jouni korhonen >>> Cc : Hannes Tschofenig; dime@ietf.org; MORAND Lionel RD-CORE-ISS; = Victor Fajardo >>> Objet : Re: fate of draft-ietf-dime-app-design-guide=20 >>>=20 >>> Hi Jouni,=20 >>>=20 >>> I believe the document is valuable but I suggest that the authors = schedule a conference call to make a proposal to the group on how to = finish it.=20 >>>=20 >>> Ciao >>> Hannes >>>=20 >>> On Nov 21, 2011, at 10:43 AM, jouni korhonen wrote: >>>=20 >>>> Folks, >>>>=20 >>>> Anyone has something against it if we withdrawn = draft-ietf-dime-app-design-guide ? The I-D expired 8 months ago and has = been in the WG since August 2007.=20 >>>>=20 >>>> Voice your opinion *against* the withdrawn by 2nd Dec. Silence will = be counted as 'yes' for withdrawn. >>>>=20 >>>> - Jouni >>>=20 >>=20 >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime >=20 From hannes.tschofenig@nsn.com Tue Dec 6 01:41:15 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA18121F86B3 for ; Tue, 6 Dec 2011 01:41:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.449 X-Spam-Level: X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id baxft2d4CK9V for ; Tue, 6 Dec 2011 01:41:15 -0800 (PST) Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id F0E5121F86A4 for ; Tue, 6 Dec 2011 01:41:14 -0800 (PST) Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id pB69fCXB009061 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Dec 2011 10:41:12 +0100 Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id pB69f6gc015683; Tue, 6 Dec 2011 10:41:11 +0100 Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 6 Dec 2011 10:40:56 +0100 Received: from 10.144.255.28 ([10.144.255.28]) by FIESEXC035.nsn-intra.net ([10.159.0.182]) via Exchange Front-End Server webmail.nsn-intra.net ([10.150.128.36]) with Microsoft Exchange Server HTTP-DAV ; Tue, 6 Dec 2011 09:40:56 +0000 User-Agent: Microsoft-Entourage/12.31.0.110725 Date: Tue, 06 Dec 2011 11:40:48 +0200 From: Hannes Tschofenig To: ext Glen Zorn , jouni korhonen Message-ID: Thread-Topic: [Dime] fate of draft-ietf-dime-app-design-guide Thread-Index: Acyz+yJEFeiKgaT3Z023G1ZBuJhsog== In-Reply-To: <4EDDDFFD.7060005@gmail.com> Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable X-OriginalArrivalTime: 06 Dec 2011 09:40:56.0936 (UTC) FILETIME=[27985680:01CCB3FB] Cc: dime@ietf.org Subject: Re: [Dime] fate of draft-ietf-dime-app-design-guide X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 06 Dec 2011 09:41:15 -0000 Hi Glen,=20 Do you have some suggestions on what we should put into the document to provide more value to the readers (for protocol designers within the IETF and outside)? Ciao Hannes On 12/6/11 11:27 AM, "ext Glen Zorn" wrote: > On 12/2/2011 2:18 PM, jouni korhonen wrote: >> Folks, >>=20 >> We got two voices for preserving the design guidelines and apart from th= e >> discussion during the Taipei meeting none against. We'll keep the I-D st= ill >> for a while in charter. >>=20 >=20 > Interesting way to measure WG "consensus". How many people are on the > dime mailing list? According to your conditions, all but 2 of those > people are considered to be "voting" no, but apparently those 2 override > the rest... >=20 >> - Jouni >>=20 >>=20 >>=20 >> On Dec 1, 2011, at 8:59 PM, >> wrote: >>=20 >>> Give me a last chance! :) >>> 8 months is not so long. >=20 > The draft _expired_ 8 months ago; this means that nobody has bothered to > update even the version # & date in more than a year. OTOH, if "8 > months is not so long", that may explain why it is considered acceptable > for 4 months (instead of 4 minutes) to elapse between the end of WGLC > and the creation of a 1 page proto write-up... >=20 >> And we were waiting anyway the publication of the 3588 Bis-version. >=20 > I did you expect that 3588bis was going to change so drastically as to > invalidate your work? >=20 >>> I will initiate a mail with at least the points that I would like to se= e >>> clarified with this document. And we can use it to set-up after that a >>> confcall. Is it OK? >>>=20 >>> Lionel >>>=20 >>> -----Message d'origine----- >>> De : Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net] >>> Envoy=E9 : lundi 21 novembre 2011 10:19 >>> =C0 : jouni korhonen >>> Cc : Hannes Tschofenig; dime@ietf.org; MORAND Lionel RD-CORE-ISS; Victo= r >>> Fajardo >>> Objet : Re: fate of draft-ietf-dime-app-design-guide >>>=20 >>> Hi Jouni,=20 >>>=20 >>> I believe the document is valuable but I suggest that the authors sched= ule a >>> conference call to make a proposal to the group on how to finish it. >>>=20 >>> Ciao >>> Hannes >>>=20 >>> On Nov 21, 2011, at 10:43 AM, jouni korhonen wrote: >>>=20 >>>> Folks, >>>>=20 >>>> Anyone has something against it if we withdrawn >>>> draft-ietf-dime-app-design-guide ? The I-D expired 8 months ago and ha= s >>>> been in the WG since August 2007. >>>>=20 >>>> Voice your opinion *against* the withdrawn by 2nd Dec. Silence will be >>>> counted as 'yes' for withdrawn. >>>>=20 >>>> - Jouni >>>=20 >>=20 >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Wed Dec 7 03:17:21 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77AF121F8B38 for ; Wed, 7 Dec 2011 03:17:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Ha+9DFFAoyN for ; Wed, 7 Dec 2011 03:17:20 -0800 (PST) Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3B71421F8AD8 for ; Wed, 7 Dec 2011 03:17:20 -0800 (PST) Received: by qadb15 with SMTP id b15so3579465qad.10 for ; Wed, 07 Dec 2011 03:17:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=uLWI/JolRhObpXCLH5TR3Apt+kolP2z7SJCMQVsoSy8=; b=HIVFzZLYz6ev4vMpkeJSwZH93Lb/2umar1KZyoBz9NzFYuTXiR6qwIeCuydHMFWzH2 UODw1g6QXO2XhYr9NeDmSHKxD1TtzL3bHsBiYrgzuN37frAdgI2uCPIX5qfE2JMPSS+q D2bZfAcL9HYUOvSEzWZrCt55mkTEv4JZRNcec= Received: by 10.224.1.69 with SMTP id 5mr16219201qae.29.1323256639661; Wed, 07 Dec 2011 03:17:19 -0800 (PST) Received: from a88-112-207-66.elisa-laajakaista.fi (a88-112-207-66.elisa-laajakaista.fi. [88.112.207.66]) by mx.google.com with ESMTPS id eb5sm2397889qab.10.2011.12.07.03.17.16 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 07 Dec 2011 03:17:17 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: <69756203DDDDE64E987BC4F70B71A26D24D15F22@Polydeuces.office.hd> Date: Wed, 7 Dec 2011 13:15:59 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> <69756203DDDDE64E987BC4F70B71A26D24D156CD@Polydeuces.office.hd> <524F99B4-8224-47CF-93AD-F8FF52F106FE@gmail.com> <69756203DDDDE64E987BC4F70B71A26D24D15F22@Polydeuces.office.hd> To: Marco Liebsch X-Mailer: Apple Mail (2.1084) Cc: "dime@ietf.org" Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 07 Dec 2011 11:17:21 -0000 Marco, On Dec 2, 2011, at 10:40 AM, Marco Liebsch wrote: > Hi Jouni, >=20 > please see my feedback inline. >=20 >> -----Original Message----- >> From: jouni korhonen [mailto:jouni.nospam@gmail.com] >> Sent: Donnerstag, 1. Dezember 2011 21:50 >> To: Marco Liebsch >> Cc: dime@ietf.org >> Subject: Re: [Dime] re-chartering >>=20 >> Hi Marco, >>=20 >> Thanks for the input. See inline. >>=20 >> On Nov 30, 2011, at 1:33 PM, Marco Liebsch wrote: >>=20 >>> Hi Jouni, >>> thanks for the updated charter proposal. Please find some minor >>> comments and proposals inline. >>>=20 >>> The Diameter Maintenance and Extensions WG will focus on maintenance >>> and extensions to the Diameter protocol required to enable its use = for >>> authentication, authorization, accounting, charging in network = access, >>> provisioning /+ of +/ configuration information within the network, >>> and other signaling purposes. >>=20 >> Ack. >>=20 >>>=20 >>> .. >>>=20 >>> Original text about the bulk operations work item: >>> - Protocol extension for a bulk and group signaling. The aim of this >>> work is to study and standardize a solution for handling a group of >>> sessions within the Diameter base protocol context. The solution = would >>> define how to identify and handle grouped sessions as a one combined >>> entity for commands and operations. >>>=20 >>> If we plan to look at bulk operation use cases also for NASREQ and >>> Credit Control applications, we may not refer to '..Diameter base = protocol >> context', which I understand as RFC3588. >>>=20 >>> Also, the last sentence about '..as a one combined entity' is not so = clear to >> me. >>=20 >> Right. Bad wording. What I meant by "handle grouped sessions as a one >> combined entity" is merely like being able to name a group of session = with a >> single name/identity and use that in signaling. In that sense one = message >> would be targeted to one combine set (=3Dentity) of session. >=20 > Sure, that's the optimal case. But does the charter text need to = comprise this > as requirement? Why not opt for group operation by identifying the = group > of users with a list of Session-IDs? No strong opinion here, so if you = think the > text is clear, fine. How about "The solution would define how to identify and handle grouped sessions in commands and operations." >>> What about the following: >>>=20 >>> - Protocol extension for /- a -/ bulk and group signaling. The aim = of >>> this work is to study and standardize a solution for handling /-a-/ >>> group/+s+/ of >>=20 >> So multiple groups..? >=20 > Not within the same operation. But separate bulk operations could be = done > in the context of different groups. So, multiple groups. If the text = points to a single > bulk operation, then it's one group. >=20 >>=20 >>> sessions within /-the Diameter base protocol -/ /+ Diameter = applications' >> +/ context. >>=20 >> So you would not extend the base protocol, rather each application >> separately using some well-defined rule? Would this them imply that a = new >> application need explicitly stated & described support for bulk/group >> signaling? >=20 > If we can extend the base with a mechanism for bulk operation that can > be applied by individual applications, that would be a good choice. My = only > concerns with the written text was to limit bulk operation to messages > of the base protocol (3588) and to exclude other applications' = messages from > being bulk-operation enabled. If the base protocol has support, then each new application can make use = of it. I think we have not decided yet whether bulk signaling support = means new base protocol messages or something else. At the moment I = would like to keep it in this way. - Jouni >=20 > marco >=20 >>=20 >>=20 >>> The solution would define how to identify and handle grouped = sessions >>> /-as a one combined entity for commands and operations-/ /+and how = to >>> signal and perform Diameter operations on these groups+/. >>=20 >>=20 >> - Jouni >>=20 >>>=20 >>> Thanks, >>> marco >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>> -----Original Message----- >>>> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On = Behalf >>>> Of jouni korhonen >>>> Sent: Mittwoch, 30. November 2011 10:40 >>>> To: dime@ietf.org >>>> Subject: Re: [Dime] re-chartering >>>>=20 >>>> Folks, >>>>=20 >>>> The next revision of the new charter proposal. I added Mark's & >>>> Lothar's comments. I recall someone had concerns on the intended >>>> "extension for a bulk and group signaling" solution space the = current >>>> text directs to. If so, just propose changes to the text. >>>>=20 >>>> - Jouni >>>>=20 >>>>=20 >>>>=20 >>>> 2011-xx-yy charter >>>> Diameter Maintenance and Extensions (dime) >>>> ------------------------------------------ >>>>=20 >>>> Charter >>>>=20 >>>> Current Status: Active >>>>=20 >>>> Chairs: >>>> Lionel Morand >>>> Jouni Korhonen >>>>=20 >>>> Operations and Management Area Directors: >>>> Dan Romascanu >>>> Ronald Bonica >>>>=20 >>>> Operations and Management Area Advisor: >>>> Dan Romascanu >>>>=20 >>>> Mailing Lists: >>>> General Discussion: dime@ietf.org >>>> To Subscribe: https://www.ietf.org/mailman/listinfo/dime >>>> Archive: http://www.ietf.org/mail- >>>> archive/web/dime/current/maillist.html >>>>=20 >>>>=20 >>>> Description of Working Group: >>>>=20 >>>> The Diameter Maintenance and Extensions WG will focus on >> maintenance >>>> and extensions to the Diameter protocol required to enable its use >>>> for authentication, authorization, accounting, charging in network >>>> access, provisioning configuration information within the network, >>>> and other signaling purposes. >>>>=20 >>>> The DIME working group plans to address the following items: >>>>=20 >>>> - Maintaining and/or progressing, along the standards track, the >>>> Diameter Base protocol and Diameter Applications. This includes >>>> extensions to Diameter Base protocol that can be considered as >>>> enhanced features or bug fixes. >>>>=20 >>>> - Diameter application design guideline. This document will provide >>>> guidelines for design of Diameter extensions. It will detail when = to >>>> consider reusing an existing application and when to develop a new >>>> application. >>>>=20 >>>> - Protocol extensions for the management of Diameter entities. This >>>> work focuses on the standardization of Management Information = Bases >>>> (MIBs) to configure Diameter entities (such as the Diameter Base >>>> protocol or Diameter Credit Control nodes). The usage of other >>>> management protocols for configuring Diameter entities may be = future >> work within the group. >>>>=20 >>>> - Protocol extension for a bulk and group signaling. The aim of = this >>>> work is to study and standardize a solution for handling a group of >>>> sessions within the Diameter base protocol context. The solution >>>> would define how to identify and handle grouped sessions as a one >>>> combined entity for commands and operations. >>>>=20 >>>> Additionally, Diameter-based systems require interoperability in >>>> order to work. The working group, along with the AD, will need to >>>> evaluate any potential extensions and require verification that = the >>>> proposed extension is needed and an appropriate use of the = Diameter >> protocol. >>>> Coordination with other IETF working groups and other SDOs will be >>>> used to ensure this. >>>>=20 >>>>=20 >>>> Goals and Milestones: >>>> Done - Submit the following two Diameter Mobility documents to = the >>>> IESG for consideration as a Proposed Standards:* 'Diameter Mobile = IPv6: >>>> Support for Home Agent to Diameter Server Interaction' * 'Diameter >>>> Mobile >>>> IPv6: Support for Network Access Server to Diameter Server = Interaction' >>>> Done - Submit 'Diameter API' to the IESG for consideration as = an >>>> Informational RFC >>>> Done - Submit 'Quality of Service Parameters for Usage with = Diameter' >> to >>>> the IESG for consideration as a Proposed Standard. >>>> Done - Submit 'Diameter QoS Application' to the IESG for = consideration >> as >>>> a Proposed Standard >>>> Done - Submit 'Diameter Support for EAP Re-authentication = Protocol' as >>>> DIME working group item >>>> Done - Submit 'Diameter User-Name and Realm Based Request = Routing >>>> Clarifications' as DIME working group item >>>> Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working = group >> item >>>> Done - Submit 'Quality of Service Attributes for Diameter' to = the IESG >> for >>>> consideration as a Proposed Standard >>>> Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for >> consideration >>>> as a Proposed Standard >>>> Done - Submit 'Diameter User-Name and Realm Based Request = Routing >>>> Clarifications' to the IESG for consideration as a Proposed = Standard >>>> Done - Submit 'Diameter NAT Control Application' as DIME = working >> group >>>> item >>>> Done - Submit 'Diameter Capabilities Update' as DIME working = group >> item >>>> Done - Submit ' Diameter Credit Control Application MIB' to the = IESG for >>>> consideration as an Informational RFC >>>> Done - Submit 'Diameter Base Protocol MIB' to the IESG for >> consideration >>>> as an Informational RFC >>>> Done - Submit 'Diameter Capabilities Update' to the IESG for >> consideration >>>> as a Proposed Standard >>>> Done - Submit 'Diameter Extended NAPTR' as DIME working group = item >>>> Done - Submit 'Realm-Based Redirection In Diameter' as DIME = working >>>> group item >>>> Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized >> Routing' >>>> as DIME working group item >>>> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key >>>> Transport' as DIME working group item >>>> Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME = working >>>> group item >>>> Done - Submit 'Diameter IKEv2 PSK' as DIME working group item >>>> Done - Submit Revision of 'Diameter Base Protocol' to the IESG = for >>>> consideration as a Proposed Standard >>>> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key >>>> Transport' to the IESG for consideration as a Proposed Standard >>>> Done - Submit 'Diameter Priority Attribute Value Pairs' to the = IESG for >>>> consideration as a Proposed Standard >>>> Done - Submit Revision of 'Diameter Network Access Server = Application >> - >>>> RFC 4005bis' as DIME working group item Sep 201x - Submit = 'Diameter >>>> Application Design Guidelines' to the IESG for consideration as a = BCP >>>> document >>>> Done - Submit 'Diameter NAT Control Application' to the IESG = for >>>> consideration as a Proposed Standard >>>> Sep 201x - Submit 'Realm-Based Redirection In Diameter' to the IESG >>>> for consideration as a Proposed Standard >>>> Done - Submit 'Diameter IKEv2 PSK' to the IESG for = consideration as a >>>> Proposed Standard >>>> Done - Submit 'Diameter Extended NAPTR' to the IESG for >> consideration >>>> as a Proposed Standard >>>> Nov 2011 - Submit 'Diameter Support for Proxy Mobile IPv6 Localized >>>> Routing' to the IESG for consideration as a Proposed Standard Jul >>>> 201x - Submit 'Diameter Support for EAP Re-authentication Protocol' >>>> to the IESG for consideration as a Proposed Standard Sep 201x - >>>> Submit Revision of 'Diameter Network Access Server Application - = RFC >>>> 4005bis' to the IESG for consideration as a Proposed Standard >>>>=20 >>>>=20 >>>> _______________________________________________ >>>> DiME mailing list >>>> DiME@ietf.org >>>> https://www.ietf.org/mailman/listinfo/dime >=20 From jouni.nospam@gmail.com Wed Dec 7 03:18:39 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4877D21F8438 for ; Wed, 7 Dec 2011 03:18:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wuppAOsIxyP6 for ; Wed, 7 Dec 2011 03:18:38 -0800 (PST) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0E31121F853E for ; Wed, 7 Dec 2011 03:18:37 -0800 (PST) Received: by laap9 with SMTP id p9so182003laa.31 for ; Wed, 07 Dec 2011 03:18:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=62Guw8mCN5Ys3JpygqFfjtrgp9MGBZiOtCRXkjyF18w=; b=B45bYhl37wqyYbgV1ICHGcCRhFsN+B4HOcimSRcBZp86gW3DAAKKMEndeT2omLMPrf NW/xRHSb87PENhkXBcDdIZp683L/BcESNl1LcDaTDP7bh29J3SMikHgXQtAtYWNPgxe1 980OXXr4bbg/DM8RRcP2Dk5jJzwQu6krWHJUs= Received: by 10.152.109.199 with SMTP id hu7mr11632650lab.16.1323256717030; Wed, 07 Dec 2011 03:18:37 -0800 (PST) Received: from a88-112-207-66.elisa-laajakaista.fi (a88-112-207-66.elisa-laajakaista.fi. [88.112.207.66]) by mx.google.com with ESMTPS id no9sm1315165lab.0.2011.12.07.03.18.35 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 07 Dec 2011 03:18:35 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) From: jouni korhonen In-Reply-To: <69756203DDDDE64E987BC4F70B71A26D24D15F22@Polydeuces.office.hd> Date: Wed, 7 Dec 2011 13:16:57 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> <69756203DDDDE64E987BC4F70B71A26D24D156CD@Polydeuces.office.hd> <524F99B4-8224-47CF-93AD-F8FF52F106FE@gmail.com> <69756203DDDDE64E987BC4F70B71A26D24D15F22@Polydeuces.office.hd> To: dime@ietf.org X-Mailer: Apple Mail (2.1084) Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 07 Dec 2011 11:18:39 -0000 Folks, Yet another revision.=20 - Jouni -------------- 2011-xx-yy charter Diameter Maintenance and Extensions (dime) ------------------------------------------ Charter Current Status: Active Chairs: Lionel Morand Jouni Korhonen Operations and Management Area Directors: Dan Romascanu Ronald Bonica Operations and Management Area Advisor: Dan Romascanu Mailing Lists: General Discussion: dime@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/dime Archive: = http://www.ietf.org/mail-archive/web/dime/current/maillist.html =20 =20 Description of Working Group: The Diameter Maintenance and Extensions WG will focus on maintenance and extensions to the Diameter protocol required to enable its use for authentication, authorization, accounting, charging in network access, provisioning of configuration information within the network, and = other signaling purposes. The DIME working group plans to address the following items: - Maintaining and/or progressing, along the standards track, the Diameter Base protocol and Diameter Applications. This includes extensions to Diameter Base protocol that can be considered as = enhanced features or bug fixes. - Diameter application design guideline. This document will provide guidelines for design of Diameter extensions. It will detail when to consider reusing an existing application and when to develop a new application. - Protocol extensions for the management of Diameter entities. This = work focuses on the standardization of Management Information Bases (MIBs) to configure Diameter entities (such as the Diameter Base protocol or Diameter Credit Control nodes). The usage of other management = protocols for configuring Diameter entities may be future work within the group. - Protocol extension for bulk and group signaling. The aim of this work is to study and standardize a solution for handling groups of sessions within the Diameter base protocol context. The solution would define how to identify and handle grouped sessions in commands and operations. Additionally, Diameter-based systems require interoperability in order to work. The working group, along with the AD, will need to evaluate any potential extensions and require verification that the proposed extension is needed. Coordination with other IETF working groups and other SDOs will be used to ensure this. =20 =20 Goals and Milestones: Done - Submit the following two Diameter Mobility documents to the = IESG for consideration as a Proposed Standards:* 'Diameter Mobile IPv6: = Support for Home Agent to Diameter Server Interaction' * 'Diameter = Mobile IPv6: Support for Network Access Server to Diameter Server = Interaction' Done - Submit 'Diameter API' to the IESG for consideration as an = Informational RFC Done - Submit 'Quality of Service Parameters for Usage with = Diameter' to the IESG for consideration as a Proposed Standard. Done - Submit 'Diameter QoS Application' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter Support for EAP Re-authentication = Protocol' as DIME working group item Done - Submit 'Diameter User-Name and Realm Based Request Routing = Clarifications' as DIME working group item Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group = item Done - Submit 'Quality of Service Attributes for Diameter' to the = IESG for consideration as a Proposed Standard Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter User-Name and Realm Based Request Routing = Clarifications' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter NAT Control Application' as DIME working = group item Done - Submit 'Diameter Capabilities Update' as DIME working group = item Done - Submit ' Diameter Credit Control Application MIB' to the = IESG for consideration as an Informational RFC Done - Submit 'Diameter Base Protocol MIB' to the IESG for = consideration as an Informational RFC Done - Submit 'Diameter Capabilities Update' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter Extended NAPTR' as DIME working group item Done - Submit 'Realm-Based Redirection In Diameter' as DIME = working group item Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized = Routing' as DIME working group item Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key Transport' as DIME working group item Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME = working group item Done - Submit 'Diameter IKEv2 PSK' as DIME working group item Done - Submit Revision of 'Diameter Base Protocol' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key Transport' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter Priority Attribute Value Pairs' to the = IESG for consideration as a Proposed Standard Done - Submit Revision of 'Diameter Network Access Server = Application - RFC 4005bis' as DIME working group item Sep 201x - Submit 'Diameter Application Design Guidelines' to the IESG = for consideration as a BCP document Done - Submit 'Diameter NAT Control Application' to the IESG for = consideration as a Proposed Standard Sep 201x - Submit 'Realm-Based Redirection In Diameter' to the IESG = for consideration as a Proposed Standard Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration = as a Proposed Standard Done - Submit 'Diameter Extended NAPTR' to the IESG for = consideration as a Proposed Standard Nov 2011 - Submit 'Diameter Support for Proxy Mobile IPv6 Localized = Routing' to the IESG for consideration as a Proposed Standard Jul 201x - Submit 'Diameter Support for EAP Re-authentication = Protocol' to the IESG for consideration as a Proposed Standard Sep 201x - Submit Revision of 'Diameter Network Access Server = Application - RFC 4005bis' to the IESG for consideration as a Proposed = Standard From Marco.Liebsch@neclab.eu Wed Dec 7 03:25:19 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 138C921F8A7A for ; Wed, 7 Dec 2011 03:25:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H1chxF4t5QyD for ; Wed, 7 Dec 2011 03:25:18 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 999E221F8A4B for ; Wed, 7 Dec 2011 03:25:17 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id E5DC2280001C8; Wed, 7 Dec 2011 12:25:16 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas1.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3lgkrou9Ad4k; Wed, 7 Dec 2011 12:25:16 +0100 (CET) Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id C3A6728000085; Wed, 7 Dec 2011 12:25:06 +0100 (CET) Received: from Polydeuces.office.hd ([169.254.3.40]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Wed, 7 Dec 2011 12:25:06 +0100 From: Marco Liebsch To: jouni korhonen Thread-Topic: [Dime] re-chartering Thread-Index: AQHMqbWhX5qzDvK+tUWyVr3a+tBLeZXCdymAgAKsrQCAACdn4IACJg6AgADUxgCAB/jxgIAAEuZQ Date: Wed, 7 Dec 2011 11:25:05 +0000 Message-ID: <69756203DDDDE64E987BC4F70B71A26D24D18CAC@Polydeuces.office.hd> References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> <69756203DDDDE64E987BC4F70B71A26D24D156CD@Polydeuces.office.hd> <524F99B4-8224-47CF-93AD-F8FF52F106FE@gmail.com> <69756203DDDDE64E987BC4F70B71A26D24D15F22@Polydeuces.office.hd> In-Reply-To: Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.6.212] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dime@ietf.org" Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 07 Dec 2011 11:25:19 -0000 Jouni, I am fine with both of your proposals below. Thanks, marco > -----Original Message----- > From: jouni korhonen [mailto:jouni.nospam@gmail.com] > Sent: Mittwoch, 7. Dezember 2011 12:16 > To: Marco Liebsch > Cc: dime@ietf.org > Subject: Re: [Dime] re-chartering >=20 > Marco, >=20 > On Dec 2, 2011, at 10:40 AM, Marco Liebsch wrote: >=20 > > Hi Jouni, > > > > please see my feedback inline. > > > >> -----Original Message----- > >> From: jouni korhonen [mailto:jouni.nospam@gmail.com] > >> Sent: Donnerstag, 1. Dezember 2011 21:50 > >> To: Marco Liebsch > >> Cc: dime@ietf.org > >> Subject: Re: [Dime] re-chartering > >> > >> Hi Marco, > >> > >> Thanks for the input. See inline. > >> > >> On Nov 30, 2011, at 1:33 PM, Marco Liebsch wrote: > >> > >>> Hi Jouni, > >>> thanks for the updated charter proposal. Please find some minor > >>> comments and proposals inline. > >>> > >>> The Diameter Maintenance and Extensions WG will focus on > maintenance > >>> and extensions to the Diameter protocol required to enable its use > >>> for authentication, authorization, accounting, charging in network > >>> access, provisioning /+ of +/ configuration information within the > >>> network, and other signaling purposes. > >> > >> Ack. > >> > >>> > >>> .. > >>> > >>> Original text about the bulk operations work item: > >>> - Protocol extension for a bulk and group signaling. The aim of this > >>> work is to study and standardize a solution for handling a group of > >>> sessions within the Diameter base protocol context. The solution > >>> would define how to identify and handle grouped sessions as a one > >>> combined entity for commands and operations. > >>> > >>> If we plan to look at bulk operation use cases also for NASREQ and > >>> Credit Control applications, we may not refer to '..Diameter base > >>> protocol > >> context', which I understand as RFC3588. > >>> > >>> Also, the last sentence about '..as a one combined entity' is not so > >>> clear to > >> me. > >> > >> Right. Bad wording. What I meant by "handle grouped sessions as a one > >> combined entity" is merely like being able to name a group of session > >> with a single name/identity and use that in signaling. In that sense > >> one message would be targeted to one combine set (=3Dentity) of sessio= n. > > > > Sure, that's the optimal case. But does the charter text need to > > comprise this as requirement? Why not opt for group operation by > > identifying the group of users with a list of Session-IDs? No strong > > opinion here, so if you think the text is clear, fine. >=20 > How about "The solution would define how to identify and handle grouped > sessions in commands and operations." >=20 >=20 > >>> What about the following: > >>> > >>> - Protocol extension for /- a -/ bulk and group signaling. The aim > >>> of this work is to study and standardize a solution for handling > >>> /-a-/ group/+s+/ of > >> > >> So multiple groups..? > > > > Not within the same operation. But separate bulk operations could be > > done in the context of different groups. So, multiple groups. If the > > text points to a single bulk operation, then it's one group. > > > >> > >>> sessions within /-the Diameter base protocol -/ /+ Diameter > applications' > >> +/ context. > >> > >> So you would not extend the base protocol, rather each application > >> separately using some well-defined rule? Would this them imply that a > >> new application need explicitly stated & described support for > >> bulk/group signaling? > > > > If we can extend the base with a mechanism for bulk operation that can > > be applied by individual applications, that would be a good choice. My > > only concerns with the written text was to limit bulk operation to > > messages of the base protocol (3588) and to exclude other > > applications' messages from being bulk-operation enabled. >=20 > If the base protocol has support, then each new application can make use = of > it. I think we have not decided yet whether bulk signaling support means > new base protocol messages or something else. At the moment I would like > to keep it in this way. >=20 > - Jouni >=20 >=20 >=20 > > > > marco > > > >> > >> > >>> The solution would define how to identify and handle grouped > >>> sessions /-as a one combined entity for commands and operations-/ > >>> /+and how to signal and perform Diameter operations on these > groups+/. > >> > >> > >> - Jouni > >> > >>> > >>> Thanks, > >>> marco > >>> > >>> > >>> > >>> > >>> > >>>> -----Original Message----- > >>>> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On > >>>> Behalf Of jouni korhonen > >>>> Sent: Mittwoch, 30. November 2011 10:40 > >>>> To: dime@ietf.org > >>>> Subject: Re: [Dime] re-chartering > >>>> > >>>> Folks, > >>>> > >>>> The next revision of the new charter proposal. I added Mark's & > >>>> Lothar's comments. I recall someone had concerns on the intended > >>>> "extension for a bulk and group signaling" solution space the > >>>> current text directs to. If so, just propose changes to the text. > >>>> > >>>> - Jouni > >>>> > >>>> > >>>> > >>>> 2011-xx-yy charter > >>>> Diameter Maintenance and Extensions (dime) > >>>> ------------------------------------------ > >>>> > >>>> Charter > >>>> > >>>> Current Status: Active > >>>> > >>>> Chairs: > >>>> Lionel Morand > >>>> Jouni Korhonen > >>>> > >>>> Operations and Management Area Directors: > >>>> Dan Romascanu > >>>> Ronald Bonica > >>>> > >>>> Operations and Management Area Advisor: > >>>> Dan Romascanu > >>>> > >>>> Mailing Lists: > >>>> General Discussion: dime@ietf.org > >>>> To Subscribe: https://www.ietf.org/mailman/listinfo/dime > >>>> Archive: http://www.ietf.org/mail- > >>>> archive/web/dime/current/maillist.html > >>>> > >>>> > >>>> Description of Working Group: > >>>> > >>>> The Diameter Maintenance and Extensions WG will focus on > >> maintenance > >>>> and extensions to the Diameter protocol required to enable its use > >>>> for authentication, authorization, accounting, charging in network > >>>> access, provisioning configuration information within the network, > >>>> and other signaling purposes. > >>>> > >>>> The DIME working group plans to address the following items: > >>>> > >>>> - Maintaining and/or progressing, along the standards track, the > >>>> Diameter Base protocol and Diameter Applications. This includes > >>>> extensions to Diameter Base protocol that can be considered as > >>>> enhanced features or bug fixes. > >>>> > >>>> - Diameter application design guideline. This document will provide > >>>> guidelines for design of Diameter extensions. It will detail when > >>>> to consider reusing an existing application and when to develop a > >>>> new application. > >>>> > >>>> - Protocol extensions for the management of Diameter entities. This > >>>> work focuses on the standardization of Management Information > >>>> Bases > >>>> (MIBs) to configure Diameter entities (such as the Diameter Base > >>>> protocol or Diameter Credit Control nodes). The usage of other > >>>> management protocols for configuring Diameter entities may be > >>>> future > >> work within the group. > >>>> > >>>> - Protocol extension for a bulk and group signaling. The aim of > >>>> this work is to study and standardize a solution for handling a > >>>> group of sessions within the Diameter base protocol context. The > >>>> solution would define how to identify and handle grouped sessions > >>>> as a one combined entity for commands and operations. > >>>> > >>>> Additionally, Diameter-based systems require interoperability in > >>>> order to work. The working group, along with the AD, will need to > >>>> evaluate any potential extensions and require verification that > >>>> the proposed extension is needed and an appropriate use of the > >>>> Diameter > >> protocol. > >>>> Coordination with other IETF working groups and other SDOs will be > >>>> used to ensure this. > >>>> > >>>> > >>>> Goals and Milestones: > >>>> Done - Submit the following two Diameter Mobility documents to t= he > >>>> IESG for consideration as a Proposed Standards:* 'Diameter Mobile > IPv6: > >>>> Support for Home Agent to Diameter Server Interaction' * 'Diameter > >>>> Mobile > >>>> IPv6: Support for Network Access Server to Diameter Server > Interaction' > >>>> Done - Submit 'Diameter API' to the IESG for consideration as an > >>>> Informational RFC > >>>> Done - Submit 'Quality of Service Parameters for Usage with > Diameter' > >> to > >>>> the IESG for consideration as a Proposed Standard. > >>>> Done - Submit 'Diameter QoS Application' to the IESG for > consideration > >> as > >>>> a Proposed Standard > >>>> Done - Submit 'Diameter Support for EAP Re-authentication Protoc= ol' > as > >>>> DIME working group item > >>>> Done - Submit 'Diameter User-Name and Realm Based Request > Routing > >>>> Clarifications' as DIME working group item > >>>> Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group > >> item > >>>> Done - Submit 'Quality of Service Attributes for Diameter' to th= e IESG > >> for > >>>> consideration as a Proposed Standard > >>>> Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for > >> consideration > >>>> as a Proposed Standard > >>>> Done - Submit 'Diameter User-Name and Realm Based Request > Routing > >>>> Clarifications' to the IESG for consideration as a Proposed Standard > >>>> Done - Submit 'Diameter NAT Control Application' as DIME working > >> group > >>>> item > >>>> Done - Submit 'Diameter Capabilities Update' as DIME working gro= up > >> item > >>>> Done - Submit ' Diameter Credit Control Application MIB' to the = IESG > for > >>>> consideration as an Informational RFC > >>>> Done - Submit 'Diameter Base Protocol MIB' to the IESG for > >> consideration > >>>> as an Informational RFC > >>>> Done - Submit 'Diameter Capabilities Update' to the IESG for > >> consideration > >>>> as a Proposed Standard > >>>> Done - Submit 'Diameter Extended NAPTR' as DIME working group > item > >>>> Done - Submit 'Realm-Based Redirection In Diameter' as DIME > working > >>>> group item > >>>> Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized > >> Routing' > >>>> as DIME working group item > >>>> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key > >>>> Transport' as DIME working group item > >>>> Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME > working > >>>> group item > >>>> Done - Submit 'Diameter IKEv2 PSK' as DIME working group item > >>>> Done - Submit Revision of 'Diameter Base Protocol' to the IESG f= or > >>>> consideration as a Proposed Standard > >>>> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key > >>>> Transport' to the IESG for consideration as a Proposed Standard > >>>> Done - Submit 'Diameter Priority Attribute Value Pairs' to the I= ESG for > >>>> consideration as a Proposed Standard > >>>> Done - Submit Revision of 'Diameter Network Access Server > Application > >> - > >>>> RFC 4005bis' as DIME working group item Sep 201x - Submit > >>>> 'Diameter Application Design Guidelines' to the IESG for > >>>> consideration as a BCP document > >>>> Done - Submit 'Diameter NAT Control Application' to the IESG for > >>>> consideration as a Proposed Standard Sep 201x - Submit 'Realm-Based > >>>> Redirection In Diameter' to the IESG for consideration as a > >>>> Proposed Standard > >>>> Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration= as a > >>>> Proposed Standard > >>>> Done - Submit 'Diameter Extended NAPTR' to the IESG for > >> consideration > >>>> as a Proposed Standard > >>>> Nov 2011 - Submit 'Diameter Support for Proxy Mobile IPv6 Localized > >>>> Routing' to the IESG for consideration as a Proposed Standard Jul > >>>> 201x - Submit 'Diameter Support for EAP Re-authentication Protocol' > >>>> to the IESG for consideration as a Proposed Standard Sep 201x - > >>>> Submit Revision of 'Diameter Network Access Server Application - > >>>> RFC 4005bis' to the IESG for consideration as a Proposed Standard > >>>> > >>>> > >>>> _______________________________________________ > >>>> DiME mailing list > >>>> DiME@ietf.org > >>>> https://www.ietf.org/mailman/listinfo/dime > > From dromasca@avaya.com Wed Dec 7 03:36:13 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C7BA21F8B74 for ; Wed, 7 Dec 2011 03:36:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.378 X-Spam-Level: X-Spam-Status: No, score=-103.378 tagged_above=-999 required=5 tests=[AWL=0.221, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pnGJs516ytx8 for ; Wed, 7 Dec 2011 03:36:12 -0800 (PST) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 05E3821F8B7A for ; Wed, 7 Dec 2011 03:36:11 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmQAAMpO306HCzI1/2dsb2JhbAA5CpohkDGBBYFyAQEBAQMBAQEPHgo0FwQCAQgNBAQBAQsCBAwLAQYBJh8JCAEBBAESCAESB4dtmkGbLYd9glRjBJpVhH+HOw X-IronPort-AV: E=Sophos;i="4.71,313,1320642000"; d="scan'208";a="318346319" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Dec 2011 06:36:10 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 07 Dec 2011 06:24:11 -0500 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: Wed, 7 Dec 2011 12:36:07 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dime] re-chartering Thread-Index: Acy00gJ10jxjNSwaTCiyR0iy/c2vjAAAeevA References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com><69756203DDDDE64E987BC4F70B71A26D24D156CD@Polydeuces.office.hd><524F99B4-8224-47CF-93AD-F8FF52F106FE@gmail.com><69756203DDDDE64E987BC4F70B71A26D24D15F22@Polydeuces.office.hd> From: "Romascanu, Dan (Dan)" To: "jouni korhonen" , Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 07 Dec 2011 11:36:13 -0000 Hi, What is the answer to the question that can be asked (and will be asked) - what does 'other signaling purposes' mean in the first paragraph?=20 Thanks and Regards, Dan > -----Original Message----- > From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of > jouni korhonen > Sent: Wednesday, December 07, 2011 1:17 PM > To: dime@ietf.org > Subject: Re: [Dime] re-chartering >=20 > Folks, >=20 > Yet another revision. >=20 > - Jouni >=20 > -------------- >=20 >=20 >=20 > 2011-xx-yy charter > Diameter Maintenance and Extensions (dime) > ------------------------------------------ >=20 > Charter >=20 > Current Status: Active >=20 > Chairs: > Lionel Morand > Jouni Korhonen >=20 > Operations and Management Area Directors: > Dan Romascanu > Ronald Bonica >=20 > Operations and Management Area Advisor: > Dan Romascanu >=20 > Mailing Lists: > General Discussion: dime@ietf.org > To Subscribe: https://www.ietf.org/mailman/listinfo/dime > Archive: http://www.ietf.org/mail- > archive/web/dime/current/maillist.html >=20 >=20 > Description of Working Group: >=20 > The Diameter Maintenance and Extensions WG will focus on maintenance > and extensions to the Diameter protocol required to enable its use > for > authentication, authorization, accounting, charging in network > access, > provisioning of configuration information within the network, and > other > signaling purposes. >=20 > The DIME working group plans to address the following items: >=20 > - Maintaining and/or progressing, along the standards track, the > Diameter Base protocol and Diameter Applications. This includes > extensions to Diameter Base protocol that can be considered as > enhanced > features or bug fixes. >=20 > - Diameter application design guideline. This document will provide > guidelines for design of Diameter extensions. It will detail when to > consider reusing an existing application and when to develop a new > application. >=20 > - Protocol extensions for the management of Diameter entities. This > work > focuses on the standardization of Management Information Bases (MIBs) > to configure Diameter entities (such as the Diameter Base protocol or > Diameter Credit Control nodes). The usage of other management > protocols > for configuring Diameter entities may be future work within the > group. >=20 > - Protocol extension for bulk and group signaling. The aim of this > work is to study and standardize a solution for handling groups of > sessions within the Diameter base protocol context. The solution > would > define how to identify and handle grouped sessions in commands and > operations. >=20 > Additionally, Diameter-based systems require interoperability in > order > to work. The working group, along with the AD, will need to evaluate > any potential extensions and require verification that the proposed > extension is needed. Coordination with other IETF working groups and > other SDOs will be used to ensure this. >=20 >=20 > Goals and Milestones: > Done - Submit the following two Diameter Mobility documents to > the IESG for consideration as a Proposed Standards:* 'Diameter Mobile > IPv6: Support for Home Agent to Diameter Server Interaction' * > 'Diameter Mobile IPv6: Support for Network Access Server to Diameter > Server Interaction' > Done - Submit 'Diameter API' to the IESG for consideration as an > Informational RFC > Done - Submit 'Quality of Service Parameters for Usage with > Diameter' to the IESG for consideration as a Proposed Standard. > Done - Submit 'Diameter QoS Application' to the IESG for > consideration as a Proposed Standard > Done - Submit 'Diameter Support for EAP Re-authentication > Protocol' as DIME working group item > Done - Submit 'Diameter User-Name and Realm Based Request Routing > Clarifications' as DIME working group item > Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group > item > Done - Submit 'Quality of Service Attributes for Diameter' to the > IESG for consideration as a Proposed Standard > Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for > consideration as a Proposed Standard > Done - Submit 'Diameter User-Name and Realm Based Request Routing > Clarifications' to the IESG for consideration as a Proposed Standard > Done - Submit 'Diameter NAT Control Application' as DIME working > group item > Done - Submit 'Diameter Capabilities Update' as DIME working > group item > Done - Submit ' Diameter Credit Control Application MIB' to the > IESG for consideration as an Informational RFC > Done - Submit 'Diameter Base Protocol MIB' to the IESG for > consideration as an Informational RFC > Done - Submit 'Diameter Capabilities Update' to the IESG for > consideration as a Proposed Standard > Done - Submit 'Diameter Extended NAPTR' as DIME working group > item > Done - Submit 'Realm-Based Redirection In Diameter' as DIME > working group item > Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized > Routing' as DIME working group item > Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic > Key Transport' as DIME working group item > Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME > working group item > Done - Submit 'Diameter IKEv2 PSK' as DIME working group item > Done - Submit Revision of 'Diameter Base Protocol' to the IESG > for consideration as a Proposed Standard > Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic > Key Transport' to the IESG for consideration as a Proposed Standard > Done - Submit 'Diameter Priority Attribute Value Pairs' to the > IESG for consideration as a Proposed Standard > Done - Submit Revision of 'Diameter Network Access Server > Application - RFC 4005bis' as DIME working group item > Sep 201x - Submit 'Diameter Application Design Guidelines' to the > IESG for consideration as a BCP document > Done - Submit 'Diameter NAT Control Application' to the IESG for > consideration as a Proposed Standard > Sep 201x - Submit 'Realm-Based Redirection In Diameter' to the IESG > for consideration as a Proposed Standard > Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration > as a Proposed Standard > Done - Submit 'Diameter Extended NAPTR' to the IESG for > consideration as a Proposed Standard > Nov 2011 - Submit 'Diameter Support for Proxy Mobile IPv6 Localized > Routing' to the IESG for consideration as a Proposed Standard > Jul 201x - Submit 'Diameter Support for EAP Re-authentication > Protocol' to the IESG for consideration as a Proposed Standard > Sep 201x - Submit Revision of 'Diameter Network Access Server > Application - RFC 4005bis' to the IESG for consideration as a Proposed > Standard >=20 >=20 >=20 >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Thu Dec 8 11:55:41 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B695F21F854D for ; Thu, 8 Dec 2011 11:55:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.562 X-Spam-Level: X-Spam-Status: No, score=-3.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4gPVd7Q5F8L1 for ; Thu, 8 Dec 2011 11:55:40 -0800 (PST) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB0D21F84C9 for ; Thu, 8 Dec 2011 11:55:40 -0800 (PST) Received: by laah2 with SMTP id h2so100338laa.31 for ; Thu, 08 Dec 2011 11:55:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Agn3hSQI5AAWCjGRhTRKgzfiB/2E0+Oi2whqiHYmRSw=; b=WsOOPJ19UvLBeKiYn4b1IMFip8e53NnXoX92jeX8/bT+yHA2EEHIiIgAl5PE7LKzAe ZXSdaYNlKwWnpAPW/qb7rWzFP0PZUwVsiyy6yfZ8vekad3t/8Bu1pVxxnIL3FOaF5pL0 l2GLwqG8BiBErVckLzdsTMyi29occuRORA868= Received: by 10.152.123.9 with SMTP id lw9mr2911049lab.12.1323374139212; Thu, 08 Dec 2011 11:55:39 -0800 (PST) Received: from [188.117.15.108] ([188.117.15.108]) by mx.google.com with ESMTPS id nw10sm5462223lab.4.2011.12.08.11.55.35 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 08 Dec 2011 11:55:36 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: Date: Thu, 8 Dec 2011 21:55:34 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com><69756203DDDDE64E987BC4F70B71A26D24D156CD@Polydeuces.office.hd><524F99B4-8224-47CF-93AD-F8FF52F106FE@gmail.com><69756203DDDDE64E987BC4F70B71A26D24D15F22@Polydeuces.office.hd> To: "Romascanu, Dan (Dan)" X-Mailer: Apple Mail (2.1084) Cc: dime@ietf.org Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 08 Dec 2011 19:55:41 -0000 Dan, On Dec 7, 2011, at 1:36 PM, Romascanu, Dan (Dan) wrote: > Hi, >=20 > What is the answer to the question that can be asked (and will be = asked) > - what does 'other signaling purposes' mean in the first paragraph?=20 Right. Good point. Here we refer to the text in Section 1.1 about new = uses of Diameter. Maybe following rewording helps: The Diameter Maintenance and Extensions WG will focus on maintenance and extensions to the Diameter protocol required to enable its use for authentication, authorization, accounting, charging in network access, provisioning of configuration information within the network, and for new signaling uses within the extensibility rules of Diameter. I.e. within a new application we are rightfully allowed to use Diameter = beyond authentication and accounting applications. At least that is my = understanding of the Section 1.1 "tone": ... network access [NASREQ]. It is also possible for the base protocol to be extended for use in new applications, via the addition of new commands or AVPs. At this time the focus of Diameter is network access and accounting applications. A truly generic AAA protocol ... - Jouni >=20 > Thanks and Regards, >=20 > Dan >=20 >=20 >=20 >=20 >> -----Original Message----- >> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf > Of >> jouni korhonen >> Sent: Wednesday, December 07, 2011 1:17 PM >> To: dime@ietf.org >> Subject: Re: [Dime] re-chartering >>=20 >> Folks, >>=20 >> Yet another revision. >>=20 >> - Jouni >>=20 >> -------------- >>=20 >>=20 >>=20 >> 2011-xx-yy charter >> Diameter Maintenance and Extensions (dime) >> ------------------------------------------ >>=20 >> Charter >>=20 >> Current Status: Active >>=20 >> Chairs: >> Lionel Morand >> Jouni Korhonen >>=20 >> Operations and Management Area Directors: >> Dan Romascanu >> Ronald Bonica >>=20 >> Operations and Management Area Advisor: >> Dan Romascanu >>=20 >> Mailing Lists: >> General Discussion: dime@ietf.org >> To Subscribe: https://www.ietf.org/mailman/listinfo/dime >> Archive: http://www.ietf.org/mail- >> archive/web/dime/current/maillist.html >>=20 >>=20 >> Description of Working Group: >>=20 >> The Diameter Maintenance and Extensions WG will focus on maintenance >> and extensions to the Diameter protocol required to enable its use >> for >> authentication, authorization, accounting, charging in network >> access, >> provisioning of configuration information within the network, and >> other >> signaling purposes. >>=20 >> The DIME working group plans to address the following items: >>=20 >> - Maintaining and/or progressing, along the standards track, the >> Diameter Base protocol and Diameter Applications. This includes >> extensions to Diameter Base protocol that can be considered as >> enhanced >> features or bug fixes. >>=20 >> - Diameter application design guideline. This document will provide >> guidelines for design of Diameter extensions. It will detail when to >> consider reusing an existing application and when to develop a new >> application. >>=20 >> - Protocol extensions for the management of Diameter entities. This >> work >> focuses on the standardization of Management Information Bases > (MIBs) >> to configure Diameter entities (such as the Diameter Base protocol > or >> Diameter Credit Control nodes). The usage of other management >> protocols >> for configuring Diameter entities may be future work within the >> group. >>=20 >> - Protocol extension for bulk and group signaling. The aim of this >> work is to study and standardize a solution for handling groups of >> sessions within the Diameter base protocol context. The solution >> would >> define how to identify and handle grouped sessions in commands and >> operations. >>=20 >> Additionally, Diameter-based systems require interoperability in >> order >> to work. The working group, along with the AD, will need to evaluate >> any potential extensions and require verification that the proposed >> extension is needed. Coordination with other IETF working groups and >> other SDOs will be used to ensure this. >>=20 >>=20 >> Goals and Milestones: >> Done - Submit the following two Diameter Mobility documents to >> the IESG for consideration as a Proposed Standards:* 'Diameter Mobile >> IPv6: Support for Home Agent to Diameter Server Interaction' * >> 'Diameter Mobile IPv6: Support for Network Access Server to Diameter >> Server Interaction' >> Done - Submit 'Diameter API' to the IESG for consideration as an >> Informational RFC >> Done - Submit 'Quality of Service Parameters for Usage with >> Diameter' to the IESG for consideration as a Proposed Standard. >> Done - Submit 'Diameter QoS Application' to the IESG for >> consideration as a Proposed Standard >> Done - Submit 'Diameter Support for EAP Re-authentication >> Protocol' as DIME working group item >> Done - Submit 'Diameter User-Name and Realm Based Request > Routing >> Clarifications' as DIME working group item >> Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group >> item >> Done - Submit 'Quality of Service Attributes for Diameter' to > the >> IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for >> consideration as a Proposed Standard >> Done - Submit 'Diameter User-Name and Realm Based Request > Routing >> Clarifications' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter NAT Control Application' as DIME working >> group item >> Done - Submit 'Diameter Capabilities Update' as DIME working >> group item >> Done - Submit ' Diameter Credit Control Application MIB' to the >> IESG for consideration as an Informational RFC >> Done - Submit 'Diameter Base Protocol MIB' to the IESG for >> consideration as an Informational RFC >> Done - Submit 'Diameter Capabilities Update' to the IESG for >> consideration as a Proposed Standard >> Done - Submit 'Diameter Extended NAPTR' as DIME working group >> item >> Done - Submit 'Realm-Based Redirection In Diameter' as DIME >> working group item >> Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized >> Routing' as DIME working group item >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic >> Key Transport' as DIME working group item >> Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME >> working group item >> Done - Submit 'Diameter IKEv2 PSK' as DIME working group item >> Done - Submit Revision of 'Diameter Base Protocol' to the IESG >> for consideration as a Proposed Standard >> Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic >> Key Transport' to the IESG for consideration as a Proposed Standard >> Done - Submit 'Diameter Priority Attribute Value Pairs' to the >> IESG for consideration as a Proposed Standard >> Done - Submit Revision of 'Diameter Network Access Server >> Application - RFC 4005bis' as DIME working group item >> Sep 201x - Submit 'Diameter Application Design Guidelines' to the >> IESG for consideration as a BCP document >> Done - Submit 'Diameter NAT Control Application' to the IESG for >> consideration as a Proposed Standard >> Sep 201x - Submit 'Realm-Based Redirection In Diameter' to the IESG >> for consideration as a Proposed Standard >> Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration >> as a Proposed Standard >> Done - Submit 'Diameter Extended NAPTR' to the IESG for >> consideration as a Proposed Standard >> Nov 2011 - Submit 'Diameter Support for Proxy Mobile IPv6 Localized >> Routing' to the IESG for consideration as a Proposed Standard >> Jul 201x - Submit 'Diameter Support for EAP Re-authentication >> Protocol' to the IESG for consideration as a Proposed Standard >> Sep 201x - Submit Revision of 'Diameter Network Access Server >> Application - RFC 4005bis' to the IESG for consideration as a = Proposed >> Standard >>=20 >>=20 >>=20 >>=20 >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime From lionel.morand@orange.com Tue Dec 13 04:53:15 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18DBB21F8AC9; Tue, 13 Dec 2011 04:53:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.248 X-Spam-Level: X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R0SNE3Xl4iaU; Tue, 13 Dec 2011 04:53:11 -0800 (PST) Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by ietfa.amsl.com (Postfix) with ESMTP id 6018721F8A97; Tue, 13 Dec 2011 04:53:10 -0800 (PST) Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 4AD14AB0013; Tue, 13 Dec 2011 13:54:16 +0100 (CET) Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id 2EFCAAB000E; Tue, 13 Dec 2011 13:54:16 +0100 (CET) Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Tue, 13 Dec 2011 13:53:08 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCB996.29955947" Date: Tue, 13 Dec 2011 13:52:58 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Publication request for Diameter Support for Proxy Mobile IPv6 Localized Routing Thread-Index: Acy5liOg9AtSfE+XRsOZbY7zKwkrUw== From: To: X-OriginalArrivalTime: 13 Dec 2011 12:53:08.0328 (UTC) FILETIME=[29BB5E80:01CCB996] Cc: dime@ietf.org, dime-chairs@tools.ietf.org Subject: [Dime] Publication request for Diameter Support for Proxy Mobile IPv6 Localized Routing X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 13 Dec 2011 12:53:15 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CCB996.29955947 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear Secretary, =20 This is a request for publication of the Internet-Draft "draft-ietf-dime-pmip6-lr-06" as a standards track RFC. Please find below the document shepherd proto write-up. =20 Best Regards. =20 Lionel =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D PROTO WRITEUP for draft-ietf-dime-pmip6-lr-06.txt =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 =20 http://tools.ietf.org/html/draft-ietf-dime-pmip6-lr-06 =20 =20 (1.a) Who is the Document Shepherd for this document? Has the Document Shepherd personally reviewed this version of the=20 document and, in particular, does he or she believe this=20 version is ready for forwarding to the IESG for publication?=20 =20 -- Lionel Morand (lionel.morand@orange.com) is the Document Shepherd, Dime co-chair. He has done a review on the document and believes it is ready to be forwarded to IESG for publication. =20 (1.b) Has the document had adequate review both from key WG members=20 and from key non-WG members? Does the Document Shepherd have=20 any concerns about the depth or breadth of the reviews that=20 have been performed? =20 =20 -- The document has been discussed in the DIME WG for more than two=20 years, with different reviews of the updated version of the draft.=20 The lastest version is the result of the consensus reached after discussion. However, only one review was done during the WGLC.=20 =20 The shepherd has reviewed the document himself and has no issue with it. Nor the shepherd has issues with the reviews done by others. =20 (1.c) Does the Document Shepherd have concerns that the document=20 needs more review from a particular or broader perspective,=20 e.g., security, operational complexity, someone familiar with=20 AAA, internationalization or XML?=20 =20 -- No. =20 =20 (1.d) Does the Document Shepherd have any specific concerns or=20 issues with this document that the Responsible Area Director and/or the IESG should be aware of? For example, perhaps he=20 or she is uncomfortable with certain parts of the document, or=20 has concerns whether there really is a need for it. In any=20 event, if the WG has discussed those issues and has indicated=20 that it still wishes to advance the document, detail those=20 concerns here. Has an IPR disclosure related to this document=20 been filed? If so, please include a reference to the=20 disclosure and summarize the WG discussion and conclusion on=20 this issue.=20 =20 -- No. =20 =20 (1.e) How solid is the WG consensus behind this document? Does it=20 represent the strong concurrence of a few individuals, with=20 others being silent, or does the WG as a whole understand and=20 agree with it? =20 =20 -- There is Dime WG consensus behind the document. =20 =20 (1.f) Has anyone threatened an appeal or otherwise indicated extreme=20 discontent? If so, please summarise the areas of conflict in=20 separate email messages to the Responsible Area Director. (It=20 should be in a separate email because this questionnaire is=20 entered into the ID Tracker.)=20 =20 -- No. =20 (1.g) Has the Document Shepherd personally verified that the=20 document satisfies all ID nits? (See the Internet-Drafts Checklist=20 and http://tools.ietf.org/tools/idnits/). Boilerplate checks are not enough; this check needs to be thorough. Has the document=20 met all formal review criteria it needs to, such as the MIB=20 Doctor, media type and URI type reviews?=20 =20 -- The shepherd has checked the document with the idnits tool and found no critical issues.. =20 The document does not need MIB doctor review. The document does not contain any media and URI types. =20 (1.h) Has the document split its references into normative and=20 informative? Are there normative references to documents that=20 are not ready for advancement or are otherwise in an unclear=20 state? If such normative references exist, what is the=20 strategy for their completion? Are there normative references=20 that are downward references, as described in [RFC3967]? If=20 so, list these downward references to support the Area=20 Director in the Last Call procedure for them [RFC3967].=20 =20 -- References are split accordingly. There is no normative reference=20 to documents with unclear status or are in progress. =20 (1.i) Has the Document Shepherd verified that the document IANA=20 consideration section exists and is consistent with the body=20 of the document? If the document specifies protocol=20 extensions, are reservations requested in appropriate IANA=20 registries? Are the IANA registries clearly identified? If=20 the document creates a new registry, does it define the=20 proposed initial contents of the registry and an allocation=20 procedure for future registrations? Does it suggest a=20 reasonable name for the new registry? See [RFC5226]. If the=20 document describes an Expert Review process has Shepherd=20 conferred with the Responsible Area Director so that the IESG=20 can appoint the needed Expert during the IESG Evaluation?=20 =20 -- This document only defines new value in the Mobility Capability registry (created by the RFC 5447) for use with the=20 MIP6-Feature-Vector AVP and requests IANA for value=20 assignment in the existing registry. =20 =20 (1.j) Has the Document Shepherd verified that sections of the=20 document that are written in a formal language, such as XML=20 code, BNF rules, MIB definitions, etc., validate correctly in=20 an automated checker?=20 =20 -- N/A =20 =20 (1.k) The IESG approval announcement includes a Document=20 Announcement Write-Up. Please provide such a Document=20 Announcement Write-Up? Recent examples can be found in the "Action" announcements for approved documents. The approval=20 announcement contains the following sections:=20 =20 Technical Summary=20 =20 -- =20 This document describes AAA support for the authorization and discovery of Proxy Mobile IPv6 mobility entities (i.e. Local Mobility=20 Anchors and Mobile Access Gateways) during localized routing. =20 For this purpose, the document defines a new value for the MIP6-Feature-Vector AVP originally defined in the RFC 5447 to indicate that Direct routing of IP packets between MNs anchored to the different MAG without involving any LMA is supported. =20 =20 Working Group Summary=20 =20 --- The document was discussed for more than two years in the WG and=20 the document captures the results of the collaborative WG work. =20 Document Quality=20 =20 --- The document is complete, straightforward, simple and well-written. =20 =20 =20 ------_=_NextPart_001_01CCB996.29955947 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear Secretary,

 

This is a request for publication = of the Internet-Draft “draft-ietf-dime-pmip6-lr-= 06” as a standards track = RFC.

Please find below the document shepherd proto = write-up.

 

Best Regards.

 

Lionel

 

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D

 PROTO WRITEUP for = draft-ietf-dime-pmip6-lr-06.txt

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D

 

http://to= ols.ietf.org/html/draft-ietf-dime-pmip6-lr-06

 

 

  (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?

 

         = --

         Lionel = Morand (lionel.morand@orange.com)

         is the = Document Shepherd, Dime co-chair. He has done a = review

         on the = document and believes it is ready to be forwarded = to

         IESG 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? 

 

         = --

         The = document has been discussed in the DIME WG for more than two =

         years,= with different reviews of the updated version of the draft. =

        The lastest = version is the result of the consensus reached

         after = discussion. However, only one review was done during the = WGLC. =

          =            =

         The = shepherd has reviewed the document himself and has = no

         issue with = it. Nor the shepherd has issues with the reviews

         done by = others.

 

  (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?

 

         = --

         = No.

 

 

  (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. =

 

         = --

         = No.

 

 

  (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 = Dime WG consensus behind the document.

 

 

  (1.f) Has anyone threatened = an appeal or otherwise indicated extreme

        discontent? If = so, please summarise 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.)

 

         = --

         = No.

 

  (1.g) Has the Document Shepherd personally verified = that the

        document = satisfies all ID nits? (See the Internet-Drafts Checklist =

        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?

 

         = --

         The = shepherd has checked the document with the idnits tool = and

         found no = critical issues..

 

         The document does not need = MIB doctor review.

         The = document does not contain any media and URI = types.

 

  (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].

 

         = --

         References = are split accordingly. There is no normative reference =

         to = documents with  unclear status or are in = progress.

 

  (1.i) Has the Document Shepherd verified that the = document IANA

        consideration = 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 [RFC5226]. If the

        document = describes an Expert Review process has Shepherd

        conferred with = the Responsible Area Director so that the IESG

        can appoint the = needed Expert during the IESG Evaluation?

 

         = --

         This = document only defines new value in the Mobility = Capability

         registry = (created by the RFC 5447) for use with the

         MIP6-F= eature-Vector AVP and requests IANA for value =

         assign= ment in the existing registry.

 

 

  (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?

 

         = --

       =   N/A

         =

         =

  = (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

 

         = --

        =

       This document = describes AAA support for the authorization and

   =     discovery of Proxy Mobile IPv6 mobility entities = (i.e. Local Mobility

       Anchors and = Mobile Access Gateways) during localized routing.  =

       For this purpose, = the document defines a new value for the

      =  MIP6-Feature-Vector AVP originally defined in the RFC 5447 to = indicate

       that Direct routing of = IP packets between MNs anchored to the different

      =  MAG without involving any LMA is = supported.

         =

         =

     Working Group Summary =

 

         = ---

         The = document was discussed for more than two years in the WG and =

         the = document captures the results of the collaborative WG = work.

 

     Document Quality =

 

         = ---

         The = document is complete, straightforward, simple and = well-written.        =

         =

 

------_=_NextPart_001_01CCB996.29955947-- From jouni.nospam@gmail.com Tue Dec 13 13:18:36 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF3F21F8484 for ; Tue, 13 Dec 2011 13:18:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iK6uaWpz2hFF for ; Tue, 13 Dec 2011 13:18:35 -0800 (PST) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4786A21F8483 for ; Tue, 13 Dec 2011 13:18:35 -0800 (PST) Received: by laah2 with SMTP id h2so55164laa.31 for ; Tue, 13 Dec 2011 13:18:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=EdfHGP2ZcfBvGqqv00IBtIu5Hffnrv+f+se0crA2ySk=; b=ABKyneF0PJJ38rzeRXqsmU8Fp8TOKUwS6LFQqW6V8VOHtbxufGnYzvj03lB1Mw6rps fhm7jiwx4347LNp/B2HDtoI0Jtx/41Z7klsFPy1bg6PLg+Wi7ddQ5PX3VuPTzBiVavsT VVytcd3W9FJsOJc3Lmksw2nNRPiiN3+j/gcRQ= Received: by 10.152.146.100 with SMTP id tb4mr16930600lab.0.1323811113533; Tue, 13 Dec 2011 13:18:33 -0800 (PST) Received: from a88-112-207-66.elisa-laajakaista.fi (a88-112-207-66.elisa-laajakaista.fi. [88.112.207.66]) by mx.google.com with ESMTPS id xw19sm282802lab.9.2011.12.13.13.18.30 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 13 Dec 2011 13:18:31 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: Date: Tue, 13 Dec 2011 23:18:29 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com><69756203DDDDE64E987BC4F70B71A26D24D156CD@Polydeuces.office.hd><524F99B4-8224-47CF-93AD-F8FF52F106FE@gmail.com><69756203DDDDE64E987BC4F70B71A26D24D15F22@Polydeuces.office.hd> To: dime@ietf.org X-Mailer: Apple Mail (2.1084) Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 13 Dec 2011 21:18:36 -0000 Folks,=20 Yet another revision. Any further comments on the charter text? I also = updated the goal & milestones. - Jouni & Lionel 2011-xx-yy charter Diameter Maintenance and Extensions (dime) ------------------------------------------ Charter Current Status: Active Chairs: Lionel Morand Jouni Korhonen Operations and Management Area Directors: Dan Romascanu Ronald Bonica Operations and Management Area Advisor: Dan Romascanu Mailing Lists: General Discussion: dime@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/dime Archive: = http://www.ietf.org/mail-archive/web/dime/current/maillist.html =20 =20 Description of Working Group: The Diameter Maintenance and Extensions WG will focus on maintenance and extensions to the Diameter protocol required to enable its use for authentication, authorization, accounting, charging in network access, provisioning of configuration information within the network, and for new signaling uses within the extensibility rules of the Diameter base protocol. The DIME working group plans to address the following items: - Maintaining and/or progressing, along the standards track, the Diameter Base protocol and Diameter Applications. This includes extensions to Diameter Base protocol that can be considered as = enhanced features or bug fixes. - Diameter application design guideline. This document will provide guidelines for design of Diameter extensions. It will detail when to consider reusing an existing application and when to develop a new application. - Protocol extensions for the management of Diameter entities. This = work focuses on the standardization of Management Information Bases (MIBs) to configure Diameter entities (such as the Diameter Base protocol or Diameter Credit Control nodes). The usage of other management = protocols for configuring Diameter entities may be future work within the group. - Protocol extension for bulk and group signaling. The aim of this work is to study and standardize a solution for handling groups of sessions within the Diameter base protocol context. The solution would define how to identify and handle grouped sessions in commands and operations. Additionally, Diameter-based systems require interoperability in order to work. The working group, along with the AD, will need to evaluate any potential extensions and require verification that the proposed extension is needed. Coordination with other IETF working groups and other SDOs will be used to ensure this. =20 =20 Goals and Milestones: Done - Submit the following two Diameter Mobility documents to the = IESG for consideration as a Proposed Standards:* 'Diameter Mobile IPv6: = Support for Home Agent to Diameter Server Interaction' * 'Diameter = Mobile IPv6: Support for Network Access Server to Diameter Server = Interaction' Done - Submit 'Diameter API' to the IESG for consideration as an = Informational RFC Done - Submit 'Quality of Service Parameters for Usage with = Diameter' to the IESG for consideration as a Proposed Standard. Done - Submit 'Diameter QoS Application' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter Support for EAP Re-authentication = Protocol' as DIME working group item Done - Submit 'Diameter User-Name and Realm Based Request Routing = Clarifications' as DIME working group item Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group = item Done - Submit 'Quality of Service Attributes for Diameter' to the = IESG for consideration as a Proposed Standard Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter User-Name and Realm Based Request Routing = Clarifications' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter NAT Control Application' as DIME working = group item Done - Submit 'Diameter Capabilities Update' as DIME working group = item Done - Submit ' Diameter Credit Control Application MIB' to the = IESG for consideration as an Informational RFC Done - Submit 'Diameter Base Protocol MIB' to the IESG for = consideration as an Informational RFC Done - Submit 'Diameter Capabilities Update' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter Extended NAPTR' as DIME working group item Done - Submit 'Realm-Based Redirection In Diameter' as DIME = working group item Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized = Routing' as DIME working group item Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key Transport' as DIME working group item Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME = working group item Done - Submit 'Diameter IKEv2 PSK' as DIME working group item Done - Submit Revision of 'Diameter Base Protocol' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key Transport' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter Priority Attribute Value Pairs' to the = IESG for consideration as a Proposed Standard Done - Submit Revision of 'Diameter Network Access Server = Application - RFC 4005bis' as DIME working group item Done - Submit 'Diameter NAT Control Application' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration = as a Proposed Standard Done - Submit 'Diameter Extended NAPTR' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized = Routing' to the IESG for consideration as a Proposed =20 Mar 2012 - Submit 'Realm-Based Redirection In Diameter' to the IESG = for consideration as a Proposed Standard Mar 2012 - Submit Revision of 'Diameter Network Access Server = Application - RFC 4005bis' to the IESG for consideration as a Proposed = Standard May 2012 - Submit 'Diameter Application Design Guidelines' to the IESG = for consideration as a BCP document Standard Jul 2012 - Submit 'Diameter Support for EAP Re-authentication = Protocol' to the IESG for consideration as a Proposed Standard From mark@azu.ca Thu Dec 15 08:23:29 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 635DB21F84C1 for ; Thu, 15 Dec 2011 08:23:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.976 X-Spam-Level: X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V3AidTZeZ3rj for ; Thu, 15 Dec 2011 08:23:28 -0800 (PST) Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 06E5B21F84CD for ; Thu, 15 Dec 2011 08:23:27 -0800 (PST) Received: by vcbfk13 with SMTP id fk13so1428472vcb.31 for ; Thu, 15 Dec 2011 08:23:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.66.70 with SMTP id m6mr571804vci.57.1323966207290; Thu, 15 Dec 2011 08:23:27 -0800 (PST) Received: by 10.52.31.9 with HTTP; Thu, 15 Dec 2011 08:23:27 -0800 (PST) In-Reply-To: References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> <69756203DDDDE64E987BC4F70B71A26D24D156CD@Polydeuces.office.hd> <524F99B4-8224-47CF-93AD-F8FF52F106FE@gmail.com> <69756203DDDDE64E987BC4F70B71A26D24D15F22@Polydeuces.office.hd> Date: Thu, 15 Dec 2011 11:23:27 -0500 Message-ID: From: Mark Jones To: dime@ietf.org Content-Type: multipart/alternative; boundary=14dae9cdc89d7aeceb04b423e7cf Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 15 Dec 2011 16:23:29 -0000 --14dae9cdc89d7aeceb04b423e7cf Content-Type: text/plain; charset=ISO-8859-1 On Tue, Dec 13, 2011 at 4:18 PM, jouni korhonen wrote: > > Folks, > > Yet another revision. Any further comments on the charter text? I also > updated the goal & milestones. > > Looks good, Jouni. Assuming Dan accepts the clarification on "new signaling uses", when does this proposal go before the IESG? /Mark > - Jouni & Lionel > > > > > 2011-xx-yy charter > Diameter Maintenance and Extensions (dime) > ------------------------------------------ > > Charter > > Current Status: Active > > Chairs: > Lionel Morand > Jouni Korhonen > > Operations and Management Area Directors: > Dan Romascanu > Ronald Bonica > > Operations and Management Area Advisor: > Dan Romascanu > > Mailing Lists: > General Discussion: dime@ietf.org > To Subscribe: https://www.ietf.org/mailman/listinfo/dime > Archive: > http://www.ietf.org/mail-archive/web/dime/current/maillist.html > > > Description of Working Group: > > The Diameter Maintenance and Extensions WG will focus on maintenance > and extensions to the Diameter protocol required to enable its use for > authentication, authorization, accounting, charging in network access, > provisioning of configuration information within the network, and for > new signaling uses within the extensibility rules of the Diameter base > protocol. > > The DIME working group plans to address the following items: > > - Maintaining and/or progressing, along the standards track, the > Diameter Base protocol and Diameter Applications. This includes > extensions to Diameter Base protocol that can be considered as enhanced > features or bug fixes. > > - Diameter application design guideline. This document will provide > guidelines for design of Diameter extensions. It will detail when to > consider reusing an existing application and when to develop a new > application. > > - Protocol extensions for the management of Diameter entities. This work > focuses on the standardization of Management Information Bases (MIBs) > to configure Diameter entities (such as the Diameter Base protocol or > Diameter Credit Control nodes). The usage of other management protocols > for configuring Diameter entities may be future work within the group. > > - Protocol extension for bulk and group signaling. The aim of this > work is to study and standardize a solution for handling groups of > sessions within the Diameter base protocol context. The solution would > define how to identify and handle grouped sessions in commands and > operations. > > Additionally, Diameter-based systems require interoperability in order > to work. The working group, along with the AD, will need to evaluate > any potential extensions and require verification that the proposed > extension is needed. Coordination with other IETF working groups and > other SDOs will be used to ensure this. > > > Goals and Milestones: > Done - Submit the following two Diameter Mobility documents to the > IESG for consideration as a Proposed Standards:* 'Diameter Mobile IPv6: > Support for Home Agent to Diameter Server Interaction' * 'Diameter Mobile > IPv6: Support for Network Access Server to Diameter Server Interaction' > Done - Submit 'Diameter API' to the IESG for consideration as an > Informational RFC > Done - Submit 'Quality of Service Parameters for Usage with Diameter' > to the IESG for consideration as a Proposed Standard. > Done - Submit 'Diameter QoS Application' to the IESG for > consideration as a Proposed Standard > Done - Submit 'Diameter Support for EAP Re-authentication Protocol' > as DIME working group item > Done - Submit 'Diameter User-Name and Realm Based Request Routing > Clarifications' as DIME working group item > Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group item > Done - Submit 'Quality of Service Attributes for Diameter' to the > IESG for consideration as a Proposed Standard > Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for > consideration as a Proposed Standard > Done - Submit 'Diameter User-Name and Realm Based Request Routing > Clarifications' to the IESG for consideration as a Proposed Standard > Done - Submit 'Diameter NAT Control Application' as DIME working > group item > Done - Submit 'Diameter Capabilities Update' as DIME working group > item > Done - Submit ' Diameter Credit Control Application MIB' to the IESG > for consideration as an Informational RFC > Done - Submit 'Diameter Base Protocol MIB' to the IESG for > consideration as an Informational RFC > Done - Submit 'Diameter Capabilities Update' to the IESG for > consideration as a Proposed Standard > Done - Submit 'Diameter Extended NAPTR' as DIME working group item > Done - Submit 'Realm-Based Redirection In Diameter' as DIME working > group item > Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized > Routing' as DIME working group item > Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic Key > Transport' as DIME working group item > Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME > working group item > Done - Submit 'Diameter IKEv2 PSK' as DIME working group item > Done - Submit Revision of 'Diameter Base Protocol' to the IESG for > consideration as a Proposed Standard > Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic Key > Transport' to the IESG for consideration as a Proposed Standard > Done - Submit 'Diameter Priority Attribute Value Pairs' to the IESG > for consideration as a Proposed Standard > Done - Submit Revision of 'Diameter Network Access Server Application > - RFC 4005bis' as DIME working group item > Done - Submit 'Diameter NAT Control Application' to the IESG for > consideration as a Proposed Standard > Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration as > a Proposed Standard > Done - Submit 'Diameter Extended NAPTR' to the IESG for consideration > as a Proposed Standard > Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized > Routing' to the IESG for consideration as a Proposed > Mar 2012 - Submit 'Realm-Based Redirection In Diameter' to the IESG for > consideration as a Proposed Standard > Mar 2012 - Submit Revision of 'Diameter Network Access Server Application > - RFC 4005bis' to the IESG for consideration as a Proposed Standard > May 2012 - Submit 'Diameter Application Design Guidelines' to the IESG > for consideration as a BCP document Standard > Jul 2012 - Submit 'Diameter Support for EAP Re-authentication Protocol' > to the IESG for consideration as a Proposed Standard > > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime > --14dae9cdc89d7aeceb04b423e7cf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Dec 13, 2011 at 4:18 PM, jouni korh= onen <jouni.= nospam@gmail.com> wrote:

Folks,

Yet another revision. Any further comments on the charter text? I also upda= ted the goal & milestones.


Looks good, Jouni. Assuming Dan accept= s the clarification on "new signaling uses", when does this propo= sal go before the IESG?

/Mark
=A0
- Jouni & Lionel




2011-xx-yy charter
Diameter Maintenance and Extensions (dime)
------------------------------------------

=A0Charter

=A0Current Status: Active

=A0Chairs:
=A0 =A0 Lionel Morand <lionel.morand@orange-ftgroup.com>
=A0 =A0 Jouni Korhonen <jouni= .korhonen@nsn.com>

=A0Operations and Management Area Directors:
=A0 =A0 Dan Romascanu <dromasca@a= vaya.com>
=A0 =A0 Ronald Bonica <rbonica@j= uniper.net>

=A0Operations and Management Area Advisor:
=A0 =A0 Dan Romascanu <dromasca@a= vaya.com>

=A0Mailing Lists:
=A0 =A0 General Discussion: dime@ietf.org=
=A0 =A0 To Subscribe: =A0 =A0 =A0 https://www.ietf.org/mailman/listinfo/dime=
=A0 =A0 Archive: =A0 =A0 =A0 =A0 =A0 =A0http://www.ietf= .org/mail-archive/web/dime/current/maillist.html


Description of Working Group:

=A0The Diameter Maintenance and Extensions WG will focus on maintenance =A0and extensions to the Diameter protocol required to enable its use for<= br> =A0authentication, authorization, accounting, charging in network access,<= br>
=A0provisioning of configuration information withi= n the network, and for
=A0new signaling uses within the extensibility rules of the Diameter= base
=A0protocol.

The DIME working group plans to address the following items:

=A0- Maintaining and/or progressing, along the standards track, the
=A0Diameter Base protocol and Diameter Applications. This includes
=A0extensions to Diameter Base protocol that can be considered as enhanced=
=A0features or bug fixes.

=A0- Diameter application design guideline. This document will provide
=A0guidelines for design of Diameter extensions. It will detail when to =A0consider reusing an existing application and when to develop a new
=A0application.

=A0- Protocol extensions for the management of Diameter entities. This wor= k
=A0focuses on the standardization of Management Information Bases (MIBs) =A0to configure Diameter entities (such as the Diameter Base protocol or =A0Diameter Credit Control nodes). The usage of other management protocols=
=A0for configuring Diameter entities may be future work within the group.<= br>
=A0- Protocol extension for bulk and group signaling. The aim of this
=A0work is to study and standardize a solution for handling groups of
=A0sessions within the Diameter base protocol context. The solution would<= br> =A0define how to identify and handle grouped sessions in commands and
=A0operations.

=A0Additionally, Diameter-based systems require interoperability in order<= br> =A0to work. The working group, along with the AD, will need to evaluate =A0any potential extensions and require verification that the proposed
=A0extension is needed. Coordination with other IETF working groups and =A0other SDOs will be used to ensure this.


Goals and Milestones:
=A0Done =A0 =A0 - Submit the following two Diameter Mobility documents to = the IESG for consideration as a Proposed Standards:* 'Diameter Mobile I= Pv6: Support for Home Agent to Diameter Server Interaction' * 'Diam= eter Mobile IPv6: Support for Network Access Server to Diameter Server Inte= raction'
=A0Done =A0 =A0 - Submit 'Diameter API' to the IESG for considerat= ion as an Informational RFC
=A0Done =A0 =A0 - Submit 'Quality of Service Parameters for Usage with= Diameter' to the IESG for consideration as a Proposed Standard.
=A0Done =A0 =A0 - Submit 'Diameter QoS Application' to the IESG fo= r consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter Support for EAP Re-authentication P= rotocol' as DIME working group item
=A0Done =A0 =A0 - Submit 'Diameter User-Name and Realm Based Request R= outing Clarifications' as DIME working group item
=A0Done =A0 =A0 - Submit 'Diameter Proxy Mobile IPv6' as DIME work= ing group item
=A0Done =A0 =A0 - Submit 'Quality of Service Attributes for Diameter&#= 39; to the IESG for consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter Proxy Mobile IPv6' to the IESG = for consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter User-Name and Realm Based Request R= outing Clarifications' to the IESG for consideration as a Proposed Stan= dard
=A0Done =A0 =A0 - Submit 'Diameter NAT Control Application' as DIM= E working group item
=A0Done =A0 =A0 - Submit 'Diameter Capabilities Update' as DIME wo= rking group item
=A0Done =A0 =A0 - Submit ' Diameter Credit Control Application MIB'= ; to the IESG for consideration as an Informational RFC
=A0Done =A0 =A0 - Submit 'Diameter Base Protocol MIB' to the IESG = for consideration as an Informational RFC
=A0Done =A0 =A0 - Submit 'Diameter Capabilities Update' to the IES= G for consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter Extended NAPTR' as DIME working= group item
=A0Done =A0 =A0 - Submit 'Realm-Based Redirection In Diameter' as = DIME working group item
=A0Done =A0 =A0 - Submit 'Diameter Support for Proxy Mobile IPv6 Local= ized Routing' as DIME working group item
=A0Done =A0 =A0 - Submit 'Diameter Attribute-Value Pairs for Cryptogra= phic Key Transport' as DIME working group item
=A0Done =A0 =A0 - Submit 'Diameter Priority Attribute Value Pairs'= as DIME working group item
=A0Done =A0 =A0 - Submit 'Diameter IKEv2 PSK' as DIME working grou= p item
=A0Done =A0 =A0 - Submit Revision of 'Diameter Base Protocol' to t= he IESG for consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter Attribute-Value Pairs for Cryptogra= phic Key Transport' to the IESG for consideration as a Proposed Standar= d
=A0Done =A0 =A0 - Submit 'Diameter Priority Attribute Value Pairs'= to the IESG for consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit Revision of 'Diameter Network Access Server A= pplication - RFC 4005bis' as DIME working group item
=A0Done =A0 =A0 - Submit 'Diameter NAT C= ontrol Application' to the IESG for consideration as a Proposed Standar= d
=A0Done =A0 =A0 - Submit 'Diameter IKEv2 PSK&#= 39; to the IESG for consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter Extended NAPTR' to the IESG for= consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter Support for Proxy Mobile IPv6= Localized Routing' to the IESG for consideration as a Proposed
=A0Mar 2012 - Submit 'Realm-Based Redirection In Diameter' to the = IESG for consideration as a Proposed Standard
=A0Mar 2012 - Submit Revision of 'Diameter Network Access Server Appli= cation - RFC 4005bis' to the IESG for consideration as a Proposed Stand= ard
=A0May 2012 - Submit 'Diameter Application Design Guidelines' to t= he IESG for consideration as a BCP document Standard
=A0Jul 2012 - Submit 'Diameter Support for EAP Re-authentication Proto= col' to the IESG for consideration as a Proposed Standard


_______________________________________________
DiME mailing list
DiME@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/dime

--14dae9cdc89d7aeceb04b423e7cf-- From jouni.nospam@gmail.com Wed Dec 21 23:15:19 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA6721F8B82 for ; Wed, 21 Dec 2011 23:15:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.98 X-Spam-Level: X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IK0qwAtnihNk for ; Wed, 21 Dec 2011 23:15:18 -0800 (PST) Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id BB0A421F8B4D for ; Wed, 21 Dec 2011 23:15:17 -0800 (PST) Received: by wgbdr13 with SMTP id dr13so11715080wgb.13 for ; Wed, 21 Dec 2011 23:15:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=NUkucjlFhS2HiV+IG4maatHrpJJqa2FcLk+3CqtwVwo=; b=NmaWg7tUkl1mulqqYRo+RhKW39aoqhNCrG1tqN5CknZK84skI+UdLBzQanVi2Zngye 8SQTgC8yJkZUt7iA8k/bShSd/h5wztwsJ7Ih7KYR4ulpnCYoL8OjfOUmZ5GJRnmWUFu6 PMauzPnWALRqrmbPvkalbQq6RPhhOdGnGaXjo= Received: by 10.227.203.78 with SMTP id fh14mr9322371wbb.12.1324538116956; Wed, 21 Dec 2011 23:15:16 -0800 (PST) Received: from [10.255.137.69] ([192.100.123.77]) by mx.google.com with ESMTPS id fi6sm12896615wib.2.2011.12.21.23.15.14 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 21 Dec 2011 23:15:15 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: Date: Thu, 22 Dec 2011 09:15:12 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <4FCEC779-A1AD-4A21-97B8-8AD1C99472C4@gmail.com> References: To: "Romascanu, Dan (Dan)" X-Mailer: Apple Mail (2.1084) Cc: dime@ietf.org Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 22 Dec 2011 07:15:19 -0000 Dan, On Dec 20, 2011, at 7:51 PM, Romascanu, Dan (Dan) wrote: > Yes. > =20 > Can you send me a clean and final version, so that I can ask the = Secretariat to send it for internal review? > =20 > Thanks and Regards, > =20 > Dan > =20 > =20 > =20 Here is the latest revision. NOTE. I actually added a milestone for the = new bulk & group signaling work we wanted to do: o Aug 2012 - Submit a document on 'Protocol extension for bulk and group = signaling' as a working group item o Aug 2013 - Submit a document on 'Protocol extension for bulk and group = signaling' to the IESG for consideration as a Proposed Standard I wanted to give it two meeting cycles..=20 - JOuni = --------------------------------------------------------------------------= ---------- 2011-xx-yy charter Diameter Maintenance and Extensions (dime) ------------------------------------------ Charter Current Status: Active Chairs: Lionel Morand Jouni Korhonen Operations and Management Area Directors: Dan Romascanu Ronald Bonica Operations and Management Area Advisor: Dan Romascanu Mailing Lists: General Discussion: dime@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/dime Archive: = http://www.ietf.org/mail-archive/web/dime/current/maillist.html =20 =20 Description of Working Group: The Diameter Maintenance and Extensions WG will focus on maintenance and extensions to the Diameter protocol required to enable its use for authentication, authorization, accounting, charging in network access, provisioning of configuration information within the network, and for new signaling uses within the extensibility rules of the Diameter base protocol. The DIME working group plans to address the following items: - Maintaining and/or progressing, along the standards track, the Diameter Base protocol and Diameter Applications. This includes extensions to Diameter Base protocol that can be considered as = enhanced features or bug fixes. - Diameter application design guideline. This document will provide guidelines for design of Diameter extensions. It will detail when to consider reusing an existing application and when to develop a new application. - Protocol extensions for the management of Diameter entities. This = work focuses on the standardization of Management Information Bases (MIBs) to configure Diameter entities (such as the Diameter Base protocol or Diameter Credit Control nodes). The usage of other management = protocols for configuring Diameter entities may be future work within the group. - Protocol extension for bulk and group signaling. The aim of this work is to study and standardize a solution for handling groups of sessions within the Diameter base protocol context. The solution would define how to identify and handle grouped sessions in commands and operations. Additionally, Diameter-based systems require interoperability in order to work. The working group, along with the AD, will need to evaluate any potential extensions and require verification that the proposed extension is needed. Coordination with other IETF working groups and other SDOs will be used to ensure this. =20 =20 Goals and Milestones: Done - Submit the following two Diameter Mobility documents to the = IESG for consideration as a Proposed Standards:* 'Diameter Mobile IPv6: = Support for Home Agent to Diameter Server Interaction' * 'Diameter = Mobile IPv6: Support for Network Access Server to Diameter Server = Interaction' Done - Submit 'Diameter API' to the IESG for consideration as an = Informational RFC Done - Submit 'Quality of Service Parameters for Usage with = Diameter' to the IESG for consideration as a Proposed Standard. Done - Submit 'Diameter QoS Application' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter Support for EAP Re-authentication = Protocol' as DIME working group item Done - Submit 'Diameter User-Name and Realm Based Request Routing = Clarifications' as DIME working group item Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group = item Done - Submit 'Quality of Service Attributes for Diameter' to the = IESG for consideration as a Proposed Standard Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter User-Name and Realm Based Request Routing = Clarifications' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter NAT Control Application' as DIME working = group item Done - Submit 'Diameter Capabilities Update' as DIME working group = item Done - Submit 'Diameter Credit Control Application MIB' to the = IESG for consideration as an Informational RFC Done - Submit 'Diameter Base Protocol MIB' to the IESG for = consideration as an Informational RFC Done - Submit 'Diameter Capabilities Update' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter Extended NAPTR' as DIME working group item Done - Submit 'Realm-Based Redirection In Diameter' as DIME = working group item Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized = Routing' as DIME working group item Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key Transport' as DIME working group item Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME = working group item Done - Submit 'Diameter IKEv2 PSK' as DIME working group item Done - Submit Revision of 'Diameter Base Protocol' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic = Key Transport' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter Priority Attribute Value Pairs' to the = IESG for consideration as a Proposed Standard Done - Submit Revision of 'Diameter Network Access Server = Application - RFC 4005bis' as DIME working group item Done - Submit 'Diameter NAT Control Application' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration = as a Proposed Standard Done - Submit 'Diameter Extended NAPTR' to the IESG for = consideration as a Proposed Standard Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized = Routing' to the IESG for consideration as a Proposed =20 Mar 2012 - Submit 'Realm-Based Redirection In Diameter' to the IESG = for consideration as a Proposed Standard Mar 2012 - Submit Revision of 'Diameter Network Access Server = Application - RFC 4005bis' to the IESG for consideration as a Proposed = Standard May 2012 - Submit 'Diameter Application Design Guidelines' to the IESG = for consideration as a BCP document Standard Jul 2012 - Submit 'Diameter Support for EAP Re-authentication = Protocol' to the IESG for consideration as a Proposed Standard Aug 2012 - Submit a document on 'Protocol extension for bulk and group = signaling' as a working group item Aug 2013 - Submit a document on 'Protocol extension for bulk and group = signaling' to the IESG for consideration as a Proposed Standard From glenzorn@gmail.com Thu Dec 22 02:46:57 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D033421F8B83 for ; Thu, 22 Dec 2011 02:46:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qVHTXwCDSE5B for ; Thu, 22 Dec 2011 02:46:57 -0800 (PST) Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1AC5D21F8B21 for ; Thu, 22 Dec 2011 02:46:57 -0800 (PST) Received: by qadz3 with SMTP id z3so5483361qad.10 for ; Thu, 22 Dec 2011 02:46:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ubrOkmQbtqVEDF68UyCENZsOreq7LRQjNsAkqmdTugM=; b=qEKHOw+hKr41BRNKG+jkxM3H3u7ZWj62mr/IGwsCfLMCjgQoQsdc1G7v4e/DRoy3ag PetlAMdVSRcgbT/Ots4lkl2hdqFIeSrm+GqaZuuqxdXuPoalv+ei1TTBQ8SeCFatQRA4 fZ5/RYk60nH9qbN6lai1sNjeTIHDU9AGZbMpI= Received: by 10.224.96.84 with SMTP id g20mr12701981qan.17.1324550816604; Thu, 22 Dec 2011 02:46:56 -0800 (PST) Received: from [192.168.1.98] (ppp-115-87-123-135.revip4.asianet.co.th. [115.87.123.135]) by mx.google.com with ESMTPS id gg6sm16631464qab.3.2011.12.22.02.46.51 (version=SSLv3 cipher=OTHER); Thu, 22 Dec 2011 02:46:55 -0800 (PST) Message-ID: <4EF30A98.2020402@gmail.com> Date: Thu, 22 Dec 2011 17:46:48 +0700 From: Glen Zorn User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: jouni korhonen References: <064.7acde6a2bdf9a7529b6f9f784b27fa78@trac.tools.ietf.org> <079.f6dc07833210b17115ee3951ef51932a@trac.tools.ietf.org> <93F308DA-4A54-4D57-A2B6-278C06395904@gmail.com> In-Reply-To: <93F308DA-4A54-4D57-A2B6-278C06395904@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: dime@ietf.org Subject: Re: [Dime] [dime] #19: Tunnel-Assignment-Id AVP X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 22 Dec 2011 10:46:57 -0000 On 11/30/2011 5:56 PM, jouni korhonen wrote: > > And the reasoning behind is? OK,I give: how many different reasons could there be? I can only think of one: the text is meant to be descriptive, not prescriptive, that is, no rationale is required for acting differently and Diameter interoperability is not, AFAICT, effected. > > - Jouni > > > On Nov 21, 2011, at 12:41 PM, dime issue tracker wrote: > >> #19: Tunnel-Assignment-Id AVP >> >> >> Comment (by gwz@…): >> >> Yes, it was intentional. >> >> -- >> -----------------------------+--------------------- >> Reporter: jouni.nospam@… | Owner: dime@… >> Type: defect | Status: new >> Priority: major | Milestone: >> Component: rfc4005bis | Version: >> Severity: In WG Last Call | Resolution: >> Keywords: | >> -----------------------------+--------------------- >> >> Ticket URL: >> dime >> >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime > > > From glenzorn@gmail.com Thu Dec 22 21:10:44 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9704021F849C for ; Thu, 22 Dec 2011 21:10:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rdcaelp4tjEc for ; Thu, 22 Dec 2011 21:10:43 -0800 (PST) Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2156C21F8496 for ; Thu, 22 Dec 2011 21:10:43 -0800 (PST) Received: by qcsf15 with SMTP id f15so6621573qcs.31 for ; Thu, 22 Dec 2011 21:10:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=zjheRd19mj0j3wqio+olkc1mVp76DLxY6xXjw4oj2Bc=; b=FoZxK15AkQ/xIfThPipocehCR7DjcVx1iTc5CzPq9MyVDns4X5by6KyWJNbRorieC+ MeW1WlqtZnmVe4w7BSbolfw5ELufrx/cKacBWG2RWfWDhFdRQa8PfYgjylXEgLtLtTdV o7KDmxs9Ckgnt3MjHXXrbCgBM3Eaiv2Es5a6s= Received: by 10.229.75.135 with SMTP id y7mr5428555qcj.40.1324617023538; Thu, 22 Dec 2011 21:10:23 -0800 (PST) Received: from [192.168.1.98] (ppp-115-87-123-135.revip4.asianet.co.th. [115.87.123.135]) by mx.google.com with ESMTPS id h9sm21848487qac.13.2011.12.22.21.10.18 (version=SSLv3 cipher=OTHER); Thu, 22 Dec 2011 21:10:21 -0800 (PST) Message-ID: <4EF40D36.70400@gmail.com> Date: Fri, 23 Dec 2011 12:10:14 +0700 From: Glen Zorn User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: jouni korhonen References: <4FCEC779-A1AD-4A21-97B8-8AD1C99472C4@gmail.com> In-Reply-To: <4FCEC779-A1AD-4A21-97B8-8AD1C99472C4@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: dime@ietf.org Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 23 Dec 2011 05:10:45 -0000 On 12/22/2011 2:15 PM, jouni korhonen wrote: > > Dan, > > On Dec 20, 2011, at 7:51 PM, Romascanu, Dan (Dan) wrote: > >> Yes. >> >> Can you send me a clean and final version, so that I can ask the Secretariat to send it for internal review? >> >> Thanks and Regards, >> >> Dan >> >> >> > > > Here is the latest revision. NOTE. I actually added a milestone for the new bulk & group signaling work we wanted to do: > > o Aug 2012 - Submit a document on 'Protocol extension for bulk and group signaling' as a working group item > o Aug 2013 - Submit a document on 'Protocol extension for bulk and group signaling' to the IESG for consideration as a Proposed Standard > > I wanted to give it two meeting cycles.. > > - JOuni > > > ------------------------------------------------------------------------------------ > > 2011-xx-yy charter > Diameter Maintenance and Extensions (dime) > ------------------------------------------ > > Charter > > Current Status: Active > > Chairs: > Lionel Morand > Jouni Korhonen > > Operations and Management Area Directors: > Dan Romascanu > Ronald Bonica > > Operations and Management Area Advisor: > Dan Romascanu > > Mailing Lists: > General Discussion: dime@ietf.org > To Subscribe: https://www.ietf.org/mailman/listinfo/dime > Archive: http://www.ietf.org/mail-archive/web/dime/current/maillist.html > > > Description of Working Group: > > The Diameter Maintenance and Extensions WG will focus on maintenance > and extensions to the Diameter protocol required to enable its use for > authentication, authorization, accounting, charging in network access, > provisioning of configuration information within the network, and for > new signaling uses within the extensibility rules of the Diameter base > protocol. One more time, AAA & in particular Diameter is NOT a generic signalling protocol, no matter how much other SDOs might want to twist it into such a thing. > > The DIME working group plans to address the following items: > > - Maintaining and/or progressing, along the standards track, the > Diameter Base protocol and Diameter Applications. This includes > extensions to Diameter Base protocol that can be considered as enhanced > features or bug fixes. > > - Diameter application design guideline. This document will provide > guidelines for design of Diameter extensions. It will detail when to > consider reusing an existing application and when to develop a new > application. > > - Protocol extensions for the management of Diameter entities. This work > focuses on the standardization of Management Information Bases (MIBs) > to configure Diameter entities (such as the Diameter Base protocol or > Diameter Credit Control nodes). The usage of other management protocols > for configuring Diameter entities may be future work within the group. > > - Protocol extension for bulk and group signaling. The aim of this > work is to study and standardize a solution for handling groups of > sessions within the Diameter base protocol context. The solution would > define how to identify and handle grouped sessions in commands and > operations. If you insist upon ignoring such important applications as state synchronization between agents, at least please change "signalling" to "session management" since that at least comes within spitting distance of actual AAA while generic "signalling" does not. ... From jouni.nospam@gmail.com Fri Dec 23 00:25:08 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4B1621F8888 for ; Fri, 23 Dec 2011 00:25:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JRR9J0gk16pP for ; Fri, 23 Dec 2011 00:25:07 -0800 (PST) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8609721F8801 for ; Fri, 23 Dec 2011 00:25:07 -0800 (PST) Received: by laah2 with SMTP id h2so3976922laa.31 for ; Fri, 23 Dec 2011 00:25:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Y3h/OCRRlCbP+PXHHhsC4zxdnZU8sXbV871MxG4cZ3s=; b=xrcquEh/PmJp2TOVcsB3WUzYf1iEIW5mbsWxfV5znBt7vSNEddYlEgFBiiZmiVIPsO vACvF6cfK1PWWBa1OqK3OyZEFRDZq9+jXmpGacWc/V6Rn3gkbR32vmW7ZC1aFOzOwmrC +RNCarQ85u2wAorH0VB3PevV9FEFx2VVJ+w/s= Received: by 10.152.111.7 with SMTP id ie7mr11186641lab.11.1324628706488; Fri, 23 Dec 2011 00:25:06 -0800 (PST) Received: from [188.117.15.110] ([188.117.15.110]) by mx.google.com with ESMTPS id st7sm9856986lab.12.2011.12.23.00.25.03 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 23 Dec 2011 00:25:04 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: Jouni In-Reply-To: <4EF40D36.70400@gmail.com> Date: Fri, 23 Dec 2011 10:25:02 +0200 Content-Transfer-Encoding: 7bit Message-Id: <9FB03157-E7EE-4C3C-82E4-E699700BE200@gmail.com> References: <4FCEC779-A1AD-4A21-97B8-8AD1C99472C4@gmail.com> <4EF40D36.70400@gmail.com> To: Glen Zorn X-Mailer: Apple Mail (2.1251.1) Cc: dime@ietf.org Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 23 Dec 2011 08:25:08 -0000 >> - Protocol extension for bulk and group signaling. The aim of this >> work is to study and standardize a solution for handling groups of >> sessions within the Diameter base protocol context. The solution would >> define how to identify and handle grouped sessions in commands and >> operations. > > If you insist upon ignoring such important applications as state > synchronization between agents, at least please change "signalling" to > "session management" since that at least comes within spitting distance > of actual AAA while generic "signalling" does not. > > ... - Protocol extension for bulk and group session management. The aim of this work is to study and standardize a solution for handling groups of sessions within the Diameter base protocol context. The solution would define how to identify and handle grouped sessions in commands and operations. Ok with me. - Jouni From dromasca@avaya.com Fri Dec 23 03:55:15 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF3A021F8B2A for ; Fri, 23 Dec 2011 03:55:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.33 X-Spam-Level: X-Spam-Status: No, score=-103.33 tagged_above=-999 required=5 tests=[AWL=0.269, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d-O7dM1hrHeg for ; Fri, 23 Dec 2011 03:55:15 -0800 (PST) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 4AD8B21F8B1D for ; Fri, 23 Dec 2011 03:55:15 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoAAONr9E7GmAcF/2dsb2JhbAA6CptahCCMPIEFgXIBAQEBAxIeCj8MBAIBCA0EBAEBCwYMCwEGASAlCQgBAQQBEggTB6M+mziIVoJWYwSacYUAh0Y X-IronPort-AV: E=Sophos;i="4.71,398,1320642000"; d="scan'208";a="321071869" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 23 Dec 2011 06:55:00 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 Dec 2011 06:51:42 -0500 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: Fri, 23 Dec 2011 12:54:57 +0100 Message-ID: In-Reply-To: <9FB03157-E7EE-4C3C-82E4-E699700BE200@gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dime] re-chartering Thread-Index: AczBTGJE33FlLAn+Tq6dPCJwNhjemQAHNtKw References: <4FCEC779-A1AD-4A21-97B8-8AD1C99472C4@gmail.com> <4EF40D36.70400@gmail.com> <9FB03157-E7EE-4C3C-82E4-E699700BE200@gmail.com> From: "Romascanu, Dan (Dan)" To: "Jouni" , "Glen Zorn" Cc: dime@ietf.org Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 23 Dec 2011 11:55:15 -0000 Should we also replace signaling by session management in the Description of the Working Group? The Diameter Maintenance and Extensions WG will focus on maintenance and extensions to the Diameter protocol required to enable its use for authentication, authorization, accounting, charging in network access, provisioning of configuration information within the network, and for new session management uses within the extensibility rules of the=20 Diameter base protocol.=20 Dan > -----Original Message----- > From: Jouni [mailto:jouni.nospam@gmail.com] > Sent: Friday, December 23, 2011 10:25 AM > To: Glen Zorn > Cc: Romascanu, Dan (Dan); dime@ietf.org > Subject: Re: [Dime] re-chartering >=20 >=20 >=20 > >> - Protocol extension for bulk and group signaling. The aim of this > >> work is to study and standardize a solution for handling groups of > >> sessions within the Diameter base protocol context. The solution > would > >> define how to identify and handle grouped sessions in commands and > >> operations. > > > > If you insist upon ignoring such important applications as state > > synchronization between agents, at least please change "signalling" > to > > "session management" since that at least comes within spitting > distance > > of actual AAA while generic "signalling" does not. > > > > ... >=20 > - Protocol extension for bulk and group session management. The aim of > this work is to study and standardize a solution for handling groups > of sessions within the Diameter base protocol context. The solution > would define how to identify and handle grouped sessions in commands > and operations. >=20 > Ok with me. >=20 >=20 > - Jouni From glenzorn@gmail.com Sat Dec 24 03:12:01 2011 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 530B921F83EF for ; Sat, 24 Dec 2011 03:12:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cJ-HpSqqwPN5 for ; Sat, 24 Dec 2011 03:12:00 -0800 (PST) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id AE6A821F84B2 for ; Sat, 24 Dec 2011 03:12:00 -0800 (PST) Received: by iaen33 with SMTP id n33so8915192iae.31 for ; Sat, 24 Dec 2011 03:11:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=qzYNXWwZ/0LsU1zlksqeAx3IitD8hxBNDrTSDqYy8Tk=; b=qPKQ6myNAgrqcW/GZ84qlfJtRrt5wjCGK6FRoBSxusccVXpZPTgobkP49pQhVgFDKH vwl/8BUDQNUl4txA6rFOK4pUpfrrRu5HVBKNZtAULe9IKxPrqUimxJFheN1islk8QF+a yI+JZCuE5UQy0wfA58hkQB8LA2pOVnuIESld4= Received: by 10.50.46.196 with SMTP id x4mr18105548igm.15.1324725117880; Sat, 24 Dec 2011 03:11:57 -0800 (PST) Received: from [192.168.1.98] (ppp-124-120-58-214.revip2.asianet.co.th. [124.120.58.214]) by mx.google.com with ESMTPS id z22sm52026752ibg.5.2011.12.24.03.11.50 (version=SSLv3 cipher=OTHER); Sat, 24 Dec 2011 03:11:55 -0800 (PST) Message-ID: <4EF5B372.208@gmail.com> Date: Sat, 24 Dec 2011 18:11:46 +0700 From: Glen Zorn User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" References: <4FCEC779-A1AD-4A21-97B8-8AD1C99472C4@gmail.com> <4EF40D36.70400@gmail.com> <9FB03157-E7EE-4C3C-82E4-E699700BE200@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: dime@ietf.org Subject: Re: [Dime] re-chartering X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 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, 24 Dec 2011 11:12:01 -0000 On 12/23/2011 6:54 PM, Romascanu, Dan (Dan) wrote: > Should we also replace signaling by session management in the > Description of the Working Group? Good idea; it might be good to be more specific that this is _Diameter_ management as well, since "session" means lots of different things to different people, many of those things having nothing to do w/AAA. > > The Diameter Maintenance and Extensions WG will focus on maintenance > and extensions to the Diameter protocol required to enable its use for > authentication, authorization, accounting, charging in network access, > provisioning of configuration information within the network, and for > new session management uses within the extensibility rules of the > Diameter base protocol. > > Dan > > >> -----Original Message----- >> From: Jouni [mailto:jouni.nospam@gmail.com] >> Sent: Friday, December 23, 2011 10:25 AM >> To: Glen Zorn >> Cc: Romascanu, Dan (Dan); dime@ietf.org >> Subject: Re: [Dime] re-chartering >> >> >> >>>> - Protocol extension for bulk and group signaling. The aim of this >>>> work is to study and standardize a solution for handling groups of >>>> sessions within the Diameter base protocol context. The solution >> would >>>> define how to identify and handle grouped sessions in commands and >>>> operations. >>> >>> If you insist upon ignoring such important applications as state >>> synchronization between agents, at least please change "signalling" >> to >>> "session management" since that at least comes within spitting >> distance >>> of actual AAA while generic "signalling" does not. >>> >>> ... >> >> - Protocol extension for bulk and group session management. The aim > of >> this work is to study and standardize a solution for handling > groups >> of sessions within the Diameter base protocol context. The solution >> would define how to identify and handle grouped sessions in > commands >> and operations. >> >> Ok with me. >> >> >> - Jouni