Re: [sieve] [Editorial Errata Reported] RFC5804 (7825)

[Alexey Melnikov <[e-mail]>]

Hi Rebecca,

I agree this is technical.

The text in the Notes comes from Section 2.3 of the RFC 5804. The 
proposed erratum is correct and should be approved.

Best Regards,

Alexey


On 28/02/2024 18:58, Rebecca VanRheenen wrote:
> Hi Murray, Francesca, and Orie,
>
> We are unable to verify this erratum that the submitter marked as editorial, so we changed the Type to “Technical”. As Stream Approver, please review and set the Status and Type accordingly (see the definitions at https://www.rfc-editor.org/errata-definitions/).
>
> RFC 5804 came from the sieve WG, which has closed.
>
> You may review the report at:
> https://www.rfc-editor.org/errata/eid7825
>
> Information on how to verify errata reports can be found at:
> https://www.rfc-editor.org/how-to-verify/
>
> Further information on errata can be found at:
> https://www.rfc-editor.org/errata.php
>
> Thank you,
> RFC Editor/rv
>
>
>
>> On Feb 27, 2024, at 8:28 AM, RFC Errata System <[e-mail]> wrote:
>>
>> The following errata report has been submitted for RFC5804,
>> "A Protocol for Remotely Managing Sieve Scripts".
>>
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid7825
>>
>> --------------------------------------
>> Type: Editorial
>> Reported by: Mauro De Gennaro <[e-mail]>
>>
>> Section: 4
>>
>> Original Text
>> -------------
>> response-logout       = response-oknobye
>>
>>
>> Corrected Text
>> --------------
>> response-logout       = response-ok
>>
>>
>> Notes
>> -----
>> The client sends the LOGOUT command when it is finished with a
>>    connection and wishes to terminate it.  The server MUST reply with an
>>    OK response.  The server MUST ignore commands issued by the client
>>    after the LOGOUT command.
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". (If it is spam, it
>> will be removed shortly by the RFC Production Center.) Please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party
>> will log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC5804 (draft-ietf-sieve-managesieve-09)
>> --------------------------------------
>> Title               : A Protocol for Remotely Managing Sieve Scripts
>> Publication Date    : July 2010
>> Author(s)           : A. Melnikov, Ed., T. Martin
>> Category            : PROPOSED STANDARD
>> Source              : Sieve Mail Filtering Language
>> Area                : Applications
>> Stream              : IETF
>> Verifying Party     : IESG
>>