Re: [secdir] Review of draft-ietf-mpls-tp-gach-dcn-06

Shawn M Emery <Shawn.Emery@Sun.COM> Mon, 19 October 2009 14:37 UTC

Return-Path: <Shawn.Emery@Sun.COM>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B95128C0FA; Mon, 19 Oct 2009 07:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level:
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99CJwgJiGlK1; Mon, 19 Oct 2009 07:37:07 -0700 (PDT)
Received: from brmea-mail-1.sun.com (brmea-mail-1.Sun.COM [192.18.98.31]) by core3.amsl.com (Postfix) with ESMTP id F3BC328C138; Mon, 19 Oct 2009 07:37:06 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n9JEbD5u016311; Mon, 19 Oct 2009 14:37:13 GMT
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; CHARSET="US-ASCII"; format="flowed"
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KRR00E00MO72K00@mail-amer.sun.com>; Mon, 19 Oct 2009 08:37:13 -0600 (MDT)
Received: from [10.0.0.5] ([unknown] [174.51.225.48]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KRR00D65NA0AZ60@mail-amer.sun.com>; Mon, 19 Oct 2009 08:37:12 -0600 (MDT)
Date: Mon, 19 Oct 2009 08:36:06 -0600
From: Shawn M Emery <Shawn.Emery@Sun.COM>
In-reply-to: <319F18AE86FD41619D03842D26812186@your029b8cecfe>
Sender: Shawn.Emery@Sun.COM
To: Adrian Farrel <Adrian.Farrel@huawei.com>
Message-id: <4ADC7956.2020108@sun.com>
References: <4ADC1C31.6060207@sun.com> <319F18AE86FD41619D03842D26812186@your029b8cecfe>
User-Agent: Thunderbird 2.0.0.23 (X11/20090929)
Cc: mpls-chairs@tools.ietf.org, draft-ietf-mpls-tp-gach-dcn@tools.ietf.org, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] Review of draft-ietf-mpls-tp-gach-dcn-06
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 14:37:08 -0000

Adrian Farrel wrote:
> Thanks for the review, Shawn.
>
>> The security considerations section does exist and describes that DCN 
>> messages are required to have adequate security mechanisms.  The 
>> section doesn't describe what those mechanisms are, but should at 
>> least provide a reference from other MPLS RFC/I-Ds that do.
>
> I'm a little unclear what you are asking for here.
> The draft defines a channel (i.e. a logical data link) down which any 
> packet-based protocol could be run.
> Are you suggesting that this draft should contain a reference to the 
> security mechanisms for each protocol that might be run down the 
> channel? That seems like an impossible task.
>
> We could, I suppose, add text to note that "the MPLS data plane does 
> not include any security mechanisms of its own, therefore it is 
> important that protocols using the DCN apply their own security."

Yes or a reference to something like RFC 3985's security considerations 
section, as it also does a good job in explaining the inherit risks of 
existing packet protocols and possible solutions.

Regards,

-- 
Shawn.