IETF Logo Mail Archive

Re: [eppext] FW: [IANA #814918] INSERT “Extensible Provisioning Protocol Mapping: Suggestion"

Patrick Mevzek <pm@dotandco.com> Sun, 26 April 2015 23:17 UTC

Return-Path: <patrick@shaktot.patoche.org>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37C481ACCF0 for <eppext@ietfa.amsl.com>; Sun, 26 Apr 2015 16:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.287
X-Spam-Level:
X-Spam-Status: No, score=0.287 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id avt9CI_BKcl4 for <eppext@ietfa.amsl.com>; Sun, 26 Apr 2015 16:17:28 -0700 (PDT)
Received: from shaktot.patoche.org (shaktot.patoche.org [212.85.152.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D0191ACCEB for <eppext@ietf.org>; Sun, 26 Apr 2015 16:17:28 -0700 (PDT)
Received: from shaktot.patoche.org (localhost.localdomain [127.0.0.1]) by shaktot.patoche.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id t3QNHK72002365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Apr 2015 01:17:20 +0200
Received: (from patrick@localhost) by shaktot.patoche.org (8.14.3/8.14.3/Submit) id t3QNHKxi002364; Mon, 27 Apr 2015 01:17:20 +0200
Date: Mon, 27 Apr 2015 01:17:19 +0200
From: Patrick Mevzek <pm@dotandco.com>
To: "eppext@ietf.org" <eppext@ietf.org>
Message-ID: <20150426231719.GC15029@home.patoche.org>
References: <RT-Ticket-814918@icann.org> <A973DE55-D717-4973-9C8B-733CF04742DD@verisign.com> <rt-4.2.9-2033-1427129077-1113.814918-9-0@icann.org> <831693C2CDA2E849A7D7A712B24E257F49F89B7A@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <20150407135631.GA32612@home.patoche.org> <831693C2CDA2E849A7D7A712B24E257F49F98906@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F49F98906@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
X-PGP-KeyID: A241FB6B
X-PGP-Fingerprint: 9DA9 5054 7A5D 03FC A9AD 9AFF 1371 9F06 A241 FB6B
X-Request-PGP: http://www.keyserver.net:11371/pks/lookup?op=vindex&search=0xA241FB6B
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Scanned-By: shaktot_dot_patoche_dot_org on 212.85.152.86
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/6L0tWSdUEWouvCLGIv0mmGRry5g>
Subject: Re: [eppext] =?utf-8?b?Rlc6IFtJQU5BICM4MTQ5MThdIElOU0VSVCDigJxFeHRl?= =?utf-8?q?nsible_Provisioning_Protocol_Mapping=3A_Suggestion=22?=
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Apr 2015 23:17:30 -0000

Hollenbeck, Scott <shollenbeck@verisign.com> 2015-04-07 16:07
> Jim Gould can address the specific question about version numbering for this particular extension, but yes, it's entirely possible for a document to change (necessitating a change in a document version number) without the XML Schema and/or namespace version number changing.
 
My main concern (for all submissions, not a specific one)                                                                                                                                                
is that the IANA registry has just a link to a                                                                                                                                                           
document, and not even an XML namespace (the one being described by                                                                                                                                      
the document).                                                                                                                                                                                           
                                                                                                                                                                                                         
In the future, there is no way to ascertain what exactly did the DEs                                                                                                                                     
analyze at the time of inclusion in the IANA registry                                                                                                                                                    
since the namespace may completely evolve with or without                                                                                                                                                
changes in the document, the document itself can change, and of course                                                                                                                                   
even the link can become stale.                                                                                                                                                                          
                                                                                                                                                                                                         
Except for RFCs, of course…                                                                                                                                                                              
                             
-- 
Patrick Mevzek

v2.8.7 | Report a Bug | By Email