Re: [Ecrit] PhoneBCP

Marc Linsner <mlinsner@cisco.com> Wed, 29 April 2009 18:51 UTC

Return-Path: <mlinsner@cisco.com>
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 7DA763A69ED for <ecrit@core3.amsl.com>; Wed, 29 Apr 2009 11:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.412
X-Spam-Level:
X-Spam-Status: No, score=-6.412 tagged_above=-999 required=5 tests=[AWL=0.187, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 6vqmUwTH3s55 for <ecrit@core3.amsl.com>; Wed, 29 Apr 2009 11:51:42 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 819033A687A for <ecrit@ietf.org>; Wed, 29 Apr 2009 11:51:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,267,1238976000"; d="scan'208";a="178645805"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 29 Apr 2009 18:52:53 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n3TIqqJo018282; Wed, 29 Apr 2009 11:52:52 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id n3TIqmgK023609; Wed, 29 Apr 2009 18:52:52 GMT
Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Apr 2009 14:52:52 -0400
Received: from [10.116.195.115] ([10.116.195.115]) by xmb-rtp-205.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Apr 2009 14:52:52 -0400
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Wed, 29 Apr 2009 14:52:51 -0400
From: Marc Linsner <mlinsner@cisco.com>
To: Randall Gellens <randy@qualcomm.com>, ECRIT <ecrit@ietf.org>
Message-ID: <C61E1A43.149FA%mlinsner@cisco.com>
Thread-Topic: [Ecrit] PhoneBCP
Thread-Index: AcnI+7JFmLGvwVzc7Em01pfFUj7wEQ==
In-Reply-To: <p06240604c61e4e949618@[192.168.1.13]>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 29 Apr 2009 18:52:52.0252 (UTC) FILETIME=[B3044DC0:01C9C8FB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1563; t=1241031173; x=1241895173; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mlinsner@cisco.com; z=From:=20Marc=20Linsner=20<mlinsner@cisco.com> |Subject:=20Re=3A=20[Ecrit]=20PhoneBCP |Sender:=20; bh=b2Sv+fjZDwSoiE/ZXKdEXK+yGNBngwVWNNfo+N1VwAY=; b=O75ECLFGSXBUH8TT1uLualYwjI5K8cNTa/rKyGeiLzmiXON5mj7tiyTNQA ZoFHFvTFToo7C9yVvgtOBBE+83SnoEVSfHYnaiTt2kmExTdNnpyt76kBkEf1 8JwPD9vLbd;
Authentication-Results: sj-dkim-4; header.From=mlinsner@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Subject: Re: [Ecrit] PhoneBCP
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: Wed, 29 Apr 2009 18:51:43 -0000

All,

*Remember, this hum closes tomorrow (Friday, May 1).

As I stated in an email on Monday.

"
This is a consolidated hum.

If you don't agree that we need an applicability statement, hum against it.

If you agree that we need an applicability statement, but don't like the
current text, hum against it.

If you agree with the statement as written, hum for it.

If consensus is against the statement, it will be taken out of the draft.

"

I use the term 'applicability statement' as that was the term that
originally started this discussion.  It in no way implies the chairs
desires.  Changing the term now would cause an even bigger discussion, IMO.
My hope is that everyone followed the discussion and makes their choice
heard via this call for a hum.  Thank you to those that have already
expressed their choice.

We still have the old version of the draft.  If consensus fails as outlined
above, we'll bring back the old version.

-Marc-  


On 4/29/09 2:38 PM, "Randall Gellens" <randy@qualcomm.com> wrote:

> There have been a couple of people asserting that the text in the
> document was added without consensus.  While it is certainly the
> chairs' prerogative to call for consensus on this point, there was a
> lot of discussion on the list five weeks ago.  It certainly had
> enough discussion then to warrant inclusion in a document version for
> discussion.  In fact, I think the current text is basically Richard's
> take on a compromise that would get us past the deadlock we seem to
> be revisiting.