[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Issue 102 in ieee802-01



Pasi,

Would the following 'tunnel-id' syntax definition cover your concerns?

   tunnel-id      =  DQUOTE 1*(TEXTDATA /("%" 2HEXDIG)) DQUOTE

Thanks,
MS 

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org 
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of 
> Pasi.Eronen@nokia.com
> Sent: Wednesday, January 25, 2006 2:52 AM
> To: radiusext@ops.ietf.org
> Subject: Issue 102 in ieee802-01
> 
> Hi,
> 
> It looks like version -01 of the IEEE attributes draft solved 
> my of my comments, but one resolution looks slightly buggy:
> 
> The ABNF includes two different ways to quoting "strange" 
> octets in tunnel-id (backslashes and percent-hex-hex), but 
> the text doesn't quite match the ABNF.
> 
> Also, I think we don't need two different quoting mechanisms; 
> the percent-hex-hex notation makes the backslashes redundant 
> (and is IMHO easier to implement in a way that really works 
> with arbitrary octets, such as LF (the rule delimeter!) and NUL).
> 
> Best regards,
> Pasi
> 
> --
> 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/>