Re: NAIbis spec revision 03

[Nagi Reddy Jonnala <Nagi_Reddy.Jonnala@alcatel.be>]

Jari,

See the snips from formal syntax (Infact they are there in the oiginal
RFC as well).

char        =/ "\" x
x           =  %x00-7F ; all 128 ASCII characters, no exception

I suppose that you would want to allow the user name like
"myusername\x0\x1". I'm curious to know  in which cases do we make use
of these combo characters.

Doesn't it look consistent if you make the syntax of x to take all 256
includes ASCII and the remaining UTF-8 characters ( i.e., x = %x00-FF)

regards
Nagi.


Jari Arkko wrote:

> Hi,
>
> Working group last call completed on this document some
> time ago. I have now put a modified draft revision and diffs
> at
>
>    http://www.arkko.com/publications/nai/naibis.txt
>    http://www.arkko.com/publications/nai/naibisdiff.html
>
> The modifications include a few editorial improvements
> on the ABNF that Pasi suggested, a couple of other
> editorial things, and the removal of a claim that
> the bis version '!' puts stricter requirements on the
> parts preceding the '!' sign than in RFC 2486.
>
> I think the conclusion from the IKEv2 discussion is
> that there's a couple of promising alternatives for
> transporting i18n or privacy enhanced NAIs over IKEv2.
> But it seems that we should not do them in the NAIbis
> spec. (But I volunteer to draft a spec for that in
> some other context.)
>
> If I missed anything, scream now. I will submit this
> to the I-D directories in a couple of days.
>
> --Jari
>
> --
> 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/>


--
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/>