Re: [eppext] Last Call: <draft-ietf-eppext-keyrelay-10.txt> (Key Relay Mapping for the Extensible Provisioning Protocol) to Proposed Standard

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 24 November 2015 21:46 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 73B961A8F4E for <eppext@ietfa.amsl.com>; Tue, 24 Nov 2015 13:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=unavailable
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 I-Lfuc5cNkFp for <eppext@ietfa.amsl.com>; Tue, 24 Nov 2015 13:46:39 -0800 (PST)
Received: from mail-oi0-x264.google.com (mail-oi0-x264.google.com [IPv6:2607:f8b0:4003:c06::264]) (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 3A5AE1A8FD4 for <eppext@ietf.org>; Tue, 24 Nov 2015 13:46:33 -0800 (PST)
Received: by oie188 with SMTP id 188so1835994oie.0 for <eppext@ietf.org>; Tue, 24 Nov 2015 13:46:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=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=/2L2JbMF5Q+q+/deVrenAhp1QL1Sqfi1a4bA56xwDEs=; b=lsNwV0daVoBTr40BUxeK96mexGDsJbGV8RF6KDTEKYSgsmhd+3PU6x3NtZ6o7sxkVC sFFkFgrzlqNyInVJJS3R2qe+gEllWhESllkK6zuKN5h76UsArIbADg83eGKTQZGrKHyW RLLBECHRtdQM4G+k8RClQjEjzSuCaaf94j0QOxm+TutnJwqbNWXxNNZBvTmogPYUZEFb jxc4GklOq9npEwqdDop9sAoDPtEPJHiFzXk4u6CFvYkhwXZxPrrvDIzCpVNagsIBAvWr 8FAartsy+wkH30fGtKCfgMRrauv8A6MRqkqHpjoMpdKSbtzRvmo1+5U2OMtTbkcO0y7u zuJg==
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=/2L2JbMF5Q+q+/deVrenAhp1QL1Sqfi1a4bA56xwDEs=; b=RI8y0g5Oe8Q7qo22cj7BrsSeRYg9Y8j+S7NrLAaRuW2xNqm0Z8RXaMP8Axz0ln9gtL p2UI3/ejtRM+h/xY5PLcTRFukHg5lOA4RZQuZATNhlUKfFwzH+TSFSoF4r3JxmcrprNh mD9Gqq/RVGdDDU1tDJBuUsu+vFQcAobyLFSc61CL5IfaXYpQOzx4kCxdDQ5p453kD4a0 45eRCwl9CqVOE6nV79PYuSp1qGQPDGEk5qMDprihn4TE4AD9T+Gv7YHFHpzmWhOqeXKR NLw0M3J59mi1Uxchup51IlvCoQuUWCxQf/4XEnqCzpv/qDoQ0IyRo9AlfEpLSgU7GNq1 N3aA==
X-Gm-Message-State: ALoCoQkGZ5vP4u1TbwZU6VAYBls0uBGBEnJLvGgL6oxVA1dY7cdqzMyLL8N4q4TNlCZIE/OIkTm3PAfg9j+jIrwBcJWo005gSA==
X-Received: by 10.140.147.67 with SMTP id 64mr37825142qht.12.1448401592638; Tue, 24 Nov 2015 13:46:32 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id p23sm2150509qkl.0.2015.11.24.13.46.32 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 24 Nov 2015 13:46:32 -0800 (PST)
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 tAOLkVof006192 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 24 Nov 2015 16:46:32 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 24 Nov 2015 16:46:31 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Rik Ribbers <rik.ribbers@sidn.nl>
Thread-Topic: [eppext] Last Call: <draft-ietf-eppext-keyrelay-10.txt> (Key Relay Mapping for the Extensible Provisioning Protocol) to Proposed Standard
Thread-Index: AQHRI9c9mqjacnt7v06ATNpNWCL6b56qzG4AgADvDME=
Date: Tue, 24 Nov 2015 21:46:29 +0000
Message-ID: <600A70B7-3B5B-43DB-A0F3-829DF64C22FA@verisign.com>
References: <20151120210547.19513.70351.idtracker@ietfa.amsl.com>, <42B2B74B-2194-434E-9471-924964FA957E@sidn.nl>
In-Reply-To: <42B2B74B-2194-434E-9471-924964FA957E@sidn.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/TICSKYAxRPPdQNhV8-iYwwS1DRI>
Cc: "eppext-chairs@ietf.org" <eppext-chairs@ietf.org>, Ulrich Wisser <ulrich@wisser.se>, "ietf@ietf.org" <ietf@ietf.org>, "barryleiba@gmail.com" <barryleiba@gmail.com>, eppext <eppext@ietf.org>
Subject: Re: [eppext] Last Call: <draft-ietf-eppext-keyrelay-10.txt> (Key Relay Mapping for the Extensible Provisioning Protocol) to Proposed Standard
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 21:46:40 -0000

I think that's a good fix, Rik.

Scott

> On Nov 24, 2015, at 3:31 AM, Rik Ribbers <rik.ribbers@sidn.nl>; wrote:
> 
> Hello All,
> 
> Based on the discussion the reseller drafts within the EPPEXT working group I revisited the keyrelay draft and came to the conclusion I want to change something in the XML schema. As it is in last call I post this message in the IETF list and the WG list.
> 
> What is the issue:
> In this thread there is a discussion on the XML schema attribute schemaLocation.   
> https://www.ietf.org/mail-archive/web/eppext/current/msg00841.html 
> 
> Having read the XML schema specification this attribute can be used in a document to provide hints as to the physical location of schema documents which may be used for assessment. In other words it is optional and is treated as a hint for XML parsers. We have added the schemaLocation to the XSDs in our own SRS implementation for XML validation and that's how it ended op in the keyrelay document.
> 
> Looking at the other EPP RFC (RFC5731,RFC5732,RFC5733) there is no schemaLocation attribute in the XML schema, so my proposal below makes the keyrelay document more in sync with the existing RFCs.
> 
> My proposal is to change the following in Chapter 4 Formal syntax:
> 
>   <import namespace="urn:ietf:params:xml:ns:epp-1.0"
>       schemaLocation="epp-1.0.xsd" />
>     <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
>       schemaLocation="eppcom-1.0.xsd" />
>     <import namespace="urn:ietf:params:xml:ns:secDNS-1.1"
>       schemaLocation="secdns-1.1.xsd" />
>     <import namespace="urn:ietf:params:xml:ns:domain-1.0"
>       schemaLocation="domain-1.0.xsd" />
> 
> into
> 
>   <import namespace="urn:ietf:params:xml:ns:epp-1.0"/>
>   <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
>   <import namespace="urn:ietf:params:xml:ns:secDNS-1.1"/>
>   <import namespace="urn:ietf:params:xml:ns:domain-1.0"/>
> 
> Is there any objection to doing this? Any other remarks?
> 
> Kind regards,
> Rik Ribbers
> 
> 
> 
>> On 20 Nov 2015, at 22:05, The IESG <iesg-secretary@ietf.org>; wrote:
>> 
>> 
>> The IESG has received a request from the Extensible Provisioning Protocol>> Extensions WG (eppext) to consider the following document:
>> - 'Key Relay Mapping for the Extensible Provisioning Protocol'
>> <draft-ietf-eppext-keyrelay-10.txt> as Proposed Standard
>> 
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2015-12-04. Exceptionally, comments may be>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>> 
>> Abstract
>> 
>> 
>>  This document describes an Extensible Provisioning Protocol (EPP)
>>  mapping for a key relay object that relays DNSSEC key material
>>  between EPP clients using the poll queue defined in RFC5730.
>> 
>>  This key relay mapping will help facilitate changing the DNS operator
>>  of a domain while keeping the DNSSEC chain of trust intact.
>> 
>> 
>> 
>> 
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-ietf-eppext-keyrelay/
>> 
>> IESG discussion can be tracked via
>> https://datatracker.ietf.org/doc/draft-ietf-eppext-keyrelay/ballot/
>> 
>> 
>> The following IPR Declarations may be related to this I-D:
>> 
>>  https://datatracker.ietf.org/ipr/2393/
>> 
>> 
>> 
>> _______________________________________________
>> EppExt mailing list
>> EppExt@ietf.org
>> https://www.ietf.org/mailman/listinfo/eppext
> 
> 
> 
> 
> _______________________________________________
> EppExt mailing list
> EppExt@ietf.org
> https://www.ietf.org/mailman/listinfo/eppext
> 
>