Re: [Sidrops] WGLC for draft-ietf-sidrops-ov-egress-00.txt - ENDS 11/25/2019 (November 25 2019)

Randy Bush <randy@psg.com> Sun, 01 December 2019 20:40 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DFCC120106; Sun, 1 Dec 2019 12:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 cbtk_URpmn6m; Sun, 1 Dec 2019 12:40:23 -0800 (PST)
Received: from mail.rg.net (mail.rg.net [198.180.150.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 181F112004D; Sun, 1 Dec 2019 12:40:23 -0800 (PST)
Received: from [37.173.163.6] (helo=[10.111.156.94]) by mail.rg.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1ibW0x-00040m-U9; Sun, 01 Dec 2019 20:40:20 +0000
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Randy Bush <randy@psg.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 1 Dec 2019 12:40:14 -0800
Message-Id: <25CB2E64-D0B5-4D5F-A59F-4864D1C340E7@psg.com>
References: <87tv6jbyjd.wl-morrowc@ops-netman.net>
Cc: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>, "sidrops@ietf.org" <sidrops@ietf.org>, "sidrops-chairs@ietf.org" <sidrops-chairs@ietf.org>, "draft-ietf-sidrops-ov-egress@ietf.org" <draft-ietf-sidrops-ov-egress@ietf.org>, Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <87tv6jbyjd.wl-morrowc@ops-netman.net>
To: Chris Morrow <morrowc@ops-netman.net>
X-Mailer: iPhone Mail (17B111)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/g1CXz4TlVph4dCP1FCA3GlL_Jtg>
Subject: Re: [Sidrops] WGLC for draft-ietf-sidrops-ov-egress-00.txt - ENDS 11/25/2019 (November 25 2019)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Dec 2019 20:40:25 -0000

Many documents already say to be sure to issue ROA(s) for the AS(s) which announce the prefix. This document does not change that in the slightest. If we start reiterating practice and restating the obvious we will have a document three or more times as large but with zero real added value.   Let us not do that to this simple document. 

randy, on a phone

> On Dec 1, 2019, at 12:07, Chris Morrow <morrowc@ops-netman.net> wrote:
> 
> On Wed, 27 Nov 2019 21:17:08 +0000,
>>> Is there such a thing as non-deterministic policy?
>>> What does it mean to say that the outcome of applying
>>> one or a set of policies is that it results in
>>> a random AS being the origin AS?
>> 
>> non-derministic != random
>> 
>> in this case it is meant to refer to policy results which depend on
>> exogenous data
> 
> The case probably is that at some point (with certain attributes set
> by an upstream bgp speaker) OriginAS could be any of a set of values.
> 
> So, ideally the operator would just create ROA with the set covered,
> right? (really 1 ROA per origin)
> 
> I think Sriram is getting to that, or is saying it in a way that
> wasn't clear to me :)
> 
> -chris