Re: [OPSAWG] CLAT (was TR: New Version Notification for draft-ietf-opsawg-nat-yang-00.txt)
<mohamed.boucadair@orange.com> Fri, 18 August 2017 14:35 UTC
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27BAA13218C for <opsawg@ietfa.amsl.com>; Fri, 18 Aug 2017 07:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=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 mJUBXVoJ_1CX for <opsawg@ietfa.amsl.com>; Fri, 18 Aug 2017 07:35:51 -0700 (PDT)
Received: from relais-inet.orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F0B21323BA for <opsawg@ietf.org>; Fri, 18 Aug 2017 07:35:49 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id B8A226056B; Fri, 18 Aug 2017 16:35:47 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.41]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 7D5CF180061; Fri, 18 Aug 2017 16:35:47 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM31.corporate.adroot.infra.ftgroup ([fe80::2cc9:4bac:7b7d:229d%19]) with mapi id 14.03.0361.001; Fri, 18 Aug 2017 16:35:45 +0200
From: mohamed.boucadair@orange.com
To: Lee Howard <lee@asgard.org>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
CC: "opsawg@ietf.org" <opsawg@ietf.org>, JACQUENET Christian IMT/OLN <christian.jacquenet@orange.com>, "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>, Qin Wu <bill.wu@huawei.com>, "sureshk@juniper.net" <sureshk@juniper.net>
Thread-Topic: CLAT (was TR: New Version Notification for draft-ietf-opsawg-nat-yang-00.txt)
Thread-Index: AdMYLPDNz1ZKlJbMRqCG7OBhszrdBAAAjECQ
Date: Fri, 18 Aug 2017 14:35:45 +0000
Message-ID: <f054f125-3f7f-4a87-af5b-39aca98583eb@OPEXCLILM31.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.168.234.3]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/lpNfQzd9jtThwum3oquwftuCaVk>
Subject: Re: [OPSAWG] CLAT (was TR: New Version Notification for draft-ietf-opsawg-nat-yang-00.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Aug 2017 14:35:54 -0000
Re-, Forwarded to the OPSAWG list. Please use this messages when replying. Apologies for the inconvenience. Cheers, Med > -----Message d'origine----- > De : BOUCADAIR Mohamed IMT/OLN > Envoyé : vendredi 18 août 2017 16:19 > À : 'Lee Howard'; jordi.palet@consulintel.es > Cc : opsawg-chairs@ietf.org; JACQUENET Christian IMT/OLN; Senthil > Sivakumar (ssenthil); 'Qin Wu'; sureshk@juniper.net > Objet : CLAT (was TR: New Version Notification for draft-ietf-opsawg-nat- > yang-00.txt) > > Hi Lee, > > (I'm adding Jordi to the discussion since he is familiar with CLAT in a > CPE) > > You suggested in Prague to add CLAT to the NAT YANG module. > > Please find below how we are planning to cover it in the next iteration of > the draft: > > (1) If a dedicated prefix is configured for CLAT, then only a stateless > XLAT will be required. That is, no mapping table will be maintained at > all. Since the module already includes NAT64 prefix(es), the CLAT IPv6 > prefix will be missing. The tree structure can be updated as follows: > > OLD: > +--rw nat64-prefixes* [nat64-prefix] > | +--rw nat64-prefix inet:ipv6-prefix > | +--rw destination-ipv4-prefix* [ipv4-prefix] > | +--rw ipv4-prefix inet:ipv4-prefix > > NEW: > > +--rw nat64-prefixes* [nat64-prefix] > | +--rw nat64-prefix inet:ipv6-prefix > | +--rw destination-ipv4-prefix* [ipv4-prefix] > | +--rw ipv4-prefix inet:ipv4-prefix > +--rw clat-ipv6-prefix? inet:ipv6-prefix > > (2) If no dedicated /64 prefix is provided, a NAT44 will be required. A > stateless XLAT will be then applied on NATed packets. This case is > natively supported by the current YANG model. > > A CLAT module can automatically select an IPv4 address from 192.0.0.0/29 > (RFC7335). This address can also be set. To do so, the tree structure can > be updated with: > > NEW: > ... > +--rw clat-ipv4-address? inet:ipv4-address > ... > > The CLAT IPv4 address will be taken by default from 192.0.0.0/29. Other > addresses can be used. > > Lee/Jordi, are there any other required changes? > > Thank you. > > Cheers, > Med > > > -----Message d'origine----- > > De : OPSAWG [mailto:opsawg-bounces@ietf.org] De la part de > > mohamed.boucadair@orange.com > > Envoyé : vendredi 18 août 2017 15:46 > > À : opsawg@ietf.org > > Cc : sureshk@juniper.net; JACQUENET Christian IMT/OLN > > Objet : [OPSAWG] TR: New Version Notification for draft-ietf-opsawg-nat- > > yang-00.txt > > > > Dear all, > > > > The -00 version integrates the comments received during the Call for > > Adoption: > > > > - Clarify how Destination NAT is covered (Tianran) > > - Follow the NMDA guidelines (Juergen and Qin) > > - Include a generic structure for ALGs instead of listing supported ones > > (Juergen) > > - Include a discussion about how other transport protocols are/can be > > supported (Juergen) > > - Include a comprehensive list of examples (Juergen) > > - Move the example to an appendix (Juergen) > > > > We do still have one pending comment that was raised by Lee Howard when > I > > presented in Prague: add CLAT to the list. > > > > Comments are more than welcome. Please review. > > > > Cheers, > > Med > > > > > -----Message d'origine----- > > > De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > > > Envoyé : vendredi 18 août 2017 15:31 > > > À : BOUCADAIR Mohamed IMT/OLN; Senthil Sivakumar; JACQUENET Christian > > > IMT/OLN; opsawg-chairs@ietf.org; Qin Wu > > > Objet : New Version Notification for draft-ietf-opsawg-nat-yang-00.txt > > > > > > > > > A new version of I-D, draft-ietf-opsawg-nat-yang-00.txt > > > has been successfully submitted by Mohamed Boucadair and posted to the > > > IETF repository. > > > > > > Name: draft-ietf-opsawg-nat-yang > > > Revision: 00 > > > Title: A YANG Data Model for Network Address Translation (NAT) > and > > > Network Prefix Translation (NPT) > > > Document date: 2017-08-18 > > > Group: opsawg > > > Pages: 67 > > > URL: https://www.ietf.org/internet-drafts/draft-ietf- > opsawg- > > > nat-yang-00.txt > > > Status: https://datatracker.ietf.org/doc/draft-ietf-opsawg- > nat- > > > yang/ > > > Htmlized: https://tools.ietf.org/html/draft-ietf-opsawg-nat- > yang- > > 00 > > > Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf- > opsawg- > > > nat-yang-00 > > > > > > > > > Abstract: > > > For the sake of network automation and the need for programming > > > Network Address Translation (NAT) function in particular, a data > > > model for configuring and managing the NAT is essential. This > > > document defines a YANG data model for the NAT function. NAT44, > > > NAT64, and NPTv6 are covered in this document. > > > > > > > > > > > > > > > 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 > > > > _______________________________________________ > > OPSAWG mailing list > > OPSAWG@ietf.org > > https://www.ietf.org/mailman/listinfo/opsawg
- Re: [OPSAWG] CLAT (was TR: New Version Notificati… mohamed.boucadair
- Re: [OPSAWG] CLAT (was TR: New Version Notificati… JORDI PALET MARTINEZ
- Re: [OPSAWG] CLAT (was TR: New Version Notificati… Lee Howard
- Re: [OPSAWG] CLAT (was TR: New Version Notificati… mohamed.boucadair