IETF Logo Mail Archive

Re: [regext] [IANA #1231867] expert review for draft-ietf-regext-epp-eai (epp-extensions)

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 07 June 2022 13:03 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F361C14CF13 for <regext@ietfa.amsl.com>; Tue, 7 Jun 2022 06:03:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h0b1PpCKUlum for <regext@ietfa.amsl.com>; Tue, 7 Jun 2022 06:02:56 -0700 (PDT)
Received: from mail1.verisign.com (mail1.verisign.com [72.13.63.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7541AC14F740 for <regext@ietf.org>; Tue, 7 Jun 2022 06:02:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=2184; q=dns/txt; s=VRSN; t=1654606977; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=UO/wRf2zKxmlCeA2c6etrDxYzfVXSK7v75wnAOxA5cs=; b=b7rA04gsqBNefCD6b7BDBY6z3oG3H5fyudpXOFXSzNE4nBkMl5Ink9Kf w2JdTxatvP/vda44s3Sk5kw8ohPxkaq+2P2dnByWgQXvFcKnAp0+BpYi0 j9KOwgfxsO4O1lk5TB/Pxwe7u5Gust2npeepZ1pmffhgdT4FN35IHs7OQ E/AraowE7AKjZRdIddClLqIdg+yC5lFPDeu7oXMSMsSgytL/WbF9/DC8U 2+adhDue5J0gje3Y52MVUkC43uke6HicAZ+rdh97SfeW2gAK15hOPUHDI A/EREC0uR0Bn0EZQxoJnZRT7+CQWlbQJ+7bO1UrJ/XeeituiRfpUl/2xR Q==;
IronPort-Data: A9a23:VeUwQ6u8WgWPyY1a19eQ9KvRXOfnVBxfMUV32f8akzHdYApBsoF/q tZmKWnQPvmPYmv3eo10PY3j8xkF6sLUx95iTgpqritmHy9G9ZOVVN+UEBz9bniYRiHhoOCLz O1FM4Wdc5pkJpP4jk3wWlQ0hSAkjclkfld4YQL9EngZqTVMEU/Nsjo+3b9g6mJUqYLhWVnV5 4ut+5S31GKNgFaYDEpFs8pvlzsy5JweiBtA1rDpTakW1LN2vyB94KM3fcldHVOhKmVnNrfSq 9L48V2M1jixEyEFUYr5z+mhIiXmdZaJVeSGoiI+t6GK3EAe9nRqukoxHKJ0hUx/011lkz3to TnkWFPZpQoBZ8XxdOohvxZwAxBbE7wX8Zr7IHG/nZCq61DEI1TR6qA7ZK02FdVwFudfK1tor MM+BQBVN1adjOWs2PSyRq9ynN8lasLsOevzuFk5lXeAUq1gGM2YBfmajTNb9G5YasRmBvbZY 84UbzBiZxfofRBVO0wWB5R4l+Ct7pX6W2QG8wLO+PVti4TV5BVT/7fOPIXwRv6XfppPhWqC5 VyZ2F2sV3n2M/Tak1Jp6EmEivXGkz/gHY8CDLCi6rtwjUOSy3M7CRQQXB28u/bRolSzVN9PN 2QV9zYg668o+ySWosLVVQe++WGCsw5EAp9LDfd87QCWj6DTpQyDADFCUCRabpots8peqSEW6 2JlVujBXVRH2IB5g1rEnltIhVte4RQoEFI=
IronPort-HdrOrdr: A9a23:V887Ja6jLzzo2ZDTPQPXwBXXdLJyesId70hD6qkXc20xTiX4rb HNoB1173/JYVoqNk3I+uruBEDoexq1yXcf2/hzAV7NZmjbkVrtAo1k4ZDr3jHsXwbvn9Qw6Y 5QN4xzEsf5A1Q/r8rriTPTL/8QhP2K6rqhi+ub9WpqVg0CUcxdxh10ERmWCXd7QwR6BZ40fa D22vZ6
X-IronPort-AV: E=Sophos;i="5.91,283,1647302400"; d="scan'208";a="16383572"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2375.24; Tue, 7 Jun 2022 09:02:53 -0400
Received: from BRN1WNEX02.vcorp.ad.vrsn.com ([10.173.153.49]) by BRN1WNEX02.vcorp.ad.vrsn.com ([10.173.153.49]) with mapi id 15.01.2375.024; Tue, 7 Jun 2022 09:02:53 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "drafts-expert-review@iana.org" <drafts-expert-review@iana.org>
CC: "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] [IANA #1231867] expert review for draft-ietf-regext-epp-eai (epp-extensions)
Thread-Index: AQHYefaSgwwoE/Eka0isFj1Fi+tMB61D5unA
Date: Tue, 07 Jun 2022 13:02:53 +0000
Message-ID: <27ca49a9436e46e7ab565bb8bec7eadf@verisign.com>
References: <RT-Ticket-1231867@icann.org> <rt-4.4.3-17530-1654298614-526.1231867-37-0@icann.org> <rt-4.4.3-16037-1654555290-573.1231867-37-0@icann.org>
In-Reply-To: <rt-4.4.3-16037-1654555290-573.1231867-37-0@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/HYgBnZNvmUpZGgT8-T4tphEl5Es>
Subject: Re: [regext] [IANA #1231867] expert review for draft-ietf-regext-epp-eai (epp-extensions)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2022 13:03:00 -0000

> -----Original Message-----
> From: Michelle Thangtamsatid via RT <drafts-expert-review@iana.org>
> Sent: Monday, June 6, 2022 6:42 PM
> Cc: Hollenbeck, Scott <shollenbeck@verisign.com>; regext@ietf.org
> Subject: [EXTERNAL] [IANA #1231867] expert review for draft-ietf-regext-
> epp-eai (epp-extensions)
>
> Caution: This email originated from outside the organization. Do not click 
> links
> or open attachments unless you recognize the sender and know the content
> is safe.
>
> Dear Scott (cc: regext WG),
>
> As the designated expert for the Extensions for the Extensible Provisioning
> Protocol (EPP) registry, can you review the proposed registration in draft-
> ietf-regext-epp-eai for us? Please see

[SAH] As noted by Tim Bray, There are a few minor issues:

The request to register the XML namespace looks fine. With respect to Tim's 
comment:

> Section 6.1 says
> “      XML:  None.  Namespace URIs do not represent an XML specification."
> and then
> "      XML:  See the "Formal Syntax" section of this document."
>
> Hmm, a namespace URI identifies an XML markup vocabulary, so "None" is a 
> little jarring. If there's no XML why the namespace? And it also feels 
> inconsistent with the second statement.

Sections 3.2 and 4 of RFC 3688 provides some context for the first "XML: None" 
above. There is no XML to be stored in the IANA registry, hence the "None".

There is no XML schema defined by this extension, so there is no need to 
register a schema. The " Registration request for the eai XML Schema" should 
be removed.

Scott

v2.23.0 | Report a Bug | By Email