Re: [Sidrops] Genart last call review of draft-ietf-sidrops-ov-egress-01
Randy Bush <randy@psg.com> Wed, 18 March 2020 19:56 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 60C663A1B11; Wed, 18 Mar 2020 12:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=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 wqu1HvNZ4VOH; Wed, 18 Mar 2020 12:56:34 -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 230503A1B0F; Wed, 18 Mar 2020 12:56:33 -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 1jEenk-0004U4-PU; Wed, 18 Mar 2020 19:56:28 +0000
Date: Wed, 18 Mar 2020 12:56:28 -0700
Message-ID: <m2v9n15teb.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Keyur Patel <keyur@arrcus.com>
Cc: Robert Sparks <rjsparks@nostrum.com>, gen-art@ietf.org, last-call@ietf.org, draft-ietf-sidrops-ov-egress.all@ietf.org, SIDR Operations WG <sidrops@ietf.org>
In-Reply-To: <5A210359-FE01-40BF-9BAD-E0250BB31BFC@arrcus.com>
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>
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="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/CmPOxoQ-hWVndew8wn0YEqOTvZc>
Subject: Re: [Sidrops] Genart last call review of draft-ietf-sidrops-ov-egress-01
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: Wed, 18 Mar 2020 19:56:42 -0000
( warning: quote depth errors and top posting. keyur's mta, well let's not get into that :) > Speaking as a wg member. and one of the first ROV implementors, tyvm. > Shouldn’t you be checking the "my autonomous system number" in the > update message (when sending it out to the ebgp peer) as opposed to > "my autonomous system number" in the open message. > > Regards, Keyur > > On 3/17/20, 8:27 PM, "Randy Bush" <randy@psg.com> wrote: > >> I wanted to avoid "be able to be" and have an explicit actor. I see >> the difficulty you point to below. > > i am happy to change to the following > >>> As the origin AS may be modified by outbound policy, a BGP speaker >>> MUST apply ROV policy semantics using the My Autonomous System number >>> in the BGP OPEN message (see RFC 4271 section 4.2) issued to the peer >>> to which the UPDATE is being sent. > > but, in my free opinion, as it is in IETF LC, the change is enough that > it might require approval by chairs and/or AD. i think you're right. what counts for ROV is the origin AS in the UPDATE. open a hole to deviate from that and ... and we have to remember that, for these UPDATEs which are redistributed into BGP by this speaker, have their AS_PATH first created when sent to the peer. i.e. we can not (yet) speak of the origin AS in the AS_PATH. so maybe 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 origin Autonomous System number which it will put in the AS_PATH (see RFC 4271 4.3 Path Attributes:b) of the UPDATE to the peer. randy
- [Sidrops] Genart last call review of draft-ietf-s… Robert Sparks via Datatracker
- Re: [Sidrops] Genart last call review of draft-ie… Randy Bush
- Re: [Sidrops] Genart last call review of draft-ie… Randy Bush
- Re: [Sidrops] Genart last call review of draft-ie… Robert Sparks
- Re: [Sidrops] Genart last call review of draft-ie… Robert Sparks
- Re: [Sidrops] Genart last call review of draft-ie… Randy Bush
- Re: [Sidrops] Genart last call review of draft-ie… Keyur Patel
- Re: [Sidrops] Genart last call review of draft-ie… Randy Bush
- Re: [Sidrops] Genart last call review of draft-ie… Keyur Patel
- Re: [Sidrops] Genart last call review of draft-ie… Ben Maddison
- Re: [Sidrops] Genart last call review of draft-ie… Randy Bush
- Re: [Sidrops] Genart last call review of draft-ie… Ben Maddison
- Re: [Sidrops] Genart last call review of draft-ie… Randy Bush
- Re: [Sidrops] Genart last call review of draft-ie… Randy Bush
- Re: [Sidrops] [Last-Call] Genart last call review… Job Snijders
- Re: [Sidrops] [Last-Call] Genart last call review… Ben Maddison
- Re: [Sidrops] [Gen-art] Genart last call review o… Alissa Cooper