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

<mohamed.boucadair@orange.com> Fri, 27 September 2019 12:35 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 4AFED12004C; Fri, 27 Sep 2019 05:35:40 -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 QwE89UBGnJB5; Fri, 27 Sep 2019 05:35:38 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F31F12001E; Fri, 27 Sep 2019 05:35:38 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id 46frqX5ZSBz1yDR; Fri, 27 Sep 2019 14:35:36 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.104]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 46frqX21mRz1xpG; Fri, 27 Sep 2019 14:35:36 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM5F.corporate.adroot.infra.ftgroup ([fe80::193b:bc32:1ad3:362d%21]) with mapi id 14.03.0468.000; Fri, 27 Sep 2019 14:35:35 +0200
From: mohamed.boucadair@orange.com
To: "Scott O. Bradner" <sob@sobco.com>, Carsten Bormann <cabo@tzi.org>
CC: "draft-ietf-core-hop-limit.all@ietf.org" <draft-ietf-core-hop-limit.all@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] Opsdir last call review of draft-ietf-core-hop-limit-05
Thread-Index: AQHVdS+oTiCecyibckiPewmZ2JLUy6c/dU1g
Date: Fri, 27 Sep 2019 12:35:35 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933031327893@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> <20190927114946.igkh7f3evmclwt4p@EMB-918HFH01> <30446701-ADE2-4231-A987-CB6AE906A3E8@tzi.org> <896FEE7F-66EB-4639-AA1F-0C641FFFC53E@sobco.com>
In-Reply-To: <896FEE7F-66EB-4639-AA1F-0C641FFFC53E@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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/-fD2qHwXActFE_4hZrj78eCYpak>
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 12:35:41 -0000

Re-,

That's fair. This is supposed to be fixed in the future with "Extends/Extended by" tag in draft-kuehlewind-update-tag. 

I'm afraid that we can't do much for hop-limit. 

Cheers,
Med

> -----Message d'origine-----
> De : core [mailto:core-bounces@ietf.org] De la part de Scott O. Bradner
> Envoyé : vendredi 27 septembre 2019 14:33
> À : Carsten Bormann
> Cc : draft-ietf-core-hop-limit.all@ietf.org; ops-dir@ietf.org;
> ietf@ietf.org; core@ietf.org
> Objet : Re: [core] Opsdir last call review of draft-ietf-core-hop-limit-05
> 
> 
> 
> > On Sep 27, 2019, at 8:24 AM, Carsten Bormann <cabo@tzi.org> wrote:
> >
> > .  Generally, we don’t use “updates” for specifications that merely
> exercise an extension point, so I don’t think hop-limit “updates” RFC
> 7252, but the “updates” label is in active discussion already anyway.
> 
> a major advantage of listing something like this as an update is that the
> implementor will know about it - if there is no hint in the index entry
> for the old RFC that there is a related RFC it would be
> very easy to overlook
> 
> Scott
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core