IETF Logo Mail Archive

Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)

"Fred Baker (fred)" <fred@cisco.com> Fri, 21 June 2013 23:04 UTC

Return-Path: <fred@cisco.com>
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 7C99E21F9E61 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 16:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.449
X-Spam-Level:
X-Spam-Status: No, score=-110.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, 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 3ceFSKRPh7+E for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 16:04:36 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id EC8BB21F9E5C for <ietf@ietf.org>; Fri, 21 Jun 2013 16:04:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=828; q=dns/txt; s=iport; t=1371855876; x=1373065476; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=4rROHp5O+EWgdEzXYotbw9B74SP6intnTmZmMBSingY=; b=Qx4D2CdmfFfsjrbsian+1lpy+bnfZcE6SjDecrLAOj2U7ZgFVHoeN0bs b36LLED4xfXpbi1VYZX+5msRAT5yRVKoOcFGVJDBBLanX+783SB9gAZzu 5QHp55a1MZ+6buWmGRLZ5KR2RVRw/sIvJpM2Al77WABHuKgTX1y1B59s9 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmAFAAXbxFGtJV2Z/2dsb2JhbABbgwl6gjy8eYECFnSCIwEBAQMBeQULAgEIIhkLMiUCBA4FCIgABrwwjxYCMQeDAGEDiGmgHoFYgTeCKA
X-IronPort-AV: E=Sophos;i="4.87,916,1363132800"; d="scan'208";a="226015496"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP; 21 Jun 2013 23:04:35 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r5LN4ZGV006477 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 21 Jun 2013 23:04:35 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.02.0318.004; Fri, 21 Jun 2013 18:04:34 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Patrik Fältström <paf@frobbit.se>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
Thread-Topic: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
Thread-Index: AQHObDyaqjV6wFd3/k2sXSlyLZPtU5k8BEAAgADilwCABDvlAA==
Date: Fri, 21 Jun 2013 23:04:34 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B922569@xmb-rcd-x09.cisco.com>
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>
In-Reply-To: <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.125]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <735413BB31725F4B91B1435690E99757@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Fri, 21 Jun 2013 23:04:41 -0000

On Jun 18, 2013, at 11:25 PM, Patrik Fältström <paf@frobbit.se> 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?

Something ICANN can do is ask the IETF for specifications. I can't promise instant delivery, but it will be slower if we don't know what they need.

v2.23.0 | Report a Bug | By Email