Re: [regext] Éric Vyncke's No Objection on draft-ietf-regext-epp-fees-18: (with COMMENT)

Roger D Carney <rcarney@godaddy.com> Tue, 01 October 2019 14:43 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 3C385120860; Tue, 1 Oct 2019 07:43:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 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, T_KAM_HTML_FONT_INVALID=0.01] 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 D7z9mCeVtens; Tue, 1 Oct 2019 07:43:04 -0700 (PDT)
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-co1nam05on071d.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe50::71d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 384D9120863; Tue, 1 Oct 2019 07:43:01 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=N/flhOqREdc72cm3YdPSHnkyVjclTrJOLEoxkgifF46jtPP5CBr9o1EkYopZtdWVI0I1IpQojE5O3hcO8iULsCUnwgohsAhNfTAiym0qPQ0p1Pk7mM5t3FNPo5pb85DBzfUYe1lzzzB0gu5OpolZ2RcOnhdrRz/Z9XyAnw93RCx2DA3KbmdAie+OEN3R8SbbeTpoOEC2J2UlmL55GGPQWaKrT2PeaARYZEEQpqJ7wi0WYbR3g1EJLRNsQUVoHOqk4sGyTVMgaPfPJd85b52Ic+0JdSm1ICr46i4PNhTmdLbs8Nn7dS6wsEsM+IOhvaGOSNiu0DdSdn2Fx1php7FxhA==
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=dhT4PEKjZ7mgePcBj+9z62UeqKuh6qagjWIMlZhO8/E=; b=Bq+b8QamA0KPrVtSJP3q5gnKGBGZ/SEnJgnt2LpgTrtIbPDhOHD/FDxdKkM+JgE+Mcysa8usZbKHOr09tQ167+cRCj8ZpONiP86LFEqiPHTkGsjKUoL0N6m69dzVFaCWRLsjVwGSTkJpIOXGp42v60DoYKyO7Bc7S3dk9GhZNi67cuid0rFOLj+i0TwYHro8fnAEO8MAoyx3HPElOXTn7Sv0MvL0qx6KWCSPP0xG+fSoo8AoTgNOwRWubwVqVyzGTYKfIvHpwtaWYUgeGu51nM9g/csuL6Iq+8IurhNPkT6tZeKNWAuqQ23DM5wQzTUPm08Kh0NNwjgMrE8wpjrAmQ==
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=dhT4PEKjZ7mgePcBj+9z62UeqKuh6qagjWIMlZhO8/E=; b=ohRPS/HwnVgzgMJAy8Wubvvxqg15m1Qt41sEjSG0UhJGX94NfY4DeEwYvl1/kP25KedMSw8GR4WmOywZwjp+9wXqopkZfRz85nJnEcgDrHXVXysD8jFXvzhihmhHO/2JFi2uDlAc9pR5/t94jUCpKCJvB158LFT46qeFZ7QoJ68=
Received: from BL0PR02MB5491.namprd02.prod.outlook.com (20.177.207.214) by BL0PR02MB4787.namprd02.prod.outlook.com (20.177.145.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.20; Tue, 1 Oct 2019 14:42:58 +0000
Received: from BL0PR02MB5491.namprd02.prod.outlook.com ([fe80::614d:ec26:993a:6d44]) by BL0PR02MB5491.namprd02.prod.outlook.com ([fe80::614d:ec26:993a:6d44%6]) with mapi id 15.20.2305.017; Tue, 1 Oct 2019 14:42:58 +0000
From: Roger D Carney <rcarney@godaddy.com>
To: The IESG <iesg@ietf.org>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: Éric Vyncke's No Objection on draft-ietf-regext-epp-fees-18: (with COMMENT)
Thread-Index: AQHVbsJXwaCRk5Chf06vUNJ9I43xrqdEq9TA
Date: Tue, 01 Oct 2019 14:42:58 +0000
Message-ID: <BL0PR02MB549111240CBDC3721A0BCBF5B19D0@BL0PR02MB5491.namprd02.prod.outlook.com>
References: <156888090162.4585.16706995483859575463.idtracker@ietfa.amsl.com>
In-Reply-To: <156888090162.4585.16706995483859575463.idtracker@ietfa.amsl.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: 5139b012-8a7a-4387-b69b-08d7467da742
x-ms-office365-filtering-ht: Tenant
x-ms-traffictypediagnostic: BL0PR02MB4787:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BL0PR02MB4787510B8920DF3EC9129ED6B19D0@BL0PR02MB4787.namprd02.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0177904E6B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(396003)(376002)(346002)(136003)(366004)(39860400002)(13464003)(199004)(189003)(11346002)(102836004)(99286004)(790700001)(6506007)(5660300002)(26005)(229853002)(446003)(33656002)(2906002)(3846002)(486006)(2501003)(7736002)(52536014)(53546011)(6436002)(476003)(76176011)(71200400001)(71190400001)(186003)(6116002)(7696005)(316002)(81156014)(8936002)(55016002)(110136005)(54896002)(606006)(6306002)(86362001)(9686003)(224303003)(25786009)(81166006)(450100002)(66556008)(66446008)(66066001)(6246003)(66476007)(236005)(256004)(14444005)(64756008)(76116006)(14454004)(478600001)(966005)(74316002)(21615005)(66946007); DIR:OUT; SFP:1102; SCL:1; SRVR:BL0PR02MB4787; H:BL0PR02MB5491.namprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: godaddy.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 0Ij56yZIbgDUt9ZCA2vQoQegG2VrPklt+NfSDKAaQRksP4LFJacbesRxNf678UujilI2Hx6h858huQ7L957+HcMcBmYbwXNWswXbM3oqq14TctEORSHygHJhV7w635pgxPZBCtXxFQKG4YdHru/6xvgw0RTWs9T4IMTLYs6BviknF7A97bax2BJ3x/tJjbNA3riVG0GassuGBAIxjGw2q9HUq5itovWNaGvClE4FY+gmraaAjSib75DlvU+YejCsu09l1HI/eFRSHRQ1qQwLUb/SUoF9CObN/tLBNLCVjV8NctGEhaJJNMoGPUjsJjqFsNelqBcrULGfbWzJEJOyYzYLiO/AmElc0lfWJE3Sj1JsRRCboIZYmoUIrOR+7EcD9M2sQYIxfeX8zIDyPhqN7sDySpmGLH47NWuj7K9pz6T/HQffaHgIaQw8h9GiuTaU6fW+Pv7cQZKaRTvEBSWDEQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BL0PR02MB549111240CBDC3721A0BCBF5B19D0BL0PR02MB5491namp_"
MIME-Version: 1.0
X-OriginatorOrg: godaddy.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5139b012-8a7a-4387-b69b-08d7467da742
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Oct 2019 14:42:58.5948 (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: 4Z026RFXU+WH+15Hn9L7S86SbVGMKc6vguUATbZY0fIEhZAD1zTt/Nh+XPxb18MNmKOKj8aqF8urVwSV4SjzJA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR02MB4787
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/CJC7obCOfN48W-m78EYmBDokllM>
Subject: Re: [regext] Éric Vyncke's No Objection on draft-ietf-regext-epp-fees-18: (with COMMENT)
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: Tue, 01 Oct 2019 14:43:07 -0000

Good Morning,



Thanks for your comments Eric, please see my responses below, a new revision will be published shortly to address issues brought up in this latest round of comments.





Thanks

Roger



-----Original Message-----
From: Éric Vyncke via Datatracker <noreply@ietf.org<mailto:noreply@ietf.org>>
Sent: Thursday, September 19, 2019 3:15 AM
To: The IESG <iesg@ietf.org<mailto:iesg@ietf.org>>
Cc: draft-ietf-regext-epp-fees@ietf.org<mailto:draft-ietf-regext-epp-fees@ietf.org>; James Gould <jgould@verisign.com<mailto:jgould@verisign.com>>; regext-chairs@ietf.org<mailto:regext-chairs@ietf.org>; jgould@verisign.com<mailto:jgould@verisign.com>; regext@ietf.org<mailto:regext@ietf.org>
Subject: Éric Vyncke's No Objection on draft-ietf-regext-epp-fees-18: (with COMMENT)



Notice: This email is from an external sender.







Éric Vyncke has entered the following ballot position for

draft-ietf-regext-epp-fees-18: No Objection



When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)





Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html

for more information about IESG DISCUSS and COMMENT positions.





The document, along with other ballot positions, can be found here:

https://datatracker.ietf.org/doc/draft-ietf-regext-epp-fees/







----------------------------------------------------------------------

COMMENT:

----------------------------------------------------------------------



Thank you for the work put into this document. I have only one COMMENT and one NITS see below.



Regards,



-éric



== COMMENT ==



-- Section 3.4 --

C.1) Any reason to have a negative value for <fee:credit> ? This seems counter-intuitive to me.



[RDC] I think I see both sides of the fee (non-negative) / credit (negative) struggle. I think if you are thinking about this in accounting terms the definitions may seem backwards but this draft is not about accounting/ledger so much, it is about the fee. In the end this draft is about the “number” (fee) a server is going to charge the client for an action (e.g. what is the fee to create this domain). Not sure if I am making this clearer or mudding it up, but to me it does seem intuitive that one is positive and one is negative. The group thought it was cleaner to make the fees positive and the credits negative.



== NITS ==



Introducing <fee:cd> earlier in the text would improve the readability of the document.



[RDC] Section 3.9 (first section this is mentioned) will be updated to provide a reference to the details in section 5.1.1.