IETF Logo Mail Archive

Re: [Gen-art] [Sidrops] Genart last call review of draft-ietf-sidrops-ov-egress-01

Randy Bush <randy@psg.com> Fri, 20 March 2020 18:29 UTC

Return-Path: <randy@psg.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 561AB3A0D9A; Fri, 20 Mar 2020 11:29:48 -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 koaG9c0TsGyH; Fri, 20 Mar 2020 11:29:46 -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 8DBE43A0DC9; Fri, 20 Mar 2020 11:29:46 -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 1jFMOq-0004IO-Np; Fri, 20 Mar 2020 18:29:40 +0000
Date: Fri, 20 Mar 2020 11:29:39 -0700
Message-ID: <m2bloq517w.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ben Maddison <benm@workonline.africa>
Cc: "keyur@arrcus.com" <keyur@arrcus.com>, "last-call@ietf.org" <last-call@ietf.org>, "rjsparks@nostrum.com" <rjsparks@nostrum.com>, "sidrops@ietf.org" <sidrops@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-sidrops-ov-egress.all@ietf.org" <draft-ietf-sidrops-ov-egress.all@ietf.org>
In-Reply-To: <37beff1136180992cc9b1a209cd5880a9db0dbff.camel@workonline.africa>
References: <158411258778.3418.757369789772046254@ietfa.amsl.com> <m2y2ry78fq.wl-randy@psg.com> <933a9d0d-319e-f6fb-4d02-82e27bb00509@nostrum.com> <m2o8su7383.wl-randy@psg.com> <5A210359-FE01-40BF-9BAD-E0250BB31BFC@arrcus.com> <m2v9n15teb.wl-randy@psg.com> <37beff1136180992cc9b1a209cd5880a9db0dbff.camel@workonline.africa>
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/gen-art/9TM3vEzOiogMjEAqfW6PuVhbmmk>
Subject: Re: [Gen-art] [Sidrops] Genart last call review of draft-ietf-sidrops-ov-egress-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Mar 2020 18:30:02 -0000

> Although a little more verbose, perhaps the following is more explicit?
> 
>     As the origin AS of a BGP UPDATE is decided by configuration and
>     outbound policy of the BGP speaker, a validating BGP speaker MUST
>     apply Route Origin Validation policy semantics Against the Route
>     Origin ASN as determined by applying the procedure in [RFC6811,
>     Section 2] to the AS_PATH (see RFC 4271 4.3 Path Attributes:b) that
>     it will send in the UPDATE to the peer.

i am torn about adding yet another 6811 ref.  does it clarify anything?
are there other possible "Route Origin Validation policy semantics?"

if so, i might put it earlier, after "apply Route Origin Validation
policy semantics".

randy

v2.23.0 | Report a Bug | By Email