[radext] NAI draft: consensus on the name "Network" Access Identifier?

[Stefan Winter <[e-mail]>]

Hello,

due to my remote-only presence in the IETF90 meeting, one little point
to discuss fell in the cracks; I'd like to ask now on the list for
opinions because this is the only thing holding back the PROTO write-up
of the NAI draft.

In TRAC issue 176 ( http://tools.ietf.org/wg/radext/trac/ticket/176 ) I
raised the point that the document is currently inconsistent in its use
of the term NAI: some parts stress that the identifier is useful in a
generic context, beyond network access, while other parts define it to
be strictly in a network context.

The inconsistency really should be fixed; the question is in what way:
either the object itself could be renamed to reflect the wider focus; or
the name "Network Access Identifier" could stay, explaining that it's
historically grown and does not intend to limit its use to network
access despite the name.

A few people have already voiced their opinion and an emerging consensus
seems to be that Network Access Identifier is a too well-known term to
change.

I'd like to confirm consensus on the list that this is the way to go.
Please let the list know if you disagree with that course of action by
15 Aug 2014.

Greetings,

Stefan Winter

-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: [phone]
Fax: [phone]

PGP key updated to 4096 Bit RSA - I will encrypt all mails if the
recipient's key is known to me

http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66