Re: [port-srv-reg] Who is doing the presenations in APParea and TSVWG

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Sun, 08 November 2009 16:22 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: port-srv-reg@core3.amsl.com
Delivered-To: port-srv-reg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5526F3A68D1 for <port-srv-reg@core3.amsl.com>; Sun, 8 Nov 2009 08:22:17 -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 sMp0AtZyzIRq for <port-srv-reg@core3.amsl.com>; Sun, 8 Nov 2009 08:22:16 -0800 (PST)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id DE20A3A6879 for <port-srv-reg@ietf.org>; Sun, 8 Nov 2009 08:22:14 -0800 (PST)
Received: from Gorry-Fairhursts-Laptop-7.local (fgrpf.plus.com [212.159.18.54]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id nA8GM9T4024329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 8 Nov 2009 16:22:10 GMT
Message-ID: <4AF6F032.4010202@erg.abdn.ac.uk>
Date: Sun, 08 Nov 2009 16:22:10 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland, No SC013683.
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
References: <4AE99189.3090208@ericsson.com> <4AE9A654.6060004@isi.edu> <5E99A77C-A43F-42EF-98D7-F7138CCD527D@apple.com> <4AF69B48.4050408@isi.edu>
In-Reply-To: <4AF69B48.4050408@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
Cc: "port-srv-reg@ietf.org" <port-srv-reg@ietf.org>
Subject: Re: [port-srv-reg] Who is doing the presenations in APParea and TSVWG
X-BeenThere: port-srv-reg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Discussion of updates to service name and transport protocol port registry <port-srv-reg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/port-srv-reg>, <mailto:port-srv-reg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/port-srv-reg>
List-Post: <mailto:port-srv-reg@ietf.org>
List-Help: <mailto:port-srv-reg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/port-srv-reg>, <mailto:port-srv-reg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Nov 2009 16:22:17 -0000

Looks good to me,

A few comments on the slides and the draft...

Slide 1:
- It would be good to include the draft name on the slide:
draft-ietf-tsvwg-iana-ports-03

Slide 8:
This line took me a wee moment to decipher:
"Port only for transports requested"
- is it better as?:
"Port only for requested transports"

Slide 11:
This line doesn't seem to be the whole story:

"Service code to at most one port"
-> This isn't a requirement as per RFC 5595 (e.g. section 4.1), although 
it is good as common practice, unless the requester knows better and 
requires expert review (as described in the draft section 10.3.2). Did 
you mean at most one port per service code?

=============

And a wee bit of (late) feedback on the DCCP topics in the draft:

Section 10.3.1:
- It is good to also cite RFC 5595 (you currently cite the draft) for 
service code information, since this updated RFC 4340 in many ways.

- We MUST note in the new draft that no registry allocations can be made 
for zero or 4294967295, and no registry allocations can be made for 
1056964608-1073741823 (high byte ASCII "?") reserved for private use 
[19.8 of RFC 4340].

- I think we may have missed the rule that:
   "IANA MUST NOT allocate more than one DCCP server port with a
    single Service Code value."

- Does this draft also updates RFC 5595, since the latter states where 
ports and service codes are registered?

Section 10.3.2:
- I think it would also be helpful to cite RFC 5595 in 10.3.2 - since 
this explains how ports and SC interact and how you can manage without 
port allocations.

Section 11: You didn't fix the acknowledgments:-)
- I don't recall Tom being in the loop, what I recall was that I ripped 
the first version of text from an earlier draft of RFC 5595 
(draft-ietf-dccp-serv-codes-04.txt).  You could check with Tom, if you 
like;-)

Gorry


Joe Touch wrote:
 > Feedback appreciated. I will be able to edit until about 0800 Monday,
 > but need to post for those online by then.
 >
 > Joe
 >
 > Stuart Cheshire wrote:
 >> On 29 Oct 2009, at 7:27, Joe Touch wrote:
 >>
 >>> I'm open Mon AM and can present if useful. I'll also be at TSVWG.
 >>>
 >>> Joe
 >>
 >> Do you have some slides prepared Joe?
 >>
 >> If you do, and you can email them to the list, I'll take a look at them
 >> tonight and give you feedback.
 >>
 >> Stuart Cheshire <cheshire@apple.com>
 >> * Wizard Without Portfolio, Apple Inc.
 >> * Internet Architecture Board
 >> * www.stuartcheshire.org
 >>
 >> ------------------------------------------------------------------------
 >>
 >> _______________________________________________
 >> Port-srv-reg mailing list
 >> Port-srv-reg@ietf.org
 >> https://www.ietf.org/mailman/listinfo/port-srv-reg