Re: EPP Domain Contacts
Mike O'Connell <[email protected]> Wed, 4 Dec 2013 08:35:57 +0200
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
--===============7143681898845772290== Content-Type: multipart/alternative; boundary="Apple-Mail=_2F9B51B0-CA39-4B2F-ACFB-197A19B74461" --Apple-Mail=_2F9B51B0-CA39-4B2F-ACFB-197A19B74461 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 04 Dec 2013, at 7:26 AM, Corey Goldfeder <[email protected]> = wrote: > We at Charleston Road Registry return a 2306 for contacts without = type. (In other words, we enforce type as a required attribute by policy = rather than by schema). Agreed - I've put a policy check in place to prevent it. I just wonder = if the spec should be slightly clearer about the type usage.=20 > On Tue, Dec 3, 2013 at 9:13 PM, Mike O'Connell <[email protected]> = wrote: > All, >=20 > I came across an issue the other day around Domain Contacts, = specifically, the domain contact element contains an optional attribute = 'type' which can be one of [tech, billing, admin]. The problem here is = that the attribute is optional with no assumed default.=20 >=20 > Does anybody use the domain contact element without the 'type' = attribute?=20 > Does anybody use a default value for the 'type' attribute when it is = not provided? >=20 > Apologies if this is a old/duplicate topic. >=20 > Regards, >=20 > Mike >=20 > -- >=20 > If you don't know where you are going, any road will get you there. >=20 >=20 > _______________________________________________ > provreg mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/provreg >=20 >=20 --Apple-Mail=_2F9B51B0-CA39-4B2F-ACFB-197A19B74461 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=iso-8859-1 <html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 04 Dec 2013, at 7:26 AM, Corey Goldfeder <<a href="mailto:[email protected]">[email protected]</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">We at Charleston Road Registry return a 2306 for contacts without type. (In other words, we enforce type as a required attribute by policy rather than by schema).</div></blockquote><div><br></div>Agreed - I've put a policy check in place to prevent it. I just wonder if the spec should be slightly clearer about the type usage. <br><div><br></div><br><blockquote type="cite"><div class= "gmail_extra"><div class="gmail_quote"> On Tue, Dec 3, 2013 at 9:13 PM, Mike O'Connell <span dir="ltr"><<a href="mailto:[email protected]" target="_blank">[email protected]</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div style="word-wrap:break-word">All,<div><br></div><div>I came across an issue the other day around Domain Contacts, specifically, the domain contact element contains an optional attribute 'type' which can be one of [tech, billing, admin]. The problem here is that the attribute is optional with no assumed default. </div> <div><br></div><div><ol><li>Does anybody use the domain contact element without the 'type' attribute? </li><li>Does anybody use a default value for the 'type' attribute when it is not provided?</li></ol><div> <br></div><div>Apologies if this is a old/duplicate topic.</div><div><br></div><div>Regards,</div><div><br></div><div>Mike</div><div><br></div><div> <span style="border-collapse:separate;border-spacing:0px"><div>--</div><div><br></div><div>If you don't know where you are going, any road will get you there.</div></span> </div> <br></div></div><br>_______________________________________________<br> provreg mailing list<br> <a href="mailto:[email protected]">[email protected]</a><br> <a href="https://www.ietf.org/mailman/listinfo/provreg" target="_blank">https://www.ietf.org/mailman/listinfo/provreg</a><br> <br></blockquote></div><br></div> </blockquote></div><br></body></html> --Apple-Mail=_2F9B51B0-CA39-4B2F-ACFB-197A19B74461-- --===============7143681898845772290== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg --===============7143681898845772290==--