Re: [OPSAWG] [Editorial Errata Reported] RFC9291 (7162)

["Rob Wilton (rwilton)" <[e-mail]>]

Yes.  I've just verified it.  Nikolai, thanks for raising it.

Regards,
Rob



From: Joe Clarke (jclarke) <[e-mail]>
Sent: 13 October 2022 13:48
To: [e-mail]; RFC Errata System <[e-mail]>; [e-mail]
Cc: [e-mail]; [e-mail]; Rob Wilton (rwilton) <[e-mail]>
Subject: Re: [Editorial Errata Reported] RFC9291 (7162)

Agreed.  Rob?

Joe

From: OPSAWG <[e-mail]<mailto:[e-mail]>> on behalf of [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Date: Thursday, October 13, 2022 at 7:29 AM
To: RFC Errata System <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Subject: Re: [OPSAWG] [Editorial Errata Reported] RFC9291 (7162)
Hi Nikolai, all,

Thank you for reporting this.

This editorial erratum should be accepted. Thanks.

Cheers,
Med

> -----Message d'origine-----
> De : RFC Errata System <[e-mail]<mailto:[e-mail]>>
> Envoyé : jeudi 13 octobre 2022 13:23
> À : [e-mail]<mailto:[e-mail]>
> Cc : [e-mail]<mailto:[e-mail]>; BOUCADAIR Mohamed INNOV/NET
> <[e-mail]<mailto:[e-mail]>>;
> [e-mail]<mailto:[e-mail]>;
> [e-mail]<mailto:[e-mail]>; luis-
> [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
> Objet : [Editorial Errata Reported] RFC9291 (7162)
>
> The following errata report has been submitted for RFC9291, "A
> YANG Network Data Model for Layer 2 VPNs".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7162
>
> --------------------------------------
> Type: Editorial
> Reported by: Nikolai Malykh <[e-mail]<mailto:[e-mail]>>
>
> Section: 9
>
> Original Text
> -------------
>    'ethernet-segments' and 'vpn-services':  An attacker who is
> able to
>       access network nodes can undertake various attacks, such as
>       deleting a running L2VPN service, interrupting all the
> traffic of
>       a client.  In addition, an attacker may modify the
> attributes of a
>       running service (e.g., QoS, bandwidth) or an ES, leading to
>       malfunctioning of the service and therefore to SLA
> violations.  In
>       addition, an attacker could attempt to create an L2VPN
> service,
>       add a new network access, or intercept/redirect the traffic
> to a
>       non-authorized node.  In addition to using NACM to prevent
>       authorized access, such activity can be detected by
> adequately
>       monitoring and tracking network configuration changes.
>
>
> Corrected Text
> --------------
>    'ethernet-segments' and 'vpn-services':  An attacker who is
> able to
>       access network nodes can undertake various attacks, such as
>       deleting a running L2VPN service, interrupting all the
> traffic of
>       a client.  In addition, an attacker may modify the
> attributes of a
>       running service (e.g., QoS, bandwidth) or an ES, leading to
>       malfunctioning of the service and therefore to SLA
> violations.  In
>       addition, an attacker could attempt to create an L2VPN
> service,
>       add a new network access, or intercept/redirect the traffic
> to a
>       non-authorized node.  In addition to using NACM to prevent
>       unauthorized access, such activity can be detected by
> adequately
>       monitoring and tracking network configuration changes.
>
>
> Notes
> -----
> Typo in last sentence, should be "unauthorized".
>
> 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 can log
> in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC9291 (draft-ietf-opsawg-l2nm-19)
> --------------------------------------
> Title               : A YANG Network Data Model for Layer 2 VPNs
> Publication Date    : September 2022
> Author(s)           : M. Boucadair, Ed., O. Gonzalez de Dios, Ed.,
> S. Barguil, L. Munoz
> Category            : PROPOSED STANDARD
> Source              : Operations and Management Area Working Group
> 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.

_______________________________________________
OPSAWG mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/opsawg