Document: draft-cridland-acap-vendor-registry-01.txt
Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
Review Date: 2010-10-19
IETF LC End Date:
IESG Telechat date: (if known)

Summary: The document has issues that should be addressed before publication.

Major issues:

- I am surprised to see the reduction of characters to ASCII only. I don't 
know how this fits with the IETF Internationalization strategy for most 
protocols. Additionally, this issue touches me personally, as a 
Spanish citizen, where I would not be able to register strings containing 
certain characters due to the lack of their representation in ASCII.

So, this draft is precluding international names be registered with IANA. 
I think this is a major issue that should be addressed.

Minor issues:

- I think this document should update ACAP (RFC 2244). This should be 
visible in the front page, so that the RFC Editor records an update 
to RFC 2244.

- I think that the [ACAP] reference should be promoted to normative 
(moved from Section 7.2 to 7.1).

Nits/editorial comments:

- Section 3, write a formal reference to UTF-8 int he first sentence.

- Section 3.3, last sentence in second paragraph , make a formal reference to 
ANNOTATE.