On Thu, 2009-09-10 at 12:23 -0400, J. Bruce Fields wrote: > From a quick skim of http://www.ietf.org/rfc/rfc3490.txt, it appears to > me that protocols (at the very least, any preexisting protocols) are all > expected to use the ascii representation on the wire, and that the > translation to unicode is meant by use for applications. > > So in our case we'd continue to expect ascii domain names on the wire, > and I believe that's also what we should store in any database. But if > someone were to write a gui administrative interface to that data, for > example, they might choose to use idna for display. Right. There should be no need to translate anything. Just store as is and use as is... Trond -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
