Thomas, The primary purpose of draft-ietf-regext-epp-fees is fees and credits, and returning the balance and credit limit in the response to a transform command is an optional feature that the server can choose to support. I don't see an issue with a server deciding to return the balance and credit limit information in the response to a billable transform command, but I don't believe it should be a requirement. Providing a mechanism to explicitly query for the balance and credit limit information is best suited with an object mapping such as the Balance Mapping. — JG
James Gould Distinguished Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 5/16/19, 4:59 AM, "Thomas Corte" <thomas.co...@knipp.de> wrote: Hello, On 15/05/2019 19:52, Gould, James wrote: > Thomas, > > I view the balance and credit limit information as separate from the > fee information supported by draft-ietf-regext-epp-fees. The balance > and credit limit information can optionally be returned by > draft-ietf-regext-epp-fees, but I believe it's better to support a > specific query mechanism. To me, this means that the current state of the fee extension is somewhat inconsistent, since it does include balance information in some contexts but not in others. Either it is a purely fee related extension (in which case the balance/credit limit features should be removed altogether), or it's a general extension dealing with all billing issues (in which case a query feature should be added). > The Balance Mapping, which is registered > in the EPP Extension Registry > (https://www.iana.org/assignments/epp-extensions/epp-extensions.xhtml), > enables querying for the balance and credit limit information > directly. The Low Balance Mapping, which is also registered in the > EPP Extension Registry, supports a poll message when the available > credit falls below a pre-defined threshold. Is there interest in > these extensions? The Balance Mapping in the EPP Extension Registry looks like a viable option, we'd consider implementing it if it became an IETF standard. Best regards, Thomas -- TANGO REGISTRY SERVICES® is a product of: Knipp Medien und Kommunikation GmbH Technologiepark Phone: +49 231 9703-222 Martin-Schmeisser-Weg 9 Fax: +49 231 9703-200 D-44227 Dortmund E-Mail: supp...@tango-rs.com Germany _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
