ietf
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

RE: [saag] i18n requirements (was: Re: NF* (Re: PKCS#11 URI slot attributes & last call))

2015-01-12 09:07:52
from [Salz, Rich] [Permanent Link] 
I'd go even further than that and just mandate MUST ASCII. 


I don't know if the IETF is "allowed" to do that any more, but +1 for the 
reasons you list.

--  
Principal Security Engineer, Akamai Technologies
IM: rsalz(_at_)jabber(_dot_)me Twitter: RichSalz
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  RE: Last Call: <draft-ietf-tls-downgrade-scsv-03.txt> (TLS Fallback Signaling Cipher Suite Value (SCSV) for Preventing Protocol Downgrade Attacks) to Proposed Standard, Salz, Rich
Next by Date:  RE: [saag] i18n requirements (was: Re: NF* (Re: PKCS#11 URI slot attributes & last call)), Salz, Rich
Previous by Thread:  Re: [saag] i18n requirements (was: Re: NF* (Re: PKCS#11 URI slot attributes & last call)), Jan Pechanec
Next by Thread:  Re: [saag] i18n requirements (was: Re: NF* (Re: PKCS#11 URI slot attributes & last call)), Nico Williams
Indexes:  [Date] [Thread] [Top] [All Lists]