Re: [core] I-D Action: draft-ietf-core-sid-06.txt

"Rob Wilton (rwilton)" <rwilton@cisco.com> Fri, 29 March 2019 11:04 UTC

Return-Path: <rwilton@cisco.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 E4855120271 for <core@ietfa.amsl.com>; Fri, 29 Mar 2019 04:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 gTflUhZMp4wd for <core@ietfa.amsl.com>; Fri, 29 Mar 2019 04:04:18 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71BCA12026A for <core@ietf.org>; Fri, 29 Mar 2019 04:04:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20826; q=dns/txt; s=iport; t=1553857458; x=1555067058; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Eo7h42mXP+wTc0mqiPy55lmNV3kmihyEe0Vkg3dA3xY=; b=Cx0lmEEMeRgKi2JEDoN4G5OQnpMY5TiEwgWq3eWwpkbgiSvv3sGSTSqa bDp/G6BW0rffiYwUZV1Js9tM1DcmfBjGH374i/tDOtqWvyzCH+yAJG8OY y6yeKblmz4Mod8+F7Q0iGNjYmZ5S1bsokZE6X6+VQO1kLeakZlN9Cx0zt 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAACF+51c/5FdJa1aChkBAQEBAQEBAQEBAQEHAQEBAQEBgVEEAQEBAQELAYEOgQJogQMnCoQEiByLKYINkkWFdxSBZw0BARgBCoRJAheFICI0CQ0BAQMBAQkBAwJtHAyFSgEBAQQBASEKQRsCAQYCEQQBAQEnAwICAiULFAkIAgQBEggGgxWBdQ+NRZtmgS+ENAIOQYUeD4EvAYsxF4FAP4ERgxI+gmEBAQIBARaBDw1hglSCVwOMeYQilBAJAoRlgwWGAIVTIoIDXYUlikqBPYsshgmNMQIRFYEuDRI4gVZwFRohgmwJgg0Xg0uFFIU/QTGOVoEfAQE
X-IronPort-AV: E=Sophos;i="5.60,284,1549929600"; d="scan'208,217";a="530466411"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Mar 2019 11:04:12 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x2TB4CNn023297 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 29 Mar 2019 11:04:12 GMT
Received: from xch-rcd-007.cisco.com (173.37.102.17) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 29 Mar 2019 06:04:11 -0500
Received: from xch-rcd-007.cisco.com ([173.37.102.17]) by XCH-RCD-007.cisco.com ([173.37.102.17]) with mapi id 15.00.1473.003; Fri, 29 Mar 2019 06:04:11 -0500
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: ivaylo petrov <ivaylo@ackl.io>, "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] I-D Action: draft-ietf-core-sid-06.txt
Thread-Index: AQHU5bJfckruPp1PlkWr7DQgfIKwn6Yh7c6AgAB/fEA=
Date: Fri, 29 Mar 2019 11:04:11 +0000
Message-ID: <a38236292e544680ac61d3708bf5c1e7@XCH-RCD-007.cisco.com>
References: <155381071244.1414.15110813535407686735@ietfa.amsl.com> <CAJFkdRyk1LwcbNAZBXcZj22aEXQYb4W6S5VVijuWp0K-_anCGQ@mail.gmail.com>
In-Reply-To: <CAJFkdRyk1LwcbNAZBXcZj22aEXQYb4W6S5VVijuWp0K-_anCGQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.63.23.177]
Content-Type: multipart/mixed; boundary="_004_a38236292e544680ac61d3708bf5c1e7XCHRCD007ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.16, xch-rcd-006.cisco.com
X-Outbound-Node: rcdn-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/BDKzxF3Z3FEfpbi6HbbscFlwZZ0>
Subject: Re: [core] I-D Action: draft-ietf-core-sid-06.txt
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, 29 Mar 2019 11:04:23 -0000

Hi Ivaylo,

I have made comments on the -05 version, and the same comments on previous versions, that have been discussed with Carsten twice, but these comments have not gone any further without any explanation why.  Perhaps they have just been missed?

Please can you check back on those threads and either incorporate the appropriate changes into the draft, or explain why you don’t want to make them.

Kind regards,
Rob


From: core <core-bounces@ietf.org> On Behalf Of ivaylo petrov
Sent: 28 March 2019 22:08
To: core@ietf.org
Cc: i-d-announce@ietf.org
Subject: Re: [core] I-D Action: draft-ietf-core-sid-06.txt

Dear all,

The new version of the sid draft is uploaded to the datatracker. It is the result of a number of discussions with IANA representatives. Please review it and don't hesitate to contact us if you have any questions or comments.

Best regards,
Ivaylo


On Thu, Mar 28, 2019 at 11:05 PM <internet-drafts@ietf.org<mailto:internet-drafts@ietf..org>> wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Constrained RESTful Environments WG of the IETF.

        Title           : YANG Schema Item iDentifier (SID)
        Authors         : Michel Veillette
                          Alexander Pelov
                          Ivaylo Petrov
        Filename        : draft-ietf-core-sid-06.txt
        Pages           : 29
        Date            : 2019-03-28

Abstract:
   YANG Schema Item iDentifiers (SID) are globally unique 64-bit
   unsigned numbers used to identify YANG items.  This document defines
   the semantics, the registration, and assignment processes of SIDs.
   To enable the implementation of these processes, this document also
   defines a file format used to persist and publish assigned SIDs.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-core-sid/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-core-sid-06
https://datatracker.ietf.org/doc/html/draft-ietf-core-sid-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-core-sid-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
core mailing list
core@ietf.org<mailto:core@ietf.org>
https://www.ietf.org/mailman/listinfo/core
--- Begin Message ---
On Mar 15, 2019, at 14:24, Rob Wilton (rwilton) <rwilton@cisco.com> wrote:
>
> In short, I think that it would be more pragmatic if SIDs are restricted to the non-negative range of the signed 64 bit integer type.  I.e. disallow values from (2^63 through 2^64 - 1).

SIDs are unsigned integers.  However, there are still languages that have a hard time with those.  And it helps if all SID deltas fit into a signed 64-bit integer.
So maybe limiting SIDs to the (non-negative) range of signed 64-bit integers is a restriction that makes sense.

https://github.com/core-wg/yang-cbor has three pull requests, but no issues.
(This apparently also happens to be the repo for the SID specification.)

Should we put up the issues there?

Grüße, Carsten

--- End Message ---