IETF Logo Mail Archive

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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Mon, 27 April 2015 10:54 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 3B3C71B3063 for <eppext@ietfa.amsl.com>; Mon, 27 Apr 2015 03:54:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] 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 MAtRaMDoXfuX for <eppext@ietfa.amsl.com>; Mon, 27 Apr 2015 03:54:29 -0700 (PDT)
Received: from mail-oi0-f97.google.com (mail-oi0-f97.google.com [209.85.218.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 882EB1B3062 for <eppext@ietf.org>; Mon, 27 Apr 2015 03:54:29 -0700 (PDT)
Received: by oiax69 with SMTP id x69so3881095oia.0 for <eppext@ietf.org>; Mon, 27 Apr 2015 03:54:28 -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:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-type:content-transfer-encoding:mime-version; bh=IvgiW0WRyDCr8b1lxEc+kreo0dK2NUv4HNy1L3m2hr8=; b=Kl6qL8LpwvbP9Vy1Vrgq06GkyLLUKC9aZFWaSNojLhBBKAs7joPGTlI1+2hfKhleKs frzpl1YbKW7YL+RJb9AQoaYqGtGu1HWAi7j6fNDylytMzI4K/EaFQsNqsfW695T3+clH mV3kTogMpkHjiIBTC/7aSARXHRG3tM2mWErnh62hvQ3bK8TRIKk0i+ulUrvM/BK+V0xn MFm5ivom/lS88v3L36zOnKx57EXTF/YeD6dnpv4qnCoP3GqclcsdQB5wvufCbZX5LOj3 ytxZc3XArXYf3LswiTll2io/0Yb5Vdm+Pdty7UrFTQTEY/xRjvFIZ4bAXtAi4lK5eYqD AwCg==
X-Gm-Message-State: ALoCoQmD9aXjPvRmVkff0vVCaxFVqbtlkSS9x0gOjdKca/pnAzdOdfs5YKTAvf2aobZuupUQrxmPY8Tn1miO4cpbEjHnF0vZmg==
X-Received: by 10.55.22.10 with SMTP id g10mr11652511qkh.26.1430132068656; Mon, 27 Apr 2015 03:54:28 -0700 (PDT)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by mx.google.com with ESMTPS id hl17sm4989614qcb.4.2015.04.27.03.54.28 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 27 Apr 2015 03:54:28 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id t3RAsR7q029910 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Apr 2015 06:54:27 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 27 Apr 2015 06:54:27 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Patrick Mevzek <pm@dotandco.com>, "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: =?utf-8?B?W2VwcGV4dF0gRlc6IFtJQU5BICM4MTQ5MThdIElOU0VSVCDigJxFeHRlbnNp?= =?utf-8?Q?ble_Provisioning_Protocol_Mapping:_Suggestion"?=
Thread-Index: AQHQgHcwlsV4NfuCIEGMP7DqI6i12p1gr8ig
Date: Mon, 27 Apr 2015 10:54:26 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F49FBBE0D@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> <831693C2CDA2E849A7D7A712B24E257F49F98906@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <20150426231719.GC15029@home.patoche.org>
In-Reply-To: <20150426231719.GC15029@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/szcsTphU2AqGGNB8QULGx8Ba8UY>
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: Mon, 27 Apr 2015 10:54:31 -0000

> -----Original Message-----
> From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Patrick
> Mevzek
> Sent: Sunday, April 26, 2015 7:17 PM
> To: eppext@ietf.org
> Subject: Re: [eppext] FW: [IANA #814918] INSERT “Extensible
> Provisioning Protocol Mapping: Suggestion"
> 
> 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.

DE analysis is captured on this mailing list. If the document changes the registry should be updated. If the link goes stale the registry entry can be removed.

Scott

v2.8.7 | Report a Bug | By Email