There is a small chance that ISO might change this in the future, but as
long as there are some excluded/user assigned ISO code elements left I
too think letting the user assign the pseudo TLD(s) makes sense.
Even though I like the .ZZ idea :-)-O
el
On 2019-11-22 20:45 , Ted Lemon wrote:
> On N
On Nov 22, 2019, at 1:33 PM, David Conrad wrote:
> I don’t understand why one would need to pick ZZ (or any other user defined
> code) to mean by convention anything. It doesn’t hurt anything, I just don’t
> see the point.
>
> I would turn the question around:
>
> Why not simply have an RFC t
This whole discussion confuses me.
As Roy and Jaap have pointed out, ISO 3166 has indicated the user defined codes
won’t be allocated. They are for private use. Just as RFC 1918 has designated
10/8 for private use.
To me, this means any of the user defined ISO codes are fair game for internal
Man, sorry for the weird random capitalization, y’all. Autocorrect has a mind
of its own.
Also, what Matt said: perhaps we could approach consensus if those in favor of
the proposal would articulate their thoughts on why specifying a two-letter is
the best solution to (this, any) problem, the
I too find myself puzzled about trying to assign ZZ for this role. I
strongly prefer we stay far away from using two letter codes for anything
other than ISO 3166 assignment of country codes for ccTLDs. (I even think
we made a mistake in allowing two letter codes in Cyrillic and
Greek.) Postel's
Eberhard:
The principle I’m trying to articulate is that our relationship to ISO 3166 is
that of a standards body which has delegated to it.
ISO 3166, in turn, specifies that this code is (for now, and at their
authority) to be used by USERS for their purposes.
It’s my assertion that it’s b
On Fri, 22 Nov 2019 at 09:05, Roy Arends wrote:
>
>
> >
> > I read that to mean they are reserved for private use, and as mentioned
> above, any centralized/standardized use is going to conflict with that.
>
> No.
>
> No one is suggesting centralised use! The opposite. You can use it locally
> be
> On 22 Nov 2019, at 21:15, Matthew Pounsett wrote:
>
> On Fri, 22 Nov 2019 at 05:16, Dr Eberhard W Lisse wrote:
>
> If users need code elements to represent country names not included
> in this part of ISO 3166, the series of letters AA, QM to QZ, XA to
> XZ,
> On 22 Nov 2019, at 16:26, Bill Woodcock wrote:
>
>
>
>> On Nov 22, 2019, at 12:20 AM, Shane Kerr wrote:
>> "User-assigned codes - If users need code elements to represent country
>> names not included in ISO 3166-1, the series of letters AA, QM to QZ, XA to
>> XZ, and ZZ, and the series A
> On 22 Nov 2019, at 16:26, Bill Woodcock wrote:
>
>
>
>> On Nov 22, 2019, at 12:20 AM, Shane Kerr wrote:
>> "User-assigned codes - If users need code elements to represent country
>> names not included in ISO 3166-1, the series of letters AA, QM to QZ, XA to
>> XZ, and ZZ, and the series A
On Fri, 22 Nov 2019 at 05:16, Dr Eberhard W Lisse wrote:
>
> If users need code elements to represent country names not included
> in this part of ISO 3166, the series of letters AA, QM to QZ, XA to
> XZ, and ZZ [...] are available.
>
> I read that to mean that a .ZZ (or r
Bill,
ISO has new draft out as part of their regular maintenance cycle which
states
[...] In addition exactly 42 alpha-2 code elements are not used in
the ISO 3166, AA, QM to QZ, XA to XZ, ZZ. This rule may change in
the future. [...]
and then references this
I
Erwin Lansing writes:
>
> Beware of assumptions. I would never have imagined in my wildest
> dreams for St. Maarten to be assigned SX.
It was on request of Dutch Sint Maarten. The argued that they where know for the
airport code for the well-known Princess Juliana International Airport But t
Bill Woodcock writes:
> Again, this is an argument from principle rather than an argument based
> on the specific case at hand. I just think that we have a
> well-established precedent that all two-letter TLDs are derived from ISO
> 3166 Alpha-2, and it's bad form to cross back over and sta
Shane Kerr writes:
> Hm... this is an interesting point.
>
> I just checked the ISO 3166 glossary:
> https://www.iso.org/glossary-for-iso-3166.html
>
> And it says:
>
> "User-assigned codes - If users need code elements to represent country
> names not included in ISO 3166-1, the series
On 22 Nov 2019, at 10:26, Bill Woodcock wrote:
Again, this is an argument from principle rather than an argument
based on the specific case at hand. I just think that we have a
well-established precedent that all two-letter TLDs are derived from
ISO 3166 Alpha-2, and it’s bad form to cross ba
On Friday, 22 November 2019 08:26:35 UTC Bill Woodcock wrote:
> ...
>
> Again, this is an argument from principle rather than an argument based on
> the specific case at hand. I just think that we have a well-established
> precedent that all two-letter TLDs are derived from ISO 3166 Alpha-2, and
> -Original Message-
> From: DNSOP On Behalf Of Bill Woodcock
> Sent: Friday, November 22, 2019 9:27
> To: Shane Kerr
> Cc: dnsop@ietf.org
> Subject: Re: [DNSOP] On .ZZ
>
>
>
> > On Nov 22, 2019, at 12:20 AM, Shane Kerr
> wrote:
> >
> > So the intention of the ISO at least is that t
> On Nov 22, 2019, at 12:20 AM, Shane Kerr wrote:
> "User-assigned codes - If users need code elements to represent country names
> not included in ISO 3166-1, the series of letters AA, QM to QZ, XA to XZ, and
> ZZ, and the series AAA to AAZ, QMA to QZZ, XAA to XZZ, and ZZA to ZZZ
> respectiv
Bill and all,
On 21/11/2019 16.25, Bill Woodcock wrote:
On Nov 21, 2019, at 12:18 AM, Brian Dickson
wrote:
IMHO, there is *no* reason not to advance .zz
For the record, I think it’s a really bad idea to start re-purposing the ISO
user-assigned codes. Just as bad an idea as if they starte
20 matches
Mail list logo
