Re: [Ecrit] Adding top-level service labels
Martin Thomson <martin.thomson@gmail.com> Tue, 14 February 2012 23:19 UTC
Return-Path: <martin.thomson@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 44F4121F8723 for <ecrit@ietfa.amsl.com>; Tue, 14 Feb 2012 15:19:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.841
X-Spam-Level:
X-Spam-Status: No, score=-4.841 tagged_above=-999 required=5 tests=[AWL=-1.242, 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 Rrfslminavvo for <ecrit@ietfa.amsl.com>; Tue, 14 Feb 2012 15:19:55 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6960D21F8718 for <ecrit@ietf.org>; Tue, 14 Feb 2012 15:19:51 -0800 (PST)
Received: by bkuw12 with SMTP id w12so498308bku.31 for <ecrit@ietf.org>; Tue, 14 Feb 2012 15:19:50 -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=qczNvyAGKD7vT4WHmEWYHJOOUGfWMGFyPe9c8w8ayPE=; b=MB6zys/Qj/uKxHffuycBVQx3jAbyfegrRPJxf02a9nFhxjrLGwsHefMvgqpEtsWxTt ZvMJOPLVjk8OrjU+21tf9jNQM6ir/w/0z/O3uGHeQQePGExZqM9PwkVWdn6tmukLacMu DG7HZ+gqf5VGivAq0rcuo0ue4nf+GGU7P0OEk=
MIME-Version: 1.0
Received: by 10.204.151.77 with SMTP id b13mr10656963bkw.57.1329261590522; Tue, 14 Feb 2012 15:19:50 -0800 (PST)
Received: by 10.204.241.81 with HTTP; Tue, 14 Feb 2012 15:19:50 -0800 (PST)
In-Reply-To: <8740CFE2-7987-4313-B6D4-989779B5D05C@bbn.com>
References: <CB1513CE.9A50%forte@att.com> <8740CFE2-7987-4313-B6D4-989779B5D05C@bbn.com>
Date: Tue, 14 Feb 2012 15:19:50 -0800
Message-ID: <CABkgnnU-Log1UjDqxCDJdw40w=hpQf+WODs2_rWPDsFuUnO0vw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Richard Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset="UTF-8"
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:19:56 -0000
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. --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] Adding top-level service labels Andrea G. Forte
- Re: [Ecrit] Adding top-level service labels Richard Barnes
- Re: [Ecrit] Adding top-level service labels Martin Thomson
- Re: [Ecrit] Adding top-level service labels Richard Barnes
- Re: [Ecrit] Adding top-level service labels Ted Hardie
- Re: [Ecrit] Adding top-level service labels Brian Rosen
- Re: [Ecrit] Adding top-level service labels Ted Hardie
- Re: [Ecrit] Adding top-level service labels Martin Thomson
- Re: [Ecrit] Adding top-level service labels Ted Hardie
- Re: [Ecrit] Adding top-level service labels Andrea G. Forte
- [Ecrit] Adding top-level service labels Marc Linsner