Re: [Idr] Validation for BGP Flow-Spec Redirect to IP Action
PVLR Pavana Murthy <pvlrpm@gmail.com> Fri, 04 May 2018 15:41 UTC
Return-Path: <pvlrpm@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1B412D7EC; Fri, 4 May 2018 08:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 UfdtrAytirRh; Fri, 4 May 2018 08:41:45 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40B8F127136; Fri, 4 May 2018 08:41:45 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id w123-v6so10538261oia.4; Fri, 04 May 2018 08:41:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tyYn/bhIGOuRKmFs+yHV/Ai24NEHEm4ASPPu300Gypo=; b=pdnd1yuZsfU92w5x4VAXVl5kHWUw+CW1MzxWKsH8gwoWwKEqKUqKfbv5lqw2d55eSO 01a9UJL3YraXn2iQ+N0fxPzl5wAio/HWOzWJ0r+QTJpEt1eV2ZRNEgN2/MgnAYiT/70a UCXnetkSDudQNMBCw70yP5muiTA4vmVqA3BYftZpDgj+c+I9/n+JA8rhkZ/UPPgLfroQ ZwYWG+nzxkxFaohztENu3xetETlFEd1o/FH1JQ5CR+bm9oyrvlEyRehYDkS4cmPmky5K 20IoL8e7QA53tjDKKmRKYFr0RcJ3FH2g7PCAVg8denoNPCoXlFpbgFmDe/thy/BPLDZ8 29wA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tyYn/bhIGOuRKmFs+yHV/Ai24NEHEm4ASPPu300Gypo=; b=N7VEC5ymyauNGHygqsSx6xuAb7fZLmFkV3BidFRS9TsK5FeLP3NW0Y3tBbgjz2oGjc 2uFn2MB4qkbEIr5arMVE+88NetMFDrHGqiuGQEi7UwTS+5x6pEur/374r2FjdsEHhEOd JgtJMIJ51myyA3pG3R2sEH5NevMEaS3HJJxa2l+agoYm+bEDhp2jGOiuKhuyK1aheplP E2NYP0YK2j55KA96k6ppGxzHPjmGp3nFxNH23LdY1SS5raKFzKz9g6XiKWaRcZOOprNO kYhYPL5S+IxuWw+nHB3dJYHAdVD29KxH0KBy4J4e8OKJ8fap6Z+2WZbElS6E3dcvNMxv bMcA==
X-Gm-Message-State: ALQs6tDdg+POgwRbiMLcVI2y7OU5Duwn59FmK5gY9QfIkUZ7Hd6dvYtL 7JM5qZUiu+BZlLV4fh2IhCVITZ9sz2fhmzlJIjs=
X-Google-Smtp-Source: AB8JxZruaFf96GUpYOXh2F3J4gPV69A7j6KDiFq592Qvut/uQmo5SnzzdUN8/rkClD3Aeo1kyOGJ2yJkiOwB6lcvWiU=
X-Received: by 2002:aca:f354:: with SMTP id r81-v6mr17990110oih.161.1525448504603; Fri, 04 May 2018 08:41:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.88.154 with HTTP; Fri, 4 May 2018 08:41:44 -0700 (PDT)
In-Reply-To: <bd31302086e4453daa60d19aff45133b@XCH-RCD-012.cisco.com>
References: <CAN-MQG6bDyzcyuVs1vmka-JZFrD9Ya1uOuU_AFxfu0GnYgdmbA@mail.gmail.com> <aaa4916758a34ed99cb7432cff257f25@XCH-RCD-012.cisco.com> <CAN-MQG6R_LCLAM5xgaak3W_oRkuQFQsgZtEodacpeiLCQV8p-g@mail.gmail.com> <bd31302086e4453daa60d19aff45133b@XCH-RCD-012.cisco.com>
From: PVLR Pavana Murthy <pvlrpm@gmail.com>
Date: Fri, 04 May 2018 21:11:44 +0530
Message-ID: <CAN-MQG7o41bnMebez1iovpRqpr=2gy9FB8xXOFDTzRRN=kUeug@mail.gmail.com>
To: "David Smith (djsmith)" <djsmith@cisco.com>
Cc: idr wg <idr@ietf.org>, Pradosh Mohapatra <mpradosh@yahoo.com>, "draft-ietf-idr-bgp-flowspec-oid@ietf.org" <draft-ietf-idr-bgp-flowspec-oid@ietf.org>, "Simpson, Adam 1. (Nokia - CA/Ottawa)" <adam.1.simpson@nokia.com>
Content-Type: multipart/alternative; boundary="0000000000003d7c16056b6328ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Itja27v6SG5SvhW2XdbX1PLkAIk>
Subject: Re: [Idr] Validation for BGP Flow-Spec Redirect to IP Action
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2018 15:41:48 -0000
Hi Dave and Adam, Thanks for the reply. Lets take the example as I gave earlier. A----B----C A, B and C are 3 routers in different AS's 1, 2 and 3 respectively. A advertises a route for target X and also a Flowspec route with "redirect IP(target X)". C receives these routes via B. Now the the origin AS or first AS in the AS_PATH of the route to target X is 1 but the peer-AS of Flowspec route is 2 According to Dave,since the peer-AS 2 does not match the origin AS 1 of the best route for target X, this redirect IP action will be considered invalid for the flowspec route received at C. This is a typical scenario. Like this, we can't propagate the Flowspec routes with "redirect IP" action, more than one AS. I think, that's not expected. I feel, we should compare origin AS or neighbor-as for both Flowspec route and the best match route of target X. We should not be using peer-AS for flowspec route and nbr-as for best match route of target x. Otherwise the above typical scenarios never work. Probably, we need to edit the draft for "redirect-ip" action. Thanks, Pavana. On Thu, May 3, 2018 at 11:08 PM, David Smith (djsmith) <djsmith@cisco.com> wrote: > Hi Pavana, > > > > >I went through the latest draft-ietf-idr-bgp-flowspec-oid-06. It calls > the first AS the Origin AS. Is it so? > > > > Correct, first AS = first AS added = last AS in AS_PATH_SEQ hex-string = > origin AS. > > last AS = last AS added = first AS in AS_PATH_SEQ hex-string = neighboring > AS. > neighbor AS = peering AS: if update is coming from EBGP and > enforce-first-AS used -as mandated by RFC 5575. > > Note that draft-ietf-idr-bgp-flowspec-oid-06 uses 'last AS *added*' in > most cases, and when it does just use 'last AS', it can be inferred. > > > > >If that’s the case, the validation will fail for any 'redirect IP' > actions coming from the AS other than neighbor AS. Is that the intention? > > > > The RFC 5575 validation procedure required that for EBGP learned flowspecs > the ‘neighboring AS’ be in the left-most (or last) position of the AS_PATH > attribute. Since this is not valid for all topologies, > draft-ietf-idr-bgp-flowspec-oid-06 redefines the BGP flowspec validation > procedures including AS_PATH attribute. Further, the redirect-ip draft > imposes an additional AS_PATH validation check (specific for redirect-ip > flowspecs only) to validate that the best matching route to the redirect-ip > 'target address' is a BGP route with origin AS matching the last AS added > within the AS_PATH attribute of the redirect-ip flowspec. As > > > > >Also In draft-ietf-idr-flowspec-redirect-ip-00.txt, instead of 'origin > AS', the word 'last AS' is used. It is confusing. Does the validation > need to consider the first AS or last AS? > > > > See feedback above. Draft-ietf-idr-bgp-flowspec-oid-06 only needs to > consider last AS while redirect-ip draft needs to consider both per above. > > > > >Regarding my second doubt, I could not get any pointers from > draft-ietf-idr-bgp-flowspec-oid-06 . Do we need to consider only BGP > routes always (for redirect-ip target address)? > > > > The redirect-ip draft allows for its added validation check to be disabled > via configuration. This allows for a non-BGP route to the redirect-ip > target address. > > > > Regards, > > > > /dave > > > > > > *From:* PVLR Pavana Murthy <pvlrpm@gmail.com> > *Sent:* Saturday, April 28, 2018 12:40 AM > *To:* David Smith (djsmith) <djsmith@cisco.com> > *Cc:* idr wg <idr@ietf.org>; Pradosh Mohapatra <mpradosh@yahoo.com>; > draft-ietf-idr-flowspec-redirect-ip@ietf.org; draft-ietf-idr-bgp-flowspec- > oid@ietf.org > *Subject:* Re: Validation for BGP Flow-Spec Redirect to IP Action > > > > Hi Dave, > > Thanks for the reply and including respective draft author aliases. > > > > I went through the latest draft-ietf-idr-bgp-flowspec-oid-06. It calls > the first AS the Origin AS. Is it so? > > If that's the case, the validation will fail for any 'redirect IP' actions > coming from the AS other than neighbor AS. Is that the intention? > > Also In draft-ietf-idr-flowspec-redirect-ip-00.txt, instead of 'origin > AS', the word 'last AS' is used.It is confusing. Does the validation need > to consider the first AS or last AS? > > > > Regarding my second doubt, I could not get any pointers from > draft-ietf-idr-bgp-flowspec-oid-06 . Do we need to consider only BGP > routes always? > > > > Thanks, > > Pavana. > > > > > On Sat, Apr 28, 2018 at 3:37 AM, David Smith (djsmith) <djsmith@cisco.com> > wrote: > > Hi Pavana, > > > > Your points are valid. With that said, I’ll defer you to > draft-ietf-idr-bgp-flowspec-oid-05 (and later) and, specifically, section > 4 (revised validation procedure) which addresses your points below. > > > > Co-incidentally, a WG last call was issued for draft-ietf-idr-bgp-flowspec-oid-06 > yesterday. > > > > Regards, > > > > /dave > > > > > > *From:* PVLR Pavana Murthy <pvlrpm@gmail.com> > *Sent:* Friday, April 13, 2018 1:51 AM > *To:* idr wg <idr@ietf.org>; pmohapat@cumulusnetworks.com; David Smith > (djsmith) <djsmith@cisco.com> > *Subject:* Validation for BGP Flow-Spec Redirect to IP Action > > > > Hello, > > In the draft draft-ietf-idr-flowspec-redirect-ip-02.txt, the following > procedure is mentioned to validate the extended community of 'Flowspec > > redirect to IP'. > > > > > > BGP speakers that support the extended communities defined in this > > draft MUST also, by default, enforce the following check when > > receiving a flow-spec route from an EBGP peer: if the received flow- > > spec route has a 'redirect to IP' extended community with a 'target > > address' X (in the global administrator field) and the best matching > > route to X is not a BGP route with *origin AS* matching the peer AS > > then the extended community should be discarded and not propagated > > along with the flow-spec route to other peers. > > > > *I have 2 doubts related to this statement.* > > > > *What is 'origin AS' here? Is it the AS no. that is first added to the AS_PATH? * > *In the previous version of the draft its mentioned as the last AS in the AS_PATH.* > *Is it the last AS no. that has been added to the AS_PATH or the last AS no. from left in AS_PATH? * > > > > *What if the redirect target X is directly connected or reachable by a static route and its not advertised by EBGP?* > > *Do we need to consider that action invalid in that case?* > > > > > > Thanks, > > Pavana. > > > > > > > > >
- [Idr] Validation for BGP Flow-Spec Redirect to IP… PVLR Pavana Murthy
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… David Smith (djsmith)
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… PVLR Pavana Murthy
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… PVLR Pavana Murthy
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… Simpson, Adam 1. (Nokia - CA/Ottawa)
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… PVLR Pavana Murthy
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… Simpson, Adam 1. (Nokia - CA/Ottawa)
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… PVLR Pavana Murthy
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… Simpson, Adam 1. (Nokia - CA/Ottawa)
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… David Smith (djsmith)
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… PVLR Pavana Murthy
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… David Smith (djsmith)
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… PVLR Pavana Murthy
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… David Smith (djsmith)
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… PVLR Pavana Murthy
- Re: [Idr] Validation for BGP Flow-Spec Redirect t… David Smith (djsmith)