Re: [core] Opsdir last call review of draft-ietf-core-hop-limit-05

<mohamed.boucadair@orange.com> Fri, 27 September 2019 11:55 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1BFF12004F; Fri, 27 Sep 2019 04:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 x7JVyhqZuKEV; Fri, 27 Sep 2019 04:55:05 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.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 48B5F120800; Fri, 27 Sep 2019 04:55:05 -0700 (PDT)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 46fqwl7260zBryr; Fri, 27 Sep 2019 13:55:03 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.64]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 46fqwl5nR6z1xnn; Fri, 27 Sep 2019 13:55:03 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBMA3.corporate.adroot.infra.ftgroup ([fe80::90fe:7dc1:fb15:a02b%21]) with mapi id 14.03.0468.000; Fri, 27 Sep 2019 13:55:03 +0200
From: mohamed.boucadair@orange.com
To: "Scott O. Bradner" <sob@sobco.com>
CC: "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-core-hop-limit.all@ietf.org" <draft-ietf-core-hop-limit.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "core@ietf.org" <core@ietf.org>
Thread-Topic: Opsdir last call review of draft-ietf-core-hop-limit-05
Thread-Index: AQHVdSKlBpG8wxh8E0C67brec56AjKc/aWLQ
Date: Fri, 27 Sep 2019 11:55:02 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933031327811@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <156954173082.31982.2465512704956520690@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B9330313276CF@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <A63F6779-653D-4DC6-9A79-E3983A742714@sobco.com>
In-Reply-To: <A63F6779-653D-4DC6-9A79-E3983A742714@sobco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
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/core/sGrlWhcxXuKW7exBFrxRo8sryig>
Subject: Re: [core] Opsdir last call review of draft-ietf-core-hop-limit-05
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2019 11:55:07 -0000

Re-,

Yes, you are right. 

But, this was fixed in the updated version I shared (https://github.com/boucadair/draft-hop-limit/blob/master/draft-ietf-core-hop-limit-06.txt): the structure of the table in the IANA section is aligned with the one in the IANA registry. 

The OLD table was moved into the core text. 

Cheers,
Med

> -----Message d'origine-----
> De : Scott O. Bradner [mailto:sob@sobco.com]
> Envoyé : vendredi 27 septembre 2019 13:00
> À : BOUCADAIR Mohamed TGI/OLN
> Cc : ops-dir@ietf.org; draft-ietf-core-hop-limit.all@ietf.org;
> ietf@ietf.org; core@ietf.org
> Objet : Re: Opsdir last call review of draft-ietf-core-hop-limit-05
> 
> 
> 
> > On Sep 27, 2019, at 4:30 AM, mohamed.boucadair@orange.com wrote:
> >
> >
> >> (that
> >> the IANA registry does not include the option categories)  and would
> >> suggest
> >> that section 6.2 specifically refer back to section 5.10 of RFC 7252
> and
> >> say
> >> that it is an extension of the table in the RFC.
> >
> > [Med] No need to mention this is an "extension" of the table in 7252.
> The IANA registry is used to maintain the updated table.
> 
> not quite the case - the IANA maintains a list of options - the table
> includes additional information not maintained by the IANA
> (but maybe should be)
> 
> Scott