Re: [tsvwg] When to use Updates -- was: SCTP NAT support, draft-stewart-natsupp-tsvwg-00
"James M. Polk" <jmpolk@cisco.com> Tue, 26 January 2010 20:55 UTC
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FE2C3A69D0 for <tsvwg@core3.amsl.com>; Tue, 26 Jan 2010 12:55:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 b-0qz+8UV8G7 for <tsvwg@core3.amsl.com>; Tue, 26 Jan 2010 12:55:04 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 2CAC53A69C7 for <tsvwg@ietf.org>; Tue, 26 Jan 2010 12:55:04 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am0FAAblXkurR7Ht/2dsb2JhbACHArtulyIChDcE
X-IronPort-AV: E=Sophos;i="4.49,348,1262563200"; d="scan'208";a="140368774"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 26 Jan 2010 20:55:14 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o0QKt9X1005470 for <tsvwg@ietf.org>; Tue, 26 Jan 2010 20:55:14 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 26 Jan 2010 12:55:11 -0800
Received: from jmpolk-wxp01.cisco.com ([10.99.80.18]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 26 Jan 2010 12:55:10 -0800
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 26 Jan 2010 14:55:00 -0600
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Message-ID: <XFE-SJC-211E8HqS5C700003480@xfe-sjc-211.amer.cisco.com>
X-OriginalArrivalTime: 26 Jan 2010 20:55:10.0953 (UTC) FILETIME=[D9953590:01CA9EC9]
Subject: Re: [tsvwg] When to use Updates -- was: SCTP NAT support, draft-stewart-natsupp-tsvwg-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2010 20:55:05 -0000
At 02:36 PM 1/26/2010, James M. Polk wrote: >At 01:52 PM 1/26/2010, Alfred =?hp-roman8?B?SM5uZXM=?= wrote: >> >>"Instructions to Request for Comments (RFC) Authors", the >>"successor of RFC 2223", >> <http://www.rfc-editor.org/rfc-editor/instructions2authors.txt> >>states in Section 2.11: >> >>| Updates >>| >>| Specifies an earlier document whose contents are modified or >>| augmented by the new document. The new document cannot be >>| used alone, it can only be used in conjunction with the >>| earlier document. >> >>That's the current definition, yet apparently not always enforced >>by the RFC Editor, in order to avoid conflict with the RFC stream >>"gatekeepers". :-) >> >>IMO, "cannot be used alone, can only be used in conjunction with >>the earlier document" is a prudently chosen clause specifying a >>criterion that can be decided upon in a rather objective manner. I'm going to just focus on this salient part above. put another way, this is discussing the differences between a new doc being dependent or independent of the "older" (or base) doc. Unfortunately -- this doesn't make the case in either way to me because any extension to a base protocol is therefore an update to that protocol because the extension is pointless without the base protocol. I can easily see one extension to a protocol being independent from another extension to the same protocol, but neither extension can work at all without the original protocol specification. From this, I don't take <http://www.rfc-editor.org/rfc-editor/instructions2authors.txt> to be very clear on the subject of updates or extensions. James >>Best regards, >> Alfred HÎnes. >> >>+------------------------+--------------------------------------------+ >>| TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | >>| Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | >>| D-71254 Ditzingen | E-Mail: ah@TR-Sys.de | >>+------------------------+--------------------------------------------+
- Re: [tsvwg] When to use Updates -- was: SCTP NAT … Alfred Hönes
- Re: [tsvwg] When to use Updates -- was: SCTP NAT … James M. Polk