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

Randy Bush <randy@psg.com> Mon, 02 December 2019 01:00 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 071B712011B; Sun, 1 Dec 2019 17:00:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 a6XMNOsfLwa5; Sun, 1 Dec 2019 17:00:20 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 BD2CD120052; Sun, 1 Dec 2019 17:00:20 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1iba4W-0000hH-7H; Mon, 02 Dec 2019 01:00:16 +0000
Date: Sun, 01 Dec 2019 17:00:14 -0800
Message-ID: <m2blsr1qzl.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>
Cc: Chris Morrow <morrowc@ops-netman.net>, "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>, "keyur@arrcus.com" <keyur@arrcus.com>
In-Reply-To: <DM6PR09MB3386E0906EE0BDC12889173784430@DM6PR09MB3386.namprd09.prod.outlook.com>
References: <87tv6jbyjd.wl-morrowc@ops-netman.net> <25CB2E64-D0B5-4D5F-A59F-4864D1C340E7@psg.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.2 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/LVpDKTvLKATYCwdW-m1xpvsH2OU>
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: Mon, 02 Dec 2019 01:00:22 -0000

> My problem was with these two sentences:
> 
> #1 
> "Configurations may have complex policy where the final announced
>    origin AS may not be easily predicted before all policies have been
>    run."
> 
> Is it not the same as simply saying: 
> Configurations may have complex policy where the final announced
>    origin AS is determined only after all policies have been run.
> 
> Why not state that and keep it simple?

because it is the inability to predict which is important.

> #2 
> "Therefore it SHOULD be possible to specify an origin validation
>  policy which MUST BE run after such non-deterministic policies."
> 
> What does it mean to say "specify origin validation policy"?

> The operator knows their complex policies and can determine
> the origin AS that would result after the policies are applied.

no.  that is point.  as stated before, exogenous data can make the
result not deteminable from analysis of the configuration.

> I hope this clarifies what I was trying to say.

it does.  but i happen not to agree with it.

randy