Thomas, No hats on.
I assume that if the Line ID is going to be opaque we don't need to define how to encode strings in it. Suresh's email wasn't clear on that, if I understood it correctly. I still would like it to be an opaque field as that keeps it aligned with the DHCP option. Bob On Nov 30, 2011, at 5:33 PM, Thomas Narten wrote: > Well, if you want the line ID field to hold a string, to do the right > thing, one probably needs to: > > 1) make the field be a UTF-8 string > > 2) have the string contain normalized unicode, so that the "string" > entered on one device correctly matches the "string" entered on the > server (which won't always happen if unnormalized unicode strings are > allowed). > > I.e., the kind of stuff that the precis WG does. :) > > Thomas > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
