Re: [Last-Call] Last Call: <draft-ietf-cdni-uri-signing-20.txt> (URI Signing for Content Delivery Network Interconnection (CDNI)) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have trouble getting through this quite dense document. However, this text:

~~~
   The URI Signing Package will be found by searching the URI Query string [RFC3986] (see [RFC3986] Section 3.4), left-to-right, for the following sequence:
   o  the URI Signing Package Attribute name,
   o  an equal symbol ('='),
   o  and a sequence of zero or more non-reserved characters (as defined in [RFC3986] Section 2.3) that will be interpreted as a signed JWT,
   o  terminated by either any reserved character (as defined in [RFC3986] Section 2.2) or the end of the URI Query string.
~~~

leads me to believe that it doesn't line up with BCP190. 

Cheers,


> On 6 Feb 2021, at 10:12 am, The IESG <iesg-secretary@xxxxxxxx> wrote:
> 
> 
> The IESG has received a request from the Content Delivery Networks
> Interconnection WG (cdni) to consider the following document: - 'URI Signing
> for Content Delivery Network Interconnection (CDNI)'
>  <draft-ietf-cdni-uri-signing-20.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@xxxxxxxx mailing lists by 2021-02-19. Exceptionally, comments may
> be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>   This document describes how the concept of URI Signing supports the
>   content access control requirements of Content Delivery Network
>   Interconnection (CDNI) and proposes a URI Signing method as a JSON
>   Web Token (JWT) profile.
> 
>   The proposed URI Signing method specifies the information needed to
>   be included in the URI to transmit the signed JWT, as well as the
>   claims needed by the signed JWT to authorize a User Agent (UA).  The
>   mechanism described can be used both in CDNI and single Content
>   Delivery Network (CDN) scenarios.
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-cdni-uri-signing/
> 
> 
> The following IPR Declarations may be related to this I-D:
> 
>   https://datatracker.ietf.org/ipr/2603/
>   https://datatracker.ietf.org/ipr/4628/
> 
> 
> 
> 
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@xxxxxxxx
> https://www.ietf.org/mailman/listinfo/ietf-announce

--
Mark Nottingham   https://www.mnot.net/

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux