Re: [Gen-art] Genart last call review of draft-ietf-idr-bgp-open-policy-18

Gyan Mishra <hayabusagsm@gmail.com> Tue, 04 January 2022 15:44 UTC

Return-Path: <hayabusagsm@gmail.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 2B63C3A1D97; Tue, 4 Jan 2022 07:44:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 34ONp2km7832; Tue, 4 Jan 2022 07:44:36 -0800 (PST)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (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 59B273A1D95; Tue, 4 Jan 2022 07:44:36 -0800 (PST)
Received: by mail-pf1-x429.google.com with SMTP id m1so32556153pfk.8; Tue, 04 Jan 2022 07:44:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gr0clOWtSLXCSfjjTtNqDk+1tevcjGzWf9PRGSa24hg=; b=K4DjGmlln3JtALY6XyrrPfanG6ABdDW8EZAfdcm7ytUMc/+rgiYIpQ+aDOySTnQMH0 25Dgv9wpeVTkl1fjqj+Ou06dcusr1Wtc3aFsL1iIBLucPhk1dOxQI4rq9jgqk+ukzygt 8Gj0qb5DDsy9oA8yEgGOMmzmmHwhHf503i3uc5wa0PI/QpWCMsXfrYY1JIQQnCIb/xRV N+yyw+h8kGe9YI4e9LALxKgnOA2BVjo3SPGUKIEHxSD5oSONnakEW9+KeCBsYW+i3m9m vz6H2TpZy7znRKfgoPILRAwnRqelMWeQEqyDJuafDro6RQdo8gHWTr8RuPGUevgvP+Zr Y40w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gr0clOWtSLXCSfjjTtNqDk+1tevcjGzWf9PRGSa24hg=; b=cnpTPHN30+d2HY47y2tukUYpH5FP7oZzMRuWo1EJLUUy92rlHU4qc7KnQzKw0L+/JG HDJtzW3Vys4WTgKRtRpwFTtmXrfppMSyD1hReHbrtz9pKw054DR6Yqmkpj5bppSsFWNx MwgH1x4PqJCcb/Thfu864A3Nll1ylQzOC6YvStjL3MpXkRRI5xBYVFzEBap/DKNLCLpe XwAbDP3J8fzn9uuW7D9+mcFFGGhSMrVQ0F9SWd2oUjlLM2ru+8KRvi7SQhfP+mQ9AFR7 creFHELUdG+1DvdACACFWN7+gKBWXZkJmOKDx6n5MKZhgIFyHmTfXALiizqNmGm5Ts2q UsMA==
X-Gm-Message-State: AOAM5322VeUs25lDW9wylloZV6RAMAygGjsqU7AjvayTj0BHzi7Qj+ZZ jaMgulPXXSnCoPhdzRUaoyKx7Ssl1IpjYObab0J7HEOs
X-Google-Smtp-Source: ABdhPJwYhv5YHeWrr/DbTJOS4aRFsWcCORAfXPBhI6QlMZ0vasSAcvIQLJ0S2yCxkyi315xbGmfOR49uHbIlFdPqIh8=
X-Received: by 2002:a63:92:: with SMTP id 140mr44691292pga.575.1641311075081; Tue, 04 Jan 2022 07:44:35 -0800 (PST)
MIME-Version: 1.0
References: <164013488006.27197.13873644386825552452@ietfa.amsl.com> <CAMMESsx35+gC7CP9ox+U-QsT8Dxkv3=Du8VRq_cprMsEc5PCyQ@mail.gmail.com>
In-Reply-To: <CAMMESsx35+gC7CP9ox+U-QsT8Dxkv3=Du8VRq_cprMsEc5PCyQ@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Tue, 04 Jan 2022 10:44:24 -0500
Message-ID: <CABNhwV30nrqJ-mOpniso6c=rJpFi0zQX93BWaQKJvKNVcrMNAw@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
Cc: Gyan Mishra via Datatracker <noreply@ietf.org>, draft-ietf-idr-bgp-open-policy.all@ietf.org, gen-art@ietf.org, idr@ietf.org, last-call@ietf.org
Content-Type: multipart/alternative; boundary="00000000000098a02a05d4c383bc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Cxa3EAHHAHDCvctjcEqPDZENfpU>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-idr-bgp-open-policy-18
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: Tue, 04 Jan 2022 15:44:41 -0000

Hi Alvaro

Happy New Year!

Welcome!

On Tue, Jan 4, 2022 at 10:12 AM Alvaro Retana <aretana.ietf@gmail.com>
wrote:

> On December 21, 2021 at 8:01:21 PM, Gyan Mishra wrote:
>
> Gyan:
>
> Hi!  Happy New Year!
>
> Thank you for the review!
>
>
> ...
> > Summary: ... The new BGP role capabilities mismatch code 2 subcode 8
> > discussed on ML seems to have multiple implementations deployed and one
> > confined by Cisco. I agree that the authors should request a new subcode
> > for the role mismatch notification.
>
> To catch others up:  there is a confirmed case of squatting on the
> assigned subcode.  A consultation on the next steps is open on the idr
> list and will close tomorrow (Jan/5).
>
> https://mailarchive.ietf.org/arch/msg/idr/RBD3Z9YIboudGAIeJLS8L--p4BU/
>
> Gyan> Thanks for update
> ...
> > Nits/editorial comments:
> > Comment related to Gao-Rexford model. The Gao-Rexford Model only has 3
> peer
> > types North bound upstream Provider, Southbound Customer and lateral same
> > tier level peer. With the role capabilities, RS and RS-Client is added
> which
> > makes it slightly different but almost identical. In describing the role
> > types would it make sense to have a graphical depiction of Gao-Redford
> model
> > with the role capabilities on adjacent peers to help explain the role
> > relationship for local and remote-as. Just an idea to help explain the
> role
> > capabilities.
>
> The role definitions are described in this document, not strictly
> carried over from Gao-Rexford.  Nonetheless, a graphical description
> on the roles defined here may make sense.  I'll leave it to the
> authors to consider (if not too complicated).


Gyan> Perfect

>
>
>
> > In the role correctness section scenario where the peer receives multiple
> > role capabilities to send role mismatch notification. What if there is a
> > timing issue and the multiple are received after the BGP open and peer is
> > established possible sequence of events issue. Is it possible the peer
> may
> > not get a mismatch notification if the peer establishes prior to getting
> a
> > different capabilities where a mismatch or problem exists that is missed
> > that could result in a route leak. I am thinking of possibly false
> positive
> > or negative or negative during BGP open capabilities exchange
>
> All capabilities are signaled in the OPEN, so there's no possibility
> for receiving a Role Capability afterwards.
>

Gyan> Agreed.  The multiple capabilities received is mentioned in the text,
however as it’s signaled in the open how would multiple capabilities be
received.  As the role capabilities are sent in the open , how can the
possibility of multiple capabilities occur?

>
>
> Alvaro.
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*