Hello, On 8/10/21 02:34, Gustavo Lozano wrote:
> I have a comment regarding the following scenario: > > The EAI supporting server MUST satisfy the following obligations when the > client does not support the EAI extension: > > [...] > > When the email property is optional in the EPP response, the server MUST > validate whether the email property is an EAI address and if so don't > return the email property in the response and otherwise return the email > property that has been set based on server policy. > > I think that omitting the email property for this case is overloading the > meaning of an optional field. How does a client know if the email > property was omitted because there is no data or an EAI?. A client may > implement different actions for each semantic (i.e., no data or EAI). > > I think that the action for this case (EAI persisted for an optional > field) should be as in the case where the email property is required, in > other words, to return the error code 2308. > > Thoughts? I agree, simply omitting an optional e-mail field if the client didn't signal EAI support creates uncertainty that must be avoided, so the 2308 error we discussed for mandatory e-mail fields should be used here, too. 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
