Re: [tcpm] WGLC: draft-ietf-tcpm-urgent-data-02.txt

John Heffner <johnwheffner@gmail.com> Tue, 02 March 2010 21:36 UTC

Return-Path: <johnwheffner@gmail.com>
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 50A603A8CC7 for <tcpm@core3.amsl.com>; Tue, 2 Mar 2010 13:36:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 UomNAllulbC9 for <tcpm@core3.amsl.com>; Tue, 2 Mar 2010 13:36:25 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 2DC293A8CBF for <tcpm@ietf.org>; Tue, 2 Mar 2010 13:36:25 -0800 (PST)
Received: by wyb40 with SMTP id 40so386126wyb.31 for <tcpm@ietf.org>; Tue, 02 Mar 2010 13:36:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=N99G3wu7VhPFKztyWs+f73c6T7D/X9mujGGmvxlsqSk=; b=Feb34+i6ShmsPnLT83rZOPCiFP3/l1+xYqG+bYIrlkZ7pqWJTDlrXMdIfbIgNpGAVH txXJpDwtZzrZIbVnwGVDX1MpcwwsbhGuw7FsLfrCYy811x/S0VbL1ZUlABr1UJZ877s7 vcaaqsss3X7TCjKKOPDaMSJD8sDo9fQblHBsw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=N9C/mdalXr/Fekct5YIk+LIR1yDeavabCru/8Trhw9jlqGyrKdvh+wtFLbOvN7GuRT AkcxsRER3+LQb0dSlDOEdkuiFU0NuFHikFYfd0rU8Gav33vEsF1eeP30NLB/5UPzQhek owV3yqX2vvQvE3BmW3cprXC+vt72G0IfBdJwQ=
MIME-Version: 1.0
Received: by 10.216.93.66 with SMTP id k44mr280914wef.63.1267565782199; Tue, 02 Mar 2010 13:36:22 -0800 (PST)
In-Reply-To: <C88F591E-99C2-4131-843F-68DE4E8CE865@weston.borman.com>
References: <5981EBEA-5F7B-422A-A094-5D2548F705EB@windriver.com> <C88F591E-99C2-4131-843F-68DE4E8CE865@weston.borman.com>
Date: Tue, 02 Mar 2010 16:36:22 -0500
Message-ID: <1e41a3231003021336v549699e1yfb4c329d82fd38c8@mail.gmail.com>
From: John Heffner <johnwheffner@gmail.com>
To: David Borman <dab@weston.borman.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "tcpm@ietf.org WG" <tcpm@ietf.org>, ayourtch@cisco.com, Fernando Gont <fernando@gont.com.ar>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-urgent-data-02.txt
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: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 02 Mar 2010 21:36:26 -0000

On Tue, Mar 2, 2010 at 4:03 PM, David Borman <dab@weston.borman.com> wrote:
> WG chair hat on:
> ----------------
> We are well past the end of the WGLC for this document.  On February 19, a new draft:
>        draft-ietf-tcpm-urgent-data-03.txt
> was posted.  I have reviewed the differences between the -02 and -03 versions, and it appears to me that all of the issues that were raised against the -02 version have been addressed in the -03 version.  There have been no additional comments on the mailing list since the -03 version was made available.
>
> Therefore, we will be sending this document to the IESG in the next day or two, so if you have any additional issues with the -03 draft, you should speak up immediately.
>
>                        -David Borman, TCPM co-chair
>
> WG chair hat off:
> -----------------
> I just realized that:
> 1) The document should have at the top:
>        Updates: RFCs 793, 1011, 1122
> 2) The "1. Introduction" section should say that it updates all 3 RFCs, not just RFC 1122.
> 3) The Normative References should include RFC 1011.
> 4) The "4. Updating RFC 1122" section should also mention all 3 RFCs, not just RFC 1122
>
> The other RFCs that talk about the urgent pointer, 924, 944, 961 and 991, are all obsoleted by RFC 1011, hence only RFC 1011 needs to be mentioned.

Nit: in the title of Section 2.1: s/inications/indications/

  -John