IETF Logo Mail Archive

Re: [DNSOP] Review of draft-manderson-rdns-xml-01

Terry Manderson <terry.manderson@icann.org> Tue, 13 August 2013 00:56 UTC

Return-Path: <terry.manderson@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37C7011E80F0 for <dnsop@ietfa.amsl.com>; Mon, 12 Aug 2013 17:56:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 AczEjUevs2XO for <dnsop@ietfa.amsl.com>; Mon, 12 Aug 2013 17:56:02 -0700 (PDT)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id CFF0A11E80E9 for <dnsop@ietf.org>; Mon, 12 Aug 2013 17:56:01 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Mon, 12 Aug 2013 17:56:01 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: Jay Daley <jay@nzrs.net.nz>
Date: Mon, 12 Aug 2013 17:55:57 -0700
Thread-Topic: [DNSOP] Review of draft-manderson-rdns-xml-01
Thread-Index: Ac6Xv+DemRK+PPpaT2qyk/HZ5R9yXg==
Message-ID: <CE2FB7EC.17F21%terry.manderson@icann.org>
In-Reply-To: <9B4EAB28-0301-474D-9F87-2BC49E55DB01@nzrs.net.nz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.6.130613
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3459236158_65058050"
MIME-Version: 1.0
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Review of draft-manderson-rdns-xml-01
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 00:56:08 -0000

Hi Jay,

On 13/08/13 9:28 AM, "Jay Daley" <jay@nzrs.net.nz> wrote:

>
>I really do not mean to cause any offence by this so apologies in advance
>if I do, but is this a case of ICANN mistaking its position here?

No offence taken, and certainly a good question to ask.


>Yes you are the excellent operator of a key part of the public
>infrastructure but that doesn't mean that every protocol you develop
>related to your technical function automatically becomes an RFC when
>documented to a sufficient standard.


I am not sensing that ICANN is mistaking its position here at all. There
are no demands for the document to become an RFC via the ISE. It is a
respectful thought, on my part, to offer the documentation of the
technical portion first to the IETF, and should the IETF choose to not to
absorb that then ICANN has done the appropriate action. In that case then
ICANN might publish the documentation as a whitepaper on a website
somewhere. But the effort has been made to be clear and transparent to the
broader technical community, and not hide nor bury anything.


Cheers
Terry

v2.23.0 | Report a Bug | By Email