[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Enum] I-D Action: New draft - draft-bellis-enum-send-n-00



> -----Original Message-----
> From: Brian Rosen [mailto:br at brianrosen.net]
>
> The question is then where to put it.

Not really, or rather it won't be enough, if it's not put into the NAPTR records some way.  For closed environments that may well be enough, but for the public ENUM it would be really hard to see how any random UA is to know to get which file for which country or have the latest copy at all times, etc.  So I think they would query an UNUSED or non-existant entry a lot regardless.  One way to do it is using an UNUSED http url, to point to a source for the data, instead of a data url.  But I don't see why it couldn't (maybe optionally) be a data url, if it were sufficiently defined.


> I would point out that the SOURCE of the data is the number plan
> administrator in a country, which is distinctly different from the
> operator
> of the public enum tree, if there is one.

Yes, but that's not the case for private use, and even for public use does it prevent the operator of the public enum tree from being able to supply such "hints", or the numbering plan admin from coordinating such with the operator?  IANAE.


> I'd rather see a mechanism that the number plan administrator could use
> directly, and I'd like to avoid the delegation issues of public enum.

ESPP? ;)


> It's really just a file.  Couldn't we just define an XML data structure
> for
> that file and figure out a way to publish it?

There are pros/cons to doing this in files.  There is no doubt that it would be far more efficient (messaging-wise) for each UA or proxy on the planet to have a numbering plan template, for the country it makes lots of calls to, but my guess is it would be fairly impractical and unnecessary for each to have those plans for all countries, and impractical for the files to be available to all UAs/proxies.  DNS has the rather nice property of lightweight just-in-time delivery with a limited scope to the node record being queried for.

-hadriel
_______________________________________________
enum mailing list
enum at ietf.org
https://www.ietf.org/mailman/listinfo/enum