IETF Logo Mail Archive

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

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Wed, 03 July 2019 16:38 UTC

Return-Path: <cpignata@cisco.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 663EC120148; Wed, 3 Jul 2019 09:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=NwaR2Zlr; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=uVBvvsuh
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 HcJqAWJknRU4; Wed, 3 Jul 2019 09:38:05 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C142D1200F9; Wed, 3 Jul 2019 09:38:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2090; q=dns/txt; s=iport; t=1562171884; x=1563381484; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=07KviOlyAy1GcbZvs+2Dqg9d573SUvPnNv8+uGgE3c8=; b=NwaR2ZlrJ7ryyQAXHJQd3EPU5DzGuymGg5bTxegZsCU3LZulUDhC9vAe l3+zVza6Y679EhXlUiWv37jB6c6cAmU4kjqOFCQtrT2aLHoq9CVjAr+Wq 4L4PhmQB78jifbJDSvA9mgaxU8Tv4BG1HY46n6L4afXi3GyfFhROvYnXr 8=;
IronPort-PHdr: 9a23:2yD5GxRAudDxyipBWUgkw/iAL9psv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESXBNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOiciHctEXUNs13q6KkNSXs35Yg6arw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AIAACl2Bxd/5NdJa1lGgEBAQEBAgEBAQEHAgEBAQGBUwUBAQEBCwGBQ1ADgT8gBAsoCoQSg0cDhFKJcoI2JZdGgS6BJANUCQEBAQwBAS0CAQGEQAIXggsjNAkOAQMBAQQBAQIBBW2KNwyFSgEBAQMBEhERDAEBNwEECwIBCBgCAiYCAgIwFRACBA4FIoMAgWsDDg8BApoUAoE4iGBxgTKCeQEBBYUPGIISCYEMKAGLXheBQD+BEScME4JMPoQuFQGDCjKCJo5om1cJAoIWk38bl3GhWoMJAgQCBAUCDgEBBYFQOIFYcBU7KgGCQT6CA4NxilNygSmLVAGBIAEB
X-IronPort-AV: E=Sophos;i="5.63,446,1557187200"; d="scan'208";a="587242684"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 Jul 2019 16:38:03 +0000
Received: from XCH-ALN-010.cisco.com (xch-aln-010.cisco.com [173.36.7.20]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id x63Gc3lB010797 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 3 Jul 2019 16:38:03 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-010.cisco.com (173.36.7.20) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 3 Jul 2019 11:38:03 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 3 Jul 2019 11:38:02 -0500
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 3 Jul 2019 11:38:02 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=07KviOlyAy1GcbZvs+2Dqg9d573SUvPnNv8+uGgE3c8=; b=uVBvvsuh6Eosr+gauM+xaC6Lb5I8cdKVgdZtQ0JIDByh/9KAFQMP3LiLwi2u48sfY+OmE7uw43Yua+XC5yofzz4gUBIAEhNwZIs+qon68m/KFWHOdkw5Xvfm6284iG5C9Q0k70qmLG0vPpiwaD9kX6+9Xf6IshzCKnWNq+0eXZI=
Received: from BL0PR11MB3028.namprd11.prod.outlook.com (20.177.204.138) by BL0PR11MB2881.namprd11.prod.outlook.com (20.177.146.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2032.20; Wed, 3 Jul 2019 16:38:01 +0000
Received: from BL0PR11MB3028.namprd11.prod.outlook.com ([fe80::28e3:f8a3:596:b998]) by BL0PR11MB3028.namprd11.prod.outlook.com ([fe80::28e3:f8a3:596:b998%3]) with mapi id 15.20.2052.010; Wed, 3 Jul 2019 16:38:01 +0000
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: 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: AQHVMaHM75Twec0400Gf+pAStIbdwaa5GBeA
Date: Wed, 03 Jul 2019 16:38:01 +0000
Message-ID: <5824682D-A4E2-4503-A21E-20C2D34A5C66@cisco.com>
References: <156214026874.14820.1075097887450900352@ietfa.amsl.com> <CALaySJKsesPDkS2vAMUvcDReRraU+h6R-R3N3MKVVB5CE=jmiQ@mail.gmail.com>
In-Reply-To: <CALaySJKsesPDkS2vAMUvcDReRraU+h6R-R3N3MKVVB5CE=jmiQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.104.11)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=cpignata@cisco.com;
x-originating-ip: [173.38.117.84]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: afd5f341-f72b-4939-4b5c-08d6ffd4d09f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BL0PR11MB2881;
x-ms-traffictypediagnostic: BL0PR11MB2881:
x-microsoft-antispam-prvs: <BL0PR11MB2881A376EBF26D6B04C03B74C7FB0@BL0PR11MB2881.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 00872B689F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(4636009)(136003)(39860400002)(376002)(346002)(366004)(396003)(199004)(189003)(8936002)(50226002)(8676002)(81166006)(81156014)(68736007)(66946007)(73956011)(6116002)(3846002)(76116006)(25786009)(54906003)(33656002)(86362001)(6916009)(316002)(2906002)(5660300002)(305945005)(66066001)(14454004)(36756003)(486006)(4326008)(99286004)(57306001)(53936002)(256004)(6512007)(11346002)(64756008)(6246003)(476003)(446003)(66476007)(2616005)(66446008)(7736002)(229853002)(76176011)(102836004)(186003)(6506007)(53546011)(71200400001)(71190400001)(6436002)(478600001)(6486002)(66556008)(26005)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:BL0PR11MB2881; H:BL0PR11MB3028.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: yN5c5YDcTUWY5K0JmNPiXltJGSopuyHYto7BAXD831ZiRHSyGQmgkRaDJvnioZjBdDOOIPOxcfgnJYLVH0AVDou6QoH59guKhK87RK32SbRFtZKeLV8iPSwH5+6Zy1ZOwI0eoXvWm2d52fTE7CQUX0XFisnumK4jK9vNLn6SQTNG1xJt3XNTDUYQV2INvQpTvmnB7ixtT4Jp+dDs5UdNSj7OvsPAEO7xh07P/P8oyNVM/l/fdWM0l1YGfgRjnLJaLsdqat0I5TUTj3P3OXzRd/azz5hJnTySAKFb9aUCbp0oBs2KIoxU+emCmrJoy3JmDfcZDAM3wi5/nr5HtJwySoxh3KYm63RhIymFzpoRYNQsHqiqapcoMWJ5S42XiIcAeXUgzAcZz5VS+/dxJ5sctSkyGU/iZcoSmt+Ig4kEArk=
Content-Type: text/plain; charset="utf-8"
Content-ID: <C3762E3A58ECC04F908E0761CB6ACEDB@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: afd5f341-f72b-4939-4b5c-08d6ffd4d09f
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jul 2019 16:38:01.5914 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: cpignata@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR11MB2881
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.20, xch-aln-010.cisco.com
X-Outbound-Node: rcdn-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/9McP0-c5HGEKm5JdSzrdbuNkmSI>
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: Wed, 03 Jul 2019 16:38:07 -0000

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?

Thanks,

-- Carlos.

> 
> Barry

v2.23.0 | Report a Bug | By Email