Re: Send-N draft: draft-bellis-enum-send-n-02 published

[email protected]
Newsgroups gmane.ietf.enum
Message-ID <OF07B9BA9D.4DAD0AE3-ON80257475.004F5C92-80257475.0050171C@nominet.org.uk>
Duane wrote:
> It gets 'broken' because send-n will interfere with wild card records
> because in most case the most specific record should take preference.

I still don't understand your objection.

If a specific record over-rides a wildcard containing a Send-N record, so 
what?!

That just means that the switch implementing Send-N will keep on asking 
for digits (one at a time) until the full number is found[*]

Can you provide an actual example zone showing how this doesn't work?

Ray

[*] Yes, I know looking up partial numbers breaks Section 2 of RFC3761. 
However IMHO that paragraph is unnecessarily restrictive because nothing 
ever actually breaks if that "rule" is broken.  This is unfortunately a 
necessary step if overlapped dialling is ever to work in I-ENUM.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.