Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
Hi, [Employed by ISOC, speaking for self] Speaking as usual only for myself, it seems to me that if there were actual demand for a WG that would actually W as a G on actual extensions, it would be pretty trivial to charter it. What would be bad IMO is a “working group” that functioned instead as DNSGATE. But I, of course, don’t have much to contribute one way or the other. Best regards, A — Andrew Sullivan Please excuse my clumbsy thums > On Jul 31, 2021, at 11:48, Ray Bellis wrote: > > > >> On 30/07/2021 19:29, Paul Wouters wrote: >> >> We are seeing the WG dropping actual protocol work because of these >> discussions. > If only we had a working group for discussing DNS Extensions... > > Ray > > ___ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
> On 30 Jul 2021, at 23:03, Rob Wilton (rwilton) wrote: > > Hi Roy, WG, Hi Rob, > Roy, just for clarity, am I right to presume that the status of the document > that you propose would purely be informational? Correct. > It is, of course, up to the WG to decide what to do with this document, but I > would like to make a couple of comments that may help the WG. > > I would like to somewhat echo a point that was made in DNSOP yesterday when > this draft was being discussed, in that I don't believe that IETF should > publish a document that either directly or indirectly undermines ISO TC46's > ownership or authority over the ISO3166 code points. I believe that this > concern is likely shared by other ADs. That was never the intent. When you read the document, it actually underwrites ISO TC46’s ownership or authority over the ISO3166 code points. Especially the part that the User Assigned code points are assigned to the user of the standard…. > Hence, if the WG decides to progress this document with the proposed > structure below, then I'm not convinced that just documenting that these code > points exist and that some people use them would be sufficient. Even though these code points exist and folks are (rightly, IMHO) using, for instance, .QY and the likes. > Given the informal liaison feedback that was received, I think the liaison feedback is not on par with the questions asked by the chairs of the IETF and IAB. IMHO it has actively undermined it. > I think that the IETF would likely need to adopt stronger wording that > proactively recommends that these country codes are not used for private > networks, and highlights the potential problems with doing so. How is that not asserting ownership or authority over the ISO code points? Roy > > Regards, > Rob > // Ops AD > > > > -Original Message- > From: DNSOP On Behalf Of Roy Arends > Sent: 30 July 2021 19:21 > To: dnsop > Subject: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld > > Dear WG > > About 40 years ago, give or take, when Jon Postel planned to use the ISO3166 > two character code elements as top level domains representing country names, > ISO's TC46 secretariat was contacted (as was requested to users of the > ISO3166 standard at the time) and he was told that the standard should not be > used for DNS, as the future was in X.500. (Postel wasn’t swayed by the > argument, and did what we now refer to as permission-less innovation). > > Recently, the ISO was contacted again, and subsequently the WG was again told > that the standard wasn’t to be used in this way. It seems that a handful of > folks are swayed by the argument and want to use this as guidance for the > future of draft-ietf-dnsop-private-tld. > > Early on, Joe Abley proposed a way forward that I held off initially: > Recognise that User Assigned 3166 code elements are used in various ways, > including private networks, that these elements have not been delegated and > are known to be used to anchor private namespaces. Do not recommend, promote > or reserve anything, no registries. Document potential future pitfalls for > using these codes for private namespaces and empower readers to make their > own decisions. > > I now see that with the current status quo, this might a way forward that > both sides of the argument might come together on. Essentially, instead of > making the pond safe, we’ll have a warning sign that using the pond is at > their own risk. > > I hope the WG can come together on this as a way forward. > > Warmly, > > Roy > > > > ___ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
On 30/07/2021 19:29, Paul Wouters wrote: > We are seeing the WG dropping actual protocol work because of these > discussions. If only we had a working group for discussing DNS Extensions... Ray ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
Hi Paul, Working Group, On 30/07/2021 20:43, Paul Wouters wrote: So was draft-ietf-dnsop-delegation-only until it was killed yesterday due to lack of time because we had to spend it on political discussions with ISO liaisons. To be clear, the discussion of the poll and priorities was informative and no decisions have been made about dropping WG documents yet. Your argument that the document got delayed due to other more pressing drafts is acknowledged. We also hold off the suggestion to raise hands for alt-tld draft in a similar way. The poll helped the discussion, but is only part of the discussion. For the individual drafts, the DNSOP chairs will contact the authors and discuss the way forward with the WG. Best regards, -- Benno ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
It appears that Joe Abley said: >Hi Paul, > >On Jul 30, 2021, at 14:55, Paul Wouters wrote: > >> We literally had a survey to ask us “what should we kill because we don’t >> have enough time” > >I don't think that's exactly the question I saw, but perhaps I misremember. > >For what it's worth (and as you know from our conversations about it on this >list) I disliked your delegation-only draft on its merits and not because of >lack of time. Same here. I think the WG had plenty of reasons not to advance it. R's, John ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
Hi Roy, WG, Roy, just for clarity, am I right to presume that the status of the document that you propose would purely be informational? It is, of course, up to the WG to decide what to do with this document, but I would like to make a couple of comments that may help the WG. I would like to somewhat echo a point that was made in DNSOP yesterday when this draft was being discussed, in that I don't believe that IETF should publish a document that either directly or indirectly undermines ISO TC46's ownership or authority over the ISO3166 code points. I believe that this concern is likely shared by other ADs. Hence, if the WG decides to progress this document with the proposed structure below, then I'm not convinced that just documenting that these code points exist and that some people use them would be sufficient. Given the informal liaison feedback that was received, I think that the IETF would likely need to adopt stronger wording that proactively recommends that these country codes are not used for private networks, and highlights the potential problems with doing so. Regards, Rob // Ops AD -Original Message- From: DNSOP On Behalf Of Roy Arends Sent: 30 July 2021 19:21 To: dnsop Subject: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld Dear WG About 40 years ago, give or take, when Jon Postel planned to use the ISO3166 two character code elements as top level domains representing country names, ISO's TC46 secretariat was contacted (as was requested to users of the ISO3166 standard at the time) and he was told that the standard should not be used for DNS, as the future was in X.500. (Postel wasn’t swayed by the argument, and did what we now refer to as permission-less innovation). Recently, the ISO was contacted again, and subsequently the WG was again told that the standard wasn’t to be used in this way. It seems that a handful of folks are swayed by the argument and want to use this as guidance for the future of draft-ietf-dnsop-private-tld. Early on, Joe Abley proposed a way forward that I held off initially: Recognise that User Assigned 3166 code elements are used in various ways, including private networks, that these elements have not been delegated and are known to be used to anchor private namespaces. Do not recommend, promote or reserve anything, no registries. Document potential future pitfalls for using these codes for private namespaces and empower readers to make their own decisions. I now see that with the current status quo, this might a way forward that both sides of the argument might come together on. Essentially, instead of making the pond safe, we’ll have a warning sign that using the pond is at their own risk. I hope the WG can come together on this as a way forward. Warmly, Roy ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
Hi Paul, On Jul 30, 2021, at 14:55, Paul Wouters wrote: > We literally had a survey to ask us “what should we kill because we don’t > have enough time” I don't think that's exactly the question I saw, but perhaps I misremember. For what it's worth (and as you know from our conversations about it on this list) I disliked your delegation-only draft on its merits and not because of lack of time. If the working group expresses similar sentiments about the 3166 private use codepoint draft I will be similarly disappointed, because I think there's non-zero value in documenting where we got to and I don't think it will be much work to do so. But life will go on. It's a shame we have to have these conversations exclusively over email instead of in a bar. I'm buying when we get to travel again. Joe ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
On Jul 30, 2021, at 14:39, Joe Abley wrote: > > Hi Paul, > > I think we've seen the working group drop particular proposed efforts for a > variety of reasons. I don't think it's accurate to characterize them all (or > any of them, to be honest) as victims to some special names obsession. We had a discussion yesterday about how do just don’t have enough time. We had a survey about prioritization because we don’t have enough time. It is all about dnsop resources. I believe my characterization is accurate. That is independent of one of my drafts being nixed for lack of time in the WG. You can look back and see me critique the WG on time spent on Special Use domains going back several years. We never reach agreement, always conclude we are not the right group. We even vowed to stop talking about and and then reneged on that (although Suzan and I disagree on the history there) > Sometimes the working group just doesn't like particular ideas, and we move > on. That’s not what happened. When adopted people felt it was an experiment that could be done even if half the group felt there was no use for it. The document then simply was never moved further by the chairs. It would have been fine if during a WGLC people said this is a bad idea after all. But that is not what happened. What happened is that the WG instead took on .zz and then threw .alt in there and then we had another couple of face time meetings in these things that just never see consensus because the WG is very vocally split. > Harmful is in the eye of the beholder, perhaps. We literally had a survey to ask us “what should we kill because we don’t have enough time” and yet we keep talking about ISO and now Roy wants to keep talking about ISO after ISO said “don’t do that”. Yeah, it’s an objective harmful waste of time. Sorry if that sounds harsh. Paul ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
On Jul 30, 2021, at 14:34, Roy Arends wrote: > > Please start a BOF and discuss this outside of dnsop. At dnsop, we don’t > have time for any more Special Use domains discussions. >> >> >> We are seeing the WG dropping actual protocol work because of these >> discussions. I now consider these discussions harmful. > > This is a working group draft, and should be discussed in the WG. So was draft-ietf-dnsop-delegation-only until it was killed yesterday due to lack of time because we had to spend it on political discussions with ISO liaisons. Paul ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
Hi Paul, On Jul 30, 2021, at 14:29, Paul Wouters wrote: > We are seeing the WG dropping actual protocol work because of these > discussions. I now consider these discussions harmful. I think we've seen the working group drop particular proposed efforts for a variety of reasons. I don't think it's accurate to characterize them all (or any of them, to be honest) as victims to some special names obsession. Sometimes the working group just doesn't like particular ideas, and we move on. Harmful is in the eye of the beholder, perhaps. Joe ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
> On 30 Jul 2021, at 19:29, Paul Wouters wrote: > > > On Jul 30, 2021, at 14:21, Roy Arends wrote: >> >> >> I now see that with the current status quo, this might a way forward that >> both sides of the argument might come together on. Essentially, instead of >> making the pond safe, we’ll have a warning sign that using the pond is at >> their own risk. >> >> I hope the WG can come together on this as a way forward. > > Please start a BOF and discuss this outside of dnsop. At dnsop, we don’t have > time for any more Special Use domains discussions. > > We are seeing the WG dropping actual protocol work because of these > discussions. I now consider these discussions harmful. This is a working group draft, and should be discussed in the WG. Roy ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
On Jul 30, 2021, at 14:21, Roy Arends wrote: > > > I now see that with the current status quo, this might a way forward that > both sides of the argument might come together on. Essentially, instead of > making the pond safe, we’ll have a warning sign that using the pond is at > their own risk. > > I hope the WG can come together on this as a way forward. Please start a BOF and discuss this outside of dnsop. At dnsop, we don’t have time for any more Special Use domains discussions. We are seeing the WG dropping actual protocol work because of these discussions. I now consider these discussions harmful. Sorry, Paul ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
[DNSOP] Moving forward on draft-ietf-dnsop-private-tld
Dear WG About 40 years ago, give or take, when Jon Postel planned to use the ISO3166 two character code elements as top level domains representing country names, ISO's TC46 secretariat was contacted (as was requested to users of the ISO3166 standard at the time) and he was told that the standard should not be used for DNS, as the future was in X.500. (Postel wasn’t swayed by the argument, and did what we now refer to as permission-less innovation). Recently, the ISO was contacted again, and subsequently the WG was again told that the standard wasn’t to be used in this way. It seems that a handful of folks are swayed by the argument and want to use this as guidance for the future of draft-ietf-dnsop-private-tld. Early on, Joe Abley proposed a way forward that I held off initially: Recognise that User Assigned 3166 code elements are used in various ways, including private networks, that these elements have not been delegated and are known to be used to anchor private namespaces. Do not recommend, promote or reserve anything, no registries. Document potential future pitfalls for using these codes for private namespaces and empower readers to make their own decisions. I now see that with the current status quo, this might a way forward that both sides of the argument might come together on. Essentially, instead of making the pond safe, we’ll have a warning sign that using the pond is at their own risk. I hope the WG can come together on this as a way forward. Warmly, Roy ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
