Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
SM <sm@resistor.net> Wed, 19 June 2013 09:15 UTC
Return-Path: <sm@resistor.net>
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 708C121F9FC0 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 02:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.365
X-Spam-Level:
X-Spam-Status: No, score=-102.365 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 tTyo6PUo5bbV for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 02:15:41 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A036A21F9FA7 for <ietf@ietf.org>; Wed, 19 Jun 2013 02:15:41 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5J9FS8V016073; Wed, 19 Jun 2013 02:15:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1371633335; bh=c5h/+VT1QS/eKiH5xm3G41nBvRo7Jl+6ef/9jww1SAM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cNq6DENqzMT65SxTGMBu6u78zhCXJ8XSOWJwAzWPiwNr+sblMgQH8h/j2hqJ/lk1Z 1BKqYZ/9+AQ+4WaGfbydPgEPl1700w8LHcLYjuwU64jSvKylLE4Nor8H2ZpTO+upY9 wOkFvSVgv3XYnUiC3uTAyfPhft+RgZRShAOvmEn4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1371633335; i=@resistor.net; bh=c5h/+VT1QS/eKiH5xm3G41nBvRo7Jl+6ef/9jww1SAM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pHV+nL/4DzVGoSVSWgfWQz1xjbnPOC1UU9tK0Hfy1endPkVJSNmWMhIGtHJLS8j1+ AJoMSLtsnDhyF6kAVifGmzSKfKx7rIMUHBRA71B+nU+bBsqR1onmOCg6tw+7moTfBn JYZd7uFbmBbR6HOXtkkhjNBPz2ohkcnah7lR4aAA=
Message-Id: <6.2.5.6.2.20130619000239.0b0ebd38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 19 Jun 2013 01:59:28 -0700
To: Patrik Fältström <paf@frobbit.se>
From: SM <sm@resistor.net>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
In-Reply-To: <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Cc: John C Klensin <john-ietf@jck.com>, 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: Wed, 19 Jun 2013 09:15:42 -0000
Hi Patrik, At 23:25 18-06-2013, Patrik Fältström wrote: >I think this is the correct strategy, BUT, I see >as a very active participant in ICANN (chair of >SSAC) that work in ICANN could be easier if some >"more" technical standards where developed in >IETF, and moved forward along standards track, >that ICANN can reference. Same with some >epp-related issues, and also DNS-related, which >I must admit I think has stalled in the IETF. >When that happens, ICANN start to "invent" or at >least discuss IETF related issues -- which I >think is non optimal. But on the other hand, if >IETF do not move forward, then what should ICANN do? I'll highlight part of a comment from Steve Crocker: (I sometimes have to explain to my colleagues at ICANN who have not had the benefit of the IETF experience that "let's send it over to the IETF" doesn't work. The IETF isn't a standing army ready to do ours or anyone else's work. Rather, I say, it's a place where the relevant people can get together to get their work done. It is easy to see why there isn't significant progress about DNS-related issues in the IETF. If nobody volunteers to do the work the work does not get done. Whether the problems are acute enough to require surgery is not for me to decide. The ITU does work as the IETF does not show interest in doing that work when it had the opportunity to do so. I would not worry too much about ICANN inventing as, to quote John Klensin: I don't know whether that is because they don't have time to write shorter reports or because they don't think the subject matter can be covered in more concise reports, but the pattern is clear, When those committees cannot agree or discover the issues are, in fact, contentious, they typically recommend the creation of more committees. Sometimes people either do not see the problems or pretend not to see them (I am not inferring that you do that). In the latter case I would be asked to explain why I think the problem is a problem when I mention it. I am somewhat suspicious when people who have much more experience than me do that. :-) I don't know whether you have been following the URNbis discussions. That WG had leisurely discussions about the drafts since over three years. It has not been able to publish a single RFC. DNSEXT has been in shutdown mode since over a year. The call for adoption of a draft in DNSOP failed as there wasn't significant interest within the working group to do that work. I'll ask a question to the other persons subscribed to this mailing list. Are there other active participants in ICANN interested in doing work in the IETF? Regards, -sm
- 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)