Hello, On 8/17/21 16:30, Mario Loffredo wrote:
> Hi Martin, > > at .it we renew every domain automatically but the fee is always the same. > > However, if I understood well, it seems to me that a possible solution > might be a combination of the extensions defined in the two RFCs. > > After all, RFC5730 allows to include more elements in the extension > section of an EPP response. I'd agree that a combination of the changePoll and fee response extensions could be used here, but there are minor problems (see below). > You can use a poll message including as extensions the > changePoll:changeData element, to convey that the operation child is > "autoRenew", plus the fee:renew element, to convey the applied fee. In RFC 8748, <fee:renew> is defined for commands, while <fee:renData> is defined for (transform) responses, so <renData> seems more appropriate. One problem here is that the poll response in this case isn't strictly the response to any (client) transform command. Actually, RFC 8748 explicitly states "This extension does not add any elements to the EPP <poll> or <info> commands or responses." which indicates that this use case (delivering fees for unsolicited, server-initiated actions in poll messages) isn't really covered by the EPP fee extension yet, even if including them in poll responses is syntactically allowed as far as the XSD is concerned. However, registrars supporting the fee extension are unlikely to expect fee information in this place. But I think support for this use case should be added to a revised version of RFC 8748. 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
