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

"Vijay K. Gurbani" <vkg@bell-labs.com> Fri, 15 February 2013 14:49 UTC

Return-Path: <vkg@bell-labs.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 8830A21F8AE6 for <alto@ietfa.amsl.com>; Fri, 15 Feb 2013 06:49:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 BULnwJQlo3kO for <alto@ietfa.amsl.com>; Fri, 15 Feb 2013 06:49:42 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id E8C0321F8AB4 for <alto@ietf.org>; Fri, 15 Feb 2013 06:49:41 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r1FEnfnh005686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Fri, 15 Feb 2013 08:49:41 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1FEnehx004701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Fri, 15 Feb 2013 08:49:40 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1FEneO4005177 for <alto@ietf.org>; Fri, 15 Feb 2013 08:49:40 -0600 (CST)
Message-ID: <511E4B94.2050804@bell-labs.com>
Date: Fri, 15 Feb 2013 08:52:04 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: alto@ietf.org
References: <CD410929.32200%w.roome@alcatel-lucent.com> <32175B8B-3F60-4DB9-AEC6-6C6D9EFE8F9C@niven-jenkins.co.uk> <CA+cvDaZJvCwWzDZQx45-MCzpjMaczkbzR84dQM32-Eno8x5M-w@mail.gmail.com>
In-Reply-To: <CA+cvDaZJvCwWzDZQx45-MCzpjMaczkbzR84dQM32-Eno8x5M-w@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
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 14:49:44 -0000

[As individual contributor]

On 02/15/2013 12:06 AM, Richard Alimi wrote:
> +1 for allowing relative URIs.  If there are no dissenting opinions,
> we'll update the draft with Ben's proposed text.

Richard: That is fine.  Originally I was going to state that we adopt
absolute URIs, but I must admit that this was driven by expediency
of us adopting *a* position instead of greeting the issue with silence
on the list.

Wendy has outlined the pros and cons of absolute versus relative URIs,
and yes it is a bit of pain to handle relative URIs,  But as long as we
have a position well spelled out in the document, adhering to it is a
matter of minor implementation complexity.  Let's go for what you
suggest above.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/