RE: Comments on draft-shaikh-rtgwg-policy-model

Antoni Przygienda <antoni.przygienda@ericsson.com> Mon, 27 July 2015 21:05 UTC

Return-Path: <antoni.przygienda@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21A9E1B33F2 for <rtgwg@ietfa.amsl.com>; Mon, 27 Jul 2015 14:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 h27MQWw0ZhaX for <rtgwg@ietfa.amsl.com>; Mon, 27 Jul 2015 14:05:08 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F1C41B33F7 for <rtgwg@ietf.org>; Mon, 27 Jul 2015 14:04:37 -0700 (PDT)
X-AuditID: c618062d-f799e6d00000329e-56-55b640b5327a
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 73.1F.12958.5B046B55; Mon, 27 Jul 2015 16:31:17 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0210.002; Mon, 27 Jul 2015 17:04:34 -0400
From: Antoni Przygienda <antoni.przygienda@ericsson.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Subject: RE: Comments on draft-shaikh-rtgwg-policy-model
Thread-Topic: Comments on draft-shaikh-rtgwg-policy-model
Thread-Index: AdDC3mGR5ZGZB0pXRXeVs9QL62qf/AAJOiSAAAEy94AAAM0xAAACmoeAAAA5XwAAAN6fAAAyTxMAAALgagAABYCcgAAbTT2AAABCKoAAAVj2AAAJQNaAANPd/gAALiYXgAAEDKwAAAL6MoAABgUoIP//5x+AgAA7iLA=
Date: Mon, 27 Jul 2015 21:04:34 +0000
Message-ID: <2E4BB27CAB87BF43B4207C0E55860F180EA89A87@eusaamb103.ericsson.se>
References: <etPan.55ae8fbf.2ac767e3.36f@corretto.local> <18774_1437550328_55AF46F8_18774_5612_26_9E32478DFA9976438E7A22F69B08FF92166A3667@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <20150722073931.GB30425@puck.nether.net> <etPan.55af51be.69dfac96.36f@corretto.local> <9439_1437568985_55AF8FD9_9439_5180_1_9E32478DFA9976438E7A22F69B08FF92166A398C@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <D1D97D09.29830%acee@cisco.com> <20150727155051.GF24197@pfrc.org> <7A2D9D5A-CCAF-4C8B-B2BC-C8DC1F05F5AF@cisco.com> <20150727191203.GA16809@pfrc.org> <2E4BB27CAB87BF43B4207C0E55860F180EA898A4@eusaamb103.ericsson.se> <20150727203522.GB16809@pfrc.org>
In-Reply-To: <20150727203522.GB16809@pfrc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNLMWRmVeSWpSXmKPExsUyuXRPoO5Wh22hBpe+mFlMfjuP2WL/wbes Fhfe/GZ2YPaY8nsjq8eSJT+ZPC73bmUNYI7isklJzcksSy3St0vgypjT2MJacIW/YsHD6AbG FTxdjJwcEgImEqd/bmOHsMUkLtxbz9bFyMUhJHCUUWLb2fXsEM5yRokfcw8yg1SxCVhIXP72 FMwWEVCUmP+/kw3EZhbwkZg36zULiC0MVLPl+C8WiBpLidmP17CCDBIR2MQosaTnMtg6FgFV iQnL5zOC2LwCvhLLfk1lBbGFBCaxSjTu4waxOQX0JF5OegtWwwh03vdTa5gglolL3Hoynwni bAGJJXvOM0PYohIvH/9jhbCVJCYtPccKUa8jsWD3J6hDtSWWLXzNDLFXUOLkzCcsExjFZiEZ OwtJyywkLbOQtCxgZFnFyFFanFqWm25ksIkRGDvHJNh0dzDueWl5iFGAg1GJh/fB8y2hQqyJ ZcWVuYcYpTlYlMR5HaPyQoUE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwGsYXGvT83ypussKL 5b/U6xMt54onqjD919Ge3f6wX6VTI7dXI0OJt1IpeNuSoCaLIE2zbQvOfTiSLTnzdMhU7X/l zxUtGlLrzBvKM7cJu1lu4Pk9a+YU0535d1eqOFexJC786GIR1PNzb7T2X/UK65ToSRpP7xec FdoVorTMYcaT/Ipn9juVWIozEg21mIuKEwGrjmc3fgIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/Yh-5G1-bZw8tG3Tuxt3fvRE2SBQ>
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2015 21:05:10 -0000

I was just poking to have fun since I fought (and implemented) the RPSL wars to be mildly blown off by ISPs telling me [what, sharing our access lists ? you claim you can anonymize them fully ? nice but nah, sorry ] ? ;-) 

Answers expected, I'll look it up once some first version is available. More than RPSL ? intriguing. RPSL was a closed algebra with closure so I really want to see how  this baby is  even better ;-)  Linear programming ? 

thanks 

--- tony
 
An idealist believes that the short run doesn't count. A cynic believes the long run doesn't matter. A realist believes that what is done or left undone in the short run determines the long run. ~~~ Sidney J. Harris 


> -----Original Message-----
> From: Jeffrey Haas [mailto:jhaas@pfrc.org]
> Sent: Monday, July 27, 2015 1:35 PM
> To: Antoni Przygienda
> Cc: Acee Lindem (acee); rtgwg@ietf.org
> Subject: Re: Comments on draft-shaikh-rtgwg-policy-model
> 
> On Mon, Jul 27, 2015 at 08:20:51PM +0000, Antoni Przygienda wrote:
> > > That's really where we're heading with regard to this model.  While
> > > BGP is obviously the first target, this is also the beginnings of a
> > > fundamental policy algebra that multiple protocols may share.
> > >
> > [Tony saiz:]
> >
> > Interesting, we're bringing RPSL back ?
> 
> I missed the RPSL wars, but got to heavily soak in their results for a few years. :-)
> 
> I think we'll see this go a lot further than RPSL since we're really dealing with
> internal router configuration rather than trying to express such policy in an inter-
> provider scenario.
> 
> >  And if so, providers are willing to share their policies finally ;-)  ?
> 
> Not a chance.
> 
> What's mildly amusing is that some discussions about route-leak mitigation (see
> discussion in grow and (s)idr) may have implications about "disclosing enough"
> to do the job.  I owe those WGs a writeup of the idea.
> 
> -- Jeff