From dromasca@avaya.com Mon Mar 1 02:56:04 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 990133A8544; Mon, 1 Mar 2010 02:56:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.339 X-Spam-Level: X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id euTO4RyijakP; Mon, 1 Mar 2010 02:56:04 -0800 (PST) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 474BB3A6A48; Mon, 1 Mar 2010 02:56:03 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.49,559,1262581200"; d="scan'208";a="178391180" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 01 Mar 2010 05:56:01 -0500 X-IronPort-AV: E=Sophos;i="4.49,559,1262581200"; d="scan'208";a="436806169" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.15]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 01 Mar 2010 05:55:25 -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: Mon, 1 Mar 2010 11:55:09 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: DIME WG chairs - call for candidates Thread-Index: Acq5Lajv13V8FFkURJGg4aCuKY3JCA== From: "Romascanu, Dan (Dan)" To: Cc: ops-area@ietf.org Subject: [Dime] DIME WG chairs - call for candidates X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2010 10:56:04 -0000 Hi, We are facing an interesting situation in the DIME WG. As you know Hannes was nominated and confirmed for an IAB position (congratulations, Hannes!) and expressed his desire to reduce many of his other activities. Victor changed employers and chairing DIME is not supported any longer in his new dayjob position. Thanks to both of them for the great contribution brought to DIME and the IETF.=20 As a result of this situation we need to find one - at least - or two - better - new chair(s) for DIME.=20 This is an open call for candidates. The job requirements include first of all good experience with the Diameter protocol and AAA applications, and management skills. Employer support for assuming the job is mandatory. If you need more information about the requirements and time needed for the job please contact me, Hannes, or Victor. If you want the job and believe that you are qualified for it please contact me.=20 There is no immediate pressure, as Hannes kindly accepted to support the transition period. However, it would be nice if we can solve the WG chairmanship nomination until Anaheim and work on the transition at the meeting.=20 Thanks and Regards, Dan =20 From root@core3.amsl.com Mon Mar 1 09:00:01 2010 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 86F2628C409; Mon, 1 Mar 2010 09:00:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100301170001.86F2628C409@core3.amsl.com> Date: Mon, 1 Mar 2010 09:00:01 -0800 (PST) Cc: dime@ietf.org Subject: [Dime] I-D ACTION:draft-ietf-dime-priority-avps-00.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2010 17:00:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter Priority Attribute Value Pairs Author(s) : K. Carlberg, T. Taylor Filename : draft-ietf-dime-priority-avps-00.txt Pages : 7 Date : 2010-2-28 This document defines Attribute-Value Pair (AVP) containers for various priority parameters for use with Diameter and the AAA framework. The parameters themselves are defined in several different protocols that operate at either the network or application layer. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-priority-avps-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-priority-avps-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-3-1085926.I-D@ietf.org> --NextPart-- From hannes.tschofenig@nsn.com Tue Mar 2 06:02:39 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5209A3A8A08; Tue, 2 Mar 2010 06:02:39 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R11XMyrnDDvN; Tue, 2 Mar 2010 06:02:38 -0800 (PST) Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 2B0AF3A8A1B; Tue, 2 Mar 2010 06:02:37 -0800 (PST) Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o22E2XPW009666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 2 Mar 2010 15:02:33 +0100 Received: from demuexc025.nsn-intra.net (demuexc025.nsn-intra.net [10.159.32.12]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o22E2WWY020986; Tue, 2 Mar 2010 15:02:33 +0100 Received: from FIESEXC015.nsn-intra.net ([10.159.0.23]) by demuexc025.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 2 Mar 2010 15:02:31 +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: Tue, 2 Mar 2010 16:01:54 +0200 Message-ID: <3D3C75174CB95F42AD6BCC56E5555B450242409C@FIESEXC015.nsn-intra.net> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dime] DIME WG chairs - call for candidates Thread-Index: Acq5Lajv13V8FFkURJGg4aCuKY3JCAA4YpuQ References: From: "Tschofenig, Hannes (NSN - FI/Espoo)" To: "ext Romascanu, Dan (Dan)" , X-OriginalArrivalTime: 02 Mar 2010 14:02:31.0929 (UTC) FILETIME=[00833690:01CABA11] Cc: ops-area@ietf.org Subject: Re: [Dime] DIME WG chairs - call for candidates X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2010 14:02:39 -0000 I would like to thank you, Dan, for helping Victor and me with your advices and with your help regarding working group management. You always had time for a chat with us. Since Area Directors are typically highly overloaded with different tasks we highly appreciated your availability.=20 Victor, it was great to do the work together with you! You brought the experience of an open source developer into the group. We need more people like you who have hands-on experience.=20 Big thanks also to everyone in the group for getting the work done. We managed to get a couple of documents published and gained a lot of insights about Diameter and the entire eco-system. I also want to mention the interop events where a number of you participated and clearly demonstrated that Diameter is widely implemented and plenty of good products are available.=20 Ciao Hannes=20 >-----Original Message----- >From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On=20 >Behalf Of ext Romascanu, Dan (Dan) >Sent: 01 March, 2010 12:55 >To: dime@ietf.org >Cc: ops-area@ietf.org >Subject: [Dime] DIME WG chairs - call for candidates > >Hi, > >We are facing an interesting situation in the DIME WG. As you=20 >know Hannes was nominated and confirmed for an IAB position=20 >(congratulations, >Hannes!) and expressed his desire to reduce many of his other=20 >activities. Victor changed employers and chairing DIME is not=20 >supported any longer in his new dayjob position. Thanks to=20 >both of them for the great contribution brought to DIME and the IETF.=20 > >As a result of this situation we need to find one - at least -=20 >or two - better - new chair(s) for DIME.=20 > >This is an open call for candidates. The job requirements=20 >include first of all good experience with the Diameter=20 >protocol and AAA applications, and management skills. Employer=20 >support for assuming the job is mandatory. If you need more=20 >information about the requirements and time needed for the job=20 >please contact me, Hannes, or Victor. If you want the job and=20 >believe that you are qualified for it please contact me.=20 > >There is no immediate pressure, as Hannes kindly accepted to=20 >support the transition period. However, it would be nice if we=20 >can solve the WG chairmanship nomination until Anaheim and=20 >work on the transition at the meeting.=20 > >Thanks and Regards, > >Dan >=20 >_______________________________________________ >DiME mailing list >DiME@ietf.org >https://www.ietf.org/mailman/listinfo/dime > From vf0213@gmail.com Tue Mar 2 06:31:53 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0824F3A8A85; Tue, 2 Mar 2010 06:31:53 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CmAbxmD9XPFD; Tue, 2 Mar 2010 06:31:51 -0800 (PST) Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 51A1A3A8A7A; Tue, 2 Mar 2010 06:31:51 -0800 (PST) Received: by wwb31 with SMTP id 31so159217wwb.31 for ; Tue, 02 Mar 2010 06:31:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=MiLs8aG/jp0u5n24DcZ+uWt/M6ErI8DjMpVMVYl4zIo=; b=SuVTcIzGWAj3g6zIxVqMeG9N9moRgOAcw6/+DxM2Gj5eJnBDsKOeM1Sfon3ivMFkY/ D5a4S9rtfqYCdYNX9CXtl0Ere6of9KtaiyArRNx+irRNTt3CVy2F3ajcYFeLsP16FAAL bgoIaZiuz1EIrC8BmSbv9qVBA4bl9/rAHCwdg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=rllPm5/Rd3CLA20L0plJkaJ65dTRUIWw4rJk8f5ivj6fbd2aG7QvyS/8RvOFJyaT0f pGVVgYj0Bb5S76vxdINCq5fyjz7Fve/qGGSFxPaHcDetzrSRAnH+mJ9jqtzSpYG6zuqE eNzYVSLaVb+yFIrTvqGlcNpwBpeshIoYL6fGQ= MIME-Version: 1.0 Received: by 10.216.90.11 with SMTP id d11mr756574wef.187.1267540307776; Tue, 02 Mar 2010 06:31:47 -0800 (PST) In-Reply-To: <3D3C75174CB95F42AD6BCC56E5555B450242409C@FIESEXC015.nsn-intra.net> References: <3D3C75174CB95F42AD6BCC56E5555B450242409C@FIESEXC015.nsn-intra.net> Date: Tue, 2 Mar 2010 08:31:47 -0600 Message-ID: <919c9f451003020631m633ba542na6aedd110f155c4e@mail.gmail.com> From: Victor Fajardo To: "Tschofenig, Hannes (NSN - FI/Espoo)" Content-Type: multipart/alternative; boundary=0016e6d56689c8953f0480d23951 Cc: dime@ietf.org, ops-area@ietf.org Subject: Re: [Dime] DIME WG chairs - call for candidates X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2010 14:31:53 -0000 --0016e6d56689c8953f0480d23951 Content-Type: text/plain; charset=ISO-8859-1 I would like to extend my thanks to Dan and Hannes for their support through the years I was involved with DIME. Dan, you have always been very supportive of us despite the varied things you had to deal with. Your time and the attention you gave is greatly appreciated. Hannes, it has been a great working with you. I'm truly appreciative of everything you have done for the group. Without you, I think we would have not progress as much as we did. Congratulations and I wish you well on your new post. I'm sure you'll do great. Many thanks to everyone in the group. Whoever continues as chair, I think they will be very lucky to have a set of very talented DIME folks to work with. It's been a pleasure working with everyone. Best regards, Victor On Tue, Mar 2, 2010 at 8:01 AM, Tschofenig, Hannes (NSN - FI/Espoo) < hannes.tschofenig@nsn.com> wrote: > I would like to thank you, Dan, for helping Victor and me with your > advices and with your help regarding working group management. You > always had time for a chat with us. Since Area Directors are typically > highly overloaded with different tasks we highly appreciated your > availability. > > Victor, it was great to do the work together with you! You brought the > experience of an open source developer into the group. We need more > people like you who have hands-on experience. > > Big thanks also to everyone in the group for getting the work done. We > managed to get a couple of documents published and gained a lot of > insights about Diameter and the entire eco-system. I also want to > mention the interop events where a number of you participated and > clearly demonstrated that Diameter is widely implemented and plenty of > good products are available. > > Ciao > Hannes > > >-----Original Message----- > >From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On > >Behalf Of ext Romascanu, Dan (Dan) > >Sent: 01 March, 2010 12:55 > >To: dime@ietf.org > >Cc: ops-area@ietf.org > >Subject: [Dime] DIME WG chairs - call for candidates > > > >Hi, > > > >We are facing an interesting situation in the DIME WG. As you > >know Hannes was nominated and confirmed for an IAB position > >(congratulations, > >Hannes!) and expressed his desire to reduce many of his other > >activities. Victor changed employers and chairing DIME is not > >supported any longer in his new dayjob position. Thanks to > >both of them for the great contribution brought to DIME and the IETF. > > > >As a result of this situation we need to find one - at least - > >or two - better - new chair(s) for DIME. > > > >This is an open call for candidates. The job requirements > >include first of all good experience with the Diameter > >protocol and AAA applications, and management skills. Employer > >support for assuming the job is mandatory. If you need more > >information about the requirements and time needed for the job > >please contact me, Hannes, or Victor. If you want the job and > >believe that you are qualified for it please contact me. > > > >There is no immediate pressure, as Hannes kindly accepted to > >support the transition period. However, it would be nice if we > >can solve the WG chairmanship nomination until Anaheim and > >work on the transition at the meeting. > > > >Thanks and Regards, > > > >Dan > > > >_______________________________________________ > >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 > --0016e6d56689c8953f0480d23951 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I would like to extend my thanks to Dan and Hannes for their support throug= h the years I was involved with DIME. Dan, you have always been very suppor= tive of us despite the varied things you had to deal with. Your time and th= e attention you gave is greatly appreciated.

Hannes, it has been a great working with you. I'm truly appreciativ= e of everything you have done for the group. Without you, I think we would = have not progress as much as we did. Congratulations and I wish you well on= your new post. I'm sure you'll do great.

Many thanks to everyone in the group. Whoever continues as chair, I thi= nk they will be very lucky to have a set of very talented DIME folks to wor= k with. It's been a pleasure working with everyone.

Best regard= s,
Victor


On Tue, Mar 2, 2010 at 8:01 AM= , Tschofenig, Hannes (NSN - FI/Espoo) <hannes.tschofenig@nsn.com> wrot= e:
I would like to t= hank you, Dan, for helping Victor and me with your
advices and with your help regarding working group management. You
always had time for a chat with us. Since Area Directors are typically
highly overloaded with different tasks we highly appreciated your
availability.

Victor, it was great to do the work together with you! You brought the
experience of an open source developer into the group. We need more
people like you who have hands-on experience.

Big thanks also to everyone in the group for getting the work done. We
managed to get a couple of documents published and gained a lot of
insights about Diameter and the entire eco-system. I also want to
mention the interop events where a number of you participated and
clearly demonstrated that Diameter is widely implemented and plenty of
good products are available.

Ciao
Hannes

>-----Original Message-----
>From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On
>Behalf Of ext Romascanu, Dan (Dan)
>Sent: 01 March, 2010 12:55
>To: dime@ietf.org
>Cc: ops-area@ietf.org
>Subject: [Dime] DIME WG chairs - call for candidates
>
>Hi,
>
>We are facing an interesting situation in the DIME WG. As you
>know Hannes was nominated and confirmed for an IAB position
>(congratulations,
>Hannes!) and expressed his desire to reduce many of his other
>activities. Victor changed employers and chairing DIME is not
>supported any longer in his new dayjob position. Thanks to
>both of them for the great contribution brought to DIME and the IETF. >
>As a result of this situation we need to find one - at least -
>or two - better - new chair(s) for DIME.
>
>This is an open call for candidates. The job requirements
>include first of all good experience with the Diameter
>protocol and AAA applications, and management skills. Employer
>support for assuming the job is mandatory. If you need more
>information about the requirements and time needed for the job
>please contact me, Hannes, or Victor. If you want the job and
>believe that you are qualified for it please contact me.
>
>There is no immediate pressure, as Hannes kindly accepted to
>support the transition period. However, it would be nice if we
>can solve the WG chairmanship nomination until Anaheim and
>work on the transition at the meeting.
>
>Thanks and Regards,
>
>Dan
>
>_______________________________________________
>DiME mailing list
>DiME@ietf.org
>https://www.ietf.org/mailman/listinfo/dime
>
_______________________________________________
DiME mailing list
DiME@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/dime

--0016e6d56689c8953f0480d23951-- From Hannes.Tschofenig@gmx.net Tue Mar 2 09:45:24 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A18A728C1FC for ; Tue, 2 Mar 2010 09:45:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.297 X-Spam-Level: X-Spam-Status: No, score=-2.297 tagged_above=-999 required=5 tests=[AWL=0.302, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ajHjNKdSZxln for ; Tue, 2 Mar 2010 09:45:24 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id DD43128C133 for ; Tue, 2 Mar 2010 09:45:21 -0800 (PST) Received: (qmail invoked by alias); 02 Mar 2010 17:45:22 -0000 Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.255.4]) [88.115.222.204] by mail.gmx.net (mp069) with SMTP; 02 Mar 2010 18:45:22 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX1+hMAsNuYOhRJjy43oCXVKul88kGEN5dn1/nCEtcT XOcHLdqVKXoLhB Message-ID: <4B8D4E8A.6080602@gmx.net> Date: Tue, 02 Mar 2010 19:44:42 +0200 From: Hannes Tschofenig User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: "dime@ietf.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.68999999999999995 Subject: [Dime] WGLC for draft-ietf-dime-priority-avps-00.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2010 17:45:24 -0000 Hi all, since the Diameter Priority Attribute Value Pairs document is very short I would suggest to start the working group last call now already. Here is a pointer to the document: http://www.ietf.org/id/draft-ietf-dime-priority-avps-00.txt This WGLC will end on the 16th March 2010. Ciao Hannes & Victor From Hannes.Tschofenig@gmx.net Wed Mar 3 12:12:59 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9AB028C22E for ; Wed, 3 Mar 2010 12:12:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.426 X-Spam-Level: X-Spam-Status: No, score=-2.426 tagged_above=-999 required=5 tests=[AWL=0.172, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H8qS1f8dYWS5 for ; Wed, 3 Mar 2010 12:12:55 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 7F59E28C241 for ; Wed, 3 Mar 2010 12:12:44 -0800 (PST) Received: (qmail invoked by alias); 03 Mar 2010 20:12:29 -0000 Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.255.4]) [88.115.222.204] by mail.gmx.net (mp070) with SMTP; 03 Mar 2010 21:12:29 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX19jAHgeMNhjeL+kKa+2MonfpiqwHvQULpBrqeEnRW 8QzG+J1shwuIql Message-ID: <4B8EC288.1040001@gmx.net> Date: Wed, 03 Mar 2010 22:11:52 +0200 From: Hannes Tschofenig User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: "dime@ietf.org" Content-Type: multipart/alternative; boundary="------------000308060407090803020505" X-Y-GMX-Trusted: 0 X-FuHaFi: 0.53000000000000003,0.55000000000000004 Subject: [Dime] DIME Agenda (Version 1) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2010 20:12:59 -0000 This is a multi-part message in MIME format. --------------000308060407090803020505 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit This is what I got so far: THURSDAY, March 25, 2010 *0900-1130 Morning Session I* Room: Palos Verdes * Agenda Bashing and Status Update (Chairs) * Diameter NAT Control Application (Frank) I did not receive further agenda requests! I do, however, believe it makes sense to talk about: Diameter Support for EAP Re-authentication Protocol (ERP) Realm-Based Redirection In Diameter Diameter Extended NAPTR Diameter IKEv2: Support for Interaction between IKEv2 Server and Diameter Server Diameter Support for Proxy Mobile IPv6 Localized Routing Diameter Priority Attribute Value Pairs (maybe, if not finished by this time) I hope to hear something from other draft authors. Ciao Hannes --------------000308060407090803020505 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit This is what I got so far:

THURSDAY, March 25, 2010

0900-1130 Morning Session I

Room: Palos Verdes

* Agenda Bashing and Status Update (Chairs)
* Diameter NAT Control Application (Frank)


I did not receive further agenda requests!


I do, however, believe it makes sense to talk about:

Diameter Support for EAP Re-authentication Protocol (ERP)
Realm-Based Redirection In Diameter
Diameter Extended NAPTR
Diameter IKEv2: Support for Interaction between IKEv2 Server and Diameter Server
Diameter Support for Proxy Mobile IPv6 Localized Routing
Diameter Priority Attribute Value Pairs (maybe, if not finished by this time)

I hope to hear something from other draft authors.

Ciao
Hannes


--------------000308060407090803020505-- From jouni.nospam@gmail.com Wed Mar 3 14:48:59 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA24C3A8CF0 for ; Wed, 3 Mar 2010 14:48:59 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KkLwan5ZCZq3 for ; Wed, 3 Mar 2010 14:48:59 -0800 (PST) Received: from mail-fx0-f213.google.com (mail-fx0-f213.google.com [209.85.220.213]) by core3.amsl.com (Postfix) with ESMTP id BBC253A8BBE for ; Wed, 3 Mar 2010 14:48:58 -0800 (PST) Received: by fxm5 with SMTP id 5so2107669fxm.29 for ; Wed, 03 Mar 2010 14:48:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=+loVrpsEC5ZJyyLUjb2tyjPuTAV+WZ4xHM9Se0qaSQQ=; b=ADqBiPZCX5qm3I0OfXWVC79IlJ9NXAmEdCcypztVTYJ4e1veblBTMxuIpjcUYuirco ILAfU7WM7DY3/oveAVA2od1npeETw7/UGgk5KiN29l/ddQEVeP77qKZhBXpZO3g0Iqlk 5UKALg0zbjKgEToVs3+2zrvKCB9YS6Xv49DJM= DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=MdDMtArdUPGTYMbqxYkLzmobekr0EXP596k9SdH5HGAklkFY601I3rESUML9QoT0ko v7CZkNAcTFpFJeHWrXPbBI2Xs1sZgxdc2VrGtfIcWdEXFVMQ7GvfnX2PlV9Kb+Uw3gn3 OgeGTeOJPLEFS0jBdT+pJgFmFQQtvzZho5Fp0= Received: by 10.223.75.155 with SMTP id y27mr765075faj.79.1267656536838; Wed, 03 Mar 2010 14:48:56 -0800 (PST) Received: from a88-112-207-124.elisa-laajakaista.fi (a88-112-207-124.elisa-laajakaista.fi [88.112.207.124]) by mx.google.com with ESMTPS id 22sm10065131fkr.59.2010.03.03.14.48.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 03 Mar 2010 14:48:56 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: <4B8EC288.1040001@gmx.net> Date: Thu, 4 Mar 2010 00:48:55 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <8BBBE271-DF25-4D3F-9083-BA60905FB9F7@gmail.com> References: <4B8EC288.1040001@gmx.net> To: Hannes Tschofenig X-Mailer: Apple Mail (2.1077) Cc: "dime@ietf.org" Subject: Re: [Dime] DIME Agenda (Version 1) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2010 22:48:59 -0000 We can give a brief update on extended NAPTR. 10mins should be ok. - Jouni On Mar 3, 2010, at 10:11 PM, Hannes Tschofenig wrote: > This is what I got so far: >=20 > THURSDAY, March 25, 2010 >=20 > 0900-1130 Morning Session I > Room: Palos Verdes=20 >=20 > * Agenda Bashing and Status Update (Chairs) > * Diameter NAT Control Application (Frank) >=20 >=20 > I did not receive further agenda requests! >=20 >=20 > I do, however, believe it makes sense to talk about:=20 >=20 > Diameter Support for EAP Re-authentication Protocol (ERP)=20 > Realm-Based Redirection In Diameter=20 > Diameter Extended NAPTR=20 > Diameter IKEv2: Support for Interaction between IKEv2 Server and = Diameter Server=20 > Diameter Support for Proxy Mobile IPv6 Localized Routing=20 > Diameter Priority Attribute Value Pairs (maybe, if not finished by = this time) >=20 > I hope to hear something from other draft authors.=20 >=20 > Ciao > Hannes >=20 >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From root@core3.amsl.com Wed Mar 3 17:00:01 2010 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id EEC3328C0DC; Wed, 3 Mar 2010 17:00:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100304010001.EEC3328C0DC@core3.amsl.com> Date: Wed, 3 Mar 2010 17:00:01 -0800 (PST) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-local-keytran-02.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2010 01:00:02 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter Attribute-Value Pairs for Cryptographic Key Transport Author(s) : G. Zorn, et al. Filename : draft-ietf-dime-local-keytran-02.txt Pages : 8 Date : 2010-03-03 Some Authentication, Authorization, and Accounting (AAA) applications require the transport of cryptographic keying material; this document specifies a set of Attribute-Value Pairs (AVPs) providing native Diameter support of cryptographic key delivery. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-local-keytran-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-local-keytran-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-03-03165100.I-D@ietf.org> --NextPart-- From sdecugis@nict.go.jp Wed Mar 3 17:20:51 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD1FE28C1D7 for ; Wed, 3 Mar 2010 17:20:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.355 X-Spam-Level: X-Spam-Status: No, score=-1.355 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AvHkZynSPl9g for ; Wed, 3 Mar 2010 17:20:46 -0800 (PST) Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:2f8:29::2]) by core3.amsl.com (Postfix) with ESMTP id 077E83A7C0A for ; Wed, 3 Mar 2010 17:20:42 -0800 (PST) Received: from gw1.nict.go.jp (gw1 [133.243.18.250]) by ns1.nict.go.jp with ESMTP id o241KhhJ027068 for ; Thu, 4 Mar 2010 10:20:43 +0900 (JST) Received: from gw1.nict.go.jp (localhost [127.0.0.1]) by gw1.nict.go.jp with ESMTP id o241KgFN001486 for ; Thu, 4 Mar 2010 10:20:42 +0900 (JST) Received: from mail2.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw1.nict.go.jp with ESMTP id o241KguB001483 for ; Thu, 4 Mar 2010 10:20:42 +0900 (JST) Received: from mail2.nict.go.jp (localhost [127.0.0.1]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 4975D16238 for ; Thu, 4 Mar 2010 10:20:42 +0900 (JST) Received: from [133.243.146.178] (5gou2f-dhcp18.nict.go.jp [133.243.146.178]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 4590F15FEA for ; Thu, 4 Mar 2010 10:20:42 +0900 (JST) Message-ID: <4B8F0ADB.2040009@nict.go.jp> Date: Thu, 04 Mar 2010 10:20:27 +0900 From: Sebastien Decugis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 MIME-Version: 1.0 To: dime@ietf.org References: <4B8EC288.1040001@gmx.net> In-Reply-To: <4B8EC288.1040001@gmx.net> X-Enigmail-Version: 1.0.1 OpenPGP: id=33D9F61D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: [Dime] DIME Agenda (Version 1) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2010 01:20:56 -0000 We'll probably have something to say about Diameter ERP as well, although I am not sure what it will be at this point :) Sebastien. Le 04/03/2010 05:11, Hannes Tschofenig a écrit : > This is what I got so far: > > > THURSDAY, March 25, 2010 > > > *0900-1130 Morning Session I* > > Room: Palos Verdes > > > * Agenda Bashing and Status Update (Chairs) > * Diameter NAT Control Application > (Frank) > > > I did not receive further agenda requests! > > > I do, however, believe it makes sense to talk about: > > Diameter Support for EAP Re-authentication Protocol (ERP) > > Realm-Based Redirection In Diameter > > Diameter Extended NAPTR > > Diameter IKEv2: Support for Interaction between IKEv2 Server and > Diameter Server > > Diameter Support for Proxy Mobile IPv6 Localized Routing > > Diameter Priority Attribute Value Pairs > (maybe, > if not finished by this time) > > I hope to hear something from other draft authors. > > Ciao > Hannes > > > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime > -- Sebastien Decugis Research fellow Network Architecture Group NICT (nict.go.jp) From sunseawq@huawei.com Wed Mar 3 17:48:55 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D56F33A8A04 for ; Wed, 3 Mar 2010 17:48:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.757 X-Spam-Level: X-Spam-Status: No, score=-0.757 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v11vcpetEcpg for ; Wed, 3 Mar 2010 17:48:55 -0800 (PST) Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 8B2743A8A10 for ; Wed, 3 Mar 2010 17:48:54 -0800 (PST) Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYQ007ZQID96S@szxga02-in.huawei.com> for dime@ietf.org; Thu, 04 Mar 2010 09:48:45 +0800 (CST) Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYQ004NPID9OD@szxga02-in.huawei.com> for dime@ietf.org; Thu, 04 Mar 2010 09:48:45 +0800 (CST) Received: from w53375 ([10.164.12.38]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KYQ00EROID87O@szxml04-in.huawei.com> for dime@ietf.org; Thu, 04 Mar 2010 09:48:45 +0800 (CST) Date: Thu, 04 Mar 2010 09:48:45 +0800 From: Qin Wu To: Hannes Tschofenig , dime@ietf.org Message-id: <00a201cabb3c$d3f178d0$260ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3598 Content-type: multipart/alternative; boundary="Boundary_(ID_3dj0d0r6WYafkunsmlvHWQ)" X-Priority: 3 X-MSMail-priority: Normal References: <4B8EC288.1040001@gmx.net> Subject: Re: [Dime] DIME Agenda (Version 1) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2010 01:48:55 -0000 This is a multi-part message in MIME format. --Boundary_(ID_3dj0d0r6WYafkunsmlvHWQ) Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Yes, we need a timeslot to discuss Diameter Support for Proxy Mobile IPv6 Localized Routing. Also we would like to request one more tiny timeslot to talk about Diameter Attribute-Value Pairs for Cryptographic Key Transport to address the comments in the WGLC. Regards! -Qin ----- Original Message ----- From: Hannes Tschofenig To: dime@ietf.org Sent: Thursday, March 04, 2010 4:11 AM Subject: [Dime] DIME Agenda (Version 1) This is what I got so far: THURSDAY, March 25, 2010 0900-1130 Morning Session I Room: Palos Verdes * Agenda Bashing and Status Update (Chairs) * Diameter NAT Control Application (Frank) I did not receive further agenda requests! I do, however, believe it makes sense to talk about: Diameter Support for EAP Re-authentication Protocol (ERP) Realm-Based Redirection In Diameter Diameter Extended NAPTR Diameter IKEv2: Support for Interaction between IKEv2 Server and Diameter Server Diameter Support for Proxy Mobile IPv6 Localized Routing Diameter Priority Attribute Value Pairs (maybe, if not finished by this time) I hope to hear something from other draft authors. Ciao Hannes ------------------------------------------------------------------------------ _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime --Boundary_(ID_3dj0d0r6WYafkunsmlvHWQ) Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT
Yes, we need a timeslot to discuss Diameter Support for Proxy Mobile IPv6 Localized Routing.
Also we would like to request one more tiny timeslot to talk about Diameter Attribute-Value Pairs for Cryptographic Key Transport
to address the comments in the WGLC.
 
Regards!
-Qin
----- Original Message -----
Sent: Thursday, March 04, 2010 4:11 AM
Subject: [Dime] DIME Agenda (Version 1)

This is what I got so far:

THURSDAY, March 25, 2010

0900-1130 Morning Session I

Room: Palos Verdes

* Agenda Bashing and Status Update (Chairs)
* Diameter NAT Control Application (Frank)


I did not receive further agenda requests!


I do, however, believe it makes sense to talk about:

Diameter Support for EAP Re-authentication Protocol (ERP)
Realm-Based Redirection In Diameter
Diameter Extended NAPTR
Diameter IKEv2: Support for Interaction between IKEv2 Server and Diameter Server
Diameter Support for Proxy Mobile IPv6 Localized Routing
Diameter Priority Attribute Value Pairs (maybe, if not finished by this time)

I hope to hear something from other draft authors.

Ciao
Hannes


_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime
--Boundary_(ID_3dj0d0r6WYafkunsmlvHWQ)-- From root@core3.amsl.com Sat Mar 6 00:45:01 2010 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 891BE3A8D58; Sat, 6 Mar 2010 00:45:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100306084501.891BE3A8D58@core3.amsl.com> Date: Sat, 6 Mar 2010 00:45:01 -0800 (PST) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-app-design-guide-10.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2010 08:45:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter Applications Design Guidelines Author(s) : V. Fajardo, H. Tschofenig Filename : draft-ietf-dime-app-design-guide-10.txt Pages : 26 Date : 2010-03-06 The Diameter Base protocol provides updated rules on how to extend Diameter by modifying and/or deriving from existing applications or creating entirely new applications. This is a companion document to the Diameter Base protocol that further explains and clarifies these rules. It is meant as a guidelines document and therefore it does not add, remove or change existing rules. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-app-design-guide-10.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-app-design-guide-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-03-06003458.I-D@ietf.org> --NextPart-- From root@core3.amsl.com Sun Mar 7 03:45:02 2010 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id B44F028C174; Sun, 7 Mar 2010 03:45:02 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100307114502.B44F028C174@core3.amsl.com> Date: Sun, 7 Mar 2010 03:45:02 -0800 (PST) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-erp-03.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2010 11:45:02 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter support for the EAP Re-authentication Protocol (ERP) Author(s) : J. Bournelle, et al. Filename : draft-ietf-dime-erp-03.txt Pages : 18 Date : 2010-03-07 The EAP Re-authentication Protocol (ERP) defines extensions to the Extensible Authentication Protocol (EAP) to support efficient re- authentication between the peer and an EAP Re-authentication (ER) server through a compatible authenticator. This document specifies Diameter support for ERP. It defines a new Diameter ERP application to transport ERP messages between an ER authenticator and the ER server, and a set of new AVPs that can be used to transport the cryptographic material needed by the re-authentication server. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-erp-03.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-erp-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-03-07033400.I-D@ietf.org> --NextPart-- From gwz@net-zen.net Sun Mar 7 04:17:51 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 18BE328C19E for ; Sun, 7 Mar 2010 04:17:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.03 X-Spam-Level: X-Spam-Status: No, score=-0.03 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_50=0.001, RCVD_IN_SORBS_WEB=0.619] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IL-vkaSy9P+7 for ; Sun, 7 Mar 2010 04:17:50 -0800 (PST) Received: from smtpauth22.prod.mesa1.secureserver.net (smtpauth22.prod.mesa1.secureserver.net [64.202.165.44]) by core3.amsl.com (Postfix) with SMTP id 5E65328C187 for ; Sun, 7 Mar 2010 04:17:50 -0800 (PST) Received: (qmail 15727 invoked from network); 7 Mar 2010 12:17:52 -0000 Received: from unknown (124.122.164.217) by smtpauth22.prod.mesa1.secureserver.net (64.202.165.44) with ESMTP; 07 Mar 2010 12:17:51 -0000 From: "Glen Zorn" To: Date: Sun, 7 Mar 2010 19:17:41 +0700 Organization: Network Zen Message-ID: <005901cabdf0$31a26f10$94e74d30$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acq9777pTzXpnBNIQJq2RnphaPch3g== Content-Language: en-us x-cr-hashedpuzzle: AOnn Adhs Bi/e CMAb Gq/g H8fH I7Xg JIAc K1qU LIqQ LjFl NsKu Pc7j QByh RSvL TxpN; 2; ZABpAG0AZQBAAGkAZQB0AGYALgBvAHIAZwA7AGgAbwBrAGUAeQBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {E55E6070-161B-439F-9CF0-FDC097B191B7}; ZwB3AHoAQABuAGUAdAAtAHoAZQBuAC4AbgBlAHQA; Sun, 07 Mar 2010 12:14:33 GMT; cAByAGUAcwBlAG4AdABhAHQAaQBvAG4AIABvAG4AIABEAGkAYQBtAGUAdABlAHIAIABFAFIAUAAgAEEAcABwACAAaQBuACAASABvAGsAZQB5AA== x-cr-puzzleid: {E55E6070-161B-439F-9CF0-FDC097B191B7} Cc: hokey@ietf.org Subject: [Dime] presentation on Diameter ERP App in Hokey X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2010 12:17:51 -0000 Is anyone interested in giving a update on the Diameter ERP app during the hokey session in Anaheim? From gwz@net-zen.net Sun Mar 7 06:00:41 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D9D523A8F6C for ; Sun, 7 Mar 2010 06:00:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.113 X-Spam-Level: X-Spam-Status: No, score=-1.113 tagged_above=-999 required=5 tests=[AWL=0.867, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yMkSOweHCEDN for ; Sun, 7 Mar 2010 06:00:41 -0800 (PST) Received: from smtpauth12.prod.mesa1.secureserver.net (smtpauth12.prod.mesa1.secureserver.net [64.202.165.35]) by core3.amsl.com (Postfix) with SMTP id 0B8643A8972 for ; Sun, 7 Mar 2010 06:00:40 -0800 (PST) Received: (qmail 22797 invoked from network); 7 Mar 2010 14:00:42 -0000 Received: from unknown (124.122.164.217) by smtpauth12.prod.mesa1.secureserver.net (64.202.165.35) with ESMTP; 07 Mar 2010 14:00:41 -0000 From: "Glen Zorn" To: Date: Sun, 7 Mar 2010 21:00:30 +0700 Organization: Network Zen Message-ID: <007301cabdfe$8efa1f60$acee5e20$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acq9+q8PGPHk759ERiOvM2FdCK5XbwAAnAJw Content-Language: en-us Subject: [Dime] FW: New Version Notification for draft-zorn-dime-radia-gate-01 X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2010 14:00:41 -0000 FYI -----Original Message----- From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20 Sent: Sunday, March 07, 2010 8:33 PM To: gwz@net-zen.net Cc: Lionel.morand@orange-ftgroup.com; tom.hiller@alcatel-lucent.com Subject: New Version Notification for draft-zorn-dime-radia-gate-01=20 A new version of I-D, draft-zorn-dime-radia-gate-01.txt has been = successfuly submitted by Glen Zorn and posted to the IETF repository. Filename: draft-zorn-dime-radia-gate Revision: 01 Title: The RADIUS-Diameter Gateway (RADIA) Application Creation_date: 2010-03-07 WG ID: Independent Submission Number_of_pages: 7 Abstract: This document describes the Diameter RADIUS-Diameter Gateway (RADIA) Application, which is designed to facillitate the interoperability of Authentication, Authorization and Accounting (AAA) systems based upon RADIUS and Diameter. = =20 The IETF Secretariat. From root@core3.amsl.com Sun Mar 7 07:45:01 2010 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 59AD53A9159; Sun, 7 Mar 2010 07:45:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100307154501.59AD53A9159@core3.amsl.com> Date: Sun, 7 Mar 2010 07:45:01 -0800 (PST) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-diameter-qos-15.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2010 15:45:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter Quality of Service Application Author(s) : D. Sun, et al. Filename : draft-ietf-dime-diameter-qos-15.txt Pages : 58 Date : 2010-03-07 This document describes the framework, messages and procedures for the Diameter Quality of Service (QoS) application. The Diameter QoS application allows network elements to interact with Diameter servers when allocating QoS resources in the network. In particular, two modes of operation, namely "Pull" and "Push", are defined. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-diameter-qos-15.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-diameter-qos-15.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-03-07074348.I-D@ietf.org> --NextPart-- From root@core3.amsl.com Sun Mar 7 08:00:01 2010 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 9A3B03A8C78; Sun, 7 Mar 2010 08:00:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100307160001.9A3B03A8C78@core3.amsl.com> Date: Sun, 7 Mar 2010 08:00:01 -0800 (PST) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-app-design-guide-11.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2010 16:00:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter Applications Design Guidelines Author(s) : V. Fajardo, et al. Filename : draft-ietf-dime-app-design-guide-11.txt Pages : 26 Date : 2010-03-07 The Diameter Base protocol provides updated rules on how to extend Diameter by modifying and/or deriving from existing applications or creating entirely new applications. This is a companion document to the Diameter Base protocol that further explains and clarifies these rules. It is meant as a guidelines document and therefore it does not add, remove or change existing rules. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-app-design-guide-11.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-app-design-guide-11.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-03-07074829.I-D@ietf.org> --NextPart-- From Lothar.Reith@detecon.com Sun Mar 7 11:34:33 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 364AA28C1C9 for ; Sun, 7 Mar 2010 11:34:33 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GKhp-4LifP9Z for ; Sun, 7 Mar 2010 11:34:32 -0800 (PST) Received: from dtc035.detecon.net (dtc035.detecon.net [194.25.60.135]) by core3.amsl.com (Postfix) with ESMTP id B807B28C1C2 for ; Sun, 7 Mar 2010 11:34:31 -0800 (PST) Received: from unknown (HELO dc00356.detecon.com) ([172.16.10.106]) by relay.dtc035.detecon.net with ESMTP; 07 Mar 2010 20:34:21 +0100 Received: from dc302v.detecon.com ([172.16.10.41]) by dc00356.detecon.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 7 Mar 2010 20:34:21 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Sun, 7 Mar 2010 20:34:35 +0100 Message-ID: <8AAA8EFE7E4B594A86052935CF66E62EA18BB6@dc302v.detecon.com> In-Reply-To: <20100307154501.59AD53A9159@core3.amsl.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: thread-topic: [Dime] I-D Action:draft-ietf-dime-diameter-qos-15.txt thread-index: Acq+DU4lEe4BF9FsSnKqSqedniW3oQAGcD0g References: <20100307154501.59AD53A9159@core3.amsl.com> From: "Reith, Lothar" To: X-OriginalArrivalTime: 07 Mar 2010 19:34:21.0900 (UTC) FILETIME=[2FD870C0:01CABE2D] Subject: Re: [Dime] I-D Action:draft-ietf-dime-diameter-qos-15.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2010 19:34:33 -0000 =20 Dear all, I noticed that this draft does not seem to be aligned with = draft-ietf-dime-qos-attributes regarding the example given therein. This is due to the fact, that draft-ietf-dime-diameter-qos-15.txt does = not cover "online charging", only "accounting". In my view, the term = "accounting" is more or less synonomous with the term = "offline-charging".=20 Because the draft-ietf-dime-qos-attributes contains an example, which is = based on online-charging using DCCA (Diameter Credit Control = Application), I believe this apparent lack of coverage for online = charging should be fixed. Proposed solution to fix this issue: In draft-ietf-dime-diameter-qos-15.txt change the title of chapter 9 = from "accounting" to "accounting and charging", and add a section that = describes, how DCCA may be used to charge for QoS, e.g. by referring to = the example given in draft-ietf-dime-qos-attributes. Alternatively, add a separate chapter 10 with title: "online charging", = in which the interworking with DCCA should be described at least at a = high level, potentially also referring to the example given in = draft-ietf-dime-qos-attributes. Best Regards, Lothar Reith Detecon International (Deutsche Telekom Group) =20 -----Urspr=FCngliche Nachricht----- Von: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] Im Auftrag von = Internet-Drafts@ietf.org Gesendet: Sonntag, 7. M=E4rz 2010 16:45 An: i-d-announce@ietf.org Cc: dime@ietf.org Betreff: [Dime] I-D Action:draft-ietf-dime-diameter-qos-15.txt A New Internet-Draft is available from the on-line Internet-Drafts = directories. This draft is a work item of the Diameter Maintenance and Extensions = Working Group of the IETF. Title : Diameter Quality of Service Application Author(s) : D. Sun, et al. Filename : draft-ietf-dime-diameter-qos-15.txt Pages : 58 Date : 2010-03-07 This document describes the framework, messages and procedures for the = Diameter Quality of Service (QoS) application. The Diameter QoS = application allows network elements to interact with Diameter servers = when allocating QoS resources in the network. In particular, two modes = of operation, namely "Pull" and "Push", are defined. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-diameter-qos-15.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader = implementation to automatically retrieve the ASCII version of the = Internet-Draft. From gwz@net-zen.net Sun Mar 7 18:16:59 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99E473A6827 for ; Sun, 7 Mar 2010 18:16:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.33 X-Spam-Level: X-Spam-Status: No, score=-1.33 tagged_above=-999 required=5 tests=[AWL=0.649, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=0.619] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-UR+OLu1LMT for ; Sun, 7 Mar 2010 18:16:58 -0800 (PST) Received: from smtpauth12.prod.mesa1.secureserver.net (smtpauth12.prod.mesa1.secureserver.net [64.202.165.35]) by core3.amsl.com (Postfix) with SMTP id 6D3BE3A6825 for ; Sun, 7 Mar 2010 18:16:58 -0800 (PST) Received: (qmail 25370 invoked from network); 8 Mar 2010 02:17:02 -0000 Received: from unknown (124.122.164.217) by smtpauth12.prod.mesa1.secureserver.net (64.202.165.35) with ESMTP; 08 Mar 2010 02:16:57 -0000 From: "Glen Zorn" To: "'Hannes Tschofenig'" References: <4B8EC288.1040001@gmx.net> In-Reply-To: <4B8EC288.1040001@gmx.net> Date: Mon, 8 Mar 2010 09:16:44 +0700 Organization: Network Zen Message-ID: <004101cabe65$68a9c010$39fd4030$@net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0042_01CABEA0.1508BF20" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acq7DfAP17zrY3saSx6XrH3jG4YMKwDVhUFg Content-Language: en-us Cc: dime@ietf.org Subject: Re: [Dime] DIME Agenda (Version 1) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 02:16:59 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0042_01CABEA0.1508BF20 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Tschofenig, Hannes (NSN - FI/Espoo) [mailto://hannes.tschofenig@nsn.com] writes: This is what I got so far: THURSDAY, March 25, 2010 0900-1130 Morning Session I Room: Palos Verdes * Agenda Bashing and Status Update (Chairs) * Diameter NAT Control Application (Frank) I did not receive further agenda requests! I do, however, believe it makes sense to talk about: Diameter Support for EAP Re-authentication Protocol (ERP) Realm-Based Redirection In Diameter Diameter Extended NAPTR Diameter IKEv2: Support for Interaction between IKEv2 Server and Diameter Server Diameter Support for Proxy Mobile IPv6 Localized Routing Diameter Priority Attribute Value Pairs (maybe, if not finished by this time) I hope to hear something from other draft authors. I would like short slots (5-10 min. each) for PCN Data Collection, The Diameter Capabilities Update Application, Diameter Attribute-Value Pairs for Cryptographic Key Transport and The RADIUS-Diameter Gateway (RADIA) Application Ciao Hannes ------=_NextPart_000_0042_01CABEA0.1508BF20 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Tschofenig, Hannes = (NSN - FI/Espoo) [mailto://hannes.t= schofenig@nsn.com] writes:

 

This is what I got = so far:

THURSDAY, March 25, 2010

0900-1130 Morning Session I

Room: Palos= Verdes

* Agenda Bashing and Status Update (Chairs)
* Diamet= er NAT Control Application (Frank)


I did not receive further agenda = requests!


I do, however, believe it makes sense to talk about:

Diameter = Support for EAP Re-authentication Protocol (ERP)
Realm-Based Redirection In Diameter
Dia= meter Extended NAPTR
Diameter IKEv2: Support for Interaction between IKEv2 Server and Diameter Server =
Diameter Support for Proxy Mobile IPv6 Localized Routing
Diam= eter Priority Attribute Value Pairs (maybe, if not finished by this = time)

I hope to hear something from other draft authors.

I would like short = slots (5-10 min. each) for PCN Data Collection, The Diameter Capabilities Update = Application, Diameter Attribute-Value Pairs for Cryptographic = Key Transport and The RADIUS-Diameter Gateway (RADIA) = Application



Ciao
Hannes

------=_NextPart_000_0042_01CABEA0.1508BF20-- From root@core3.amsl.com Sun Mar 7 23:45:02 2010 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 935003A683B; Sun, 7 Mar 2010 23:45:02 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100308074502.935003A683B@core3.amsl.com> Date: Sun, 7 Mar 2010 23:45:02 -0800 (PST) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-nat-control-02.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 07:45:02 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter Network Address and Port Translation Control Application Author(s) : F. Brockners, et al. Filename : draft-ietf-dime-nat-control-02.txt Pages : 40 Date : 2010-03-07 This document describes the framework, messages, and procedures for the Diameter Network Address and Port Translation Control Application (DNCA), allowing for per-endpoint control of large scale NAT/NAPT devices, which are put in place to cope with IPv4-address space completion. The DNCA allows external devices to configure and manage a NAT device - expanding the existing Diameter-based AAA and policy control capabilities with a NAT/NAPT control component. These external devices can be network elements in the data plane such as a Network Access Server (NAS), or can be more centralized control plane devices such as AAA-servers. DNCA establishes a context to commonly identify and manage endpoints on a gateway or server, and a large scale NAPT/NAT device. This includes, for example, the control of the total number of NAT-bindings allowed or the allocation of a specific NAT-binding for a particular endpoint. In addition, it allows large scale NAT devices to provide information relevant to accounting purposes. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-nat-control-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-nat-control-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-03-07233210.I-D@ietf.org> --NextPart-- From root@core3.amsl.com Mon Mar 8 06:45:05 2010 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 4FB043A6904; Mon, 8 Mar 2010 06:45:05 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100308144505.4FB043A6904@core3.amsl.com> Date: Mon, 8 Mar 2010 06:45:05 -0800 (PST) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-ikev2-psk-diameter-01.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 14:45:05 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter IKEv2: Support for Interaction between IKEv2 Server and Diameter Server Author(s) : V. Cakulev, A. Lior Filename : draft-ietf-dime-ikev2-psk-diameter-01.txt Pages : 17 Date : 2010-03-08 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 pre-shared secrets. With [RFC 5778] the 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 pre-shared secret based authentication available with IKEv2. This document therefore extends the functionality offered by [RFC 5778] with pre-shared key based authentication offered by IKEv2 when no EAP is used. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-ikev2-psk-diameter-01.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-ikev2-psk-diameter-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-03-08063703.I-D@ietf.org> --NextPart-- From wwwrun@core3.amsl.com Mon Mar 8 07:41:32 2010 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id E1D7A3A69EE; Mon, 8 Mar 2010 07:41:32 -0800 (PST) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20100308154132.E1D7A3A69EE@core3.amsl.com> Date: Mon, 8 Mar 2010 07:41:32 -0800 (PST) Cc: Internet Architecture Board , dime mailing list , dime chair , RFC Editor Subject: [Dime] Protocol Action: 'Diameter Quality of Service Application' to Proposed Standard X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 15:41:33 -0000 The IESG has approved the following document: - 'Diameter Quality of Service Application ' as a Proposed Standard This document is the product of the Diameter Maintenance and Extensions Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-diameter-qos-15.txt Technical Summary The document specifies a framework, messages and AVPs for performing QoS authorization operations. It defines a QoS Diameter application that allows network elements (QoS aware routers) to interact with Diameter servers to authorize QoS request. It has been designed to operate in both 'Push' or 'Pull' mode where QoS authorization state is either sent to the network element pro-actively (Push) or the network element directly request QoS authorization from the Diameter server. A set of commands and AVPs has been defined to support both operating modes. A supplemental state machine that augments the Diameter base protocol (RFC3588) state machine has also been defined to cleanly support Push mode operations. The document also describes QoS authorization session establishment as well as re-authorization. It provides examples and call flows that describes how QoS authorization can be used other applications (e.g. NSLP, SIP). Working Group Summary There was consensus in the WG to publish the document. Document Quality The document has been sent for review to NSIS and relevant QoS folks. This document defines a core component of a Network Operators QoS architecture and thus have gone through a long review process both within DIME WG and outside of it. It has also traversed several re-start iteration before its current acceptable state. Personnel Victor Fajardo is the document shepherd for this document. Dan Romascanu is the shepherding AD. From Hannes.Tschofenig@gmx.net Mon Mar 8 11:44:03 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EC4A3A6B31 for ; Mon, 8 Mar 2010 11:44:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.549 X-Spam-Level: X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oKrNxrIonlUe for ; Mon, 8 Mar 2010 11:44:02 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 1AFD33A6B11 for ; Mon, 8 Mar 2010 11:44:01 -0800 (PST) Received: (qmail invoked by alias); 08 Mar 2010 19:43:54 -0000 Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.255.4]) [88.115.222.204] by mail.gmx.net (mp068) with SMTP; 08 Mar 2010 20:43:54 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX193G/4FIcV3g9iuzPTCehbKRKPo3Nt6up3CFO4dBj rOHa5a2zddWTmT Message-ID: <4B955354.6090004@gmx.net> Date: Mon, 08 Mar 2010 21:43:16 +0200 From: Hannes Tschofenig User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: "dime@ietf.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.70999999999999996 Subject: [Dime] draft-ietf-dime-ikev2-psk-diameter-01.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 19:44:03 -0000 Just noticed that this document has a really unfortunate titel: Diameter IKEv2: Support for Interaction between IKEv2 Server and Diameter Server Is there a chance to put PSK based authentication or so somewhere into the title? Something like "Diameter Mobile IPv6 Pre-Shared Secret-based IKEv2 Authentication" Ciao Hannes From violeta.cakulev@alcatel-lucent.com Mon Mar 8 12:30:37 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 969673A69AF for ; Mon, 8 Mar 2010 12:30:37 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upoL7LGRSKC6 for ; Mon, 8 Mar 2010 12:30:36 -0800 (PST) Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 3AD293A68F2 for ; Mon, 8 Mar 2010 12:30:36 -0800 (PST) Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id o28KUb2r020966; Mon, 8 Mar 2010 14:30:37 -0600 (CST) Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id o28KUYot021524; Mon, 8 Mar 2010 14:30:37 -0600 (CST) Received: from USNAVSXCHMBSA3.ndc.alcatel-lucent.com ([135.3.39.119]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Mon, 8 Mar 2010 14:30:34 -0600 From: "Cakulev, Violeta (Violeta)" To: Hannes Tschofenig , "dime@ietf.org" Date: Mon, 8 Mar 2010 14:30:31 -0600 Thread-Topic: [Dime] draft-ietf-dime-ikev2-psk-diameter-01.txt Thread-Index: Acq+97655M2PxBXjRtythwepq2FhJwAAG17A Message-ID: References: <4B955354.6090004@gmx.net> In-Reply-To: <4B955354.6090004@gmx.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35 Subject: Re: [Dime] draft-ietf-dime-ikev2-psk-diameter-01.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 20:30:37 -0000 Hannes, Thanks for the comment. It definitely makes sense to put PSK based authentication in the title, how= ever in 3GPP2 this application is used for both Mobile IPv6 and inter-techn= ology handoff. How about "Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Se= rver to Diameter Server Interaction"? Regards, -Violeta -----Original Message----- From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of Han= nes Tschofenig Sent: Monday, March 08, 2010 2:43 PM To: dime@ietf.org Subject: [Dime] draft-ietf-dime-ikev2-psk-diameter-01.txt Just noticed that this document has a really unfortunate titel: Diameter IKEv2: Support for Interaction between IKEv2 Server and Diameter Server Is there a chance to put PSK based authentication or so somewhere into the = title? Something like "Diameter Mobile IPv6 Pre-Shared Secret-based IKEv2 Authenti= cation" Ciao Hannes _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime From Hannes.Tschofenig@gmx.net Mon Mar 8 12:33:56 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C338A3A6A75 for ; Mon, 8 Mar 2010 12:33:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yTxJbh1weL3x for ; Mon, 8 Mar 2010 12:33:55 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 986FC3A69CA for ; Mon, 8 Mar 2010 12:33:53 -0800 (PST) Received: (qmail invoked by alias); 08 Mar 2010 20:33:47 -0000 Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.255.4]) [88.115.222.204] by mail.gmx.net (mp068) with SMTP; 08 Mar 2010 21:33:47 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX1+DVap9RgWDwf82K4FNyaZKS5VX1myTommgbVQWQ9 fSIjODImb42NbA Message-ID: <4B955EFF.2020909@gmx.net> Date: Mon, 08 Mar 2010 22:33:03 +0200 From: Hannes Tschofenig User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: "Cakulev, Violeta (Violeta)" References: <4B955354.6090004@gmx.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.58999999999999997 Cc: "dime@ietf.org" Subject: Re: [Dime] draft-ietf-dime-ikev2-psk-diameter-01.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 20:33:56 -0000 Sounds much better. Cakulev, Violeta (Violeta) wrote: > Hannes, > Thanks for the comment. > It definitely makes sense to put PSK based authentication in the title, however in 3GPP2 this application is used for both Mobile IPv6 and inter-technology handoff. > > How about "Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction"? > > Regards, > -Violeta > > -----Original Message----- > From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of Hannes Tschofenig > Sent: Monday, March 08, 2010 2:43 PM > To: dime@ietf.org > Subject: [Dime] draft-ietf-dime-ikev2-psk-diameter-01.txt > > Just noticed that this document has a really unfortunate titel: > > Diameter IKEv2: Support for Interaction between IKEv2 Server and > Diameter Server > > > Is there a chance to put PSK based authentication or so somewhere into the title? > Something like "Diameter Mobile IPv6 Pre-Shared Secret-based IKEv2 Authentication" > > Ciao > Hannes > > > > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime > From root@core3.amsl.com Mon Mar 8 13:45:01 2010 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id BD7A53A6A31; Mon, 8 Mar 2010 13:45:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100308214501.BD7A53A6A31@core3.amsl.com> Date: Mon, 8 Mar 2010 13:45:01 -0800 (PST) Cc: dime@ietf.org Subject: [Dime] I-D Action:draft-ietf-dime-ikev2-psk-diameter-02.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 21:45:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction Author(s) : V. Cakulev, A. Lior Filename : draft-ietf-dime-ikev2-psk-diameter-02.txt Pages : 17 Date : 2010-03-08 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 pre-shared secrets. With [RFC 5778] the 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 pre-shared secret based authentication available with IKEv2. This document therefore extends the functionality offered by [RFC 5778] with pre-shared key based authentication offered by IKEv2 when no EAP is used. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-ikev2-psk-diameter-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-ikev2-psk-diameter-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-03-08134116.I-D@ietf.org> --NextPart-- From gwz@net-zen.net Wed Mar 10 04:29:03 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 283DC3A6887 for ; Wed, 10 Mar 2010 04:29:03 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qrFvnzsN0DZb for ; Wed, 10 Mar 2010 04:29:02 -0800 (PST) Received: from smtpauth14.prod.mesa1.secureserver.net (smtpauth14.prod.mesa1.secureserver.net [64.202.165.39]) by core3.amsl.com (Postfix) with SMTP id 4F9123A68B6 for ; Wed, 10 Mar 2010 04:29:00 -0800 (PST) Received: (qmail 823 invoked from network); 10 Mar 2010 12:29:04 -0000 Received: from unknown (115.87.89.44) by smtpauth14.prod.mesa1.secureserver.net (64.202.165.39) with ESMTP; 10 Mar 2010 12:29:04 -0000 From: "Glen Zorn" To: Date: Wed, 10 Mar 2010 19:28:40 +0700 Organization: Network Zen Message-ID: <001501cac04d$390cdec0$ab269c40$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcrATTbybk5B4F+UTNK8+CDSFqopgQ== Content-Language: en-us Subject: [Dime] Comments on draft-ietf-dime-erp-03.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2010 12:29:03 -0000 Section 4 says: If there is an ER server in the same domain as the authenticator (local domain), Diameter routing MUST QUESTION: Should this say "SHOULD: instead of "MUST"? be configured so that this ERP/DER message reaches this server, even if the Destination-Realm is not the local domain. I wonder what the purpose of this paragraph might be: why would it be necessary to configure Diameter routing at all? Actually, it seems like this passage could break the ERP app, since the very next paragraph says that the message should be routed to the bootstrapped ER server in the re-authentication case. This seems like the correct behavior, so why modify it? Section 4 says: When an ER server receives the ERP/DER message, it searches its local database for a root key FFS: and authorization state? There seems to be some confusion here: an ER server will _never_ receive an ERP/DER message, since that is a _Diameter_ message, not an EAP message. Actually, the confusion starts in the Introduction: "a new Diameter ERP application to transport ERP messages between an ER authenticator and the ER server". "Authenticator" is a technical term & refers to an EAP protocol entity, not a Diameter entity, so how can send Diameter messages? Clearing up this confusion might go a long way toward making an acceptable specification. From tena@huawei.com Wed Mar 10 19:01:02 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 408483A6B18 for ; Wed, 10 Mar 2010 19:01:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.454 X-Spam-Level: X-Spam-Status: No, score=-101.454 tagged_above=-999 required=5 tests=[AWL=1.144, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9V4m6oWQGsAG for ; Wed, 10 Mar 2010 19:01:01 -0800 (PST) Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id EFA0E3A6B12 for ; Wed, 10 Mar 2010 19:01:00 -0800 (PST) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZ3004D8KDSFE@szxga04-in.huawei.com> for dime@ietf.org; Thu, 11 Mar 2010 11:01:04 +0800 (CST) Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZ300MBTKDSLR@szxga04-in.huawei.com> for dime@ietf.org; Thu, 11 Mar 2010 11:01:04 +0800 (CST) Received: from z00147053k ([10.70.39.148]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KZ3003BXKDSQP@szxml06-in.huawei.com> for dime@ietf.org; Thu, 11 Mar 2010 11:01:04 +0800 (CST) Date: Thu, 11 Mar 2010 11:01:04 +0800 From: Tina TSOU To: dime@ietf.org, Glen Zorn Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Mailer: Microsoft Outlook Express 6.00.2900.5843 Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <001501cac04d$390cdec0$ab269c40$@net> Subject: Re: [Dime] Comments on draft-ietf-dime-erp-03.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Mar 2010 03:01:02 -0000 B. R. Tina http://tinatsou.weebly.com/contact.html ----- Original Message ----- From: "Glen Zorn" To: Sent: Wednesday, March 10, 2010 8:28 PM Subject: [Dime] Comments on draft-ietf-dime-erp-03.txt > Section 4 says: > If there is an ER server in the same domain as the authenticator > (local domain), Diameter routing MUST > > QUESTION: > Should this say "SHOULD: instead of "MUST"? > > be configured so that this ERP/DER message reaches this server, even > if the Destination-Realm is not the local domain. > I wonder what the purpose of this paragraph might be: why would it be > necessary to configure Diameter routing at all? Actually, it seems like > this passage could break the ERP app, since the very next paragraph says > that the message should be routed to the bootstrapped ER server in the > re-authentication case. This seems like the correct behavior, so why > modify > it? > > > Section 4 says: > When an ER server receives the ERP/DER message, it searches its local > database for a root key > > FFS: > and authorization state? > There seems to be some confusion here: an ER server will _never_ receive > an > ERP/DER message, since that is a _Diameter_ message, not an EAP message. > Actually, the confusion starts in the Introduction: "a new Diameter ERP > application to transport ERP messages between an ER authenticator and the > ER > server". "Authenticator" is a technical term & refers to an EAP protocol > entity, not a Diameter entity, so how can send Diameter messages? > Clearing > up this confusion might go a long way toward making an acceptable > specification. True. We need to work it out. Perhaps we have to separate the logical functional entity for EAP stuff, and the roles of Diameter stuff. > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From sunseawq@huawei.com Wed Mar 10 20:17:46 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 21ABA3A6A35 for ; Wed, 10 Mar 2010 20:17:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.645 X-Spam-Level: X-Spam-Status: No, score=-0.645 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iTa5uvatgM6F for ; Wed, 10 Mar 2010 20:17:45 -0800 (PST) Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 2F20A3A67E1 for ; Wed, 10 Mar 2010 20:17:45 -0800 (PST) Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZ300I91NXFCS@szxga01-in.huawei.com> for dime@ietf.org; Thu, 11 Mar 2010 12:17:40 +0800 (CST) Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZ300L2HNXFIJ@szxga01-in.huawei.com> for dime@ietf.org; Thu, 11 Mar 2010 12:17:39 +0800 (CST) Received: from w53375 ([10.164.12.38]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KZ300E90NXFB9@szxml06-in.huawei.com> for dime@ietf.org; Thu, 11 Mar 2010 12:17:39 +0800 (CST) Date: Thu, 11 Mar 2010 12:17:39 +0800 From: Qin Wu To: Glen Zorn , dime@ietf.org Message-id: <056b01cac0d1$c9b57250$260ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3598 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <001501cac04d$390cdec0$ab269c40$@net> Subject: Re: [Dime] Comments on draft-ietf-dime-erp-03.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Mar 2010 04:17:46 -0000 > Section 4 says: > If there is an ER server in the same domain as the authenticator > (local domain), Diameter routing MUST > > QUESTION: > Should this say "SHOULD: instead of "MUST"? > > be configured so that this ERP/DER message reaches this server, even > if the Destination-Realm is not the local domain. > I wonder what the purpose of this paragraph might be: why would it be > necessary to configure Diameter routing at all? Actually, it seems like > this passage could break the ERP app, since the very next paragraph says > that the message should be routed to the bootstrapped ER server in the > re-authentication case. This seems like the correct behavior, so why modify > it? [Qin]: Not sure the ER server can terminate the ERP/DER message based on *Diameter ERP application*, when the Destination-Realm of the message received from the peer is not the local domain. In my understanding, Normally Destination-Realm or Realm part of NAI is chosen by the peer and determine how the Diameter message is routed. Maybe the destination-Realm can be changed by the Diameter intermediate node. But the only example I can image is Dedicated NAI is used, the Diameter proxy in the visited realm can replace the destination-realm of message with home realm name rather than vistited realm name or local realm name. What am I missing? _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From sunseawq@huawei.com Wed Mar 10 22:27:05 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 918FD3A6B08 for ; Wed, 10 Mar 2010 22:27:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.626 X-Spam-Level: X-Spam-Status: No, score=-0.626 tagged_above=-999 required=5 tests=[AWL=-0.131, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IyqYhWlpNViU for ; Wed, 10 Mar 2010 22:27:04 -0800 (PST) Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id EB90D3A6B3A for ; Wed, 10 Mar 2010 22:21:31 -0800 (PST) Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZ300FNFTMMUX@szxga02-in.huawei.com> for dime@ietf.org; Thu, 11 Mar 2010 14:20:46 +0800 (CST) Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZ300GTNTMMF2@szxga02-in.huawei.com> for dime@ietf.org; Thu, 11 Mar 2010 14:20:46 +0800 (CST) Received: from w53375 ([10.164.12.38]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KZ30035OTMLSR@szxml04-in.huawei.com> for dime@ietf.org; Thu, 11 Mar 2010 14:20:46 +0800 (CST) Date: Thu, 11 Mar 2010 14:20:45 +0800 From: Qin Wu To: Glen Zorn , dime@ietf.org Message-id: <064b01cac0e2$fc28e1c0$260ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3598 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <001501cac04d$390cdec0$ab269c40$@net> Subject: Re: [Dime] Comments on draft-ietf-dime-erp-03.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Mar 2010 06:27:05 -0000 > Section 4 says: > When an ER server receives the ERP/DER message, it searches its local > database for a root key > > FFS: > and authorization state? [Qin]: I guess we talk this before as one of open issue. Seems authorization attributes is missing, such as 1.how the service type and Authorization-Lifetime is configured, 2.how to verify the local ER server is authorized to advertise the domain name, 3.how to authorize those users for ERP service. On the other hand, we should decouple authorization with authentication. > There seems to be some confusion here: an ER server will _never_ receive an > ERP/DER message, since that is a _Diameter_ message, not an EAP message. > Actually, the confusion starts in the Introduction: "a new Diameter ERP > application to transport ERP messages between an ER authenticator and the ER > server". "Authenticator" is a technical term & refers to an EAP protocol > entity, not a Diameter entity, so how can send Diameter messages? Clearing > up this confusion might go a long way toward making an acceptable > specification. [Qin]: Is it a big issue? _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From gwz@net-zen.net Wed Mar 10 23:24:22 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06FCD3A6850 for ; Wed, 10 Mar 2010 23:24:22 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dDVrMTtQyUd5 for ; Wed, 10 Mar 2010 23:24:21 -0800 (PST) Received: from smtpauth04.prod.mesa1.secureserver.net (smtpauth04.prod.mesa1.secureserver.net [64.202.165.95]) by core3.amsl.com (Postfix) with SMTP id 7C5163A6867 for ; Wed, 10 Mar 2010 23:24:20 -0800 (PST) Received: (qmail 3162 invoked from network); 11 Mar 2010 07:24:24 -0000 Received: from unknown (115.87.89.44) by smtpauth04.prod.mesa1.secureserver.net (64.202.165.95) with ESMTP; 11 Mar 2010 07:24:23 -0000 From: "Glen Zorn" To: "'Qin Wu'" References: <001501cac04d$390cdec0$ab269c40$@net> <064b01cac0e2$fc28e1c0$260ca40a@china.huawei.com> In-Reply-To: <064b01cac0e2$fc28e1c0$260ca40a@china.huawei.com> Date: Thu, 11 Mar 2010 14:23:54 +0700 Organization: Network Zen Message-ID: <00cd01cac0eb$d0fa69c0$72ef3d40$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcrA4wBhIu+JdWmmTWqp9B16NOfWYQACKedw Content-Language: en-us Cc: dime@ietf.org Subject: Re: [Dime] Comments on draft-ietf-dime-erp-03.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Mar 2010 07:24:22 -0000 Qin Wu [mailto:sunseawq@huawei.com] writes: ... > > There seems to be some confusion here: an ER server will _never_ > receive an > > ERP/DER message, since that is a _Diameter_ message, not an EAP > message. > > Actually, the confusion starts in the Introduction: "a new Diameter > ERP > > application to transport ERP messages between an ER authenticator and > the ER > > server". "Authenticator" is a technical term & refers to an EAP > protocol > > entity, not a Diameter entity, so how can send Diameter messages? > Clearing > > up this confusion might go a long way toward making an acceptable > > specification. > > [Qin]: Is it a big issue? Yes. From hannes.tschofenig@nsn.com Sun Mar 14 12:10:13 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F9D63A69DA for ; Sun, 14 Mar 2010 12:10:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.515 X-Spam-Level: X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ok42mb10x0Ef for ; Sun, 14 Mar 2010 12:10:12 -0700 (PDT) Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 440893A69FB for ; Sun, 14 Mar 2010 12:09:57 -0700 (PDT) Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o2EJA2nP002856 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sun, 14 Mar 2010 20:10:02 +0100 Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o2EJA2cw004684 for ; Sun, 14 Mar 2010 20:10:02 +0100 Received: from FIESEXC015.nsn-intra.net ([10.159.0.23]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Sun, 14 Mar 2010 20:10:02 +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: Sun, 14 Mar 2010 21:10:01 +0200 Message-ID: <3D3C75174CB95F42AD6BCC56E5555B45025114BC@FIESEXC015.nsn-intra.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Agenda Thread-Index: AcrDVV8kvLqIZU4nQmygdBEHxwKPlQ== From: "Tschofenig, Hannes (NSN - FI/Espoo)" To: X-OriginalArrivalTime: 14 Mar 2010 19:10:02.0305 (UTC) FILETIME=[F2C02B10:01CAC3A9] Subject: [Dime] Agenda X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Mar 2010 19:10:13 -0000 Hi all,=20 I have uploaded the agenda to the tools page (because I seem to have the access rights and the new chairs do not yet have them). You can find it here:=20 http://www.ietf.org/proceedings/10mar/agenda/dime.txt I received a lot of requests and I let the new chairs decide how they want to re-arrange the slots and how much time they want to give to everyone.=20 Ciao Hannes From dromasca@avaya.com Sun Mar 14 15:59:57 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2EA7E3A6783 for ; Sun, 14 Mar 2010 15:59:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.291 X-Spam-Level: X-Spam-Status: No, score=-1.291 tagged_above=-999 required=5 tests=[AWL=-1.292, BAYES_50=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TeowamZPEFtn for ; Sun, 14 Mar 2010 15:59:56 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id BF0613A63C9 for ; Sun, 14 Mar 2010 15:59:55 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.49,639,1262581200"; d="scan'208";a="180243763" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 14 Mar 2010 19:00:01 -0400 X-IronPort-AV: E=Sophos;i="4.49,639,1262581200"; d="scan'208";a="441626910" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.15]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 14 Mar 2010 18:59:59 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 14 Mar 2010 23:59:37 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New DIME WG Chairs Thread-Index: AcrDygVQHtmuDip9QTKeHt7xSRZzvg== From: "Romascanu, Dan (Dan)" To: Subject: [Dime] New DIME WG Chairs X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Mar 2010 22:59:57 -0000 The call for volunteers for new WG chairs got an excellent response. Thanks to everybody who volunteered. It was a tough choice between a number of candidates with impressive record and willingness to assume further responsibilities. This is very encouraging and proves in my opinion that Diameter continues to gather momentum in the IETF and in the Internet in general. My decision in consultation with my co-AD is to nominate Jouni Korhonen and Lionel Morand as new DIME co-chairs. I think that Jouni and Lionel gather experience, enthusiasm and a balance of development and deployment experience. I wish them good luck in their new assignment.=20 Hannes, Victor, Jouni and Lionel will work for the transition until Anaheim.=20 Dan From sdecugis@nict.go.jp Tue Mar 16 01:01:08 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC3A83A6874 for ; Tue, 16 Mar 2010 01:01:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.055 X-Spam-Level: X-Spam-Status: No, score=-0.055 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, HELO_EQ_JP=1.244] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5cXoO1x7Nfkp for ; Tue, 16 Mar 2010 01:01:07 -0700 (PDT) Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:2f8:29::2]) by core3.amsl.com (Postfix) with ESMTP id D1EA83A659A for ; Tue, 16 Mar 2010 01:00:59 -0700 (PDT) Received: from gw1.nict.go.jp (gw1 [133.243.18.250]) by ns1.nict.go.jp with ESMTP id o2G8157G016832 for ; Tue, 16 Mar 2010 17:01:05 +0900 (JST) Received: from gw1.nict.go.jp (localhost [127.0.0.1]) by gw1.nict.go.jp with ESMTP id o2G815mG000493 for ; Tue, 16 Mar 2010 17:01:05 +0900 (JST) Received: from mail2.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw1.nict.go.jp with ESMTP id o2G815VE000490 for ; Tue, 16 Mar 2010 17:01:05 +0900 (JST) Received: from mail2.nict.go.jp (localhost [127.0.0.1]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 042E82C2AC for ; Tue, 16 Mar 2010 17:01:05 +0900 (JST) Received: from [133.243.146.169] (5gou2f-dhcp09.nict.go.jp [133.243.146.169]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 007FB2C29A for ; Tue, 16 Mar 2010 17:01:04 +0900 (JST) Message-ID: <4B9F3AB6.4060609@nict.go.jp> Date: Tue, 16 Mar 2010 17:00:54 +0900 From: Sebastien Decugis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: dime@ietf.org References: <001501cac04d$390cdec0$ab269c40$@net> In-Reply-To: <001501cac04d$390cdec0$ab269c40$@net> X-Enigmail-Version: 1.0.1 OpenPGP: id=33D9F61D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Dime] Comments on draft-ietf-dime-erp-03.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2010 08:01:09 -0000 Hi, sorry for late reply. Preliminary question: what is "Network Working Group" ? > I wonder what the purpose of this paragraph might be: why would it be > necessary to configure Diameter routing at all? It is necessary to configure it in the case of an explicit bootstrapping request, since the NAI contains the home server, but we want to bootstrap the local server (if any). In any other case, there should be no conflict : default Diameter routing would send the message to this local ER server anyway. If we do not configure the routing explicitly, the message will go to the home domain, and might not pass through the local ER server. In such case, we loose the benefit of this local server. > There seems to be some confusion here: an ER server will _never_ receive an > ERP/DER message, since that is a _Diameter_ message, not an EAP message. > Actually, the confusion starts in the Introduction: "a new Diameter ERP > application to transport ERP messages between an ER authenticator and the ER > server". "Authenticator" is a technical term & refers to an EAP protocol > entity, not a Diameter entity, so how can send Diameter messages? Clearing > up this confusion might go a long way toward making an acceptable > specification. > No you mean that we have to define yet *another* protocol to transport the ERP message between a Diameter entity (that receives the Diameter ERP request) and the ER server ? Seems like recursive to me if we don't accept that the ER server *has* to talk "Diameter" as well... I will be glad to discuss this further in Anaheim. About the term "authenticator", I confess it is unclear to me what the difference is between all the terminology for this entity (the one that actually decides if the peer gets access or not, and generates the Diameter EAP request in full EAP authentication scenario). Is "NAS" better? Best regards, Sebastien. -- Sebastien Decugis Research fellow Network Architecture Group NICT (nict.go.jp) From jouni.nospam@gmail.com Wed Mar 17 03:36:39 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2C0D3A6835 for ; Wed, 17 Mar 2010 03:36:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.451 X-Spam-Level: * X-Spam-Status: No, score=1.451 tagged_above=-999 required=5 tests=[AWL=0.960, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_BL_SPAMCOP_NET=1.96] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aUKN3o+E22es for ; Wed, 17 Mar 2010 03:36:35 -0700 (PDT) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by core3.amsl.com (Postfix) with ESMTP id 55DFC3A659A for ; Wed, 17 Mar 2010 03:36:29 -0700 (PDT) Received: by fg-out-1718.google.com with SMTP id e21so458349fga.13 for ; Wed, 17 Mar 2010 03:36:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:content-type :content-transfer-encoding:subject:date:message-id:cc:to :mime-version:x-mailer; bh=rTLkqFSJai4ENxMHa2G7MakCcrp3HLgCuEmdHRvn4oI=; b=uEjttoXlyUzZQTzjzlTh6LkLBYYHeF6znS4gbKA3FLMJvqzC+Uk05xjVhXHnwr9PsS 8h/C18AZ9XfYYhJo2GPfb5v4lXqzn7qXtw2mochAhkNY9OmTIfxwEIKlsN7D0nIULZGT 7B2Q50tZ55GXlISIYHiaMPlnka2U/8VhXdmzk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; b=CR5jhqESjAX506hsiz8LfiGMl1GXDVgi76cwwk/JCXk0eci23hz23FiAFIBT3bOLz0 uYnbkn+a9dD1wd9zw/8NqsabmZYdeKKJRDziXpcZZUGtzjC/JxHwGz3DWFd2H1LO8BAg 9BytWlVTx2Z6TouzeszsiJY+gd/6LL7eRmvio= Received: by 10.87.2.15 with SMTP id e15mr2978122fgi.22.1268822196062; Wed, 17 Mar 2010 03:36:36 -0700 (PDT) Received: from [10.254.2.47] ([192.100.123.77]) by mx.google.com with ESMTPS id d8sm1525776fga.0.2010.03.17.03.36.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 17 Mar 2010 03:36:35 -0700 (PDT) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 17 Mar 2010 12:36:32 +0200 Message-Id: To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) Subject: [Dime] Slides for the Dime meeting X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2010 10:36:39 -0000 Presenters, Send your slides to the chairs latest by Wednesday 24th Mar. Regards, Jouni & Lionel From jouni.nospam@gmail.com Mon Mar 22 16:24:17 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3907C28C237 for ; Mon, 22 Mar 2010 16:24:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.469 X-Spam-Level: X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GOInIaVXrU5D for ; Mon, 22 Mar 2010 16:24:15 -0700 (PDT) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 04A2928C242 for ; Mon, 22 Mar 2010 16:24:14 -0700 (PDT) Received: by vws12 with SMTP id 12so69247vws.31 for ; Mon, 22 Mar 2010 16:24:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:content-type :content-transfer-encoding:subject:date:message-id:cc:to :mime-version:x-mailer; bh=eq0wyjgX/TiBKezGLsMzVZ7jZet7brx4DQIMd4Zx2ms=; b=K4t+WPBfN31QnqUknQT02WTcYvD37q8bfhURMTgCEUEJB8gZ1MP0Qr+xoK0Xrk/Ixo 07DisCG4auA7R4B75ZRvvJO3uw8XIoC4j/878tckQwRrNcJDBhYBi7o+f77p8pQlKfTQ 8pt6SaaZbPUd4BqnV+tYMjh+5Uc/HMaHTkAk0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; b=xgdBhTuXlYkUk54QkzP+Lf3VbWvoM9FEnkrJotz4NGKi6jLokAi5E+P5xon3vD/UtC gZOVuecrlnMlD3wckJx6cHXp8u6ayauWujyK+ZZ7UzUJ8Ng4eQl2sPI+ZlVFxRZo2sxm Juo5QR/HHjC4mvm8TqDEjqmh9tP7tc9GMs7ss= Received: by 10.220.123.104 with SMTP id o40mr1479161vcr.88.1269300265906; Mon, 22 Mar 2010 16:24:25 -0700 (PDT) Received: from dhcp-wireless-open-abg-24-75.meeting.ietf.org ([130.129.24.75]) by mx.google.com with ESMTPS id 33sm38835303vws.10.2010.03.22.16.24.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 22 Mar 2010 16:24:24 -0700 (PDT) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 23 Mar 2010 01:24:23 +0200 Message-Id: <048B3FF1-3F81-41D3-9933-0B19687381B2@gmail.com> To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) Subject: [Dime] DIME agenda updated X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Mar 2010 23:24:17 -0000 Hi, The revised agenda has been uploaded. If you think you need more than = the "standard" 10mins for your presentation, please send a mail to = chairs. - Lionel & Jouni= From sdecugis@nict.go.jp Tue Mar 23 09:31:26 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 369B83A6CBA for ; Tue, 23 Mar 2010 09:31:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.481 X-Spam-Level: * X-Spam-Status: No, score=1.481 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LCtTaS-Yk+MX for ; Tue, 23 Mar 2010 09:31:23 -0700 (PDT) Received: from sd-11965.dedibox.fr (sd-11965.dedibox.fr [88.191.67.190]) by core3.amsl.com (Postfix) with ESMTP id E304A3A6C7F for ; Tue, 23 Mar 2010 09:31:22 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by sd-11965.dedibox.fr (Postfix) with ESMTP id 7B2A727DD1 for ; Tue, 23 Mar 2010 17:31:40 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at sd-11965.dedibox.fr Received: from sd-11965.dedibox.fr ([127.0.0.1]) by localhost (sd-11965.dedibox.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BbS8h276DDWd for ; Tue, 23 Mar 2010 17:31:35 +0100 (CET) Received: from [202.249.37.5] (morbier.koganei.wide.ad.jp [202.249.37.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sd-11965.dedibox.fr (Postfix) with ESMTPSA id 7909E27DD0 for ; Tue, 23 Mar 2010 17:31:34 +0100 (CET) Message-ID: <4BA8ECE1.1080109@nict.go.jp> Date: Wed, 24 Mar 2010 01:31:29 +0900 From: Sebastien Decugis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: "dime@ietf.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Dime] freeDiameter implementation X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2010 16:31:26 -0000 Hello, (sorry for the slightly off-topic mail) I just thought I could take the opportunity of IETF77 meeting to present the freeDiameter [1] implementation if there is interest here. In short, freeDiameter is a new open-source implementation, in C language, BSD-like license (WIDE license actually), supporting RFC3588 and 3588bis documents (i.e. dedicated TLS port, simplified state machine), designed to be easily extended (bu plug-ins) to support any Diameter application you like (or advanced routing, or...). Currently, only the base protocol is supported, but there is work in progress on two plug-ins: a RADIUS/Diameter gateway (following guidelines of RFC4005), and a Diameter EAP server (RFC4072) implementation. If you are interested in a detailed presentation on this project, please mail me, and I will organize a small tutorial during this IETF meeting. Thanks for reading! Best regards, Sebastien. [1] http://aaa.koganei.wide.ad.jp From lionel.morand@orange-ftgroup.com Tue Mar 23 13:24:54 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06FC83A684F for ; Tue, 23 Mar 2010 13:24:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.482 X-Spam-Level: * X-Spam-Status: No, score=1.482 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QuYF+a73vquM for ; Tue, 23 Mar 2010 13:24:53 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by core3.amsl.com (Postfix) with ESMTP id 0E67E3A6784 for ; Tue, 23 Mar 2010 13:24:53 -0700 (PDT) Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda13.si.francetelecom.fr (ESMTP service) with ESMTP id D9ABD19090C; Tue, 23 Mar 2010 21:25:10 +0100 (CET) Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id BFB6338403A; Tue, 23 Mar 2010 21:25:07 +0100 (CET) Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Tue, 23 Mar 2010 21:25:07 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Tue, 23 Mar 2010 21:25:05 +0100 Message-ID: <32266_1269375907_4BA923A3_32266_264454_1_D109C8C97C15294495117745780657AE0C66E6A7@ftrdmel1> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: REMINDER: Slides for the Dime meeting Thread-Index: AcrFvdz8bWVQB+DERbSy5TbtmdZ6HwFCCK7w References: From: To: X-OriginalArrivalTime: 23 Mar 2010 20:25:07.0933 (UTC) FILETIME=[EE0830D0:01CACAC6] X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.3.23.200042 Subject: [Dime] REMINDER: Slides for the Dime meeting X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2010 20:24:54 -0000 Presenters, Please provide your slides before 7.30pm on Wednesday. People not attending the meeting but following the audio stream will need t= he presentation material before the beginning of the meeting (at 9am on Thu= rsday). Thank you! Lionel & Jouni=20 > -----Message d'origine----- > De : jouni korhonen [mailto:jouni.nospam@gmail.com]=20 > Envoy=E9 : mercredi 17 mars 2010 11:37 > =C0 : dime@ietf.org > Cc : jouni korhonen; MORAND Lionel RD-CORE-ISS > Objet : Slides for the Dime meeting >=20 > Presenters,=20 >=20 > Send your slides to the chairs latest by Wednesday 24th Mar. >=20 > Regards, > Jouni & Lionel >=20 ********************************* This message and any attachments (the "message") are confidential and inten= ded solely for the addressees.=20 Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration.=20 France Telecom Group shall not be liable for the message if altered, change= d or falsified. If you are not the intended addressee of this message, please cancel it imm= ediately and inform the sender. ******************************** From stefan.winter@restena.lu Thu Mar 25 10:36:10 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B97F3A6C5E for ; Thu, 25 Mar 2010 10:36:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.469 X-Spam-Level: X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XplejHRqRG4p for ; Thu, 25 Mar 2010 10:36:09 -0700 (PDT) Received: from legolas.restena.lu (legolas.restena.lu [158.64.1.34]) by core3.amsl.com (Postfix) with ESMTP id B906B3A6E15 for ; Thu, 25 Mar 2010 10:30:46 -0700 (PDT) Received: from legolas.restena.lu (localhost [127.0.0.1]) by legolas.restena.lu (Postfix) with ESMTP id 59B65A98AA for ; Thu, 25 Mar 2010 18:31:08 +0100 (CET) Received: from [158.64.15.252] (252-15.vpn.restena.lu [158.64.15.252]) by legolas.restena.lu (Postfix) with ESMTPSA id 4ECDBA98CC for ; Thu, 25 Mar 2010 18:31:01 +0100 (CET) Message-ID: <4BAB9DD0.7080708@restena.lu> Date: Thu, 25 Mar 2010 10:30:56 -0700 From: Stefan Winter User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: dime@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV Subject: [Dime] Jabber scribe discontinued X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Mar 2010 17:36:10 -0000 Floks, my Jabber connection just went down, and Alan DeKok's as well. Seems like all of Jabber is down, and I can't continue to scribe :-( Sorry, Stefan From tena@huawei.com Thu Mar 25 10:47:07 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BA2A3A6967 for ; Thu, 25 Mar 2010 10:47:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -97.261 X-Spam-Level: X-Spam-Status: No, score=-97.261 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BjAWjMDPP+IK for ; Thu, 25 Mar 2010 10:47:06 -0700 (PDT) Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 43FD83A6DEF for ; Thu, 25 Mar 2010 10:45:25 -0700 (PDT) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZU00BZQMO1K5@szxga04-in.huawei.com> for dime@ietf.org; Fri, 26 Mar 2010 01:45:37 +0800 (CST) Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZU00065MO1JP@szxga04-in.huawei.com> for dime@ietf.org; Fri, 26 Mar 2010 01:45:37 +0800 (CST) Received: from dhcp-wireless-open-abg-25-219.meeting.ietf.org (dhcp-wireless-open-abg-25-219.meeting.ietf.org [130.129.25.219]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KZU00BXEMNV9J@szxml01-in.huawei.com>; Fri, 26 Mar 2010 01:45:37 +0800 (CST) Date: Thu, 25 Mar 2010 10:45:30 -0700 From: Tina TSOU In-reply-to: <4BAB9DD0.7080708@restena.lu> To: Stefan Winter Message-id: <2E7A5AE0-2DF7-462E-9346-72B43697D85E@huawei.com> MIME-version: 1.0 X-Mailer: Apple Mail (2.936) Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-transfer-encoding: 7BIT References: <4BAB9DD0.7080708@restena.lu> Cc: dime@ietf.org Subject: Re: [Dime] Jabber scribe discontinued X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Mar 2010 17:47:07 -0000 The server has been restarted. It works now. B. R. Tina http://tinatsou.weebly.com/contact.html On Mar 25, 2010, at 10:30 AM, Stefan Winter wrote: > Floks, > > my Jabber connection just went down, and Alan DeKok's as well. Seems > like all of Jabber is down, and I can't continue to scribe :-( > > Sorry, > > Stefan > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Wed Mar 31 04:46:37 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 895733A689B for ; Wed, 31 Mar 2010 04:46:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.131 X-Spam-Level: * X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S4B9X92QFPVq for ; Wed, 31 Mar 2010 04:46:36 -0700 (PDT) Received: from mail-bw0-f217.google.com (mail-bw0-f217.google.com [209.85.218.217]) by core3.amsl.com (Postfix) with ESMTP id A30E43A6892 for ; Wed, 31 Mar 2010 04:46:35 -0700 (PDT) Received: by bwz9 with SMTP id 9so1957873bwz.29 for ; Wed, 31 Mar 2010 04:47:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:content-type:subject :date:message-id:cc:to:mime-version:x-mailer; bh=Bba4vtJ2k7zY3AQxc0X+b0RuEeSrzPGet9ChfrpwXtA=; b=wnYKP/5Akc3u5cwdd/55R5F+FFoih3+N4vK3RAjGkSY6BULYyxWzRASfyi96cjt17K 9DvgDSclOlRltA5oJUWXtIBER9Jgur2TQWUkjxJagov0nlmj67fdmg29NCjiGwdFQMRv cteCwX1lyB8R5CAiH8RuceeTLJFIqwM8BV1r0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:subject:date:message-id:cc:to:mime-version :x-mailer; b=KNMDbAR1jUtl/8LYiJyM00trBBl5c1iuLJZUWsDDm6mE/NNgKBdq4KQTXMS3dG05zr Ev1gd0wjSpdDHxk+KZcRitwpuY72UAbVp5TQdwVL7hHN7Tn9l/4SKpPQCLvmTxj9GNOM 7or+5VHdSzhuoq/29YW26T1jSPiQFURp15ixA= Received: by 10.204.132.194 with SMTP id c2mr228017bkt.167.1270036022797; Wed, 31 Mar 2010 04:47:02 -0700 (PDT) Received: from [10.254.0.254] ([192.100.123.77]) by mx.google.com with ESMTPS id s17sm57065946bkd.10.2010.03.31.04.47.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 31 Mar 2010 04:47:01 -0700 (PDT) From: jouni korhonen Content-Type: multipart/mixed; boundary=Apple-Mail-3--328952206 Date: Wed, 31 Mar 2010 14:47:03 +0300 Message-Id: <00F70B04-0BDF-44FA-87FA-356872F3B323@gmail.com> To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) Subject: [Dime] Draft notes from IETF#77 Dime WG meeting. X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2010 11:46:37 -0000 --Apple-Mail-3--328952206 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi all, First, thanks to Sebastien and Tom for detailed notes! Here are what we = combined out of them. Have a look at it and if you think something has = been captured incorrectly, please let us know asap. The final notes will = have a slightly better layout.. hopefully ;) - Jouni & Lionel --Apple-Mail-3--328952206 Content-Disposition: attachment; filename=dime-draft-notes.txt Content-Type: text/plain; name="dime-draft-notes.txt" Content-Transfer-Encoding: quoted-printable DIME met in Palos Verdes 9:00-11:30 Thursday March 25 Jouni Korhonen and Lionel Morand chaired the meeting. NOTE WELL was presented. 1. Agenda and Status =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Jouni, charts RFC3588bis: Hannes promised Victor to do PROTO writeup. Dan suggested not to do it = now because of open issues. There is a small issue with DNS that is discussed today, = apart for this it should be ready (Hannes). An editor *will* be needed at time of = IESG review (Tom). Can Victor still do it? Hannes says Victor will still act as the = editor. He has only given up co-chair work. 2. NAPT control =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Frank Brockners, charts Clarifications added. Terminology: Manager-agent rather than client-server because it is not = clear which is which in the flow of messages. Authors ask if group ready for last = call, and for detailed reviews. Jouni: the document seems ready, will have a look at it, and if OK issue = the WGLC.=20 Expect for reviews. Not many people read it in the room (5 people = have read it). 3) Diameter Support for EAP Re-authentication Protocol =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D Sebastien Decugis, charts Glen Zorn noted that a decision at the IETF76 meeting that local = handovers would not be visible from the home domain had not been confirmed on the list. = Hannes stated that it would be desirable to have such visibility. Tom Taylor = recalled that it was suggested that authorization would provide the necessary = visibility. Lionel: will raise issue on the list. Hannes asked who understood the issue. He restated it, then asked if = this would be desirable. Mark Jones suggested a mechanism for notifying the home = domain should be provided but not mandated. xxxx suggested the requirement = would be deployment-dependent. Glen Zorn suggested that while EAP/ERP messages = would not go back to the homne domain, Diameter operations could be happening in = the background that do. Hannes: summary, leave status as is (handover not visible to home = domain) and leave it to deployment to provide an alternative. No apparent = agreement, either with this position or with requiring the document to = provide a mechanism. Lionel: continue discussion on list, see where we get. 4) Realm-Based Redirection In Diameter =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Tom Taylor, charts IPR from Huawei has been finally declared. 2 reviews received, however = comments not yet addressed. Agreed that the resolution of the application problem is to specify this = like the capability update, as an increment that can be incorporated into a new = application. Jouni: don't remember well, the outcome could be to define a mechanism, and people who want to support it have to use a new app (making = use of the new mechanism) Tom: ok, it resolves the issue... Mention of the caching time should be deleted. 5) Diameter Extended NAPTR =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D Mark Jones, charts Some discussion re "aaa" tag, no change - distinction of Diameter vs. = RADIUS. Some discussion of procedures for vendor-specific application service = tags. Mark will bring proposal to the list -- inclined to require RFC = (individual, Informational). Lionel: reprise of aaa+ issue. Not well specified in 3588 -- don't need = carry on with this in 3588bis. Will review text on list -- issue of = obsoleting 3588 stuff. Stefan: "aaa+ap1" too generic, use "Diameter+ap1"-like instead. Mark: OK. Lionel: What is the role of the "x-" tags? Mark: for applications defined in documents not in RFC series, they = cannot be created in the registry otherwise. (clarifying discussion) Followed discussion on RFC3958 about rules for IANA attributions with = Dan. Follow-up on this: Mark bring discussion to the list about RFC3588bis = update. Lionel: why do we want to keep what is in the 3588? Do we need backward compatibility? To be checked on the mailing list... General query: Is there any current deployment on (3588)-NAPTR dynamic = discovery? So far no one has stated they have implemented it. 6) Diameter IKEv2 PSK =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D http://www.ietf.org/id/draft-ietf-dime-ikev2-psk-diameter-02.txt o Presenter: Violeta Cakulev Hannes done a review. 2 new revisions since then. Dan: The document updates 5778, it must be specified in the header. Violeta: I am not sure it updates the document, have to check. 7) Diameter Support for Proxy Mobile IPv6 Localized Routing =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D http://www.ietf.org/id/draft-ietf-dime-pmip6-lr-00.txt o Presenter: Glen Zorn, charts Glen commented on excessive number of figures. Dan: do need the figures to hang the text on. Jouni: how likely this document will match what Netext WG is doing? Glen: looks pretty good at the moment. (on proposal 3) Dan: the original draft text sounds like everything is needed...=20 The proposed change might be useful. Conclusion - Request WG feedback on the proposals, encourage more = feedback. (will be done on the mailing list, everybody is sleeping in the room... = ;) 8) Diameter Priority Attribute Value Pairs =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D http://www.ietf.org/id/draft-ietf-dime-priority-avps-00.txt o Presenter: Tom Taylor, charts Need some confirmation on the list requesting publication. WGLC ended without any comment =3D> problem. Ken Carlberg has asked a couple of companies to look and comment. Karl: the WGLC was just before IETF, everybody is quite busy.=20 I asked reviews but got no feedback in this period. Jouni: Chairs will renew or extend LC after the meeting. Glen: There can only be 1 "last" call :-) Please make sure there is only = one. 9) Diameter Attribute-Value Pairs for Cryptographic Key Transport =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D http://www.ietf.org/id/draft-ietf-dime-local-keytran-02.txt o Presenter: Glen Zorn, charts No comments. And Jabber also died meanwhile ;) 10) Diameter Capabilities Update Application =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D http://www.ietf.org/id/draft-ietf-dime-capablities-update-03.txt o Presenter: Glen Zorn, no charts Believes it is ready to be last-called. No activity to report. Dan: this WG has a lot of docs in progress. Problem is that very little feedback from participants other than authors. If you want more progress on *your* draft, please review *others* as well. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Jouni: Now considering individual drafts. No room for new milestones = until existing work done. Dan: but can still develop drafts as individual drafts. 11) Diameter Parameter Query =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D http://tools.ietf.org/id/draft-winterbottom-dime-param-query-01.txt o Presenter: James Winterbottom, charts Glen Zorn: this is a database access problem, not a Diameter problem. Nothing prevents anyone from querying the database using a suitable protocol. Alan Dekok: supports Glen's view. Diameter does AAA, the cost to add = queries is small, but you end doing SQL-like in Diameter, which is not = good. Hannes: so what mechanism would you use?. Alan: Trusted computing group (TGC) working on exactly this problem. TCG = has a standard to access database with SOAP, for what happens in the = network. It is quite new, no not much deployed, but they solve exactly this = problem.=20 Frank: individual SDOs will create their own Diameter applications, but = generic solution very difficult. Lionel: not sure Diameter is = well-suited for the necessary notifications. Dan: impression in = Hiroshima and now the same. Document needs further development, perhaps = breaking up to focus on specific problems. Lionel: We had this discussion in several places, we cannot really come = to a standard solution. Dan: the context of this draft is probably not related to DiME work.=20 This work would require a serious rechartering. Cleanup, split the = document, then come back with parts that fit. Jouni: you referenced several SDO. Do you have a timeline? Wolfgang: I am in favor of the proposal. Diameter is a good protocol for = this purpose. Glen: what is the problem with different SDOs doing the job differently. = Each is dealing with a different database structure. James: then why caring for Diameter at all? Dan: this does not solve any problems related to access. Sees little = chance for this to be accepted as a DIME work item. If you want to do it, = there is another WG (?) Lionel: problem with doing it here is how to be generic enough to solve everyone's needs. Individual SDOs can provide more targetted solutions. Only value added would be to have standard values for = AVPs. James: it is already in the draft: we require explicitly what = information we want. Lionel: How do you standardize what to query? It will be different in = each context. Martin Thompson: problem needs to be recast in different perspective. = Query is: what was in such-and-such AAA request, and what was the = content of the response? More like an accounting record query. Jabber: no support for database query. xxxx: perhaps define a design pattern, so SDOs can do things in a way = that does least damage to Diameter. Dan: the mechanism is there in Diameter. But the problem is not only out = of scope of DIME, it is outside the domain of expertise of the WG. Wolfgang: How do we query "who owns the IP address XXX" ? Diameter is a logical interface for this. Dan: this is philosophical.=20 Mark: we are querying very specific attributes, not anything generic.=20 We want to know AAA-network access information. If clarified in the draft, it can be considered. Jouni: can work on draft, but cannot expect early action on it. And = time's up... 12) Diameter PreCongestion Notification (PCN) Data Collection = Application = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D http://tools.ietf.org/id/draft-huang-dime-pcn-collection-02.txt o Presenter: Tom Taylor, charts Status report, no comments. 13) The RADIUS-Diameter Gateway (RADIA) Application =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D http://tools.ietf.org/id/draft-zorn-dime-radia-gate-01.txt o Presenter: Glen Zorn, no charts Not sure if anybody cares about the topic anymore. Will be considered by AAA directorate. Jouni & Lionel: Meeting concluded. --Apple-Mail-3--328952206-- From naveen.sarma@gmail.com Wed Mar 31 06:36:51 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C7F23A6816 for ; Wed, 31 Mar 2010 06:36:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.132 X-Spam-Level: * X-Spam-Status: No, score=1.132 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5T9Mwfc9Tgch for ; Wed, 31 Mar 2010 06:36:50 -0700 (PDT) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 5A2CC3A67B6 for ; Wed, 31 Mar 2010 06:36:50 -0700 (PDT) Received: by vws9 with SMTP id 9so42148vws.31 for ; Wed, 31 Mar 2010 06:37:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:received :message-id:subject:to:content-type; bh=GJp2I/KwrN6EcnQPxTTjD5MXnAkfTI9OC8NwmAyBU7o=; b=dBKpySIlzbqBufc2qECsX5Hy/Uj9UMrjQ8b9EXeJJNwKXuITQUS0+bcJUcCtB1dzto fuDhW3qHhCy2m3i+hsHTxRfYgLjuLK2lTEjuQvnC513Sgs2g47Y+nfH0X9qwUt7AAVHD mgcROWtPRtU+0p61rm6tPiuGem4Yowqwd4PjE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=MFmYZEejdgZFlqCYthDXuWOOSJltAzsnbVyB7LTpnOuGKRtokIAZaRKswh+XTzdUoS xxeq+1fEKba5thOw6aRoBW0GnbvAiaw9HvXf0x6ZuKbEj+LhiuQ+ZcaYO3mGR2rzzS8g fu+QTr2FgiVtBBhPRNzM/9oq7cJ9bknfravFA= MIME-Version: 1.0 Received: by 10.220.125.78 with HTTP; Wed, 31 Mar 2010 06:36:56 -0700 (PDT) From: Naveen Kottapalli Date: Wed, 31 Mar 2010 14:36:56 +0100 Received: by 10.220.47.220 with SMTP id o28mr1295939vcf.6.1270042636126; Wed, 31 Mar 2010 06:37:16 -0700 (PDT) Message-ID: To: dime@ietf.org Content-Type: multipart/alternative; boundary=0016e6464f582d0d86048318d8ab Subject: [Dime] Message mis-sequencing over SCTP X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2010 13:36:51 -0000 --0016e6464f582d0d86048318d8ab Content-Type: text/plain; charset=ISO-8859-1 Hi, Am just wondering whether the mis-sequencing in the delivery of packets when SCTP is being used as transport layer would cause any problem. For example, take an association with 5 out-streams to send out the Diameter messages. Immediately after sending CEA on stream 0, all other messages are sent over other streams like 1, 2, 3, and 4. There is a chance that the other Diameter messages will reach the peer before the CEA is processed? Does the existing draft miss the sequencing problem over SCTP? Yours, Naveen. --0016e6464f582d0d86048318d8ab Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,
=A0
Am just wondering whether the mis-sequencing in the delivery of packet= s when SCTP is being used as transport layer would cause any problem.=A0 Fo= r example, take an association=A0with 5 out-streams to send out the Diamete= r messages.=A0 Immediately after sending CEA on stream 0, all other message= s are sent over other streams like 1, 2, 3, and 4.
=A0
There=A0is a chance that the other Diameter messages will reach the pe= er before the CEA is processed?=A0=A0 Does the existing draft miss the sequ= encing problem over SCTP?

Yours,
Naveen.
--0016e6464f582d0d86048318d8ab-- From Mark.Jones@bridgewatersystems.com Wed Mar 31 06:48:32 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6D013A68BC for ; Wed, 31 Mar 2010 06:48:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.855 X-Spam-Level: X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_83=0.6, J_CHICKENPOX_84=0.6, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lMehN7q7GyIg for ; Wed, 31 Mar 2010 06:48:32 -0700 (PDT) Received: from mail29.messagelabs.com (mail29.messagelabs.com [216.82.249.147]) by core3.amsl.com (Postfix) with ESMTP id 6B0913A679C for ; Wed, 31 Mar 2010 06:48:31 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: Mark.Jones@bridgewatersystems.com X-Msg-Ref: server-10.tower-29.messagelabs.com!1270043340!87347898!1 X-StarScan-Version: 6.2.4; banners=-,-,- X-Originating-IP: [72.35.6.119] Received: (qmail 20831 invoked from network); 31 Mar 2010 13:49:01 -0000 Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-10.tower-29.messagelabs.com with RC4-SHA encrypted SMTP; 31 Mar 2010 13:49:01 -0000 Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Wed, 31 Mar 2010 09:49:00 -0400 From: Mark Jones To: "dime@ietf.org" Date: Wed, 31 Mar 2010 09:48:59 -0400 Thread-Topic: NAPTR fix for 3588bis Thread-Index: AcrQ2OoOkkvS5kgdQTWGX10AFAOdng== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [Dime] NAPTR fix for 3588bis X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2010 13:48:33 -0000 Here are the proposed changes to 3588bis to implement the fix for the NAPTR= issues discussed at IETF#77 (see http://www.ietf.org/proceedings/10mar/sli= des/dime-5.pdf). Comments appreciated. There was some discussion at the meeting of creating S-NAPTR Application Se= rvice Tag entries for the unregistered NAPTR values in RFC3588 ("AAA+D2x").= No consensus was reached but my impression was that we were leaning toward= s NOT creating these entries. That would be my preference too but are there= any objections on the list? Regards Mark ************************* FIRST CHANGE ************************* Section 5.2 Diameter Peer Discovery =3D> Replace step 2 with the following text: 2. The Diameter implementation performs a NAPTR query for a server in a particular realm. The Diameter implementation has to know in advance which realm to look for a Diameter agent in. This could be deduced, for example, from the 'realm' in a NAI that a Diameter implementation needed to perform a Diameter operation on. The NAPTR usage in Diameter follows the S-NAPTR DDDS application=20 [RFC3958] which means that the SERVICE field includes tags for the=20 desired application and supported application protocol. The application service tag for a Diameter application is 'aaa' and= =20 the supported application protocol tags are 'diameter.tcp',=20 'diameter.sctp' or 'diameter.tls'.=20 The client follows the resolution process defined by the S-NAPTR=20 DDDS [RFC3958] application to find a matching SRV or A record of=20 a suitable peer. The domain suffixes in the NAPTR replacement field SHOULD match the domain of the original query. ************************* SECOND CHANGE ************************* Section 11.6 NAPTR Service Fields =3D> Rename this section to S-NAPTR Parameters and replace content with: This document registers a S-NAPTR Application Service Tag value of "aaa". This document also registers the following S-NAPTR Application Protocol Tag= s: Tag | Protocol ---------------|--------- diameter.tcp | TCP diameter.sctp | SCTP diameter.tls | TLS ************************* THIRD CHANGE ************************** Appendix B. NAPTR Example =3D> Rename section to S-NAPTR Example and modify as follows. As an example, consider a client that wishes to resolve aaa: example.com. The client performs a NAPTR query for that domain, and the following NAPTR records are returned: ;; order pref flags service regexp replacement IN NAPTR 50 50 "s" "aaa:diameter.tls" "" _diameter._tls.examp= le.com IN NAPTR 100 50 "s" "aaa:diameter.tcp" "" _aaa._tcp.example.co= m IN NAPTR 150 50 "s" "aaa:diameter.sctp" "" _diameter._sctp.exam= ple.com This indicates that the server supports TLS, TCP and SCTP in that order. If the client supports TLS, TLS will be used, targeted to a host determined by an SRV lookup of _diameter._tls.example.com. That lookup would return: ;; Priority Weight Port Target IN SRV 0 1 5060 server1.example.com IN SRV 0 2 5060 server2.example.com ************************* FOURTH CHANGE ************************** 14.1. Normative References =3D> Add new reference to S-NAPTR DDDS RFC3958. ************************* END OF CHANGES *********************** From tom111.taylor@bell.net Wed Mar 31 06:50:50 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 68A723A67B6 for ; Wed, 31 Mar 2010 06:50:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.934 X-Spam-Level: * X-Spam-Status: No, score=1.934 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, MSGID_FROM_MTA_HEADER=0.803] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pz-PHBWpFO0H for ; Wed, 31 Mar 2010 06:50:49 -0700 (PDT) Received: from blu0-omc3-s37.blu0.hotmail.com (blu0-omc3-s37.blu0.hotmail.com [65.55.116.112]) by core3.amsl.com (Postfix) with ESMTP id 90A8F3A679C for ; Wed, 31 Mar 2010 06:50:49 -0700 (PDT) Received: from BLU0-SMTP10 ([65.55.116.73]) by blu0-omc3-s37.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 31 Mar 2010 06:51:20 -0700 X-Originating-IP: [74.12.183.53] X-Originating-Email: [tom111.taylor@bell.net] Message-ID: Received: from [192.168.2.11] ([74.12.183.53]) by BLU0-SMTP10.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 31 Mar 2010 06:51:20 -0700 Date: Wed, 31 Mar 2010 09:51:17 -0400 From: Tom Taylor User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Naveen Kottapalli References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 31 Mar 2010 13:51:20.0372 (UTC) FILETIME=[3E367F40:01CAD0D9] Cc: dime@ietf.org Subject: Re: [Dime] Message mis-sequencing over SCTP X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2010 13:50:50 -0000 Sounds like a good point. Seems to me the rules should be: - use only stream 0 until the Diameter connection has been set up - all messages relating to the same session must use the same stream. That should be added to section 2.1.1. Naveen Kottapalli wrote: > Hi, > > Am just wondering whether the mis-sequencing in the delivery of packets when > SCTP is being used as transport layer would cause any problem. For example, > take an association with 5 out-streams to send out the Diameter messages. > Immediately after sending CEA on stream 0, all other messages are sent over > other streams like 1, 2, 3, and 4. > > There is a chance that the other Diameter messages will reach the peer > before the CEA is processed? Does the existing draft miss the sequencing > problem over SCTP? > > Yours, > Naveen. > > > > ------------------------------------------------------------------------ > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Wed Mar 31 09:23:57 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78DDA3A6B0B for ; Wed, 31 Mar 2010 09:23:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.269 X-Spam-Level: X-Spam-Status: No, score=-0.269 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_83=0.6, J_CHICKENPOX_84=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s23MCUyYHOrK for ; Wed, 31 Mar 2010 09:23:56 -0700 (PDT) Received: from mail-bw0-f217.google.com (mail-bw0-f217.google.com [209.85.218.217]) by core3.amsl.com (Postfix) with ESMTP id 1FD193A6A71 for ; Wed, 31 Mar 2010 09:20:00 -0700 (PDT) Received: by bwz9 with SMTP id 9so215494bwz.29 for ; Wed, 31 Mar 2010 09:20:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=3ALWoMP1jpPtvHNAHqlIeMUhI2Hf5rJURs8PmxEHpqE=; b=XMWMz89wobMmCeCOi+5ujWRIEmJ4zjhE2E22ol1L6JxiDZVEyJmTNXFjdR5ftpUljW tH5NpatktQ18u3Z8bkhXHkG0/ejdxoQ5Z1cpXObFPnFfNK8L1v2r/6/ld3/6Hni7SHLf JlMLFj2KGo4HUuz1eO6UAqaIVfeYK2dVSHXts= DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=AU7+CnqHiSwlol7kcGPSEl+72LPcyIJ6/U8T4bUGSMozTgg5yA8KV6LAZAWRUWaVbm fDDqqHMaWKW9x06CumP8SdWY5oSu2n6m2PpK60YuqleHzV4OhPPcSHIuOMZ66uSU2QIW MmydSIfc4VlfllL1Hv5ead6y+cnBcp+0V1pHk= Received: by 10.204.134.211 with SMTP id k19mr2069927bkt.48.1270052428461; Wed, 31 Mar 2010 09:20:28 -0700 (PDT) Received: from a88-114-167-158.elisa-laajakaista.fi (a88-114-167-158.elisa-laajakaista.fi [88.114.167.158]) by mx.google.com with ESMTPS id 14sm3551858bwz.2.2010.03.31.09.20.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 31 Mar 2010 09:20:27 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: Date: Wed, 31 Mar 2010 19:20:25 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <082F9E86-364B-4535-A54D-F6759B33E023@gmail.com> References: To: Mark Jones X-Mailer: Apple Mail (2.1077) Cc: "dime@ietf.org" Subject: Re: [Dime] NAPTR fix for 3588bis X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2010 16:23:57 -0000 Hi, Thanks Mark for initiating the discussion and proposing text. My initial = comments inline. On Mar 31, 2010, at 4:48 PM, Mark Jones wrote: > Here are the proposed changes to 3588bis to implement the fix for the = NAPTR issues discussed at IETF#77 (see = http://www.ietf.org/proceedings/10mar/slides/dime-5.pdf). >=20 > Comments appreciated. >=20 > There was some discussion at the meeting of creating S-NAPTR = Application Service Tag entries for the unregistered NAPTR values in = RFC3588 ("AAA+D2x"). No consensus was reached but my impression was that = we were leaning towards NOT creating these entries. That would be my = preference too but are there any objections on the list? Would be ok I think.. However, I really would like to see even some = discussion related to them _somewhere_. Any ideas? Would an errata be = enough to cover that? >=20 > Regards > Mark >=20 > ************************* FIRST CHANGE ************************* >=20 > Section 5.2 Diameter Peer Discovery >=20 > =3D> Replace step 2 with the following text: >=20 > 2. The Diameter implementation performs a NAPTR query for a server > in a particular realm. The Diameter implementation has to know > in advance which realm to look for a Diameter agent in. This > could be deduced, for example, from the 'realm' in a NAI that a > Diameter implementation needed to perform a Diameter operation > on. >=20 > The NAPTR usage in Diameter follows the S-NAPTR DDDS application=20= > [RFC3958] which means that the SERVICE field includes tags for = the=20 > desired application and supported application protocol. > The application service tag for a Diameter application is 'aaa' = and=20 > the supported application protocol tags are 'diameter.tcp',=20 > 'diameter.sctp' or 'diameter.tls'.=20 RFC3958 ABNF does not allow "." in iana-registered-protocol, so the = application protocol has to be changed, like "diametertcp" or "dtcp" = etc.. >=20 > The client follows the resolution process defined by the S-NAPTR=20= > DDDS [RFC3958] application to find a matching SRV or A record of=20= > a suitable peer. The domain suffixes in the NAPTR replacement = field > SHOULD match the domain of the original query. >=20 >=20 > ************************* SECOND CHANGE ************************* >=20 > Section 11.6 NAPTR Service Fields >=20 > =3D> Rename this section to S-NAPTR Parameters and replace content = with: >=20 > This document registers a S-NAPTR Application Service Tag value of = "aaa". >=20 > This document also registers the following S-NAPTR Application = Protocol Tags: >=20 > Tag | Protocol > ---------------|--------- > diameter.tcp | TCP > diameter.sctp | SCTP > diameter.tls | TLS See my note above regarding the application protocol. >=20 > ************************* THIRD CHANGE ************************** >=20 > Appendix B. NAPTR Example >=20 > =3D> Rename section to S-NAPTR Example and modify as follows. >=20 > As an example, consider a client that wishes to resolve aaa: > example.com. The client performs a NAPTR query for that domain, and > the following NAPTR records are returned: >=20 > ;; order pref flags service regexp replacement > IN NAPTR 50 50 "s" "aaa:diameter.tls" "" = _diameter._tls.example.com > IN NAPTR 100 50 "s" "aaa:diameter.tcp" "" = _aaa._tcp.example.com > IN NAPTR 150 50 "s" "aaa:diameter.sctp" "" = _diameter._sctp.example.com And lets have an example of "a" flag as well: IN NAPTR 150 50 "a" "aaa:diametertls" "" server1.example.com IN NAPTR 150 50 "a" "aaa:diametertls" "" server2.example.com >=20 > This indicates that the server supports TLS, TCP and SCTP in that > order. If the client supports TLS, TLS will be used, targeted to a > host determined by an SRV lookup of _diameter._tls.example.com. = That > lookup would return: >=20 > ;; Priority Weight Port Target > IN SRV 0 1 5060 server1.example.com > IN SRV 0 2 5060 server2.example.com >=20 >=20 > ************************* FOURTH CHANGE ************************** >=20 > 14.1. Normative References >=20 > =3D> Add new reference to S-NAPTR DDDS RFC3958. >=20 > ************************* END OF CHANGES *********************** - Jouni >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From Mark.Jones@bridgewatersystems.com Wed Mar 31 11:32:04 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 113403A67B2 for ; Wed, 31 Mar 2010 11:32:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.966 X-Spam-Level: X-Spam-Status: No, score=-3.966 tagged_above=-999 required=5 tests=[AWL=0.304, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_83=0.6, J_CHICKENPOX_84=0.6, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-Og9KbyFo9i for ; Wed, 31 Mar 2010 11:32:02 -0700 (PDT) Received: from mail51.messagelabs.com (mail51.messagelabs.com [216.82.241.99]) by core3.amsl.com (Postfix) with ESMTP id 585D23A6A2A for ; Wed, 31 Mar 2010 11:32:02 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: Mark.Jones@bridgewatersystems.com X-Msg-Ref: server-8.tower-51.messagelabs.com!1270060352!32503630!1 X-StarScan-Version: 6.2.4; banners=-,-,- X-Originating-IP: [72.35.6.119] Received: (qmail 18029 invoked from network); 31 Mar 2010 18:32:33 -0000 Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-8.tower-51.messagelabs.com with RC4-SHA encrypted SMTP; 31 Mar 2010 18:32:33 -0000 Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Wed, 31 Mar 2010 14:32:32 -0400 From: Mark Jones To: jouni korhonen Date: Wed, 31 Mar 2010 14:32:29 -0400 Thread-Topic: [Dime] NAPTR fix for 3588bis Thread-Index: AcrQ7lmZpnDp2WD3Qoa3CaP20gcAJgADGixQ Message-ID: References: <082F9E86-364B-4535-A54D-F6759B33E023@gmail.com> In-Reply-To: <082F9E86-364B-4535-A54D-F6759B33E023@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dime@ietf.org" Subject: Re: [Dime] NAPTR fix for 3588bis X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2010 18:32:04 -0000 Thanks for the feedback, Jouni. Responses inline. > -----Original Message----- > From: jouni korhonen [mailto:jouni.nospam@gmail.com] > Sent: March 31, 2010 12:20 PM > To: Mark Jones > Cc: dime@ietf.org > Subject: Re: [Dime] NAPTR fix for 3588bis >=20 > Hi, >=20 > Thanks Mark for initiating the discussion and proposing text. My > initial comments inline. >=20 > On Mar 31, 2010, at 4:48 PM, Mark Jones wrote: >=20 > > Here are the proposed changes to 3588bis to implement the fix for the > NAPTR issues discussed at IETF#77 (see > http://www.ietf.org/proceedings/10mar/slides/dime-5.pdf). > > > > Comments appreciated. > > > > There was some discussion at the meeting of creating S-NAPTR > Application Service Tag entries for the unregistered NAPTR values in > RFC3588 ("AAA+D2x"). No consensus was reached but my impression was > that we were leaning towards NOT creating these entries. That would be > my preference too but are there any objections on the list? >=20 > Would be ok I think.. However, I really would like to see even some > discussion related to them _somewhere_. Any ideas? Would an errata be > enough to cover that? >=20 I do agree this change needs to be discussed but I assumed we were going to= have that discussion _here_ on this list. If the errata review procedure i= s likely to generate more discussion then I'm all for it. >=20 > > > > Regards > > Mark > > > > ************************* FIRST CHANGE ************************* > > > > Section 5.2 Diameter Peer Discovery > > > > =3D> Replace step 2 with the following text: > > > > 2. The Diameter implementation performs a NAPTR query for a server > > in a particular realm. The Diameter implementation has to know > > in advance which realm to look for a Diameter agent in. This > > could be deduced, for example, from the 'realm' in a NAI that a > > Diameter implementation needed to perform a Diameter operation > > on. > > > > The NAPTR usage in Diameter follows the S-NAPTR DDDS > application > > [RFC3958] which means that the SERVICE field includes tags for > the > > desired application and supported application protocol. > > The application service tag for a Diameter application is 'aaa' > and > > the supported application protocol tags are 'diameter.tcp', > > 'diameter.sctp' or 'diameter.tls'. >=20 > RFC3958 ABNF does not allow "." in iana-registered-protocol, so the > application protocol has to be changed, like "diametertcp" or "dtcp" > etc.. >=20 Lucky for us that IANA is ignoring the RFC3958 ABNF then :) http://www.iana.org/assignments/s-naptr-parameters/s-naptr-parameters.xhtml Another errata perhaps? iana-registered-protocol =3D ALPHA *31ALPHANUMSYM > > > > The client follows the resolution process defined by the S- > NAPTR > > DDDS [RFC3958] application to find a matching SRV or A record > of > > a suitable peer. The domain suffixes in the NAPTR replacement > field > > SHOULD match the domain of the original query. > > > > > > ************************* SECOND CHANGE ************************* > > > > Section 11.6 NAPTR Service Fields > > > > =3D> Rename this section to S-NAPTR Parameters and replace content > with: > > > > This document registers a S-NAPTR Application Service Tag value of > "aaa". > > > > This document also registers the following S-NAPTR Application > Protocol Tags: > > > > Tag | Protocol > > ---------------|--------- > > diameter.tcp | TCP > > diameter.sctp | SCTP > > diameter.tls | TLS >=20 > See my note above regarding the application protocol. >=20 >=20 > > > > ************************* THIRD CHANGE ************************** > > > > Appendix B. NAPTR Example > > > > =3D> Rename section to S-NAPTR Example and modify as follows. > > > > As an example, consider a client that wishes to resolve aaa: > > example.com. The client performs a NAPTR query for that domain, > and > > the following NAPTR records are returned: > > > > ;; order pref flags service regexp replacement > > IN NAPTR 50 50 "s" "aaa:diameter.tls" "" > _diameter._tls.example.com > > IN NAPTR 100 50 "s" "aaa:diameter.tcp" "" > _aaa._tcp.example.com > > IN NAPTR 150 50 "s" "aaa:diameter.sctp" "" > _diameter._sctp.example.com >=20 > And lets have an example of "a" flag as well: >=20 > IN NAPTR 150 50 "a" "aaa:diametertls" "" server1.example.com > IN NAPTR 150 50 "a" "aaa:diametertls" "" server2.example.com >=20 Fine by me. >=20 > > > > This indicates that the server supports TLS, TCP and SCTP in that > > order. If the client supports TLS, TLS will be used, targeted to a > > host determined by an SRV lookup of _diameter._tls.example.com. > That > > lookup would return: > > > > ;; Priority Weight Port Target > > IN SRV 0 1 5060 server1.example.com > > IN SRV 0 2 5060 server2.example.com > > > > > > ************************* FOURTH CHANGE ************************** > > > > 14.1. Normative References > > > > =3D> Add new reference to S-NAPTR DDDS RFC3958. > > > > ************************* END OF CHANGES *********************** >=20 > - Jouni >=20 >=20 >=20 > > > > _______________________________________________ > > DiME mailing list > > DiME@ietf.org > > https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Wed Mar 31 11:46:42 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AD0E3A67B1 for ; Wed, 31 Mar 2010 11:46:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.269 X-Spam-Level: X-Spam-Status: No, score=-0.269 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_83=0.6, J_CHICKENPOX_84=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J6lwYBxAB3Kv for ; Wed, 31 Mar 2010 11:46:40 -0700 (PDT) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by core3.amsl.com (Postfix) with ESMTP id 7C3E03A6A2F for ; Wed, 31 Mar 2010 11:46:40 -0700 (PDT) Received: by fxm27 with SMTP id 27so351440fxm.28 for ; Wed, 31 Mar 2010 11:47:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=dwQhsAtCEolmGg47LqCHB2UlcJTi7Y3idY9o1kkk0xU=; b=rSAztFj9J3+dExnYuZZqspQHwrA8AvGAbhePXWLXK5NKdSubEYLi1r7oZ6OqHSSlKC paKMWlBNm5090WZzXKGvzb6KJTUUwwEwsUE/t4v5TbVOosMpRX/jc2Me/Rhlt5hdRSCH 35DBvoQdx8byp9aYrgabrqA9f72jTuh7Fss6Y= DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=MYpnxvQZeuKmogI5+NiKlfQxqy8C1oVuYHv+8Ih/WFdPPCKrucDWai6AMt4pmIjzdx UC6+B9imSrksHlR0lHz9A2QBTymklixdgQHMAXUlg8ft4LbQaLDClqv4S1BvFNLQs84N lYCrti7FjewJsrh6dw22kAff6DUA+FU+rxVZE= Received: by 10.223.7.91 with SMTP id c27mr8888001fac.19.1270061220843; Wed, 31 Mar 2010 11:47:00 -0700 (PDT) Received: from a88-114-167-158.elisa-laajakaista.fi (a88-114-167-158.elisa-laajakaista.fi [88.114.167.158]) by mx.google.com with ESMTPS id 18sm560603fks.5.2010.03.31.11.46.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 31 Mar 2010 11:46:59 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: Date: Wed, 31 Mar 2010 21:46:57 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <619BD781-223A-433C-BCE0-2B8803D2193B@gmail.com> References: <082F9E86-364B-4535-A54D-F6759B33E023@gmail.com> To: Mark Jones X-Mailer: Apple Mail (2.1077) Cc: "dime@ietf.org" Subject: Re: [Dime] NAPTR fix for 3588bis X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2010 18:46:42 -0000 Hi, On Mar 31, 2010, at 9:32 PM, Mark Jones wrote: > Thanks for the feedback, Jouni. Responses inline. >=20 >> -----Original Message----- >> From: jouni korhonen [mailto:jouni.nospam@gmail.com] >> Sent: March 31, 2010 12:20 PM >> To: Mark Jones >> Cc: dime@ietf.org >> Subject: Re: [Dime] NAPTR fix for 3588bis >>=20 >> Hi, >>=20 >> Thanks Mark for initiating the discussion and proposing text. My >> initial comments inline. >>=20 >> On Mar 31, 2010, at 4:48 PM, Mark Jones wrote: >>=20 >>> Here are the proposed changes to 3588bis to implement the fix for = the >> NAPTR issues discussed at IETF#77 (see >> http://www.ietf.org/proceedings/10mar/slides/dime-5.pdf). >>>=20 >>> Comments appreciated. >>>=20 >>> There was some discussion at the meeting of creating S-NAPTR >> Application Service Tag entries for the unregistered NAPTR values in >> RFC3588 ("AAA+D2x"). No consensus was reached but my impression was >> that we were leaning towards NOT creating these entries. That would = be >> my preference too but are there any objections on the list? >>=20 >> Would be ok I think.. However, I really would like to see even some >> discussion related to them _somewhere_. Any ideas? Would an errata be >> enough to cover that? >>=20 >=20 > I do agree this change needs to be discussed but I assumed we were = going to have that discussion _here_ on this list. If the errata review = procedure is likely to generate more discussion then I'm all for it. Right. I have no idea how the errata stuff actually works in practice = but we should, of course, first have a common agreement on the list. >=20 >>=20 >>>=20 >>> Regards >>> Mark >>>=20 >>> ************************* FIRST CHANGE ************************* >>>=20 >>> Section 5.2 Diameter Peer Discovery >>>=20 >>> =3D> Replace step 2 with the following text: >>>=20 >>> 2. The Diameter implementation performs a NAPTR query for a server >>> in a particular realm. The Diameter implementation has to know >>> in advance which realm to look for a Diameter agent in. This >>> could be deduced, for example, from the 'realm' in a NAI that a >>> Diameter implementation needed to perform a Diameter operation >>> on. >>>=20 >>> The NAPTR usage in Diameter follows the S-NAPTR DDDS >> application >>> [RFC3958] which means that the SERVICE field includes tags for >> the >>> desired application and supported application protocol. >>> The application service tag for a Diameter application is 'aaa' >> and >>> the supported application protocol tags are 'diameter.tcp', >>> 'diameter.sctp' or 'diameter.tls'. >>=20 >> RFC3958 ABNF does not allow "." in iana-registered-protocol, so the >> application protocol has to be changed, like "diametertcp" or "dtcp" >> etc.. >>=20 >=20 > Lucky for us that IANA is ignoring the RFC3958 ABNF then :) >=20 > = http://www.iana.org/assignments/s-naptr-parameters/s-naptr-parameters.xhtm= l >=20 > Another errata perhaps? >=20 > iana-registered-protocol =3D ALPHA *31ALPHANUMSYM Great to see even RFC3958 authors do not follow the ABNF they created in = later RFCs. RFC3958 already has an errata that says the ALPHANUM = definition for iana-registered-protocol is missing and proposes one as a = solution. Maybe we just have to carry on the tradition of dodgy IANA = DNS definitions in Diameter ;) - Jouni >=20 >>>=20 >>> The client follows the resolution process defined by the S- >> NAPTR >>> DDDS [RFC3958] application to find a matching SRV or A record >> of >>> a suitable peer. The domain suffixes in the NAPTR replacement >> field >>> SHOULD match the domain of the original query. >>>=20 >>>=20 >>> ************************* SECOND CHANGE ************************* >>>=20 >>> Section 11.6 NAPTR Service Fields >>>=20 >>> =3D> Rename this section to S-NAPTR Parameters and replace content >> with: >>>=20 >>> This document registers a S-NAPTR Application Service Tag value of >> "aaa". >>>=20 >>> This document also registers the following S-NAPTR Application >> Protocol Tags: >>>=20 >>> Tag | Protocol >>> ---------------|--------- >>> diameter.tcp | TCP >>> diameter.sctp | SCTP >>> diameter.tls | TLS >>=20 >> See my note above regarding the application protocol. >>=20 >>=20 >>>=20 >>> ************************* THIRD CHANGE ************************** >>>=20 >>> Appendix B. NAPTR Example >>>=20 >>> =3D> Rename section to S-NAPTR Example and modify as follows. >>>=20 >>> As an example, consider a client that wishes to resolve aaa: >>> example.com. The client performs a NAPTR query for that domain, >> and >>> the following NAPTR records are returned: >>>=20 >>> ;; order pref flags service regexp replacement >>> IN NAPTR 50 50 "s" "aaa:diameter.tls" "" >> _diameter._tls.example.com >>> IN NAPTR 100 50 "s" "aaa:diameter.tcp" "" >> _aaa._tcp.example.com >>> IN NAPTR 150 50 "s" "aaa:diameter.sctp" "" >> _diameter._sctp.example.com >>=20 >> And lets have an example of "a" flag as well: >>=20 >> IN NAPTR 150 50 "a" "aaa:diametertls" "" = server1.example.com >> IN NAPTR 150 50 "a" "aaa:diametertls" "" = server2.example.com >>=20 >=20 > Fine by me. >=20 >>=20 >>>=20 >>> This indicates that the server supports TLS, TCP and SCTP in that >>> order. If the client supports TLS, TLS will be used, targeted to a >>> host determined by an SRV lookup of _diameter._tls.example.com. >> That >>> lookup would return: >>>=20 >>> ;; Priority Weight Port Target >>> IN SRV 0 1 5060 server1.example.com >>> IN SRV 0 2 5060 server2.example.com >>>=20 >>>=20 >>> ************************* FOURTH CHANGE ************************** >>>=20 >>> 14.1. Normative References >>>=20 >>> =3D> Add new reference to S-NAPTR DDDS RFC3958. >>>=20 >>> ************************* END OF CHANGES *********************** >>=20 >> - Jouni >>=20 >>=20 >>=20 >>>=20 >>> _______________________________________________ >>> DiME mailing list >>> DiME@ietf.org >>> https://www.ietf.org/mailman/listinfo/dime >=20 From jouni.nospam@gmail.com Wed Mar 31 12:08:18 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B5533A69A2 for ; Wed, 31 Mar 2010 12:08:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.269 X-Spam-Level: X-Spam-Status: No, score=-0.269 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_83=0.6, J_CHICKENPOX_84=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y0v5LHGZ0J8I for ; Wed, 31 Mar 2010 12:08:17 -0700 (PDT) Received: from mail-bw0-f217.google.com (mail-bw0-f217.google.com [209.85.218.217]) by core3.amsl.com (Postfix) with ESMTP id 9F3303A6A46 for ; Wed, 31 Mar 2010 12:08:14 -0700 (PDT) Received: by bwz9 with SMTP id 9so338264bwz.29 for ; Wed, 31 Mar 2010 12:08:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=3P5Porq7p0oh7zEd481cmK7nNDGJz5DW1JiD5I1hN4w=; b=KFcDINFzcdS0MTl3PVj6uGsMCBdAqLvXpjOQ3/j15XxD+yKdxkJ2i+8X5BI3cJo22X E7qD+bfmVkh7WO8OiwbC5GdHpfy1oxFe2B7ezxE/NwkAI/GFjaXxder/MwaOkX15BJUD oIDmY4sbgw/bR9Kb0c/4RoQpuwiE7qF7+GkMo= DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=V5/67iYKlXH32UlcECTv3hdgsZJvHihrY456klTVzF4jeCFf2clnJxCSi80j248jsl trADxC9eMqsWecGBNyv/OsEsAiL/77BxyhKL0E3GjLixnAZEE/621hGAnnKmHZMq4KD1 sxPtiFky4aTy3z9TcfW16GeafhCfmLFraIud4= Received: by 10.204.156.22 with SMTP id u22mr33567bkw.24.1270062521765; Wed, 31 Mar 2010 12:08:41 -0700 (PDT) Received: from a88-114-167-158.elisa-laajakaista.fi (a88-114-167-158.elisa-laajakaista.fi [88.114.167.158]) by mx.google.com with ESMTPS id 16sm3599767bwz.13.2010.03.31.12.08.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 31 Mar 2010 12:08:41 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: Date: Wed, 31 Mar 2010 22:08:39 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: <082F9E86-364B-4535-A54D-F6759B33E023@gmail.com> To: Mark Jones X-Mailer: Apple Mail (2.1077) Cc: "dime@ietf.org" Subject: Re: [Dime] NAPTR fix for 3588bis X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2010 19:08:18 -0000 [snip] >>> desired application and supported application protocol. >>> The application service tag for a Diameter application is 'aaa' >> and >>> the supported application protocol tags are 'diameter.tcp', >>> 'diameter.sctp' or 'diameter.tls'. >>=20 >> RFC3958 ABNF does not allow "." in iana-registered-protocol, so the >> application protocol has to be changed, like "diametertcp" or "dtcp" >> etc.. >>=20 >=20 > Lucky for us that IANA is ignoring the RFC3958 ABNF then :) >=20 > = http://www.iana.org/assignments/s-naptr-parameters/s-naptr-parameters.xhtm= l >=20 > Another errata perhaps? >=20 > iana-registered-protocol =3D ALPHA *31ALPHANUMSYM More on this topic.. RFC3958 itself contain examples that go against the = ABNF. So, I _guess_ it is ok for us to assume that "iana-registered-protocol =3D ALPHA *31ALPHANUM" is actually "iana-registered-protocol =3D ALPHA *31ALPHANUMSYM" - Jouni >=20 >>>=20 >>> The client follows the resolution process defined by the S- >> NAPTR >>> DDDS [RFC3958] application to find a matching SRV or A record >> of >>> a suitable peer. The domain suffixes in the NAPTR replacement >> field >>> SHOULD match the domain of the original query. >>>=20 >>>=20 >>> ************************* SECOND CHANGE ************************* >>>=20 >>> Section 11.6 NAPTR Service Fields >>>=20 >>> =3D> Rename this section to S-NAPTR Parameters and replace content >> with: >>>=20 >>> This document registers a S-NAPTR Application Service Tag value of >> "aaa". >>>=20 >>> This document also registers the following S-NAPTR Application >> Protocol Tags: >>>=20 >>> Tag | Protocol >>> ---------------|--------- >>> diameter.tcp | TCP >>> diameter.sctp | SCTP >>> diameter.tls | TLS >>=20 >> See my note above regarding the application protocol. >>=20 >>=20 >>>=20 >>> ************************* THIRD CHANGE ************************** >>>=20 >>> Appendix B. NAPTR Example >>>=20 >>> =3D> Rename section to S-NAPTR Example and modify as follows. >>>=20 >>> As an example, consider a client that wishes to resolve aaa: >>> example.com. The client performs a NAPTR query for that domain, >> and >>> the following NAPTR records are returned: >>>=20 >>> ;; order pref flags service regexp replacement >>> IN NAPTR 50 50 "s" "aaa:diameter.tls" "" >> _diameter._tls.example.com >>> IN NAPTR 100 50 "s" "aaa:diameter.tcp" "" >> _aaa._tcp.example.com >>> IN NAPTR 150 50 "s" "aaa:diameter.sctp" "" >> _diameter._sctp.example.com >>=20 >> And lets have an example of "a" flag as well: >>=20 >> IN NAPTR 150 50 "a" "aaa:diametertls" "" = server1.example.com >> IN NAPTR 150 50 "a" "aaa:diametertls" "" = server2.example.com >>=20 >=20 > Fine by me. >=20 >>=20 >>>=20 >>> This indicates that the server supports TLS, TCP and SCTP in that >>> order. If the client supports TLS, TLS will be used, targeted to a >>> host determined by an SRV lookup of _diameter._tls.example.com. >> That >>> lookup would return: >>>=20 >>> ;; Priority Weight Port Target >>> IN SRV 0 1 5060 server1.example.com >>> IN SRV 0 2 5060 server2.example.com >>>=20 >>>=20 >>> ************************* FOURTH CHANGE ************************** >>>=20 >>> 14.1. Normative References >>>=20 >>> =3D> Add new reference to S-NAPTR DDDS RFC3958. >>>=20 >>> ************************* END OF CHANGES *********************** >>=20 >> - Jouni >>=20 >>=20 >>=20 >>>=20 >>> _______________________________________________ >>> DiME mailing list >>> DiME@ietf.org >>> https://www.ietf.org/mailman/listinfo/dime >=20 From naveen.sarma@gmail.com Wed Mar 31 13:08:33 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E7C523A682C for ; Wed, 31 Mar 2010 13:08:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.168 X-Spam-Level: X-Spam-Status: No, score=-0.168 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZoO7D9ap4lpr for ; Wed, 31 Mar 2010 13:08:33 -0700 (PDT) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id E6A3B3A6807 for ; Wed, 31 Mar 2010 13:08:32 -0700 (PDT) Received: by vws9 with SMTP id 9so241636vws.31 for ; Wed, 31 Mar 2010 13:09:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:content-type; bh=TKBI/WCWo+EefL/zGxg7oM8pmYap28/V9Hzjo+etLNI=; b=u3jNr7Nr5mxK994DvNx+jslAvCEIzBCTs+eRvR1Or5olmvNRceXA/nSMgi3qk8s+jH BSKzUqEOgzrE9ghVLIWGCwQGpltxD2hj4Aw/K3QPDOEXXeWKAEn5/OVNR9q7V8vCdUiG MWJ7WPgMX9OAnjMuzlU5TT90HbQsw3ZVgBKkc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=D/FDxRzxBZGrKY7yfw9rwsJ4DPCF5rrbZgKhUsfulpmBIrf63+ywKf6ED2y8f36u2o w7Q7Wa++ocV+6gda0U4061kL5G+NpSuyBTX6KyhJ6OgNpJskOxJ4eknwdHY/JCrY/Ss5 puJJBQmUfj1xHGwRQCotKjKJIhYjZ1rbtZwrY= MIME-Version: 1.0 Received: by 10.220.125.78 with HTTP; Wed, 31 Mar 2010 13:08:40 -0700 (PDT) In-Reply-To: References: From: Naveen Kottapalli Date: Wed, 31 Mar 2010 21:08:40 +0100 Received: by 10.220.107.167 with SMTP id b39mr4502245vcp.16.1270066140173; Wed, 31 Mar 2010 13:09:00 -0700 (PDT) Message-ID: To: dime@ietf.org Content-Type: multipart/alternative; boundary=00c09f8fe4502059c304831e5148 Subject: Re: [Dime] Message mis-sequencing over SCTP X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2010 20:08:34 -0000 --00c09f8fe4502059c304831e5148 Content-Type: text/plain; charset=ISO-8859-1 I feel, we can handle the same way as SIGTRAN is handling. Yours, Naveen. On 31 March 2010 14:51, Tom Taylor wrote: > Sounds like a good point. Seems to me the rules should be: > > - use only stream 0 until the Diameter connection has been set up > - all messages relating to the same session must use the same stream. > > That should be added to section 2.1.1. > > > Naveen Kottapalli wrote: > >> Hi, >> >> Am just wondering whether the mis-sequencing in the delivery of packets >> when >> SCTP is being used as transport layer would cause any problem. For >> example, >> take an association with 5 out-streams to send out the Diameter messages. >> Immediately after sending CEA on stream 0, all other messages are sent >> over >> other streams like 1, 2, 3, and 4. >> >> There is a chance that the other Diameter messages will reach the peer >> before the CEA is processed? Does the existing draft miss the sequencing >> problem over SCTP? >> >> Yours, >> Naveen. >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime >> > --00c09f8fe4502059c304831e5148 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I feel, we=A0can handle the same way as SIGTRAN is handling.

Yours,
Naveen.

On 31 March 2010 14:51, Tom Taylor <tom111= .taylor@bell.net> wrote:
Sounds like a good point. Seems = to me the rules should be:

=A0- use only stream 0 until the Diameter= connection has been set up
=A0- all messages relating to the same session must use the same stream.
That should be added to section 2.1.1.


Naveen Kottapalli wr= ote:
Hi,

Am just wondering whether the mis-sequencing in the deliver= y of packets when
SCTP is being used as transport layer would cause any = problem. =A0For example,
take an association with 5 out-streams to send = out the Diameter messages.
Immediately after sending CEA on stream 0, all other messages are sent over=
other streams like 1, 2, 3, and 4.

There is a chance that the ot= her Diameter messages will reach the peer
before the CEA is processed? = =A0 Does the existing draft miss the sequencing
problem over SCTP?

Yours,
Naveen.



----= --------------------------------------------------------------------
_______________________________________________
DiME mailing list
DiME@ietf.org
https= ://www.ietf.org/mailman/listinfo/dime


--00c09f8fe4502059c304831e5148-- From sdecugis@nict.go.jp Wed Mar 31 18:45:47 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97B303A6916 for ; Wed, 31 Mar 2010 18:45:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.225 X-Spam-Level: X-Spam-Status: No, score=-0.225 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_JP=1.244] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jv+0oVx3siOk for ; Wed, 31 Mar 2010 18:45:46 -0700 (PDT) Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:2f8:29::3]) by core3.amsl.com (Postfix) with ESMTP id B1E013A68E3 for ; Wed, 31 Mar 2010 18:45:45 -0700 (PDT) Received: from gw2.nict.go.jp (gw2 [133.243.18.251]) by ns2.nict.go.jp with ESMTP id o311kEt3023980 for ; Thu, 1 Apr 2010 10:46:14 +0900 (JST) Received: from gw2.nict.go.jp (localhost [127.0.0.1]) by gw2.nict.go.jp with ESMTP id o311kEbC014867 for ; Thu, 1 Apr 2010 10:46:14 +0900 (JST) Received: from mail3.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw2.nict.go.jp with ESMTP id o311kECd014864 for ; Thu, 1 Apr 2010 10:46:14 +0900 (JST) Received: from mail3.nict.go.jp (localhost [127.0.0.1]) by mail3.nict.go.jp (NICT Mail) with ESMTP id 121FD5243 for ; Thu, 1 Apr 2010 10:46:14 +0900 (JST) Received: from [133.243.146.171] (5gou2f-dhcp11.nict.go.jp [133.243.146.171]) by mail3.nict.go.jp (NICT Mail) with ESMTP id 0A743195F for ; Thu, 1 Apr 2010 10:46:14 +0900 (JST) Message-ID: <4BB3FAE1.4050503@nict.go.jp> Date: Thu, 01 Apr 2010 10:46:09 +0900 From: Sebastien Decugis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: dime@ietf.org References: In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: id=33D9F61D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: [Dime] Message mis-sequencing over SCTP X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Apr 2010 01:45:47 -0000 Hi, Here is my implementer point of view on this issue: - this issue *does* occur, I saw several messages dropped because of this in my tests. This is problematic because since the connection is not dropped, there is no reason for the sender to re-issue the message. - I fixed the problem by forcing all messages on the responder side to be sent on the same stream as the CEA, until a new message is received from the initiator (so that we are sure the connection is in open state). I am not sure if this is worth mentioning in the document, or if it is considered as an implementation-specific solution. If there is an agreement to add a small paragraph about it in 3588bis, I can volunteer to write a text describing the issue and a solution... Best regards, Sebastien. Le 31/03/2010 22:51, Tom Taylor a écrit : > Sounds like a good point. Seems to me the rules should be: > > - use only stream 0 until the Diameter connection has been set up > - all messages relating to the same session must use the same stream. > > That should be added to section 2.1.1. > > > Naveen Kottapalli wrote: >> Hi, >> >> Am just wondering whether the mis-sequencing in the delivery of >> packets when >> SCTP is being used as transport layer would cause any problem. For >> example, >> take an association with 5 out-streams to send out the Diameter >> messages. >> Immediately after sending CEA on stream 0, all other messages are >> sent over >> other streams like 1, 2, 3, and 4. >> >> There is a chance that the other Diameter messages will reach the peer >> before the CEA is processed? Does the existing draft miss the >> sequencing >> problem over SCTP? >> >> Yours, >> Naveen. >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> 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 > -- Sebastien Decugis Research fellow Network Architecture Group NICT (nict.go.jp) From suckfish@ihug.co.nz Wed Mar 31 20:50:25 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BAE713A6AA8 for ; Wed, 31 Mar 2010 20:50:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.475 X-Spam-Level: X-Spam-Status: No, score=-0.475 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RELAY_IS_203=0.994] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XCUnXflMwjU5 for ; Wed, 31 Mar 2010 20:50:25 -0700 (PDT) Received: from mailfilter68.ihug.co.nz (mailfilter68.ihug.co.nz [203.109.136.68]) by core3.amsl.com (Postfix) with ESMTP id 5AF7D3A6A7B for ; Wed, 31 Mar 2010 20:50:23 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAHu1s0t2XKYT/2dsb2JhbACbOHK1BIUBBIsm X-IronPort-AV: E=Sophos;i="4.51,345,1267354800"; d="scan'208";a="270089935" Received: from 118-92-166-19.dsl.dyn.ihug.co.nz (HELO i.geek.nz) ([118.92.166.19]) by smtp.mailfilter5.ihug.co.nz with SMTP; 01 Apr 2010 16:52:53 +1300 Date: Thu, 1 Apr 2010 16:50:42 +1300 From: Ralph Loader To: Tom Taylor Message-Id: <20100401165042.ac842ead.suckfish@ihug.co.nz> In-Reply-To: References: X-Mailer: Sylpheed 3.0.0 (GTK+ 2.20.0; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dime@ietf.org Subject: Re: [Dime] Message mis-sequencing over SCTP X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Apr 2010 03:50:26 -0000 > Sounds like a good point. Seems to me the rules should be: > > - use only stream 0 until the Diameter connection has been set up > - all messages relating to the same session must use the same stream. Is the second suggested rule (same session must use the same stream) actually of any use? IIRC, in principal, messages on the same session may take different routes to their destination (where multiple Diameter proxies are available) and that makes enforcing ordering on a single hop irrelevant to the session? The Diameter application must either enforce ordering or cope with reordering, anyway? Cheers, Ralph. > > That should be added to section 2.1.1. > > > Naveen Kottapalli wrote: > > Hi, > > > > Am just wondering whether the mis-sequencing in the delivery of packets when > > SCTP is being used as transport layer would cause any problem. For example, > > take an association with 5 out-streams to send out the Diameter messages. > > Immediately after sending CEA on stream 0, all other messages are sent over > > other streams like 1, 2, 3, and 4. > > > > There is a chance that the other Diameter messages will reach the peer > > before the CEA is processed? Does the existing draft miss the sequencing > > problem over SCTP? > > > > Yours, > > Naveen. > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > 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 From sdecugis@nict.go.jp Wed Mar 31 22:39:11 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 876533A6902 for ; Wed, 31 Mar 2010 22:39:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.119 X-Spam-Level: * X-Spam-Status: No, score=1.119 tagged_above=-999 required=5 tests=[AWL=-1.345, BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_JP=1.244, J_CHICKENPOX_83=0.6, J_CHICKENPOX_84=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A4juMokp0seC for ; Wed, 31 Mar 2010 22:39:09 -0700 (PDT) Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:2f8:29::2]) by core3.amsl.com (Postfix) with ESMTP id 937A43A682F for ; Wed, 31 Mar 2010 22:39:08 -0700 (PDT) Received: from gw1.nict.go.jp (gw1 [133.243.18.250]) by ns1.nict.go.jp with ESMTP id o315dcSI020308 for ; Thu, 1 Apr 2010 14:39:38 +0900 (JST) Received: from gw1.nict.go.jp (localhost [127.0.0.1]) by gw1.nict.go.jp with ESMTP id o315dchm002924 for ; Thu, 1 Apr 2010 14:39:38 +0900 (JST) Received: from mail2.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw1.nict.go.jp with ESMTP id o315dcUH002921 for ; Thu, 1 Apr 2010 14:39:38 +0900 (JST) Received: from mail2.nict.go.jp (localhost [127.0.0.1]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 83019163D6 for ; Thu, 1 Apr 2010 14:39:38 +0900 (JST) Received: from [133.243.146.171] (5gou2f-dhcp11.nict.go.jp [133.243.146.171]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 7B3C116099 for ; Thu, 1 Apr 2010 14:39:38 +0900 (JST) Message-ID: <4BB43191.5000505@nict.go.jp> Date: Thu, 01 Apr 2010 14:39:29 +0900 From: Sebastien Decugis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: dime@ietf.org References: In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: id=33D9F61D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Dime] NAPTR fix for 3588bis X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Apr 2010 05:39:11 -0000 Hi, > diameter.tcp | TCP > diameter.sctp | SCTP > diameter.tls | TLS > I still don't understand why TLS is at the same level as TCP and SCTP, while it is actually TLS over TCP or TLS over SCTP. I think that either "secure diameter" (diameters?) or "secure tcp / secure sctp" (tcps / sctps) would make more sense. By the way, the document lacks a reference on how TLSoverSCTP is supposed to be implemented... (RFC3436?) Best regards, Sebastien. -- Sebastien Decugis Research fellow Network Architecture Group NICT (nict.go.jp) From nilanjan@mavenir.com Wed Mar 31 23:11:15 2010 Return-Path: X-Original-To: dime@core3.amsl.com Delivered-To: dime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A3A93A6AB0 for ; Wed, 31 Mar 2010 23:11:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.126 X-Spam-Level: ** X-Spam-Status: No, score=2.126 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, RELAY_IS_203=0.994, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hyIcZWKbeDq0 for ; Wed, 31 Mar 2010 23:11:14 -0700 (PDT) Received: from smtp105.biz.mail.in2.yahoo.com (smtp105.biz.mail.in2.yahoo.com [203.104.19.14]) by core3.amsl.com (Postfix) with SMTP id 4AB843A688D for ; Wed, 31 Mar 2010 23:11:05 -0700 (PDT) Received: (qmail 36883 invoked from network); 1 Apr 2010 06:11:33 -0000 Received: from ABTS-KK-static-098.63.166.122.airtelbroadband.in (nilanjan@122.166.63.98 with login) by smtp105.biz.mail.in2.yahoo.com with SMTP; 01 Apr 2010 11:41:33 +0530 IST X-Yahoo-SMTP: SjFJ0IWswBA6kepkfKBs_0YoUv59TuLlAD9M X-YMail-OSG: mgJZtnAVM1nXmNvqmpDcvuG.5xEeTir9zdQAqMXh.6BmY_0qeT5OASfyXWQAktbuv0eSy1AmVVdLoFYsxKB5BPpQVRVCxeHF8hOgiOvOnGlK23_FmOPCnH7yIMvGpvJ5fY8imJG87wSnVuGdYVCVS1Jsu3gjYACwUBrHqDXVkAfKq3pNYKJrFxo1s6fi0hRjTJTZOA8Pl2vFKZpeGyU6n7DDUut0VNEL8t3wZxRee_PP.IRgR8nbULJNfhkBFZBUswSMsHF2_TA- X-Yahoo-Newman-Property: ymail-3 From: "Nilanjan" To: "'Ralph Loader'" , "'Tom Taylor'" References: <20100401165042.ac842ead.suckfish@ihug.co.nz> In-Reply-To: <20100401165042.ac842ead.suckfish@ihug.co.nz> Date: Thu, 1 Apr 2010 11:41:26 +0530 Message-ID: <000001cad162$297b3120$7c719360$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcrRTpAsEbeyTrw+ScqozQZZPyODRQAD4gOA Content-Language: en-us Cc: dime@ietf.org Subject: Re: [Dime] Message mis-sequencing over SCTP X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Apr 2010 06:11:15 -0000 I think, this mis-sequencing can only happen CEA followed by new request using different stream-id in case of SCTP. 1) This is because CEA does not have any Confirmation defined in protocol, so peer does not have any knowledge of whether CEA is reached and accepted, before issuing a request. This may have implementation solution like forcing all initial REQ immediately after sending CEA to use same stream-id of CEA until any msg from peer received (any REQ/RES). I am thinking this mis-sequencing is limited to only very small scenario, since a) Generally CER is sent by Diameter Client, who likes to send REQ to Diameter server, even though Diameter is Peer-to-peer protocol. b) This is only when we need to send REQ immediately after sending CEA, and not giving enough time to reach CEA packet to peer (max time to live) or to see whether peer disconnects to Diameter connection (in case of CEA is not accepted) c) Sending application request before starting watch-dog message So, this may be required to keep in protocol, and can be left to implementation. 2) In case of Diameter session application, some AVP defined like (CC-Request-Number in case of CCA), which can be used to reordering any messages using different stream-id in case of SCTP. Kind Regards, Nilanjan -----Original Message----- From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of Ralph Loader Sent: Thursday, April 01, 2010 9:21 AM To: Tom Taylor Cc: dime@ietf.org Subject: Re: [Dime] Message mis-sequencing over SCTP > Sounds like a good point. Seems to me the rules should be: > > - use only stream 0 until the Diameter connection has been set up > - all messages relating to the same session must use the same stream. Is the second suggested rule (same session must use the same stream) actually of any use? IIRC, in principal, messages on the same session may take different routes to their destination (where multiple Diameter proxies are available) and that makes enforcing ordering on a single hop irrelevant to the session? The Diameter application must either enforce ordering or cope with reordering, anyway? Cheers, Ralph. > > That should be added to section 2.1.1. > > > Naveen Kottapalli wrote: > > Hi, > > > > Am just wondering whether the mis-sequencing in the delivery of packets when > > SCTP is being used as transport layer would cause any problem. For example, > > take an association with 5 out-streams to send out the Diameter messages. > > Immediately after sending CEA on stream 0, all other messages are sent over > > other streams like 1, 2, 3, and 4. > > > > There is a chance that the other Diameter messages will reach the peer > > before the CEA is processed? Does the existing draft miss the sequencing > > problem over SCTP? > > > > Yours, > > Naveen. > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > 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 _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime