Re: [sipcore] Proposal: Call for adoption & WGLC: draft-roach-sipcore-priority-00

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Tue, 13 November 2012 19:50 UTC

Return-Path: <keith.drage@alcatel-lucent.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 40CE821F8718 for <sipcore@ietfa.amsl.com>; Tue, 13 Nov 2012 11:50:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.976
X-Spam-Level:
X-Spam-Status: No, score=-109.976 tagged_above=-999 required=5 tests=[AWL=0.273, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, 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 mc2JidCtdtRS for <sipcore@ietfa.amsl.com>; Tue, 13 Nov 2012 11:50:32 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 4B48B21F84D2 for <sipcore@ietf.org>; Tue, 13 Nov 2012 11:50:31 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id qADJnjND022298 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 13 Nov 2012 20:50:26 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Tue, 13 Nov 2012 20:50:20 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Adam Roach <adam@nostrum.com>
Date: Tue, 13 Nov 2012 20:50:19 +0100
Thread-Topic: [sipcore] Proposal: Call for adoption & WGLC: draft-roach-sipcore-priority-00
Thread-Index: Ac3BSrQVnQ6zOI3cSLy5IgJ6uCTlrAAjTwZg
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE202D3002E08@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <50A160D8.8030602@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B02AD26@ESESSMB209.ericsson.se> <50A17929.5060005@alum.mit.edu> <EDC0A1AE77C57744B664A310A0B23AE202D3002AF9@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <50A1B736.7070708@nostrum.com>
In-Reply-To: <50A1B736.7070708@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "sipcore-ads@tools.ietf.org" <sipcore-ads@tools.ietf.org>, SIPCORE <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: Tue, 13 Nov 2012 19:50:33 -0000

I'm referring to these comments I made on the template proposal on 6th November which I copy here:

" As regards the template (which other mails have suggested), we possibly do not need one.

Part of this down to the level of review that is required; in the document this is set as IETF review. At this level, an RFC has to exist and go through IETF community review. There will be enough people around in this process to ensure that all the information that people need to see outside the IANA table actually exists. Conversely where we are allocating values on expert review, a template could be essential if only to ensure the expert doing the review has enough information available to perform the review; that information may well exceed the information that needs to appear in the template itself.

Note that I did have a discussion with IANA on both these issues, and it would be wrong to say an opinion was expressed, Michelle seemed to be in alignment with these points."

Keith

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]
> Sent: 13 November 2012 02:58
> To: DRAGE, Keith (Keith)
> Cc: Paul Kyzivat; Christer Holmberg; SIPCORE; sipcore-ads@tools.ietf.org
> Subject: Re: [sipcore] Proposal: Call for adoption & WGLC: draft-roach-
> sipcore-priority-00
> 
> On 11/12/12 16:46, DRAGE, Keith (Keith) wrote:
> > It might also be appropriate to answer the points I made in response,
> rather than just repeating the demand.
> 
> Are you meaning to indicate the question of whether this document
> updates 3261? That seems to be the only point of contention you've
> raised, and I've heard scant support for your position on that topic.
> 
> By way of contrast, Paul, Ben, Robert and I -- the only others who have
> engaged on this rather esoteric bit of IETF arcana -- have all stated
> what *I* believe are lucid and defensible reasons that this draft is
> required to update 3261. I'm certainly willing to consider the
> conversation to be ongoing, if there are new points to be made.
> Otherwise, this is clearly a non-technical matter of opinion about which
> people seem to have already reached their own conclusions, and the
> preponderance of the expressed opinion seems to put you in a minority
> class of size one.
> 
> /a