[OPSAWG] TR: New Version Notification for draft-ietf-opsawg-nat-yang-00.txt

<mohamed.boucadair@orange.com> Fri, 18 August 2017 13:46 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 CC4EB1323C9 for <opsawg@ietfa.amsl.com>; Fri, 18 Aug 2017 06:46:19 -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 35pz8GLOLS7w for <opsawg@ietfa.amsl.com>; Fri, 18 Aug 2017 06:46:17 -0700 (PDT)
Received: from relais-inet.orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A9451323FB for <opsawg@ietf.org>; Fri, 18 Aug 2017 06:46:14 -0700 (PDT)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar24.francetelecom.fr (ESMTP service) with ESMTP id 066F7C014F; Fri, 18 Aug 2017 15:46:13 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.41]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id D279F80062; Fri, 18 Aug 2017 15:46:12 +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 15:46:09 +0200
From: mohamed.boucadair@orange.com
To: "opsawg@ietf.org" <opsawg@ietf.org>
CC: 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: New Version Notification for draft-ietf-opsawg-nat-yang-00.txt
Thread-Index: AQHTGCYxFTBAjXjWbk+rPM0P5RoFsqKKHPCg
Date: Fri, 18 Aug 2017 13:46:08 +0000
Message-ID: <ac093868-b6ad-49b7-9449-959af2e2b0e7@OPEXCLILM31.corporate.adroot.infra.ftgroup>
References: <150306304258.14107.7355173713892326702.idtracker@ietfa.amsl.com>
In-Reply-To: <150306304258.14107.7355173713892326702.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.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/QKcQ9MldKW6pIu_enI0UIkLueOE>
Subject: [OPSAWG] 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 13:46:20 -0000

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