Subject: Re: [core] New Version Notification for draft-ietf-core-href-07.txt

From: Carsten Bormann <[email-masked]>
Date: Thu, 28 Oct 2021 02:23:28 +0200

Revision -07 has additional discussion on the constraints that CRIs bring with them compared to text-based URIs (and, conversely, things you can do in CRIs you cannot do in URIs).

The ABNF also is more explicit in naming various constants.

I’m afraid we got one of these wrong:

no-authority = NOAUTH-NOSLASH / NOAUTH-LEADINGSLASH	
 	   NOAUTH-NOSLASH = null	
 	   NOAUTH-LEADINGSLASH = true

NOAUTH-NOSLASH is not further discussed in the text, but null actually is the value for having a leading slash in the path, while true is the value for removing that (as in URNs, W3C DID URIs, etc.).

Grüße, Carsten

> On 25. Oct 2021, at 23:54, [email-masked] wrote:
> 
> 
> A new version of I-D, draft-ietf-core-href-07.txt
> has been successfully submitted by Carsten Bormann and posted to the
> IETF repository.
> 
> Name:		draft-ietf-core-href
> Revision:	07
> Title:		Constrained Resource Identifiers
> Document date:	2021-10-25
> Group:		core
> Pages:		21
> URL:            https://www.ietf.org/archive/id/draft-ietf-core-href-07.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-core-href/
> Html:           https://www.ietf.org/archive/id/draft-ietf-core-href-07.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-core-href
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-core-href-07
> 
> Abstract:
>   The Constrained Resource Identifier (CRI) is a complement to the
>   Uniform Resource Identifier (URI) that serializes the URI components
>   in Concise Binary Object Representation (CBOR) instead of a sequence
>   of characters.  This simplifies parsing, comparison and reference
>   resolution in environments with severe limitations on processing
>   power, code size, and memory size.
> 
> 
> 
> 
> The IETF Secretariat
> 
>