Re: [alto] Should we allow relative URIs in resource directories?

Richard Alimi <rich@velvetsea.net> Fri, 15 February 2013 06:07 UTC

Return-Path: <richard.alimi@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BB3921F8A49 for <alto@ietfa.amsl.com>; Thu, 14 Feb 2013 22:07:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNX76DX2yRUy for <alto@ietfa.amsl.com>; Thu, 14 Feb 2013 22:07:09 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 6125E21F8717 for <alto@ietf.org>; Thu, 14 Feb 2013 22:07:09 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id o1so712407wic.11 for <alto@ietf.org>; Thu, 14 Feb 2013 22:07:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=yHeFbYUC7jfgC4ojSRUZ1+ZwMqmAa9kdeg8byQShEP4=; b=NWmaU1mVQRO4A7hEPY8XgWJTwVeFQMz8S0tH+nTlRDdsj04cFaAbNiDey8SzzG2YOi 89Mp0kNx9vZy+B9SwPKLJ83Ti2Kqa+yjRg7cPbwB23Osqa/ISTBO7i4Ee9eqs+R98CaV wkpRl0hxqrAzDObSKuKWZS0bbJDcDwMbDaDHZn7Zce6ae5XYz1F/hHq6gwEPAK2VgejV ZhU4CkvoMjLRiJP7S4RQY4xYZ+Snw6ODiwXu2ib/65wZNzHWMC45kg1DzEsQL1GqV1nV 7yAha5VD5C78FAfIPpFeOMN3PPopcUMzk2uh88kXex6638ptpS8TnTEzWhk63QvyiHYq x8bQ==
X-Received: by 10.180.85.97 with SMTP id g1mr3729703wiz.29.1360908428463; Thu, 14 Feb 2013 22:07:08 -0800 (PST)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.58.209.169 with HTTP; Thu, 14 Feb 2013 22:06:48 -0800 (PST)
In-Reply-To: <32175B8B-3F60-4DB9-AEC6-6C6D9EFE8F9C@niven-jenkins.co.uk>
References: <CD410929.32200%w.roome@alcatel-lucent.com> <32175B8B-3F60-4DB9-AEC6-6C6D9EFE8F9C@niven-jenkins.co.uk>
From: Richard Alimi <rich@velvetsea.net>
Date: Thu, 14 Feb 2013 22:06:48 -0800
X-Google-Sender-Auth: t8QZrnAOxlaeuewJzLQobQl7r2w
Message-ID: <CA+cvDaZJvCwWzDZQx45-MCzpjMaczkbzR84dQM32-Eno8x5M-w@mail.gmail.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: multipart/alternative; boundary="f46d0444036c734e9704d5bd2f57"
Cc: Wendy Roome <w.roome@alcatel-lucent.com>, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Should we allow relative URIs in resource directories?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 06:07:10 -0000

On Wed, Feb 13, 2013 at 10:56 PM, Ben Niven-Jenkins <ben@niven-jenkins.co.uk
> wrote:

> Wendy,
>
> On 13 Feb 2013, at 14:38, Wendy Roome wrote:
>
> > RFC 3986 does define relative URIs, so technically that's sufficient. But
> > I think that's like a lawyer burying some critical information -- like
> > "double every amount that you owe us" -- in tiny type in a footnote.
> > Legal, but sleazy.
> >
> > The problem is that software libraries with a simple connectToServer(uri)
> > function require an absolute uri. If the uri might be relative, the
> client
> > must first resolve the uri in the context of some absolute base uri. Most
> > libraries provide a function to do that, but it's easy to forget that
> step.
> >
> > Case in point: My client, which passed all the interop tests, failed when
> > it contacted a server that returned relative URIs. (And yes, I've since
> > fixed my client.)
> >
> > So if we want to allow relative URIs, we should be more explicit. At the
> > very least, add this sentence to the end of Ben's revised uri section:
> >
> >    Relative URIs should be resolved using the URI of the Information
> > Resource Directory as the base URI.
>
> Or a reference to section 5 of RFC 3986 rather than re-specifying its
> semantics.
>
> Maybe something like:
>    URIs can be relative and MUST be resolved according to section 5 of
>    [RFC3986].
>

+1 for allowing relative URIs.  If there are no dissenting opinions, we'll
update the draft with Ben's proposed text.


>
> Ben
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>