Draft:  draft-ietf-enum-validation-arch-03.txt
Reviewer: Black_David@emc.com
Review Date: Tuesday 8/29/2006 2:19 AM CST
IETF LC Date: 8/30/2006

Summary: This draft is on the right track but has open issues,
described in the review.

The draft is well-written and primarily concerns procedures for
ENUM assignment validation.  It's close to ready for publication
as an RFC, but I found one open issue that needs attention:

The example in Figure 2 uses what appear to be real phone
numbers (or what could be real phone numbers) in Switzerland.
That's not a good idea - see Section 3, subsection 6 of:

	http://www.ietf.org/ID-Checklist.html

It's not clear to me whether the fictitious phone numbers described
in the ID-Checklist are sufficient for the examples required
in Figure 2.  If fictitious phone numbers in Switzerland are used,
please describe them as fictitious and please provide the IESG
with a reference showing that they are fictitious so that they
can be added to the Checklist's list of available fictitious
phone numbers.