Re: [6tisch] Adam Roach's Discuss on draft-ietf-6tisch-minimal-security-13: (with DISCUSS and COMMENT)

[Michael Richardson <[e-mail]>]

Adam Roach via Datatracker <[e-mail]> wrote:
    > §8.1.1:

    >> o The Uri-Path option is set to "j".

    > COAP URIs are generally subject to BCP 190 restrictions, which would
    > require the path to either be provisioned, discovered, or under the
    > ".well-known" tree. The use of a reserved domain name here may change
    > the rationale; but for the sake of not establishing a precedent for

Yes, we think that it does.
The Host: is "6tisch.arpa", so we think that we are the owner of the URI, as
per BCP190 section 1, paragraph 3:

   }  Because the owner of the URI (as defined in [webarch]
   }  Section 2.2.2.1) is choosing to use the server or the application,
   }  this can be seen as reasonable delegation of authority.

How/where should we reference this?

    > path squatting in CoAP, this document needs to clearly explain the
    > rationale of why BCP 190 should not apply in this case. Alternately,
    > the implied URI can be changed to something like
    > "coap://6tisch.arpa/.well-known/j"

We feel that those 11 bytes are not needed. We already didn't like the
6tisch.arpa part....

    > ----------------------------------------------------------------------
    > COMMENT:
    > ----------------------------------------------------------------------

    >> This document allocates a well-known name under the .arpa name space
    >> according to the rules given in [RFC3172].  The name "6tisch.arpa" is
    >> requested.  No subdomains are expected.  No A, AAAA or PTR record is
    >> requested.

    > Although "No subdomains are expected" is useful text, I don't think
    > it's sufficient to satisfy RFC 3172's requirements of specifying "the
    > rules for how the subdomain is administered." I would suggest something
    > like:

    > "No subdomains are expected, and addition of any such subdomains
    > requires the publication of an IETF standards-track RFC."

I used your text.

--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-