[Idr] Error handling for BGP extended NH encoding capability
Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Tue, 12 March 2024 11:15 UTC
Return-Path: <muthu.arul@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 6876CC151089 for <idr@ietfa.amsl.com>; Tue, 12 Mar 2024 04:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 E5DpQEJC9EwM for <idr@ietfa.amsl.com>; Tue, 12 Mar 2024 04:15:30 -0700 (PDT)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (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 B120AC151084 for <idr@ietf.org>; Tue, 12 Mar 2024 04:15:28 -0700 (PDT)
Received: by mail-ed1-x533.google.com with SMTP id 4fb4d7f45d1cf-564647bcdbfso4370421a12.2 for <idr@ietf.org>; Tue, 12 Mar 2024 04:15:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710242126; x=1710846926; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=kdqd93o3K+Hgn9XfEhKcw1xlsQemw6OatwPUmCiMyyo=; b=iWCKcz01MDQ7kTngT8ZGcdLvfFmUcXIHzQ3kW+n1qDfgF+ABiLWzs8buLCZKvgf1kA Ke5kQE5wGIVEQzWpd4P95jcJ6iu14L+VNAwjqokBoHNLP3lvGA11xRShO3ADAIVd/ryw 1Q2fOB3cP3VTSDgGdl0A34S8RugNvPyQovJWQLibJeMaxWMrlr7l8a8Ibq/Znkx/3bGk eZwL4ecZaHog28dN4EZt9lzKsZ9ntfDNqAf0rxB2W/9d6GKujQ3MHQVe2e9aqdJkuONt TyJ23W+2YEZyQytCgpiit7UMkP5P/vfFIwgjyNzpilJxf22qoKhKoy52WAb3ZdPJymt/ 7D/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710242126; x=1710846926; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=kdqd93o3K+Hgn9XfEhKcw1xlsQemw6OatwPUmCiMyyo=; b=WDHdMbKgt3JQlO4Ta5Rp8B/tdhQbcRuPf97BUVGflVltckgwudjVPA90RHsEMPnHTP V+Sl3Y+EC/ZDjyyz74uOg4nIotjT84OFrUgj5eLAJm19AIq2FN/lgZAe5wIidwVo4HS5 Dv6O9E0RQ8juZ0hhu1ukN/mWtDYpvgZxAs5Fq/QbVcA4JcX5ivjMC7ljAh9l6FOQcWkI 4jIH8pm6DVzWIVwldM+GRjJaDn4TQN0xRO2B/AQSOmlQVzpsZV7anK4hwINC3S8WLU1w C19al4o8rncrYEwEuwYHHmTblSe7prhF5WCBILkf0A/SRp3NFZ4CmLcVvQMptPFJrnyI /+Lg==
X-Gm-Message-State: AOJu0YxbsdsIBm0JtLRmOnp5xs7Prwo+qAsKlfl6FWHCrhkgs0VQS6Lh QBLjkZdJFKx1NhzWaYecKkQ8KSi1hGNPC6f+BVAUqGq4Sbb37D/GBQrCN4CGM5S8tBhxUFqS6m6 t3W9JtUZ2lLSb2glj8nrxNB2tAev/GZ6EjcA=
X-Google-Smtp-Source: AGHT+IGXx3dxucBz1Eo8DQtEi/Ve08ZV3M/4AGfp8jt+hg9JSSuugdOav1wcSC6lnujISvfTFprESHioa3rtJQh2IQY=
X-Received: by 2002:a50:d7c2:0:b0:567:a740:7172 with SMTP id m2-20020a50d7c2000000b00567a7407172mr5311985edj.41.1710242126364; Tue, 12 Mar 2024 04:15:26 -0700 (PDT)
MIME-Version: 1.0
From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Date: Tue, 12 Mar 2024 16:45:14 +0530
Message-ID: <CAKz0y8x+jyJ+9O8Luh9AjQ3ZQsXTw2qm3Mf_R5Hbnt8j8rUcQg@mail.gmail.com>
To: "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006c0ad5061374c69c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_Kw9_Bv4M-2nMfD2Hg671dTJCeI>
Subject: [Idr] Error handling for BGP extended NH encoding capability
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 12 Mar 2024 11:15:30 -0000
Hi, RFC8950 specifies the BGP extended NH encoding capability as: <snip> Since this document only concerns itself with the advertisement of IPv4 NLRI and VPN-IPv4 NLRI with an IPv6 next hop, this specification only allows the following values in the Capability Value field of the Extended Next Hop Encoding capability: NLRI AFI = 1 (IPv4) NLRI SAFI = 1, 2, 4, 128, or 129 Nexthop AFI = 2 (IPv6) This document does not specify the use of the Extended Next Hop Encoding capability with any other combinations of <NLRI AFI, NLRI SAFI, Nexthop AFI>. </snip> But, it does not say what a receiver supporting the extended NH encoding capability should do if it receives an invalid <NLRI AFI, NLRI SAFI, Nexthop AFI> in this capability. This is also unlike a capability that the receiver does not itself support or recognize which must be ignored as per RFC5492. Comments? Regards, Muthu
- [Idr] Error handling for BGP extended NH encoding… Muthu Arul Mozhi Perumal