Re: [Anima] review comments draft-ietf-anima-stable-connectivity-03-rev Med.doc

<mohamed.boucadair@orange.com> Fri, 28 July 2017 12:02 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F2CD131FC8; Fri, 28 Jul 2017 05:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 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, RP_MATCHES_RCVD=-0.001, 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 HwZt56heiS83; Fri, 28 Jul 2017 05:02:28 -0700 (PDT)
Received: from relais-inet.orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32CDE12783A; Fri, 28 Jul 2017 05:02:28 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 98335C04E7; Fri, 28 Jul 2017 14:02:26 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.27]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 66347120055; Fri, 28 Jul 2017 14:02:26 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7C.corporate.adroot.infra.ftgroup ([fe80::8007:17b:c3b4:d68b%19]) with mapi id 14.03.0352.000; Fri, 28 Jul 2017 14:02:26 +0200
From: mohamed.boucadair@orange.com
To: Toerless Eckert <tte@cs.fau.de>
CC: "anima@ietf.org" <anima@ietf.org>, "draft-ietf-anima-stable-connectivity@ietf.org" <draft-ietf-anima-stable-connectivity@ietf.org>
Thread-Topic: review comments draft-ietf-anima-stable-connectivity-03-rev Med.doc
Thread-Index: AQHTBwlq4p6dbunGJUaeYa4krab8d6JpH4XA
Date: Fri, 28 Jul 2017 12:02:25 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A014351@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <20170727185150.GZ3889@faui40p.informatik.uni-erlangen.de>
In-Reply-To: <20170727185150.GZ3889@faui40p.informatik.uni-erlangen.de>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/AapMJlhGqTG2QDJE9y_SqDRUjFY>
Subject: Re: [Anima] review comments draft-ietf-anima-stable-connectivity-03-rev Med.doc
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 12:02:30 -0000

Hi Toerless, 

The new version looks much more better. Thanks. 

Some comments about these two minor point:

- "IPv4 to IPv6 NAT can be used." - Do you mean RFC7915
  I intentionally did not want to elaborate on the details of which of the 15? different
  NAT options can be used best. When i worked on this, i got a working setup with NAT-PT and i think
  also NAT64 statefull (RFC6146). This was mostly driven by whatever old router OS versions
  where available.Also your note re. rfc7757. The main issue is that the stateless translations would
  require matching address structures in he ACP, and i certainly would not want to fudge the ACP design
  to support NAT better. Rather use some horrific NAT option. That should even accelerate pushing IPv6
  into NOC/OAM equipment. 

  So, i didn't add any pointers to those RFCs you mentioned. I think its good if this is
  left as an exercise to the reader ;-)

Med: Fair. Please change "IPv4 to IPv6 NAT can be used" to "IPv4 to IPv6 translation can be used" because it is more than "Address" translation. 

- "I'm afraid NoO " - i did not get that.

Med: This was related to this part of your text: 

==
   Overall, the use of NAT is especially subject to the RoI (Return of
   Investment) considerations,  
========

The reasoning about NAT and RoI may seem to be intuitive, but I'm afraid it does not reflect the deployment reality. The use of NAT may even come for free or be a function of the traffic and so on.

I would delete the mention of RoI. 

Cheers,
Med

> -----Message d'origine-----
> De : Toerless Eckert [mailto:tte@cs.fau.de]
> Envoyé : jeudi 27 juillet 2017 20:52
> À : BOUCADAIR Mohamed IMT/OLN
> Cc : anima@ietf.org; draft-ietf-anima-stable-connectivity@ietf.org
> Objet : Re: review comments draft-ietf-anima-stable-connectivity-03-rev
> Med.doc
> 
> Thanks a lot, Mohamed for the thorough review!
> 
> I pushed -04 of the draft out with your changes incorporated. IMHO it's
> all great textual improvements but no logical changes, aka: should be fine
> for prior reviewers.
> 
> Diff:
> 
> http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.o
> rg/id/draft-ietf-anima-stable-connectivity-
> 03.txt&url2=https://www.ietf.org/id/draft-ietf-anima-stable-connectivity-
> 04.txt
> 
> Your original review doc:
> 
> https://github.com/anima-wg/autonomic-control-plane/blob/master/draft-
> ietf-anima-stable-connectivity/03-review-mohamed.boucadair.doc
> 
> My reply comments:
> 
> https://github.com/anima-wg/autonomic-control-plane/blob/master/draft-
> ietf-anima-stable-connectivity/03-review-mohamed.boucadair-reply.txt
> 
> While incorporating your review, i also figured that it would be good if
> ACP connect
> would allow auto-configuration of NMS hosts, so i added a paragraph to
> mandate RFC4191,
> but i didn't rev ACP draft just for that yet, so here's just diff on
> github for that;
> 
> http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.o
> rg/id/draft-ietf-anima-autonomic-control-plane-
> 08.txt&url2=https://raw.githubusercontent.com/anima-wg/autonomic-control-
> plane/af74117400b6a5a7fca1acf2ab910d64a580a5c9/draft-ietf-anima-autonomic-
> control-plane/draft-ietf-anima-autonomic-control-plane.txt
> 
> Cheers
>     Toerless
> 
> On Mon, Jul 24, 2017 at 05:49:07AM +0000, mohamed.boucadair@orange.com
> wrote:
> > Dear Toreless,
> >
> > I'm resending this document as I didn't receive an ACK from your side.
> >
> > Please consider those as part of the WGLC comments.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De : BOUCADAIR Mohamed IMT/OLN
> > > Envoyé : vendredi 7 juillet 2017 14:58
> > > À : 'tte+ietf@cs.fau.de'
> > > Objet : Envoi d?un message : draft-ietf-anima-stable-connectivity-03-
> rev
> > > Med.doc
> > >
> > > Dear Toreless,
> > >
> > > Please find some comments about this draft.
> > >
> > > Cheers,
> > > Med
>