On 10/24/06, Anand Kumria <[EMAIL PROTECTED]> wrote:
On Mon, 23 Oct 2006 18:45:23 -0400, Luis R. Rodriguez wrote:

> iso3166-1
>
> ISO 3166-1, as part of the ISO 3166 standard, provides codes for the names
> of countries and dependent areas. It was first published in 1974 by
> the International Organization for Standardization (ISO) and defines three
> different codes for each area:

[snip]

+       r |= iso3166_1_add(887, "YE", "YEM",
+               "Yemen");
+       r |= iso3166_1_add(891, "CS", "SCG",
+               "Serbia and Montenegro");
+       r |= iso3166_1_add(894, "ZM", "ZMB",
+               "Zambia");


According to the ISO, at:

<http://www.iso.org/iso/en/commcentre/pressreleases/2006/Ref1031.html>

and

<http://www.iso.org/iso/en/prods-services/iso3166ma/03updates-on-iso-3166/nlv12-div.html>

Serbia and Montenegro have been allocated new codes,
RS and ME respectively.

Will update accordingly, thanks.

Is this ISO3166 stuff supposed to track the standard?

Yes.

If so, what happens when a country splits or two join together?

We update it.

Will that require lock-step updates to user-space, or will it be insulated
by this changes?

I didn't intend on having a userspace update this as I figured these
updates are rare and could just go with a new kernel release, and as
this would currently only be used for regulatory domain control it
should't have a negative impact. If there are more modules which can
make use of this then perhaps we can consider a more robust interface.

 Luis
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to