Re: [Sip] On The Essentialness of Corrections

"Vijay K. Gurbani" <vkg@alcatel-lucent.com> Mon, 17 December 2007 16:01 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4IP0-0000wZ-CT; Mon, 17 Dec 2007 11:01:10 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J4IOy-0000vT-FT for sip-confirm+ok@megatron.ietf.org; Mon, 17 Dec 2007 11:01:08 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4IOy-0000v2-2u for sip@ietf.org; Mon, 17 Dec 2007 11:01:08 -0500
Received: from ihemail4.lucent.com ([135.245.0.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4IOx-0003hC-Ng for sip@ietf.org; Mon, 17 Dec 2007 11:01:07 -0500
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id lBHG11FG010251; Mon, 17 Dec 2007 10:01:02 -0600 (CST)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90]) by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id lBHG0wj17176; Mon, 17 Dec 2007 10:01:02 -0600 (CST)
Message-ID: <47669D3A.6040903@alcatel-lucent.com>
Date: Mon, 17 Dec 2007 10:00:58 -0600
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] On The Essentialness of Corrections
References: <B765A23B-AB7F-4723-A957-4EEB48788FA4@softarmor.com> <4762F188.4080409@alcatel-lucent.com> <79ADF841-123A-4560-8B83-FB10D46D8C23@softarmor.com>
In-Reply-To: <79ADF841-123A-4560-8B83-FB10D46D8C23@softarmor.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: IETF SIP List <sip@ietf.org>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Dean Willis wrote:
> It's the "logical product" of the essential corrections process.
> 
> Each draft in the essential corrections process has to specify 
> line-by-line changes to the RFC it is correcting. If we were to extract 
> those changes and apply them to the source, we would get the "tracking 
> draft" I'm talking about.

OK; I am with you now.  In that case, yes, maintaining one draft
is preferable.

This also means that -- as Jonathan said earlier -- we have to be
careful as to what constitutes an essential correction  vs. new
functionality.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip