On 26 Aug 2008, at 03:56, Matvey Teplov wrote:
> Some time ago there was a discussion over the origination tagging.
> It took me a while to get through the draft publishing stages, but
> finally it is in. Can you please review the document and send me
> your comments. Draft is located at:
> http://www.ietf.org/internet-drafts/draft-teplov-grow-rfc4384-bis-00.txt
Section 3.3:
>> - Country - three digits of E.164 country code, e.g.: USA (001),
>> Russia (007), UK (044), NL (031), PA (501). Countries should be
>> linked to the regions in according to the scheme for geographic sub-
>> regions used by the United Nations. To prevent misunderstanding no
>> codes from this documents are used, but relations between the
>> region and the country
While in some cases E.164 "country codes" do, indeed, map
appropriately to a country, there are exceptions. The NANPA region is
an obvious one ("001" is not "USA" -- it's a region that incorporates
several countries of which the USA is just one).
> - State - code defined by the local internet authorities if needed
In the general case there is no such authority, surely.
> - City - three digits of intra-county city dialling code with the
> padded to three leading zeros, e.g.: Amsterdam (020), Moscow (495),
> Washington DC (202). If there is more than one code that is used
> then local internet authorities should standardize such.
So, there's an assumption that a dial plan in a particular region
works similarly to that in (say) the USA, and that the code for a city
will not be longer than three digits?
What happens when a city dialling code is reassigned, as has happened
in the UK several times over the last couple of decades?
What happens when two cities use the same dialling code? There are
half a dozen sizeable towns in south-western Ontario that all use the
area code (NANPA NPA) 519.
What happens when a city is assigned a dialling code overlay? 519 is
overlaid with 226. Which to use?
I realise there's no specific need for the linkage between location
and number to be accurate (in the sense that nobody is going to be
unable to call an ambulance simply because a route is tagged
confusingly) but as a mechanism of convenience it leaves a lot to be
desired. Linking "location" encoding to the telephone numbering system
is barely useful today, and will become less and less useful (and more
and more confusing) as time goes on.
I'll note that ISO 3166-1 numeric already specifies a three-digit
numerical system for countries ("economies", if you're sensitive to
Taiwan's status). ISO 3166 is already tied in other contexts to
Internet registries, and might be a more palatable dependency.
Joe
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
