From qh.resu01@gmail.com Sat May 4 00:26:07 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC94921F8681 for ; Sat, 4 May 2013 00:26:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.229 X-Spam-Level: X-Spam-Status: No, score=-2.229 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eamxSKsllbPP for ; Sat, 4 May 2013 00:26:07 -0700 (PDT) Received: from mail-da0-x229.google.com (mail-da0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 1E73521F860B for ; Sat, 4 May 2013 00:26:07 -0700 (PDT) Received: by mail-da0-f41.google.com with SMTP id y19so1127994dan.14 for ; Sat, 04 May 2013 00:26:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:to:from:reply-to:subject:message-id:x-priority :x-mailer:mime-version:content-transfer-encoding:content-type; bh=AEpZ+aCT2PXWVK5mtpT25o8WzwkBX2DVgoiWySTreyo=; b=C6ascrntIQTqvG1k9ooIqsaZmIP2D3v6OH5+rlU6GvCZ+/WMhxi8RlBGprpxaKGhx9 Urt88aLqIsR3JYmgAX134Mqtesu3KHDfByGpLo1IlYf35z7abF4x5HkMcXvSvYzMorXN R6Mu0l/wDvAa1eT5OSqTmkgcZdmCEfPlJ1dNqjYIo7NyQYDr17+xeP44wWYm1KTyVgDk qoXKOKQhv+cnNFXsC386VVEjzD/Zvf3S6U5nbgyrDZlHAwfjidFYozHedII3IAzJppJj xK2Ilo7kzx2Lv8u9WXXkxCYWtBGDGD9e+B+046Cupa/OUtLtgWMNK+s84aMBqVNAbKfP toOg== X-Received: by 10.66.52.50 with SMTP id q18mr18071859pao.201.1367652366797; Sat, 04 May 2013 00:26:06 -0700 (PDT) Received: from queryhome.com (ec2-54-245-79-134.us-west-2.compute.amazonaws.com. [54.245.79.134]) by mx.google.com with ESMTPSA id ag4sm14818508pbc.20.2013.05.04.00.26.05 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 04 May 2013 00:26:05 -0700 (PDT) Date: Sat, 4 May 2013 07:26:04 +0000 To: dime@ietf.org From: Kevin Peterson Message-ID: X-Priority: 3 X-Mailer: CatPHPMailer 5.1 (phpmailer.sourceforge.net) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" Subject: [Dime] What is the difference between Ro and Gy interface of diameter? X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Kevin Peterson List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 May 2013 07:26:30 -0000 Hi, As per my understanding both are same but could not confirm the same from internet so asking this question. Thanks, Kevin Peterson From isj-dime@i1.dk Sat May 4 04:58:22 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B459821F949D for ; Sat, 4 May 2013 04:58:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.233 X-Spam-Level: **** X-Spam-Status: No, score=4.233 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_EQ_DK=1.009, HELO_MISMATCH_DK=1.7, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qa1xzq+vqbHj for ; Sat, 4 May 2013 04:58:12 -0700 (PDT) Received: from i1.dk (188-176-48-94-static.dk.customer.tdc.net [188.176.48.94]) by ietfa.amsl.com (Postfix) with ESMTP id 9588E21F93AA for ; Sat, 4 May 2013 04:58:12 -0700 (PDT) Received: from i1.dk (isjsys5 [127.0.0.1]) by i1.dk (Postfix) with ESMTP id 4672E5C009C for ; Sat, 4 May 2013 13:58:07 +0200 (CEST) Received: from isjsys.int.i1.dk (isjsys-i0.int.i1.dk [IPv6:2001:16d8:dd31:1:219:d1ff:fe90:2bfa]) by i1.dk (Postfix) with ESMTP for ; Sat, 4 May 2013 13:58:07 +0200 (CEST) Received: from isjsys.localnet (localhost [IPv6:::1]) by isjsys.int.i1.dk (Postfix) with ESMTP id 1C295E9FA6 for ; Sat, 4 May 2013 13:58:07 +0200 (CEST) From: Ivan Skytte =?iso-8859-1?q?J=F8rgensen?= To: dime@ietf.org Date: Sat, 4 May 2013 13:58:06 +0200 User-Agent: KMail/1.13.6 (Linux/2.6.37.6-0.11-desktop; KDE/4.6.0; x86_64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <201305041358.06833.isj-dime@i1.dk> Subject: Re: [Dime] What is the difference between Ro and Gy interface of diameter? X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 May 2013 11:58:22 -0000 On L=F8rdag den 4. maj 2013 09:26:04 Kevin Peterson wrote: > Hi,=20 >=20 > As per my understanding both are same but could not confirm the same from= internet so asking this question. Gy is mostly a restricted subset of Ro. For instance, in Gy online charging= the use of multiple-services-credit-control AVP is mandatory. Gy also adds some AVPs that Ro doesn't specify (eg. volume-quota-threshold). /isj From alanmcn@openet.com Sat May 4 05:44:46 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1F8121F91F1 for ; Sat, 4 May 2013 05:44:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.738 X-Spam-Level: X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MoFbmk5cZjMN for ; Sat, 4 May 2013 05:44:42 -0700 (PDT) Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.168]) by ietfa.amsl.com (Postfix) with ESMTP id DCE3B21F89B0 for ; Sat, 4 May 2013 05:44:41 -0700 (PDT) Received: from [85.158.137.19:10945] by server-8.bemta-3.messagelabs.com id 32/48-25864-8B205815; Sat, 04 May 2013 12:44:40 +0000 X-Env-Sender: alanmcn@openet.com X-Msg-Ref: server-2.tower-39.messagelabs.com!1367671480!16929040!1 X-Originating-IP: [212.187.194.139] X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4924 invoked from network); 4 May 2013 12:44:40 -0000 Received: from unknown.level3.net (HELO dubhbca02.openet-dublin) (212.187.194.139) by server-2.tower-39.messagelabs.com with RC4-SHA encrypted SMTP; 4 May 2013 12:44:40 -0000 Received: from DUBEXCH01.openet-dublin ([10.0.3.84]) by dubhbca02.openet-dublin ([10.0.3.81]) with mapi; Sat, 4 May 2013 13:44:34 +0100 From: Alan McNamee To: Kevin Peterson , "dime@ietf.org" Date: Sat, 4 May 2013 13:44:33 +0100 Thread-Topic: [Dime] What is the difference between Ro and Gy interface of diameter? Thread-Index: Ac5ImLVw6HuJs6KtRIuLR0Kun1YkOAAKzO/A Message-ID: <53CF299802A281409CB89D5E3DDC4AF70A677DD4AF@DUBEXCH01.openet-dublin> References: In-Reply-To: Accept-Language: en-US, en-IE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-IE Content-Type: multipart/alternative; boundary="_000_53CF299802A281409CB89D5E3DDC4AF70A677DD4AFDUBEXCH01open_" MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 04 May 2013 12:52:24 -0700 Subject: Re: [Dime] What is the difference between Ro and Gy interface of diameter? X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 May 2013 12:46:33 -0000 --_000_53CF299802A281409CB89D5E3DDC4AF70A677DD4AFDUBEXCH01open_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Kevin, Ro is a 3GPP reference point that describes the connection to the OCS from = another functional component. It is a general term that covers multiple con= necting components such as GGSN, P-GW, WLAN, IMS AS, MBMS server, etc. See = 3GPP TS 32.296 Figure 5.= 1 for reference. Gy is an specific instance of the Ro reference point that connects a chargi= ng component from the packet-switched domain (PS domain) i.e. PCEF within a= GGSN or P-GW to the OCS. See 3GPP TS 32.251 Figure 4.3-1 for reference. Let me know if you need further information. Regards, Alan McNamee. Openet VP Of Technology Chief Scientist -----Original Message----- From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of Kev= in Peterson Sent: 04 May 2013 08:26 To: dime@ietf.org Subject: [Dime] What is the difference between Ro and Gy interface of diame= ter? Hi, As per my understanding both are same but could not confirm the same from i= nternet so asking this question. Thanks, Kevin Peterson _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime ________________________________ This email and any files transmitted with it are confidential and intended = solely for the use of the individual or entity to whom they are addressed. = If you are not the intended recipient, please note that any review, dissemi= nation, disclosure, alteration, printing, circulation, retention or transmi= ssion of this e-mail and/or any file or attachment transmitted with it, is = prohibited and may be unlawful. If you have received this e-mail or any fil= e or attachment transmitted with it in error please notify postmaster@opene= t.com. Although Openet has taken reasonable precautions to ensure no viruse= s are present in this email, we cannot accept responsibility for any loss o= r damage arising from the use of this email or attachments. --_000_53CF299802A281409CB89D5E3DDC4AF70A677DD4AFDUBEXCH01open_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Kevin,

 

Ro is a 3GPP reference point that describes the c= onnection to the OCS from another functional component. It is a general ter= m that covers multiple connecting components such as GGSN, P-GW, WLAN, IMS = AS, MBMS server, etc. See 3GPP TS 32.296= Figure 5.1 for reference.

 

Gy is an specific instance of the Ro reference po= int that connects a charging component from the packet-switched domain (PS = domain) i.e. PCEF within a GGSN or P-GW to the OCS. See 3GPP TS 32.251= Figure 4.3-1 for reference.

 

Let me know if you need further information.=

 

Regards,

Alan McNamee.

 

&nbs= p;

Openet

VP Of Tec= hnology

Chief Sci= entist

 

 

-----Original Message-----
From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of Kev= in Peterson
Sent: 04 May 2013 08:26
To: dime@ietf.org
Subject: [Dime] What is the difference between Ro and Gy interface of diame= ter?

 

Hi,

 

As per my understanding both are same but could n= ot confirm the same from internet so asking this question.

 

Thanks,

Kevin Peterson

 

 

_______________________________________________

DiME mailing list

DiME@ietf.org

https://www.iet= f.org/mailman/listinfo/dime


This email and any files tra= nsmitted with it are confidential and intended solely for the use of the in= dividual or entity to whom they are addressed. If you are not the intended = recipient, please note that any review, dissemination, disclosure, alteration, printing, circulation, retention or= transmission of this e-mail and/or any file or attachment transmitted with= it, is prohibited and may be unlawful. If you have received this e-mail or= any file or attachment transmitted with it in error please notify postmaster@openet.com. Although Openet has = taken reasonable precautions to ensure no viruses are present in this email= , we cannot accept responsibility for any loss or damage arising from the u= se of this email or attachments.
 --_000_53CF299802A281409CB89D5E3DDC4AF70A677DD4AFDUBEXCH01open_-- From wwwrun@rfc-editor.org Fri May 10 17:37:56 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A92921F8FEB; Fri, 10 May 2013 17:37:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.927 X-Spam-Level: X-Spam-Status: No, score=-101.927 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bQ5upO0A8btf; Fri, 10 May 2013 17:37:56 -0700 (PDT) Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 0728221F8ECA; Fri, 10 May 2013 17:37:56 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id F26FF62101; Fri, 10 May 2013 17:37:39 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20130511003739.F26FF62101@rfc-editor.org> Date: Fri, 10 May 2013 17:37:39 -0700 (PDT) Cc: dime@ietf.org, rfc-editor@rfc-editor.org Subject: [Dime] RFC 6942 on Diameter Support for the EAP Re-authentication Protocol (ERP) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 May 2013 00:37:56 -0000 A new Request for Comments is now available in online RFC libraries. RFC 6942 Title: Diameter Support for the EAP Re-authentication Protocol (ERP) Author: J. Bournelle, L. Morand, S. Decugis, Q. Wu, G. Zorn Status: Standards Track Stream: IETF Date: May 2013 Mailbox: julien.bournelle@orange.com, lionel.morand@orange.com, sdecugis@freediameter.net, sunseawq@huawei.com, glenzorn@gmail.com Pages: 18 Characters: 35357 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dime-erp-17.txt URL: http://www.rfc-editor.org/rfc/rfc6942.txt 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 Attribute-Value Pairs (AVPs) that can be used to transport the cryptographic material needed by the re-authentication server. This document is a product of the Diameter Maintenance and Extensions Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From jouni.nospam@gmail.com Sat May 11 12:23:43 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B5AD21F8511 for ; Sat, 11 May 2013 12:23:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.999 X-Spam-Level: X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhGDEAg-m-SL for ; Sat, 11 May 2013 12:23:39 -0700 (PDT) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by ietfa.amsl.com (Postfix) with ESMTP id 01E8A21F8C40 for ; Sat, 11 May 2013 12:23:38 -0700 (PDT) Received: by mail-ee0-f54.google.com with SMTP id e50so2092606eek.27 for ; Sat, 11 May 2013 12:23:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:content-transfer-encoding:subject:date :references:to:message-id:mime-version:x-mailer; bh=5Bm6+oj+Q3PFMy6Uiml+U3yE50evLxhynTnjGkC20aE=; b=eiW8bfPX5VFIq+kxoepY9O1EYL1NXnQ4C0tmPG9iCKr0kLCq4Sbhg8tBYQ2o2dyJY0 7M5YBz6QRRGDyZ7YDuT+fcaevAeZ3aX7V+eEL04zhFU6H1ijZOcGt+G7D2T+J4V7KG/n gYkUU4byEe5tf9cPDw6eRf5EZfUknmDalDpv8eYGBTH7a1xIUgMHtWhCVd1lnAuoqHWC Xa3FIdU3XKcUDO+894lbru+hBPh2dWPuJzRDadfM/BerNQ4/LTeKyZ8fve/E9OCOiAeE af2tNNBlTf3r467scy7iA4cuwxlui+30nAsrvNfBZbfkX59e5kgs0+OVA1F54Yr+f4AI 38dw== X-Received: by 10.14.3.137 with SMTP id 9mr57983952eeh.0.1368300218000; Sat, 11 May 2013 12:23:38 -0700 (PDT) Received: from ?IPv6:2001:1bc8:101:f101:d846:65ee:4074:aef0? ([2001:1bc8:101:f101:d846:65ee:4074:aef0]) by mx.google.com with ESMTPSA id bp51sm11745899eeb.5.2013.05.11.12.23.36 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 11 May 2013 12:23:37 -0700 (PDT) From: Jouni Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sat, 11 May 2013 22:23:34 +0300 References: <20130511003739.F26FF62101@rfc-editor.org> To: dime@ietf.org Message-Id: Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) Subject: [Dime] New RFC 6942 on Diameter Support for the EAP Re-authentication Protocol (ERP) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 May 2013 19:23:43 -0000 Congrats to the authors and thanks for the hard work. Jouni & Lionel Begin forwarded message: > From: rfc-editor@rfc-editor.org > Subject: RFC 6942 on Diameter Support for the EAP Re-authentication = Protocol (ERP) > Date: May 11, 2013 3:37:39 AM GMT+03:00 > To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org > Cc: dime@ietf.org, rfc-editor@rfc-editor.org >=20 > A new Request for Comments is now available in online RFC libraries. >=20 >=20 > RFC 6942 >=20 > Title: Diameter Support for the EAP=20 > Re-authentication Protocol (ERP)=20 > Author: J. Bournelle, L. Morand, > S. Decugis, Q. Wu, > G. Zorn > Status: Standards Track > Stream: IETF > Date: May 2013 > Mailbox: julien.bournelle@orange.com,=20 > lionel.morand@orange.com,=20 > sdecugis@freediameter.net, > sunseawq@huawei.com,=20 > glenzorn@gmail.com > Pages: 18 > Characters: 35357 > Updates/Obsoletes/SeeAlso: None >=20 > I-D Tag: draft-ietf-dime-erp-17.txt >=20 > URL: http://www.rfc-editor.org/rfc/rfc6942.txt >=20 > 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 Attribute-Value Pairs (AVPs) that can be > used to transport the cryptographic material needed by the > re-authentication server. >=20 > This document is a product of the Diameter Maintenance and Extensions = Working Group of the IETF. >=20 > This is now a Proposed Standard. >=20 > STANDARDS TRACK: This document specifies an Internet standards track > protocol for the Internet community,and requests discussion and = suggestions > for improvements. Please refer to the current edition of the Internet > Official Protocol Standards (STD 1) for the standardization state and > status of this protocol. Distribution of this memo is unlimited. >=20 > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist >=20 > For searching the RFC series, see = http://www.rfc-editor.org/rfcsearch.html. > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. >=20 > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. = Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. >=20 >=20 > The RFC Editor Team > Association Management Solutions, LLC >=20 >=20 From internet-drafts@ietf.org Mon May 13 03:54:21 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE0F221F90DF; Mon, 13 May 2013 03:54:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.043 X-Spam-Level: X-Spam-Status: No, score=-102.043 tagged_above=-999 required=5 tests=[AWL=0.557, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aPukorbcaNAZ; Mon, 13 May 2013 03:54:16 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9118A21F9416; Mon, 13 May 2013 03:54:15 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.44.p7 Message-ID: <20130513105415.14648.61536.idtracker@ietfa.amsl.com> Date: Mon, 13 May 2013 03:54:15 -0700 Cc: dime@ietf.org Subject: [Dime] I-D Action: draft-ietf-dime-rfc4005bis-13.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 May 2013 10:54:21 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Diameter Maintenance and Extensions Worki= ng Group of the IETF. Title : Diameter Network Access Server Application Author(s) : Glen Zorn Filename : draft-ietf-dime-rfc4005bis-13.txt Pages : 68 Date : 2013-05-13 Abstract: This document describes the Diameter protocol application used for Authentication, Authorization, and Accounting (AAA) services in the Network Access Server (NAS) environment; it obsoletes RFC 4005. When combined with the Diameter Base protocol, Transport Profile, and Extensible Authentication Protocol specifications, this application specification satisfies typical network access services requirements. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dime-rfc4005bis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-dime-rfc4005bis-13 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dime-rfc4005bis-13 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From priyank.luthra@gmail.com Wed May 15 03:03:01 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 063E621F8F12 for ; Wed, 15 May 2013 03:03:01 -0700 (PDT) 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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YbVMQbG1-W1j for ; Wed, 15 May 2013 03:03:00 -0700 (PDT) Received: from mail-ia0-x234.google.com (mail-ia0-x234.google.com [IPv6:2607:f8b0:4001:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 936D321F8F0E for ; Wed, 15 May 2013 03:03:00 -0700 (PDT) Received: by mail-ia0-f180.google.com with SMTP id l27so1920806iae.11 for ; Wed, 15 May 2013 03:03:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=0y8kYywxbL5xxMJAP1zuNJ5kieh45Zfg0gLduIZky1Q=; b=eXh2lEHB5Uaks5DeRlQGx6wm6v99ViJ9lycsmwX14xDGO73xQ+eWvH61Imakbch097 Lhki/U89Cjs/ur+j3PaEhZf4Z1dAi5VpErFD2ETvnZqV6IjfsrictWOlszDMHrM2AC8j Y6gwS70QNuMWqenPheWB47EJG+RC8Muz3TNUE5i1Ytl7SAKDiGiHvnyXc6Zmc3OrH6Gp rW7W329LyN2KgpMMZICMw3lCX+NYYHNqAHnRvBGRu8RpU6YfjTzyC22IEtVSoHKuPHUz RcYKTzU/5CgK9zn+ipotBRB36ZcuzugUz6ihf9rmYrHa1aVgXs/j2GbUKjZuXrdMzMua UNWA== MIME-Version: 1.0 X-Received: by 10.50.101.4 with SMTP id fc4mr5004497igb.10.1368612180143; Wed, 15 May 2013 03:03:00 -0700 (PDT) Received: by 10.64.250.3 with HTTP; Wed, 15 May 2013 03:03:00 -0700 (PDT) Date: Wed, 15 May 2013 15:33:00 +0530 Message-ID: From: Priyank Luthra To: dime@ietf.org Content-Type: multipart/alternative; boundary=047d7bd6b5bcd5387a04dcbeda00 Subject: [Dime] Significance of Result-Code in DWA X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2013 10:03:01 -0000 --047d7bd6b5bcd5387a04dcbeda00 Content-Type: text/plain; charset=ISO-8859-1 Hi, I wanted to know if there is any significance of Result-Code AVP in DWA (Device-watchdog-answer). What would be the use case where a failed response (eg. 5012) is sent in the DWA ? In that case will the server teer down the transport connection or send DPR ? Or should the server consider DWA with any result-code as a valid scenario and assume that the peer is active. -- Regards, Priyank --047d7bd6b5bcd5387a04dcbeda00 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I wanted to know if there is any si= gnificance of Result-Code AVP in DWA (Device-watchdog-answer).
Wh= at would be the use case where a failed response (eg. 5012) is sent in the = DWA ?

In that case will the server teer down the transport co= nnection or send DPR ?
Or should the server consider DWA with any= result-code as a valid=A0scenario=A0and assume that the peer is active.



--
Regards,
Pri= yank
--047d7bd6b5bcd5387a04dcbeda00-- From dimeg@intracom.gr Wed May 15 03:29:07 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ACD621F8EFC for ; Wed, 15 May 2013 03:29:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8zqTlmJ-6kV for ; Wed, 15 May 2013 03:29:00 -0700 (PDT) Received: from extmail.intranet.gr (extmail.intranet.gr [192.92.155.11]) by ietfa.amsl.com (Postfix) with ESMTP id AB61821F8A53 for ; Wed, 15 May 2013 03:28:59 -0700 (PDT) Received: from mailserv.intranet.gr (mailserv.intranet.GR [146.124.14.106]) by extmail.intranet.gr (8.14.5/8.14.5) with ESMTP id r4FASu5O015408 for ; Wed, 15 May 2013 13:28:56 +0300 (EEST) Received: from mailserv.intranet.gr (localhost [127.0.0.1]) by mailserv.intranet.gr (8.13.6/8.13.1) with ESMTP id r4FASumX001818 for ; Wed, 15 May 2013 13:28:56 +0300 (EEST) Received: from iris.intranet.gr (iris.intranet.GR [146.124.80.178]) by mailserv.intranet.gr (8.13.6/8.13.1) with ESMTP id r4FASrSD001807 for ; Wed, 15 May 2013 13:28:53 +0300 (EEST) Received: from [172.17.49.211] ([172.17.49.211] verified) by iris.intranet.gr (CommuniGate Pro SMTP 5.3.13) with ESMTP id 55038646 for dime@ietf.org; Wed, 15 May 2013 13:28:53 +0300 Message-ID: <51936368.2060206@intracom.gr> Date: Wed, 15 May 2013 13:28:56 +0300 From: Gerasimos Dimitriadis User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: dime@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Dime] RFC6737 and Relay nodes X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2013 10:29:07 -0000 Hi all, I'd like to ask you a question on Capabilities Update when 'relay' nodes are concerned. Specifically, I want to ask whether 'relay' nodes need to advertise the Capabilities Update App Id (10) alongside 0xffffffff towards adjacent diameter nodes or not. Consider a case where proxy agent A is connected to relay agent B, and A wants to update its supported applications. If B has not advertised 10 in the initial CER / CEA exchange (alongside 0xffffffff), how can A know if B implements RFC6737? Should A try a Capabilities Update nevertheless and, in case that RFC 6737 is not implemented, just get a DIAMETER_APPLICATION_UNSUPPORTED error back? The above issue could be fixed if the Capabilities Update App Id is sent alongside 0xffffffff in the initial capabilities exchange handshake, but it feels a little bit strange, since 0xffffffff implies 'all applications'. Thank you and BRs, Gerasimos From trac+dime@trac.tools.ietf.org Thu May 16 06:17:56 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 279CE21F909A for ; Thu, 16 May 2013 06:17:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tdfc4PsZFjKZ for ; Thu, 16 May 2013 06:17:55 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 65A9321F905F for ; Thu, 16 May 2013 06:17:54 -0700 (PDT) Received: from localhost ([127.0.0.1]:44676 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1Ucy45-0005VZ-5z; Thu, 16 May 2013 15:17:49 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "dime issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: draft-ietf-dime-overload-reqs@tools.ietf.org, emcmurry@computer.org X-Trac-Project: dime Date: Thu, 16 May 2013 13:17:49 -0000 X-URL: http://tools.ietf.org/wg/dime/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/dime/trac/ticket/22#comment:1 Message-ID: <078.3809e79ccb8e079881080921108554f7@trac.tools.ietf.org> References: <063.45b1591034a7b3ba091d1456a2c2172a@trac.tools.ietf.org> X-Trac-Ticket-ID: 22 In-Reply-To: <063.45b1591034a7b3ba091d1456a2c2172a@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-dime-overload-reqs@tools.ietf.org, emcmurry@computer.org, dime@ietf.org X-SA-Exim-Mail-From: trac+dime@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: ben@nostrum.com, emcmurry@computer.org Resent-Message-Id: <20130516131755.65A9321F905F@ietfa.amsl.com> Resent-Date: Thu, 16 May 2013 06:17:54 -0700 (PDT) Resent-From: trac+dime@trac.tools.ietf.org Cc: dime@ietf.org Subject: Re: [Dime] [dime] #22: explicit requirement for a default algorithm is needed X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Reply-To: dime@ietf.org List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2013 13:17:56 -0000 #22: explicit requirement for a default algorithm is needed Changes (by emcmurry@computer.org): * status: new => closed * resolution: => fixed Comment: added requirement 33 -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-dime-overload- emcmurry@computer.org | reqs@tools.ietf.org Type: defect | Status: closed Priority: minor | Milestone: Component: overload- | Version: reqs | Resolution: fixed Severity: In WG Last | Call | Keywords: | -------------------------+------------------------------------------------- Ticket URL: dime From emcmurry@computer.org Fri May 17 13:51:50 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A06F321F96A9 for ; Fri, 17 May 2013 13:51:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.835 X-Spam-Level: X-Spam-Status: No, score=-1.835 tagged_above=-999 required=5 tests=[AWL=0.763, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2oMuVK1z4PHr for ; Fri, 17 May 2013 13:51:45 -0700 (PDT) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id 6735521F96AC for ; Fri, 17 May 2013 13:51:44 -0700 (PDT) Received: from cpe-76-184-161-215.tx.res.rr.com ([76.184.161.215] helo=antikythera.casamcmurry.com) by mho-02-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1UdRct-000F3z-M3 for dime@ietf.org; Fri, 17 May 2013 20:51:43 +0000 Received: from localhost (localhost [127.0.0.1]) by antikythera.casamcmurry.com (Postfix) with ESMTP id EC74E334EC95 for ; Fri, 17 May 2013 15:51:42 -0500 (CDT) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 76.184.161.215 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/3a9SUIJnSaeDbB+x1dcGNbuCbFWIS74Y= X-Virus-Scanned: amavisd-new at casamcmurry.com Received: from antikythera.casamcmurry.com ([127.0.0.1]) by localhost (antikythera.casamcmurry.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VZD20zBgzMdb for ; Fri, 17 May 2013 15:51:42 -0500 (CDT) Received: from [192.168.13.6] (unknown [192.168.13.6]) by antikythera.casamcmurry.com (Postfix) with ESMTPSA id 7C8BC334EC81 for ; Fri, 17 May 2013 15:51:42 -0500 (CDT) From: Eric McMurry Content-Type: multipart/alternative; boundary="Apple-Mail=_559117A1-32ED-4460-9FB5-85A22E1AF9DA" Message-Id: Date: Fri, 17 May 2013 15:51:40 -0500 To: "dime@ietf.org" Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) X-Mailer: Apple Mail (2.1503) Subject: [Dime] draft-roach-dime-overload-ctrl-03 X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 May 2013 20:51:50 -0000 --Apple-Mail=_559117A1-32ED-4460-9FB5-85A22E1AF9DA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii A new version of the proposed overload control mechanism is available. = This version fixes the requirements non-compliance found during the = analysis on the prior version, with the exception of requirement 34 = (crossing non-adjacent, non-supporting elements). URL: = http://www.ietf.org/internet-drafts/draft-roach-dime-overload-ctrl-03.txt Status: = http://datatracker.ietf.org/doc/draft-roach-dime-overload-ctrl Htmlized: = http://tools.ietf.org/html/draft-roach-dime-overload-ctrl-03 Diff: = http://www.ietf.org/rfcdiff?url2=3Ddraft-roach-dime-overload-ctrl-03 --Apple-Mail=_559117A1-32ED-4460-9FB5-85A22E1AF9DA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii A new = version of the proposed overload control mechanism is available. =  This version fixes the requirements non-compliance found during = the analysis on the prior version, with the exception of requirement 34 = (crossing non-adjacent, non-supporting = elements).





= --Apple-Mail=_559117A1-32ED-4460-9FB5-85A22E1AF9DA-- From kotecha_kamal@yahoo.com Fri May 17 14:47:42 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A421021F96D3 for ; Fri, 17 May 2013 14:47:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.674 X-Spam-Level: X-Spam-Status: No, score=0.674 tagged_above=-999 required=5 tests=[AWL=-0.213, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, J_CHICKENPOX_63=0.6, RCVD_IN_SORBS_WEB=0.619, SARE_HTML_USL_OBFU=1.666] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MbAaeGtZk77i for ; Fri, 17 May 2013 14:47:36 -0700 (PDT) Received: from nm33-vm4.bullet.mail.ne1.yahoo.com (nm33-vm4.bullet.mail.ne1.yahoo.com [98.138.229.68]) by ietfa.amsl.com (Postfix) with ESMTP id 3099521F96C4 for ; Fri, 17 May 2013 14:47:36 -0700 (PDT) Received: from [98.138.90.49] by nm33.bullet.mail.ne1.yahoo.com with NNFMP; 17 May 2013 21:47:35 -0000 Received: from [98.138.87.1] by tm2.bullet.mail.ne1.yahoo.com with NNFMP; 17 May 2013 21:47:35 -0000 Received: from [127.0.0.1] by omp1001.mail.ne1.yahoo.com with NNFMP; 17 May 2013 21:47:35 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 744294.46544.bm@omp1001.mail.ne1.yahoo.com Received: (qmail 28305 invoked by uid 60001); 17 May 2013 21:47:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1368827255; bh=9wd5HuHYgpLKapt+kUBZXXaR4PFgxM2lv76pDArjv7Y=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=sDQk8PdHtQRtGHIJ3YadtnCbRTQt5r9Oxa4zrVWeo5u0KQFFhuhDEl/H3oL5Nl8ph8cl6zin6xkGOqjFZrWPwnRclDNPgm4RiRYcd/zCzbsBBA2spzD/RkADQsCOKMMIajDlpXuLZ3UGyYx/YPEhDlqwbeCFFjHDU/QfseRCULM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=q0o47W8DHOOKF//6qkah517xKUVMx0MPGxkBKzljUhsl/oWHu2LemfJIZyPZsA5AdsS2+ey4qkfm91jCKjfVmcxuyePfCeRsqDG0izi/ltDEKcpAjsnBotRGXqxvISKxiWkSFQVMnJc3VGqVGaFwL5MgkYzVtUsuaU9TrdjzrMY=; X-YMail-OSG: IGNX6e4VM1kORC2PI2YHSjeaUnecy41HtkEN3cJsKr2MeIF jhPwKya74XifP7LKdRybhovAq4X1zKQjDlawmFP.ATssnOZx4jGYA4fZvh3N VjOSOqdKfYsjDLrLnYcT2wd1ieD8NfN6NbjPMl5a4F1KIcxyxZXaUmiRWu9f UY.iCuvtRRsSA_sB_gfqVEzkS3MNxd_M44UmDaXatIFCouf7E08NTk8JVut8 M0IeqMtoAYVZkymBhfQjhvkLz6UQqLVzbjDwPspMZPgyXr_kg6SLuQwApGlA g15zD7h.h9UNyeFxPwEALmIp.sWjAFBAUSGEMgFwRe2Y9JaCIffKS_0_Yo.g 97GQSUEV5c5Q7fdcXKEz9bluA8X2yg0R8mmjAkeiS4Qip3g0oVFAXL_McYye gBMONaZuvPP7cFifLPDYrwoMmopUoOeUgGIsrmUc_mSHAiwfFNgBOZJCDXLm 5D0CV4rsglM9yf6RJWRmThgMWM5cIb4Ul1qzhcdmzfecUSzozo801bYA5TPk Zt_ZwfcbO6tw_u3S80Q-- Received: from [115.240.40.89] by web120104.mail.ne1.yahoo.com via HTTP; Fri, 17 May 2013 14:47:35 PDT X-Rocket-MIMEInfo: 002.001, wqAKwqAKSGkgRm9sa3MsIApXZSBhcmUgZmFjaW5nIGEgcHJvYmxlbSB3aXRoIERpYW1ldGVyIENyZWRpdCBDb250cm9sIEFwcGxpY2F0aW9uOiAKUHJvYmxlbSBkaXNjcmlwdGlvbjogCkRpYW1ldGVyIGNsaWVudCBzZW5kcyBhIENDUi11cGRhdGUgbWVzc2FnZSB0byBzZXJ2ZXIsYnV0IHNlcnZlciBkb2VzIG5vdCByZXNwb25kIHRvIHRoZSByZXF1ZXN0LiAKTm93LGFzIGNsaWVudCBpcyBjb25maWd1cmVkIHdpdGggc2Vzc2lvbiBmYWlsb3ZlciwgaXQgd2lsbCBzZW5kIENDUi11cGRhdGUgdG8gYmFja3VwIHMBMAEBAQE- X-Mailer: YahooMailWebService/0.8.142.542 Message-ID: <1368827255.90883.YahooMailNeo@web120104.mail.ne1.yahoo.com> Date: Fri, 17 May 2013 14:47:35 -0700 (PDT) From: Kamal Kotecha To: "DiME@ietf.org" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-1312421089-551264531-1368827255=:90883" Subject: [Dime] Diameter Credit Control Application--Issue during CCR-Update X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Kamal Kotecha List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 May 2013 21:47:42 -0000 ---1312421089-551264531-1368827255=:90883 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable =A0=0A=A0=0AHi Folks, =0AWe are facing a problem with Diameter Credit Contr= ol Application: =0AProblem discription: =0ADiameter client sends a CCR-upda= te message to server,but server does not respond to the request. =0ANow,as = client is configured with session failover, it will send CCR-update to back= up server. =0AIn this update message, Destination Host AVP is not being inc= luded. (???) =0AHence, in same destination realm, this request is forwarde= d to random peer. =0AThis random peer is responding with failure message a= s "Diamater Unable to Comply".=0AWhats wrong here..?? =0A(in rfc 4006, I'm = not able to track this kind of scenario!)=0ARegards,=0AKamal Kotecha=0A=0A= =0AKamal Kotecha=0AWirefree Num:+91 9725683242=0A ---1312421089-551264531-1368827255=:90883 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
 =
 
Hi Folks,
<= span>
We are facing a problem with Diameter Credit = Control Application:
Proble= m discription:
Diameter cli= ent sends a CCR-update message to server,but server does not respond to the= request.
Now,as client is = configured with session failover, it will send CCR-update to backup server.=
In this update message, Destination Host AVP is not being included. = (???)
Hence, in same destin= ation realm, this request is forwarded to random peer.
This random peer is= responding with failure message as "Diamater Unable to Comply".
Whats wrong here..??
= (in rfc 4006, I'm not able to track this kind of scenario!)
Regards,
Kamal Kotecha
 <= /div>
Kamal Kotecha
Wirefree Num:+91 9725683242
---1312421089-551264531-1368827255=:90883-- From jouni.nospam@gmail.com Sun May 19 11:53:42 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 181DF21F842F for ; Sun, 19 May 2013 11:53:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.399 X-Spam-Level: X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_32=0.6, J_CHICKENPOX_63=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79bn9zUqjOUo for ; Sun, 19 May 2013 11:53:37 -0700 (PDT) Received: from mail-ee0-f47.google.com (mail-ee0-f47.google.com [74.125.83.47]) by ietfa.amsl.com (Postfix) with ESMTP id 4C54921F8425 for ; Sun, 19 May 2013 11:53:32 -0700 (PDT) Received: by mail-ee0-f47.google.com with SMTP id t10so3459691eei.34 for ; Sun, 19 May 2013 11:53:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:mime-version:content-type:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=MKUSjXNrYBILdf4LN+7SLQYCO5EqEnneoSJTfkBm/YY=; b=DOL5RrZEuOA79cTiiqB8LdbRBGkkcjb6dyg6V4I6iQ23ZaSazaR4HfRwwtwg1ObnLR fLpNJMEU4obIjbT9pQxtqK0M7l8TybcV0LBQxv5P6vNuH5Yi/f9L5Vn/GJfQ4mLYZcNS W0Toouurd1KtwVSyij33USv98g3vC5LWWZ2W828Pms+QaqEqnkHjU4WbV2Nght+xu+1U 9uxU1GYmRbBE+ZG7GrpSh1WwEQc0z2kAoiLEd9CoW8zdto4p+qLtWdT3W7+pfqCGAvuz SQkkeVaFzRwPixErOjyP8mje1pbv+qZnQLtBh1xn4dsMe9l0HaK5Zgv9nCas3ZJ7RVG3 Lyqg== X-Received: by 10.14.38.198 with SMTP id a46mr157471633eeb.11.1368989612101; Sun, 19 May 2013 11:53:32 -0700 (PDT) Received: from [188.117.15.107] ([188.117.15.107]) by mx.google.com with ESMTPSA id s8sm32935741eeo.4.2013.05.19.11.53.29 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 May 2013 11:53:30 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=iso-8859-1 From: Jouni In-Reply-To: <1368827255.90883.YahooMailNeo@web120104.mail.ne1.yahoo.com> Date: Sun, 19 May 2013 21:53:28 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <4015A41B-1D4C-45B8-9EE2-345A92BB3F81@gmail.com> References: <1368827255.90883.YahooMailNeo@web120104.mail.ne1.yahoo.com> To: Kamal Kotecha X-Mailer: Apple Mail (2.1283) Cc: "DiME@ietf.org" Subject: Re: [Dime] Diameter Credit Control Application--Issue during CCR-Update X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 May 2013 18:53:42 -0000 Hard to know since we do not have further information of the message = contents and deployment details. The error you received is due the server not = knowing what to do with the received request for an application it supports. I = would have expected to see e.g. DIAMETER_UNKNOWN_SESSION_ID, though. I am = _not_ a "CCR expert" but unless the primary and backup server share the session = state, sending an update to a random server is obvious to fail. There is no = such state change in the CCR state machine afaik (after a very quick look). In RFC4006 Section 7 there is an explicit text stating: In the following state machine table, the failover to a secondary server upon 'Temporary error' or 'Failure to send' is not explicitly described. Moving an ongoing credit-control message stream to an alternative server is, however, possible if the CC-Session-Failover AVP is set to FAILOVER_SUPPORTED, as described in section 5.7. Re-sending a credit-control event to an alternative server is supported as described in section 6.5. In Section 6.5 it says: Failover to an alternative credit-control server is allowed for a one time event, as the server is not maintaining session states. For ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Since your client is sending updates, I assume you are operating in=20 a session-based credit-control mode, right? Sending an update to a = backup server would cause an error and your client would be misbehaving. In Section 5.7 it says: If a failure occurs during an ongoing credit-control session, the credit-control client may move the credit-control message stream to an alternative server if the CC-server indicated FAILOVER_SUPPORTED ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ in the CC-Session-Failover AVP. A secondary credit-control server ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ name, either received from the home Diameter AAA server or configured ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ locally, can be used as an address of the backup server. If the CC- ^^^^^^^ Session-Failover AVP is set to FAILOVER_NOT_SUPPORTED, the credit- control message stream MUST NOT be moved to a backup server. Are these conditions met before sending the update to a random backup server? - JOuni On May 18, 2013, at 12:47 AM, Kamal Kotecha wrote: > =20 > =20 > Hi Folks, > We are facing a problem with Diameter Credit Control Application: > Problem discription: > Diameter client sends a CCR-update message to server,but server does = not respond to the request. > Now,as client is configured with session failover, it will send = CCR-update to backup server. > In this update message, Destination Host AVP is not being included. = (???) > Hence, in same destination realm, this request is forwarded to random = peer. > This random peer is responding with failure message as "Diamater = Unable to Comply". > Whats wrong here..?? > (in rfc 4006, I'm not able to track this kind of scenario!) > Regards, > Kamal Kotecha > =20 > Kamal Kotecha > Wirefree Num:+91 9725683242 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From jouni.nospam@gmail.com Sun May 26 08:35:40 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B839A21F8E8F for ; Sun, 26 May 2013 08:35:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCjpdHs3eiRC for ; Sun, 26 May 2013 08:35:40 -0700 (PDT) Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 1E6F121F8B98 for ; Sun, 26 May 2013 08:35:39 -0700 (PDT) Received: by mail-ea0-f171.google.com with SMTP id b15so3533820eae.16 for ; Sun, 26 May 2013 08:35:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; bh=aXhDf6swLriQUZ+nMT9xu3Z3LxVqz6W9AptGq3Y1K1A=; b=OrC9gmnImHAu6Od8eFoYVFBqA3MeBFkHxY1Oe3UjwDlsW5CiocuVDWuB0wG4WD4RLD dfCWgTFGAHeDt4BedCBSBDc8Ev26mzdwGIMN9rHMK62KZGyqWFt8SwTc13xGzgF4BrJ1 6jYnCPCch8JMWazhGTeBCnOE6QkSp8mUpR2hOk2K3NMGcoTKefauwhsA9hWnudmvcyko SrKOM6cgi05w7EldCaniIA414oS5hkUYM3yBmAuSV3SiWwgkD3y0KMzj5/FC7sSfS3qY +NCu+fxZJ1YM0c39szR1anx8iW9iMDqEY4YR/wWT9mQ8QqkbzWtdYk0N8mY8oxMMHr4Y TbRQ== X-Received: by 10.14.94.193 with SMTP id n41mr6468750eef.122.1369582539218; Sun, 26 May 2013 08:35:39 -0700 (PDT) Received: from ?IPv6:2001:1bc8:101:f101:a972:9099:50e9:c5d? ([2001:1bc8:101:f101:a972:9099:50e9:c5d]) by mx.google.com with ESMTPSA id z52sm36076896eea.1.2013.05.26.08.35.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 May 2013 08:35:38 -0700 (PDT) From: Jouni Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 26 May 2013 18:35:35 +0300 Message-Id: <9A4AC6D9-BDB5-414E-8DF1-7BC42594250A@gmail.com> To: "DiME@ietf.org" Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) Cc: dime-chairs@tools.ietf.org Subject: [Dime] Call for agenda items for IETF#87 Berlin meeting X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 May 2013 15:35:40 -0000 Folks, We have requested for two hour meeting slot. If you feel like presenting your work (be that in the current charter or not), send a request to the co-chairs. Obviously, chartered items will be prioritized over other topics. - Jouni & Lionel From jouni.nospam@gmail.com Tue May 28 09:09:53 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9804F21F9787 for ; Tue, 28 May 2013 09:09:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.187 X-Spam-Level: X-Spam-Status: No, score=-1.187 tagged_above=-999 required=5 tests=[AWL=1.185, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AMIHXJFnZ5yT for ; Tue, 28 May 2013 09:09:53 -0700 (PDT) Received: from mail-ea0-x22c.google.com (mail-ea0-x22c.google.com [IPv6:2a00:1450:4013:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id CA31B21F97EC for ; Tue, 28 May 2013 09:09:33 -0700 (PDT) Received: by mail-ea0-f172.google.com with SMTP id d10so4714801eaj.3 for ; Tue, 28 May 2013 09:09:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=LYjxgc/IUdQb94JuItxSH1+ztUQcGVCFW+QaoI2isU8=; b=UczlbxizyWbVo4Kg0/RhyvGTi7ik1JQk0TZWN7+ZXbYmOu7q5kvi5ROrqlrQpanXAW IunJkWWX5b9hzUM2rR/D0yfEwPI+03EkdbzDqJp0Pl8tCZyPRlsUdK075AfqbQ1qWW2e NNfUYROnXVCgF5788shzCTa2l68d+Mo28qdZm45eASPDKmUiPVhY2meRpUyhI/eZ3KUY egXMF164lHhjIop6bF3DcAojgzUiwkYWRDb1QI6eo1ZJwolMYezdXy7AL2lO0zSb5EPc y4XnNNKx8ZqXUsTBCFsIwMrkHLmpIi3gfbWw6T+Q1JiRulWDXgEtD9P4nplpR6PO5cN+ PPrw== X-Received: by 10.14.122.135 with SMTP id t7mr14816866eeh.141.1369757372657; Tue, 28 May 2013 09:09:32 -0700 (PDT) Received: from [188.117.15.110] ([188.117.15.110]) by mx.google.com with ESMTPSA id y2sm48792867eeu.2.2013.05.28.09.09.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 09:09:31 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Jouni Korhonen In-Reply-To: <16048_1366721479_517683C7_16048_612_1_6B7134B31289DC4FAF731D844122B36E1C297C@PEXCVZYM13.corporate.adroot.infra.ftgroup> Date: Tue, 28 May 2013 19:09:29 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: <43587557-EA86-43A1-9F7E-C821FC6E35B6@gmail.com> <16048_1366721479_517683C7_16048_612_1_6B7134B31289DC4FAF731D844122B36E1C297C@PEXCVZYM13.corporate.adroot.infra.ftgroup> To: "dime@ietf.org" X-Mailer: Apple Mail (2.1503) Cc: "dime-chairs@tools.ietf.org" Subject: Re: [Dime] WGLC for draft-ietf-dime-overload-reqs-06 X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2013 16:09:53 -0000 Folks, We seem to have reached consensus on this document and can conclude it = have passed its WGLC. So, the next step is chairs doing yet another = review while writing the proto write-up, and then eventually move the = document into IESG process. - Jouni & Lionel On Apr 23, 2013, at 3:49 PM, lionel.morand@orange.com wrote: > Folks, >=20 > As discussed last week, the authors of draft-ietf-dime-overload-reqs = have requested for a new WGLC. > All the pending issues have been closed and the last version of the = draft seems to be ready for publication. >=20 > This email starts a two week WGLC for = draft-ietf-dime-overload-reqs-06. > The WGLC ends Tuesday 7th May 2013. Post your comments to the mailing = list and if you think something needs to be changed, put that also into = the Issue Tracker.=20 >=20 > - Jouni & Lionel >=20 >=20 > = __________________________________________________________________________= _______________________________________________ >=20 > Ce message et ses pieces jointes peuvent contenir des informations = confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez = recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les = messages electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a = ete altere, deforme ou falsifie. Merci. >=20 > This message and its attachments may contain confidential or = privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and = delete this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for = messages that have been modified, changed or falsified. > Thank you. >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From internet-drafts@ietf.org Wed May 29 03:05:22 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60F3B21F9375; Wed, 29 May 2013 03:05:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.475 X-Spam-Level: X-Spam-Status: No, score=-102.475 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bQ7ozr42yUPS; Wed, 29 May 2013 03:05:20 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D03921F9371; Wed, 29 May 2013 03:05:20 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.50 Message-ID: <20130529100520.26815.33081.idtracker@ietfa.amsl.com> Date: Wed, 29 May 2013 03:05:20 -0700 Cc: dime@ietf.org Subject: [Dime] I-D Action: draft-ietf-dime-app-design-guide-17.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 10:05:23 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Diameter Maintenance and Extensions Worki= ng Group of the IETF. Title : Diameter Applications Design Guidelines Author(s) : Lionel Morand Victor Fajardo Hannes Tschofenig Filename : draft-ietf-dime-app-design-guide-17.txt Pages : 21 Date : 2013-05-29 Abstract: The Diameter Base protocol provides facilities for protocol extensibility enabling to define new Diameter applications or modify existing applications. This document is a companion document to the Diameter base protocol that further explains and clarifies the rules to extend the Diameter base protocol. It is meant as a guidelines document and therefore it does not add, remove or change existing rules. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dime-app-design-guide There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-dime-app-design-guide-17 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dime-app-design-guide-17 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From lionel.morand@orange.com Wed May 29 03:11:34 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B896A21F93BA for ; Wed, 29 May 2013 03:11:34 -0700 (PDT) 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, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6UOyAA4+k4pS for ; Wed, 29 May 2013 03:11:30 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id B631021F8CE9 for ; Wed, 29 May 2013 03:11:14 -0700 (PDT) Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id BF6A73B4B19 for ; Wed, 29 May 2013 12:11:13 +0200 (CEST) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id A4BAB27C067 for ; Wed, 29 May 2013 12:11:13 +0200 (CEST) Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Wed, 29 May 2013 12:11:13 +0200 From: To: "dime@ietf.org" Thread-Topic: [Dime] I-D Action: draft-ietf-dime-app-design-guide-17.txt Thread-Index: AQHOXFQo/aPY4BgPs0KmNYAdCSe6AZkb7+9Q Date: Wed, 29 May 2013 10:11:12 +0000 Message-ID: <15891_1369822273_51A5D441_15891_2782_3_6B7134B31289DC4FAF731D844122B36E1F0F3B@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <20130529100520.26815.33081.idtracker@ietfa.amsl.com> In-Reply-To: <20130529100520.26815.33081.idtracker@ietfa.amsl.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.197.38.3] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.29.85419 Subject: Re: [Dime] I-D Action: draft-ietf-dime-app-design-guide-17.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 10:11:34 -0000 In this version: - small editorial corrections/id-nits - update of the section 5.11 (Diameter security mechanisms) to clarify that= IKEv2 is recommended instead of IKEv1. Cheers, Lionel -----Message d'origine----- De=A0: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part de i= nternet-drafts@ietf.org Envoy=E9=A0: mercredi 29 mai 2013 12:05 =C0=A0: i-d-announce@ietf.org Cc=A0: dime@ietf.org Objet=A0: [Dime] I-D Action: draft-ietf-dime-app-design-guide-17.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Diameter Maintenance and Extensions Worki= ng Group of the IETF. Title : Diameter Applications Design Guidelines Author(s) : Lionel Morand Victor Fajardo Hannes Tschofenig Filename : draft-ietf-dime-app-design-guide-17.txt Pages : 21 Date : 2013-05-29 Abstract: The Diameter Base protocol provides facilities for protocol extensibility enabling to define new Diameter applications or modify existing applications. This document is a companion document to the Diameter base protocol that further explains and clarifies the rules to extend the Diameter base protocol. It is meant as a guidelines document and therefore it does not add, remove or change existing rules. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dime-app-design-guide There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-dime-app-design-guide-17 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dime-app-design-guide-17 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete al= tere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for message= s that have been modified, changed or falsified. Thank you. From lionel.morand@orange.com Wed May 29 03:12:26 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A531021F93D1 for ; Wed, 29 May 2013 03:12:26 -0700 (PDT) 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, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0WDUw7d6w529 for ; Wed, 29 May 2013 03:12:22 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 4601A21F93D2 for ; Wed, 29 May 2013 03:12:22 -0700 (PDT) Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id B3D782641C6 for ; Wed, 29 May 2013 12:12:21 +0200 (CEST) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 9CAB84C06D for ; Wed, 29 May 2013 12:12:21 +0200 (CEST) Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Wed, 29 May 2013 12:12:21 +0200 From: To: "dime@ietf.org" Thread-Topic: [Dime] I-D Action: draft-ietf-dime-app-design-guide-17.txt Thread-Index: AQHOXFQo/aPY4BgPs0KmNYAdCSe6AZkb7+9QgAABR6A= Date: Wed, 29 May 2013 10:12:20 +0000 Message-ID: <11375_1369822341_51A5D485_11375_800_1_6B7134B31289DC4FAF731D844122B36E1F0F61@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <20130529100520.26815.33081.idtracker@ietfa.amsl.com> <15891_1369822273_51A5D441_15891_2782_3_6B7134B31289DC4FAF731D844122B36E1F0F3B@PEXCVZYM13.corporate.adroot.infra.ftgroup> In-Reply-To: <15891_1369822273_51A5D441_15891_2782_3_6B7134B31289DC4FAF731D844122B36E1F0F3B@PEXCVZYM13.corporate.adroot.infra.ftgroup> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.197.38.3] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.21.113319 Subject: Re: [Dime] I-D Action: draft-ietf-dime-app-design-guide-17.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 10:12:26 -0000 It was the last required change and the draft is ready for publication. Lionel -----Message d'origine----- De=A0: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part de l= ionel.morand@orange.com Envoy=E9=A0: mercredi 29 mai 2013 12:11 =C0=A0: dime@ietf.org Objet=A0: Re: [Dime] I-D Action: draft-ietf-dime-app-design-guide-17.txt In this version: - small editorial corrections/id-nits - update of the section 5.11 (Diameter security mechanisms) to clarify that= IKEv2 is recommended instead of IKEv1. Cheers, Lionel -----Message d'origine----- De=A0: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part de i= nternet-drafts@ietf.org Envoy=E9=A0: mercredi 29 mai 2013 12:05 =C0=A0: i-d-announce@ietf.org Cc=A0: dime@ietf.org Objet=A0: [Dime] I-D Action: draft-ietf-dime-app-design-guide-17.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Diameter Maintenance and Extensions Worki= ng Group of the IETF. Title : Diameter Applications Design Guidelines Author(s) : Lionel Morand Victor Fajardo Hannes Tschofenig Filename : draft-ietf-dime-app-design-guide-17.txt Pages : 21 Date : 2013-05-29 Abstract: The Diameter Base protocol provides facilities for protocol extensibility enabling to define new Diameter applications or modify existing applications. This document is a companion document to the Diameter base protocol that further explains and clarifies the rules to extend the Diameter base protocol. It is meant as a guidelines document and therefore it does not add, remove or change existing rules. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dime-app-design-guide There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-dime-app-design-guide-17 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dime-app-design-guide-17 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete al= tere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for message= s that have been modified, changed or falsified. Thank you. _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete al= tere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for message= s that have been modified, changed or falsified. Thank you. From jouni.nospam@gmail.com Thu May 30 02:38:14 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63D1A21F915C for ; Thu, 30 May 2013 02:38:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJezsBl0CI36 for ; Thu, 30 May 2013 02:38:13 -0700 (PDT) Received: from mail-ea0-x229.google.com (mail-ea0-x229.google.com [IPv6:2a00:1450:4013:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1C921F9676 for ; Thu, 30 May 2013 02:38:12 -0700 (PDT) Received: by mail-ea0-f169.google.com with SMTP id m14so39274eaj.0 for ; Thu, 30 May 2013 02:38:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=LeCS7Hdh4+/2dHgptC0Eh52gcwaRVgKsEwEloDFuAjs=; b=N8eaxBMYebAFDltmXl3ugBczBCm5GvNd9zmSj+rfVJ6lYFnNrzGSuD4I2xIGz6Br6y RpxWznovitoUfZa4OL/6PtzjquArq/6kA0dt8RL+rau1103rMt+Ewjf3A2HE+GCJ/oBl XELAlYuNveL/94yPHtG7nTNxA6BkXaK/J93q+3cCCO3pGX6hH6vNkM28283Sb2J+dfjP QQY45soVOwS0+ieEUKeQcv9IIT7Cq/PPQqTd5NSToRt3rO1WklHrqP0468k9W5EQxeMK EGtp7e/CywQEtnhol1DgsNkNcwBpblAgRc6k5/5GVu4FmYGoOlZjTqrWWJCCaz93oep3 g3cA== X-Received: by 10.14.107.69 with SMTP id n45mr9038410eeg.67.1369906692154; Thu, 30 May 2013 02:38:12 -0700 (PDT) Received: from ?IPv6:2001:1bc8:101:f101:4520:729f:9f71:d049? ([2001:1bc8:101:f101:4520:729f:9f71:d049]) by mx.google.com with ESMTPSA id m48sm59407231eeh.16.2013.05.30.02.38.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 02:38:08 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Jouni Korhonen In-Reply-To: <11375_1369822341_51A5D485_11375_800_1_6B7134B31289DC4FAF731D844122B36E1F0F61@PEXCVZYM13.corporate.adroot.infra.ftgroup> Date: Thu, 30 May 2013 12:38:06 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130529100520.26815.33081.idtracker@ietfa.amsl.com> <15891_1369822273_51A5D441_15891_2782_3_6B7134B31289DC4FAF731D844122B36E1F0F3B@PEXCVZYM13.corporate.adroot.infra.ftgroup> <11375_1369822341_51A5D485_11375_800_1_6B7134B31289DC4FAF731D844122B36E1F0F61@PEXCVZYM13.corporate.adroot.infra.ftgroup> To: "dime@ietf.org" X-Mailer: Apple Mail (2.1503) Cc: "dime-chairs@tools.ietf.org" Subject: [Dime] WGLC for draft-ietf-dime-app-design-guide-17 X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 May 2013 09:38:14 -0000 Folks, Since the last revision includes some changes that are beyond = editorials, there will be another quick one week WGLC for the = draft-ietf-dime-app-design-guide-17. Specifically pay attention to Section 5.11 changed security = recommendations. The WGLC starts today and ends 6th June 2013 EOB. - Jouni On May 29, 2013, at 1:12 PM, lionel.morand@orange.com wrote: > It was the last required change and the draft is ready for = publication. >=20 > Lionel >=20 > -----Message d'origine----- > De : dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part = de lionel.morand@orange.com > Envoy=E9 : mercredi 29 mai 2013 12:11 > =C0 : dime@ietf.org > Objet : Re: [Dime] I-D Action: draft-ietf-dime-app-design-guide-17.txt >=20 > In this version: >=20 > - small editorial corrections/id-nits > - update of the section 5.11 (Diameter security mechanisms) to clarify = that IKEv2 is recommended instead of IKEv1. >=20 > Cheers, >=20 > Lionel >=20 > -----Message d'origine----- > De : dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part = de internet-drafts@ietf.org > Envoy=E9 : mercredi 29 mai 2013 12:05 > =C0 : i-d-announce@ietf.org > Cc : dime@ietf.org > Objet : [Dime] I-D Action: draft-ietf-dime-app-design-guide-17.txt >=20 >=20 > 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. >=20 > Title : Diameter Applications Design Guidelines > Author(s) : Lionel Morand > Victor Fajardo > Hannes Tschofenig > Filename : draft-ietf-dime-app-design-guide-17.txt > Pages : 21 > Date : 2013-05-29 >=20 > Abstract: > The Diameter Base protocol provides facilities for protocol > extensibility enabling to define new Diameter applications or modify > existing applications. This document is a companion document to the > Diameter base protocol that further explains and clarifies the rules > to extend the Diameter base protocol. It is meant as a guidelines > document and therefore it does not add, remove or change existing > rules. >=20 >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-dime-app-design-guide >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-dime-app-design-guide-17 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dime-app-design-guide-17 >=20 >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime >=20 > = __________________________________________________________________________= _______________________________________________ >=20 > Ce message et ses pieces jointes peuvent contenir des informations = confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez = recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les = messages electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a = ete altere, deforme ou falsifie. Merci. >=20 > This message and its attachments may contain confidential or = privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and = delete this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for = messages that have been modified, changed or falsified. > Thank you. >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime >=20 > = __________________________________________________________________________= _______________________________________________ >=20 > Ce message et ses pieces jointes peuvent contenir des informations = confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez = recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les = messages electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a = ete altere, deforme ou falsifie. Merci. >=20 > This message and its attachments may contain confidential or = privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and = delete this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for = messages that have been modified, changed or falsified. > Thank you. >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From hannes.tschofenig@gmx.net Fri May 31 07:40:29 2013 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEE2921F9691 for ; Fri, 31 May 2013 07:40:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.346 X-Spam-Level: X-Spam-Status: No, score=-101.346 tagged_above=-999 required=5 tests=[AWL=0.634, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p8q-8TmSOPaY for ; Fri, 31 May 2013 07:40:25 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 54D6121F91A5 for ; Fri, 31 May 2013 07:40:25 -0700 (PDT) Received: from mailout-de.gmx.net ([10.1.76.28]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0Lds7x-1U15911lGF-00j3e7 for ; Fri, 31 May 2013 16:40:24 +0200 Received: (qmail invoked by alias); 31 May 2013 14:40:24 -0000 Received: from unknown (EHLO [10.255.135.144]) [194.251.119.201] by mail.gmx.net (mp028) with SMTP; 31 May 2013 16:40:24 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX18tvk1HF7QtUggKl5ZRQCBKcRbu7rdambt/HQgcOP PvXDk1SW41ItEt Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=iso-8859-1 From: Hannes Tschofenig In-Reply-To: Date: Fri, 31 May 2013 17:40:21 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130529100520.26815.33081.idtracker@ietfa.amsl.com> <15891_1369822273_51A5D441_15891_2782_3_6B7134B31289DC4FAF731D844122B36E1F0F3B@PEXCVZYM13.corporate.adroot.infra.ftgroup> <11375_1369822341_51A5D485_11375_800_1_6B7134B31289DC4FAF731D844122B36E1F0F61@PEXCVZYM13.corporate.adroot.infra.ftgroup> To: Jouni Korhonen X-Pgp-Agent: GPGMail 1.4.1 X-Mailer: Apple Mail (2.1085) X-Y-GMX-Trusted: 0 Cc: "dime@ietf.org" , "dime-chairs@tools.ietf.org" Subject: Re: [Dime] WGLC for draft-ietf-dime-app-design-guide-17 X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 14:40:29 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Jouni,=20 thanks for starting the working group last call.=20 I re-read the entire document and made a couple of editorial changes = here and there for improved clarity.=20 Here is the updated draft:=20 = https://github.com/hannestschofenig/tschofenig-ids/blob/master/diameter-de= sign-guide/draft-ietf-dime-app-design-guide-18.txt In a discussion with Sebastien a few days ago we were wondering whether = it would make sense to put a short section into the document that = explains what a document authors needs to do to register various = Diameter extensions (e.g., applications, command codes, AVPs).=20 Ciao Hannes On May 30, 2013, at 12:38 PM, Jouni Korhonen wrote: >=20 > Folks, >=20 > Since the last revision includes some changes that are beyond = editorials, there > will be another quick one week WGLC for the = draft-ietf-dime-app-design-guide-17. > Specifically pay attention to Section 5.11 changed security = recommendations. >=20 > The WGLC starts today and ends 6th June 2013 EOB. >=20 > - Jouni >=20 >=20 > On May 29, 2013, at 1:12 PM, lionel.morand@orange.com wrote: >=20 >> It was the last required change and the draft is ready for = publication. >>=20 >> Lionel >>=20 >> -----Message d'origine----- >> De : dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part = de lionel.morand@orange.com >> Envoy=E9 : mercredi 29 mai 2013 12:11 >> =C0 : dime@ietf.org >> Objet : Re: [Dime] I-D Action: = draft-ietf-dime-app-design-guide-17.txt >>=20 >> In this version: >>=20 >> - small editorial corrections/id-nits >> - update of the section 5.11 (Diameter security mechanisms) to = clarify that IKEv2 is recommended instead of IKEv1. >>=20 >> Cheers, >>=20 >> Lionel >>=20 >> -----Message d'origine----- >> De : dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part = de internet-drafts@ietf.org >> Envoy=E9 : mercredi 29 mai 2013 12:05 >> =C0 : i-d-announce@ietf.org >> Cc : dime@ietf.org >> Objet : [Dime] I-D Action: draft-ietf-dime-app-design-guide-17.txt >>=20 >>=20 >> 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. >>=20 >> Title : Diameter Applications Design Guidelines >> Author(s) : Lionel Morand >> Victor Fajardo >> Hannes Tschofenig >> Filename : draft-ietf-dime-app-design-guide-17.txt >> Pages : 21 >> Date : 2013-05-29 >>=20 >> Abstract: >> The Diameter Base protocol provides facilities for protocol >> extensibility enabling to define new Diameter applications or modify >> existing applications. This document is a companion document to the >> Diameter base protocol that further explains and clarifies the rules >> to extend the Diameter base protocol. It is meant as a guidelines >> document and therefore it does not add, remove or change existing >> rules. >>=20 >>=20 >>=20 >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-dime-app-design-guide >>=20 >> There's also a htmlized version available at: >> http://tools.ietf.org/html/draft-ietf-dime-app-design-guide-17 >>=20 >> A diff from the previous version is available at: >> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dime-app-design-guide-17 >>=20 >>=20 >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >>=20 >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime >>=20 >> = __________________________________________________________________________= _______________________________________________ >>=20 >> Ce message et ses pieces jointes peuvent contenir des informations = confidentielles ou privilegiees et ne doivent donc >> pas etre diffuses, exploites ou copies sans autorisation. Si vous = avez recu ce message par erreur, veuillez le signaler >> a l'expediteur et le detruire ainsi que les pieces jointes. Les = messages electroniques etant susceptibles d'alteration, >> France Telecom - Orange decline toute responsabilite si ce message a = ete altere, deforme ou falsifie. Merci. >>=20 >> This message and its attachments may contain confidential or = privileged information that may be protected by law; >> they should not be distributed, used or copied without authorisation. >> If you have received this email in error, please notify the sender = and delete this message and its attachments. >> As emails may be altered, France Telecom - Orange is not liable for = messages that have been modified, changed or falsified. >> Thank you. >>=20 >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime >>=20 >> = __________________________________________________________________________= _______________________________________________ >>=20 >> Ce message et ses pieces jointes peuvent contenir des informations = confidentielles ou privilegiees et ne doivent donc >> pas etre diffuses, exploites ou copies sans autorisation. Si vous = avez recu ce message par erreur, veuillez le signaler >> a l'expediteur et le detruire ainsi que les pieces jointes. Les = messages electroniques etant susceptibles d'alteration, >> France Telecom - Orange decline toute responsabilite si ce message a = ete altere, deforme ou falsifie. Merci. >>=20 >> This message and its attachments may contain confidential or = privileged information that may be protected by law; >> they should not be distributed, used or copied without authorisation. >> If you have received this email in error, please notify the sender = and delete this message and its attachments. >> As emails may be altered, France Telecom - Orange is not liable for = messages that have been modified, changed or falsified. >> Thank you. >>=20 >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org iQEcBAEBCgAGBQJRqLZVAAoJEGhJURNOOiAtaMoIAJd7aaEFPXyK5doFro2yzrEa 0si5Kml13T/WceO28mwYHcwgM4OoreZ+2I6lid0zTC2F2KDJ+xuGnvrZ6gAHK601 b5h85prw6Q+LrWW6dQXr5EUbs/5Qgx0VUo/tJy4LkY4iVYpqk1wfPHkv5wEgKZjB g9Gwfj+APTtftFCvp5Uk+HNv9LTJ4YNTA5PzSR2dC3H5SXTZA7wDpT+jYpUnlLge G7QfwVDUTvZWaUqDYOW117kIIFPA8YMEVK5zVSsLHBgQJ8uVe56pP77h6xsMwc7W BN5FbSnr6JuVSt7EHniOWOnOCTdQvQslDQOI1qSzojk6ovqOIzyzYPwLMiKDpQU=3D =3DnskR -----END PGP SIGNATURE-----