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

Alvaro Retana <aretana.ietf@gmail.com> Tue, 04 January 2022 15:12 UTC

Return-Path: <aretana.ietf@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 E7FDF3A1D4B; Tue, 4 Jan 2022 07:12:36 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 Ca5_yGbB5uDW; Tue, 4 Jan 2022 07:12:32 -0800 (PST)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 4972F3A1D4A; Tue, 4 Jan 2022 07:12:32 -0800 (PST)
Received: by mail-ed1-x52a.google.com with SMTP id w16so149856459edc.11; Tue, 04 Jan 2022 07:12:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=sIy1pOhlsmfHwgq9q2NHxTnd/2y473nr/aBZCYA/ipk=; b=O8xWvccNKsQPW2bD86jbE3KYVqKWzv51sPIMex//EPwgX598KrwIvcEf0rF8/c50bO ScBrSOb/toc8hCsvjphu4RvM49JFQcn5mlbWNSLQ/xFikgt1e1TE8RDfd66aC/gq1iNN 7HjYCxmPxA8rLCQzCEtSIiHWJk1FZ1V7f+dYW+78NP9ZHq6/FoZ6Qb/7WUcF1awN2q3s Cxqbe9Ymy4Hu8xF2LYzs9hMlRuImGupmocxg645sC/1sXeGS+sWiFx/cDGpK2Gi+Uqld xsp35zvKSsp6rM1BFwP/80UqkW0iPGRMvNWEZMxoMDESYLJnUFQzXZ4l8MAGMzOStjAc auEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=sIy1pOhlsmfHwgq9q2NHxTnd/2y473nr/aBZCYA/ipk=; b=p0WpaGN3un806YIFzcqeFcvTyCalRB9MktwBjOo2T0MxFrr6jHEakCQlLm5gra8No8 peJvJA31SLrXahYD6QGrss34MfC3iiQ8PLwELzyMurJfyKX4IhkTXjzmXsptiEQWN5Hd P1pOkG+DmH0c53251lcBp0PjzSVSYDYpmhiQMmIR0HeZS+qAUExcMDPLSajQIEyDIlOn VD3RzRNFFyznIpsjZu7sTTFGgZbExDPJScFuWvuVBAQACMYih/RLSDWwLQt7xisLyW/3 y/ZZQV2L038jD9TT9L2uWLwcqdRJ8RoZHidrfzS7Uegf8SIGSnwsXzKBXk+zj97/5wGk e3Yw==
X-Gm-Message-State: AOAM531F7XVTc3fgYcdUoAWCC0W4JLHOCovikLTP+oNXQtqje4WnrcGP fnjJjGXVCwWWlSZm8NlhFB1FCVI/xi6rL+l7CMw=
X-Google-Smtp-Source: ABdhPJzG0jOPNc7e1XD+yPtk00nNg3KvmSarF6WXRwY8slZ1LlDy8xa7VlpTFnsNDpwpLO3qQ+NROy+E6BD69uPGyEo=
X-Received: by 2002:a17:907:2177:: with SMTP id rl23mr13582908ejb.662.1641309149749; Tue, 04 Jan 2022 07:12:29 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 4 Jan 2022 07:12:28 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <164013488006.27197.13873644386825552452@ietfa.amsl.com>
References: <164013488006.27197.13873644386825552452@ietfa.amsl.com>
MIME-Version: 1.0
Date: Tue, 04 Jan 2022 07:12:28 -0800
Message-ID: <CAMMESsx35+gC7CP9ox+U-QsT8Dxkv3=Du8VRq_cprMsEc5PCyQ@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>, gen-art@ietf.org, Gyan Mishra via Datatracker <noreply@ietf.org>
Cc: draft-ietf-idr-bgp-open-policy.all@ietf.org, idr@ietf.org, last-call@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Aa-K1H6t2Qgey_WINQ8KUgSFi98>
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:12:37 -0000

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/


...
> 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).


> 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.


Alvaro.