Draft: draft-ietf-enum-void-01.txt
Review: Suzanne Woolf
Date: 25 maj 2005 

draft: draft-ietf-enum-void-01.txt
status: LC for Proposed Standard


Summary: I've read the IESG comments and have only a couple of minor
ones to add. I respect the pending comments from IESG members but see
no additional grounds for not advancing this draft.

1) Scott Hollenbeck already noted that NXDOMAIN is an
implementation-specific name for RCODE 3 as defined in 1034/1035,
although it may have been "inadvertently standardized" by being
included in a later standards track DNS specification. In addition,
the RR examples included are implementation-specific (I think $ORIGIN
is a BIND-ism too).

2) I'm not sure the name VOID is ideal, it doesn't distinguish between
an invalid/unassignable number of some kind and an unused/unassigned
number. But I'm happy to assume that the ENUM WG members would know if
they needed such a thing.

3) Since there's no obligation on a carrier to define this NAPTR for a
node, I'm a little less concerned about security side-effects than I
might be, but I do suggest considering Margaret's comment about
exposing additional data by filling in "voids" in a delegation.