Re: [stir] stir-06: Reality check on numbers (6.1.1)

The international E.164 number can only be decimal digits.

That therefore means that the country code, the national destination code, and the subscriber number, all of which are component parts of an international E.164 number, can only be decimal digits.

That would imply that the only part that could contain such a character is a prefix to an E.164 number, or if the number is not an E.164 number, such as a private dial plan.

I'd note that RFC 3966 states: "All phone numbers MUST use the global form unless they cannot be represented as such."

I suspect that "*", "#", etc have more usage in numbers that are dialstrings rather than telephone numbers.

Regards

Keith

-----Original Message-----
From: stir [mailto:stir-bounces@ietf.org] On Behalf Of Paul Kyzivat
Sent: 11 December 2015 15:58
To: stir@ietf.org
Subject: Re: [stir] stir-06: Reality check on numbers (6.1.1)

On 12/10/15 9:15 PM, Eric Burger wrote:
> Section 6.1.1 on Canonicalization states:
>        Once an implementation has identified a telephone number, it must
>        construct a number string.  Implementations MUST drop any leading
>        +'s, any internal dashes, parentheses or other non-numeric
>        characters, excepting only the leading "#" or "*" keys used in
>        some special service numbers (typically, these will appear only in
>        the To header field value).  This MUST result in an ASCII string
>        limited to "#", "*" and digits without whitespace or visual
>        separators.
>
> Survey time: does pound or star  EVER appear in a From field? E.164 does not allow it.

pound isn't allowed at all in a sip uri, except via escaping.

There is no mention of escaping (or unescaping) in the text. If there is the possibility of pound coming through then that is needed.

Also, * and # (as well as A-D) are never valid in global numbers, but are valid within local numbers not just first, but anywhere in the number. So why is there special treatment for a *leading* star or pound?

ISTM that canonicalization of dialstrings that represent local rather than global numbers is fraught with difficulty.

	Thanks,
	Paul

_______________________________________________
stir mailing list
stir@ietf.org
https://www.ietf.org/mailman/listinfo/stir