Re: [GROW] Alvaro Retana's Discuss on draft-ietf-grow-bmp-local-rib-10: (with DISCUSS and COMMENT)
Job Snijders <job@fastly.com> Wed, 28 April 2021 15:12 UTC
Return-Path: <job@fastly.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B7253A0EEC for <grow@ietfa.amsl.com>; Wed, 28 Apr 2021 08:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.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 sxid2xDRsrAa for <grow@ietfa.amsl.com>; Wed, 28 Apr 2021 08:12:30 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 CF4F63A0EEF for <grow@ietf.org>; Wed, 28 Apr 2021 08:12:29 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id d14so10855040edc.12 for <grow@ietf.org>; Wed, 28 Apr 2021 08:12:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=0khIrBljvE05zUKgOOTEQCKywW5JbQa6PFUup63pM3U=; b=TGlYA2WU4gMyHjJLhX0heJRa4AfS8rDX46XgkATeCf/nWF8HxTQ2fviyV/yKx/DMdR vrBRXSZkSJObJmYI7zpODt4ZfamoppEigvFXLEW85qSSG2WRhkoLza8Ti/iNOOF2QnkH WoygXiFNOFgzfeYmeUtZ5yBVa0OqlVrSM4Jkc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=0khIrBljvE05zUKgOOTEQCKywW5JbQa6PFUup63pM3U=; b=dJsrHrLYjgtqkqG+wF2hTPUlI7qciplU/axjC94H9o77OgkbOD4AH+xi0qJ/M7k4N6 h1OeKVB7LgBcB/E+MWKGNfx/+nR/ksqLrh9yNk9AEMOG6GmFxY5FO29xxspZM5kD/5az Zv9ojIDpILcEHxs3KDkLuCdQi/DEdyXy4Si42EHEFFN8RKEPnJOJFDs9J80K/ZIQYjDL FkB0IINJVMrsli5gShIha31070b8+BzZb+W2HNeaNLz/xE0bLuTWnjl0l8ZW0O9P8062 6qB8/jR/jOS7zWeEn1p6oRw3Ho67Wx6m7WYfqguRl50CjyJdzqeJ/x8bpADO8lGg7+/c qNaw==
X-Gm-Message-State: AOAM532nYf742vWtvvvT7UdGzB5Kc0b0sem35Jc5ksWPn3fHD+sQnZzq RB701zeaUJxOlTjbTa0baWpC/g==
X-Google-Smtp-Source: ABdhPJxaZdH07TjZGOPj9Ic9u5K2Drjn9N346+WTDf06FbCKoasD4mXhodO5i7PJSA89e0FdMPusHQ==
X-Received: by 2002:a05:6402:cb3:: with SMTP id cn19mr11909978edb.206.1619622745930; Wed, 28 Apr 2021 08:12:25 -0700 (PDT)
Received: from snel (mieli.sobornost.net. [45.138.228.4]) by smtp.gmail.com with ESMTPSA id t20sm99593ejc.61.2021.04.28.08.12.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 28 Apr 2021 08:12:25 -0700 (PDT)
Date: Wed, 28 Apr 2021 17:12:23 +0200
From: Job Snijders <job@fastly.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-grow-bmp-local-rib@ietf.org, grow-chairs@ietf.org, grow@ietf.org
Message-ID: <YIl7V3rBY+vbXwoD@snel>
References: <161765178219.25574.4147551293313412089@ietfa.amsl.com> <YIBiHiycqGtrEJqt@snel>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <YIBiHiycqGtrEJqt@snel>
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/_8razEjBQlpMjM6SF01Jf6YXu9I>
Subject: Re: [GROW] Alvaro Retana's Discuss on draft-ietf-grow-bmp-local-rib-10: (with DISCUSS and COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Apr 2021 15:12:34 -0000
Hi all, We (GROW chairs + Alvaro + draft authors Tim & Paolo) had a productive call, a number of suggestions for clarification came to light. Tim will follow up by sending a summary of proposed changes to the list. And some questions for the GROW group. Thanks! Job On Wed, Apr 21, 2021 at 07:34:22PM +0200, Job Snijders wrote: > Dear Alvaro, draft authors, > > Perhaps it would be good to have a voice discussion? This might expedite > figuring out a solution to how we describe things. > > From what I understand the BMP Loc-RIB draft to propose is that all BMP > messages of the Loc-RIB instance type are 'synthesized', as the > Information Base contains the router's best paths (regardless of > original protocol). It indeed would be good if the document is very > clear on this aspect. > > I'm happy to organize a call for early next week (early PST / afternoon > CEST timeslot). > > Kind regards, > > Job & Chris > GROW Chairs > > On Mon, Apr 05, 2021 at 12:43:02PM -0700, Alvaro Retana via Datatracker wrote: > > Alvaro Retana has entered the following ballot position for > > draft-ietf-grow-bmp-local-rib-10: Discuss > > > > When responding, please keep the subject line intact and reply to all > > email addresses included in the To and CC lines. (Feel free to cut this > > introductory paragraph, however.) > > > > > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html > > for more information about IESG DISCUSS and COMMENT positions. > > > > > > The document, along with other ballot positions, can be found here: > > https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-local-rib/ > > > > > > > > ---------------------------------------------------------------------- > > DISCUSS: > > ---------------------------------------------------------------------- > > > > I am balloting DISCUSS because there are significant clarity issues. > > > > (1) 4.2. Peer Flags > > > > In section 4.2 of [RFC7854], the "locally sourced routes" comment > > under the L flag description is removed. If locally sourced routes > > are communicated using BMP, they MUST be conveyed using the Loc-RIB > > instance peer type. > > > > This change is bigger than simply removing a comment: it is changing the > > behavior. Note that §8.2/rfc7854 also talks about the L flag. Do the same > > considerations apply? I would like to see a clearer treatment of the change > > related to locally sourced routes -- a separate section/sub-section seems > > appropriate. > > > > (2) §4.2/8.2: Peer Flags > > > > §4.2 defines a new Flag as follows: > > > > 0 1 2 3 4 5 6 7 > > +-+-+-+-+-+-+-+-+ > > |F| Reserved | > > +-+-+-+-+-+-+-+-+ > > > > But it doesn't mention that this field is intended to be specific to the > > Loc-RIB peer-type. OTOH, §8.2 (IANA Considerations) does: > > > > This document defines a new flag (Section 4.2) and proposes that peer > > flags are specific to the peer type: > > > > The registry [1] shows that the early allocation was made in the "generic" (not > > per-peer-type) Peer Flags field. The flags defined in rfc7854 and rfc8671 both > > assume the same set of Flags for all peer types. > > > > [1] > > https://www.iana.org/assignments/bmp-parameters/bmp-parameters.xhtml#peer-flags > > > > (3) §5.4 (Route Monitoring) The implication in this section is that a BGP > > UPDATE includes the route information -- but the information in the Loc-RIB may > > not have come from BGP, so there is no BGP UPDATE to propagate. This clearly > > is a case where the UPDATE is fabricated. Please provide specific instructions > > on how this UPDATE is constructed, including any path attributes. > > > > > > ---------------------------------------------------------------------- > > COMMENT: > > ---------------------------------------------------------------------- > > > > (1) §3 (Definitions) > > > > * Post-Policy Adj-RIB-Out: The result of applying outbound policy to > > an Adj-RIB-Out. This MUST be what is actually sent to the peer. > > > > s/This MUST be what is actually sent to the peer./This is what is sent to the > > peer. > > > > Note that this document should not use Normative language related to what a BGP > > session does. In this case, that is rfc4271's job. > > > > (2) §5.2 (Peer UP Notification): "Capabilities MUST include the 4-octet ASN and > > all necessary capabilities to represent the Loc-RIB route monitoring messages. > > Only include capabilities if they will be used for Loc-RIB monitoring messages." > > > > Which are the capabilities that "will be used for Loc-RIB monitoring messages"? > > The action above is required (MUST), but no specifics are given. > > > > (3) §5.2.1: "The Information field contains a UTF-8 string whose value MUST be > > equal to the value of the VRF or table name (e.g. RD instance name) being > > conveyed." > > > > - Please take a look at the Shutdown Communication string definition in rfc9003 > > and use a similar definition. > > > > - The "value of the VRF or table name" is a local matter, right? How can the > > requirement be normatively enforced? How can the receiver enforce the "MUST"? > > IOW, s/MUST.../The information field contains the value of the VRF or table > > name... > > > > - There's no need to redefine the TLV in §5.3. > > > > (4) §5.4: "As defined in section 4.3 of [RFC7854]..." The quote comes from > > §4.6. > > > > (5) §5.5 (Route Mirroring): "Route mirroring is not applicable to Loc-RIB and > > Route Mirroring messages SHOULD be ignored." If not applicable...when is it > > ok not to ignore the Route Mirroring messages? IOW, why is this behavior > > recommended and not required? > > > > (6) In general, the terminology used throughout the document is well-known to > > BMP/BGP users but may not be to the average reader. Please add references > > (most can be informational). These are some examples: > > > > - Please add a reference to rfc471 when introducing Loc-RIB/Adj-RIB-In. > > There's a mention in the Abstract about Loc-RIB, but that is not enough. > > > > - s/Adj-RIB-In Post-Policy/Post-Policy Adj-RIB-In/g > > That is how rfc7854 defines the term. Also, please add a reference on first > > mention. > > > > - s/Adj-RIB-In Pre-Policy/pre-policy Adj-RIB-In/g > > Same as above. > > > > - Add a reference for BGP-LS (rfc7752). > > > > - s/add-paths/ADD-PATH/g > > That is how rfc7911 uses the term. Also, please add a reference on first > > mention. > > > > - s/BGP-ID/BGP Identifier/g > > From rfc4271. rfc7854 uses "BGP ID". > > > > - Expand RD on first use. > > > > - Add a reference for "4octet ASN" (rfc6793). > > > > (7) [nits] > > > > s/after best-path selection/after best route selection > > That's the terminology used in rfc4271 > > > > s/build Adj-RIB-Out/build the Adj-RIB-Out > > > > > >
- [GROW] Alvaro Retana's Discuss on draft-ietf-grow… Alvaro Retana via Datatracker
- Re: [GROW] Alvaro Retana's Discuss on draft-ietf-… Tim Evens (tievens)
- Re: [GROW] Alvaro Retana's Discuss on draft-ietf-… Alvaro Retana
- Re: [GROW] Alvaro Retana's Discuss on draft-ietf-… Job Snijders
- Re: [GROW] Alvaro Retana's Discuss on draft-ietf-… Warren Kumari
- Re: [GROW] Alvaro Retana's Discuss on draft-ietf-… Job Snijders
- Re: [GROW] Alvaro Retana's Discuss on draft-ietf-… Warren Kumari
- Re: [GROW] Alvaro Retana's Discuss on draft-ietf-… Alvaro Retana