Re: [regext] FW: I-D Action: draft-hollenbeck-regext-rfc7483bis-00.txt

Jasdip Singh <jasdips@arin.net> Wed, 06 May 2020 16:41 UTC

Return-Path: <jasdips@arin.net>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 717663A0593 for <regext@ietfa.amsl.com>; Wed, 6 May 2020 09:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 FqLBHz7EraqM for <regext@ietfa.amsl.com>; Wed, 6 May 2020 09:41:35 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [192.136.136.51]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 538373A0415 for <regext@ietf.org>; Wed, 6 May 2020 09:41:35 -0700 (PDT)
Received: from CAS01CHA.corp.arin.net (cas01cha.corp.arin.net [10.1.30.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTPS id 6F78F10757B2; Wed, 6 May 2020 12:41:33 -0400 (EDT)
Received: from CAS02CHA.corp.arin.net (10.1.30.63) by CAS01CHA.corp.arin.net (10.1.30.62) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 6 May 2020 12:41:32 -0400
Received: from CAS02CHA.corp.arin.net ([fe80::ccb9:9ec8:d7a9:aab7]) by CAS02CHA.corp.arin.net ([fe80::19e5:ca2:bbfd:3b4e%17]) with mapi id 15.00.1104.000; Wed, 6 May 2020 12:41:32 -0400
From: Jasdip Singh <jasdips@arin.net>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
CC: "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [regext] FW: I-D Action: draft-hollenbeck-regext-rfc7483bis-00.txt
Thread-Index: AQHV5lXh3r+CzPLbDEewAYYhuTktcKgg4LOQgACXVYCAeoB1AIAACEgA
Date: Wed, 6 May 2020 16:41:32 +0000
Message-ID: <DDE086DB-CC41-4BA7-8E46-E47FA240C841@arin.net>
References: <158202847369.14106.8963334452011519309@ietfa.amsl.com> <bb1c73111e9f48ff83f8b1e454faf954@verisign.com> <2ABBB82E-DD9A-430B-8BD4-58122F8A2E53@arin.net> <665437daca2c4553a3360240b3a5b24e@verisign.com>
In-Reply-To: <665437daca2c4553a3360240b3a5b24e@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.1.26.115]
Content-Type: multipart/alternative; boundary="_000_DDE086DBCC414BA78E46E47FA240C841arinnet_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Ds7-l0XStBV--9vu8PPdkzaVfJ0>
Subject: Re: [regext] FW: I-D Action: draft-hollenbeck-regext-rfc7483bis-00.txt
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 May 2020 16:41:40 -0000

I agree with your comments, Scott. Thanks.

Jasdip

On May 6, 2020, at 12:11 PM, Hollenbeck, Scott <shollenbeck@verisign.com<mailto:shollenbeck@verisign.com>> wrote:

Thanks for the feedback, Jasdip. More below…

From: Jasdip Singh <jasdips@arin.net<mailto:jasdips@arin.net>>
Sent: Tuesday, February 18, 2020 11:28 AM
To: Hollenbeck, Scott <shollenbeck@verisign.com<mailto:shollenbeck@verisign.com>>
Cc: regext@ietf.org<mailto:regext@ietf.org>
Subject: [EXTERNAL] Re: [regext] FW: I-D Action: draft-hollenbeck-regext-rfc7483bis-00.txt

Hello Scott,

Here is my (mostly minor) feedback:


  1.  4.8 For consistency with other examples, add spaces before and after ‘:’ in the publicIds example.
  2.  5.1 Similarly, add spaces before and after ‘:' in the entity example. (There could be other places in the whole doc.)

[SAH] I’m not so sure. I haven’t found a normative style guide that describes spacing conventions, and I see inconsistent use of spaces in our own standard for JSON data interchange (see Section 13 of RFC 7159). I think I’d like to leave these alone.

You are right. :)


  1.  5.3 Should maxSigLife have a more normative reference (RFC 4034) than RFC 5910?

[SAH] maxSigLife doesn’t appear in RFC 4034, so I think 5910 is the appropriate reference.

No, you are right.


  1.  5.3 Figure 24: Handle in the entity object is XXXX but it is xxxx in links’ URIs.
  2.  5.4 Figure 26: Handle in the entity object is XXXX but it is xxxx in links’ URIs. Lastly, RFC 5952 recommends lowercase v6 notation (section 4.3); may lowercase (C00) in http://example.net/ip/2001:C00::/23 and likes.

[SAH] Will fix.

  1.  5.4 Should startAddress be clarified as "a string representing the starting…”? Similarly, for endAddress description.

[SAH] Will fix.

  1.  5.5 Should the "Autonomous System Number Entity Object Class” title be “The Autonomous System Number Object Class”?

[SAH] Will fix.

  1.  5.5 So as to hold 4-byte ASNs (0 to 4294967295), should we clarify the JSON number as uint32 (unsigned) (as per https://developers.google.com/discovery/v1/type-format)?

[SAH] will fix.

  1.  5.5 Should name be clarified as "a string representing an identifier…”?

[SAH] Will fix.
Thanks,
Jasdip