Document: draft-klensin-unicode-escapes-06.txt Reviewer: Spencer Dawkins Review Date: 2007-11-08 IETF LC End Date: 2007-11-15 IESG Telechat date: Summary: This document is ready for publication as a BCP, with one question and one comment for the sponsoring AD. I should also mention that the document is very clear and well-written. Comments: This document uses a fair amount of SHOULD/SHOULD NOT language without a lot of explanation about why the SHOULDs are not MUSTs. I'm not sure what's appropriate for an APPS-area BCP, but I usually ask about SHOULD/SHOULD NOT without guidance. This is a BCP that recommends two different encoding escapes. If the SHOULDs are something like "MUST unless you're using the other method", is 2119 language even needed?