Re: [stir] current draft charter

<philippe.fouquart@orange.com> Tue, 18 June 2013 15:45 UTC

Return-Path: <philippe.fouquart@orange.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25BC421F9AE2 for <stir@ietfa.amsl.com>; Tue, 18 Jun 2013 08:45:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KXOzsoNqKtPS for <stir@ietfa.amsl.com>; Tue, 18 Jun 2013 08:44:59 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id BABBB21F9ACA for <stir@ietf.org>; Tue, 18 Jun 2013 08:44:55 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 0F9D532497D; Tue, 18 Jun 2013 17:44:54 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id C5D9235C090; Tue, 18 Jun 2013 17:44:53 +0200 (CEST)
Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Tue, 18 Jun 2013 17:44:53 +0200
From: philippe.fouquart@orange.com
To: Richard Barnes <rlb@ipv.sx>, Dave Crocker <dcrocker@bbiw.net>
Thread-Topic: [stir] current draft charter
Thread-Index: AQHOZwiVGT8OWD09JUqSfli80C7Gm5kxLcUAgAAL0QCAAIQHAIAAcu6AgAADDoCAABB/AIAAJmCAgAAQaYCAAADrAIAABU0AgABkooCAAOCqgIAAU3yAgAA76gCABBp2gIAAEO2AgABhe4CAABagAIAAEU+AgAA97YCAABdWgIAAkrUAgAAi54CAAJAeAIAAxmUggAAPOQCAAAHLgIAAAUSAgAAoxkA=
Date: Tue, 18 Jun 2013 15:44:53 +0000
Message-ID: <21650_1371570293_51C08075_21650_436_1_B5939C6860701C49AA39C5DA5189448B0A3864@PEXCVZYM12.corporate.adroot.infra.ftgroup>
References: <CDE47FBA.21982%jon.peterson@neustar.biz> <275EE7EE-E92C-454A-BD5C-C04BE171AA14@cs.columbia.edu> <4647_1371560112_51C058B0_4647_190_1_B5939C6860701C49AA39C5DA5189448B0A37D8@PEXCVZYM12.corporate.adroot.infra.ftgroup> <010701ce6c35$672f6970$358e3c50$@shockey.us> <51C078F1.4020508@dcrocker.net> <CAL02cgRo4iTB59Ux+QLbV83ook9Mg=CQ6RDSYDHGsxjPf6HrTA@mail.gmail.com>
In-Reply-To: <CAL02cgRo4iTB59Ux+QLbV83ook9Mg=CQ6RDSYDHGsxjPf6HrTA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.1]
Content-Type: multipart/alternative; boundary="_000_B5939C6860701C49AA39C5DA5189448B0A3864PEXCVZYM12corpora_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.21.113319
Cc: "stir@ietf.org" <stir@ietf.org>, Henning Schulzrinne <hgs@cs.columbia.edu>, "Peterson, Jon" <jon.peterson@neustar.biz>, Richard Shockey <richard@shockey.us>
Subject: Re: [stir] current draft charter
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stir>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 15:45:03 -0000

Either of these would work fine for me.

I don't want to make it sound more complex than necessary but would just note that using the term "assignee" is sometimes also tricky. For example, a number range assignee may remain the same even though numbers have been ported out of that range. (Incidentally, in a number of national numbering plan, it's always the assignee's responsibility to provide an annual report on the use of that range (and on all of its assigned ranges), which may therefore oddly enough include numbers that have been ported out)

Using your terms, in these cases, the holder has a number in a range which is and remains assigned to a party it (the holder) has no relationship with.

Philippe Fouquart
Orange Labs Networks
+33 (0) 1 45 29 58 13

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Tuesday, June 18, 2013 5:17 PM
To: Dave Crocker
Cc: Richard Shockey; FOUQUART Philippe OLNC/OLN; stir@ietf.org; Peterson, Jon; Henning Schulzrinne
Subject: Re: [stir] current draft charter

On Tue, Jun 18, 2013 at 11:12 AM, Dave Crocker <dhc@dcrocker.net<mailto:dhc@dcrocker.net>> wrote:
On 6/18/2013 8:06 AM, Richard Shockey wrote:
Although people sometimes like using ownership as a shortcut, it's more of a
right of use really. (I'm sure some here will remember discussions on the
notion of carrier of record with eye-watering nostalgia)

As someone who's been using the term ownership here, I'll note that I indeed meant it as an expedient and am happy to use whatever term is already common or that the group prefers.  The 'right to use' is the important issue here, not the legality of ownership.

Absent there being an established term, how about assignment and assignee, in place of ownership and owner?

That would be consistent with usage in the Internet number / RPKI space.  The verb "to hold" is also used, e.g., the holder of number resources.

--Richard




d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net<http://bbiw.net>
_______________________________________________
stir mailing list
stir@ietf.org<mailto:stir@ietf.org>
https://www.ietf.org/mailman/listinfo/stir


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.