We had intended to transfer "eap-noob.net" to IANA, but replacing this domain with .arpa is equally ok.
The domain name reservation considerations in section 4.4. of https://tools.ietf.org/html/draft-aura-eap-noob-05#section-4.4 will still be relevant. Tuomas -----Original Message----- From: Eliot Lear <l...@cisco.com> Sent: Wednesday, 6 March, 2019 15:31 To: Alan DeKok <al...@deployingradius.com> Cc: Aura Tuomas <tuomas.a...@aalto.fi>; emu@ietf.org Subject: Re: [Emu] Questions about EAP-NOOB Importance: High And indeed it was Alan who I was referring to in my message. I generally agree with Alan’s thinking below. Eliot > On 6 Mar 2019, at 13:45, Alan DeKok <al...@deployingradius.com> wrote: > > On Mar 6, 2019, at 7:23 AM, Aura Tuomas <tuomas.a...@aalto.fi> wrote: >> The realm used by the peer is initially “eap-noob.net”. The server can >> assign another realm in Initial Exchange. The main purpose for assigning >> another realm is that the peer can later use it for roaming in access >> networks that have AAA routing set up for the assigned realm. > > This is fine for an initial draft. I'd avoid implementing anything that > uses "eap-noob.net", though. > > The correct domain to use is .arpa: > > https://www.iana.org/domains/arpa > > The controlling document here is RFC 3172. > > It looks like EAP-TEAP-BRSKI requires a similar NAI for provisioning. So it > would best best to coordinate both the name, and the use of it. Perhaps > "provisioning.arpa" could be used as a generic name, and then subdomains > within that could be used for particular purposes. > > Alan DeKok. > > _______________________________________________ > Emu mailing list > Emu@ietf.org > https://www.ietf.org/mailman/listinfo/emu _______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
