1 / 3

StringPrep/SASLPrep/… update IETF 76 – Hiroshima November, 2009

StringPrep/SASLPrep/… update IETF 76 – Hiroshima November, 2009. Alexey Melnikov alexey.melnikov@isode.com From email by Nico Williams and Joe Hildebrand. Issues/Possible requirements. Independent of a particular version of Unicode

oprah
Download Presentation

StringPrep/SASLPrep/… update IETF 76 – Hiroshima November, 2009

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. StringPrep/SASLPrep/… updateIETF 76 – HiroshimaNovember, 2009 Alexey Melnikov alexey.melnikov@isode.com From email by Nico Williams and Joe Hildebrand

  2. Issues/Possible requirements • Independent of a particular version of Unicode • Algorithm described using Unicode properties + [possibly] some small set of exceptions • Failing that, a mechanism toupdate to new Unicode versions with a relatively small amount of standardsand implementation work. Or at least update to a more modern version of Unicode.

  3. Issues/Possible requirements • Backward compatibility with RFC 4013/RFC 3454 ? • NFKC? Move to NFC or NFD? • Multiple normalization profiles (possibly negotiable) ??? • Query strings should be un-normalized ? • Comparisons to storage strings should be normalization-insensitive ?

More Related