[weirds] Richard Barnes' No Objection on draft-ietf-weirds-bootstrap-10: (with COMMENT)

["Richard Barnes" <[e-mail]>]

Richard Barnes has entered the following ballot position for
draft-ietf-weirds-bootstrap-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-weirds-bootstrap/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I'm a little unclear as to why this document is necessary.  It seems like
given the use of 30X redirects in -using-http, you could just start with
an IANA root server and redirect your way down the tree.  It may appear
that this bootstrap mechanism saves queries to the root, but you could
achieve the same effect or better using 301 redirects with appropriate
caching.

The use of JSON in this syntax is slightly disappointing.  Generally,
using JSON arrays to contain items of different types is not a great
idea.  It seems like the "services" entries should actually be objects,
with entries indicating the semantics of the inner arrays, e.g.:

OLD: [ ["1.0.0.0/8", "192.0.0.0/8"], ["https://rir1.example.com/myrdap/"]
]
NEW: { "resources": ["1.0.0.0/8", "192.0.0.0/8"], "urls":
["https://rir1.example.com/myrdap/"] }

This should not be hard to describe in the notation of Section 10.2, and
it only uses a few more bytes on the wire.