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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 07 April 2015 14:09 UTC

Return-Path: <shollenbeck@verisign.com>
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 A65BB1A87A2 for <eppext@ietfa.amsl.com>; Tue, 7 Apr 2015 07:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.29
X-Spam-Level:
X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham
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 NeMgDb0p_PoJ for <eppext@ietfa.amsl.com>; Tue, 7 Apr 2015 07:09:25 -0700 (PDT)
Received: from mail-qg0-f97.google.com (mail-qg0-f97.google.com [209.85.192.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5460E1B35FD for <eppext@ietf.org>; Tue, 7 Apr 2015 07:07:03 -0700 (PDT)
Received: by qgdz60 with SMTP id z60so2971694qgd.0 for <eppext@ietf.org>; Tue, 07 Apr 2015 07:07:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:content-transfer-encoding :mime-version; bh=tiXygv7D88FZZgANrB+GFZMRooVTgUzYXJbwFEQTkn8=; b=CVO0Byn3Jo15ZnpsmVgLTZ1bfDdT8tDEC3quYi9VhHsqT68xvDtiCuAikJ1QTFHM9a GFYqi+YFjlkMHdJiOMx2OuGbMUpA/j4VwhH7X88Xzy3GPyJ7e0vKgVj00eK9zoxkJGht q0ZoErf/HQdooPaBeCNqFehC57miO7JFsb63drkEq6S2AjHT8B3Z+lUiByCkeKX+OLrg AWDmC8F7dBBGZONfDy4VBdKgPaEnkIMGwM4+0pthWAx3Jrbf0aT9ZfKdo44iAwfdmm5A cebveuQaSEdiLvzU2eU1UDCfUmMITgxpKEd1hyyGOndIcJHB83RL30ZbjojWbDsDBgrI 47XQ==
X-Gm-Message-State: ALoCoQk8klN/1ne9DZB+3+9TXrTj/xCAC1v+8BPw0MoD1IMkKHb9/w8iayj01AsIDyfstWfXthNxudHYdFWETmIkKAIHeUG0pA==
X-Received: by 10.55.56.20 with SMTP id f20mr38068963qka.100.1428415622412; Tue, 07 Apr 2015 07:07:02 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by mx.google.com with ESMTPS id 6sm2052206qcf.1.2015.04.07.07.07.02 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 07 Apr 2015 07:07:02 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t37E70ET029331 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 7 Apr 2015 10:07:01 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 7 Apr 2015 10:07:00 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Patrick Mevzek <pm@dotandco.com>
Thread-Topic: =?utf-8?B?W2VwcGV4dF0gRlc6IFtJQU5BICM4MTQ5MThdIElOU0VSVCDigJxFeHRlbnNp?= =?utf-8?Q?ble_Provisioning_Protocol_Mapping:_Suggestion"?=
Thread-Index: AQHQcTqy1mukJ2FyB0ySRDN0fkNeTZ1BlSsw
Date: Tue, 7 Apr 2015 14:07:00 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F49F98906@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
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>
In-Reply-To: <20150407135631.GA32612@home.patoche.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/ZcFp1TE8O7rAYzZc-ZjldhvjvrM>
Cc: "eppext@ietf.org" <eppext@ietf.org>
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: Tue, 07 Apr 2015 14:09:27 -0000

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.

Scott

> -----Original Message-----
> From: Patrick Mevzek [mailto:pm@dotandco.com]
> Sent: Tuesday, April 07, 2015 9:57 AM
> To: Hollenbeck, Scott
> Cc: eppext@ietf.org
> Subject: Re: [eppext] FW: [IANA #814918] INSERT “Extensible
> Provisioning Protocol Mapping: Suggestion"
> 
> Hello,
> 
> I've stumbled upon something, maybe irrelevant, maybe interesting in
> general for the WG.
> 
> The PDF quoted has a "Version 1.4" in preamble with also a nice summary
> at beginning with differences for each version.
> However the namespace is
> http://www.verisign-grs.com/epp/suggestion-1.1
> 
> Does that mean that the document changed without a change in namespace
> version?
> Or that the 1.1 namespace version was published after version 1.4 of
> the
> document?
> 
> To be more generic, if not done already, shouldn't the WG eventually
> give some guidance to authors and/or mandate a change of namespace
> version when documentation does change? With some related issues:
> - what for simple bugfixes or erratas?
> - what if the server/client behaves in practice differently from what
>   was documented?
> - also, should the WG discuss how to handle transitions from one
>   version to another?
> I'm aware of specific cases in the past, like for example a switch
> from one version to another where the server was allowing either one,
> of course with different capabilities…
> (this also creates the problem of namespace in polling messages… what
> is they are retrieved by registrar long after the fact, hence the
> namespace does not exist anymore or if the registrar did not choose
> the given namespace at login, should he still get it in its polling
> message?)
> 
> Hollenbeck, Scott <shollenbeck@verisign.com> 2015-03-23 19:05
> > Submitted for DE evaluation.
> >
> > Scott
> >
> > -----Original Message-----
> > From: Amanda Baber via RT [mailto:iana-prot-param-comment@iana.org]
> > Sent: Monday, March 23, 2015 12:45 PM
> > Cc: Hollenbeck, Scott
> > Subject: [IANA #814918] INSERT “Extensible Provisioning Protocol
> Mapping: Suggestion"
> >
> > #11 of 18.
> >
> > -----BEGIN FORM-----
> > Name of Extension:
> > “Extensible Provisioning Protocol Mapping: Suggestion"
> >
> > Document Status:
> > Informational
> >
> > Reference:
> > http://www.verisigninc.com/assets/epp-sdk/EPP-Suggestion-Mapping.pdf
> >
> > Registrant Name and Email Address:
> > VeriSign Inc., epp-registry@verisign.com
> >
> > TLDs: Any
> >
> > IPR Disclosure: None
> >
> > Status: Active
> >
> > Notes: None
> > -----END FORM-----
> >
> > —
> >
> >
> > JG
> >
> >
> >
> >
> >
> > James Gould
> > Distinguished Engineer
> > jgould@Verisign.com
> >
> > 703-948-3271
> > 12061 Bluemont Way
> > Reston, VA 20190
> >
> > VerisignInc.com
> >
> > “This message (including any attachments) is intended only for the
> use of the individual or entity to which it is addressed, and may
> contain information that is non-public, proprietary, privileged,
> confidential and exempt from disclosure under applicable law or may be
> constituted as attorney work product. If you are not the intended
> recipient, you are hereby notified that any use, dissemination,
> distribution, or copying of this communication is strictly prohibited.
> If you have received this message in error, notify sender immediately
> and delete this message immediately.”
> >
> > Download BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png
> >
> > image/png 4KiB
> > Image not shown because display is disabled in system configuration.
> > _______________________________________________
> > EppExt mailing list
> > EppExt@ietf.org
> > https://www.ietf.org/mailman/listinfo/eppext
> 
> --
> Patrick Mevzek
> The reasonable man adapts himself to the world; the unreasonable one
> persists in trying to adapt the world to himself. Therefore all
> progress depends on the unreasonable man.  -- George Bernard Shaw