Re: [core] draft-ietf-core-link-format-11 - discover virtual hosted resources

Klaus Hartke <hartke@tzi.org> Sat, 21 April 2012 03:25 UTC

Return-Path: <hartke@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E28F21F84FB for <core@ietfa.amsl.com>; Fri, 20 Apr 2012 20:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.627
X-Spam-Level:
X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
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 1xShf18oe3Wa for <core@ietfa.amsl.com>; Fri, 20 Apr 2012 20:25:34 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 490DF21F84B8 for <core@ietf.org>; Fri, 20 Apr 2012 20:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q3L3PP84026575 for <core@ietf.org>; Sat, 21 Apr 2012 05:25:25 +0200 (CEST)
Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 08FFD287 for <core@ietf.org>; Sat, 21 Apr 2012 05:25:24 +0200 (CEST)
Received: by dady13 with SMTP id y13so18427202dad.27 for <core@ietf.org>; Fri, 20 Apr 2012 20:25:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.195.163 with SMTP id if3mr9516678pbc.127.1334978723002; Fri, 20 Apr 2012 20:25:23 -0700 (PDT)
Received: by 10.68.23.37 with HTTP; Fri, 20 Apr 2012 20:25:22 -0700 (PDT)
In-Reply-To: <F5CA9E96-C66D-459C-9ABF-B230D34FE877@sensinode.com>
References: <6029ED8C-2341-4199-A439-F0DB02A55DA4@koanlogic.com> <F5CA9E96-C66D-459C-9ABF-B230D34FE877@sensinode.com>
Date: Sat, 21 Apr 2012 05:25:22 +0200
Message-ID: <CAB6izETH8czdmvv_Jii+UMorQQ--=ZwypHKKH_XEnBsEBwpAJQ@mail.gmail.com>
From: Klaus Hartke <hartke@tzi.org>
To: core@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [core] draft-ietf-core-link-format-11 - discover virtual hosted resources
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Apr 2012 03:25:35 -0000

Hi Zach,

On 15 April 2012 19:47, Zach Shelby <zach@sensinode.com> wrote:
> What this means in practice is that the target for this relation has to be on the same origin server. The result is that if the target is an absolute URI, then the host part should be interpreted as a virtual host name (and thus should be included in the Uri-Host option). [...] There is no reason your virtual host name couldn't be really short though and thus just as efficient as using the Uri-Host field.

Do you mean a server like "sensor1.example.com" could advertise a
virtual host "xy" rather than "temp.sensor1.example.com" in its
well-known core?

What happens when two different servers both advertise a virtual host
"xy"? Can a client with a cache use a stored response that is the
result of retrieving resource "/res" of virtual host "xy" at
[2001:DB8::abcd] to satisfy a request for resource "/res" of virtual
host "xy" at [2001:DB8::9999]? The request URI is <coap://xy/res> in
both cases.


Klaus