Re: [Ecrit] PhoneBCP

"James M. Polk" <jmpolk@cisco.com> Wed, 29 April 2009 21:21 UTC

Return-Path: <jmpolk@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 6314928C0E5 for <ecrit@core3.amsl.com>; Wed, 29 Apr 2009 14:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.485
X-Spam-Level:
X-Spam-Status: No, score=-6.485 tagged_above=-999 required=5 tests=[AWL=0.114, 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 jkq1XV-OQNSo for <ecrit@core3.amsl.com>; Wed, 29 Apr 2009 14:21:30 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 7E4FB28C2ED for <ecrit@ietf.org>; Wed, 29 Apr 2009 14:20:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,268,1238976000"; d="scan'208";a="295371317"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 29 Apr 2009 21:22:16 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n3TLMGEt010032 for <ecrit@ietf.org>; Wed, 29 Apr 2009 14:22:16 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n3TLMGhn015206 for <ecrit@ietf.org>; Wed, 29 Apr 2009 21:22:16 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Apr 2009 14:22:15 -0700
Received: from jmpolk-wxp01.cisco.com ([10.89.22.47]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Apr 2009 14:22:15 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 29 Apr 2009 16:22:11 -0500
To: Marc Linsner <mlinsner@cisco.com>, ECRIT <ecrit@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <C6177BF4.147ED%mlinsner@cisco.com>
References: <C6177BF4.147ED%mlinsner@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID: <XFE-SJC-212Mnap2SAW00003db8@xfe-sjc-212.amer.cisco.com>
X-OriginalArrivalTime: 29 Apr 2009 21:22:15.0768 (UTC) FILETIME=[91B04D80:01C9C910]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1655; t=1241040136; x=1241904136; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jmpolk@cisco.com; z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com> |Subject:=20Re=3A=20[Ecrit]=20PhoneBCP |Sender:=20; bh=vae6175TmvSoh7OeSN+4Id6ERMGa8zsjwECzZR7VeTU=; b=t/Hp3UY8D5QnfJfpOrRjm1FPdGZQUjaCdbIK4fPHm/+pe9UIjgU5jvW/vF KL+o1g6q9oy39iCn3JkgwYD0l5IXymonOEGJ2QtP4BH6n+AqWRfBpjNpc+P1 k/PxEJilgEuMNk0hUJfCXfI2NrVjb6vMtxiFFTcWQAL9eC+NEc7fg=;
Authentication-Results: sj-dkim-1; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 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 21:21:31 -0000

Marc

I do not believe the applicability statement is necessary, regardless 
of how well or poor it is written.  The scope of this effort is clear 
- in the IETF community - and this is not an industry view of 
applicability, which is how I believe some are reacting as if it were.

Were this applicability to remain, then every IETF ID and RFC would 
require one, as I know of no situation in which any communication is 
ever entirely comprised of IETF technologies (i.e., every 
communication has a layer 2 - which the IETF has no charge of - or is 
contained entirely within the same physical entity, in which it is 
rare that maintaining standards based protocols are necessary). There 
may be corner cases that I'm not thinking about - but I believe this 
is generally true.

Therefore, I hum *no* to add this applicability statement.

James

At 01:23 PM 4/24/2009, Marc Linsner wrote:
><http://www.ietf.org/internet-drafts/draft-ietf-ecrit-phonebcp-09.txt>http://www.ietf.org/internet-drafts/draft-ietf-ecrit-phonebcp-09.txt 
>
>
>At the San Francisco meeting and ensuing list threads, the last 
>issue around PhoneBCP was whether or not to include an 
>'applicability statement'.  The hum during the meeting was 
>inconclusive.  The draft editor has included text in this latest 
>version in an attempt to compromise on this issue.
>
>Please review this version and respond by Friday May 1 to the list 
>as to your acceptance of this change.
>
>Thanks,
>
>Marc, Hannes, & Roger
>_______________________________________________
>Ecrit mailing list
>Ecrit@ietf.org
>https://www.ietf.org/mailman/listinfo/ecrit