Re: [IETF] IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
John Curran <jcurran@istaff.org> Fri, 21 June 2013 15:46 UTC
Return-Path: <jcurran@istaff.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 841C821F9D09 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 08:46:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id knFb732CUyZw for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 08:46:36 -0700 (PDT)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by ietfa.amsl.com (Postfix) with ESMTP id A3C9621F9C4D for <ietf@ietf.org>; Fri, 21 Jun 2013 08:46:36 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=diamond.istaff.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1Uq3Xn-000LeM-0h; Fri, 21 Jun 2013 15:46:35 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/NdkNjdtYc+Iq1j0lKS5sg
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: John Curran <jcurran@istaff.org>
In-Reply-To: <BB52D64B1827B309BF7D9629@JcK-HP8200.jck.com>
Date: Fri, 21 Jun 2013 11:46:34 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <C13DA83D-FC43-4243-897F-3E6B17B3434D@istaff.org>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <51C21498.3020008@gmail.com> <C8EEFB02-5637-4247-98F6-3B414E045E0E@kumari.net> <BB52D64B1827B309BF7D9629@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Cc: Patrik Fältström <paf@frobbit.se>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 15:46:42 -0000
On Jun 19, 2013, at 8:43 PM, John C Klensin <john-ietf@jck.com> wrote: > ... > The point, Warren (and others) is that all of these are "ICANN > doing technical stuff" and even "technical standards" in a broad > sense of that term. Some of it is stuff that the IETF really > should not want to do (I'm tempted to say "avoid like the > plague"). Some of it probably should be here. As an outsider > to both, there is a certain amount of stuff that has ended up in > SSAC and even RSAC that might have been better located in SAAG > or some IETF or NOG DNS operations group. I certainly won't > argue that we've got the balance right. And I think it is > unfortunate that the very early redesign of the original PSO had > the side effect of making it hard or impossible to work out > optimal boundaries and cross-review mechanisms with ICANN and > that we are instead having a discussion more than a dozen years > later about keeping ICANN from doing technical work or making > standards. +1 (specifically - it is unfortunate that a more operational ICANN / IETF liaison did not emerge via the PSO structure) > Let's not complicate things further by making the assumption > that anything that reasonably looks like "technical stuff" > belongs in the IETF and not in ICANN. It is likely to just make > having the right conversations even harder. I believe that policy issues that are under active discussion in ICANN can also be discussed in the IETF, but there is recognition that ICANN is likely the more appropriate place to lead the process of consensus development and approval. I believe that protocol development that is under active discussion at the IETF can also discussed at ICANN, but there is recognition that the IETF is likely the appropriate place to lead the process of consensus development and approval. Note that there are lots of things that are neither policy nor protocols (e.g. operational best practices and guidelines) and while one can claim that either forum is valid, it really depends on the particular situation and where those folks who are closest to the problem actually choose to go with it (and depending on the protocol, that might not be either of the above...) /John Disclaimer: My views alone - YMMV.
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… John C Klensin
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… Christopher Morrow
- Re: [Back to] Last Call: <draft-housley-rfc2050bi… David Conrad
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… Jari Arkko
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… John C Klensin
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… Jari Arkko
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… Christopher Morrow
- Re: [Back to] Last Call: <draft-housley-rfc2050bi… Christopher Morrow
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… Randy Bush
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… Patrik Fältström
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… SM
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… Patrik Fältström
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… Paul Hoffman
- Lessons from PROVREG WG was Re: IETF, ICANN and W… Edward Lewis
- Re: Lessons from PROVREG WG was Re: IETF, ICANN a… joel jaeggli
- Re: Lessons from PROVREG WG was Re: IETF, ICANN a… Thomas Narten
- Re: Lessons from PROVREG WG was Re: IETF, ICANN a… Patrik Fältström
- RE: Lessons from PROVREG WG was Re: IETF, ICANN a… Hollenbeck, Scott
- Re: Lessons from PROVREG WG was Re: IETF, ICANN a… Edward Lewis
- Re: IETF, ICANN and non-standards John Levine
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… Brian E Carpenter
- Re: IETF, ICANN and non-standards Ted Lemon
- Re: [IETF] Re: IETF, ICANN and non-standards Warren Kumari
- Re: [IETF] Re: IETF, ICANN and non-standards Joe Abley
- Re: [IETF] Re: IETF, ICANN and Whois (Was Re: Las… Warren Kumari
- Re: IETF, ICANN and non-standards John R. Levine
- Re: IETF, ICANN and non-standards John C Klensin
- Re: [IETF] Re: IETF, ICANN and Whois (Was Re: Las… John C Klensin
- Re: [IETF] IETF, ICANN and Whois (Was Re: Last Ca… John Curran
- Re: [IETF] IETF, ICANN and Whois (Was Re: Last Ca… David Farmer
- Re: [IETF] IETF, ICANN and Whois (Was Re: Last Ca… John C Klensin
- Re: [IETF] IETF, ICANN and Whois (Was Re: Last Ca… John Curran
- Re: IETF, ICANN and Whois (Was Re: Last Call: <dr… Fred Baker (fred)