Subject: [mpls] draft-ietf-mpls-tp-security-framework-02 WG LC comments

From: Gregory Mirsky <[email-masked]>
Date: Fri, 4 Nov 2011 13:49:06 -0400

Dear Authors, et al.,
Please consider my comments listed below:
*       Section 1.1 "There are also needs for MPLS-TP and MPLS interworking" seems ambiguous. Perhaps "There are also needs for MPLS-TP and non-MPLS-TP interworking".
*       Section 1.2 "G-ACh (control plane attack, DoS attack, message intercept, etc.)" I think that G-ACh might be used to launch attack on the data plane, e.g. trigger protection switchover or lock a connection, as well.
*       Section 1.2 "Data plane authentication" isn't it part of G-ACh issues?
*       Section 3 "...the data plane should continue to forward packets without being impacted". I think that separation of Control Plane and Data Plane implies that all enabled in the data plane operations, e.g. OAM, protection, will act without impact in case control plane and/or management plane are under attack.
*       Section 3. Split requirements into single statements without "as well as" and enumerate them
*       Section 4.2 might add 'c' to list of possible attacks via G-ACh to trigger protection switchover and/or restoration; locking of a transport connection.

        Regards,
                Greg