Re: [secdir] SecDir review of draft-ietf-tsvwg-rsvp-l3vpn-02

Magnus Westerlund <magnus.westerlund@ericsson.com> Thu, 29 October 2009 15:23 UTC

Return-Path: <magnus.westerlund@ericsson.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 BFD103A6783; Thu, 29 Oct 2009 08:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.234
X-Spam-Level:
X-Spam-Status: No, score=-6.234 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 ZhR8QT3Uwh7A; Thu, 29 Oct 2009 08:23:12 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 9DE743A6802; Thu, 29 Oct 2009 08:23:11 -0700 (PDT)
X-AuditID: c1b4fb3c-b7b3fae00000105f-62-4ae9b36ddad6
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id F8.D1.04191.D63B9EA4; Thu, 29 Oct 2009 16:23:26 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 29 Oct 2009 16:23:25 +0100
Received: from [147.214.183.163] ([147.214.183.163]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 29 Oct 2009 16:23:25 +0100
Message-ID: <4AE9B36D.1020403@ericsson.com>
Date: Thu, 29 Oct 2009 16:23:25 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Stefan Santesson <stefan@aaa-sec.com>
References: <C666D4B1.2C65%stefan@aaa-sec.com>
In-Reply-To: <C666D4B1.2C65%stefan@aaa-sec.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 29 Oct 2009 15:23:25.0700 (UTC) FILETIME=[C25CE440:01CA58AB]
X-Brightmail-Tracker: AAAAAA==
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Francois le Faucheur <flefauch@cisco.com>, Bruce Davie <bsd@cisco.com>, secdir@ietf.org, iesg@ietf.org, Ashok Narayanan <ashokn@cisco.com>, James Polk <jmpolk@cisco.com>
Subject: Re: [secdir] SecDir review of draft-ietf-tsvwg-rsvp-l3vpn-02
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: Thu, 29 Oct 2009 15:23:13 -0000

Hi Stefan,

Are you happy with the new version?

I will put this document on the agenda for the IESG call the week after
IETF. If you have serious grief then please tell me quickly so that I
can pull the document from the agenda.

Cheers

Magnus

Stefan Santesson skrev:
> 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.
> 
> This specification define a set of procedures to overcome challenges
> with deployment of Resource Reservation Protocols over BGP/MPLS VPNs.
> 
> The BGP/MPLS VPN (RFC 4364) is a VPN technique that doesn't rely
> encryption to ensure secrecy or message integrity. The security
> properties are instead dependent on the security of the network
> infrastructure.
> 
> It appears that this draft makes a serious effort to describe and
> analyze relevant security considerations. With my limited expertise in
> this particular area I can't find any thing that is obviously missing.
> 
> However, one question that comes to my mind, which might be worth
> looking at from a security perspective, is whether the procedures
> introduced by this document requires the communication to be unencrypted
> and if so, whether deployment of this protocol blocks or prevents
> legitimate use of e.g. IPsec based VPN as discussed in RFC 4364 and RFC
> 4023. If this is the case, should it be discussed in the security
> considerations section?
> 
> 
> *Stefan Santesson
> *AAA-sec.com
> 
> 
> 
> 
> 


-- 

Magnus Westerlund

IETF Transport Area Director
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------