Re: [sipcore] Proposal: Call for adoption& WGLC: draft-roach-sipcore-priority-00
Robert Sparks <rjsparks@nostrum.com> Wed, 19 December 2012 17:45 UTC
Return-Path: <rjsparks@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F11521F87B2 for <sipcore@ietfa.amsl.com>; Wed, 19 Dec 2012 09:45:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level:
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, SPF_PASS=-0.001, 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 X5PlMW7UKScO for <sipcore@ietfa.amsl.com>; Wed, 19 Dec 2012 09:45:50 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 351C921F8615 for <sipcore@ietf.org>; Wed, 19 Dec 2012 09:45:50 -0800 (PST)
Received: from unnumerable.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBJHjhBS079117 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 19 Dec 2012 11:45:44 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <50D1FD47.207@nostrum.com>
Date: Wed, 19 Dec 2012 11:45:43 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
References: <50A160D8.8030602@alum.mit.edu> <50B68A43.8040605@alum.mit.edu><EDC0A1AE77C57744B664A310A0B23AE20ADA4CD53D@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B0493C3@ESESSMB209.ericsson.se> <999913AB42CC9341B05A99BBF358718D0229B91C@FIESEXC035.nsn-intra.net>
In-Reply-To: <999913AB42CC9341B05A99BBF358718D0229B91C@FIESEXC035.nsn-intra.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Cc: sipcore@ietf.org
Subject: Re: [sipcore] Proposal: Call for adoption& WGLC: draft-roach-sipcore-priority-00
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 17:45:51 -0000
For clarity - this was the message I was pointing to in my AD review. RjS On 11/29/12 6:20 AM, Tschofenig, Hannes (NSN - FI/Espoo) wrote: > I fear you guys read a bit too much into the term "template". > > IANA typically wants to know what information a request for adding a new > value into an existing registry should contain. This is called the > template. As mentioned, here the required info is pretty obvious: a > label and a reference to a document that contains the semantic. If you > want to make it 100% clear add a sentence: "Registration requests to > IANA must include a label (value for the priority header field) and a > reference to a document that explains the semantic of that label." > > What is, however, missing from the IANA consideration is an indication > whether you envision entries to be updated, deleted, or deprecated. I > would write "Updating, deleting, or deprecating of entries in the > registry is not envisioned." > > Ciao > Hannes > >> -----Original Message----- >> From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On >> Behalf Of ext Christer Holmberg >> Sent: Thursday, November 29, 2012 1:51 PM >> To: DRAGE, Keith (Keith); Paul Kyzivat; sipcore@ietf.org >> Subject: Re: [sipcore] Proposal: Call for adoption& WGLC: draft-roach- >> sipcore-priority-00 >> >> Hi, >> >>> Regarding 1), noone has yet responded as to why we need a template > for >> a document where registration requires IETF work. The template >>> is in my view there to ensure all the information that is needed is >> available for expert review. The document management of an internet >>> draft means that if information is needed for review the next > revision >> can provide it. We only need a template if someone decides a different >>> registration policy is needed. >> Fair enough. I hereby withdraw my request for a template :) >> >> Regards, >> >> Christer >> >> >>> -----Original Message----- >>> From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On >>> Behalf Of Paul Kyzivat >>> Sent: 28 November 2012 22:04 >>> To: sipcore@ietf.org >>> Subject: Re: [sipcore] Proposal: Call for adoption & WGLC: >>> draft-roach- >>> sipcore-priority-00 >>> >>> The WGLC and adoption deadline has now passed for >>> draft-roach-sipcore-priority-00. Nine people (other than chairs and >>> authors) made meaningful comments. >>> >>> I conclude there is consensus to adopt this draft as a wg document. >>> >>> Regarding WGLC, two notable issues were raised, and I don't yet see > a >>> clear consensus on those issues: >>> >>> - should there be a registration template? >>> Christer advocates this, Keith opposes, Adam finds it > unnecessary. >>> - should this document also spell out the semantics of all the >> priority >>> values defined in 3261? (Currently it only defines "emergency".) >>> Dan, James, and Roy in favor, Adam and I prefer not to do it *in >> this >>> document*. >>> >>> So, I will ask Adam to submit a wg draft version of this document, >>> otherwise unchanged. >>> >>> While he is doing that, I would like to get a broader consensus on >> the >>> issues above. I'll post a separate question on each of those, to > keep >>> the discussions separate. >>> >>> Thanks, >>> Paul >>> >>> On 11/12/12 3:49 PM, Paul Kyzivat wrote: >>>> PLEASE RESPOND TO THIS MESSAGE >>>> >>>> This is a request to the sipcore wg to adopt the new individual >>>> draft draft-roach-sipcore-priority-00, and a start of WGLC on that >>>> document, to end on Sunday, November 25, 2012. (This is a trivial >>>> doc to review, but people may be slow getting back to work after >> the >>>> meeting and there is a holiday coming in the US, so I'm giving > more >>>> time than I otherwise >>>> would.) >>>> >>>> The reason for this is that the ecrit wg wants to define a new >> value >>>> for the Priority header field. RFC 3261 defines that header field >>>> and an initial set of values. It also mentions the possibility of >> extension. >>>> But it failed to establish an IANA registry for that purpose, and >>>> didn't otherwise define a process for extension. >>>> >>>> The intro to *this* document explains its purpose: >>>> >>>> This document defines a new IANA registry to keep track of the >>> values >>>> defined for the Session Initiation Protocol (SIP) "Priority" >> header >>>> field. This header field was defined in [RFC3261], section >> 20.26. >>>> It was clearly specified in a way that allows for the creation >>>> of >>> new >>>> values beyond those originally specified; however, no registry >> has >>>> been established for it. >>>> >>>> Once that is done, ecrit will be able to make their extension in >>>> accord with the registration procedures that have been defined. > The >>>> registration policy is "IETF Review", so discussion of the merits >> of >>>> that new value can be discussed as part of the review of *that* >>>> document: draft-ietf-ecrit-psap-callback. >>>> >>>> REQUESTED ACTIONS: >>>> >>>> - indicate (ASAP) willingness, or not, for the sipcore wg to work >> on >>>> this problem, and adopt this draft as the basis for that work. >>>> >>>> - provide any comments you have on this document before the end of >>>> the WGLC period (Friday, November 25.) >>>> >>>> Thanks, >>>> Paul >>>> _______________________________________________ >>>> sipcore mailing list >>>> sipcore@ietf.org >>>> https://www.ietf.org/mailman/listinfo/sipcore >>>> >>> _______________________________________________ >>> sipcore mailing list >>> sipcore@ietf.org >>> https://www.ietf.org/mailman/listinfo/sipcore >> _______________________________________________ >> sipcore mailing list >> sipcore@ietf.org >> https://www.ietf.org/mailman/listinfo/sipcore >> _______________________________________________ >> sipcore mailing list >> sipcore@ietf.org >> https://www.ietf.org/mailman/listinfo/sipcore > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore
- [sipcore] Proposal: Call for adoption & WGLC: dra… Paul Kyzivat
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Christer Holmberg
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Paul Kyzivat
- Re: [sipcore] Proposal: Call for adoption & WGLC:… DRAGE, Keith (Keith)
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Christer Holmberg
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Dan Wing
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Adam Roach
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Dale R. Worley
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Adam Roach
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Laura Liess
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Olle E. Johansson
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Olle E. Johansson
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Ben Campbell
- Re: [sipcore] Proposal: Call for adoption & WGLC:… DRAGE, Keith (Keith)
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Dan Wing
- Re: [sipcore] Proposal: Call for adoption & WGLC:… James Polk
- Re: [sipcore] Proposal: Call for adoption & WGLC:… DRAGE, Keith (Keith)
- Re: [sipcore] Proposal: Call for adoption & WGLC:… DRAGE, Keith (Keith)
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Paul Kyzivat
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Roy, Radhika R CIV (US)
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Paul Kyzivat
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Adam Roach
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Christer Holmberg
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Ben Campbell
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Christer Holmberg
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Hannes Tschofenig
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Paul Kyzivat
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Paul Kyzivat
- [sipcore] consensus call: draft-roach-sipcore-pri… Paul Kyzivat
- [sipcore] consensus call: draft-roach-sipcore-pri… Paul Kyzivat
- Re: [sipcore] consensus call: draft-roach-sipcore… Andrew Allen
- Re: [sipcore] consensus call: draft-roach-sipcore… Christer Holmberg
- Re: [sipcore] consensus call: draft-roach-sipcore… Christer Holmberg
- Re: [sipcore] consensus call: draft-roach-sipcore… Michael Procter
- Re: [sipcore] Proposal: Call for adoption & WGLC:… DRAGE, Keith (Keith)
- Re: [sipcore] Proposal: Call for adoption & WGLC:… Christer Holmberg
- Re: [sipcore] Proposal: Call for adoption& WGLC: … Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [sipcore] consensus call: draft-roach-sipcore… Paul Kyzivat
- Re: [sipcore] consensus call: draft-roach-sipcore… Christer Holmberg
- Re: [sipcore] Proposal: Call for adoption& WGLC: … DRAGE, Keith (Keith)
- Re: [sipcore] Proposal: Call for adoption& WGLC: … Robert Sparks