Re: [Uri-review] Request for review of new ipn: URI scheme

[Mykyta Yevstifeyev <[e-mail]>]

Hello Elwyn,

Here are some comments to the 'ipn' URI scheme registration template - 
see in-line.

> 4. IANA Considerations
>
>    Registration of the "ipn" URI scheme is requested as follows.
Here the Informative reference to RFC 4395 might be acceptable.
>
>    URI scheme name: "ipn".
>
>    Status: provisional.
I wonder why it is Provisional.  Provisional means 'not complete and 
acceptable specification' while this is not such case.  I suggest Permanent.
>
>    URI scheme syntax:
>
>    This specification uses the Augmented Backus-Naur Form (ABNF)
>    notation of [RFC2234], including the core ABNF syntax rule for DIGIT
>    defined by that specification.
Why RFC 2234 - it is obsoleted by RFC 4234 and RFC 5234 - the most 
current doc.  Moreover, I am not able to find any reference in the 
corresponding section of the draft to any of the documents.  If you 
accept RFC 5234, the rule definition must be rule=def but not rule:=def.
>
>    o  ipn-uri := "ipn:" ipn-hier-part
>
>    o  ipn-hier-part := node-nbr nbr-delim service-nbr ; a path-rootless
This rule is not acceptable at all.  I do not know what you mean, but 
'node-nbr nbr-delim service-nbr' is already path-rootless; moreover what 
are 'a' and ';' rules, that are not defined at all.  You might have 
meant "a" and ";" but I am not sure for this and other concerns I've 
told about above.  I'd like you clarify this syntax.
>
>    o  node-nbr := 1*DIGIT
>
>    o  nbr-delim := "."
>
>    o  service-nbr := 1*DIGIT
>
>    None of the reserved characters defined in the generic URI syntax are
>    used as delimiters within URIs of the IPN scheme.
>
>    URI scheme semantics: URIs of the IPN scheme are used as endpoint
>    identifiers in the Delay-Tolerant Networking (DTN) Bundle Protocol
>    (BP) [RFC5050] as described in 2.1 above.
>
>    Encoding considerations: URIs of the IPN scheme are encoded
>    exclusively in US-ASCII characters.
Here I'd propose the better variant: "generic encoding considerations 
for URI schemes, defined in Section 2 of [RFC3986], concern 'ipn' one as 
well.  Non-ASCII characters are to be mapped as defined in Section 3.1 
of RFC 3987 [RFC3987]" with the Normative reference of RFC 3987.

>
>    Applications and/or protocols that use this URI scheme name: the
>    Delay-Tolerant Networking (DTN) Bundle Protocol (BP) [RFC5050].
>
>    Interoperability considerations: as noted above, URIs of the IPN
>    scheme are encoded exclusively in US-ASCII characters.
This is not Interoperability considerations - you'd better omit this 
point in the template at all.
>
> [...]
>
>    Contact: Scott Burleigh, Jet Propulsion Laboratory, California
>    Institute of Technology, [e-mail], +1 (800) 393-
>    3353.
>
>    Author/Change controller.  Scott Burleigh, Jet Propulsion Laboratory,
>    California Institute of Technology, [e-mail], +1
>    [phone].
I'd like you, as the doc. shepherd, bring these comments to the authors' 
attention.

Mykyta Yevstifeyev

16.02.2011 20:41, Elwyn Davies wrote:
> Hi.
>
> The DTN Research Group has a draft being examined by the IESG for
> approval as an Experimental RFCthat contains the specification of the
> ipn: URI scheme:
> http://tools.ietf.org/html/draft-irtf-dtnrg-cbhe-08
>
> We would like to request review of the scheme prior to approval of the
> draft.
>
> The original motivation for the definition of this scheme is usage of
> DTNs in space-based networks where bandwidth is at a premium, but its
> usage is not confined to theis application.
>
> It has been observed by the responsible AD that the ABNF syntax in the
> draft is faulty (it uses ':=' rather than '=' throughout.. it will be
> replaced with:
>
> ipn-uri       = "ipn:" ipn-hier-part
> ipn-hier-part = node-nbr nbr-delim service-nbr ; a path-rootless
> node-nbr      = 1*DIGIT
> nbr-delim     = "."
> service-nbr   = 1*DIGIT
>
> We also need to specify the References for the scheme - the only
> relevant reference is the defining draft, which will hopefully be an
> experimental RFC shortly.
>
> Regards,
> Elwyn Davies
> Document Shepherd
>
> _______________________________________________
> Uri-review mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/uri-review
>