Re: [Dime] Fwd: New Version Notification for draft-zhou-dime-4over6-provisioning-04.txt
<lionel.morand@orange.com> Wed, 17 September 2014 11:12 UTC
Return-Path: <lionel.morand@orange.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9387D1A0202 for <dime@ietfa.amsl.com>; Wed, 17 Sep 2014 04:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aXi6feq0E0AH for <dime@ietfa.amsl.com>; Wed, 17 Sep 2014 04:12:27 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E1231A0067 for <dime@ietf.org>; Wed, 17 Sep 2014 04:12:27 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 237EB18C36E; Wed, 17 Sep 2014 13:12:25 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 07A1F35C07B; Wed, 17 Sep 2014 13:12:25 +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.03.0195.001; Wed, 17 Sep 2014 13:12:24 +0200
From: lionel.morand@orange.com
To: Tom Taylor <tom.taylor.stds@gmail.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] Fwd: New Version Notification for draft-zhou-dime-4over6-provisioning-04.txt
Thread-Index: AQHP0hnq2qfCS0mUN0+aJfg/GZ8d0ZwFEFrQ
Date: Wed, 17 Sep 2014 11:12:23 +0000
Message-ID: <6341_1410952345_54196C99_6341_4311_1_6B7134B31289DC4FAF731D844122B36E721810@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <20140917012142.28396.19843.idtracker@ietfa.amsl.com> <5418E8F8.9010605@gmail.com>
In-Reply-To: <5418E8F8.9010605@gmail.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.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.9.17.72421
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/QKzOcaLoMuIcOo-IYCSak1k-Uhs
Subject: Re: [Dime] Fwd: New Version Notification for draft-zhou-dime-4over6-provisioning-04.txt
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 11:12:29 -0000
Hi Tom, Coming back on the need for a new format ("Common prefix Data format"), could you please explain (or remind me) why this new AVP format would be simpler than creating a Grouped AVP as soon as Prefix or Address can be provisioned? For instance, based on the current draft, the Tunnel-Source-Pref-Or-Addr is defined as a single AVP using the new AVP format defined in this draft: 3.4. Tunnel-Source-Pref-Or-Addr AVP The Tunnel-Source-Pref-Or-Addr AVP (AVP Code TBD02) conveys either the IPv6 Binding Prefix or the tunnel source address on the CE, as described in Section 2.2. The Tunnel-Source-Pref-Or-Addr AVP uses the common prefix data format. The AddressType field MUST be set to 2 (IPv6). Valid values in the PrefixLength field are from 0 to 128 (full address). This AVP is defined separately from the LW4over6-Binding AVP (which includes it) to provide flexibility in the transport of the tunnel source address from the provisioning system to AAA. But the same info could be also provided as follow: 3.4. Tunnel-Source-Pref-Or-Addr AVP The Tunnel-Source-Pref-Or-Addr (AVP Code TBD0X) is of type Grouped. It MUST contains either an either the IPv6 Binding Prefix or the tunnel source address on the CE, as described in Section 2.2. Tunnel-Source-Pref-Or-Addr ::= < AVP Header: TBD0X > [ Tunnel-Source-Address ] [ Tunnel-Source-Prefix ] *[ AVP ] 3.X Tunnel-Source-Address AVP The Tunnel-Source-Address AVP (AVP Code xxx) is of type Address and specifies the tunnel source IPv6 address on the CE. 3.Y. Framed-IPv6-Prefix AVP The Tunnel-Source-Prefix AVP (AVP Code yyy) is of type OctetString and contains the IPv6 Binding Prefix on the CE. If there is no risk of clash, the existing Framed-IPv6-Prefix AVP could even be reused for the second one. This alternative would have the advantage not to define a new format. I'm not saying that the definition of any new format should be prohibited. But in this case, it seems weird to have to define a new format for combining different types of information that can be already carried in existing AVPs. About the link with Softwires, we need to ensure that the set of information defined in this document has reviewed and somehow endorsed by the WG. Then I think it will become a pure Dime discussion. Lionel -----Message d'origine----- De : DiME [mailto:dime-bounces@ietf.org] De la part de Tom Taylor Envoyé : mercredi 17 septembre 2014 03:51 À : dime@ietf.org Objet : [Dime] Fwd: New Version Notification for draft-zhou-dime-4over6-provisioning-04.txt This is the mature version of a document on which DIME has provided advice in the past. Please have a quick look and see whether it makes sense in Diameter terms. If it is OK, I'm not sure what process the Chairs want to follow: adopt as a DIME document, or pass it off to Softwires? Tom Taylor -------- Original Message -------- Subject: New Version Notification for draft-zhou-dime-4over6-provisioning-04.txt Date: Tue, 16 Sep 2014 18:21:42 -0700 From: internet-drafts@ietf.org To: M. Boucadair <mohamed.boucadair@orange.com>, "Qiong Sun" <sunqiong@ctbri.com.cn>, "Tom Taylor" <tom.taylor.stds@gmail.com>, Cathy Zhou <cathy.zhou@huawei.com>, Qiong Sun <sunqiong@ctbri.com.cn>, T. Taylor <tom.taylor.stds@gmail.com>, "Cathy Zhou" <cathy.zhou@huawei.com>, "Mohamed Boucadair" <mohamed.boucadair@orange.com> A new version of I-D, draft-zhou-dime-4over6-provisioning-04.txt has been successfully submitted by T. Taylor and posted to the IETF repository. Name: draft-zhou-dime-4over6-provisioning Revision: 04 Title: Attribute-Value Pairs For Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional Solutions Document date: 2014-09-16 Group: Individual Submission Pages: 17 URL: http://www.ietf.org/internet-drafts/draft-zhou-dime-4over6-provisioning-04.txt Status: https://datatracker.ietf.org/doc/draft-zhou-dime-4over6-provisioning/ Htmlized: http://tools.ietf.org/html/draft-zhou-dime-4over6-provisioning-04 Diff: http://www.ietf.org/rfcdiff?url2=draft-zhou-dime-4over6-provisioning-04 Abstract: During the transition from IPv4 to IPv6, customer equipment may have to support one of the various transition methods that have been defined for carrying IPv4 packets over IPv6. This document enumerates the information that needs to be provisioned on a customer edge router to support a list of transition techniques based on tunneling IPv4 in IPv6, with a view to defining reusable components for a reasonable transition path between these techniques. To the extent that the provisioning is done dynamically, AAA support is needed to provide the information to the network server responsible for passing the information to the customer equipment. This document specifies Diameter (RFC 6733) attribute-value pairs to be used for that purpose. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime _________________________________________________________________________________________________________________________ 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, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
- [Dime] Fwd: New Version Notification for draft-zh… Tom Taylor
- Re: [Dime] Fwd: New Version Notification for draf… lionel.morand
- Re: [Dime] Fwd: New Version Notification for draf… Tom Taylor
- Re: [Dime] Fwd: New Version Notification for draf… lionel.morand
- Re: [Dime] Fwd: New Version Notification for draf… Tom Taylor