[Lsvr] Need clarification on IGP-Metric TLV for LS Link Attributes in BGP-SPF deployments

Pushpasis Sarkar <pushpasis.ietf@gmail.com> Mon, 09 March 2020 15:31 UTC

Return-Path: <pushpasis.ietf@gmail.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D30B3A12A3; Mon, 9 Mar 2020 08:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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] 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 Ky4-cmzlTNhL; Mon, 9 Mar 2020 08:31:09 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 E9B1F3A12B6; Mon, 9 Mar 2020 08:31:07 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id h5so2151540edn.5; Mon, 09 Mar 2020 08:31:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=Z9HlxPkU8+7zFplF8yM1JBeRX443bhY8vWdcvuFDJ2U=; b=TPKTkbuhy3f8Fw/i5atA+KAUiY0Ra4YjVwX+fbWtQQz1s7CPZKDErms3tB7YRlISts fVyLjFCIp/sz6RD9IXDDA/L6ClIZxXMr06N6Rpi3WHmqu+R+eXJyc40Uyq9cvHUpcwpX kS0qFeCxVvhNulLJCQmB+qd7OrSslX3/4Cw1Js/OBO3c8Xx7v3obn4qGOJwoeHYqHXQW RzxJ20aLNcaWtL/26rG0Q/O6xcbvvodQEJccH60yLIL3QWJctqK+RcRAXE2eBSxJMhxl dxrE+wU8ahceclv2cKHaf2xCvwDWQiXv8L6r3GnZ6/MNaZogTSQ2SRGptpl1papk0Lva Cs5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=Z9HlxPkU8+7zFplF8yM1JBeRX443bhY8vWdcvuFDJ2U=; b=d8IVJtFcIO0Coht4tDGID8WKJE/n7Sj4M/zSbDuEDGozvtEW/MXsRRessUNEzSRk7k egIVTIjQE7oGXU3LG1VDIzkcIylFwzP/ctQ7b0VInYuf7HBWplb6XYpuQixVEiloz/h8 MTbXG7N7mb611MH8a9rWqRNPlItgAWmqPpsyPOXGo4x9gzBXvCA4K/7TI2tP89hE2Yaz BjbA6SuSKPo3JT4DGGxAfexfAwY6KSONpAwU63OI7yMQ/VLCXe7qr9Xl6CFWezYVmXmK xcjR8m+vXTHjuDgyKU0IqqvREGFSoxZgcGjIvaxKdJixfdQ4TRyUXAQBD14OrG6WQAlC tMXQ==
X-Gm-Message-State: ANhLgQ0KclqfWVj/eSJWmbeVnH2mt8qZJXVVlt7I+igYURsrbDXOyemn AFaL24pvVpFYU0lJuA9Lm+wC4eEhlMu/Ebt142kMc4Mn
X-Google-Smtp-Source: ADFU+vtyoT0D9cz9clcjKUHbP0Ivv/tDXsBs/w5PXm1eVhSZEGlhYsn20K56fjKOb6bx6tDWjv1++9m923uX2AlgsgE=
X-Received: by 2002:a05:6402:951:: with SMTP id h17mr14934534edz.79.1583767866094; Mon, 09 Mar 2020 08:31:06 -0700 (PDT)
MIME-Version: 1.0
From: Pushpasis Sarkar <pushpasis.ietf@gmail.com>
Date: Mon, 09 Mar 2020 21:00:55 +0530
Message-ID: <CAEFuwkh=zmq_W_DD_MLePtc2pAZY7T1aENbbE01_cU588ZxDxQ@mail.gmail.com>
To: draft-ietf-lsvr-bgp-spf@ietf.org
Cc: lsvr@ietf.org
Content-Type: multipart/alternative; boundary="00000000000010bc3d05a06db17d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/Wtyl0Yu67fMNBqDDMbEfo5aO_Rg>
Subject: [Lsvr] Need clarification on IGP-Metric TLV for LS Link Attributes in BGP-SPF deployments
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2020 15:31:11 -0000

Hi Authors,

I need a small clarification on how the Link IGP-Metric TLV (type 1095) for
the links originated by an BGP-SPF speaker look like. My doubt is
specifically on what would be the length of the metric value. For example,
following is the excerpt from RFC7752 section 3.3.2.4 which specifies the
length to be 1, 2 or 3 bytes for ISIS narrow-metrics, OSPF and ISIS
wide-metrics.

3.3.2.4.  IGP Metric TLV

   The IGP Metric TLV carries the metric for this link.  The length of
   this TLV is variable, depending on the metric width of the underlying
   protocol.  IS-IS small metrics have a length of 1 octet (the two most
   significant bits are ignored).  OSPF link metrics have a length of 2
   octets.  IS-IS wide metrics have a length of 3 octets.

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |              Type             |             Length            |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     //      IGP Link Metric (variable length)      //
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                     Figure 21: IGP Metric TLV Format


What should be the length of the metric field when the origin is a BGP-SPF
speaker?

Looking forward to your clarification on this. Also it will be appreciated
a lot if a sentence or two can be added to the draft clarifying the above
in the next version.

Thanks and regards,
-Pushpasis