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

"Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]" <wesley.m.eddy@nasa.gov> Wed, 10 February 2010 18:41 UTC

Return-Path: <wesley.m.eddy@nasa.gov>
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 324AE3A73C0 for <tcpm@core3.amsl.com>; Wed, 10 Feb 2010 10:41:41 -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=[AWL=0.000, 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 TayNFFjMnr-I for <tcpm@core3.amsl.com>; Wed, 10 Feb 2010 10:41:40 -0800 (PST)
Received: from ndmsnpf02.ndc.nasa.gov (ndmsnpf02.ndc.nasa.gov [198.117.0.122]) by core3.amsl.com (Postfix) with ESMTP id 0F1F73A73B6 for <tcpm@ietf.org>; Wed, 10 Feb 2010 10:41:39 -0800 (PST)
Received: from ndjsppt02.ndc.nasa.gov (ndjsppt02.ndc.nasa.gov [198.117.1.101]) by ndmsnpf02.ndc.nasa.gov (Postfix) with ESMTP id 2EB84D0011; Wed, 10 Feb 2010 12:42:50 -0600 (CST)
Received: from ndjshub02.ndc.nasa.gov (ndjshub02-pub.ndc.nasa.gov [198.117.1.161]) by ndjsppt02.ndc.nasa.gov (8.14.3/8.14.3) with ESMTP id o1AIgoRs015909; Wed, 10 Feb 2010 12:42:50 -0600
Received: from NDJSSCC01.ndc.nasa.gov ([198.117.4.166]) by ndjshub02.ndc.nasa.gov ([198.117.1.161]) with mapi; Wed, 10 Feb 2010 12:42:49 -0600
From: "Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]" <wesley.m.eddy@nasa.gov>
To: David Borman <david.borman@windriver.com>, Fernando Gont <fernando@gont.com.ar>, "ayourtch@cisco.com" <ayourtch@cisco.com>
Date: Wed, 10 Feb 2010 12:42:49 -0600
Thread-Topic: [tcpm] WGLC: draft-ietf-tcpm-urgent-data-02.txt
Thread-Index: AcqmmtGeRjmFwy6KSmq7yuQ79ckQvgD42DSA
Message-ID: <C304DB494AC0C04C87C6A6E2FF5603DB47DD6035B8@NDJSSCC01.ndc.nasa.gov>
References: <5981EBEA-5F7B-422A-A094-5D2548F705EB@windriver.com>
In-Reply-To: <5981EBEA-5F7B-422A-A094-5D2548F705EB@windriver.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2010-02-10_14:2010-02-06, 2010-02-10, 2010-02-10 signatures=0
Cc: "tcpm@ietf.org" <tcpm@ietf.org>
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: Wed, 10 Feb 2010 18:41:41 -0000

I concur with Michael's suggested edits, plus here are some
more comments.  Overall, I think it's in good shape and just
about ready to publish.  A minor update should be all that's
needed, but I do want to make sure that one of the
recommendations is worded correctly (see final comment below).

Editorial:

- section 1, paragraph 3:
  "IT accommodates" -> "it accommodates" ?

- section 1, paragraph 3:
  "using urgent the urgent" -> "using the urgent"

- section 1, paragraph 4:
  "how current TCP implementations" ->
  "how some current TCP implementations"


- section 3.2, paragraph 1:
  "never reflected into" -> "never was reflected in"


Semi-Technical:

- section 2.3 - on the allowed length of urgent data, should this
  mention that obviously there is a limitation due to the length
  of a sequence number field?  You can't send a terabyte of urgent
  data.

- section 6:
  I think it's not worded correctly when we say that applications
  using the sockets API MUST set SO_OOBINLINE.  What we really
  want to say is more like:

  "Even though applications SHOULD NOT employ the urgent mechanism,
   applications that require the use of urgent data MUST set
   SO_OOBINLINE."

  Right?  Apps that don't use urgent data shouldn't have to be
  bothered by the fact that it's broken.

--
Wes Eddy
MTI Systems


>-----Original Message-----
>From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On Behalf Of
>David Borman
>Sent: Friday, February 05, 2010 2:38 PM
>To: tcpm@ietf.org WG
>Cc: tcpm-chairs@tools.ietf.org; ayourtch@cisco.com; Fernando Gont
>Subject: [tcpm] WGLC: draft-ietf-tcpm-urgent-data-02.txt
>
>Note: As recent discussions on this list have indicated, we need members
>of this mailing list to be involved.  Please take the time to read
>through this document and send a message to the mailing list either
>supporting publishing this document, or commenting on why it is not
>ready to be published.  This particular document is quite short and easy
>to understand.  -David Borman, TCPM co-chair.
>----------------------------
>
>This is to announce the start of the WG Last Call for:
>
>Title           : On the implementation of the TCP urgent mechanism
>Author(s)       : F. Gont and A. Yourtchenko
>Filename        : draft-ietf-tcpm-urgent-data-02.txt
>Pages           : 13
>Date            : November 26, 2009
>Intended Status : Proposed Standard
>
>http://www.ietf.org/internet-drafts/draft-ietf-tcpm-urgent-data-02.txt
>
>It is our understanding that all the feedback has been incorporated into
>this latest version and that there are no known outstanding issues with
>this document.
>
>Please send feedback to the list.
>
>The WGLC will end on Friday, February 19, 2010.
>_______________________________________________
>tcpm mailing list
>tcpm@ietf.org
>https://www.ietf.org/mailman/listinfo/tcpm