Re: [Dots] AD review of draft-ietf-dots-data-channel-25

<mohamed.boucadair@orange.com> Mon, 25 February 2019 06:18 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD66B130DE4; Sun, 24 Feb 2019 22:18:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 JdvUJkLGwwoe; Sun, 24 Feb 2019 22:18:38 -0800 (PST)
Received: from 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 5677A12F1AC; Sun, 24 Feb 2019 22:18:38 -0800 (PST)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 447BbJ2n6jz2xnl; Mon, 25 Feb 2019 07:18:36 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.20]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 447BbJ1m2VzCqks; Mon, 25 Feb 2019 07:18:36 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBMA1.corporate.adroot.infra.ftgroup ([fe80::f04d:ad3c:61de:a175%21]) with mapi id 14.03.0435.000; Mon, 25 Feb 2019 07:18:36 +0100
From: mohamed.boucadair@orange.com
To: Benjamin Kaduk <kaduk@mit.edu>
CC: "draft-ietf-dots-data-channel@ietf.org" <draft-ietf-dots-data-channel@ietf.org>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: AD review of draft-ietf-dots-data-channel-25
Thread-Index: AQHUyTUuwyprX++Zj0q/Tpc5E7J3eaXpxvrggAZKQzA=
Date: Mon, 25 Feb 2019 06:18:35 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA24A19@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <20190213164622.GX56447@kduck.mit.edu> <787AE7BB302AE849A7480A190F8B93302EA1F03D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20190214191707.GM56447@kduck.mit.edu> <20190220155847.GC69562@kduck.mit.edu> <787AE7BB302AE849A7480A190F8B93302EA230C1@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302EA230C1@OPEXCAUBMA2.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.114.13.247]
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/dots/yrjdPZdzC_VtY2XuPzwIzvveI4Y>
Subject: Re: [Dots] AD review of draft-ietf-dots-data-channel-25
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2019 06:18:40 -0000

Hi Ben, 

The updated version with this change is available online.

Cheers,
Med

> -----Message d'origine-----
> De : mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
> Envoyé : jeudi 21 février 2019 07:16
> À : Benjamin Kaduk
> Cc : draft-ietf-dots-data-channel@ietf.org; dots@ietf.org
> Objet : RE: AD review of draft-ietf-dots-data-channel-25
> 
> Hi Ben,
> 
> Done in my local copy.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Benjamin Kaduk [mailto:kaduk@mit.edu]
> > Envoyé : mercredi 20 février 2019 16:59
> > À : BOUCADAIR Mohamed TGI/OLN
> > Cc : draft-ietf-dots-data-channel@ietf.org; dots@ietf.org
> > Objet : Re: AD review of draft-ietf-dots-data-channel-25
> >
> > On Thu, Feb 14, 2019 at 01:17:07PM -0600, Benjamin Kaduk wrote:
> > >
> > > On Thu, Feb 14, 2019 at 02:31:26PM +0000, mohamed.boucadair@orange.com
> > wrote:
> > > >
> > > > > -----Message d'origine-----
> > > > > De : Benjamin Kaduk [mailto:kaduk@mit.edu]
> > > > > Envoyé : mercredi 13 février 2019 17:46
> > > > > À : draft-ietf-dots-data-channel@ietf.org
> > > > > Cc : dots@ietf.org
> > > > > Objet : AD review of draft-ietf-dots-data-channel-25
> > > > >
> > > > >
> > > > > Section 3.5
> > > > >
> > > > > I had to read up on RESTCONF and NETCONF while reviewing this, but
> from
> > > > > what I've seen so far, the "error-severity" field is only present in
> > > > > NETCONF and not RESTCONF.  If so, then we shouldn't need to talk
> about
> > it
> > > > > here, since we use RESTCONF exclusively.  I also couldn't find
> whether
> > > > > there's a registry that we should add the "loop-detected" error-tag
> to.
> > > > > Can anyone here help me out?
> > > > >
> > > >
> > > > [Med] We used the template in
> > https://tools.ietf.org/html/rfc6241#appendix-A because the errors in 8040
> are
> > the ones imported from there.
> > >
> > > Thanks for the pointer.   It sounds like I'll need to ask around about
> this
> > > one.
> >
> > Benoit and Martin confirm that "error-severity" has no purpose in RESTCONF,
> > so I think we can safely drop this line.
> >
> > -Ben