To:
"'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
From:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Date:
Wed, 21 Nov 2001 10:35:00 -0500
Sender:
owner-ietf-provreg@cafax.se
Subject:
FW: EPP - Voice field
Described below is the fix I intend to put into the contact mapping to ensure that telephone numbers can contain a full 15 characters per E.164. The issue is that the current definition: <pattern value="(\+[0-9]{1,3}\.[0-9]{1,12})?"/> allows only 12 characters in the local part of the number, but E.164 says that the local part can contain up to "15-n" digits, where "n" is the length of the country code. The fix preserves the "look" of telephone numbers used in earlier versions, but it increases the maximum length of the local part and ensures that the total length remains valid. Thanks to Ayesha Damaraju for bringing this to my attention. -Scott- -----Original Message----- From: Hollenbeck, Scott Sent: Wednesday, October 24, 2001 10:32 AM To: 'Damaraju, Ayesha' Subject: RE: EPP - Voice field > -----Original Message----- > From: Damaraju, Ayesha [mailto:ayesha.damaraju@NeuStar.com] > Sent: Wednesday, October 24, 2001 10:30 AM > To: 'Hollenbeck, Scott' > Subject: RE: EPP - Voice field > > > Scott, > > Will it be then - > with out period? > > We may change it internally for now. > > > <simpleType name="e164StringType"> > > <restriction base="normalizedString"> > > <pattern value="(\+[0-9]{1,15})?"/> > > </restriction> > > </simpleType> I'd do something just a little bit different to preserve whatever people might be doing with the period. Here's what I'd propose: <simpleType name="e164StringType"> <restriction base="normalizedString"> <pattern value="(\+[0-9]{1,3}\.[0-9]{1,14})?"/> <maxLength value="17"/> </restriction> </simpleType> This pattern doesn't change whatever data people might have already exchanged, but it does allow the national number part to be up to 14 digits without blowing the 15 digit (17 above to include the "+" and "." characters) limit. -Scott-