Re: [L1vpn] Your Discusses and Comments on draft-ietf-l1vpn-bgp-auto-discovery-04.txt

<Pasi.Eronen@nokia.com> Fri, 16 May 2008 11:02 UTC

Return-Path: <l1vpn-bounces@ietf.org>
X-Original-To: l1vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l1vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E3CC03A6B19; Fri, 16 May 2008 04:02:38 -0700 (PDT)
X-Original-To: l1vpn@core3.amsl.com
Delivered-To: l1vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4482C3A69E1 for <l1vpn@core3.amsl.com>; Thu, 15 May 2008 23:37:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.498
X-Spam-Level:
X-Spam-Status: No, score=-5.498 tagged_above=-999 required=5 tests=[AWL=-0.099, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_14=0.6, 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 7XgzkKDGohCC for <l1vpn@core3.amsl.com>; Thu, 15 May 2008 23:37:11 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 1443B3A6ABF for <l1vpn@ietf.org>; Thu, 15 May 2008 23:37:10 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m4G6aJwD031310; Fri, 16 May 2008 09:36:35 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 May 2008 09:36:26 +0300
Received: from vaebe104.NOE.Nokia.com ([10.160.244.59]) by vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 May 2008 09:36:25 +0300
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 16 May 2008 09:36:24 +0300
Message-ID: <1696498986EFEC4D9153717DA325CB72A137A0@vaebe104.NOE.Nokia.com>
In-Reply-To: <02a101c8b5ee$c6768880$0200a8c0@your029b8cecfe>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Your Discusses and Comments on draft-ietf-l1vpn-bgp-auto-discovery-04.txt
Thread-Index: Aci177a/kieCGXGfTrmas+aNmw2hewBL24Sg
References: <02a101c8b5ee$c6768880$0200a8c0@your029b8cecfe>
From: Pasi.Eronen@nokia.com
To: adrian@olddog.co.uk, dward@cisco.com, tim.polk@nist.gov
X-OriginalArrivalTime: 16 May 2008 06:36:25.0330 (UTC) FILETIME=[29CE1520:01C8B71F]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Fri, 16 May 2008 04:02:37 -0700
Cc: l1vpn@ietf.org
Subject: Re: [L1vpn] Your Discusses and Comments on draft-ietf-l1vpn-bgp-auto-discovery-04.txt
X-BeenThere: l1vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@ietf.org>
List-Help: <mailto:l1vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: l1vpn-bounces@ietf.org
Errors-To: l1vpn-bounces@ietf.org

Hi Adrian,

I've cleared my discuss.

Best regards,
Pasi 

> -----Original Message-----
> From: ext Adrian Farrel [mailto:adrian@olddog.co.uk] 
> Sent: 14 May, 2008 21:17
> To: dward@cisco.com; Eronen Pasi (Nokia-NRC/Helsinki); 
> tim.polk@nist.gov
> Cc: Hamid Ould-Brahim; takeda.tomonori@lab.ntt.co.jp; l1vpn@ietf.org
> Subject: Your Discusses and Comments on 
> draft-ietf-l1vpn-bgp-auto-discovery-04.txt
> 
> Hi,
> 
> The editor has made a new version of this draft based on your 
> issues and the 
> subsequent email exchanges.
> 
> > 
> http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-bgp-auto-
> discovery-05.txt
> 
> We hope that the changes (summarised below alongside your 
> coments) address 
> your points and you can clear your Discusses.
> 
> Thanks,
> Adrian
> 
> ===
> > Pasi Eronen:
> >
> > Discuss [2008-05-05]:
> > Process comment: Sandy Murphy's SecDir review needs a response.
> >
> > As noted in Sandy Murphy's SecDir review, this document seems to
> > expand the L1VPN concept significantly beyond the scope of RFC 4847
> > and draft-ietf-l1vpn-applicability-basic-mode, both of which
> > explicitly rule out inter-as/inter-provider L1VPNs.  Expanding the
> > scope of inter-AS/inter-provider VPNs makes the assumption about
> > transitive trust of all BGP speakers rather dubious.
> 
> The I-D has been updated to make clear that 
> inter-AS/inter-provider are out 
> of scope. The following paragraph has been added to the end 
> of Section 2.
> 
>    Although multi-AS L1VPNs are currently out of scope for the Basic
>    Mode, the mechanisms defined in this document appear to be easily
>    applicable to a multi-AS scenario should such a need arise in the
>    future. At that time additional work may be required to examine
>    various aspects including security.
> 
> ===
> > Pasi Eronen:
> >
> > Comment [2008-05-05]:
> > Sandy's SecDir review also identified a number of places that would
> > benefit from some clarification of the text, and provided editorial
> > comments that should be taken into acccount.
> 
> We believe these have been picked up, discussed with Sandy as 
> necessary, and 
> fixed in the new I-D.
> 
> ===
> > Tim Polk:
> >
> > Comment [2008-05-08]:
> > Sandy Murphy has asked what happens if the basic security assumption
> > does not hold.
> >
> > Given the importance of the basic trust assumption - all 
> the participants
> > are trustworthy, and trust is transitive - it would also be 
> nice if the
> > security considerations noted *why* the wg feels this is a 
> reasonable
> > assumption.  (I assume it is based on the fact that all the 
> peers are
> > members of the same provider network?)
> 
> This is fixed by a simple addition right at the end of 
> Section 6. This 
> points out that the restriction of the technique to a single provider 
> network means that the trust model is much more applicable.
> 
> 
> 
> 
_______________________________________________
L1vpn mailing list
L1vpn@ietf.org
https://www.ietf.org/mailman/listinfo/l1vpn