IETF Logo Mail Archive

Re: [regext] Opsdir last call review of draft-ietf-regext-epp-fees-16

Roger D Carney <rcarney@godaddy.com> Fri, 06 September 2019 14:48 UTC

Return-Path: <rcarney@godaddy.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 80F92120CC0; Fri, 6 Sep 2019 07:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=secureservernet.onmicrosoft.com
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 jMBqI39gpvnK; Fri, 6 Sep 2019 07:48:17 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-eopbgr800101.outbound.protection.outlook.com [40.107.80.101]) (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 99F7C120C90; Fri, 6 Sep 2019 07:48:17 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=S1zc2A4w4ztWXLx/NttnUtFGx21ZsRbMJ4V9Wxr80AVasMMFc7OUpw/qrNQ/H54I407dCz9g+Plt9F69RzC/wb5HrDE2VeA5lgYS+345faqQP82ufUEzMNn74E+axYUQXvmfMRtTeXjw/FZGAfzJD2ICKFz1hUnin5pgD27zNP7O/BLK4N8Y3UnucNvL1gPqOEakIYs4PT2cl7tSefifqk3A7ybP0sADjRvbroqlo5WJTOJ356geOvRhWGqOzI9japCPZYJ75JiOrbiwPiqlKfHEiS3IYOTzgpfrIf1fstH+cBMfj0Rns89mf/LkZquWLIc0aI2KBPV0fVb8N+bgLg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2COLfSJ6EWr3A7KvFO/eKj4iOZYJnLDW8YmM+DBE1i4=; b=W0qRq9w81Pr5XClRLmJBUEdy6QqjEZIv10kPMD2NNLfOGlpTezkMmc45wqIM5gIPY2SsiC3AS0Vt1VHDGcm5BvIbDOpXajKAcfqbdlrQkWTPf1422D5p98Ph5bgl4EzYQxkeK73dhPdN/IOBQngcxQvrXI8aXZh9Qn6+eXzP7CgetnNfMIXS2QqbCCHBcXzoNZ4CwF9VVjt4FkZ726PBYxwTZd36MJkGXiTtUHO/u31JVUr4AeYpPteIX4dLlBdqGwuf9EIPvYV4y6OTs5fglyAlzhH8G8axMfPp487/KqZvMawI0ZyTQ7rvuvArT8jm2q3N92JB0cH0AEPD+63Igw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=godaddy.com; dmarc=pass action=none header.from=godaddy.com; dkim=pass header.d=godaddy.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=secureservernet.onmicrosoft.com; s=selector2-secureservernet-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2COLfSJ6EWr3A7KvFO/eKj4iOZYJnLDW8YmM+DBE1i4=; b=dtmIYKkW908r1awjaicPlyGv4O9+T2kg+KBjk7LalvDGBUq5Gy6l9MWcRE9U29r+EalQkUUOwTWKz/UX4xB8O4+ubC6eJxTBANdWiMrJKDgLf101HbWCcr5Eru6FpSFuyHcV5fw8NCO67GuvqDgLDrVRHvFjDni+OXBmI1q0P1E=
Received: from BL0PR02MB5491.namprd02.prod.outlook.com (20.177.207.214) by BL0PR02MB4625.namprd02.prod.outlook.com (10.167.172.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.19; Fri, 6 Sep 2019 14:48:16 +0000
Received: from BL0PR02MB5491.namprd02.prod.outlook.com ([fe80::de0:ffa3:56a:6f4e]) by BL0PR02MB5491.namprd02.prod.outlook.com ([fe80::de0:ffa3:56a:6f4e%6]) with mapi id 15.20.2220.022; Fri, 6 Sep 2019 14:48:16 +0000
From: Roger D Carney <rcarney@godaddy.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Barry Leiba <barryleiba@computer.org>
CC: "ops-dir@ietf.org" <ops-dir@ietf.org>, IETF discussion list <ietf@ietf.org>, "draft-ietf-regext-epp-fees.all@ietf.org" <draft-ietf-regext-epp-fees.all@ietf.org>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: Opsdir last call review of draft-ietf-regext-epp-fees-16
Thread-Index: AQHVMXQYtqC0OHQ0mku5gb5l2g0TRaa44HsAgAA3+ICAYrQQ0A==
Date: Fri, 06 Sep 2019 14:48:16 +0000
Message-ID: <BL0PR02MB549148C0C57557C1579F3497B1BA0@BL0PR02MB5491.namprd02.prod.outlook.com>
References: <156214026874.14820.1075097887450900352@ietfa.amsl.com> <CALaySJKsesPDkS2vAMUvcDReRraU+h6R-R3N3MKVVB5CE=jmiQ@mail.gmail.com> <5824682D-A4E2-4503-A21E-20C2D34A5C66@cisco.com>
In-Reply-To: <5824682D-A4E2-4503-A21E-20C2D34A5C66@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rcarney@godaddy.com;
x-originating-ip: [173.18.40.219]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e1db4384-3ae3-428d-36ff-08d732d94047
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:BL0PR02MB4625;
x-ms-traffictypediagnostic: BL0PR02MB4625:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BL0PR02MB4625B349902C597A841FC0DAB1BA0@BL0PR02MB4625.namprd02.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0152EBA40F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(346002)(39860400002)(366004)(396003)(136003)(13464003)(189003)(199004)(52536014)(74316002)(9686003)(7736002)(5660300002)(11346002)(186003)(110136005)(54906003)(6506007)(66446008)(64756008)(66556008)(66476007)(66946007)(76116006)(6436002)(476003)(6246003)(3846002)(6116002)(790700001)(86362001)(256004)(478600001)(14454004)(2906002)(53936002)(7696005)(229853002)(316002)(33656002)(446003)(76176011)(14444005)(71190400001)(71200400001)(53546011)(486006)(4326008)(25786009)(55016002)(99286004)(102836004)(66066001)(54896002)(8936002)(81166006)(81156014)(6306002)(26005)(8676002); DIR:OUT; SFP:1102; SCL:1; SRVR:BL0PR02MB4625; H:BL0PR02MB5491.namprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: godaddy.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Lqnd/MrdEpygz8uB0Dcx3rQBFXHhmct1+sPw9BCh+kgbwE+tDkwWMo27TruN0Zufswl1+Xwr6e2c03+YjUoiL5KvIZhqMlRNURaZmQOJVuKygiFYVYjLVZuHEoJyvp2uzAbzojDzwkX6n0PxqFPNVFDf4HMGGh67Su86GtBOzXt6AoNWiJ0+xhaOUhYnUduow7XeE4T8c5914ZioElyH8vrC/hSoxeRevZ28wJdqyCPeyzVNXuIa7a0g7AbvNoTXg/QpxmTnZLR+dzjlw6LDc64z//R5bX/gCG/Db4lab/c9qboaQ1H3ovlGO3eOG0qV0yupTwPrYiwdb76GojL5d+KvDpMlLXy4462RtifEfm5rNPKQtpr6GTF7KxBIOsjA6JPZT9o6AOglHYKNfgXPjR5ZoqOuYGGmBsZDGK2eGGQ=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BL0PR02MB549148C0C57557C1579F3497B1BA0BL0PR02MB5491namp_"
MIME-Version: 1.0
X-OriginatorOrg: godaddy.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e1db4384-3ae3-428d-36ff-08d732d94047
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Sep 2019 14:48:16.2396 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d5f1622b-14a3-45a6-b069-003f8dc4851f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 8dXqkRcMcg85c0OdhWVdvpsP+QdveA3ZyU1LjsDhkISNUgqrd6vEs6+K4KeRYznF3Jfx9zHYxTTdte8+arGKFw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR02MB4625
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/7lvi1hlUxDjGs6Z-po_GW_SEdpU>
Subject: Re: [regext] Opsdir last call review of draft-ietf-regext-epp-fees-16
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 06 Sep 2019 14:48:26 -0000

Good Morning,



Thank you for your follow-up Carlos, please see my responses below. A new version of the draft will be published shortly and will address all of the review comments that needed edits.





Thanks

Roger



-----Original Message-----

From: Carlos Pignataro (cpignata) <cpignata@cisco.com>

Sent: Wednesday, July 3, 2019 11:38 AM

To: Barry Leiba <barryleiba@computer.org>

Cc: ops-dir@ietf.org; IETF discussion list <ietf@ietf.org>; draft-ietf-regext-epp-fees.all@ietf.org; regext@ietf.org

Subject: Re: Opsdir last call review of draft-ietf-regext-epp-fees-16



Notice: This email is from an external sender.







Hi, Barry,



> On Jul 3, 2019, at 9:17 AM, Barry Leiba <barryleiba@computer.org> wrote:

>

> Thanks, Carlos, for the review.



Anytime!



>

> On one item in your list:

>

>> 4. S3.4. Does this text imply there is no zero fee or credit

>> possible? Might be useful to explicitly set guidance for the use of 0/null fee/credit.

>>

>>   A <fee:fee> element MUST

>>   have a non-negative value.  A <fee:credit> element MUST have a

>>   negative value.

>

> The text says the fee can be zero ("non-negative"), but the credit

> can't (has to be negative).  That makes general sense, doesn't it?  Do

> you really think there needs to be further explanation of that?



Since zero is neither negative nor positive, I thought it was potentially a source of misinterpretation.



But you are correct, the text as-is is accurate and perfect.



That is why I marked these as “Minor comments, questions, and nits for your consideration”. As this is an Ops-Dir review, Appendix A of RFC 5706 is detailed about defaults, boundary conditions, hence asking :-)



BTW, re-reading that section, I noticed:



   A server MAY respond with multiple <fee:fee> and <fee:credit>

   elements in the same response.  In such cases, the net fee or credit

   applicable to the transaction is the arithmetic sum of the values of

   each of the <fee:fee> and/or <fee:credit> elements.



Do these need to include the same <fee:currency> or otherwise how would the arithmetic sum work?



[RDC] Yes, the currencies are the same and the schema enforces this rule.



Thanks,



-- Carlos.



>

> Barry

v2.23.0 | Report a Bug | By Email