Re: [tcpm] Fwd: New Version Notification fordraft-gont-tcpm-urgent-data-00

"Anantha Ramaiah (ananth)" <ananth@cisco.com> Mon, 10 November 2008 04:11 UTC

Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62F173A69D6; Sun, 9 Nov 2008 20:11:25 -0800 (PST)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43C933A69DA for <tcpm@core3.amsl.com>; Sun, 9 Nov 2008 20:11:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 Hy+gFQOyCMdF for <tcpm@core3.amsl.com>; Sun, 9 Nov 2008 20:11:23 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 77F923A69D6 for <tcpm@ietf.org>; Sun, 9 Nov 2008 20:11:23 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,572,1220227200"; d="scan'208";a="191529263"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 10 Nov 2008 04:11:20 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mAA4BKt0025590; Sun, 9 Nov 2008 20:11:20 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mAA4BKeb006631; Mon, 10 Nov 2008 04:11:20 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 9 Nov 2008 20:11:20 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 9 Nov 2008 20:11:19 -0800
Message-ID: <0C53DCFB700D144284A584F54711EC58061E8C1C@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <4914EFC9.7060906@isi.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] Fwd: New Version Notification fordraft-gont-tcpm-urgent-data-00
Thread-Index: AclBRAy7P4tNt26kRO+8kCay9Wc2ugBoQYVw
References: <200810280000.m9S00h4E029878@venus.xmundo.net><A56C813C-B46D-4A02-A905-DD6B7E163156@windriver.com><200810280203.m9S23foZ023071@venus.xmundo.net><523175BF-A76B-4A4C-B726-AE4274BE9A44@windriver.com><200810290227.m9T2RAHQ001594@venus.xmundo.net><49088156.6020305@isi.edu><200811030149.mA31n6fe020648@venus.xmundo.net><4914B521.3090509@isi.edu><200811080140.mA81eqGx025906@venus.xmundo.net> <4914EFC9.7060906@isi.edu>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Joe Touch" <touch@ISI.EDU>, "Fernando Gont" <fernando@gont.com.ar>
X-OriginalArrivalTime: 10 Nov 2008 04:11:20.0462 (UTC) FILETIME=[62D422E0:01C942EA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=967; t=1226290280; x=1227154280; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ananth@cisco.com; z=From:=20=22Anantha=20Ramaiah=20(ananth)=22=20<ananth@cisco .com> |Subject:=20RE=3A=20[tcpm]=20Fwd=3A=20New=20Version=20Notif ication=20fordraft-gont-tcpm-urgent-data-00 |Sender:=20; bh=luEjlEhsEo2ZkNNO7ZvCEGZ5yZ53rqXrNt8tE9mTZRU=; b=viykXVEFCFtAn6e0MjZpIBUKf5XDZBlYPJAqbunD37Hcim2ltGEb7pDyaj 4PTmEDi4e18h+mSYWCdKJv+Pshf3NGoCbaMbKhfeK9pzn/TsqDFzotA5W1Kp 7uPaDX/hFy;
Authentication-Results: sj-dkim-2; header.From=ananth@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
Cc: tcpm@ietf.org, David Borman <david.borman@windriver.com>, "Andrew Yourtchenko \(ayourtch\)" <ayourtch@cisco.com>
Subject: Re: [tcpm] Fwd: New Version Notification fordraft-gont-tcpm-urgent-data-00
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

<snip>
 
> Fernando Gont wrote:
> ...
> >> Simply
> >> describing it as "what has been deployed" is insufficient 
> >> justification to call this anything other than a bug 
> without further rationale.
> > 
> > And... what would that change? Okay, I can answer this one for you: 
> > More and more people would look somewhere else to find out how the 
> > protocols work in practice.
> > 
> > P.S.: What was it called? "rough consensus and.... "?
> 
> It's not "running code." either.
> 
> We are not here to write documents that describe only what 
> has been implemented. We need to decide what the target is.
> 
> If you want merely to document "what is", that's a fine 
> description for a man page, but it doesn't provide utility in 
> a standards body.

Why wouldn't BCP help in this case ? Esp. if you are trying to document
what is widely being done and also has agreement with the standards.

-Anantha
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm