Re: Inconsistent Domain Status Value Guidance in RFC 5731
Michael Young <[email protected]> Fri, 11 Sep 2015 15:30:09 -0400
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
--===============3254409517960093208== Content-Type: multipart/alternative; boundary="Apple-Mail=_6985C8D0-3691-487F-86D1-E09E5495128F" --Apple-Mail=_6985C8D0-3691-487F-86D1-E09E5495128F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Scott I=E2=80=99m not sure (long time ago) but I think it originally = had to do with allowing differing levels of detailed response depending = on who was asking - hence server policy. Seems like it got changed in = one spot to allow for that but not another. -Michael Young > On Sep 11, 2015, at 3:20 PM, Hollenbeck, Scott = <[email protected]> wrote: >=20 > =E2=80=9CServer policy=E2=80=9D is a slippery slope when it comes to = interoperability. Anyway, I can=E2=80=99t find anything in the email = archive that sheds any light on my original question. The text has been = consistent since before RFC 3730, so maybe it=E2=80=99s not as confusing = as I thought it was this morning. > =20 > Scott > =20 > From: provreg [mailto:[email protected] = <mailto:[email protected]>] On Behalf Of Roger D Carney > Sent: Friday, September 11, 2015 2:18 PM > To: [email protected] <mailto:[email protected]> > Subject: Re: [provreg] Inconsistent Domain Status Value Guidance in = RFC 5731 > =20 > +1 Jim, this is how I read it as well and it does make sense to me. = And like Jim, I am not sure why a server would not return the status(es) = and we would request that they do, but I do not see a problem with how = the RFC is written. > =20 > =20 > Thanks > Roger > =20 > =20 > From: provreg [mailto:[email protected] = <mailto:[email protected]>] On Behalf Of Gould, James > Sent: Friday, September 11, 2015 7:00 AM > To: Hollenbeck, Scott > Cc: [email protected] <mailto:[email protected]> > Subject: Re: [provreg] Inconsistent Domain Status Value Guidance in = RFC 5731 > =20 > Scott, > =20 > It doesn=E2=80=99t =E2=80=9Ctickle any memories=E2=80=9D, but making = the status optional (=E2=80=9CZero or more OPTIONAL=E2=80=9D) in the = info response leaves it up to server policy whether or not to return = =E2=80=9Cthe at least one associated status value". It makes sense in = describing the statuses in section 2.3 that there must be at least one = status, and leave the return of the statuses optional in the info = response based on server policy. I=E2=80=99m not sure why the server = would not want to return the statuses, but the protocol supports such a = policy. =20 > =20 > =E2=80=94 > =20 > JG >=20 >=20 > <image001.png> >=20 > James Gould > Distinguished Engineer > [email protected] <x-msg://42/[email protected]> >=20 > 703-948-3271 > 12061 Bluemont Way > Reston, VA 20190 >=20 > VerisignInc.com <http://verisigninc.com/> > =20 > On Sep 11, 2015, at 7:28 AM, Hollenbeck, Scott = <[email protected] <mailto:[email protected]>> wrote: > =20 > I received a mail note from someone asking about a difference in the = text that appears in RFC 5731 and the schema that is supposed to support = that text. First, the text from Section 2.3: >=20 > "A domain object MUST always have at least one associated status = value". >=20 > Text from Section 3.1.2 (info response): >=20 > "Zero or more OPTIONAL <domain:status> elements that contain the = current status descriptors associated with the domain" >=20 > The schema matches the 3.1.2 text. I can't remember why or how we = ended up with text that says "MUST always have at least one" in one = section and "Zero or more OPTIONAL" in another section. Does this tickle = any memories for anyone? >=20 > Scott >=20 > _______________________________________________ > provreg mailing list > [email protected] <mailto:[email protected]> > https://www.ietf.org/mailman/listinfo/provreg = <https://www.ietf.org/mailman/listinfo/provreg> > =20 > _______________________________________________ > provreg mailing list > [email protected] <mailto:[email protected]> > https://www.ietf.org/mailman/listinfo/provreg = <https://www.ietf.org/mailman/listinfo/provreg> --Apple-Mail=_6985C8D0-3691-487F-86D1-E09E5495128F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><div class=3D"">Scott I=E2=80=99m not sure (long time ago) = but I think it originally had to do with allowing differing levels = of detailed response depending on who was asking - hence server policy. = Seems like it got changed in one spot to allow for that but not = another.</div><div class=3D""><br class=3D""></div><div = class=3D"">-Michael Young</div><div class=3D""><br class=3D""></div><br = class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On = Sep 11, 2015, at 3:20 PM, Hollenbeck, Scott <<a = href=3D"mailto:[email protected]" = class=3D"">[email protected]</a>> wrote:</div><br = class=3D"Apple-interchange-newline"><div class=3D""><div = class=3D"WordSection1" style=3D"page: WordSection1; font-family: = Helvetica; font-size: 12px; font-style: normal; font-variant: normal; = font-weight: normal; letter-spacing: normal; line-height: normal; = orphans: auto; text-align: start; text-indent: 0px; text-transform: = none; white-space: normal; widows: auto; word-spacing: 0px; = -webkit-text-stroke-width: 0px;"><div style=3D"margin: 0in 0in 0.0001pt; = font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span = style=3D"font-family: Calibri, sans-serif; color: rgb(153, 51, 102);" = class=3D"">=E2=80=9CServer policy=E2=80=9D is a slippery slope when it = comes to interoperability. Anyway, I can=E2=80=99t find anything in the = email archive that sheds any light on my original question. The text has = been consistent since before RFC 3730, so maybe it=E2=80=99s not as = confusing as I thought it was this morning.<o:p = class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; = font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span = style=3D"font-family: Calibri, sans-serif; color: rgb(153, 51, 102);" = class=3D""> </span></div><div class=3D""><div style=3D"margin: 0in = 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" = class=3D""><span style=3D"font-size: 11pt; font-family: Calibri, = sans-serif; color: rgb(153, 51, 102);" class=3D"">Scott</span><span = style=3D"font-family: Calibri, sans-serif; color: rgb(153, 51, 102);" = class=3D""><o:p class=3D""></o:p></span></div></div><div style=3D"margin: = 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', = serif;" class=3D""><span style=3D"font-family: Calibri, sans-serif; = color: rgb(153, 51, 102);" class=3D""> </span></div><div = style=3D"border-style: none none none solid; border-left-color: blue; = border-left-width: 1.5pt; padding: 0in 0in 0in 4pt;" class=3D""><div = class=3D""><div style=3D"border-style: solid none none; = border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: = 3pt 0in 0in;" class=3D""><div style=3D"margin: 0in 0in 0.0001pt; = font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><b = class=3D""><span style=3D"font-size: 10pt; font-family: Tahoma, = sans-serif;" class=3D"">From:</span></b><span style=3D"font-size: 10pt; = font-family: Tahoma, sans-serif;" class=3D""><span = class=3D"Apple-converted-space"> </span>provreg [<a = href=3D"mailto:[email protected]" style=3D"color: purple; = text-decoration: underline;" = class=3D"">mailto:[email protected]</a>]<span = class=3D"Apple-converted-space"> </span><b class=3D"">On Behalf = Of<span class=3D"Apple-converted-space"> </span></b>Roger D = Carney<br class=3D""><b class=3D"">Sent:</b><span = class=3D"Apple-converted-space"> </span>Friday, September 11, 2015 = 2:18 PM<br class=3D""><b class=3D"">To:</b><span = class=3D"Apple-converted-space"> </span><a = href=3D"mailto:[email protected]" style=3D"color: purple; = text-decoration: underline;" class=3D"">[email protected]</a><br = class=3D""><b class=3D"">Subject:</b><span = class=3D"Apple-converted-space"> </span>Re: [provreg] Inconsistent = Domain Status Value Guidance in RFC 5731<o:p = class=3D""></o:p></span></div></div></div><div style=3D"margin: 0in 0in = 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" = class=3D""><o:p class=3D""> </o:p></div><div style=3D"margin: 0in = 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" = class=3D""><span style=3D"color: rgb(31, 73, 125);" class=3D"">+1 Jim, = this is how I read it as well and it does make sense to me. And = like Jim, I am not sure why a server would not return the status(es) and = we would request that they do, but I do not see a problem with how the = RFC is written.<o:p class=3D""></o:p></span></div><div style=3D"margin: = 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', = serif;" class=3D""><span style=3D"color: rgb(31, 73, 125);" = class=3D""> </span></div><div style=3D"margin: 0in 0in 0.0001pt; = font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span = style=3D"color: rgb(31, 73, 125);" class=3D""> </span></div><div = style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times = New Roman', serif;" class=3D""><span style=3D"color: rgb(31, 73, 125);" = class=3D"">Thanks<o:p class=3D""></o:p></span></div><div style=3D"margin: = 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', = serif;" class=3D""><span style=3D"color: rgb(31, 73, 125);" = class=3D"">Roger<o:p class=3D""></o:p></span></div><div style=3D"margin: = 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', = serif;" class=3D""><span style=3D"color: rgb(31, 73, 125);" = class=3D""> </span></div><div style=3D"margin: 0in 0in 0.0001pt; = font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span = style=3D"color: rgb(31, 73, 125);" class=3D""> </span></div><div = class=3D""><div style=3D"border-style: solid none none; = border-top-color: rgb(225, 225, 225); border-top-width: 1pt; padding: = 3pt 0in 0in;" class=3D""><div style=3D"margin: 0in 0in 0.0001pt; = font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><b = class=3D""><span style=3D"font-size: 11pt; font-family: Calibri, = sans-serif;" class=3D"">From:</span></b><span style=3D"font-size: 11pt; = font-family: Calibri, sans-serif;" class=3D""><span = class=3D"Apple-converted-space"> </span>provreg [<a = href=3D"mailto:[email protected]" style=3D"color: purple; = text-decoration: underline;" = class=3D"">mailto:[email protected]</a>]<span = class=3D"Apple-converted-space"> </span><b class=3D"">On Behalf = Of<span class=3D"Apple-converted-space"> </span></b>Gould, James<br = class=3D""><b class=3D"">Sent:</b><span = class=3D"Apple-converted-space"> </span>Friday, September 11, 2015 = 7:00 AM<br class=3D""><b class=3D"">To:</b><span = class=3D"Apple-converted-space"> </span>Hollenbeck, Scott<br = class=3D""><b class=3D"">Cc:</b><span = class=3D"Apple-converted-space"> </span><a = href=3D"mailto:[email protected]" style=3D"color: purple; = text-decoration: underline;" class=3D"">[email protected]</a><br = class=3D""><b class=3D"">Subject:</b><span = class=3D"Apple-converted-space"> </span>Re: [provreg] Inconsistent = Domain Status Value Guidance in RFC 5731<o:p = class=3D""></o:p></span></div></div></div><div style=3D"margin: 0in 0in = 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" = class=3D""><o:p class=3D""> </o:p></div><div class=3D""><div = style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times = New Roman', serif;" class=3D"">Scott,<o:p = class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in = 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" = class=3D""><o:p class=3D""> </o:p></div></div><div style=3D"margin: = 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', = serif;" class=3D"">It doesn=E2=80=99t =E2=80=9Ctickle any memories=E2=80=9D= , but making the status optional (=E2=80=9CZero or more OPTIONAL=E2=80=9D)= in the info response leaves it up to server policy whether or not to = return =E2=80=9Cthe at least one associated status value". It = makes sense in describing the statuses in section 2.3 that there must be = at least one status, and leave the return of the statuses optional in = the info response based on server policy. I=E2=80=99m not sure why = the server would not want to return the statuses, but the protocol = supports such a policy. <span = class=3D"Apple-converted-space"> </span><o:p = class=3D""></o:p></div><div class=3D""><div style=3D"margin: 0in 0in = 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" = class=3D""><o:p class=3D""> </o:p></div><div class=3D""><div = class=3D""><div style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; = font-family: 'Times New Roman', serif;" class=3D""><span = style=3D"font-size: 11.5pt; font-family: Calibri, sans-serif;" = class=3D"">=E2=80=94</span><span style=3D"font-size: 9pt; font-family: = Verdana, sans-serif;" class=3D""><o:p class=3D""></o:p></span></div><div = style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times = New Roman', serif; -webkit-text-stroke-width: 0px; word-spacing: 0px;" = class=3D""><span style=3D"font-size: 9pt; font-family: Verdana, = sans-serif;" class=3D""> </span></div><p class=3D"MsoNormal" = style=3D"margin: 0in 0in 12pt; font-size: 12pt; font-family: 'Times New = Roman', serif; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><span = style=3D"font-size: 11pt; font-family: Calibri, sans-serif;" = class=3D"">JG</span><span style=3D"font-size: 9pt; font-family: Verdana, = sans-serif;" class=3D""><o:p class=3D""></o:p></span></p></div><div = style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times = New Roman', serif;" class=3D""><span style=3D"font-size: 9pt; = font-family: Verdana, sans-serif;" class=3D""><br class=3D""><span = id=3D"cid:[email protected]"><image001.png></span></spa= n><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif;" = class=3D""><br class=3D""></span><span style=3D"font-family: Times, = serif;" class=3D""><br class=3D""></span><b class=3D""><span = style=3D"font-size: 10pt; font-family: Helvetica, sans-serif; color: = rgb(0, 106, 170);" class=3D"">James Gould<br class=3D""></span></b><span = style=3D"font-size: 10pt; font-family: Helvetica, sans-serif; color: = rgb(107, 109, 113);" class=3D"">Distinguished Engineer<br class=3D""><a = href=3D"x-msg://42/[email protected]" style=3D"color: purple; = text-decoration: underline;" class=3D"">[email protected]</a><br = class=3D""><br class=3D"">703-948-3271<br class=3D"">12061 Bluemont = Way<br class=3D"">Reston, VA 20190<br class=3D""><br = class=3D""></span><span style=3D"font-size: 10pt; font-family: = Helvetica, sans-serif; color: rgb(0, 106, 170);" class=3D""><a = href=3D"http://verisigninc.com/" style=3D"color: purple; = text-decoration: underline;" class=3D"">VerisignInc.com</a></span><span = style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" = class=3D""></span><o:p class=3D""></o:p></div></div><div style=3D"margin: = 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', = serif;" class=3D""><o:p class=3D""> </o:p></div><div = class=3D""><blockquote style=3D"margin-top: 5pt; margin-bottom: 5pt;" = class=3D""><div class=3D""><div style=3D"margin: 0in 0in 0.0001pt; = font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D"">On = Sep 11, 2015, at 7:28 AM, Hollenbeck, Scott <<a = href=3D"mailto:[email protected]" style=3D"color: purple; = text-decoration: underline;" class=3D"">[email protected]</a>> = wrote:<o:p class=3D""></o:p></div></div><div style=3D"margin: 0in 0in = 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" = class=3D""><o:p class=3D""> </o:p></div><div class=3D""><div = style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times = New Roman', serif;" class=3D"">I received a mail note from someone = asking about a difference in the text that appears in RFC 5731 and the = schema that is supposed to support that text. First, the text from = Section 2.3:<br class=3D""><br class=3D"">"A domain object MUST always = have at least one associated status value".<br class=3D""><br = class=3D"">Text from Section 3.1.2 (info response):<br class=3D""><br = class=3D"">"Zero or more OPTIONAL <domain:status> elements that = contain the current status descriptors associated with the domain"<br = class=3D""><br class=3D"">The schema matches the 3.1.2 text. I can't = remember why or how we ended up with text that says "MUST always have at = least one" in one section and "Zero or more OPTIONAL" in another = section. Does this tickle any memories for anyone?<br class=3D""><br = class=3D"">Scott<br class=3D""><br = class=3D"">_______________________________________________<br = class=3D"">provreg mailing list<br class=3D""><a = href=3D"mailto:[email protected]" style=3D"color: purple; = text-decoration: underline;" class=3D"">[email protected]</a><br = class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/provreg" = style=3D"color: purple; text-decoration: underline;" = class=3D"">https://www.ietf.org/mailman/listinfo/provreg</a><o:p = class=3D""></o:p></div></div></blockquote></div><div style=3D"margin: = 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', = serif;" class=3D""><o:p = class=3D""> </o:p></div></div></div></div><span style=3D"font-family:= Helvetica; font-size: 12px; font-style: normal; font-variant: normal; = font-weight: normal; letter-spacing: normal; line-height: normal; = orphans: auto; text-align: start; text-indent: 0px; text-transform: = none; white-space: normal; widows: auto; word-spacing: 0px; = -webkit-text-stroke-width: 0px; float: none; display: inline = !important;" = class=3D"">_______________________________________________</span><br = style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; = font-variant: normal; font-weight: normal; letter-spacing: normal; = line-height: normal; orphans: auto; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; widows: auto; word-spacing: = 0px; -webkit-text-stroke-width: 0px;" class=3D""><span = style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; = font-variant: normal; font-weight: normal; letter-spacing: normal; = line-height: normal; orphans: auto; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; widows: auto; word-spacing: = 0px; -webkit-text-stroke-width: 0px; float: none; display: inline = !important;" class=3D"">provreg mailing list</span><br = style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; = font-variant: normal; font-weight: normal; letter-spacing: normal; = line-height: normal; orphans: auto; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; widows: auto; word-spacing: = 0px; -webkit-text-stroke-width: 0px;" class=3D""><a = href=3D"mailto:[email protected]" style=3D"color: purple; = text-decoration: underline; font-family: Helvetica; font-size: 12px; = font-style: normal; font-variant: normal; font-weight: normal; = letter-spacing: normal; line-height: normal; orphans: auto; text-align: = start; text-indent: 0px; text-transform: none; white-space: normal; = widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" = class=3D"">[email protected]</a><br style=3D"font-family: Helvetica; = font-size: 12px; font-style: normal; font-variant: normal; font-weight: = normal; letter-spacing: normal; line-height: normal; orphans: auto; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: = 0px;" class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/provreg"= style=3D"color: purple; text-decoration: underline; font-family: = Helvetica; font-size: 12px; font-style: normal; font-variant: normal; = font-weight: normal; letter-spacing: normal; line-height: normal; = orphans: auto; text-align: start; text-indent: 0px; text-transform: = none; white-space: normal; widows: auto; word-spacing: 0px; = -webkit-text-stroke-width: 0px;" = class=3D"">https://www.ietf.org/mailman/listinfo/provreg</a></div></blockq= uote></div><br class=3D""></body></html>= --Apple-Mail=_6985C8D0-3691-487F-86D1-E09E5495128F-- --===============3254409517960093208== 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 --===============3254409517960093208==--