Hi Volker, If you run a real-world scenario where a registrant captures a complex street address, say for an office park, it’s going to be two or three lines long for example: Street1 Room 5, Floor 3 Street2 Orange Building, Teal Office Park, Street3 123 Silver Street now if the registrant moves buildings to a private residence for example: Street1 456 Yellow Avenue you wouldn’t want: Street2 Orange Building, Teal Office Park, Street3 123 Silver Street to remain. At the end of the day it’s up to the Registry policy; you can make it the Registrar’s problem to explicitly clear all fields or; provide some handling around resetting the fields if only one entry is provided. I know it’s not a direct answer but hopefully it sheds some light? -- Mike O'Connell Domain Name Services (Pty) Ltd +27 11 568 2812

On 25 Feb 2015, at 3:30 PM, Volker Janzen Notify <volker.janzen-notify@internetx.com> wrote:

Hi all,

I've a question regarding contact:addr inside of a contact:postalInfo block when using contact:chg.

E.g. this XML snippet from RFC 5733 (excerpt only):

C: <contact:chg> C: <contact:postalInfo type="int"> C: <contact:org/> C: <contact:addr> C: <contact:street>124 Example Dr.</contact:street> C: <contact:street>Suite 200</contact:street> C: <contact:city>Dulles</contact:city> C: <contact:sp>VA</contact:sp> C: <contact:pc>20166-6503</contact:pc> C: <contact:cc>US</contact:cc> C: </contact:addr> C: </contact:postalInfo> C: </contact:chg>

contact:street may occur zero to three times.

Is it intended that a single contact:street element should replace all existing contact:street elements or only the first contact:street element of the contact object?

Volker Janzen Team Entwicklung

-- InterNetX GmbH Maximilianstr. 6 93047 Regensburg Germany

Tel: +49 941 59559-0 Fax: +49 941 59579-050

www.internetx.com www.facebook.com/InterNetX www.twitter.com/InterNetX

Geschäftsführer/CEO: Thomas Mörz Amtsgericht Regensburg, HRB 7142

GPG-Key: 0x186C5F77 GPG-Fingerprint: 392E 8730 FE23 DCE8 8878 8524 5361 BCCC 186C 5F77

Hi, This same question came up on the provreg mailing list by Klaus Malorny ( http://www.ietf.org/mail-archive/web/provreg/current/msg07560.html ) that you can review. I paste in my reply to that thread ( http://www.ietf.org/mail-archive/web/provreg/current/msg07571.html) below for reference: I agree that it changes/modifies the elements specified, where I view the elements as being the direct child elements of <contact:chg>, which include: 1. <contact:postalInfo> with type attribute as being relevant * For example, if a contact had both types of postalInfo, inclusion of only one of the types ("int" or "loc") under the <contact:chg> does not implicitly remove the other type. * All sub-elements of the <contact:postalInfo> with type would be replaced including the two streets to one street example. 2. <contact:voice> to replace the voice 3. <contact:fax> to replace the fax 4. <contact:email> to replace the email 5. <contact:authInfo> to replace the authorization information 6. <contact:disclose> to replace the disclosure. The questions are focused on <contact:postalInfo> since it's a complex entity with one to two instances ("int" or "loc"). I view the concept of change as being a replace of the instance whether it's a complex or simple instance. — JG [cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com] James Gould Distinguished Engineer jgould@Verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 VerisignInc.com<http://VerisignInc.com> On Feb 25, 2015, at 8:30 AM, Volker Janzen Notify <volker.janzen-notify@internetx.com<mailto:volker.janzen-notify@internetx.com>> wrote: Hi all, I've a question regarding contact:addr inside of a contact:postalInfo block when using contact:chg. E.g. this XML snippet from RFC 5733 (excerpt only): C: <contact:chg> C: <contact:postalInfo type="int"> C: <contact:org/> C: <contact:addr> C: <contact:street>124 Example Dr.</contact:street> C: <contact:street>Suite 200</contact:street> C: <contact:city>Dulles</contact:city> C: <contact:sp>VA</contact:sp> C: <contact:pc>20166-6503</contact:pc> C: <contact:cc>US</contact:cc> C: </contact:addr> C: </contact:postalInfo> C: </contact:chg> contact:street may occur zero to three times. Is it intended that a single contact:street element should replace all existing contact:street elements or only the first contact:street element of the contact object? Volker Janzen Team Entwicklung -- InterNetX GmbH Maximilianstr. 6 93047 Regensburg Germany Tel: +49 941 59559-0 Fax: +49 941 59579-050 www.internetx.com<http://www.internetx.com> www.facebook.com/InterNetX www.twitter.com/InterNetX Geschäftsführer/CEO: Thomas Mörz Amtsgericht Regensburg, HRB 7142 GPG-Key: 0x186C5F77 GPG-Fingerprint: 392E 8730 FE23 DCE8 8878 8524 5361 BCCC 186C 5F77