RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0

Bernie Hoeneisen <[email protected]>
Newsgroups gmane.ietf.enum,gmane.ietf.provreg
Message-ID <Pine.LNX.4.61.0409281316310.3503@machb>
Hi Scott!

Thanks for your feedback!

On Mon, 27 Sep 2004, Hollenbeck, Scott wrote:

> OK, I had a chance to take a closer look.  I noticed that you're using a
> 31-character token for the E.164 number.  Why is that?  An E.164 number can
> contain no more than 15 digits per E.164, so why allow a maximum of 31?  For
> what it's worth I used a type like this in the EPP contact mapping:

The idea behind this was to leave it a Registry policy issue (or up to the 
validation method documentation), what format to use, in order to keep it 
as generic as possible. This would allow over-dialing, and characters 
such as "-", "(", ")" as seperators. Furthermore one could 
describe number ranges, e.g. "+41-44-26815xx", with this format.
I do not have a strong opinion on which format to use for this.

> Also, throughout the document s/März/March/

Ouuppps...!
This is due to a bug in the "xml2rfc" package. It used my locale settings, 
i.e. the environment variable "LC_TIME=de_CH" although any output 
documents of the xml2rfc tool are in English. I have submitted a Bug 
Report and informed the Debian maintainer about this issue. I even got 
immediately a patch!
However, this will be correct in the next revision.


cheers,
  Bernie

_______________________________________________
enum mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/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.