Re: [secdir] SECDIR review of draft-ietf-ccamp-path-key-ero-03

Sure thing, Chris.

The references would be to RFC 5440 and to 
draft-ietf-mpls-mpls-and-gmpls-security-framework-04.txt

Cheers,
Adrian
----- Original Message ----- 
From: "Chris Lonvick" <clonvick@cisco.com>
To: <iesg@ietf.org>; <secdir@ietf.org>; <jpv@cisco.com>; "Rich Bradford" 
<rbradfor@cisco.com>; <adrian@olddog.co.uk>; "Deborah Brungard" 
<dbrungard@att.com>
Sent: Monday, February 02, 2009 9:16 PM
Subject: SECDIR review of draft-ietf-ccamp-path-key-ero-03

> Hi,
>
> 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.
>
> Overall, the document appears to be well written and comprehensive and I 
> have no problem with it proceeding to become an RFC.
>
> I do have one editorial comment.  In Section 4, Security Considerations, 
> the following bullet appears.
> ===
>    - Authenticity of the path key. A concern is that the path key in the
>      PKS will be altered or faked leading to erroneous path key
>      expansion and the use of the wrong CPS. The consequence would be a
>      bad ERO in a Path message causing the LSP to be set up incorrectly
>      resulting in incorrect network resource usage, diversion of traffic
>      to where it can be intercepted, or failure to set up the LSP. These
>      problems can be prevented by protecting the protocol exchanges in
>      PCEP and RSVP-TE using standard security techniques.
> ===
> I feel that the term "standard security techniques" is too vague for a 
> standards track document and would ask you to rephrase the last sentence 
> to be:
> "These problems can be prevented by protecting the protocol exchanges in 
> PCEP and RSVP-TE using the techniques described in [PSEC] and [RFC2205]."
> Or reference other techniques if you have them in mind.
>
> Best regards,
> Chris
> 

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