[secdir] Secdir last call review of draft-ietf-spring-segment-routing-mpls-18

Linda Dunbar <Linda.dunbar@huawei.com> Fri, 01 March 2019 00:21 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar <Linda.dunbar@huawei.com>
To: secdir@ietf.org
Cc: spring@ietf.org, draft-ietf-spring-segment-routing-mpls.all@ietf.org, ietf@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155139967435.28679.14505997897302676815@ietfa.amsl.com>
Date: Thu, 28 Feb 2019 16:21:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/50tXdjK7EmTCELk0GgGg35O6_ec>
Subject: [secdir] Secdir last call review of draft-ietf-spring-segment-routing-mpls-18

Reviewer: Linda Dunbar
Review result: Ready

Reviewer: Linda Dunbar
Review result: Ready

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the security area directors.
 Document editors and WG chairs should treat these comments just like any other
last call comments.

The document provides the detailed explanation of SR-MPLS processing in
addition to RFC 8402. Since SR-MPLS are in the trusted domain, it is assumed
that there is no malicious attacks to the nodes for the data plane and control
plane.  RFC8402 already has the good description on the Security Consideration
for both SR-MPLS & SRv6.

Linda Dunbar

[secdir] Secdir last call review of draft-ietf-sp… Linda Dunbar