Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP

Carsten Bormann <cabo@tzi.org> Thu, 27 January 2011 09:17 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 757CF28C123; Thu, 27 Jan 2011 01:17:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.307
X-Spam-Level:
X-Spam-Status: No, score=-106.307 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 bUpGDrwDF7FN; Thu, 27 Jan 2011 01:17:09 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by core3.amsl.com (Postfix) with ESMTP id 89A0E28C10E; Thu, 27 Jan 2011 01:17:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id p0R9K1IM005984; Thu, 27 Jan 2011 10:20:01 +0100 (CET)
Received: from [192.168.10.52] (christoph.dagstuhl.de [192.76.146.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id F37BE40E; Thu, 27 Jan 2011 10:19:59 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>
Date: Thu, 27 Jan 2011 10:20:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D75A1EB1-B142-41D4-A270-FCA8DD81CB23@tzi.org>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.1082)
Cc: Cullen Jennings <fluffy@cisco.com>, tsvwg@ietf.org, IETF discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 09:17:10 -0000

On Jan 27, 2011, at 09:52, Lars Eggert wrote:

>> all new protocols should
>>  be security-capable

Sure.

How is this relevant?

In some protocols, there is value to use them without communication security (think TLS) for some applications, and with communication security for others.
We used to distinguish these two cases using two ports, now we use a single port plus per-connection negotiation like STARTLS.
I think the draft is trying to encourage this conversion, and I agree with this, at least where latency is less relevant.

With UDP-based protocols, it is harder to do this.
Please look at section 7.3 of

	http://tools.ietf.org/html/draft-ietf-core-coap-04.html#section-7.3

and tell us whether this is how you would like this to be handled for UDP-based protocols in the future.
If not, we may want to add to the guidance in the (tsvwg) draft.

Gruesse, Carsten