Hi Eliot, On 4/24/20 4:22 PM, Eliot Lear wrote:
Hi Mohit On 24 Apr 2020, at 15:02, Mohit Sethi M <mohit.m.sethi=40ericsson....@dmarc.ietf.org><mailto:mohit.m.sethi=40ericsson....@dmarc.ietf.org> wrote: Hi Max, Tuomas can give you a definite answer. My understanding is that error 1001 should be sent by the server if the received identity does not follow the requirements of draft-aura-eap-noob. Besides, implementing the stricter checks of this draft is easier than validating the ABNF of RFC7542 (after which you would anyways need to verify compliance with this draft). And you are right. The absence of server-assigned realm in Figure 2 is probably an editorial oversight. However, I wouldn't call the optional server assigned realm as RESERVED_DOMAIN. If anything, I would call eap-noob.net as a reserved/special use domain. There are all manner of reasons not to use eap-noob.net. I think we talked to the IAB about this at some point and they were comfortable with something in .ARPA, but we’d need to reconfirm. This is a small matter that should be cleared up with a few email exchanges. Absolutely. Using something in .arpa makes perfect sense. But until that is allocated, implementations need a temporary placeholder. The current text in section 3.3.1 of the draft even says (https://tools.ietf.org/html/draft-aura-eap-noob-08#section-3.3.1): The default realm for the peer is "eap-noob.net" (.arpa domain TBA). --Mohit Eliot _______________________________________________ Emu mailing list Emu@ietf.org<mailto:Emu@ietf.org> https://www.ietf.org/mailman/listinfo/emu
_______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
