Hi Sam,
My apologies to you and to the working group for my seriously delayed
processing of your feedback. I'll work to reply to all threads shortly.
Comments inline.
On 5/16/16 3:52 PM, Sam Whited wrote:
Hi Peter et al.
A few quick notes regarding your draft to replace RFC 7700:
* Nit: §1.1 ¶3 uses the term "display name" several times, but the
document otherwise uses the term "nickname"
Primarily that's because RFC 5322 calls it a display name (e.g., in the
string "Sam Whited <[email protected]>" the substring "Sam Whited" is a
display-name, but it's not necessarily what we'd typically refer to as a
nickname).
* §2.1: "May any instances of non-ASCII space be mapped…" sounds odd,
should this just say "Instances of non-ASCII space should be mapped…"
Typo: s/May/Map/
* §2.2 Specifies that UTF-8 MUST be used as the encoding; do we really
want to limit this to UTF-8 only? Is this for comparison purposes?
Then again, 99.99% of the time UTF-8 is what you should be using
anyways, so I'm not sure that it matters.
UTF-8 is your friend, and everything in PRECIS is UTF-8.
* §2.3: "Normalization Rule" is listed twice for enforcement
The second bullet point should be "Case Mapping Rule".
Thanks!
Peter
_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis
