From jouni.nospam@gmail.com Tue Nov 1 03:12:58 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 8EF2921F8F44 for ; Tue, 1 Nov 2011 03:12:58 -0700 (PDT) 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 7aTA7LP8kR05 for ; Tue, 1 Nov 2011 03:12:58 -0700 (PDT) Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id DA39F21F8EFF for ; Tue, 1 Nov 2011 03:12:57 -0700 (PDT) Received: by eyg24 with SMTP id 24so6555270eyg.31 for ; Tue, 01 Nov 2011 03:11:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=Pn5wmqJVeZ7sq+yvYwvQWI5ctAB9vQgIVJT19Ob9TG4=; b=QYNP6RI3pCz3wGSGiMMlenRqUF08XwtTcxvGflQ5U8yD7xMjVFZBDd86XT4tO3x1lw by/fkVzyjHs5ygb+5r/XJh8qwfvAT1kMShO6hye9sv0bNdJzD3+I9E8gN5g7XmKwRb/w 1wXlvxn0DXPdBTdEb4YB/MsJTGJb3v4eGo37w= Received: by 10.14.9.206 with SMTP id 54mr1509059eet.248.1320142309161; Tue, 01 Nov 2011 03:11:49 -0700 (PDT) Received: from dhcp-27-53.ripemtg.ripe.net (dhcp-27-53.ripemtg.ripe.net. [193.0.27.53]) by mx.google.com with ESMTPS id x12sm38159982eef.9.2011.11.01.03.11.34 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Nov 2011 03:11:48 -0700 (PDT) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 1 Nov 2011 12:11:32 +0200 Message-Id: <96952D18-BD5E-4760-BC94-799A45C2F295@gmail.com> To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [Dime] draft agenda posted 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, 01 Nov 2011 10:12:58 -0000 Folks, The draft agenda for the upcoming meeting has been uploaded. Check it = out and feel free to comment. http://www.ietf.org/proceedings/82/agenda/dime.txt - Jouni= From jouni.nospam@gmail.com Tue Nov 1 03:19: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 7BDFA21F8D6C for ; Tue, 1 Nov 2011 03:19:57 -0700 (PDT) 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 Wtyx46E6PbgH for ; Tue, 1 Nov 2011 03:19:57 -0700 (PDT) Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 600FD21F8AFD for ; Tue, 1 Nov 2011 03:19:25 -0700 (PDT) Received: by eyg24 with SMTP id 24so6558754eyg.31 for ; Tue, 01 Nov 2011 03:18:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=p4OHd7WYgwNuu+DDLmtAoaV+Fu5lOOzzvtAZPleBHJY=; b=bregfIXecArFYBq6iomBowG3cInnESQlU2VozoGqhG0Krwz+TjJflhwI9pFxycrsd8 nuPDMipLMoaZi5yY1g7cFCYF4B5yE2cFY3iB33Q+aWSqkDKLL7SGaIzILy/1yK8j2Way T4Y9WMNPYnCBYsEYvKp25Vudx5CG96cofxBGk= Received: by 10.14.4.65 with SMTP id 41mr1400312eei.194.1320142683129; Tue, 01 Nov 2011 03:18:03 -0700 (PDT) Received: from dhcp-27-53.ripemtg.ripe.net (dhcp-27-53.ripemtg.ripe.net. [193.0.27.53]) by mx.google.com with ESMTPS id o4sm58978483eeb.0.2011.11.01.03.17.57 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Nov 2011 03:18:02 -0700 (PDT) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 1 Nov 2011 12:17:54 +0200 Message-Id: <100C75C6-7714-4A2B-8F06-EA70D5121FCA@gmail.com> To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [Dime] note taker(s) and a jabber scribe 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, 01 Nov 2011 10:19:57 -0000 Folks, Feel free to volunteer as a note taker or a jabber scribe for the = upcoming Dime meeting in Taipei. Drop a mail to chairs if you feel it is = your responsibility to the community ;) - Jouni & Lionel= From jouni.nospam@gmail.com Mon Nov 7 16:00:27 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 E14151F0C4C for ; Mon, 7 Nov 2011 16:00:27 -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 wfmUZPrc83-e for ; Mon, 7 Nov 2011 16:00:27 -0800 (PST) Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0B9211F0C44 for ; Mon, 7 Nov 2011 16:00:26 -0800 (PST) Received: by bkbzv15 with SMTP id zv15so4707843bkb.31 for ; Mon, 07 Nov 2011 16:00:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; bh=Q5c9nrJtwl0RNRLXiKJEy2EsrfT5u8ub/R6TOnqydMc=; b=OcFzEYQkwEhio9BlTTIdgMzmTnTskiKFO+tBxfpd0zspAuiFFiyK9yIWXUXh1U0yPK DqxvL+1p1/cgxGUDldfQeqVRXMSt48uAhQiqmWvD6mh8PuHcKquQDz+mC7TFIftlxptN ZEdiEPsjhSrGRgqjNLd1B5NzshOa60ZGLNhWI= Received: by 10.204.132.211 with SMTP id c19mr20874573bkt.94.1320710424835; Mon, 07 Nov 2011 16:00:24 -0800 (PST) Received: from a83-245-211-74.elisa-laajakaista.fi (a83-245-211-74.elisa-laajakaista.fi. [83.245.211.74]) by mx.google.com with ESMTPS id x14sm19034487bkf.10.2011.11.07.16.00.20 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 07 Nov 2011 16:00:21 -0800 (PST) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 8 Nov 2011 02:00:18 +0200 Message-Id: To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Cc: dime-chairs@tools.ietf.org Subject: [Dime] About rechartering 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, 08 Nov 2011 00:00:28 -0000 Folks, In last IETF we had discussion about adding new work to our charter and = widening the scope a bit. One particular item was the bulk/group = signaling. We are going to have a discussion in this specific topic and = rechartering during the Dime WG meeting next week. For a basis for the = discussion I have included a new charter proposal *draft*. Feel free to = comment it (and we will anyway continue in Taipei the discussion.) There = is no milestones included yet.. as we better first discuss the charter = content and the newly added proposal for work. While we are doing tweaks = to the charter it is a good place to do some cleanup as well. Any comments on the first stab for the new charter? Note that all = milestone are still missing as they will come once other stuff has been = discussed. However, I currently think (a subject to change) one or max = two documents are needed to fulfill the bulk/group handling of sessions.=20= - Jouni & Lionel ------------------------------------------------------------------------ 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 and provisioning in network access as well as for other applications environments (e.g., IP telephony, mobility). The DIME working group plains 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 works 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, AAA 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 used to ensure this. From wwwrun@rfc-editor.org Sat Nov 12 22:16:06 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 7291511E80A3; Sat, 12 Nov 2011 22:16:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.243 X-Spam-Level: X-Spam-Status: No, score=-102.243 tagged_above=-999 required=5 tests=[AWL=-0.243, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, 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 iEZrBb8cfLPx; Sat, 12 Nov 2011 22:16:06 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 142C811E8080; Sat, 12 Nov 2011 22:16:06 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id DD1E362179; Sat, 12 Nov 2011 22:11:03 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20111113061103.DD1E362179@rfc-editor.org> Date: Sat, 12 Nov 2011 22:11:03 -0800 (PST) Cc: dime@ietf.org, rfc-editor@rfc-editor.org Subject: [Dime] RFC 6408 on Diameter Straightforward-Naming Authority Pointer (S-NAPTR) Usage 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: Sun, 13 Nov 2011 06:16:06 -0000 A new Request for Comments is now available in online RFC libraries. RFC 6408 Title: Diameter Straightforward-Naming Authority Pointer (S-NAPTR) Usage Author: M. Jones, J. Korhonen, L. Morand Status: Standards Track Stream: IETF Date: November 2011 Mailbox: mark@azu.ca, jouni.nospam@gmail.com, lionel.morand@orange-ftgroup.com Pages: 14 Characters: 32490 Updates: RFC3588 I-D Tag: draft-ietf-dime-extended-naptr-09.txt URL: http://www.rfc-editor.org/rfc/rfc6408.txt The Diameter base protocol specifies mechanisms whereby a given realm may advertise Diameter nodes and the supported transport protocol. However, these mechanisms do not reveal the Diameter applications that each node supports. A peer outside the realm would have to perform a Diameter capability exchange with every node until it discovers one that supports the required application. This document updates RFC 3588, "Diameter Base Protocol", and describes an improvement using an extended format for the Straightforward-Naming Authority Pointer (S-NAPTR) application service tag that allows for discovery of the supported applications without doing Diameter capability exchange beforehand. [STANDARDS-TRACK] This document is a product of the Diameter Maintanence and Extensions Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From jouni.nospam@gmail.com Sun Nov 13 16:04:37 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 8A24511E8081 for ; Sun, 13 Nov 2011 16:04:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.738 X-Spam-Level: X-Spam-Status: No, score=-0.738 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_RECV_IP_061228=0.895, SARE_RECV_SPAM_DOMN0b=1.666] 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 b-IXCOBVVf3A for ; Sun, 13 Nov 2011 16:04:37 -0800 (PST) Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id F351D11E8073 for ; Sun, 13 Nov 2011 16:04:36 -0800 (PST) Received: by ywt34 with SMTP id 34so4132405ywt.31 for ; Sun, 13 Nov 2011 16:04:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:references :to:message-id:mime-version:x-mailer; bh=lMkID8RA9ELzADHaR8v8rHqc5N8f5IfDQeifG9bmH08=; b=YzRHe8+jF3S8FFYigFQouJXnyhAqEuDIPOx01LGmJtYBSRluJqV9WgxSg6Xw9V0KX7 xn8NmBrstPeg+E9hbByTgCal354p23xZ4V3M086zbZeYtvGaR6ItaiUwjLcfFA/1345E 6VLuv4Qg43m3Jt/FZq7mTJcyAufRApV/3mRW4= Received: by 10.68.12.105 with SMTP id x9mr45460977pbb.109.1321229075611; Sun, 13 Nov 2011 16:04:35 -0800 (PST) Received: from [192.168.0.15] (61-230-53-171.dynamic.hinet.net. [61.230.53.171]) by mx.google.com with ESMTPS id b8sm51814891pba.16.2011.11.13.16.04.33 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 16:04:34 -0800 (PST) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 14 Nov 2011 02:04:29 +0200 References: <20111113061103.DD1E362179@rfc-editor.org> To: dime@ietf.org Message-Id: <89E2C64F-F827-474D-9149-5E79BABBD037@gmail.com> Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [Dime] Fwd: RFC 6408 on Diameter Straightforward-Naming Authority Pointer (S-NAPTR) Usage 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, 14 Nov 2011 00:04:37 -0000 One of our I-Ds finally reached completion. Thanks to everyone for the = hard work. - Jouni Begin forwarded message: > From: rfc-editor@rfc-editor.org > Date: November 13, 2011 8:11:03 AM GMT+02:00 > To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org > Cc: dime@ietf.org, rfc-editor@rfc-editor.org > Subject: RFC 6408 on Diameter Straightforward-Naming Authority Pointer = (S-NAPTR) Usage >=20 >=20 > A new Request for Comments is now available in online RFC libraries. >=20 >=20 > RFC 6408 >=20 > Title: Diameter Straightforward-Naming Authority Pointer=20= > (S-NAPTR) Usage=20 > Author: M. Jones, J. Korhonen, > L. Morand > Status: Standards Track > Stream: IETF > Date: November 2011 > Mailbox: mark@azu.ca,=20 > jouni.nospam@gmail.com,=20 > lionel.morand@orange-ftgroup.com > Pages: 14 > Characters: 32490 > Updates: RFC3588 >=20 > I-D Tag: draft-ietf-dime-extended-naptr-09.txt >=20 > URL: http://www.rfc-editor.org/rfc/rfc6408.txt >=20 > The Diameter base protocol specifies mechanisms whereby a given realm > may advertise Diameter nodes and the supported transport protocol. > However, these mechanisms do not reveal the Diameter applications > that each node supports. A peer outside the realm would have to > perform a Diameter capability exchange with every node until it > discovers one that supports the required application. This document > updates RFC 3588, "Diameter Base Protocol", and describes an > improvement using an extended format for the Straightforward-Naming > Authority Pointer (S-NAPTR) application service tag that allows for > discovery of the supported applications without doing Diameter > capability exchange beforehand. [STANDARDS-TRACK] >=20 > This document is a product of the Diameter Maintanence and Extensions = Working Group of the IETF. >=20 > This is now a Proposed Standard Protocol. >=20 > STANDARDS TRACK: This document specifies an Internet standards track > protocol for the Internet community,and requests discussion and = suggestions > for improvements. Please refer to the current edition of the Internet > Official Protocol Standards (STD 1) for the standardization state and > status of this protocol. Distribution of this memo is unlimited. >=20 > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist >=20 > For searching the RFC series, see = http://www.rfc-editor.org/rfcsearch.html. > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. >=20 > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. = Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. >=20 >=20 > The RFC Editor Team > Association Management Solutions, LLC >=20 >=20 > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce From internet-drafts@ietf.org Sun Nov 13 17:25:52 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 2788E11E80D4; Sun, 13 Nov 2011 17:25:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.514 X-Spam-Level: X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, 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 4w8UOiEQZc7k; Sun, 13 Nov 2011 17:25:51 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A754811E80CE; Sun, 13 Nov 2011 17:25:51 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.63 Message-ID: <20111114012551.6134.18975.idtracker@ietfa.amsl.com> Date: Sun, 13 Nov 2011 17:25:51 -0800 Cc: dime@ietf.org Subject: [Dime] I-D Action: draft-ietf-dime-ikev2-psk-diameter-11.txt 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, 14 Nov 2011 01:25:52 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Diameter Maintenance and Extensions W= orking Group of the IETF. Title : Diameter IKEv2 SK: Shared Key-based Support for IKEv2 Se= rver to Diameter Server Interaction Author(s) : Violeta Cakulev Avi Lior Semyon Mizikovsky Filename : draft-ietf-dime-ikev2-psk-diameter-11.txt Pages : 22 Date : 2011-11-13 The Internet Key Exchange protocol version 2 (IKEv2) is a component of the IPsec architecture and is used to perform mutual authentication as well as to establish and to maintain IPsec security associations (SAs) between the respective parties. IKEv2 supports several different authentication mechanisms, such as the Extensible Authentication Protocol (EAP), certificates, and shared key. Diameter interworking for Mobile IPv6 between the Home Agent, as a Diameter client, and the Diameter server has been specified. However, that specification focused on the usage of EAP and did not include support for shared key based authentication available with IKEv2. This document specifies the IKEv2 Server to the Diameter server communication when the IKEv2 Peer authenticates using the Internet Key Exchange v2 with Shared Key. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-ikev2-psk-diameter-11.t= xt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-dime-ikev2-psk-diameter-11.txt From jouni.nospam@gmail.com Sat Nov 19 22:45:53 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 E526321F84A1 for ; Sat, 19 Nov 2011 22:45:53 -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 bWSO1QfuA3sC for ; Sat, 19 Nov 2011 22:45:53 -0800 (PST) Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id D897021F8467 for ; Sat, 19 Nov 2011 22:45:45 -0800 (PST) Received: by bkbzv15 with SMTP id zv15so5972256bkb.31 for ; Sat, 19 Nov 2011 22:45:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=KhCaPLkBP5TqY+01cSRUUfgnJGtCJdQRu50C1RzfUhA=; b=n3BFwCkwZM7dAuUujMki80hlhxCCTjj2AYZkpmiQuTtl73m17s3Z2QLQSD4QrzW2nd pWQ6VFltTNiaMDDCbRFkC3cKRKiI/iZrL47C55pV/QX5ul3ZKj8DLq9viiDuaKdqwfHQ 70Gknjm2ZhE697Af3AXD1BbnKO4zEn8Zx2YNk= Received: by 10.204.16.67 with SMTP id n3mr10009898bka.6.1321771544898; Sat, 19 Nov 2011 22:45:44 -0800 (PST) Received: from a83-245-212-188.elisa-laajakaista.fi (a83-245-212-188.elisa-laajakaista.fi. [83.245.212.188]) by mx.google.com with ESMTPS id dq2sm4367798bkb.11.2011.11.19.22.45.43 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 19 Nov 2011 22:45:43 -0800 (PST) From: jouni korhonen Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Sun, 20 Nov 2011 08:43:41 +0200 Message-Id: To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [Dime] Draft Dime notes from IETF#82 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: Sun, 20 Nov 2011 06:45:54 -0000 Folks, Check the draft notes from the meeting. If you have something to = add/remove/modify let me know in TWO weeks. Big thanks to Jean for = taking them. - Jouni = --------------------------------------------------------------------------= ------------------------------------ * Draft notes * Diameter Maintenance and Extensions =3D=3D Logistics = =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=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D THURSDAY, November 17, 2011 1740-1940 Afternoon Session III (note, session moved) Chairs: Jouni Korhonen (jouni.nospam@gmail.com) Lionel Morand (lionel.morand@orange-ftgroup.com) Room: 2103 Conflicts: lisp, samrg, multrans (bof), vipr, sdn (bof), tls, decade =3D=3D Administrative = =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=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Agenda Bashing (chairs, = 10min) o Bluesheets o Jabber: tbd o Note taker #1: Jean Mahoney o Note taker #2: tbd Lionel is at the 3GPP meeting. Moving rechartering discussion to earlier in the meeting. Dan (AD) has a = colliding BoF to attend to a late scheduling of WG meetings. Rechartering: The other bullets based on what the WG has done (see the last page in = agenda slideset).=20 Last bullet is new.=20 Dan - IESG hasn't seen the charter proposal. Comment from IESG - the = docs walk the border of the scope of the WG. Maybe this is needed. = Prefer an open discussion with the IESG to show there is demand from the = industry and support from the WG. (the comment refers using Diameter for = other purposes than pure AAA, such as, NAT control and generic = configuration management) What are the use cases for the bulk signaling. How does this enter into = the scope (first paragraph)? Marco Liebsch - Need to write up how the bulk signaling help to reduce = signaling overhead.=20 Dan - So you are saying this can be described as an optimization of the = protocol? Mark Jones - says yes.=20 Glen Zorn - Signaling is not AAA. Change the word signaling to session = control, which is part of AAA. 3588 and 3588bis says that diameter can = be used for things other than AAA.=20 Mark - Good point on the signaling term.=20 Dan - Even if 3588 talks about other applications, this working group is = chartered on incremental extensions are scoped to AAA. Marco - I don't think it conflicts with the motivation for the charter. = Group signaling doesn't deviate from AAA context.=20 Dan - we have two options:=20 - keep the current framework - easier to recharter, but will face the = same kind of discusses from IESG members.=20 - Or rewrite the first paragraph - it's your decision.=20 Jouni - need to work on option 2 text. If we can't come up with text, = fall back to option 1. Glen - prefer option 2 to enlarge scope of dime to encompass = synchronization state between proxies. This current change wouldn't do = that.=20 Jouni - post what you want to see as text as the charter.=20 ACTION =3D=3D> To folks who want something to happen, they should = propose text for new charter within a few weeks.=20 WG Status Update (chairs, = 15min) Documents in WG process: o draft-ietf-dime-erp-07 Going for WGLC o draft-ietf-dime-pmip6-lr-06 Completed WGLC. Going to move = forward o draft-ietf-dime-rfc4005bis-05 TRAC issues not addressed. IESG Processing: o draft-ietf-dime-diameter-base-protocol-mib-06 o draft-ietf-dime-diameter-cc-appl-mib-03 o draft-ietf-dime-ikev2-psk-diameter-10 o draft-ietf-dime-nat-control-12 o draft-ietf-dime-priority-avps-05 o draft-ietf-dime-rfc3588bis-29 RFC-Editor's Queue: o draft-ietf-dime- -07 o draft-ietf-dime-extended-naptr-09 Now out as RFC 6408 o draft-ietf-dime-local-keytran-14 Missing in Action: o draft-ietf-dime-app-design-guide Expired -> withdraw the = I-D? o draft-ietf-dime-realm-based-redirect Expired -> withdraw the = I-D? Jouni - anyone have an opinion on keeping app-design-guide? Victor has = moved on. It needs to be rewritten in many places, needs new info added.=20= No opinions expressed. Should the document keep realm-based-redirect? There's an IPR issue. Glen - is it useful? Jouni - I don't have a use case for this.=20 Glen - I don't know how much work is required. I recall that it went to = WGLC.=20 Jouni - the authors haven't responded. 4 major defects in tracker. = Anyone against removing it? Glen - these have been abandoned by the authors? Jouni nods. Glen - I don't have an issue with getting rid of the documents, but you = can assign new authors. Jouni - anyone interested in taken them on? silence. Glen - Design guides are useless. Is the other one useful? =3D=3D> DECISION: Jouni will submit question to the list. =20 =3D=3D Working group draft presentations = =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 WG Draft Status updates since last IETF#81 o draft-ietf-dime-ikev2-psk-diameter (Violeta, = 15min) The open issues and DISCUSSes have been resolved. Presented changes made since the last meeting.=20 Jouni - is something referencing this? Violeta - 3GPP2 documents reference it. Jouni - thanks for the hard work. =3D=3D Individual drafts presentations = =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 Other discussion topics = =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=3D=3D=3D=3D= =3D o Diameter Bulk Signaling (Marco/Mark, = 30min) Mark presenting 3GPP hasn't proposed mechanisms for group signaling, would like to get = in front of it.=20 Doesn't specify new applications. I'm not proposing NASREQ or DCCA. Jouni - how big are the changes to the state machines? Mark - The mods are not as radical as I thought they were be. They are = in the draft. Marco - We had an individual draft with a generic model, but no = discussion on deployment considerations. I think it's the right approach = to assess whether it's sufficient or a more generic approach is needed. o draft-ietf-dime-3588bis (Glen, = >15min) * next steps to resolve the DISCUSSes Jouni presented the IESG comments, highlighting Saint-Andre's feedback, = which has been resolved (during the IETF meeting in a f2f discussions). Glen discussed Stephen Farrell's feedback. Security is the elephant in = the room. Glen thinks that it needs to be MUST to run diameter over = IPSEC or TLS. Don't care if we embarrass operators. The SDOs don't = specify security.=20 Stefan Winter - we should write that security is a MUST. Glen - another way to clear the discuss - leave it as-is and then detail = the security problems with doing anything else, like network domain = security. Would make the SDOs less happy.=20 ACTION: Jouni will respond via email. Simon Mizikovsky - even if we implement Farrell's feedback, it doesn't = provide security if the operator doesn't do it. Doesn't solve anything. Stefan - we can be very clear that if the operators don't do it, they = open themselves to risk. Simon - makes the box more expensive. SDO says, "If not secured by other = means, then=82 .." Stefan - we need to specify the security.=20 =3D=3D AOB = =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=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 total = >85min =20 =3D=3D> ACTION: Please comment on the charter.=20 From glenzorn@gmail.com Sun Nov 20 01:52: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 AE29321F88B7 for ; Sun, 20 Nov 2011 01:52: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 eR1av92ygUEo for ; Sun, 20 Nov 2011 01:52:35 -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 388D921F84FA for ; Sun, 20 Nov 2011 01:52:35 -0800 (PST) Received: by iaeo4 with SMTP id o4so7170006iae.31 for ; Sun, 20 Nov 2011 01:52:33 -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:subject :content-type:content-transfer-encoding; bh=sOeBYEsTpbS9iBLT4retvwzRooD1W+Id1mMjPP2/E8Q=; b=Kyhr8CDqw0engpdt5SWsq0nFGNhZJreNtaStVQzZrhKTRXhA5uDwIxSiA0tsGvv3nC lwCzBY/Zk7SUkdxg43bQeCXkNCTiJCIsxd0zj1t6Yssq4U2vh+R32AWz1RrlZK00w9Mk PRIixJjgvNrhq5nCxm6nwtstFjKFV6hAhhmMo= Received: by 10.43.53.1 with SMTP id vo1mr9987287icb.2.1321782753728; Sun, 20 Nov 2011 01:52:33 -0800 (PST) Received: from [192.168.1.98] (ppp-58-11-251-173.revip2.asianet.co.th. [58.11.251.173]) by mx.google.com with ESMTPS id z10sm29663861ibv.9.2011.11.20.01.52.30 (version=SSLv3 cipher=OTHER); Sun, 20 Nov 2011 01:52:32 -0800 (PST) Message-ID: <4EC8CDDC.109@gmail.com> Date: Sun, 20 Nov 2011 17:52:28 +0800 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: dime-chairs@tools.ietf.org, "dime@ietf.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Dime] draft-ietf-dime-pmip6-lr 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: Sun, 20 Nov 2011 09:52:35 -0000 The last communication regarding this draft from either of the Chairs was more than 2 months ago, announcing a "short one week WGLC" (http://www.ietf.org/mail-archive/web/dime/current/msg04865.html). I may be wrong, but I believe that a week past some time ago. Did the draft pass WGLC? If so, it at all likely that a request for publication will be forthcoming (perhaps even this year)? From Tina.Tsou.Zouting@huawei.com Sat Nov 19 23:14:54 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 3F60421F85BB for ; Sat, 19 Nov 2011 23:14:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.766 X-Spam-Level: X-Spam-Status: No, score=-4.766 tagged_above=-999 required=5 tests=[AWL=-0.768, BAYES_50=0.001, 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 Y3Go-KLY4tqX for ; Sat, 19 Nov 2011 23:14:53 -0800 (PST) Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 4F76B21F8532 for ; Sat, 19 Nov 2011 23:14:53 -0800 (PST) Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUY00KT76SKWM@szxga05-in.huawei.com> for dime@ietf.org; Sun, 20 Nov 2011 15:14:45 +0800 (CST) Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUY00IWG6SK9V@szxga05-in.huawei.com> for dime@ietf.org; Sun, 20 Nov 2011 15:14:44 +0800 (CST) Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AFC29161; Sun, 20 Nov 2011 15:14:43 +0800 Received: from SZXEML422-HUB.china.huawei.com (10.82.67.161) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sun, 20 Nov 2011 15:14:30 +0800 Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.40]) by szxeml422-hub.china.huawei.com ([10.82.67.161]) with mapi id 14.01.0323.003; Sun, 20 Nov 2011 15:14:37 +0800 Date: Sun, 20 Nov 2011 07:14:37 +0000 From: Tina TSOU In-reply-to: To: jouni korhonen Message-id: <71CDCEF1-4A47-4FA0-8B4F-CB45CCDD3088@huawei.com> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_8PVYojtAwlUbu/fAJKusWg)" Content-language: en-US Accept-Language: en-US, zh-CN Thread-topic: [Dime] Draft Dime notes from IETF#82 Thread-index: AQHMp1ATLhMHZ1aT7U6Q9yZmtGGOGJW1WX/O X-MS-Has-Attach: X-MS-TNEF-Correlator: X-CFilter-Loop: Reflected References: X-Mailman-Approved-At: Sun, 20 Nov 2011 04:03:55 -0800 Cc: "dime@ietf.org" Subject: Re: [Dime] Draft Dime notes from IETF#82 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: Sun, 20 Nov 2011 07:14:54 -0000 --Boundary_(ID_8PVYojtAwlUbu/fAJKusWg) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Tom and I will update draft-ietf-dime-realm-based-redirect before Paris. Tom was not 100% healthy. He is recovering now. Sent from my iPad On Nov 20, 2011, at 2:46 PM, "jouni korhonen" > wrote: draft-ietf-dime-realm-based-redirect --Boundary_(ID_8PVYojtAwlUbu/fAJKusWg) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT
Tom and I will update draft-ietf-dime-realm-based-redirect before Paris.
Tom was not 100% healthy. He is recovering now.

Sent from my iPad

On Nov 20, 2011, at 2:46 PM, "jouni korhonen" <jouni.nospam@gmail.com> wrote:

draft-ietf-dime-realm-based-redirect
--Boundary_(ID_8PVYojtAwlUbu/fAJKusWg)-- From jouni.nospam@gmail.com Mon Nov 21 00:22:37 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 3FCD221F8AB0 for ; Mon, 21 Nov 2011 00:22:37 -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 pr5+O3uEs-XU for ; Mon, 21 Nov 2011 00:22:36 -0800 (PST) Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2A7EA21F8532 for ; Mon, 21 Nov 2011 00:22:35 -0800 (PST) Received: by bkbzv15 with SMTP id zv15so7158726bkb.31 for ; Mon, 21 Nov 2011 00:22:35 -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=KhdSHvDQOSWwc6dXWiin0V4MB2Jgroc0mCSmB/9ElJ0=; b=bAYEBocCStZF/Lov8uIWAj37XQb72o1S7E9tYQBxBbL2dSqYW//4w7WlSe6W082pt6 29/QHEQm1SQoY8eai45L4z0mAbgEGBHtU440GRlyi1L9jfAoXM4UaCl9FwxV0IZxEz8m fTQxxBinf1K8/WREhBDV2zRSnu3Jeh2iI7wg0= Received: by 10.204.147.75 with SMTP id k11mr13377408bkv.102.1321863754117; Mon, 21 Nov 2011 00:22:34 -0800 (PST) Received: from a83-245-212-188.elisa-laajakaista.fi (a83-245-212-188.elisa-laajakaista.fi. [83.245.212.188]) by mx.google.com with ESMTPS id f14sm6623597bkv.3.2011.11.21.00.22.31 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Nov 2011 00:22:32 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: <4EC8CDDC.109@gmail.com> Date: Mon, 21 Nov 2011 10:22:30 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4EC8CDDC.109@gmail.com> To: Glen Zorn X-Mailer: Apple Mail (2.1084) Cc: "dime@ietf.org" , dime-chairs@tools.ietf.org Subject: Re: [Dime] draft-ietf-dime-pmip6-lr 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, 21 Nov 2011 08:22:37 -0000 Glen, Maybe you missed the agenda and status presentation in IETF82? There is = says: "Completed WGLC. Going to move forward".. i.e. next step is proto = write-up. - Jouni On Nov 20, 2011, at 11:52 AM, Glen Zorn wrote: > The last communication regarding this draft from either of the Chairs > was more than 2 months ago, announcing a "short one week WGLC" > (http://www.ietf.org/mail-archive/web/dime/current/msg04865.html). I > may be wrong, but I believe that a week past some time ago. Did the > draft pass WGLC? If so, it at all likely that a request for = publication > will be forthcoming (perhaps even this year)? > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Mon Nov 21 00:30:48 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 A374421F8B1D for ; Mon, 21 Nov 2011 00:30:48 -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 xJVD3rlSRfWh for ; Mon, 21 Nov 2011 00:30:48 -0800 (PST) Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id DD14021F8B11 for ; Mon, 21 Nov 2011 00:30:47 -0800 (PST) Received: by bkbzv15 with SMTP id zv15so7168348bkb.31 for ; Mon, 21 Nov 2011 00:30:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=Ik9ZatwVAHZLo7OUDYkd5UU9cNfpzGJggPNLTF39uaw=; b=Kt/+Jh8taxjoVjuhQOlx2H/lJzW6tuQUf0gdBA/asf6+/+iwuws1Fp5AF5c9VeWuPp yO7Mt2dWgrAR96Q2vPNGTSLVJDw7PZwSFmfRT/nUKvkg3nUOWWegQfroTEB+IfTtwrIR 7u4/qEzMBaRBADkvfeKzZbqH98chqjBgLK5CM= Received: by 10.204.132.78 with SMTP id a14mr10053630bkt.15.1321864246901; Mon, 21 Nov 2011 00:30:46 -0800 (PST) Received: from a83-245-212-188.elisa-laajakaista.fi (a83-245-212-188.elisa-laajakaista.fi. [83.245.212.188]) by mx.google.com with ESMTPS id f14sm6642810bkv.3.2011.11.21.00.30.45 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Nov 2011 00:30:46 -0800 (PST) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 21 Nov 2011 10:30:44 +0200 Message-Id: <1F0F8105-A42C-4F63-846E-9BE3B453EE09@gmail.com> To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [Dime] RFC3588bis and SRVs 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, 21 Nov 2011 08:30:48 -0000 Folks, This relates to a DISCUSS by Peter: = https://datatracker.ietf.org/doc/draft-ietf-dime-rfc3588bis/ballot/#peter-= saint-andre We discussed the possible solution during the week and here's one = solution that should be acceptable. The key point is to differentiate = between secured and unsecured connections with 's' i.e. "diameter" for = plaintext and "diameters" for secured transport connections. Diameter base protocol RFC3588 has reserved and used "_stcp" since its = publication 2003. In that sense the claim "in practice '_sctp' is not = used in existing SRV records" is not quite true. Whether it has been = deployed is a different thing but the code base is there. For the = backward compatibility we need to keep the old "_sctp". Therefore, I = think we cannot switch from "_sctp" to "_udp" just like that. So, keeping in mind that RFC3588 has since 2003 used = '_diameter._sctp'.realm for SRVs, have the following text in Section = 5.2: 3. If no NAPTR records are found, the requester directly queries = for one of the following SRV records: for Diameter over TCP, use "_diameter._tcp.realm"; for Diameter over TLS, use "_diameters._tcp.realm"; for Diameter over SCTP, use "_diameter._sctp.realm"; for Diameter over DTLS, use "_diameters._sctp.realm". If SRV records are found then the=20 requester can perform address record query (A RR's and/or AAAA RR's) for the target hostname specified in the SRV records. If no SRV records are found, the requester gives up. - Jouni From jouni.nospam@gmail.com Mon Nov 21 00:38: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 8FD8921F8B37 for ; Mon, 21 Nov 2011 00:38:29 -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 aCe-8-muj7qs for ; Mon, 21 Nov 2011 00:38:29 -0800 (PST) Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id D22B221F8B36 for ; Mon, 21 Nov 2011 00:38:28 -0800 (PST) Received: by bkbzv15 with SMTP id zv15so7176391bkb.31 for ; Mon, 21 Nov 2011 00:38:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=XEedrW2+pD0tDxRIfcAtRuIfPXUZHm8Iun89f5du+Iw=; b=uAgPWoPWEmaR+HLl6AO7Xnv2sPN5+5qlnjwjfgKBUC9m4PFwPLPK24Mll1ZMFutOc9 HknlaVGeNM9hVkvJGpZ88FKPv3fuAtp7ybNKWh8jmXR2LPHPGVrVr6+IS2+RYxmCp9l7 rIjvmPeogrkl60xKzXZx19A+x+478U7zavExM= Received: by 10.204.132.78 with SMTP id a14mr10080629bkt.15.1321864707881; Mon, 21 Nov 2011 00:38:27 -0800 (PST) Received: from a83-245-212-188.elisa-laajakaista.fi (a83-245-212-188.elisa-laajakaista.fi. [83.245.212.188]) by mx.google.com with ESMTPS id o7sm6621139bkw.16.2011.11.21.00.38.26 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Nov 2011 00:38:27 -0800 (PST) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 21 Nov 2011 10:38:25 +0200 Message-Id: <9A2E9984-EA8E-41D7-9834-916F73DCF432@gmail.com> To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [Dime] On RFC3588bis security.. Stephen Farrell's DISCUSS 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, 21 Nov 2011 08:38:29 -0000 Folks, During the meeting we had a discussion on Stephen Farrell's discuss: = https://datatracker.ietf.org/doc/draft-ietf-dime-rfc3588bis/ballot/#stephe= n-farrell Glen had a solution proposal that we follow what Stephen suggested i.e. = mandate use of either IPsec or (D)TLS within the spec and leave out the = "some security mechanism". This of course has some impact on product & = deployment level as from now on either IPsec or (D)TLS must be used.. Any feedback? - Jouni= From jouni.nospam@gmail.com Mon Nov 21 00:43:16 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 539A221F8B3B for ; Mon, 21 Nov 2011 00:43:16 -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 0zX3g-Um+j7p for ; Mon, 21 Nov 2011 00:43:15 -0800 (PST) Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6725821F8B38 for ; Mon, 21 Nov 2011 00:43:15 -0800 (PST) Received: by bkbzv15 with SMTP id zv15so7181966bkb.31 for ; Mon, 21 Nov 2011 00:43:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; bh=49RmOdCSzw3VqyA+e0/Jt9oNhcST1GAb31G7O940JIc=; b=LyBrajx4Gp4FXr4sTvpxsVsuuOKYp75aIfLwpcGEN22HJa5gZ8b2Hu0mZMOSNxwJUo klsQsEza6EQacDdZccu7K9l768qdbz+W+91u0hpTbGIaQ8ZCjOMRgRgmhcoeBRoDk2d4 j80ytBjoWW/1+KHBkT2FgYmxi5OeEvFNQja9k= Received: by 10.204.146.84 with SMTP id g20mr7170979bkv.44.1321864994491; Mon, 21 Nov 2011 00:43:14 -0800 (PST) Received: from a83-245-212-188.elisa-laajakaista.fi (a83-245-212-188.elisa-laajakaista.fi. [83.245.212.188]) by mx.google.com with ESMTPS id jf4sm1062649bkc.5.2011.11.21.00.43.12 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Nov 2011 00:43:13 -0800 (PST) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 21 Nov 2011 10:43:11 +0200 Message-Id: <1ECBE0F0-5658-4DAD-B7EC-B06DFAF02E9F@gmail.com> To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [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, 21 Nov 2011 08:43:16 -0000 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.=20 Voice your opinion *against* the withdrawn by 2nd Dec. Silence will be = counted as 'yes' for withdrawn. - Jouni= From jouni.nospam@gmail.com Mon Nov 21 00:47:33 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 1827721F8B5B for ; Mon, 21 Nov 2011 00:47:33 -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 9+GySYScn69f for ; Mon, 21 Nov 2011 00:47:32 -0800 (PST) Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB3121F8B5A for ; Mon, 21 Nov 2011 00:47:32 -0800 (PST) Received: by bkbzv15 with SMTP id zv15so7186517bkb.31 for ; Mon, 21 Nov 2011 00:47:31 -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=Lvzl+gGauIjhXb3J8qblUPtcsFwo1ERV25QXKQTEZro=; b=Hi5GSVM5FqTplHop6wNnWBkurXXK96xeueRL84Zg2UJ//oforFK+VvFTiSQn5KiIWF aTj/TsVTuFrVgmMR1FWXauPCnRs+ykyaYfANwIQO/P3ewhdMqX5iUHL6x9VQ7nt76s8V 8z3oUibWnX/54BZvrsBsPEGcZIL9sUG7muGBA= Received: by 10.204.154.1 with SMTP id m1mr13279910bkw.107.1321865251335; Mon, 21 Nov 2011 00:47:31 -0800 (PST) Received: from a83-245-212-188.elisa-laajakaista.fi (a83-245-212-188.elisa-laajakaista.fi. [83.245.212.188]) by mx.google.com with ESMTPS id dq2sm6655647bkb.11.2011.11.21.00.47.29 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Nov 2011 00:47:30 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: <71CDCEF1-4A47-4FA0-8B4F-CB45CCDD3088@huawei.com> Date: Mon, 21 Nov 2011 10:47:28 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <9BAA71EA-CFD0-4541-BA15-E4FE840EC8B4@gmail.com> References: <71CDCEF1-4A47-4FA0-8B4F-CB45CCDD3088@huawei.com> To: Tina TSOU X-Mailer: Apple Mail (2.1084) Cc: "dime@ietf.org" Subject: Re: [Dime] Draft Dime notes from IETF#82 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, 21 Nov 2011 08:47:33 -0000 Ok. Fair enough. Since the I-D has already been through WGLC and had = enough reviews, you just need to tackle the remaining TRAC issues. Once = those have been addressed, we'll rerun a short WGLC again. Therefore it = would be preferable to spin out a new revision a way in advance of Paris = meeting. - Jouni On Nov 20, 2011, at 9:14 AM, Tina TSOU wrote: > Tom and I will update draft-ietf-dime-realm-based-redirect before = Paris. > Tom was not 100% healthy. He is recovering now. >=20 > Sent from my iPad >=20 > On Nov 20, 2011, at 2:46 PM, "jouni korhonen" = wrote: >=20 >> draft-ietf-dime-realm-based-redirect From Tina.Tsou.Zouting@huawei.com Mon Nov 21 00:50: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 6BB5D21F8B61 for ; Mon, 21 Nov 2011 00:50:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.061 X-Spam-Level: X-Spam-Status: No, score=-6.061 tagged_above=-999 required=5 tests=[AWL=0.538, 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 9HCwAu6I-v5A for ; Mon, 21 Nov 2011 00:50:31 -0800 (PST) Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id B287D21F8B5D for ; Mon, 21 Nov 2011 00:50:30 -0800 (PST) Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LV0009GM5U79M@szxga03-in.huawei.com> for dime@ietf.org; Mon, 21 Nov 2011 16:49:20 +0800 (CST) Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LV000L1H5TK4C@szxga03-in.huawei.com> for dime@ietf.org; Mon, 21 Nov 2011 16:49:19 +0800 (CST) Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AFC94950; Mon, 21 Nov 2011 16:49:14 +0800 Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 21 Nov 2011 16:49:13 +0800 Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.40]) by szxeml408-hub.china.huawei.com ([10.82.67.95]) with mapi id 14.01.0323.003; Mon, 21 Nov 2011 16:49:07 +0800 Date: Mon, 21 Nov 2011 08:49:06 +0000 From: Tina TSOU In-reply-to: <9A2E9984-EA8E-41D7-9834-916F73DCF432@gmail.com> X-Originating-IP: [10.212.244.201] To: jouni korhonen , "dime@ietf.org" Message-id: MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-language: en-US Content-transfer-encoding: 7BIT Accept-Language: en-US, zh-CN Thread-topic: [Dime] On RFC3588bis security.. Stephen Farrell's DISCUSS Thread-index: AQHMqCj2+wJ4gdqW806UlxHEKgNa9ZW3A/Qg X-MS-Has-Attach: X-MS-TNEF-Correlator: X-CFilter-Loop: Reflected References: <9A2E9984-EA8E-41D7-9834-916F73DCF432@gmail.com> Subject: Re: [Dime] On RFC3588bis security.. Stephen Farrell's DISCUSS 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, 21 Nov 2011 08:50:35 -0000 This solution works for me, though I think TLS is closer to what most of the vendors currently implement. Best Regards, Tina TSOU http://tinatsou.weebly.com/contact.html -----Original Message----- From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of jouni korhonen Sent: Monday, November 21, 2011 12:38 AM To: dime@ietf.org Subject: [Dime] On RFC3588bis security.. Stephen Farrell's DISCUSS Folks, During the meeting we had a discussion on Stephen Farrell's discuss: https://datatracker.ietf.org/doc/draft-ietf-dime-rfc3588bis/ballot/#stephen-farrell Glen had a solution proposal that we follow what Stephen suggested i.e. mandate use of either IPsec or (D)TLS within the spec and leave out the "some security mechanism". This of course has some impact on product & deployment level as from now on either IPsec or (D)TLS must be used.. Any feedback? - Jouni _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Mon Nov 21 01:02:34 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 11DE321F8B54 for ; Mon, 21 Nov 2011 01:02:34 -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 pTM3TzbMEx+N for ; Mon, 21 Nov 2011 01:02:33 -0800 (PST) Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4938121F8B49 for ; Mon, 21 Nov 2011 01:02:33 -0800 (PST) Received: by bkbzv15 with SMTP id zv15so7202412bkb.31 for ; Mon, 21 Nov 2011 01:02:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=iejAFXC6HozOL3U3W59AsOeAhyfZn0sy2ZUrdu8kg/s=; b=TDdK2fEivRPkCwjb1aCHM2QzO3QwtdrrhAVX4SLoDuTascbipXEuyMWd4CGWiQutMb EEl8oHp8iYisAMvijTHQD/RbLzw8ukHx2HrBD8wRoD4eJ6sJvnokYLYk/PQWFIceNSwT 7QhLA0Zzc3mx5iB3qLDzjqlzxePvKs401OECM= Received: by 10.205.121.1 with SMTP id ga1mr10966357bkc.60.1321866152330; Mon, 21 Nov 2011 01:02:32 -0800 (PST) Received: from a83-245-212-188.elisa-laajakaista.fi (a83-245-212-188.elisa-laajakaista.fi. [83.245.212.188]) by mx.google.com with ESMTPS id c4sm6686169bkk.13.2011.11.21.01.02.30 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Nov 2011 01:02:31 -0800 (PST) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 21 Nov 2011 11:02:29 +0200 Message-Id: <24FDCD7A-21A9-45F6-90C2-58DEAA1CF8F9@gmail.com> To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [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: Mon, 21 Nov 2011 09:02:34 -0000 Folks, As discussed in Taipei, please start working on the re-chartering text. = The original first text proposal (with all its typos and such) is here: = http://www.ietf.org/mail-archive/web/dime/current/msg04885.html If you have an issue with the existing text, propose a modification. If = you thing something has to be in the in addition to the current text, = propose new text. During the meeting we agreed to *expand* our charter beyond plain AAA, = thus allowing us to work on signaling level and using Diameter for other = purposes as plain AAA. This would mean a modification to charter's = description of the WG. For example: "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 in network access, = provisioning configuration information within the network, and using Diameter for other signaling purposes than authentication, authorization, accounting in network access." Using Diameter beyond plain AAA is already hinted in Section 1.1 of = RFC3588: ... 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= From Hannes.Tschofenig@gmx.net Mon Nov 21 01:19:27 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 1CA7121F8B3B for ; Mon, 21 Nov 2011 01:19:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.499 X-Spam-Level: X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, 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 I6inFXf8yRYQ for ; Mon, 21 Nov 2011 01:19:26 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 1D45A21F8B42 for ; Mon, 21 Nov 2011 01:19:25 -0800 (PST) Received: (qmail invoked by alias); 21 Nov 2011 09:19:24 -0000 Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [10.0.0.4]) [88.115.216.191] by mail.gmx.net (mp018) with SMTP; 21 Nov 2011 10:19:24 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX19prF5eK2lpTIjxgjZdkZ4XJMbOl48G6O7+puBw+C o/4a6KHUuFH+Qg Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Hannes Tschofenig In-Reply-To: <1ECBE0F0-5658-4DAD-B7EC-B06DFAF02E9F@gmail.com> Date: Mon, 21 Nov 2011 11:19:23 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <6A3D0DF3-3D5F-4753-984F-52F88B689192@gmx.net> References: <1ECBE0F0-5658-4DAD-B7EC-B06DFAF02E9F@gmail.com> To: jouni korhonen X-Mailer: Apple Mail (2.1084) X-Y-GMX-Trusted: 0 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: Mon, 21 Nov 2011 09:19:27 -0000 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 trac+dime@trac.tools.ietf.org Mon Nov 21 02:41: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 7B8AF21F8B91 for ; Mon, 21 Nov 2011 02:41:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 i6Yzk4EfFhON for ; Mon, 21 Nov 2011 02:41:40 -0800 (PST) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 85EA121F8B92 for ; Mon, 21 Nov 2011 02:41:40 -0800 (PST) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1RSRJa-0001YO-Ak; Mon, 21 Nov 2011 05:41:31 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "dime issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dime@ietf.org, gwz@net-zen.net X-Trac-Project: dime Date: Mon, 21 Nov 2011 10:41:30 -0000 X-URL: http://tools.ietf.org/wg/dime/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/dime/trac/ticket/19#comment:1 Message-ID: <079.f6dc07833210b17115ee3951ef51932a@trac.tools.ietf.org> References: <064.7acde6a2bdf9a7529b6f9f784b27fa78@trac.tools.ietf.org> X-Trac-Ticket-ID: 19 In-Reply-To: <064.7acde6a2bdf9a7529b6f9f784b27fa78@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dime@ietf.org, gwz@net-zen.net, dime-chairs@tools.ietf.org X-SA-Exim-Mail-From: trac+dime@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false X-Mailman-Approved-At: Mon, 21 Nov 2011 07:27:59 -0800 Cc: dime-chairs@tools.ietf.org Subject: Re: [Dime] [dime] #19: Tunnel-Assignment-Id AVP X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Reply-To: dime@ietf.org List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2011 10:41:41 -0000 #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 From trac+dime@trac.tools.ietf.org Mon Nov 21 02:43: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 A44E521F8B50 for ; Mon, 21 Nov 2011 02:43:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 kZZBslXsOH7P for ; Mon, 21 Nov 2011 02:43:39 -0800 (PST) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 3E96821F8801 for ; Mon, 21 Nov 2011 02:43:39 -0800 (PST) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1RSRLd-0001b3-Hp; Mon, 21 Nov 2011 05:43:37 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "dime issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dime@ietf.org, gwz@net-zen.net X-Trac-Project: dime Date: Mon, 21 Nov 2011 10:43:37 -0000 X-URL: http://tools.ietf.org/wg/dime/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/dime/trac/ticket/16#comment:1 Message-ID: <079.3b3ada33d6d269ff84d3820a103f9dee@trac.tools.ietf.org> References: <064.0512efebff43593dc4038989266f0cc0@trac.tools.ietf.org> X-Trac-Ticket-ID: 16 In-Reply-To: <064.0512efebff43593dc4038989266f0cc0@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dime@ietf.org, gwz@net-zen.net, dime-chairs@tools.ietf.org X-SA-Exim-Mail-From: trac+dime@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false X-Mailman-Approved-At: Mon, 21 Nov 2011 07:27:59 -0800 Cc: dime-chairs@tools.ietf.org Subject: Re: [Dime] [dime] #16: Accounting-Request (ACR) Command X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Reply-To: dime@ietf.org List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2011 10:43:39 -0000 #16: Accounting-Request (ACR) Command Comment (by gwz@…): OK, but that means that nobody will ever be able to use this command in a vendor-specific application, right? -- -----------------------------+--------------------- 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 From trac+dime@trac.tools.ietf.org Mon Nov 21 02:46: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 E057C21F8B91 for ; Mon, 21 Nov 2011 02:46:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 hU7xVbFF+4ko for ; Mon, 21 Nov 2011 02:46:44 -0800 (PST) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 40A5B21F8B77 for ; Mon, 21 Nov 2011 02:46:44 -0800 (PST) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1RSROd-0001iS-CQ; Mon, 21 Nov 2011 05:46:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "dime issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-dime-rfc3588bis@ietf.org, gwz@net-zen.net X-Trac-Project: dime Date: Mon, 21 Nov 2011 10:46:43 -0000 X-URL: http://tools.ietf.org/wg/dime/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/dime/trac/ticket/21#comment:2 Message-ID: <072.59d4ccde69cf262d2019a6b78c366705@trac.tools.ietf.org> References: <057.183c15a66cdfb38d9d333c1e501a2367@trac.tools.ietf.org> X-Trac-Ticket-ID: 21 In-Reply-To: <057.183c15a66cdfb38d9d333c1e501a2367@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-dime-rfc3588bis@ietf.org, gwz@net-zen.net, dime@ietf.org X-SA-Exim-Mail-From: trac+dime@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20111121104644.40A5B21F8B77@ietfa.amsl.com> Resent-Date: Mon, 21 Nov 2011 02:46:44 -0800 (PST) Resent-From: trac+dime@trac.tools.ietf.org X-Mailman-Approved-At: Mon, 21 Nov 2011 07:27:59 -0800 Cc: dime@ietf.org Subject: Re: [Dime] [dime] #21: typo X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Reply-To: dime@ietf.org List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2011 10:46:45 -0000 #21: typo Changes (by gwz@…): * status: new => closed * resolution: => fixed -- -------------------------------+------------------------------------------- Reporter: gwz@… | Owner: draft-ietf-dime-rfc3588bis@… Type: defect | Status: closed Priority: trivial | Milestone: Component: rfc3588bis | Version: Severity: Active WG | Resolution: fixed Document | Keywords: | -------------------------------+------------------------------------------- Ticket URL: dime From trac+dime@trac.tools.ietf.org Mon Nov 21 02:52:42 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 F3A1621F8B8C for ; Mon, 21 Nov 2011 02:52:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 ZMX4Pey8Taio for ; Mon, 21 Nov 2011 02:52:41 -0800 (PST) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 8DEF221F8B5E for ; Mon, 21 Nov 2011 02:52:41 -0800 (PST) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1RSRUN-00084J-0w; Mon, 21 Nov 2011 05:52:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "dime issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dime@ietf.org, gwz@net-zen.net X-Trac-Project: dime Date: Mon, 21 Nov 2011 10:52:39 -0000 X-URL: http://tools.ietf.org/wg/dime/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/dime/trac/ticket/18#comment:1 Message-ID: <079.0cc93c9317cad8abf6537639d01511fe@trac.tools.ietf.org> References: <064.56d439c7d20332f7ef87b62b012e4829@trac.tools.ietf.org> X-Trac-Ticket-ID: 18 In-Reply-To: <064.56d439c7d20332f7ef87b62b012e4829@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dime@ietf.org, gwz@net-zen.net, dime-chairs@tools.ietf.org X-SA-Exim-Mail-From: trac+dime@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false X-Mailman-Approved-At: Mon, 21 Nov 2011 07:27:59 -0800 Cc: dime-chairs@tools.ietf.org Subject: Re: [Dime] [dime] #18: Called-Station-Id AVP X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Reply-To: dime@ietf.org List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2011 10:52:42 -0000 #18: Called-Station-Id AVP Changes (by gwz@…): * status: new => closed * resolution: => fixed Comment: Offending sentence removed. -- -----------------------------+--------------------- Reporter: jouni.nospam@… | Owner: dime@… Type: defect | Status: closed Priority: major | Milestone: Component: rfc4005bis | Version: Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+--------------------- Ticket URL: dime From trac+dime@trac.tools.ietf.org Mon Nov 21 06:37: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 9C6F221F8B2B for ; Mon, 21 Nov 2011 06:37:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 6KrztXJrNTFa for ; Mon, 21 Nov 2011 06:37:17 -0800 (PST) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 7F51D21F8B29 for ; Mon, 21 Nov 2011 06:37:17 -0800 (PST) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1RSUzf-00054u-Ls; Mon, 21 Nov 2011 09:37:11 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "dime issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dime@ietf.org, gwz@net-zen.net X-Trac-Project: dime Date: Mon, 21 Nov 2011 14:37:11 -0000 X-URL: http://tools.ietf.org/wg/dime/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/dime/trac/ticket/17#comment:1 Message-ID: <079.b7bd18a35a368f7b0c427d9a9aded494@trac.tools.ietf.org> References: <064.68d0444852392e4d5c5c35d7b3b08c48@trac.tools.ietf.org> X-Trac-Ticket-ID: 17 In-Reply-To: <064.68d0444852392e4d5c5c35d7b3b08c48@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dime@ietf.org, gwz@net-zen.net, dime-chairs@tools.ietf.org X-SA-Exim-Mail-From: trac+dime@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false X-Mailman-Approved-At: Mon, 21 Nov 2011 07:27:59 -0800 Cc: dime-chairs@tools.ietf.org Subject: Re: [Dime] [dime] #17: QoSFilterRule X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Reply-To: dime@ietf.org List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2011 14:37:21 -0000 #17: QoSFilterRule Comment (by gwz@…): I'd be more than happy to take out QosFilter Rule & put in a reference to RFC 5777. Any other opinions? -- -----------------------------+--------------------- 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 From wwwrun@rfc-editor.org Tue Nov 22 16:21: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 3C12D21F8A91 for ; Tue, 22 Nov 2011 16:21:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.495 X-Spam-Level: X-Spam-Status: No, score=-102.495 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 6ln54dNhgxUf for ; Tue, 22 Nov 2011 16:21:42 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id DE27321F8A7E for ; Tue, 22 Nov 2011 16:21:42 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id DB2A4B1E005; Tue, 22 Nov 2011 16:16:05 -0800 (PST) To: jouni.nospam@gmail.com, julien.bournelle@orange-ftgroup.com, Hannes.Tschofenig@nsn.com, charliep@wichorus.com, kchowdhury@starentnetworks.com, dromasca@avaya.com, rbonica@juniper.net, lionel.morand@orange-ftgroup.com, jouni.korhonen@nsn.com From: RFC Errata System Message-Id: <20111123001605.DB2A4B1E005@rfc-editor.org> Date: Tue, 22 Nov 2011 16:16:05 -0800 (PST) X-Mailman-Approved-At: Tue, 22 Nov 2011 23:17:27 -0800 Cc: dime@ietf.org, rkuntz@us.toyota-itc.com, rfc-editor@rfc-editor.org Subject: [Dime] [Editorial Errata Reported] RFC5447 (3034) 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, 23 Nov 2011 00:21:46 -0000 The following errata report has been submitted for RFC5447, "Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5447&eid=3034 -------------------------------------- Type: Editorial Reported by: Romain Kuntz Section: 4.2.5 Original Text ------------- The following examples show how the LOCAL_HOME_AGENT_ASSIGNMENT (referred to as LOCAL-bit in the examples) capability and the MIP- Agent-Info AVP Corrected Text -------------- The following examples show how the LOCAL_HOME_AGENT_ASSIGNMENT (referred to as LOCAL-bit in the examples) capability and the MIP6- Agent-Info AVP Notes ----- There is no such thing as the "MIP-Agent-Info" AVP, it should be "MIP6-Agent-Info" Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5447 (draft-ietf-dime-mip6-integrated-12) -------------------------------------- Title : Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction Publication Date : February 2009 Author(s) : J. Korhonen, Ed., J. Bournelle, H. Tschofenig, C. Perkins, K. Chowdhury Category : PROPOSED STANDARD Source : Diameter Maintanence and Extensions Area : Operations and Management Stream : IETF Verifying Party : IESG From wwwrun@rfc-editor.org Tue Nov 22 16:29: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 9383D1F0C4F for ; Tue, 22 Nov 2011 16:29:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.496 X-Spam-Level: X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 8Ly4eBmbWUET for ; Tue, 22 Nov 2011 16:29:28 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 384C91F0C4D for ; Tue, 22 Nov 2011 16:29:28 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 2E7D6B1E005; Tue, 22 Nov 2011 16:23:51 -0800 (PST) To: jouni.nospam@gmail.com, Hannes.Tschofenig@gmx.net, julien.bournelle@orange-ftgroup.com, gerardo.giaretta@gmail.com, madjid.nakhjiri@motorola.com, dromasca@avaya.com, rbonica@juniper.net, lionel.morand@orange-ftgroup.com, jouni.korhonen@nsn.com From: RFC Errata System Message-Id: <20111123002351.2E7D6B1E005@rfc-editor.org> Date: Tue, 22 Nov 2011 16:23:51 -0800 (PST) X-Mailman-Approved-At: Tue, 22 Nov 2011 23:17:27 -0800 Cc: dime@ietf.org, rkuntz@us.toyota-itc.com, rfc-editor@rfc-editor.org Subject: [Dime] [Editorial Errata Reported] RFC5778 (3035) 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, 23 Nov 2011 00:29:28 -0000 The following errata report has been submitted for RFC5778, "Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5778&eid=3035 -------------------------------------- Type: Editorial Reported by: Romain Kuntz Section: GLOBAL Original Text ------------- MIP-Agent-Info Corrected Text -------------- MIP6-Agent-Info Notes ----- There is no such thing as the "MIP-Agent-Info" AVP (section 5.2.2 and 6.21), it should be "MIP6-Agent-Info" instead. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5778 (draft-ietf-dime-mip6-split-17) -------------------------------------- Title : Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction Publication Date : February 2010 Author(s) : J. Korhonen, Ed., H. Tschofenig, J. Bournelle, G. Giaretta, M. Nakhjiri Category : PROPOSED STANDARD Source : Diameter Maintanence and Extensions Area : Operations and Management Stream : IETF Verifying Party : IESG From jouni.nospam@gmail.com Tue Nov 22 23:57:53 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 C7D5811E8081 for ; Tue, 22 Nov 2011 23:57:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.58 X-Spam-Level: X-Spam-Status: No, score=-3.58 tagged_above=-999 required=5 tests=[AWL=0.019, 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 M3crlOK-UUob for ; Tue, 22 Nov 2011 23:57:53 -0800 (PST) Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB3821F8467 for ; Tue, 22 Nov 2011 23:57:52 -0800 (PST) Received: by fabs1 with SMTP id s1so1597234fab.31 for ; Tue, 22 Nov 2011 23:57:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=UV2DBhAWfg++ofjlqBoDUn/E5CKYv2jaVNV3Hp2a+Hs=; b=TrBMPOvgtgGRr+U7knQFwqf+hHqvgNGEZ0haTPyEPtFqCVIWDg0ul6tLX0Z2V9NkrH smbW9OUNZi/A+3VacAzBuDo87Du13Yv6mD9EvtxoLfo/fvWlNuhT208uBPPrL0qpO/B1 +Q36FMoRxTUShHxWZEBd6q4Eeftnu2rzsQPHc= Received: by 10.152.104.236 with SMTP id gh12mr13987257lab.49.1322035071672; Tue, 22 Nov 2011 23:57:51 -0800 (PST) Received: from a83-245-212-188.elisa-laajakaista.fi (a83-245-212-188.elisa-laajakaista.fi. [83.245.212.188]) by mx.google.com with ESMTPS id hm12sm15013710lab.9.2011.11.22.23.57.50 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 22 Nov 2011 23:57:50 -0800 (PST) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 23 Nov 2011 09:57:48 +0200 Message-Id: To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [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, 23 Nov 2011 07:57:53 -0000 Folks, The second stab on re-chartering text. Propose your changes and justify = also *why*. Note there are bunch of unknown dates in milestones and = such. - 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 in network access, = provisioning configuration information within the network, and using Diameter for other signaling purposes than authentication, authorization, accounting in network access. 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, AAA 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 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 stefan.winter@restena.lu Thu Nov 24 01:08:55 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 B436621F87D6 for ; Thu, 24 Nov 2011 01:08:55 -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 wNLuhnKXgPO1 for ; Thu, 24 Nov 2011 01:08:55 -0800 (PST) Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 7E56621F87C5 for ; Thu, 24 Nov 2011 01:08:44 -0800 (PST) Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 458BC107B5 for ; Thu, 24 Nov 2011 10:08:43 +0100 (CET) Received: from [IPv6:2001:a18:1:8:91c9:f33e:51fa:2e44] (unknown [IPv6:2001:a18:1:8:91c9:f33e:51fa:2e44]) by smtprelay.restena.lu (Postfix) with ESMTPS id 396F910691 for ; Thu, 24 Nov 2011 10:08:43 +0100 (CET) Message-ID: <4ECE09D8.6010503@restena.lu> Date: Thu, 24 Nov 2011 10:09:44 +0100 From: Stefan Winter User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: dime@ietf.org References: <9A2E9984-EA8E-41D7-9834-916F73DCF432@gmail.com> In-Reply-To: <9A2E9984-EA8E-41D7-9834-916F73DCF432@gmail.com> X-Enigmail-Version: 1.3.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig167D5FFDCC60B5A87CDB3007" X-Virus-Scanned: ClamAV Subject: Re: [Dime] On RFC3588bis security.. Stephen Farrell's DISCUSS 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, 24 Nov 2011 09:08:55 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig167D5FFDCC60B5A87CDB3007 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, > Folks, > > During the meeting we had a discussion on Stephen Farrell's discuss: ht= tps://datatracker.ietf.org/doc/draft-ietf-dime-rfc3588bis/ballot/#stephen= -farrell > > Glen had a solution proposal that we follow what Stephen suggested i.e.= mandate use of either IPsec or (D)TLS within the spec and leave out the = "some security mechanism". This of course has some impact on product & de= ployment level as from now on either IPsec or (D)TLS must be used.. > > Any feedback? As voiced in the meeting, I think that removing the "some" security mechanism is a very good idea. Stefan > > - Jouni > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime --=20 Stefan WINTER Ingenieur de Recherche Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National= e et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473 --------------enig167D5FFDCC60B5A87CDB3007 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7OCdwACgkQ+jm90f8eFWZ3BgCdHathfX2xDYmTd9gnacGCIONI 8jQAoIvLpgUUfFoodN2YxKvnno7KXWMw =6uHE -----END PGP SIGNATURE----- --------------enig167D5FFDCC60B5A87CDB3007-- From mark@azu.ca Mon Nov 28 08:49: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 50F1921F8B61 for ; Mon, 28 Nov 2011 08:49:21 -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 Vdlsy7L5Ru0S for ; Mon, 28 Nov 2011 08:49:20 -0800 (PST) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id DD6F921F8C07 for ; Mon, 28 Nov 2011 08:49:19 -0800 (PST) Received: by vbbez10 with SMTP id ez10so5518303vbb.31 for ; Mon, 28 Nov 2011 08:49:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.77.69 with SMTP id q5mr46861688vdw.11.1322498959223; Mon, 28 Nov 2011 08:49:19 -0800 (PST) Received: by 10.52.165.42 with HTTP; Mon, 28 Nov 2011 08:49:19 -0800 (PST) In-Reply-To: References: Date: Mon, 28 Nov 2011 11:49:19 -0500 Message-ID: From: Mark Jones To: dime@ietf.org Content-Type: multipart/alternative; boundary=20cf307f3834ae2cd104b2ce4870 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: Mon, 28 Nov 2011 16:49:21 -0000 --20cf307f3834ae2cd104b2ce4870 Content-Type: text/plain; charset=ISO-8859-1 Looks good to me. Some minor rewording suggestions for the consideration of the group... First paragraph: 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 in network access, provisioning configuration information within the network, and other signaling purposes. Why?: The removed text is redundant. Last paragraph: 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. Why?: - Generalize motherhood "interoperability" statement. I would also be ok with removing it. - Added clause on "appropriate use of Diameter" since we do seem to discuss this a lot. /Mark On Wed, Nov 23, 2011 at 2:57 AM, jouni korhonen wrote: > Folks, > > The second stab on re-chartering text. Propose your changes and justify > also *why*. Note there are bunch of unknown dates in milestones and such. > > - 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 in network access, provisioning > configuration information within the network, and using Diameter for > other signaling purposes than authentication, authorization, accounting > in network access. > > 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, AAA 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 > 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 > --20cf307f3834ae2cd104b2ce4870 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Looks good to me.=A0Some minor rewording suggestions for the consideration = of the group...

First paragraph:
=A0= =A0The Diameter Maintenance and Extensions WG will focus on maintenance=A0 =A0and extensions to the Diameter protocol required to enable its use = for
=A0 =A0authentication, authorization, accounting in network access, provisi= oning
=A0 =A0configuration information within the network, and=A0other s= ignaling purposes.
Why?: The removed text is redundant.

Last paragraph:
=A0 =A0Additionally, Diameter-based systems = require interoperability in order to work.
=A0 =A0The working group, alo= ng with the AD, will need to evaluate
=A0 =A0any potential extensions an= d require verification that the proposed
=A0 =A0extension is needed and an appropriate use of the Diameter protocol.=
=A0 =A0Coordination with other IETF working groups=A0and other S= DOs will be used to ensure this.
Why?:=A0
=A0 =A0- Gene= ralize motherhood "interoperability" statement. I would also be o= k with removing it.
=A0 =A0- Added clause on "appropriate use of Diameter" since= we do seem to discuss this a lot.

/Mark

On Wed, Nov 23, 2011 at 2:57 AM,= jouni korhonen <jouni.nospam@gmail.com> wrote:
Folks,

The second stab on re-chartering text. Propose your changes and justify als= o *why*. Note there are bunch of unknown dates in milestones and such.

- Jouni & Lionel

---------------------------------------------------------


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

Charter

Current Status: Active

Chairs:
=A0 =A0Lionel Morand <lionel.morand@orange-ftgroup.com>
=A0 =A0Jouni Korhonen <jouni.= korhonen@nsn.com>

Operations and Management Area Directors:
=A0 =A0Dan Romascanu <dromasca@av= aya.com>
=A0 =A0Ronald Bonica <rbonica@ju= niper.net>

Operations and Management Area Advisor:
=A0 =A0Dan Romascanu <dromasca@av= aya.com>

Mailing Lists:
=A0 =A0General Discussion: dime@ietf.org<= /a>
=A0 =A0To Subscribe: =A0 =A0 =A0 https://www.ietf.org/mailman/listinfo/dime<= /a>
=A0 =A0Archive: =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 =A0authentication, authorization, accounting in network access, provisionin= g
=A0configuration information within the network, and using Diameter for
=A0other signaling purposes than authentication, authorization, accounting<= br> =A0in network access.

=A0The 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<= br> =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 work=
=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<= br> =A0for configuring Diameter entities may be future work within the group.
=A0- Protocol extension for a bulk and group signaling. The aim of this
=A0work is to study and standardize a solution for handling a group of
=A0sessions within the Diameter base protocol context. The solution would =A0define how to identify and handle grouped sessions as a one combined
=A0entity for commands and operations.

=A0Additionally, AAA systems require interoperability in order to work.
=A0The 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
=A0and other SDOs will be used to ensure this.


Goals and Milestones:
=A0Done =A0 =A0 - Submit the following two Diameter Mobility documents to t= he IESG for consideration as a Proposed Standards:* 'Diameter Mobile IP= v6: Support for Home Agent to Diameter Server Interaction' * 'Diame= ter Mobile IPv6: Support for Network Access Server to Diameter Server Inter= action'
=A0Done =A0 =A0 - Submit 'Diameter API' to the IESG for considerati= on 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 for= consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter Support for EAP Re-authentication Pr= otocol' as DIME working group item
=A0Done =A0 =A0 - Submit 'Diameter User-Name and Realm Based Request Ro= uting Clarifications' as DIME working group item
=A0Done =A0 =A0 - Submit 'Diameter Proxy Mobile IPv6' as DIME worki= ng group item
=A0Done =A0 =A0 - Submit 'Quality of Service Attributes for Diameter= 9; to the IESG for consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter Proxy Mobile IPv6' to the IESG f= or consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter User-Name and Realm Based Request Ro= uting Clarifications' to the IESG for consideration as a Proposed Stand= ard
=A0Done =A0 =A0 - Submit 'Diameter NAT Control Application' as DIME= working group item
=A0Done =A0 =A0 - Submit 'Diameter Capabilities Update' as DIME wor= king 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 f= or consideration as an Informational RFC
=A0Done =A0 =A0 - Submit 'Diameter Capabilities Update' to the IESG= 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 D= IME working group item
=A0Done =A0 =A0 - Submit 'Diameter Support for Proxy Mobile IPv6 Locali= zed Routing' as DIME working group item
=A0Done =A0 =A0 - Submit 'Diameter Attribute-Value Pairs for Cryptograp= hic 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 group= item
=A0Done =A0 =A0 - Submit Revision of 'Diameter Base Protocol' to th= e IESG for consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter Attribute-Value Pairs for Cryptograp= hic Key Transport' to the IESG for consideration as a Proposed Standard=
=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 Ap= plication - RFC 4005bis' as DIME working group item
=A0Sep 201x - Submit 'Diameter Application Design Guidelines' to th= e IESG for consideration as a BCP document
=A0Done =A0 =A0 - Submit 'Diameter NAT Control Application' to the = IESG for consideration as a Proposed Standard
=A0Sep 201x - Submit 'Realm-Based Redirection In Diameter' to the I= ESG for consideration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter IKEv2 PSK' to the IESG for consi= deration as a Proposed Standard
=A0Done =A0 =A0 - Submit 'Diameter Extended NAPTR' to the IESG for = consideration as a Proposed Standard
=A0Nov 2011 - Submit 'Diameter Support for Proxy Mobile IPv6 Localized = Routing' to the IESG for consideration as a Proposed Standard
=A0Jul 201x - Submit 'Diameter Support for EAP Re-authentication Protoc= ol' to the IESG for consideration as a Proposed Standard
=A0Sep 201x - Submit Revision of 'Diameter Network Access Server Applic= ation - RFC 4005bis' to the IESG for consideration as a Proposed Standa= rd

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

--20cf307f3834ae2cd104b2ce4870-- From Lothar.Reith@detecon.com Mon Nov 28 10:22:20 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 4C86B21F8D31 for ; Mon, 28 Nov 2011 10:22:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 nJjWtJbsZ94t for ; Mon, 28 Nov 2011 10:22:15 -0800 (PST) Received: from dtc035.detecon.net (dtc035.detecon.net [194.25.60.135]) by ietfa.amsl.com (Postfix) with ESMTP id 64C2C21F8C6A for ; Mon, 28 Nov 2011 10:22:13 -0800 (PST) Received: from unknown (HELO dc00356.detecon.com) ([172.16.10.106]) by relay.dtc035.detecon.net with ESMTP; 28 Nov 2011 19:22:08 +0100 Received: from dc302v.detecon.com ([172.16.10.41]) by dc00356.detecon.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 28 Nov 2011 19:22:07 +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_01CCADFA.A326F6DC" Date: Mon, 28 Nov 2011 19:22:13 +0100 Message-ID: <8AAA8EFE7E4B594A86052935CF66E62E056115C8@dc302v.detecon.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dime] re-chartering Thread-Index: Acyt7a3JLEIQhfjeQYKATep3Y+dadgABYstA References: From: "Reith, Lothar" To: "Mark Jones" , X-OriginalArrivalTime: 28 Nov 2011 18:22:07.0657 (UTC) FILETIME=[A317B190:01CCADFA] 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: Mon, 28 Nov 2011 18:22:20 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CCADFA.A326F6DC Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, =20 I would like to suggest to change the term "accounting" to "accounting and online charging" in order to reflect in the first paragraph the online charging capabilities supported by Diameter Credit Control Application (RFC4006). =20 Best Regards, Lothar Reith Detecon International GmbH (Deutsche Telekom Group) =20 Von: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] Im Auftrag von Mark Jones Gesendet: Montag, 28. November 2011 17:49 An: dime@ietf.org Betreff: Re: [Dime] re-chartering =20 Looks good to me. Some minor rewording suggestions for the consideration of the group... =20 First paragraph: 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 in network access, provisioning configuration information within the network, and other signaling purposes. Why?: The removed text is redundant. =20 Last paragraph: 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. Why?:=20 - Generalize motherhood "interoperability" statement. I would also be ok with removing it. - Added clause on "appropriate use of Diameter" since we do seem to discuss this a lot. =20 /Mark =20 On Wed, Nov 23, 2011 at 2:57 AM, jouni korhonen wrote: Folks, The second stab on re-chartering text. Propose your changes and justify also *why*. Note there are bunch of unknown dates in milestones and such. - 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 in network access, provisioning configuration information within the network, and using Diameter for other signaling purposes than authentication, authorization, accounting in network access. 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, AAA 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 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 =20 ------_=_NextPart_001_01CCADFA.A326F6DC Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear all,

 

I would like to suggest to change the term = “accounting”  to “accounting and online charging” in order to = reflect in the first paragraph the online charging capabilities supported by = Diameter Credit Control Application (RFC4006).

 

Best Regards, Lothar Reith

Detecon International GmbH (Deutsche Telekom = Group)

 

Von: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] Im Auftrag von Mark Jones
Gesendet: Montag, 28. November 2011 17:49
An: dime@ietf.org
Betreff: Re: [Dime] re-chartering

 

Looks good to = me. Some minor rewording suggestions for the consideration of the = group...

 

First = paragraph:

   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 in network = access, provisioning
   configuration information within the network, = and other signaling purposes.

Why?: The removed text = is redundant.

 

Last = paragraph:

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

Why?: 

   - = Generalize motherhood "interoperability" statement. I would also be ok = with removing it.

   - Added = clause on "appropriate use of Diameter" since we do seem to discuss this = a lot.

 

/Mark

 

On Wed, Nov 23, 2011 = at 2:57 AM, jouni korhonen <jouni.nospam@gmail.com> wrote:

Folks,

The second stab on re-chartering text. Propose your changes and justify = also *why*. Note there are bunch of unknown dates in milestones and such.

- Jouni & Lionel

---------------------------------------------------------


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

Charter

Current Status: Active

Chairs:
   Lionel Morand <lionel.morand@orange-ftg= roup.com>
   Jouni Korhonen <jouni.korhonen@nsn.com>
=
Operations and Management Area Directors:
   Dan Romascanu <dromasca@avaya.com>
   Ronald Bonica <rbonica@juniper.net>

Operations and Management Area Advisor:
   Dan Romascanu <dromasca@avaya.com>

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/maill= ist.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 in network access, = provisioning
 configuration information within the network, and using Diameter = for
 other signaling purposes than authentication, authorization, = accounting
 in network access.

 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, AAA 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
 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

 

------_=_NextPart_001_01CCADFA.A326F6DC-- From jouni.nospam@gmail.com Tue Nov 29 03:56: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 1CA2321F8B00 for ; Tue, 29 Nov 2011 03:56:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.83 X-Spam-Level: X-Spam-Status: No, score=-2.83 tagged_above=-999 required=5 tests=[AWL=0.150, 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 jjI+HLwMlc5t for ; Tue, 29 Nov 2011 03:56:56 -0800 (PST) Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id E133821F84AC for ; Tue, 29 Nov 2011 03:56:55 -0800 (PST) Received: by eear51 with SMTP id r51so1165537eea.31 for ; Tue, 29 Nov 2011 03:56:55 -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=alqKdooIkwi9k2YwI3Zy5Xk83+KZRGvHF2z8gjYpaq4=; b=agEswmq+/H+oO45MLmfwUY9yNiC9XdyZ1idphxeJ1xP4fAadUvJU9IgDe+hIa+hWTC bT6mxxo68ga/eGHm0axBQKOB83/dTxTW5EhvgF+N/xbTYFDTmRiKksNnhNSTy5axmXks kuU1L8VQTU8fh2Y3TOg+HCKSMI3CBAsmFMKmk= Received: by 10.180.7.198 with SMTP id l6mr49737802wia.3.1322567814989; Tue, 29 Nov 2011 03:56:54 -0800 (PST) Received: from [10.255.131.156] ([192.100.123.77]) by mx.google.com with ESMTPS id z3sm14443490wid.11.2011.11.29.03.56.52 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 Nov 2011 03:56:54 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 From: jouni korhonen In-Reply-To: <8AAA8EFE7E4B594A86052935CF66E62E056115C8@dc302v.detecon.com> Date: Tue, 29 Nov 2011 13:56:49 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <7F716F2F-8E39-4AD9-952D-6BA3C6590A4E@gmail.com> References: <8AAA8EFE7E4B594A86052935CF66E62E056115C8@dc302v.detecon.com> To: "Reith, Lothar" 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: Tue, 29 Nov 2011 11:56:57 -0000 Lothar, On Nov 28, 2011, at 8:22 PM, Reith, Lothar wrote: > Dear all, > =20 > I would like to suggest to change the term =93accounting=94 to = =93accounting and online charging=94 in order to reflect in the first = paragraph the online charging capabilities supported by Diameter Credit = Control Application (RFC4006). Are you referring to e.g. "..its use for authentication, authorization, = accounting in network access.." ? There accounting is just part of the = expanded AAA acronym. To be sure what you want, could you propose the = actual text change? - Jouni > =20 > Best Regards, Lothar Reith > Detecon International GmbH (Deutsche Telekom Group) > =20 > Von: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] Im Auftrag = von Mark Jones > Gesendet: Montag, 28. November 2011 17:49 > An: dime@ietf.org > Betreff: Re: [Dime] re-chartering > =20 > Looks good to me. Some minor rewording suggestions for the = consideration of the group... > =20 > First paragraph: > 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 in network access, = provisioning > configuration information within the network, and other signaling = purposes. > Why?: The removed text is redundant. > =20 > Last paragraph: > 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. > Why?:=20 > - Generalize motherhood "interoperability" statement. I would also = be ok with removing it. > - Added clause on "appropriate use of Diameter" since we do seem to = discuss this a lot. > =20 > /Mark > =20 > On Wed, Nov 23, 2011 at 2:57 AM, jouni korhonen = wrote: > Folks, >=20 > The second stab on re-chartering text. Propose your changes and = justify also *why*. Note there are bunch of unknown dates in milestones = and such. >=20 > - Jouni & Lionel >=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 in network access, = provisioning > configuration information within the network, and using Diameter for > other signaling purposes than authentication, authorization, = accounting > in network access. >=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, AAA 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 > _______________________________________________ > 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 Nov 30 01:39: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 3935021F86F6 for ; Wed, 30 Nov 2011 01:39:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.905 X-Spam-Level: X-Spam-Status: No, score=-2.905 tagged_above=-999 required=5 tests=[AWL=0.075, 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 d3RypZ1FcYcX for ; Wed, 30 Nov 2011 01:39:58 -0800 (PST) Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2500F21F86A6 for ; Wed, 30 Nov 2011 01:39:57 -0800 (PST) Received: by eear51 with SMTP id r51so247795eea.31 for ; Wed, 30 Nov 2011 01:39: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:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=wDLvIr0P4PoWbo8A/W17y3EZLWx7WeZiBEjxYenDdUE=; b=CDa6gXAhIpQV2Op1kfHe8tiY/Nj3eV/ThO0/WwOxlfVGVzYMl4LsXOuwwa/mcbOQyA huXhlJxBtDirtS4tiXRFB2SJ0aQgW24r87IuaJ+l9mFMwcPitQ6ZRBLH00TbIHTR1Nv+ Qnvyr87lvvxpGDQ+lcWU3/YUPHD50WST9C0hY= Received: by 10.180.106.3 with SMTP id gq3mr1142537wib.34.1322645997169; Wed, 30 Nov 2011 01:39:57 -0800 (PST) Received: from [10.255.133.69] ([192.100.123.77]) by mx.google.com with ESMTPS id fw16sm1556843wbb.13.2011.11.30.01.39.54 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 Nov 2011 01:39:55 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: Date: Wed, 30 Nov 2011 11:39:52 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> References: 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, 30 Nov 2011 09:39:59 -0000 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 =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 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. =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 jouni.nospam@gmail.com Wed Nov 30 02:39: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 9D9B021F8B07 for ; Wed, 30 Nov 2011 02:39:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.93 X-Spam-Level: X-Spam-Status: No, score=-2.93 tagged_above=-999 required=5 tests=[AWL=0.050, 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 ZF9EbGoTFJis for ; Wed, 30 Nov 2011 02:39:09 -0800 (PST) Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id EB47121F8B06 for ; Wed, 30 Nov 2011 02:39:08 -0800 (PST) Received: by faap14 with SMTP id p14so300937faa.31 for ; Wed, 30 Nov 2011 02:39:08 -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=xZg3FlvJf7+hluTyuPp5HaoCLtcDStcWv9ntE7KRE24=; b=qbUSAy9FeFbwIzQlebQcMjo/+uflm5RXUJ0Dfv5Tx7INwk/OiD/kBueIFrM8DfKwNC zzRc6sx7prb/oHwiYH+JVgCiWVIWbqsfSWkModbKMV/+QP14KYz8j2AddoBK8zUpH5B+ tUCeb8GJL4augg9ZdNfk9vMtXAfpu6VYXGPh0= Received: by 10.180.4.102 with SMTP id j6mr1302266wij.38.1322649548028; Wed, 30 Nov 2011 02:39:08 -0800 (PST) Received: from [10.255.128.225] ([192.100.123.77]) by mx.google.com with ESMTPS id x8sm422348wix.17.2011.11.30.02.39.05 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 Nov 2011 02:39:06 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 From: jouni korhonen In-Reply-To: <079.3b3ada33d6d269ff84d3820a103f9dee@trac.tools.ietf.org> Date: Wed, 30 Nov 2011 12:39:02 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <064.0512efebff43593dc4038989266f0cc0@trac.tools.ietf.org> <079.3b3ada33d6d269ff84d3820a103f9dee@trac.tools.ietf.org> To: dime@ietf.org, Mark Jones X-Mailer: Apple Mail (2.1084) Cc: Glen Zorn , dime-chairs@tools.ietf.org Subject: Re: [Dime] [dime] #16: Accounting-Request (ACR) Command 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, 30 Nov 2011 10:39:09 -0000 You could but you finding out the vendor-id for the vendor specific = application might need more work then. IMHO we should keep the = Vendor-Specific- Application-Id.. just to make life easier. - Jouni On Nov 21, 2011, at 12:43 PM, dime issue tracker wrote: > #16: Accounting-Request (ACR) Command >=20 >=20 > Comment (by gwz@=85): >=20 > OK, but that means that nobody will ever be able to use this command = in a > vendor-specific application, right? >=20 > --=20 > -----------------------------+--------------------- > Reporter: jouni.nospam@=85 | Owner: dime@=85 > Type: defect | Status: new > Priority: major | Milestone: > Component: rfc4005bis | Version: > Severity: In WG Last Call | Resolution: > Keywords: | > -----------------------------+--------------------- >=20 > Ticket URL: = > dime >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From fbrockne@cisco.com Wed Nov 30 02:39:49 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 A40DF21F8B06 for ; Wed, 30 Nov 2011 02:39:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 1zW4+aZUl+P6 for ; Wed, 30 Nov 2011 02:39:48 -0800 (PST) Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id C6A5E21F8B21 for ; Wed, 30 Nov 2011 02:39:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fbrockne@cisco.com; l=8056; q=dns/txt; s=iport; t=1322649583; x=1323859183; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=hQ3Wu1U2wo2veHeDNPi47a7N5drGSS2EdvgFS+uqB7s=; b=M0HVgVM2G2jCxNO32OcCALrCdFxiUxZxwuCIjTgEHobN6R7jRisnUQh6 Xp87xvIoJGMHDMQzzdfFwsArQW9VKod2IPI1Sv7VJqRjuks5Y7DlQ3PBa cVaxtkUgXz1om3pp0zYMMo/FetgOIZRuCW9Cjitkfcz6O3Fz/z64dnQRl 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4AAO0G1k6Q/khM/2dsb2JhbAA6CpprkBiBBYFyAQEBAQMBAQEPAR0KNBcEAgEIEQQBAQsCBBcBBgEmHwkIAQEEARIIARIHh22ZJwGeNodsglFjBJ8yhzY X-IronPort-AV: E=Sophos;i="4.69,596,1315180800"; d="scan'208";a="4034760" Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 30 Nov 2011 10:39:41 +0000 Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAUAdfNp016698; Wed, 30 Nov 2011 10:39:41 GMT Received: from xmb-ams-106.cisco.com ([144.254.74.81]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 30 Nov 2011 11:39:41 +0100 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, 30 Nov 2011 11:39:37 +0100 Message-ID: <0D212BD466921646B58854FB79092CEC072BE54B@XMB-AMS-106.cisco.com> In-Reply-To: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dime] re-chartering Thread-Index: AcyvRBd4KPRDBvoVTlu+P3Zw7nh0iQAB438w References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> From: "Frank Brockners (fbrockne)" To: "jouni korhonen" , X-OriginalArrivalTime: 30 Nov 2011 10:39:41.0213 (UTC) FILETIME=[5DBFD4D0:01CCAF4C] 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, 30 Nov 2011 10:39:49 -0000 Thanks for the updated version. Two minor comments: - typo: s/for a bulk/for bulk/ - 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, 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? Thanks, Frank =20 =20 > -----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 >=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 Wed Nov 30 02:52: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 CB44721F8B23 for ; Wed, 30 Nov 2011 02:52:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.943 X-Spam-Level: X-Spam-Status: No, score=-2.943 tagged_above=-999 required=5 tests=[AWL=0.038, 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 7D4Z1-Aeo7VA for ; Wed, 30 Nov 2011 02:52:41 -0800 (PST) Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9F6A521F8B20 for ; Wed, 30 Nov 2011 02:52:41 -0800 (PST) Received: by faap14 with SMTP id p14so311253faa.31 for ; Wed, 30 Nov 2011 02:52:40 -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=CRU+74ufqKUIMcpgOyLGt8n/CP86oV9G+kl4P2q2C1c=; b=LTWQx2FyKGbJLuTWQU7c1nx7lySA/MECl1AaCe35bVuKqBZXeIOj504zS6BHbUrRUk YQH6lFi9sQuql8zSbYMULNS2/txcpG7o0+opH6rG1upSsnZtol5/prAT0Im1BJ9tu+j2 NzcF4AXLYwYAQhJLR7BpBYHAlOHJkjuJS5JgI= Received: by 10.180.19.42 with SMTP id b10mr1743973wie.39.1322650360772; Wed, 30 Nov 2011 02:52:40 -0800 (PST) Received: from [10.255.128.225] ([192.100.123.77]) by mx.google.com with ESMTPS id n2sm430838wiz.16.2011.11.30.02.52.37 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 Nov 2011 02:52:38 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 From: jouni korhonen In-Reply-To: <079.b7bd18a35a368f7b0c427d9a9aded494@trac.tools.ietf.org> Date: Wed, 30 Nov 2011 12:52:34 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <8DA9C2E7-8D78-441E-9F5B-2B6FD59089DC@gmail.com> References: <064.68d0444852392e4d5c5c35d7b3b08c48@trac.tools.ietf.org> <079.b7bd18a35a368f7b0c427d9a9aded494@trac.tools.ietf.org> To: dime@ietf.org, Mark Jones X-Mailer: Apple Mail (2.1084) Cc: Glen Zorn Subject: Re: [Dime] [dime] #17: QoSFilterRule 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, 30 Nov 2011 10:52:45 -0000 I am for RFC5777 reference. I do have some reservations to deprecate = existing QosFilter Rule... someone might even have implemented it ;) - Jouni On Nov 21, 2011, at 4:37 PM, dime issue tracker wrote: > #17: QoSFilterRule >=20 >=20 > Comment (by gwz@=85): >=20 > I'd be more than happy to take out QosFilter Rule & put in a reference = to > RFC 5777. Any other opinions? >=20 > --=20 > -----------------------------+--------------------- > Reporter: jouni.nospam@=85 | Owner: dime@=85 > Type: defect | Status: new > Priority: major | Milestone: > Component: rfc4005bis | Version: > Severity: In WG Last Call | Resolution: > Keywords: | > -----------------------------+--------------------- >=20 > Ticket URL: = > dime >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Wed Nov 30 02:56:32 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 81F1421F8ABB for ; Wed, 30 Nov 2011 02:56:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.95 X-Spam-Level: X-Spam-Status: No, score=-2.95 tagged_above=-999 required=5 tests=[AWL=0.030, 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 6U3chR6mS0gR for ; Wed, 30 Nov 2011 02:56:31 -0800 (PST) Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9E321F86D0 for ; Wed, 30 Nov 2011 02:56:31 -0800 (PST) Received: by eear51 with SMTP id r51so304234eea.31 for ; Wed, 30 Nov 2011 02:56:30 -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=6hYbk7Kum9Ch3VXJRSh6iREB1sFzmwUhoT7af5qgBFo=; b=Ul+HS9tfsRJnIYy2bizKwTM+RuHl+1fq5P8+pnJxqqGAO2lZhervaPJKldvEZBPQXi g6Wjqp5CrF1/x9qqmorfArNux1oMtpeTW/EkoqzX6a26CXb0wDkz0D1LwZFVP0nCNh// y1K7fk8jnUhxmL0NhdQVH5qVez39/imOY3hgE= Received: by 10.180.106.3 with SMTP id gq3mr1336416wib.34.1322650590448; Wed, 30 Nov 2011 02:56:30 -0800 (PST) Received: from [10.255.128.225] ([192.100.123.77]) by mx.google.com with ESMTPS id hq5sm438319wib.7.2011.11.30.02.56.28 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 Nov 2011 02:56:29 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 From: jouni korhonen In-Reply-To: <079.f6dc07833210b17115ee3951ef51932a@trac.tools.ietf.org> Date: Wed, 30 Nov 2011 12:56:23 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <93F308DA-4A54-4D57-A2B6-278C06395904@gmail.com> References: <064.7acde6a2bdf9a7529b6f9f784b27fa78@trac.tools.ietf.org> <079.f6dc07833210b17115ee3951ef51932a@trac.tools.ietf.org> To: Glen Zorn , Mark Jones X-Mailer: Apple Mail (2.1084) 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: Wed, 30 Nov 2011 10:56:32 -0000 And the reasoning behind is? - Jouni On Nov 21, 2011, at 12:41 PM, dime issue tracker wrote: > #19: Tunnel-Assignment-Id AVP >=20 >=20 > Comment (by gwz@=85): >=20 > Yes, it was intentional. >=20 > --=20 > -----------------------------+--------------------- > Reporter: jouni.nospam@=85 | Owner: dime@=85 > Type: defect | Status: new > Priority: major | Milestone: > Component: rfc4005bis | Version: > Severity: In WG Last Call | Resolution: > Keywords: | > -----------------------------+--------------------- >=20 > Ticket URL: = > dime >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Wed Nov 30 02:59: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 1905C21F8B2B for ; Wed, 30 Nov 2011 02:59:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.955 X-Spam-Level: X-Spam-Status: No, score=-2.955 tagged_above=-999 required=5 tests=[AWL=0.025, 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 0fVXnqq89QT6 for ; Wed, 30 Nov 2011 02:59:34 -0800 (PST) Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6C13021F8B24 for ; Wed, 30 Nov 2011 02:59:34 -0800 (PST) Received: by faap14 with SMTP id p14so316297faa.31 for ; Wed, 30 Nov 2011 02:59:33 -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=BwSS7+DqqFbgw3V1BwhqOW7aLbXWle0HsrkLMWTfjqs=; b=LQPrertICktm7ZFDU9/NPj2cKna5+wBbiTuzutG6sPwbM5SH2Hfj4BP5kedwZPdOV0 O8qOByWprq0pPsNy+lBV/Cgq26R/JD76GUR19tk+4qTQ//DmofHcL7t0wf8QztxDYfB/ 9t4YCU4KqvsohgnU63jAIVBcFoP/wC88y7udI= Received: by 10.180.105.3 with SMTP id gi3mr1343051wib.36.1322650773524; Wed, 30 Nov 2011 02:59:33 -0800 (PST) Received: from [10.255.128.225] ([192.100.123.77]) by mx.google.com with ESMTPS id dw6sm437405wib.12.2011.11.30.02.59.30 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 Nov 2011 02:59:31 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: <4E51289C.20401@gmail.com> Date: Wed, 30 Nov 2011 12:59:26 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <91C4C13F-787E-4120-B1A0-2C65BE66B7A1@gmail.com> References: <057.0ca7cc0abc305c0fa4d3c5ae33d14fe6@trac.tools.ietf.org> <8C993400-B596-4A55-A229-B8432EC5EEB6@gmail.com> <4E4F7491.5030709@gmail.com> <1DA18178-E97F-4928-AC56-A83DAC8AA5E3@gmail.com> <4E50C54E.4030401@gmail.com> <9CAFBBC5-7F5A-4536-83EA-53EBF3A8AF9B@gmail.com> <4E51289C.20401@gmail.com> To: Glen Zorn X-Mailer: Apple Mail (2.1084) Cc: dime@ietf.org Subject: Re: [Dime] rfc3588bis next revision; was Re: [dime] #20: no accounting model specified 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, 30 Nov 2011 10:59:35 -0000 Shouldn't we then do the change in RFC4005bis and be done with this = ticket? Any proposal for a text? - Jouni On Aug 21, 2011, at 6:47 PM, Glen Zorn wrote: > On 8/21/2011 10:28 PM, jouni korhonen wrote: >=20 > ... >=20 >>>> Hmm.. Any particular reason why NASREQ uses base app id for ACR/ACA = and not base acct id? >>>=20 >>> I think that it is an error in 4005. Actually, I find it hard to >>> believe that NASREQ would ever work except in a monolithic, "toy" >>> implementation. For example, the NASREQ version of the ASR/ASA = messages >>> includes a bunch of optional AVPs (with the 'M' bit set) that are >>> undefined in RFC 3588 to the base protocol server; it's hard to = imagine >>> how a standard implementation of 3588 could not treat the reception = of >>> such AVPs as an error. >>=20 >> MAybe this is then good candidates to be fixed in 4005bis? Or do you = think it would make situation worse in real deployments from a backward = compatibility point of view? >=20 > I was under the impression that there are no real deployments; if = there > were, someone would certainly have noticed this, don't you think? >=20 > ... From Marco.Liebsch@neclab.eu Wed Nov 30 03:33: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 7271121F8A71 for ; Wed, 30 Nov 2011 03:33: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 K+otQYkaWkhY for ; Wed, 30 Nov 2011 03:33:18 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 49D6121F8A6F for ; Wed, 30 Nov 2011 03:33:18 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 3C497280001C8; Wed, 30 Nov 2011 12:33:17 +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 edgI4Iktg+7L; Wed, 30 Nov 2011 12:33:17 +0100 (CET) Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 17FC7280000FC; Wed, 30 Nov 2011 12:33:07 +0100 (CET) Received: from Polydeuces.office.hd ([169.254.3.40]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Wed, 30 Nov 2011 12:33:07 +0100 From: Marco Liebsch To: jouni korhonen , "dime@ietf.org" Thread-Topic: [Dime] re-chartering Thread-Index: AQHMqbWhX5qzDvK+tUWyVr3a+tBLeZXCdymAgAKsrQCAACdn4A== Date: Wed, 30 Nov 2011 11:33:06 +0000 Message-ID: <69756203DDDDE64E987BC4F70B71A26D24D156CD@Polydeuces.office.hd> References: <807C6512-D688-4393-B6E1-C4D2C9604582@gmail.com> In-Reply-To: <807C6512-D688-4393-B6E1-C4D2C9604582@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 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, 30 Nov 2011 11:33:19 -0000 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 o= ther signaling purposes. .. 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. If we plan to look at bulk operation use cases also for NASREQ and Credit C= ontrol 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. What about the following: - Protocol extension for /- a -/ bulk and group signaling. The aim of thi= s work is to study and standardize a solution for handling /-a-/ group/+s+/= of sessions within /-the Diameter base protocol -/ /+ Diameter applications= ' +/ context. 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 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 >=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 wor= k > 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 Diamete= r' to > the IESG for consideration as a Proposed Standard. > Done - Submit 'Diameter QoS Application' to the IESG for considerat= ion 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 it= em > Done - Submit 'Quality of Service Attributes for Diameter' to the I= ESG for > consideration as a Proposed Standard > Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for consider= ation > 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 gr= oup > item > Done - Submit 'Diameter Capabilities Update' as DIME working group = item > Done - Submit ' Diameter Credit Control Application MIB' to the IES= G for > consideration as an Informational RFC > Done - Submit 'Diameter Base Protocol MIB' to the IESG for consider= ation > as an Informational RFC > Done - Submit 'Diameter Capabilities Update' to the IESG for consid= eration > 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 Rou= ting' > 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 wor= king > 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 Applicati= on - > 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 considerati= on > 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 Applicati= on - > 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 hannes.tschofenig@gmx.net Wed Nov 30 03:38:54 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 7FD3A21F87D9 for ; Wed, 30 Nov 2011 03:38:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 Jz9ZxGjw75ZI for ; Wed, 30 Nov 2011 03:38:54 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id A6C1421F86EE for ; Wed, 30 Nov 2011 03:38:53 -0800 (PST) Received: (qmail invoked by alias); 30 Nov 2011 11:38:51 -0000 Received: from unknown (EHLO [10.112.95.212]) [62.50.241.116] by mail.gmx.net (mp071) with SMTP; 30 Nov 2011 12:38:51 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX1+B9NwcZqSBwKcnXK3r3e5JlVf3A8Arx2+iPDfLF7 B8OO3Yd7XqzIU5 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 From: Hannes Tschofenig In-Reply-To: <8DA9C2E7-8D78-441E-9F5B-2B6FD59089DC@gmail.com> Date: Wed, 30 Nov 2011 12:38:49 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <15B8251F-B6A3-4DAB-8F0D-5001085413F1@gmx.net> References: <064.68d0444852392e4d5c5c35d7b3b08c48@trac.tools.ietf.org> <079.b7bd18a35a368f7b0c427d9a9aded494@trac.tools.ietf.org> <8DA9C2E7-8D78-441E-9F5B-2B6FD59089DC@gmail.com> To: jouni korhonen X-Mailer: Apple Mail (2.1084) X-Y-GMX-Trusted: 0 Cc: dime@ietf.org, Glen Zorn Subject: Re: [Dime] [dime] #17: QoSFilterRule 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, 30 Nov 2011 11:38:54 -0000 I also agree that a reference to RFC 5777 might be useful. I don't see = any other useful option.=20 On Nov 30, 2011, at 11:52 AM, jouni korhonen wrote: >=20 > I am for RFC5777 reference. I do have some reservations to deprecate = existing QosFilter Rule... someone might even have implemented it ;) >=20 > - Jouni >=20 >=20 > On Nov 21, 2011, at 4:37 PM, dime issue tracker wrote: >=20 >> #17: QoSFilterRule >>=20 >>=20 >> Comment (by gwz@=85): >>=20 >> I'd be more than happy to take out QosFilter Rule & put in a = reference to >> RFC 5777. Any other opinions? >>=20 >> --=20 >> -----------------------------+--------------------- >> Reporter: jouni.nospam@=85 | Owner: dime@=85 >> Type: defect | Status: new >> Priority: major | Milestone: >> Component: rfc4005bis | Version: >> Severity: In WG Last Call | Resolution: >> Keywords: | >> -----------------------------+--------------------- >>=20 >> Ticket URL: = >> dime >>=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 dromasca@avaya.com Wed Nov 30 07:55:02 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 3FAA521F8801 for ; Wed, 30 Nov 2011 07:55:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.249 X-Spam-Level: X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[AWL=0.350, 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 CiPo6hfL3vD1 for ; Wed, 30 Nov 2011 07:55:00 -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 DF65D21F84B7 for ; Wed, 30 Nov 2011 07:54:59 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArMAANxQ1k6HCzI1/2dsb2JhbABEhQOVbY8agQiBBYFyAQEBAQMSEQ0EUQYBCA0EBAEBAwIGBgwLAQICAwFEBwEBBQQBBBMIARmHbZg5hBSJbpFngTCGW4F/M2MEmjqMLg X-IronPort-AV: E=Sophos;i="4.69,597,1315195200"; d="scan'208";a="317188014" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 30 Nov 2011 10:54:59 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 30 Nov 2011 10:43:14 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Date: Wed, 30 Nov 2011 16:54:57 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Robert Sparks' Discuss on draft-ietf-dime-priority-avps-05: (withDISCUSS) Thread-Index: AcyvdwkxjsoVUpLUTVu5ZoopbiUlbQAAUUjA From: "Romascanu, Dan (Dan)" To: Subject: [Dime] FW: Robert Sparks' Discuss on draft-ietf-dime-priority-avps-05: (withDISCUSS) 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, 30 Nov 2011 15:55:02 -0000 RG9jdW1lbnQgZWRpdG9ycyBhbmQgc2hlcGhlcmQsIA0KDQpQbGVhc2UgYWRkcmVzcyB0aGUgaXNz dWVzIHJhaXNlZCBieSBSb2JlcnQgU3BhcmtzIGluIGhpcyBESVNDVVNTLiANCg0KVGhhbmtzIGFu ZCBSZWdhcmRzLA0KDQpEYW4NCg0KDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZy b206IGllc2ctYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmllc2ctYm91bmNlc0BpZXRmLm9yZ10g T24gQmVoYWxmIE9mIFJvYmVydCBTcGFya3MNClNlbnQ6IFdlZG5lc2RheSwgTm92ZW1iZXIgMzAs IDIwMTEgNTo0NSBQTQ0KVG86IFRoZSBJRVNHDQpDYzogZGltZS1jaGFpcnNAdG9vbHMuaWV0Zi5v cmc7IGRyYWZ0LWlldGYtZGltZS1wcmlvcml0eS1hdnBzQHRvb2xzLmlldGYub3JnDQpTdWJqZWN0 OiBSb2JlcnQgU3BhcmtzJyBEaXNjdXNzIG9uIGRyYWZ0LWlldGYtZGltZS1wcmlvcml0eS1hdnBz LTA1OiAod2l0aERJU0NVU1MpDQoNClJvYmVydCBTcGFya3MgaGFzIGVudGVyZWQgdGhlIGZvbGxv d2luZyBiYWxsb3QgcG9zaXRpb24gZm9yDQpkcmFmdC1pZXRmLWRpbWUtcHJpb3JpdHktYXZwcy0w NTogRGlzY3Vzcw0KDQpXaGVuIHJlc3BvbmRpbmcsIHBsZWFzZSBrZWVwIHRoZSBzdWJqZWN0IGxp bmUgaW50YWN0IGFuZCByZXBseSB0byBhbGwNCmVtYWlsIGFkZHJlc3NlcyBpbmNsdWRlZCBpbiB0 aGUgVG8gYW5kIENDIGxpbmVzLiAoRmVlbCBmcmVlIHRvIGN1dCB0aGlzDQppbnRyb2R1Y3Rvcnkg cGFyYWdyYXBoLCBob3dldmVyLikNCg0KUGxlYXNlIHJlZmVyIHRvIGh0dHA6Ly93d3cuaWV0Zi5v cmcvaWVzZy9zdGF0ZW1lbnQvZGlzY3Vzcy1jcml0ZXJpYS5odG1sDQpmb3IgbW9yZSBpbmZvcm1h dGlvbiBhYm91dCBJRVNHIERJU0NVU1MgYW5kIENPTU1FTlQgcG9zaXRpb25zLg0KDQoNCg0KLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLQ0KRElTQ1VTUzoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KVGhlIGZpcnN0IHBhcmFncmFw aCBvZiB0aGUgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgc2VjdGlvbiBpcyB1bmNsZWFyLiBJdCBh cHBlYXJzIHRvIGluc3RydWN0IGVsZW1lbnRzIChub3QgY2xlYXIgd2hpY2ggZWxlbWVudHMpIHRv IGlnbm9yZSBpbnRlZ3JpdHkgcHJvdGVjdGVkIHZhbHVlcy4gRG9lcyBpdCBtZWFuIGludGVncml0 eSBwcm90ZWN0ZWQgdmFsdWVzIHRoYXQgZmFpbCBpbnRlZ3JpdHkgY2hlY2s/IEl0IGluZGljYXRl cyB0aGF0IHByb3RvY29sIHNwZWNpZmljIGVycm9yIG1lc3NhZ2VzIHNob3VsZCBiZSBzZW50IHdo ZW4gdGhlc2UgdmFsdWVzIGFyZSBpZ25vcmVkIC0gd2hpY2ggcHJvdG9jb2wocyk/ICBJcyB0aGUg cGFyYWdyYXBoIHRyeWluZyB0byBzYXkgc29tZXRoaW5nIG1vcmUgdGhhbiAibG9jYWwgcG9saWN5 IGNhbiBvdmVycmlkZSB0aGUgcG9saWN5IHJlcXVlc3RlZCBieSBwcm90b2NvbCBtZXNzYWdlcyI/ IA0KDQoNCg0KDQo= From carlberg@g11.org.uk Wed Nov 30 08:02:58 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 C621B21F8B51 for ; Wed, 30 Nov 2011 08:02:58 -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 kPEnXCrM3xQ7 for ; Wed, 30 Nov 2011 08:02:58 -0800 (PST) Received: from portland.eukhosting.net (portland.eukhosting.net [92.48.97.5]) by ietfa.amsl.com (Postfix) with ESMTP id BA51921F8AB9 for ; Wed, 30 Nov 2011 08:02:57 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=g11.org.uk; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=rr73sgnfRx0wr4CeL0jVLeCwD0RFLaUJA8SkEZFkM7gXs/B/cQIT3gUrzgiS6tsfCYML16su7bylEWCUZCn87/XiDXorW5koMjyB/1YOX01Jtm2uCIAOp9c7omp7e160; Received: from c-76-111-69-4.hsd1.va.comcast.net ([76.111.69.4]:63671 helo=miro-2.private) by portland.eukhosting.net with esmtpa (Exim 4.69) (envelope-from ) id 1RVmcW-0004JG-Gg; Wed, 30 Nov 2011 16:02:52 +0000 Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: ken carlberg In-Reply-To: Date: Wed, 30 Nov 2011 11:02:54 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <6B4A8E55-416C-49C8-BD40-3186BBC20E73@g11.org.uk> References: To: "Romascanu, Dan (Dan)" X-Mailer: Apple Mail (2.1251.1) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - portland.eukhosting.net X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - g11.org.uk X-Source: X-Source-Args: X-Source-Dir: Cc: dime@ietf.org Subject: Re: [Dime] Robert Sparks' Discuss on draft-ietf-dime-priority-avps-05: (withDISCUSS) 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, 30 Nov 2011 16:02:58 -0000 Dan, are we awaiting any further reviews, or does Robert's DISCUSS culminate = the reviews/comments from the IESG. -ken On Nov 30, 2011, at 10:54 AM, Romascanu, Dan (Dan) wrote: > Document editors and shepherd,=20 >=20 > Please address the issues raised by Robert Sparks in his DISCUSS.=20 >=20 > Thanks and Regards, >=20 > Dan >=20 >=20 >=20 >=20 > -----Original Message----- > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf = Of Robert Sparks > Sent: Wednesday, November 30, 2011 5:45 PM > To: The IESG > Cc: dime-chairs@tools.ietf.org; = draft-ietf-dime-priority-avps@tools.ietf.org > Subject: Robert Sparks' Discuss on draft-ietf-dime-priority-avps-05: = (withDISCUSS) >=20 > Robert Sparks has entered the following ballot position for > draft-ietf-dime-priority-avps-05: Discuss >=20 > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut = this > introductory paragraph, however.) >=20 > Please refer to = http://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. >=20 >=20 >=20 > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- >=20 > The first paragraph of the Security Considerations section is unclear. = It appears to instruct elements (not clear which elements) to ignore = integrity protected values. Does it mean integrity protected values that = fail integrity check? It indicates that protocol specific error messages = should be sent when these values are ignored - which protocol(s)? Is = the paragraph trying to say something more than "local policy can = override the policy requested by protocol messages"?=20 >=20 >=20 >=20 >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From dromasca@avaya.com Wed Nov 30 08:05: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 004F721F8B70 for ; Wed, 30 Nov 2011 08:05:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.279 X-Spam-Level: X-Spam-Status: No, score=-103.279 tagged_above=-999 required=5 tests=[AWL=0.320, 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 bZ6eMv2aUVpq for ; Wed, 30 Nov 2011 08:05:44 -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 0BF0921F8B6D for ; Wed, 30 Nov 2011 08:05:43 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArMAAPZS1k7GmAcF/2dsb2JhbABEmnCQIoEFgXIBAQEBAwEBAQ8eCjQLDAQCAQgNBAQBAQEKBgwLAQYBJh8JCAEBBBMIARmHbZxPm1GKPWMEmjqMLg X-IronPort-AV: E=Sophos;i="4.69,597,1315195200"; d="scan'208";a="317190985" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 30 Nov 2011 11:05:43 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 30 Nov 2011 11:03:43 -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, 30 Nov 2011 17:05:41 +0100 Message-ID: In-Reply-To: <6B4A8E55-416C-49C8-BD40-3186BBC20E73@g11.org.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dime] Robert Sparks' Discuss on draft-ietf-dime-priority-avps-05: (withDISCUSS) Thread-Index: AcyveY3I/djhqvTqRSKRWfuUZX+QuQAACt+A References: <6B4A8E55-416C-49C8-BD40-3186BBC20E73@g11.org.uk> From: "Romascanu, Dan (Dan)" To: "ken carlberg" Cc: dime@ietf.org Subject: Re: [Dime] Robert Sparks' Discuss on draft-ietf-dime-priority-avps-05: (withDISCUSS) 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, 30 Nov 2011 16:05:45 -0000 Hi Ken, There may be other reviews and comments until the telechat tomorrow. However, I suggest to respond to each of them separately.=20 Regards, Dan > -----Original Message----- > From: ken carlberg [mailto:carlberg@g11.org.uk] > Sent: Wednesday, November 30, 2011 6:03 PM > To: Romascanu, Dan (Dan) > Cc: dime@ietf.org > Subject: Re: [Dime] Robert Sparks' Discuss on draft-ietf-dime-priority- > avps-05: (withDISCUSS) >=20 > Dan, >=20 > are we awaiting any further reviews, or does Robert's DISCUSS culminate > the reviews/comments from the IESG. >=20 > -ken >=20 >=20 > On Nov 30, 2011, at 10:54 AM, Romascanu, Dan (Dan) wrote: >=20 > > Document editors and shepherd, > > > > Please address the issues raised by Robert Sparks in his DISCUSS. > > > > Thanks and Regards, > > > > Dan > > > > > > > > > > -----Original Message----- > > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf > Of Robert Sparks > > Sent: Wednesday, November 30, 2011 5:45 PM > > To: The IESG > > Cc: dime-chairs@tools.ietf.org; draft-ietf-dime-priority- > avps@tools.ietf.org > > Subject: Robert Sparks' Discuss on draft-ietf-dime-priority-avps-05: > (withDISCUSS) > > > > Robert Sparks has entered the following ballot position for > > draft-ietf-dime-priority-avps-05: Discuss > > > > When responding, please keep the subject line intact and reply to all > > email addresses included in the To and CC lines. (Feel free to cut > this > > introductory paragraph, however.) > > > > Please refer to http://www.ietf.org/iesg/statement/discuss- > criteria.html > > for more information about IESG DISCUSS and COMMENT positions. > > > > > > > > --------------------------------------------------------------------- > - > > DISCUSS: > > --------------------------------------------------------------------- > - > > > > The first paragraph of the Security Considerations section is > unclear. It appears to instruct elements (not clear which elements) to > ignore integrity protected values. Does it mean integrity protected > values that fail integrity check? It indicates that protocol specific > error messages should be sent when these values are ignored - which > protocol(s)? Is the paragraph trying to say something more than "local > policy can override the policy requested by protocol messages"? > > > > > > > > > > _______________________________________________ > > DiME mailing list > > DiME@ietf.org > > https://www.ietf.org/mailman/listinfo/dime From dromasca@avaya.com Wed Nov 30 13:51:18 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 90D3E11E8099 for ; Wed, 30 Nov 2011 13:51:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.789 X-Spam-Level: X-Spam-Status: No, score=-102.789 tagged_above=-999 required=5 tests=[AWL=-0.190, BAYES_00=-2.599, 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 P2CphCFenhoY for ; Wed, 30 Nov 2011 13:51:17 -0800 (PST) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 81A7211E8081 for ; Wed, 30 Nov 2011 13:51:16 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqkAADuj1k7GmAcF/2dsb2JhbABEhQOVbY8agQiBBYFyAQEBAQMSEQ0EPhMGAQgNBAQBAQMCBgYMCwECAgMBRAcBAQUEAQQTCAEZh22YdoQUiW6RV4EwiFozYwSaOowu X-IronPort-AV: E=Sophos;i="4.71,273,1320642000"; d="scan'208";a="220288959" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 30 Nov 2011 16:51:15 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 30 Nov 2011 16:49:13 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Date: Wed, 30 Nov 2011 22:51:08 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: David Harrington's Discuss on draft-ietf-dime-priority-avps-05: (withDISCUSS and COMMENT) Thread-Index: AcyvinAuHKBwuWciR3+t86HTtKTRFQAH51zQ From: "Romascanu, Dan (Dan)" To: Subject: [Dime] FW: David Harrington's Discuss on draft-ietf-dime-priority-avps-05: (withDISCUSS and COMMENT) 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, 30 Nov 2011 21:51:18 -0000 X-List-Received-Date: Wed, 30 Nov 2011 21:51:18 -0000 RG9jdW1lbnQgZWRpdG9ycyBhbmQgc2hlcGhlcmQsDQoNClBsZWFzZSBhZGRyZXNzIHRoZSBpc3N1 ZXMgcmFpc2VkIGJ5IERhdmlkIGluIGhpcyBESVNDVVNTLiANCg0KVGhhbmtzIGFuZCBSZWdhcmRz LA0KDQpEYW4NCg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpZXNnLWJv dW5jZXNAaWV0Zi5vcmcgW21haWx0bzppZXNnLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBP ZiBEYXZpZCBIYXJyaW5ndG9uDQpTZW50OiBXZWRuZXNkYXksIE5vdmVtYmVyIDMwLCAyMDExIDg6 MDQgUE0NClRvOiBUaGUgSUVTRw0KQ2M6IGRpbWUtY2hhaXJzQHRvb2xzLmlldGYub3JnOyBkcmFm dC1pZXRmLWRpbWUtcHJpb3JpdHktYXZwc0B0b29scy5pZXRmLm9yZw0KU3ViamVjdDogRGF2aWQg SGFycmluZ3RvbidzIERpc2N1c3Mgb24gZHJhZnQtaWV0Zi1kaW1lLXByaW9yaXR5LWF2cHMtMDU6 ICh3aXRoRElTQ1VTUyBhbmQgQ09NTUVOVCkNCg0KRGF2aWQgSGFycmluZ3RvbiBoYXMgZW50ZXJl ZCB0aGUgZm9sbG93aW5nIGJhbGxvdCBwb3NpdGlvbiBmb3INCmRyYWZ0LWlldGYtZGltZS1wcmlv cml0eS1hdnBzLTA1OiBEaXNjdXNzDQoNCldoZW4gcmVzcG9uZGluZywgcGxlYXNlIGtlZXAgdGhl IHN1YmplY3QgbGluZSBpbnRhY3QgYW5kIHJlcGx5IHRvIGFsbA0KZW1haWwgYWRkcmVzc2VzIGlu Y2x1ZGVkIGluIHRoZSBUbyBhbmQgQ0MgbGluZXMuIChGZWVsIGZyZWUgdG8gY3V0IHRoaXMNCmlu dHJvZHVjdG9yeSBwYXJhZ3JhcGgsIGhvd2V2ZXIuKQ0KDQpQbGVhc2UgcmVmZXIgdG8gaHR0cDov L3d3dy5pZXRmLm9yZy9pZXNnL3N0YXRlbWVudC9kaXNjdXNzLWNyaXRlcmlhLmh0bWwNCmZvciBt b3JlIGluZm9ybWF0aW9uIGFib3V0IElFU0cgRElTQ1VTUyBhbmQgQ09NTUVOVCBwb3NpdGlvbnMu DQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpESVNDVVNTOg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoxKSBUaGUg SW50cm9kdWN0aW9uIHNheXMgIlRoZSBpbmZsdWVuY2UgYXR0cmlidXRlZCB0byBwcmlvcml0aXph dGlvbiBtYXkgYWxzbyBhZmZlY3QgUW9TLCBidXQgaXQNCiAgIGlzIG5vdCB0byBiZSBjb25mdXNl ZCB3aXRoIFFvUy4iIGJ1dCBzZWN0aW9uIDQgcmVjb3JkcyB0aGlzIGluIHRoZSBJQU5BIFFvUyBQ cm9maWxlIHJlZ2lzdHJ5LCBhbmQgc2VjdGlvbiA1IHNheXMgdGhpcyBkb2N1bWVudHMgZGVzY3Jp YmVzIGFuIGV4dGVuc2lvbiBmb3IgY29udmV5aW5nIFFvUyBpbmZvcm1hdGlvbi4gRG9lc24ndCB0 aGlzIGNvbmZ1c2UgcHJpb3JpdGl6YXRpb24gd2l0aCBRb1M/DQoNCjIpIEkgYW0gdW5jbGVhciBv biB0aGUgcmVsYXRpb24gYmV0d2VlbiAzR1BQLWRlZmluZWQgQVZQcyBhbmQgdGhlIEFWUHMgZGVm aW5lZCBoZXJlLiBUaGUgbGFzdCBwYXJhZ3JhcGggb2YgMS4xIHNheXMgdGhlIDNHUFAgd29yayBp cyBub3QgcmVsZXZhbnQgdG8gdGhlIGN1cnJlbnQgZG9jdW1lbnQ7IHRoZW4gd2h5IG1lbnRpb24g aXQ/IEkgdGhpbmsgaXQgaXMgcmVsZXZhbnQgaW4gdGhhdCBpdCBpbXBhY3RzIHByaW9yaXRpemF0 aW9uLCBidXQgdGhlIDNHUFAgcHJpb3JpdGl6YXRpb24gaXMgbGltaXRlZCB0byB3aXRoaW4gYSB3 YWxsZWQgZ2FyZGVuLiBZb3UgZG9uJ3Qgc2F5IHNvLCBidXQgSSBhc3N1bWUgdGhpcyBtZWFucyB0 aGUgQVZQcyBkZWZpbmVkIGluIHRoaXMgZG9jdW1lbnQgZG8gTk9UIG9wZXJhdGUgaW4gYSB3YWxs ZWQgZ2FyZGVuLiBEbyB0aGUgRVRTSSBBVlBzIGFsc28gb3BlcmF0ZSBpbiBhIHdhbGxlZCBnYXJk ZW4/IEkgc3VnZ2VzdCB0aGF0IHRoaXMgc2hvdWxkIGJlIG1hZGUgY2xlYXJlciBieSBzcGVjaWZ5 aW5nIG1vcmUgY2xlYXJseSB0aGUgaW50ZW5kZWQgc2NvcGUgb2YgdGhlIEVUU0ksIDNHUFAsIGFu ZCBJRVRGIEFWUHMuDQoNCjMpIEkgdGhpbmsgYW4gaW1wb3J0YW50IG1pc3NpbmcgZWxlbWVudCBo ZXJlIGlzIHRoZSBpbXBhY3QgdGhlc2UgZGlmZmVyZW50IHNjb3BlcyBoYXZlIG9uIG9wZXJhdGlv bmFsIGNvbnNpZGVyYXRpb25zLiBXaGF0IGRvZXMgYW4gb3BlcmF0b3IgbmVlZCB0byBrbm93IGFi b3V0IHRoZSBwcmlvcml0aXphdGlvbiBjYXVzZWQgYnkgdGhlc2UgQVZQcyBmcm9tIGRpZmZlcmVu dCBTRE9zLCBhbmQgaG93IGRvIHRoZXkgaW50ZXJhY3QgaWYgbXVsdGlwbGUgdHlwZXMgb2YgcHJp b3JpdGl6YXRpb24gaXMgcHJlc2VudD8gV2hpY2ggb25lcyB0YWtlIHByZWNlZGVuY2UsIGFzc3Vt aW5nIGNvbXBhcmFibGUgdmFsdWVzIG9mIHByaW9yaXRpemF0aW9uPw0KDQo0KSBUaGUgM0dQUCBp cyBzdXBwb3NlZCB0byBiZSBmb3IgdXNlIGluIGEgd2FsbGVkIGdhcmRlbjsgd2hhdCBoYXBwZW5z IGlmIGl0ICJlc2NhcGVzIGludG8gdGhlIHdpbGQiPyBJcyB0aGVyZSBhbnl0aGluZyBhbiBvcGVy YXRvciBjYW4vc2hvdWxkIGRvIHRvIG1ha2Ugc3VyZSB0aGlzIGRvZXNuJ3QgaGFwcGVuLCBzdWNo IGFzIGNvbmZpZ3VyaW5nIGEgZmlyZXdhbGwgdG8gcHJldmVudCB0aGUgQVZQcyBmcm9tIGNyb3Nz aW5nIG5ldHdvcmsgYm91bmRhcmllcz8NCg0KNSkgcHJpb3JpdGl6YXRpb24gbWlnaHQgYWZmZWN0 IFFvUy4gV2hhdCBzb3J0IG9mIG9wZXJhdGlvbmFsIGltcGFjdCBtaWdodCB0aGlzIGhhdmUsIGlm IHNvbWUgdHJhZmZpYyBwcmlvcml0aXplZCBieSwgZm9yIGV4YW1wbGUsIGEgZGlmZnNlcnYgY29k ZXBvaW50IGlzIG92ZXJyaWRkZW4gYnkgYW4gQVZQPyBBcmUgdGhlcmUgY2VydGFpbiB0eXBlcyBv ZiB0cmFmZmljIHRoYXQgb3BlcmF0b3JzIHNob3VsZCBtYWtlIHN1cmUgQVZQcyBkbyBub3Qgb3Zl cnJpZGUgdGhlIHByb3RvY29sLWRlZmluZWQgUW9TPw0KDQo2KSBXaGF0IGlzIHRoZSBwZXJzaXN0 ZW5jZSBvZiB0aGVzZSBBVlAgc2V0dGluZ3M/IERvIHRoZXNlIEFWUHMgb25seSBhZmZlY3QgdGhl IGN1cnJlbnQgc2Vzc2lvbiwgYW5kIHRoZSBBVlAtZHJpdmVuIHByaW9yaXRpemF0aW9uIGlzIHJl bW92ZWQgd2hlbiB0aGUgYXV0aG9yaXplZCBzZXNzaW9uIGVuZHMsIG9yIGRvZXMgdGhlIEFWUC1k cml2ZW4gcHJpb3JpdGl6YXRpb24gY29udGludWUgYWZ0ZXIgdGhlIGN1cnJlbnQgc2Vzc2lvbiBj bG9zZXM/DQoNCjcpIGluIDMuMSwgcGFzc2l2ZSB2b2NpZSBpcyB1c2VkIHRvIHN0YXRlICJEZWZl bmRpbmctcHJpb3JpdHkgaXMgc2V0IHdoZW4gdGhlIHJlc2VydmF0aW9uIGhhcyBiZWVuIGFkbWl0 dGVkLiIgVGhhdCBpcyBhIGJpdCBhbWJpZ3VvdXMgdG8gbWUuIERvIEkgdW5kZXJzdGFuZCBjb3Jy ZWN0bHkgdGhhdCB0aGUgZGVmZW5kaW5nLXByaW9yaXR5IEFWUCBpcyAqKnNldCoqIGJ5IHRoZSBj bGllbnQgaW4gdGhlIHJlcXVlc3QgbWVzc2FnZSAgYmVmb3JlIGFkbWlzc2lvbiwgYnV0IHRoZSBw cmlvcml0aXphdGlvbiBpcyBvbmx5ICoqc2V0KiogYnkgdGhlIE5BUyBpbiBpdHMgaW50ZXJuYWwg ZW5mb3JjZW1lbnQgY2FsY3VsYXRpb25zIHdoZW4gdGhlIHNlc3Npb24gaXMgYWRtaXR0ZWQ/IENh biB0aGUgdGV4dCBjbGFyaWZ5IHdobyB0aGUgYWN0b3JzIGFyZSwgYW5kIHdoZW4gYW5kIHdoYXQg ZWFjaCBvZiB0aGVtIHNldHM/DQoNCjgpIGluIDMuMS4xLCAidmFsdWUgdGhhdCB3b3VsZCBiZSBl bmNvZGVkIGluIHRoZSBzaWduYWxlZCAuLi4gZWxlbWVudC4iIGVuY29kZWQgaW4gd2hhdCBtZXNz YWdlPw0Kd2hlcmUgaXMgdGhpcyBwb2xpY3kgZWxlbWVudCBlbmNvZGVkPyBDYW4geW91IHByb3Zp ZGUgYSByZWZlcmVuY2U/DQoNCjkpIGluIDMuMiwgIlRoZSBhZG1pc3Npb24gcHJpb3JpdHkgb2Yg dGhlIGZsb3cgaXMgdXNlZCB0byBpbmNyZWFzZSB0aGUgcHJvYmFiaWxpdHkgb2YNCiAgIHNlc3Np b24gZXN0YWJsaXNobWVudCBmb3Igc2VsZWN0ZWQgZmxvd3MuIiBJIGRvbid0IHVuZGVyc3RhbmQg dGhlIHJlbGF0aW9uc2hpcCBiZXR3ZWVuICJ0aGUgZmxvdyIgYW5kICJzZWxlY3RlZCBmbG93cyIs IGFuZCB0aGUgcmVsYXRpb25zaGlwIGJldHdlZW4gdGhlc2UgZmxvd3MgYW5kIEFBQSBzZXNzaW9u cy4gSXMgInRoZSBmbG93IiB0aGUgQUFBLWF1dGhvcml6ZWQgc2Vzc2lvbiBmbG93PyBBcmUgdGhl ICJzZWxlY3RlZCBmbG93cyIgaW4gdGhlIHNhbWUgYXV0aG9yaXplZCBzZXNzaW9uPyBvciBkb2Vz IHRoaXMgQVZQIGFmZmZlY3QgZmxvd3MgaW4gb3RoZXIgQUFBLXNlc3Npb25zPyBJcyB0aGUgYWRt aXNzaW9uIHByaW9yaXR5IG9mIHRoZSBmbG93IHJlZmVyaW5nIHRvIHRoZSBhZG1pc3Npb24tcHJp b2lydHktQVZQLCBvciB0aGUgYWRtaXNzaW9uLXByaW9yaXR5IHBhcmFtZXRlciB0aGF0IHRoZSBB VlAgbW9kZWxzPyANCg0KDQoNCg0KDQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpDT01NRU5UOg0KLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLQ0KDQoxKSBJIGFncmVlIHdpdGggb3RoZXIgY29tbWVudHMgYWJvdXQgdGhlIGNv bmZ1c2lvbiBzdXJyb3VkaW5nIGludGVncml0eS1wcm90ZWN0ZWQgdmFsdWVzLg0KDQoyKSBUaGUg c2Vjb25kIHBhcmFncmFwaCBvZiBzZWN0aW9uIDUgc2F5cyAiVXNlIC4uIE1VU1QgdGFrZSBpbnRv IGNvbnNpZGVyYXRpb24gLi4uIiBJIHRoaW5rIHRoaXMgaXMgYW4gaW5jb3JyZWN0IHVzYWdlIGZv ciBNVVNUOyBNVVNUIGlzIGZvciBpbXBsZW1lbnRlcnMuIChTaW5jZSBhbiBvcGVyYXRvciBtaWdo dCBjaG9vc2UgdG8gTk9UIGNvbnNpZGVyIHRoZSBpc3N1ZXMgYW5kIHNlY3VyaXR5IG9mIERpYW1l dGVyIGJhc2UsIHRoaXMgZG9jdW1lbnQgc2hvdWxkIHdhcm4gdXNlcnMgd2hhdCB2dWxuZXJhYmls aXRpZXMgbWlnaHQgZXhpc3QgaW4gdGhlaXIgbmV0d29yayBpZiBhbm90aGVyIG9wZXJhdG9yIGln bm9yZXMgdGhlc2UgaXNzdWVzLikNCg0KMykgSW4gYWNrbm93bGVkZ2VtZW50cywgeW91IGNyZWRp dCBhIG51bWJlciBvZiBwZW9wbGUgd2l0aCByZXNvbHZpbmcgdGhlICJwcm9ibGVtcyIsIGJ1dCBk b24ndCBtZW50aW9uIHdoYXQgcHJvYmxlbXMgdGhvc2Ugd2VyZS4gDQoNCg0K From bill.wu@huawei.com Wed Nov 30 18:29: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 0AA9A21F84DA for ; Wed, 30 Nov 2011 18:29:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.372 X-Spam-Level: X-Spam-Status: No, score=-6.372 tagged_above=-999 required=5 tests=[AWL=0.227, 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 e7BFWTGS1NUn for ; Wed, 30 Nov 2011 18:29:18 -0800 (PST) Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id D40D221F84D6 for ; Wed, 30 Nov 2011 18:29:17 -0800 (PST) Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVI00GCH6WKXL@szxga05-in.huawei.com> for dime@ietf.org; Thu, 01 Dec 2011 10:29:09 +0800 (CST) Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVI00GVB6WIXF@szxga05-in.huawei.com> for dime@ietf.org; Thu, 01 Dec 2011 10:29:08 +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 AFJ07451; Thu, 01 Dec 2011 10:29:08 +0800 Received: from SZXEML421-HUB.china.huawei.com (10.82.67.160) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 01 Dec 2011 10:29:02 +0800 Received: from w53375q (10.138.41.130) by szxeml421-hub.china.huawei.com (10.82.67.160) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 01 Dec 2011 10:28:59 +0800 Date: Thu, 01 Dec 2011 10:28:57 +0800 From: Qin Wu X-Originating-IP: [10.138.41.130] To: jouni korhonen , dime@ietf.org 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> 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 02:29:19 -0000 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 Tina.Tsou.Zouting@huawei.com Wed Nov 30 19:12: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 3823011E809B for ; Wed, 30 Nov 2011 19:12:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.419 X-Spam-Level: X-Spam-Status: No, score=-6.419 tagged_above=-999 required=5 tests=[AWL=0.180, 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 oPld+fLOYOAu for ; Wed, 30 Nov 2011 19:12:44 -0800 (PST) Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 1AE0611E8094 for ; Wed, 30 Nov 2011 19:12:44 -0800 (PST) Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVI001KJ8VD0Z@szxga03-in.huawei.com> for dime@ietf.org; Thu, 01 Dec 2011 11:11:37 +0800 (CST) Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVI004WF8VDAE@szxga03-in.huawei.com> for dime@ietf.org; Thu, 01 Dec 2011 11:11:37 +0800 (CST) Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AFL71255; Thu, 01 Dec 2011 11:11:21 +0800 Received: from SZXEML424-HUB.china.huawei.com (10.82.67.163) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 01 Dec 2011 11:11:11 +0800 Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.40]) by szxeml424-hub.china.huawei.com ([10.82.67.163]) with mapi id 14.01.0323.003; Thu, 01 Dec 2011 11:10:54 +0800 Date: Thu, 01 Dec 2011 03:10:53 +0000 From: Tina TSOU In-reply-to: To: Qin Wu Message-id: <11DBAD8B-2508-45BF-AB8C-571292213B26@huawei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-language: en-US Content-transfer-encoding: 7BIT Accept-Language: en-US, zh-CN Thread-topic: [Dime] re-chartering Thread-index: AQHMr9D647UgCDS5T0inIWSc5j5FgJXGTgrl X-MS-Has-Attach: X-MS-TNEF-Correlator: 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: Thu, 01 Dec 2011 03:12:45 -0000 Some other candidate wording: Group? Aggregation? Grouping? Compound? Sent from my iPad On Nov 30, 2011, at 6:30 PM, "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 >> > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime