IETF Logo Mail Archive

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

"Francois Le Faucheur (flefauch)" <flefauch@cisco.com> Fri, 08 November 2013 18:50 UTC

Return-Path: <flefauch@cisco.com>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D788411E8110 for <cdni@ietfa.amsl.com>; Fri, 8 Nov 2013 10:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bUZaxkri5Pj5 for <cdni@ietfa.amsl.com>; Fri, 8 Nov 2013 10:50:44 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id D8B7F21F9FDA for <cdni@ietf.org>; Fri, 8 Nov 2013 10:50:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5136; q=dns/txt; s=iport; t=1383936642; x=1385146242; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=KjVTqpS6i1iG6zV02rTOf7r/jVZLhVAul1K5woXp6EA=; b=dXmVWDpb7QJxiQjR63E4MiObW4FT+wol/j/HZyagGUFJrrNTGTYQ08HB r+2cx1mxwpekv3T5zsMXv/fvn68sC2dt145Q+IyRPkxkgS5W3FQWrXLd0 jDq4Jy0iOqlFaLpBwE1VRkJvoBJY9kOaX/06Z7XS20n9y2810FeFKVOik E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAO8xfVKtJXG8/2dsb2JhbABZgkNEOFO/FoEwFnSCJgEBBAEBAWsLEAIBCD8HJwsUEQEBBAENBRuHZg29KASPYwQHgyCBEAOYD5ILgyaBaiQc
X-IronPort-AV: E=Sophos; i="4.93,661,1378857600"; d="scan'208,217"; a="282561329"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-5.cisco.com with ESMTP; 08 Nov 2013 18:50:41 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id rA8Iofjc017811 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 8 Nov 2013 18:50:41 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.47]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Fri, 8 Nov 2013 12:50:41 -0600
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>, Mark Nottingham <mnot@mnot.net>
Thread-Topic: [CDNi] URI structure issue with draft-leung-cdni-uri-signing-03
Thread-Index: Ac7cVxkp2B429Y2iTw+ZtXmQWSPwwwAjp16A
Date: Fri, 08 Nov 2013 18:50:40 +0000
Message-ID: <E91F0E52-E262-4731-89D0-F63F18776E5D@cisco.com>
References: <CD85F32117029D4F9AEF48BDEF5536AB1DB8A6D1@xmb-aln-x03.cisco.com>
In-Reply-To: <CD85F32117029D4F9AEF48BDEF5536AB1DB8A6D1@xmb-aln-x03.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.70.59]
Content-Type: multipart/alternative; boundary="_000_E91F0E52E262473189D0F63F18776E5Dciscocom_"
MIME-Version: 1.0
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] URI structure issue with draft-leung-cdni-uri-signing-03
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cdni>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2013 18:50:59 -0000

Putting Mark explicitely in the loop.
Francois

On 7 Nov 2013, at 23:49, Kent Leung (kleung) <kleung@cisco.com<mailto:kleung@cisco.com>> wrote:

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 mailing list
CDNi@ietf.org<mailto:CDNi@ietf.org>
https://www.ietf.org/mailman/listinfo/cdni

v2.23.0 | Report a Bug | By Email