Re: [CDNi] I-D Action: draft-ietf-cdni-uri-signing-10.txt

Seeing as there hasn't been any negative feedback on the new direction (or
any feedback at all) I'd like to point out that we have this particular
draft in revision control in github. I've also submitted a pull request if
anyone would like to review it.

https://github.com/rayvbr/URISigningSpec/pull/5

This adds a version claim so that we can upgrade more easily and also
ignore unknown claims. We originally had a version field to begin with but
there was nothing in JWT that was similar so it was left out of the first
JWT revision. We (Matt Miller and I) also consulted with a JWT expert on
the name used and how to get it registered properly.

Thanks.

On Tue, Oct 4, 2016 at 2:34 AM Brandenburg, R. (Ray) van <
ray.vanbrandenburg@tno.nl> wrote:

> Hi all,
>
> As you can see, we’ve just uploaded a new version of the URI Signing
> document. This is a major rewrite that incorporates the decision we made in
> Berlin to base the URI Signing algorithm on JSON Web Token.
>
> There are still a few open issues, but we wanted to get the groups opinion
> on whether this is going in the right direction.
>
> Best regards,
>
> Ray
>
>
>
> On 04/10/2016, 10:31, "CDNi on behalf of internet-drafts@ietf.org" <
> cdni-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote:
>
>
>     A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>     This draft is a work item of the Content Delivery Networks
> Interconnection of the IETF.
>
>             Title           : URI Signing for CDN Interconnection (CDNI)
>             Authors         : Ray van Brandenburg
>                               Kent Leung
>                               Phil Sorber
>                               Matthew Miller
>         Filename        : draft-ietf-cdni-uri-signing-10.txt
>         Pages           : 29
>         Date            : 2016-10-04
>
>     Abstract:
>        This document describes how the concept of URI signing supports the
>        content access control requirements of CDNI and proposes a URI
>        signing method as a JSON Web Token (JWT) [RFC7519] 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 UA.  The mechanism
>        described can be used both in CDNI and single CDN scenarios.
>
>
>     The IETF datatracker status page for this draft is:
>     https://datatracker.ietf.org/doc/draft-ietf-cdni-uri-signing/
>
>     There's also a htmlized version available at:
>     https://tools.ietf.org/html/draft-ietf-cdni-uri-signing-10
>
>     A diff from the previous version is available at:
>     https://www.ietf.org/rfcdiff?url2=draft-ietf-cdni-uri-signing-10
>
>
>     Please note that it may take a couple of minutes from the time of
> submission
>     until the htmlized version and diff are available at tools.ietf.org.
>
>     Internet-Drafts are also available by anonymous FTP at:
>     ftp://ftp.ietf.org/internet-drafts/
>
>     _______________________________________________
>     CDNi mailing list
>     CDNi@ietf.org
>     https://www.ietf.org/mailman/listinfo/cdni
>
>
> This message may contain information that is not intended for you. If you
> are not the addressee or if this message was sent to you by mistake, you
> are requested to inform the sender and delete the message. TNO accepts no
> liability for the content of this e-mail, for the manner in which you use
> it and for damage of any kind resulting from the risks inherent to the
> electronic transmission of messages.
> _______________________________________________
> CDNi mailing list
> CDNi@ietf.org
> https://www.ietf.org/mailman/listinfo/cdni
>