Re: [DNSOP] On .ZZ

2019-11-24 Thread Tim Wicinski
I can not speak for all DNSOP chairs, but this chair would prefer to not repeat all those "fun" RFC6761 discussions, as Mr. Conrad mentioned. If the working group is missing a "fun" type of discussion, I am sure the chairs can come up something suitably entertaining. Tim On Fri, Nov 22, 2019 a

Re: [DNSOP] On .ZZ

2019-11-22 Thread Dr Eberhard W Lisse
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Ted Lemon
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread David Conrad
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Bill Woodcock
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Steve Crocker
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Bill Woodcock
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Matthew Pounsett
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Roy Arends
> 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,

Re: [DNSOP] On .ZZ

2019-11-22 Thread Roy Arends
> 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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Roy Arends
> 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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Matthew Pounsett
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Dr Eberhard W Lisse
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Jaap Akkerhuis
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Jaap Akkerhuis
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Jaap Akkerhuis
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Nishal Goburdhan
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Paul Vixie
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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Erwin Lansing
> -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: > > > &

Re: [DNSOP] On .ZZ

2019-11-22 Thread Bill Woodcock
> 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

Re: [DNSOP] On .ZZ

2019-11-22 Thread Shane Kerr
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

Re: [DNSOP] On .ZZ

2019-11-21 Thread Bill Woodcock
> 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 started re-purposing 1918 space.

Re: [DNSOP] On .ZZ

2019-11-21 Thread Dr Eberhard W Lisse
I agree with Jaap (about the principle). I think it is safe to assume that there will not be a ccTLD corresponding to an alpha-2 code element that does not form part of 3161-1 ie is available as 'User Assigned'. I personally find an alpha-3 code element, ie .ZZZ, less confusing to the casual user

Re: [DNSOP] On .ZZ

2019-11-21 Thread Brian Dickson
On Thu, Nov 21, 2019 at 3:57 PM Vladimír Čunát wrote: > On 11/21/19 8:26 AM, Paul Wouters wrote: > > for example if ICANN delegates .zzz there will be interesting typo > attacks possible in this weird private space > > In this respect .zz is at least better than .xx which was among the > suggesti

Re: [DNSOP] On .ZZ

2019-11-20 Thread Vladimír Čunát
On 11/21/19 8:26 AM, Paul Wouters wrote: > for example if ICANN delegates .zzz there will be interesting typo attacks > possible in this weird private space In this respect .zz is at least better than .xx which was among the suggestions. > Finally, I agree. People want something semantic and mor

Re: [DNSOP] On .ZZ

2019-11-20 Thread Jaap Akkerhuis
Paul Wouters writes: > > > > > On Nov 21, 2019, at 15:18, Alexander Mayrhofer > > wrote: > > > > > > ..ZZ would remind me of long beards and loud motorcycles for the rest > > of my life.. https://de.wikipedia.org/wiki/ZZ_Top > > English speaking people can’t even agree on how to p

Re: [DNSOP] On .ZZ

2019-11-20 Thread Paul Wouters
> On Nov 21, 2019, at 15:18, Alexander Mayrhofer > wrote: > > > ..ZZ would remind me of long beards and loud motorcycles for the rest > of my life.. https://de.wikipedia.org/wiki/ZZ_Top English speaking people can’t even agree on how to pronounce this name.. Having an undelegated .zz is

Re: [DNSOP] On .ZZ

2019-11-20 Thread Jared Mauch
..ZZ makes as much sense as anything else to be honest, virtually anything is going to conflict with some acronym or name out there. - Jared > On Nov 21, 2019, at 2:18 AM, Alexander Mayrhofer > wrote: > > Setting the basic issue aside (I'm still a bit torn) I agree with > Warren that it would

[DNSOP] On .ZZ

2019-11-20 Thread Alexander Mayrhofer
Setting the basic issue aside (I'm still a bit torn) I agree with Warren that it would need a string that has a meaning. ..ZZ would remind me of long beards and loud motorcycles for the rest of my life.. https://de.wikipedia.org/wiki/ZZ_Top best, Alex