RE: draft-kulmala-l3vpn-interas-option-d-02

"Martin Halstead" <mhalstead@nexagent.com> Thu, 20 April 2006 10:33 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWWTG-0003O8-Pl; Thu, 20 Apr 2006 06:33:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWWTG-0003O2-9x for l3vpn@ietf.org; Thu, 20 Apr 2006 06:33:10 -0400
Received: from hostedexchange.hostedservice.com ([217.28.130.38]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWWTF-0006eh-1H for l3vpn@ietf.org; Thu, 20 Apr 2006 06:33:10 -0400
Received: from THHS2EXBE2X.hostedservice2.net ([192.168.33.21]) by hostedexchange.hostedservice.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 20 Apr 2006 11:33:04 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 20 Apr 2006 11:33:02 +0100
Message-ID: <B2B4D3618441D941B811329A672FD64E01032311@THHS2EXBE2X.hostedservice2.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-kulmala-l3vpn-interas-option-d-02
Thread-Index: AcZjFw7si+ih4riVTV22ShRaAd1KXQBTQ1mA
From: Martin Halstead <mhalstead@nexagent.com>
To: Ron Bonica <rbonica@juniper.net>
X-OriginalArrivalTime: 20 Apr 2006 10:33:04.0022 (UTC) FILETIME=[CE2DCB60:01C66465]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: l3vpn@ietf.org
Subject: RE: draft-kulmala-l3vpn-interas-option-d-02
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

Ron

You make a good point - I think that 'draft-ietf-l3vpn-rt-constrain'
does play well with 'option d' as a means to restrict VPN route updates
to interested parties only. This could apply when a single ASBR is
peered with more than one ASBR (in my opinion a very good thing). The
distribution graphs (and associated policies) would then sit between
peered ASBRs, rather than across ASes as described in the 'constrain'
draft.

BTW - I think that in the case of L3 VPN, the 'constrain' draft should
add that the option is only applicable to multi-AS options 'b' and 'c'
and by implication will not work with option 'a'.

Regards

Martin
mhalstead@nexagent.com

-----Original Message-----
From: Ron Bonica [mailto:rbonica@juniper.net] 
Sent: 18 April 2006 19:37
To: Martin Halstead
Cc: l3vpn@ietf.org
Subject: Re: draft-kulmala-l3vpn-interas-option-d-02

Martin,

BTW, would Option D play well with Constrained VPN Route Distribution (
                draft-ietf-l3vpn-rt-constrain)?

                                Ron