IETF Logo Mail Archive

Re: [GROW] Working Group Call for Adoption draft-francois-grow-bmp-loc-peer (start 24/Oct/2023 end 07/Nov/2023)

Pierre Francois <pierre.francois.ietf@gmail.com> Mon, 11 December 2023 12:46 UTC

Return-Path: <pierre.francois.ietf@gmail.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 97D04C14F68A for <grow@ietfa.amsl.com>; Mon, 11 Dec 2023 04:46:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c0DkwFwjL6B3 for <grow@ietfa.amsl.com>; Mon, 11 Dec 2023 04:46:55 -0800 (PST)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84945C14F684 for <grow@ietf.org>; Mon, 11 Dec 2023 04:46:55 -0800 (PST)
Received: by mail-pj1-x1033.google.com with SMTP id 98e67ed59e1d1-28654179ec0so4292524a91.2 for <grow@ietf.org>; Mon, 11 Dec 2023 04:46:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1702298814; x=1702903614; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dXecqyT0AKYZnbpUA45Z3kAzfYZKrd5/ygkdaPIotII=; b=hhMdkoCuhKaZXFNASkvqlLQUyOdsxeRblWZcy2TOuyKuZxND24iaJNu55FxdqgRYj9 sy1BHBKNTUk5+qcM5SkhYB9PntfNR5oRjXEZp3Z/2bmI6ZPqhtPvBxyYS6xPdfnJfgmc VdsJ0JWrVDsJvrf4GxrKZNCOXr47aTlQyDpR9mjpCV+Zx2R2btrXnPCK2cFSzGUbYErH xF5FIYAku+acJiwKRgIRd7lyucGWsGkT77xQosFnOMgA/JLQS6xOrXQDdVbLSDuBEeyi vfLyV5PFRcIpzgp36WuKY4j4PPbH8tvE2U7YMQXxAC40t7U9JIeKUoUbqw64uHOer+Px pWAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702298815; x=1702903615; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dXecqyT0AKYZnbpUA45Z3kAzfYZKrd5/ygkdaPIotII=; b=i5BP5ntjLBtBdOT+tXyBZ1T7pHFpa85ZB9rfRAsUg+5+nQmsCkHOyFbVcYQKXxbHZd mML4GGqnuzzYgJ9K78JtlLv/o2Q0WDDr3M1+zEQZUyylCgx7sm0WjWmQvbUPi5uA3KBe VqrrFB2LHKD2j4GG5/y3mlS+q54q01hnGS/mXapOdAWxJy22Je5vC5GUDDeIfccjXCJF D+lgnHD9A4hRmruZTPwlM07bY6vyVVjvCusPe0uyfFRyoCYE49XUUF0OwMJMZLtTJBa5 SK05xOth/QmTv60yg4X0tSow0eRJLEGDrk29voyrvkbwNlyNmH3C/qgZvPJ6pI7OvxJh 75IQ==
X-Gm-Message-State: AOJu0Yy+UoIcMxhPYgd5rTDdKECWr/81uOYbEfX5Glw9R5TJK5rhJR9C JwCdcptz9Wdq+WPw7wkZPDa1Jqf261Htt8QpmU8=
X-Google-Smtp-Source: AGHT+IFNUH8cngIpUur6wXpID37gnkSPw8bY9dABYVsALhmIxDFHEVnhRxn+z3mCAb+qjLLualZXZ8yAhRcgIjRTdWE=
X-Received: by 2002:a17:90b:1e07:b0:286:6cc1:3f25 with SMTP id pg7-20020a17090b1e0700b002866cc13f25mr3159110pjb.92.1702298814584; Mon, 11 Dec 2023 04:46:54 -0800 (PST)
MIME-Version: 1.0
References: <ZTeruakgQVGB4upB@snel> <20231104094141.GD12685@pfrc.org>
In-Reply-To: <20231104094141.GD12685@pfrc.org>
From: Pierre Francois <pierre.francois.ietf@gmail.com>
Date: Mon, 11 Dec 2023 13:46:43 +0100
Message-ID: <CAFNmoOGztPw8rdnRT6AWe4itZSi_BPsSWaKi8yCddjjB6fJP3g@mail.gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: Job Snijders <job=40fastly.com@dmarc.ietf.org>, grow@ietf.org
Content-Type: multipart/alternative; boundary="000000000000251a6c060c3b5439"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/aRbhKuQ_3ugXJGRdIay2HJZjCLo>
Subject: Re: [GROW] Working Group Call for Adoption draft-francois-grow-bmp-loc-peer (start 24/Oct/2023 end 07/Nov/2023)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 11 Dec 2023 12:46:56 -0000

Hello Jeff,

Sorry for the (extremely) late reply.

Le sam. 4 nov. 2023 à 10:41, Jeffrey Haas <jhaas@pfrc.org> a écrit :

> On Tue, Oct 24, 2023 at 01:34:17PM +0200, Job Snijders wrote:
> > The authors of draft-francois-grow-bmp-loc-peer asked whether GROW
> > working group could consider adoption of the internet-draft.
> >
> > This message is a request to the group for feedback on whether this
> > internet-draft should be adopted.
>
> I think the work should be adopted.
>
> Further comments for the authors on this version:
>
> - The address selector is sufficient for ipv4, ipv6, but not ipv6
> link-local
>   addresses.
>

That's a good point.  We could add an "Address Type" field in the TLV,
IPv4, IPv6, and "IPv6 Link-Local" which would allow to define an interface
id or interface name bound with that ipv6 address.
To keep the footprint as low as possible we'd prefer an interface id "à la"
SNMP but if this is not flexible enough a string for the interface name
could work too.

> - The authors should consider what, if anything, should be done about BGP
>   routes learned from non-BGP live speakers; e.g. APIs or static
>   configuration.
>


In 2.1 we specify that self-originated routes are advertised with a zero
value Peer Address in the TLV. To the best of our knowledge, API and
statically configured routes would fall under that category.
Are we missing something? Do you mean something different than this by
"APIs or static"?


> - Probably a general comment on the TLV procedures over-all, the error
>   handling for cases of conflicting information from the TLVs needs to be
>   addressed.  For example, what if NLRI index 5 is present both in a group
>   and individually and conflicting state is expressed.
>

We'll happily let the authors of draft-ietf-grow-bmp-tlv reply to this :)
We'll align with whatever they decide if there are any changes to make on
our side.

Regards,




>
> -- Jeff
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>

v2.23.0 | Report a Bug | By Email