tsv-dir review of draft-ietf-tsvwg-iana-ports-09
"Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]" <wesley.m.eddy@nasa.gov> Wed, 19 January 2011 20:51 UTC
Return-Path: <wesley.m.eddy@nasa.gov>
X-Original-To: tsv-area@core3.amsl.com
Delivered-To: tsv-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 27BD33A71C9; Wed, 19 Jan 2011 12:51:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.358
X-Spam-Level:
X-Spam-Status: No, score=-106.358 tagged_above=-999 required=5 tests=[AWL=0.241, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 RyyrNcLjJsJH; Wed, 19 Jan 2011 12:51:38 -0800 (PST)
Received: from ndjsnpf03.ndc.nasa.gov (ndjsnpf03.ndc.nasa.gov [198.117.1.123]) by core3.amsl.com (Postfix) with ESMTP id 39CAC3A7067; Wed, 19 Jan 2011 12:51:38 -0800 (PST)
Received: from ndjsppt03.ndc.nasa.gov (ndjsppt03.ndc.nasa.gov [198.117.1.102]) by ndjsnpf03.ndc.nasa.gov (Postfix) with ESMTP id 30B202D8556; Wed, 19 Jan 2011 14:54:19 -0600 (CST)
Received: from ndjshub05.ndc.nasa.gov (ndjshub05.ndc.nasa.gov [198.117.4.164]) by ndjsppt03.ndc.nasa.gov (8.14.3/8.14.3) with ESMTP id p0JKsJss019943; Wed, 19 Jan 2011 14:54:19 -0600
Received: from NDJSSCC01.ndc.nasa.gov ([198.117.4.166]) by ndjshub05.ndc.nasa.gov ([198.117.4.164]) with mapi; Wed, 19 Jan 2011 14:54:19 -0600
From: "Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]" <wesley.m.eddy@nasa.gov>
To: TSV Dir <tsv-dir@ietf.org>, TSV Area <tsv-area@ietf.org>
Date: Wed, 19 Jan 2011 14:54:18 -0600
Subject: tsv-dir review of draft-ietf-tsvwg-iana-ports-09
Thread-Topic: tsv-dir review of draft-ietf-tsvwg-iana-ports-09
Thread-Index: Acu4GwoLc6l+m9QORjOgpPrBb3Pp7A==
Message-ID: <C304DB494AC0C04C87C6A6E2FF5603DB4826D98A33@NDJSSCC01.ndc.nasa.gov>
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=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2011-01-19_08:2011-01-19, 2011-01-19, 1970-01-01 signatures=0
Cc: tsvwg IETF list <tsvwg@ietf.org>, "draft-ietf-tsvwg-iana-ports@tools.ietf.org" <draft-ietf-tsvwg-iana-ports@tools.ietf.org>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2011 20:51:40 -0000
I've reviewed this document as part of the transport area directorate's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors for their information and to allow them to address any issues raised. The authors should consider this review together with any other last-call comments they receive. Please always CC tsv-dir@ietf.org if you reply to or forward this review. This draft is ready for publication as a BCP RFC. A few small comments which I don't think should be blocking are: 1 - on page 11, in section 6, "near-infinite" is a bit of an exaggeration 2 - on page 16, there's a typo: "MUST accompanied" should be "MUST be accompanied" 3 - on page 17, it may be a good idea to be clear whether the Assignee can be an individual (not just an organization) 4 - on page 17, Contact is defined as a person, but using the IESG as the Contact makes it a group (not a "person"); it might be good to clarify Contact as a person or group of people 5 - on page 17, in the Reference definition, it may be good to qualify the description of broadcast/multicast/anycast use by the protocol as being IP-layer broadcast/multicast/anycast to disambiguate from possible application-layer mechanisms for these that might be used -- Wes Eddy MTI Systems
- tsv-dir review of draft-ietf-tsvwg-iana-ports-09 Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
- Re: tsv-dir review of draft-ietf-tsvwg-iana-ports… Lars Eggert