Dear WG:

We received a good set of volunteers to serve as authors in developing
a document to provide a solid security analysis of SRv6 [1].  Thank
you to all who volunteered!

This is the team the chairs selected:

  Nick Buraglio
  Luis Contreras
  Fernando Gont
  Tal Mizrahi
  Tian Tong


While, as with any other document, the WG will decide on its adoption
and eventual progress, what follows are specifics related to the
chairs' expectations:

(1) The work will consider SRv6 as specified in RFC8402 (Segment Routing
    Architecture), RFC8754 (IPv6 Segment Routing Header (SRH)), RFC8986
    (Segment Routing over IPv6 (SRv6) Network Programming), and other related
    RFCs.  It should consider security-related topics not covered in those
    existing RFCs or that may need further coverage.

(2) The objective is to identify threats, analyze potential mitigation
    mechanisms, and highlight gaps that may affect the deployment of SRv6.
    The proposal of solutions to close any gaps is outside the scope of the
    document.

(3) The document should limit itself to an analysis of SRv6 and not compare it
    with other technologies.


As a first step, the authors will define a high-level outline of the
topics to be covered.   A description of a threat model is a necessary
component.

SRv6 security and this document are on the radar of the IESG, making
them a high-priority work item for the WG.  We expect the work to be
progressed, presented, and reviewed in a timely manner, which should
include periodic updates and discussions on the list and at in-person
and virtual interim meetings (as needed).


Thanks!

Alvaro (for the Chairs)

[1] https://mailarchive.ietf.org/arch/msg/spring/SxNKw2kWw3W3sHoyY32ngRexzeU/

_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Reply via email to