Re: [Ecrit] Adding top-level service labels

Ted Hardie <ted.ietf@gmail.com> Tue, 14 February 2012 23:28 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 419D821E80E3 for <ecrit@ietfa.amsl.com>; Tue, 14 Feb 2012 15:28:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.689
X-Spam-Level:
X-Spam-Status: No, score=-3.689 tagged_above=-999 required=5 tests=[AWL=-0.090, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 9bl-ukQ1EhZf for <ecrit@ietfa.amsl.com>; Tue, 14 Feb 2012 15:28:56 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 490EC21E807F for <ecrit@ietf.org>; Tue, 14 Feb 2012 15:28:56 -0800 (PST)
Received: by vbbfr13 with SMTP id fr13so430213vbb.31 for <ecrit@ietf.org>; Tue, 14 Feb 2012 15:28:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=gKU/Ws9cY+x0xsrcK94SLnP0xz208CSghkJzUqJcgXQ=; b=EbdH9kHMjDupBfspFJ4Bif4A+KaeKh1vXaAlyuITPX6s0yQ1VNrVSlavYd2FNzP8IC 9/6dBLKA1puufwUikkCoCJfh2p2Nni0SV5SqdnQNxQbZAscU5nNGt5jgloX4MGZZEC/+ szZymIe+HAXgEx6MVux2ggMIFfMQpDfdIwJB8=
MIME-Version: 1.0
Received: by 10.52.91.196 with SMTP id cg4mr10039009vdb.68.1329262135854; Tue, 14 Feb 2012 15:28:55 -0800 (PST)
Received: by 10.52.31.68 with HTTP; Tue, 14 Feb 2012 15:28:55 -0800 (PST)
In-Reply-To: <CABkgnnU-Log1UjDqxCDJdw40w=hpQf+WODs2_rWPDsFuUnO0vw@mail.gmail.com>
References: <CB1513CE.9A50%forte@att.com> <8740CFE2-7987-4313-B6D4-989779B5D05C@bbn.com> <CABkgnnU-Log1UjDqxCDJdw40w=hpQf+WODs2_rWPDsFuUnO0vw@mail.gmail.com>
Date: Tue, 14 Feb 2012 15:28:55 -0800
Message-ID: <CA+9kkMDnrFjZZwddGYDY6a2nVteQFGzLbLWakP2JD6xaPdBLmg@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "ecrit@ietf.org Org" <ecrit@ietf.org>
Subject: Re: [Ecrit] Adding top-level service labels
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2012 23:28:57 -0000

On Tue, Feb 14, 2012 at 3:19 PM, Martin Thomson
<martin.thomson@gmail.com> wrote:
> I have no problem with opening registration.
>
> In the interests of democratization of the space, is there anything
> prohibiting someone from using an http: URI to identify a service?
> The only reason that you want some portion of the urn:service: space
> is for interoperability.  The only other stricture is global
> uniqueness.

RFC 6451 says it is compatible with RFC 5222, which specifies service
URNs; I think if it were to relax from a managed namespace to any URI
(or even HTTP URIs), then I think you'd need to update at least 6451,
and maybe 5222.

If you don't want interoperablity, you could use a UUID, with a
mapping known only to the application.  But I suspect the value is in
some intersection of interoperablity, human readability, and
uniqueness.

regards,

Ted


>
> --Martin
>
> On 14 February 2012 14:57, Richard Barnes <rbarnes@bbn.com> wrote:
>> Dear WG,
>>
>> There has been little response to this proposal from Andrea.  In discussions with the ADs, the chairs have concluded that if this document progresses, it will have to be through the working group.  So we would like to issue a consensus call for whether the WG should take this document on as a WG item.
>>
>> Please send comments to the list no later than 21 Feb 2012.
>>
>> Thanks,
>> Richard and Marc
>>
>>
>> On Dec 19, 2011, at 4:16 PM, Andrea G. Forte wrote:
>>
>>> Dear all,
>>>
>>> Recently, the LoST Extensions draft has been ratified as RFC 6451. This
>>> means that people can start using LoST for non-emergency services.
>>> Furthermore, Telecom Italia (the first Italian mobile carrier) has
>>> contacted us for knowing the status of the service classification draft as
>>> they were interested in working in that area.
>>>
>>> We think that times have matured enough to resume our discussion on
>>> non-emergency location-based services. However, given that this is the
>>> ECRIT working group, I wanted to bring to the group's attention the draft
>>> on service URN update policy
>>> [http://tools.ietf.org/html/draft-forte-ecrit-service-urn-policy-00].
>>>
>>> As a reminder, this draft would update "Section 4.1 of [RFC5031] in that
>>> the policy for adding top-level service labels is "Expert Review".  The
>>> expert is designated by the RAI Area Director". Today standard action is
>>> required for this, which is a significant overkill to just add "food" or
>>> "lodging". I do not see any harm in introducing this change in policy but
>>> I would like to know the opinion of the WG.
>>>
>>> Thanks,
>>> -- Andrea G. Forte
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Ecrit mailing list
>>> Ecrit@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ecrit
>>
>> _______________________________________________
>> Ecrit mailing list
>> Ecrit@ietf.org
>> https://www.ietf.org/mailman/listinfo/ecrit
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit