Re: WGLC Announcement for draft-ietf-tsvwg-iana-ports-08 - 26th November2010

Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 01 December 2010 14:42 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B25323A6B38 for <tsvwg@core3.amsl.com>; Wed, 1 Dec 2010 06:42:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.555
X-Spam-Level:
X-Spam-Status: No, score=-106.555 tagged_above=-999 required=5 tests=[AWL=0.044, 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 jXZ0eoGnuKzt for <tsvwg@core3.amsl.com>; Wed, 1 Dec 2010 06:42:55 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 783AA3A6A1A for <tsvwg@ietf.org>; Wed, 1 Dec 2010 06:42:55 -0800 (PST)
X-AuditID: c1b4fb3d-b7b8cae0000016b1-93-4cf65f385abe
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id F9.27.05809.83F56FC4; Wed, 1 Dec 2010 15:44:08 +0100 (CET)
Received: from [147.214.183.21] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.2.234.1; Wed, 1 Dec 2010 15:44:07 +0100
Message-ID: <4CF65F37.8050400@ericsson.com>
Date: Wed, 01 Dec 2010 15:44:07 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: "t.petch" <ietfc@btconnect.com>
Subject: Re: WGLC Announcement for draft-ietf-tsvwg-iana-ports-08 - 26th November2010
References: <4CCBD067.60206@erg.abdn.ac.uk> <000201cb7b49$212cbc00$4001a8c0@gateway.2wire.net> <4CD159B0.2050906@ericsson.com> <005901cb7b6e$80bbc740$4001a8c0@gateway.2wire.net>
In-Reply-To: <005901cb7b6e$80bbc740$4001a8c0@gateway.2wire.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: tsvwg list <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2010 14:42:56 -0000

Hi,

The author team has now edited this issue into our draft version.
However, after some consideration of IANAs language use we have ended up
using "assign" and assignment instead of allocation. Then we use
"assignment request" or "assignment procedure" depending on context. I
hope that is still satisfactory.

Magnus

t.petch skrev 2010-11-03 16:47:
> ----- Original Message -----
> From: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
> To: "t.petch" <ietfc@btconnect.com>
> Cc: "tsvwg list" <tsvwg@ietf.org>
> Sent: Wednesday, November 03, 2010 1:46 PM
> 
>> Hi Tom,
>>
>> Apparently your comment from January about the mix of terms was missed
>> and not addressed.
>>
>> If I understand the English terms correctly, what we are describing that
>> IANA should do is Allocation, i.e. set aside identifiers for particular
>> usages. We are not giving over the number space to the ones that
>> request, thus Assignment would be wrong?
>>
>> I think we can mostly eliminate one of the terms assignment and
>> allocation. I think we will have more difficult to get rid of
>> registration. My personal thinking on this is at least the following
>> relationship between the terms: A Registrant performs a Registration
>> (process or request) so that IANA can perform an Allocation of a service
>> name and possibly ports.
> 
> Magnus
> 
> That would address my concern. As you say, assign has more of an overtone
> of a legal transfer of ownership, which allocate does not (even if my dictionary
> defines allocate as assign:-(  There is a lot of assignation in the current I-D
> but
> I think that most of it should be changed.
> 
> I like too the idea that registration is the request, and that IANA allocates,
> and
> again, there is a lot of registration and I think that most of it should be
> changed.
> 
> It is unfortunate that the end result of an allocation by IANA is a registry but
> I
> do not think that that can be helped:-(   Whatever terminology we agree on,
> I think that the I-D should spell it out early on.
> 
> I did scan a variety of I-Ds with IANA actions and see IANA allocating,
> registering
> and assigning values in registries, with perhaps the last as the most common,
> but that does
> not make it the right choice for me.
> 
> Tom Petch


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------