Re: [Sip] draft-drage-sip-essential-correction-02.txt

"Vijay K. Gurbani" <vkg@alcatel-lucent.com> Mon, 19 November 2007 18:32 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 1IuBQ1-0004Ao-Tq; Mon, 19 Nov 2007 13:32:25 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IuBPz-00047h-Pt for sip-confirm+ok@megatron.ietf.org; Mon, 19 Nov 2007 13:32:23 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuBPz-00047U-Fg for sip@ietf.org; Mon, 19 Nov 2007 13:32:23 -0500
Received: from ihemail3.lucent.com ([135.245.0.37]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuBPz-0000HT-2l for sip@ietf.org; Mon, 19 Nov 2007 13:32:23 -0500
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id lAJIWK61003640 for <sip@ietf.org>; Mon, 19 Nov 2007 12:32:20 -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 lAJIWKj21221; Mon, 19 Nov 2007 12:32:20 -0600 (CST)
Message-ID: <4741D6B3.2040801@alcatel-lucent.com>
Date: Mon, 19 Nov 2007 12:32:19 -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: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
Subject: Re: [Sip] draft-drage-sip-essential-correction-02.txt
References: <5D1A7985295922448D5550C94DE29180019335E2@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE29180019335E2@DEEXC1U01.de.lucent.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.37
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
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

DRAGE, Keith (Keith) wrote:
> I have submitted a new version of 
> 
> http://www.ietf.org/internet-drafts/draft-drage-sip-essential-correction
> -02.txt
[...]
> -	a link to the web page giving details of the documents currently
> in the process.

Keith: Would the SIP ABNF IPv6 fix draft qualify?
   (http://tools.ietf.org/html/draft-gurbani-sip-ipv6-abnf-fix-00)
Need to discuss this in WG.

> -	a new section for drafts to list the normative requirements
> outside (and in addition to) the section structure documentation that is
> already in the document. In doing this I have listed it as an open issue
> and would welcome feedback as to whether this the correct wording or
> not, or whether anything else needs to be stated.

The template you give essentially follows the sections enumerated
in http://tools.ietf.org/html/draft-sparks-sip-invfix-00.  As a
means of codifying information, it seems reasonable.  Also, if
you eyeball the three other -fix drafts besides invfix-00 (i.e.,
http://tools.ietf.org/html/draft-ietf-sip-record-route-fix,
http://tools.ietf.org/html/draft-ietf-sip-fork-loop-fix, and
http://tools.ietf.org/html/draft-gurbani-sip-ipv6-abnf-fix-00)
they essentially follow the same template anyway.

Thanks,

- 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