Hello, On 13/02/2017 14:59, Hollenbeck, Scott wrote:
> Jim, the change option should be interpreted as “completely replace old > value with this new value”. Whatever postalInfo is provided with an > update should completely replace whatever was there before. Looking at > the use case you described, yes, you can replace <contact:postalInfo > type=”int”> with <contact:postalInfo type=”loc”> by including the “loc” > value in the <contact:chg> element. If that’s not clear it’s only because > I didn’t think the meaning of “change” was ambiguous. That’s why there’s > nothing there to selectively identify the values to be altered – “change” > means “completely replace”. If the idea were to completely replace all postal info by whatever <postalInfo> elements are specified in the <chg> element, then there would be no point in having a special - potentially completely empty - "chgPostalInfoType" type in the schema there, since it allows the addition of incomplete address data that could result in schema violations for <contact:info> responses. This could just be "postalInfoType" then to enforce the presence of mandatory fields. This seems to indicate that the original idea was *not* a complete replacement. This would otherwise also kind of contradict the way <chg> is interpreted for domains (RFC 5731), since it would imply that one could not change a domain's registrant without also changing or removing a domain's authinfo string. Note that this topic has been discussed before, starting at https://www.ietf.org/mail-archive/web/provreg/current/msg07560.html As a result of that discussion, our own EPP server implementation in the TANGO Registry System does the following: * if a <postalInfo> loc/int element is specified which is "empty" ("empty" being defined as: no org, no name, and mandatory address element "city" missing), the server removes that element from the contact * if it is not empty, it completely replaces the respective loc/int data * if the contact has loc/int data which is not present in the <chg> element, that data is retained, i.e. *not* removed Best regards, Thomas -- TANGO REGISTRY SERVICES® Knipp Medien und Kommunikation GmbH Thomas Corte Technologiepark Phone: +49 231 9703-222 Martin-Schmeisser-Weg 9 Fax: +49 231 9703-200 D-44227 Dortmund E-Mail: thomas.co...@knipp.de Germany _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
