Hello

Sorry I have not been checking the mails of this mailing list for a while...

In my opinion as registries we have a special role and should stick to
the RFC’s as close as possible for a strong EPP standard everybody can
rely on. Therefore I find it valuable to discuss the RFC’s and get
everybody's input.

I think that there is an issue with potentially breaking some clients,
although for some clients it may not be a problem as was pointed out.

Also I don't see a big problem for clients to not receive full
information in a message of a freshly implemented Change Poll Extension
response since they didn't get it at all before the extension was
implemented.

The suggestion of James Gould to give a hint about the missing extension
part in the <msg> field of the poll response may be a way to go. This
filed is intended for humans and thats what we want to do: Inform a
human to prepare his client and configure the Login command accordingly
if he wants to receive the information of the extension.

However the ChangePoll Extension is not the only one we need to inform
about. How should we inform about a changes in DNSSec Data? We also
would have to indicate that the DNSSec extension should be configured in
order to include something like

<secDNS:infData
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"><secDNS:dsData><secDNS:keyTag>2371</secDNS:keyTag>
<secDNS:alg>13</secDNS:alg>
<secDNS:digestType>2</secDNS:digestType>
<secDNS:digest>F991B7FDE40A2C4CD7BEFBBE9A1073D1FC3E34EC6DC31E2931320D1CD8392390</secDNS:digest>
</secDNS:dsData>
</secDNS:infData>

in the extension part..

We are planing to do something like this as we are going to implement
the RFC-8078 / RFC-7344 CDS feature. Of course there will also be an out
of band communication with our registrars about this.

Martin

--  SWITCH 
Martin Casanova, Domain Applications
Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland 
phone +41 44 268 15 55, direct +41 44 268 16 25
martin.casan...@switch.ch, www.switch.ch 
 
Working for a better digital world





_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to