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

<> Sun, 03 August 2014 09:40 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id D8CCC1A0298 for <>; Sun, 3 Aug 2014 02:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, WEIRD_PORT=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fnmGbveQsAHs for <>; Sun, 3 Aug 2014 02:40:37 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E5C611A0296 for <>; Sun, 3 Aug 2014 02:40:36 -0700 (PDT)
Received: from (unknown [xx.xx.xx.201]) by (ESMTP service) with ESMTP id ADDC52AC8A4; Sun, 3 Aug 2014 11:40:34 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown []) by (ESMTP service) with ESMTP id 16855384061; Sun, 3 Aug 2014 11:40:20 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0181.006; Sun, 3 Aug 2014 11:40:19 +0200
From: <>
To: Stefan Winter <>, Bernard Aboba <>
Thread-Topic: [radext] NAI draft: consensus on the name "Network" Access Identifier?
Thread-Index: AQHPrWLfsgtrsUX5NkisNOGD3nOjA5u9J/cAgAF7I4U=
Date: Sun, 3 Aug 2014 09:40:19 +0000
Message-ID: <>
References: <>, <BLU406-EAS1128B276CC838F79A6E7CE893E40@phx.gbl>
In-Reply-To: <BLU406-EAS1128B276CC838F79A6E7CE893E40@phx.gbl>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2014.6.25.220919
Cc: "" <>
Subject: Re: [radext] NAI draft: consensus on the name "Network" Access Identifier?
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 03 Aug 2014 09:40:40 -0000

No change :-)

Envoyé depuis mon Sony Xperia SP d'Orange

---- Bernard Aboba a écrit ----

Do not change the term.

> On Aug 1, 2014, at 1:30, "Stefan Winter" <> wrote:
> 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 ( ) 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: +352 424409 1
> Fax: +352 422473
> PGP key updated to 4096 Bit RSA - I will encrypt all mails if the
> recipient's key is known to me
> _______________________________________________
> radext mailing list
radext mailing list


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,
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, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.