rfc2486bis
stefaan.de_cnodder@alcatel.be Thu, 18 March 2004 15:51 UTC
Envelope-to: radiusext-data@psg.com
Delivery-date: Thu, 18 Mar 2004 15:52:24 +0000
Message-ID: <4059C57E.59C1C7F3@alcatel.be>
Date: Thu, 18 Mar 2004 16:51:26 +0100
From: stefaan.de_cnodder@alcatel.be
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: rfc2486bis
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Hi, I have a few small questions/comments on draft-arkko-roamops-rfc2486bis-00: 1) examples in section 2.8: why is @howard.edu an invalid NAI? And why has eng%nancy@bigu.edu been removed from the list of valid NAIs compared to RFC2486? I believe it is still valid, or should it be put in the list of invalid NAIs? 2) Would it not be better to define the nai in 2.1 as follows: nai = [realm "!"] ( <....> ) with <....> the current nai defintion. This to make the explanation in section 2.7 more formal. 3) typo: a quotation mark too much at the end in the nai definition in 2.1. regards, Stefaan -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/radiusext/>
- Re: rfc2486bis Bernard Aboba
- rfc2486bis stefaan.de_cnodder
- RE: rfc2486bis Pasi.Eronen
- RE: rfc2486bis Blair T. Bullock
- Re: rfc2486bis Jari Arkko
- RE: rfc2486bis Bernard Aboba
- Re: rfc2486bis Jari Arkko
- Re: rfc2486bis Bernard Aboba
- RE: rfc2486bis Wijnen, Bert (Bert)
- Re: rfc2486bis stefaan.de_cnodder
- Re: rfc2486bis Nagi
- Re: rfc2486bis Jari Arkko