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

Adam Roach <adam@nostrum.com> Tue, 13 November 2012 02:58 UTC

Return-Path: <adam@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 E252F21F884A for <sipcore@ietfa.amsl.com>; Mon, 12 Nov 2012 18:58:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.157
X-Spam-Level:
X-Spam-Status: No, score=-102.157 tagged_above=-999 required=5 tests=[AWL=0.443, 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 GIhdNmeXn4Op for <sipcore@ietfa.amsl.com>; Mon, 12 Nov 2012 18:58:06 -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 534CE21F8847 for <sipcore@ietf.org>; Mon, 12 Nov 2012 18:58:06 -0800 (PST)
Received: from Orochi.local (99-152-144-32.lightspeed.dllstx.sbcglobal.net [99.152.144.32]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qAD2vxun006319 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 12 Nov 2012 20:58:00 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <50A1B736.7070708@nostrum.com>
Date: Mon, 12 Nov 2012 20:57:58 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@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>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE202D3002AF9@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 99.152.144.32 is authenticated by a trusted mechanism)
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 02:58:07 -0000

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