Re: [Sidrops] Alissa Cooper's No Objection on draft-ietf-sidrops-ov-egress-02: (with COMMENT)
Randy Bush <randy@psg.com> Mon, 06 April 2020 17:07 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 AC6163A0AE0; Mon, 6 Apr 2020 10:07:08 -0700 (PDT)
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 RwXH7ofc82ku; Mon, 6 Apr 2020 10:07:07 -0700 (PDT)
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 0BDE33A0AE5; Mon, 6 Apr 2020 10:07:06 -0700 (PDT)
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 1jLVDD-0005i4-Ou; Mon, 06 Apr 2020 17:07:04 +0000
Date: Mon, 06 Apr 2020 10:07:02 -0700
Message-ID: <m2v9mca6h5.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Alissa Cooper via Datatracker <noreply@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-sidrops-ov-egress@ietf.org, sidrops-chairs@ietf.org, sidrops@ietf.org, keyur@arrcus.com, warren@kumari.net, nathalie@ripe.net
In-Reply-To: <158619174173.5693.3701421912223917488@ietfa.amsl.com>
References: <158619174173.5693.3701421912223917488@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 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/IeBPac7876UaWoiJfrypKVuSPqE>
Subject: Re: [Sidrops] Alissa Cooper's No Objection on draft-ietf-sidrops-ov-egress-02: (with COMMENT)
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, 06 Apr 2020 17:07:09 -0000
> "Therefore it SHOULD be possible to specify an origin validation > policy which MUST BE run after such non-deterministic policies." > > The normative language here doesn't quite make sense. "MUST BE" is not a > normative keyword and the construction "SHOULD ... which MUST" is a little > confusing. point > I would suggest something like: > > An origin validation policy that is required to be run after such > non-deterministic policies SHOULD be specified. nope. that says the op SHOULD specify the policy; when MAY would be the appropriate point here. how about a simpler hack (with context)? Configurations may have complex policy where the final announced origin AS may not be easily predicted before these policies have been run. Therefore it SHOULD be possible to specify an origin validation policy which will run after all such non-deterministic policies. i suspect some might suggest the point of the draft should really be s/SHOULD/MUST/ randy
- [Sidrops] Alissa Cooper's No Objection on draft-i… Alissa Cooper via Datatracker
- Re: [Sidrops] Alissa Cooper's No Objection on dra… Randy Bush
- Re: [Sidrops] Alissa Cooper's No Objection on dra… Alissa Cooper