Re: [Errata Verified] RFC7889 (5726)
"Stan Kalisch" <[email protected]> Mon, 20 May 2019 19:09:44 -0400
| Newsgroups | gmane.ietf.imapext |
|---|---|
| Message-ID | <[email protected]> |
--===============7469213210977744282==
Content-Type: multipart/alternative; boundary=5a432961747a4ca0900d684be6384d66
--5a432961747a4ca0900d684be6384d66
Content-Type: text/plain
On Mon, May 20, 2019, at 6:36 PM, RFC Errata System wrote:
> ----- Verifier notes -----
> Yes, this is an error: it comes from a combination of the RFC Editor style of double-spacing between sentences, the construction of the examples in XML in a manner that doesn't distinguish them from sentences, and the fact that it's nearly impossible to notice the situation when one is giving a final review.
>
> Editorial, though, because it's in examples. The ABNF is the authoritative place, and that's correct.
This is helpful to know, and when you put it like that, makes complete sense to me. I suppose part of my confusion stems from the fact that I reported an erratum for an example in an RFC about two years ago and it was verified as technical. Is this something that varies across disciplines? This may be helpful information for those who report errors but are not as familiar as others with the IETF and RFC Editor's process.
Thanks,
Stan
>
> --------------------------------------
> RFC7889 (draft-ietf-imapapnd-appendlimit-extension-10)
> --------------------------------------
> Title : The IMAP APPENDLIMIT Extension
> Publication Date : May 2016
> Author(s) : J. SrimushnamBoovaraghamoorthy, N. Bisht
> Category : PROPOSED STANDARD
> Source : IMAP APPEND Extensions
> Area : Applications and Real-Time
> Stream : IETF
> Verifying Party : IESG
>
--5a432961747a4ca0900d684be6384d66
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">On Mon, May 20, 2019, at 6:36 PM, RFC Errata System wrote:=
<br></div><blockquote type=3D"cite" id=3D"qt"><div style=3D"font-family:=
Arial;">----- Verifier notes -----<br></div><div style=3D"font-family:Ar=
ial;">Yes, this is an error: it comes from a combination of the RFC Edit=
or style of double-spacing between sentences, the construction of the ex=
amples in XML in a manner that doesn't distinguish them from sentences, =
and the fact that it's nearly impossible to notice the situation when on=
e is giving a final review.<br></div><div style=3D"font-family:Arial;"><=
br></div><div style=3D"font-family:Arial;">Editorial, though, because it=
's in examples. The ABNF is the authoritative place, and that's co=
rrect.<br></div></blockquote><div style=3D"font-family:Arial;"><br></div=
><div style=3D"font-family:Arial;">This is helpful to know, and when you=
put it like that, makes complete sense to me. I suppose part of m=
y confusion stems from the fact that I reported an erratum for an exampl=
e in an RFC about two years ago and it was verified as technical. =
Is this something that varies across disciplines? This may be help=
ful information for those who report errors but are not as familiar as o=
thers with the IETF and RFC Editor's process.<br></div><div style=3D"fon=
t-family:Arial;"><br></div><div style=3D"font-family:Arial;"><br></div><=
div style=3D"font-family:Arial;">Thanks,<br></div><div style=3D"font-fam=
ily:Arial;">Stan</div><div style=3D"font-family:Arial;"><br></div><block=
quote type=3D"cite" id=3D"qt"><div style=3D"font-family:Arial;"><br></di=
v><div style=3D"font-family:Arial;">------------------------------------=
--<br></div><div style=3D"font-family:Arial;">RFC7889 (draft-ietf-imapap=
nd-appendlimit-extension-10)<br></div><div style=3D"font-family:Arial;">=
--------------------------------------<br></div><div style=3D"font-famil=
y:Arial;">Title &nb=
sp; : The IMAP APPENDLIMIT Extension<br></div><d=
iv style=3D"font-family:Arial;">Publication Date : May=
2016<br></div><div style=3D"font-family:Arial;">Author(s) &n=
bsp; : J. SrimushnamBoovaragha=
moorthy, N. Bisht<br></div><div style=3D"font-family:Arial;">Category&nb=
sp; : PROPOS=
ED STANDARD<br></div><div style=3D"font-family:Arial;">Source  =
; : IM=
AP APPEND Extensions<br></div><div style=3D"font-family:Arial;">Area&nbs=
p; &nbs=
p; : Applications and Real-Time<br></div><div style=3D"font-=
family:Arial;">Stream &nb=
sp; : IETF<br></div><div style=3D"font-family:Ar=
ial;">Verifying Party : IESG<br></div><div style=
=3D"font-family:Arial;"><br></div></blockquote><div style=3D"font-family=
:Arial;"><br></div></body></html>
--5a432961747a4ca0900d684be6384d66--
--===============7469213210977744282==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
imapext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imapext
--===============7469213210977744282==--