IETF Logo Mail Archive

Re: [OPSAWG] some too late nits in draft-ietf-opsawg-nat-yang-17

<mohamed.boucadair@orange.com> Wed, 10 October 2018 11:22 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 55A0F130ED6; Wed, 10 Oct 2018 04:22:32 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 TXkigcPhu-6F; Wed, 10 Oct 2018 04:22:30 -0700 (PDT)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CDAD130ED3; Wed, 10 Oct 2018 04:22:30 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id 42VWsd1v79z10nX; Wed, 10 Oct 2018 13:22:29 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.66]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 42VWsd13CwzFpWY; Wed, 10 Oct 2018 13:22:29 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA1.corporate.adroot.infra.ftgroup ([fe80::95e2:eb4b:3053:fabf%19]) with mapi id 14.03.0415.000; Wed, 10 Oct 2018 13:22:28 +0200
From: mohamed.boucadair@orange.com
To: tom petch <ietfc@btconnect.com>, Ignas Bagdonas <ibagdona@gmail.com>
CC: "opsawg-chairs@ietf.org" <opsawg-chairs@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-ietf-opsawg-nat-yang@ietf.org" <draft-ietf-opsawg-nat-yang@ietf.org>
Thread-Topic: some too late nits in draft-ietf-opsawg-nat-yang-17
Thread-Index: AQHUYIFohvcba2lv7E2jDHYZgCK0nqUYUWPQ
Date: Wed, 10 Oct 2018 11:22:27 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302DFEDE68@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <153754677994.7443.9092939251929421656.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B93302DFE5AA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <4E1DE484-9B3C-4977-A4F3-13F716A109AD@kuehlewind.net> <787AE7BB302AE849A7480A190F8B93302DFE5C3E@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <23FA14C7-66E0-4A3C-B0AB-91CB3DF48203@kuehlewind.net> <20180924101247.hokoet4cgtxwcvim@anna.jacobs.jacobs-university.de> <021801d46081$4455ac20$4001a8c0@gateway.2wire.net>
In-Reply-To: <021801d46081$4455ac20$4001a8c0@gateway.2wire.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.2]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/8U1UYYHK-V7vQ6RNCL2MC5GRCDw>
Subject: Re: [OPSAWG] some too late nits in draft-ietf-opsawg-nat-yang-17
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Oct 2018 11:22:33 -0000

Hi Tom, 

Thank you for sharing the comments. 

Please see inline. 

Cheers,
Med

> -----Message d'origine-----
> De : tom petch [mailto:ietfc@btconnect.com]
> Envoyé : mercredi 10 octobre 2018 12:10
> À : Ignas Bagdonas
> Cc : opsawg-chairs@ietf.org; opsawg@ietf.org; draft-ietf-opsawg-nat-
> yang@ietf.org
> Objet : some too late nits in draft-ietf-opsawg-nat-yang-17
> 
> I note that
> RFC7050

[Med] This is an informative reference as Section 5.1 of that RFC provides some information about what is meant by destination-based pref64. We could provide RFC7225 as another pointer, but the intent is not to be exhaustive here.  

> RFC7335

[Med] This is not required to implement 646xlat, but 6877 is normative. RFC7335 is provided for information purposes to understand from where we extracted some prefixes cited in the text.  

> appear in YANG description clauses but are only Informative References,
> not Normative as they should be.
> 
> Security Considerations references TLS1.2 RFC5246 where TLS1.3 RFC8446
> should now be used

[Med] The document was approved by the IESG prior to the update to yang security guidelines available at https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines: 

==
Update from RFC5246 to RFC8446 - [WK - 2018-10-08 ]
==

I'm neutral on this one. 

> 
> A Note to the RFC Editor perhaps
> 
> Tom Petch

v2.23.0 | Report a Bug | By Email