Re: [Ecrit] Service URN IANA Policy
"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Fri, 02 October 2009 06:27 UTC
Return-Path: <Hannes.Tschofenig@gmx.net>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5ACE53A6A01 for <ecrit@core3.amsl.com>; Thu, 1 Oct 2009 23:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.027
X-Spam-Level:
X-Spam-Status: No, score=-2.027 tagged_above=-999 required=5 tests=[AWL=0.572, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZeEM2CvfRPQN for <ecrit@core3.amsl.com>; Thu, 1 Oct 2009 23:27:27 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 7D63F3A6993 for <ecrit@ietf.org>; Thu, 1 Oct 2009 23:27:26 -0700 (PDT)
Received: (qmail invoked by alias); 02 Oct 2009 06:28:51 -0000
Received: from unknown (EHLO 4FIL42860) [192.100.123.77] by mail.gmx.net (mp025) with SMTP; 02 Oct 2009 08:28:51 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18XjdszHlAXHWCqelRuWrOfRTPh7Gg1dEGDsD5EpF DqCt4l+4fETBqr
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
To: "'James M. Polk'" <jmpolk@cisco.com>, "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>, ecrit@ietf.org
References: <3D3C75174CB95F42AD6BCC56E5555B4501BE7D30@FIESEXC015.nsn-intra.net> <XFE-SJC-211HkidcDjo00003009@xfe-sjc-211.amer.cisco.com>
Date: Fri, 02 Oct 2009 09:31:52 +0300
Message-ID: <033a01ca432a$085bc5c0$8501fe0a@nsnintra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcpC4dFM7XNEBgtKThqN8RhojwAW9AARxMRw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <XFE-SJC-211HkidcDjo00003009@xfe-sjc-211.amer.cisco.com>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.55
Subject: Re: [Ecrit] Service URN IANA Policy
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 02 Oct 2009 06:27:28 -0000
Hi James, >Chairs > >With respect to >http://www.ietf.org/internet-drafts/draft-polk-ecrit-lost-geoco >ding-00.txt >and forte's draft, I assume they keep -ecrit- in their >filename, and are individually submitted to the RFC-Editor >when the author feels they are ready? Andrea has worked on a few documents, namely: http://tools.ietf.org/html/draft-forte-ecrit-service-urn-policy http://tools.ietf.org/html/draft-forte-ecrit-service-classification http://tools.ietf.org/html/draft-forte-ecrit-lost-extensions So, which one do you mean? Regarding your document draft-polk-ecrit-lost-geocoding-00.txt >From what I could hear at the last IETF meeting (via my remote participation) a couple of folks had suggestions regarding your document and they roughly proposed the following approach: * Define a protocol for geocoding (not based on LoST) * Define a discovery mechanism (based on LoST) for discovering the server that does the geocoding Regarding the overall approach of working on non-emergency services I have not spoken to Cullen/Robert about this particular document. I plan to post a separate mail about our very recent chat with them. > >I don't mean this to be nefarious sounding, as I plan on >working within the WG until this doc has consensus of at least >those that care about it (knowing that because this isn't >going to be a WG item, the whole WG doesn't necessarily need >to have reached consensus. > >Is this the general plan of action for these types of IDs? > >Of should each of these IDs have -ecrit- removed from the >filenames because there is no hope of them ever being WG items now? > >Looking for clarification and guidance Thanks for raising this issue. Ciao Hannes > >James > >At 08:36 AM 9/30/2009, Tschofenig, Hannes (NSN - FI/Espoo) wrote: >>Hi all, >> >>we discussed the need to change the IANA allocation policy for the >>definition of new top-level services within this working group a few >>times. With the >>http://tools.ietf.org/html/draft-forte-ecrit-service-urn-policy-00 >>proposal Henning and Andrea have describe the modification. We would >>change the allocation policy of top-level services from "Standards >>Action" to "Expert Review". >> >>The policy for assigning labels to sub-services is left unchanged and >>may differ for each top-level service designation and must be defined >>by the document describing the top-level service. For the Service URN >>RFC (RFC 5031) two sub-services are defined, namely 'sos' and >'counseling'. >>The policy for adding sub-services to the 'sos' and the 'counseling' >>services, as defined in RFC 5031, is "Expert Review". >> >>In order to progress draft-forte-ecrit-service-urn-policy-00 we would >>like to know whether someone has problems with this allocation policy >>change. >> >>Ciao >>Hannes & Marc >>_______________________________________________ >>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] Service URN IANA Policy Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Ecrit] Service URN IANA Policy Ted Hardie
- Re: [Ecrit] Service URN IANA Policy Hannes Tschofenig
- Re: [Ecrit] Service URN IANA Policy James M. Polk
- Re: [Ecrit] Service URN IANA Policy Hannes Tschofenig
- Re: [Ecrit] Service URN IANA Policy & the Geocodiā¦ James M. Polk
- Re: [Ecrit] Service URN IANA Policy Henning Schulzrinne
- Re: [Ecrit] Service URN IANA Policy Ted Hardie