Re: [Dime] [Editorial Errata Reported] RFC6733 (4210)

[Benoit Claise <[e-mail]>]

Hi Lionel,

I mixed up 2 erratum: 4210 and 4209.
4210 has already been treated.
Sorry for the confusion

Regards, Benoit
> Hi Benoit,
>
> I have already given my view on this errata reported.
> But I let others provide additional feedback if required.
>
> Lionel
>
> -----Message d'origine-----
> De : DiME [mailto:[e-mail]] De la part de [e-mail]
> Envoyé : vendredi 26 décembre 2014 18:35
> À : RFC Errata System; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]
> Cc : [e-mail]; [e-mail]
> Objet : Re: [Dime] [Editorial Errata Reported] RFC6733 (4210)
>
> Diameter is a peer-to-peer protocol and peers are Diameter nodes sharing a Diameter transport connection. Therefore, a "peer" can be either the sender or the receiver of the request, depending on the context.
> I don't think that the proposed correction is justified.
>
> regards,
>
> Lionel
>
> -----Message d'origine-----
> De : RFC Errata System [mailto:[e-mail]]
> Envoyé : vendredi 26 décembre 2014 07:11 À : [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; MORAND Lionel IMT/OLN Cc : [e-mail]; [e-mail]; [e-mail] Objet : [Editorial Errata Reported] RFC6733 (4210)
>
> The following errata report has been submitted for RFC6733, "Diameter Base Protocol".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6733&eid=4210
>
> --------------------------------------
> Type: Editorial
> Reported by: Hans Liu <[e-mail]>
>
> Section: 5.4.3
>
> Original Text
> -------------
>     The Disconnect-Cause AVP (AVP Code 273) is of type Enumerated.  A
>     Diameter node MUST include this AVP in the Disconnect-Peer-Request
>     message to inform the peer of the reason for its intention to shut
>     down the transport connection.  The following values are supported:
>        REBOOTING                         0
>           A scheduled reboot is imminent.  A receiver of a DPR with
>           above result code MAY attempt reconnection.
>        BUSY                              1
>           The peer’s internal resources are constrained, and it has
>           determined that the transport connection needs to be closed.
>           A receiver of a DPR with above result code SHOULD NOT attempt
>           reconnection.
>        DO_NOT_WANT_TO_TALK_TO_YOU        2
>           The peer has determined that it does not see a need for the
>           transport connection to exist, since it does not expect any
>           messages to be exchanged in the near future.  A receiver of a
>           DPR with above result code SHOULD NOT attempt reconnection.
>
> Corrected Text
> --------------
>     The Disconnect-Cause AVP (AVP Code 273) is of type Enumerated.  A
>     Diameter node MUST include this AVP in the Disconnect-Peer-Request
>     message to inform the peer of the reason for its intention to shut
>     down the transport connection.  The following values are supported:
>        REBOOTING                         0
>           A scheduled reboot is imminent.  A receiver of a DPR with
>           above result code MAY attempt reconnection.
>        BUSY                              1
>           The internal resources are constrained, and it has
>           determined that the transport connection needs to be closed.
>           A receiver of a DPR with above result code SHOULD NOT attempt
>           reconnection.
>        DO_NOT_WANT_TO_TALK_TO_YOU        2
>           The node has determined that it does not see a need for the
>           transport connection to exist, since it does not expect any
>           messages to be exchanged in the near future.  A receiver of a
>           DPR with above result code SHOULD NOT attempt reconnection.
>
> Notes
> -----
> The "peer" in 1st paragraph represents the receiver. However in the descriptions for cause values the "peer" represents the sender.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC6733 (draft-ietf-dime-rfc3588bis-33)
> --------------------------------------
> Title               : Diameter Base Protocol
> Publication Date    : October 2012
> Author(s)           : V. Fajardo, Ed., J. Arkko, J. Loughney, G. Zorn, Ed.
> Category            : PROPOSED STANDARD
> Source              : Diameter Maintenance and Extensions
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
> _______________________________________________
> DiME mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dime
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>