Am 16.10.2013 00:52, schrieb Peter Saint-Andre:
> On 10/15/13 4:26 PM, [email protected] wrote:
>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-precis-framework
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-precis-framework-10
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-precis-framework-10
>
> Reviews of -10 or the diff would be helpful. I plan to check them both
> to make sure that I've accurately addressed all of the last call feedback.
>
> Thanks!
>
> Peter
>
I've had a quick look at the diff, and some areas I felt I should look
at again. I'm generally very happy about the outcome. Thank you for your
hard work. Some minor comments:
Sections 3.2.2 and 3.3.2 say «Certain characters from the Exceptions
("F")». That's a bit awkward as a reader. A forward reference to section
7.6, noting they are explicitly listed there would help.
In Section 4.1.3 about case mapping we currently have:
«In general, the combination of case preservation and case-insensitive
comparison of internationalized strings is NOT RECOMMENDED; instead,
application protocols SHOULD either (a) not preserve case but perform
case-insensitive comparison or (b) preserve case but perform
case-sensitive comparison.»
I wonder what the rational for this is? Both SASLprep-bis and Nicknames
seem to want case-preservation, but case-insensitive comparison. I may
be mistaken though.
In Section 10.5 "Visually Similar Characters" I'd suggest a reference to
UTS #39, describing confusable detection and mixed-script detection.
Regards,
Florian
_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis
