-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/5/12 10:14 PM, Takahiro Nemoto wrote: > Dear Peter-san and all, > > Thank you for introducing our I-D. Please read and give your > comments/suggestions.
First, thank you for working on this document. I agree with you that "the file describing derived property value table for precis should be generated". It is also good to know that you have worked on an implementation that generates the tables. I am also working on an implementation (unfortunately I did not have time to finish it before IETF 84, but I plan to do that in August) and would like to "compare notes" with you. I recognize that the tables in draft-ietf-precis-framework are quite likely incorrect in some places since I created them by hand, so I will work to make more accurate tables next month. You mention the need to do string validity checking, for example to make sure that string length is non-zero. Do you think that is a PRECIS check or a check at the application layer? I've always thought this is something that the application would do, not PRECIS. As to special mappings like "Map to SPACE" and "Map to Nothing", it seems to me that in a post-stringprep system we can handle those by more carefully defining the string classes. You make a good point about the order of processing (normalization then validity in IDNA2008 vs. validity then normalization in SASLprep-bis). It does seem preferable to have a consistent order. Let's make sure we have discussion about this at the meeting two weeks from now. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAEhWQACgkQNL8k5A2w/vx9PACg9JzuOBZexL7KUVuGymn2JPWx puoAmwW1Sr6RNR1TXpExT3PHx4NEw5mr =SORW -----END PGP SIGNATURE----- _______________________________________________ precis mailing list [email protected] https://www.ietf.org/mailman/listinfo/precis
