[CDNi] URI structure issue with draft-leung-cdni-uri-signing-03

"Kent Leung (kleung)" <kleung@cisco.com> Fri, 08 November 2013 07:50 UTC

From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: URI structure issue with draft-leung-cdni-uri-signing-03
Thread-Index: Ac7cVxkp2B429Y2iTw+ZtXmQWSPwww==
Date: Fri, 08 Nov 2013 07:49:52 +0000
Message-ID: <CD85F32117029D4F9AEF48BDEF5536AB1DB8A6D1@xmb-aln-x03.cisco.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_CD85F32117029D4F9AEF48BDEF5536AB1DB8A6D1xmbalnx03ciscoc_"
MIME-Version: 1.0
Subject: [CDNi] URI structure issue with draft-leung-cdni-uri-signing-03
Precedence: list

Just an update on this topic.

A few of us met with Mark Nottingham today to discuss the issue that he brought up in draft-nottingham-uri-get-off-my-lawn. In summary, Mark does not want "baked in" query string attributes or any portion in the URI. So, the proposed solution presented in the WG session should address that concern. Basically, CDNI metadata conveys how the query string is encoded to include the URI Signing information elements (URI signature, algorithm used, etc.) This information is used by the Downstream CDN to validate the Signed URI.

The next step is to revise the draft so the URI Signing method uses this approach. It should also incorporate the comments from Kevin. When that's ready, Mark agreed to review the draft and stamp it as "off his lawn" if the solution no longer is standardizing a structure in the URI. :)

Kent

[CDNi] URI structure issue with draft-leung-cdni-… Kent Leung (kleung)
Re: [CDNi] URI structure issue with draft-leung-c… Francois Le Faucheur (flefauch)