Re: [Supa] BGP and SUPA policy

"Susan Hares" <shares@ndzh.com> Thu, 28 May 2015 10:58 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: supa@ietfa.amsl.com
Delivered-To: supa@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC5C1A88F3 for <supa@ietfa.amsl.com>; Thu, 28 May 2015 03:58:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.455
X-Spam-Level:
X-Spam-Status: No, score=-98.455 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, J_CHICKENPOX_12=0.6, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6EvRTh70zXcZ for <supa@ietfa.amsl.com>; Thu, 28 May 2015 03:58:29 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 136531A88D2 for <supa@ietf.org>; Thu, 28 May 2015 03:58:29 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.178.112;
From: Susan Hares <shares@ndzh.com>
To: 'Juergen Schoenwaelder' <j.schoenwaelder@jacobs-university.de>
References: <024301d08bff$dde57c30$99b07490$@ndzh.com> <20150511154034.GD24192@elstar.local> <005f01d08c22$cbcb2810$63617830$@ndzh.com> <20150527120841.GB41087@elstar.local>
In-Reply-To: <20150527120841.GB41087@elstar.local>
Date: Thu, 28 May 2015 06:58:24 -0400
Message-ID: <009301d09935$380b1070$a8213150$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIoIBMCbwjM/X+bT9sXDwHwU7c6eQJrCRLtAS29UbYCkhxhqJyw0s8g
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/supa/k8k1Mbya4eA8y_22ZMRNBC5e7Ys>
Cc: 'John Strassner' <John.sc.Strassner@huawei.com>, supa@ietf.org
Subject: Re: [Supa] BGP and SUPA policy
X-BeenThere: supa@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This list is to discuss SUPA \(Shared Unified Policy Automation\) related issues." <supa.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/supa>, <mailto:supa-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/supa/>
List-Post: <mailto:supa@ietf.org>
List-Help: <mailto:supa-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/supa>, <mailto:supa-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2015 10:58:30 -0000

Juergen: 

As you have noticed in message to Anees, this definition for prefix lists
has problems. It would be good to send these comments to the rtgwg WG.  You
can either also cross-post to IDR or I will summarize this work to IDR. 

Sue 

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] 
Sent: Wednesday, May 27, 2015 8:09 AM
To: Susan Hares
Cc: 'John Strassner'; supa@ietf.org
Subject: Re: [Supa] BGP and SUPA policy

Thanks Susan,

I finally found the time to read draft-shaikh-rtgwg-policy-model and I think
I roughly understand what it tries to do.

/js

On Mon, May 11, 2015 at 03:43:42PM -0400, Susan Hares wrote:
> Juregen:
> 
> The IDR Working group is progressing the documents for the BGP policy 
> based on a combination of the draft
> http://datatracker.ietf.org/doc/draft-shaikh-idr-bgp-model/   and the
draft:
> http://datatracker.ietf.org/doc/draft-zhdankin-idr-bgp-cfg.   This work
has
> been ongoing for over 18 months.   A merged draft will be out later this
> month. 
> 
> The authors have agreed to start with the policy 
> http://datatracker.ietf.org/doc/draft-shaikh-rtgwg-policy-model, and 
> iterate from this point.
> 
> This is the base BGP work, and upon this foundation other BGP work will be
> expanded.   BGP policy for L2VPN, L3VPN, EVPN is being considered in BESS,
> but it depend on the base BGP work plus extensions to cover other BGP 
> configuration and policy.
> 
> My understanding is that policy is a layered approach going from
application
> to AS/Network layer, to device layer.   Please see my understanding of the
> policy layers below.  I would appreciate any insight you have
> 
> Sue
> 
> Policy layers: 
> Application layer policies (intent based) AS / Network-wide policy 
> (SUPA policies, IDR SLA policies, L3SM policies AS / Network-wide 
> topologies (I2RS client view of topology, ALTO topology) Device policy 
> for dynamic abstract topologies (I2RS agent Topology, I2RS agent RIB, 
> I2RS agent FB-RIBs) Device policy for dynamic policy for protocol 
> (ISIS, OSPF, BGP, SFC, SPRING,
> MPLS)
> Device policy for dynamic routes (ISIS, OSPF, BGP) Device policy for 
> static routes Device policy for interfaces
> 
> 
> -----Original Message-----
> From: Supa [mailto:supa-bounces@ietf.org] On Behalf Of Juergen 
> Schoenwaelder
> Sent: Monday, May 11, 2015 11:41 AM
> To: Susan Hares
> Cc: 'John Strassner'; supa@ietf.org
> Subject: Re: [Supa] BGP and SUPA policy
> 
> On Mon, May 11, 2015 at 11:33:44AM -0400, Susan Hares wrote:
> > John and others: 
> > 
> > Could you please describe how SUPA policy interacts with the BGP 
> > policy and dynamic BGP policy?
> 
> We can try. To avoid misunderstandings, can you tell us which BGP 
> documents we specifically should look at?
> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> 
> _______________________________________________
> Supa mailing list
> Supa@ietf.org
> https://www.ietf.org/mailman/listinfo/supa
> 
> _______________________________________________
> Supa mailing list
> Supa@ietf.org
> https://www.ietf.org/mailman/listinfo/supa

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>