[bess] A question about Tunnel Identifier in PMSI Tunnel Attribute etc.

Hiroshi Tsunoda <tsuno@m.ieice.org> Tue, 08 August 2017 20:20 UTC

Return-Path: <dr.h.t@ieee.org>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 2B64F132652 for <bess@ietfa.amsl.com>; Tue, 8 Aug 2017 13:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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=ieee-org.20150623.gappssmtp.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id vvsf0Axj9R5M for <bess@ietfa.amsl.com>; Tue, 8 Aug 2017 13:20:44 -0700 (PDT)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 ED27A13264C for <bess@ietf.org>; Tue, 8 Aug 2017 13:20:43 -0700 (PDT)
Received: by mail-qk0-x22b.google.com with SMTP id d145so25868086qkc.2 for <bess@ietf.org>; Tue, 08 Aug 2017 13:20:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee-org.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to:cc; bh=sttWKHk9RG+wBneu53LzTib5lnRwNlGzMM6E336TaTI=; b=eBMpKj2rxP1ZServoDfLEy5XE54ClVK5UC/W7yaP7jIZeQnCD+wY/NgaGD8rY5Nzh/ CQ50orZZw6ht/bmW3YRMCkUhjPwLjGkYd0ZIcBUImGUOaUfAOOZFE/zdF9lUDSFR2Fkc BBR4aePjVGVcyryX8ncI363a+AO/OzlnSMHzOIyqHiPpP2R272khya9QHj9xo+o7yRVf PUOG87mWEMhKwepDqsGl26GMxSkFN6XEWUNXLQMzhDIhARALOICW9E1kmf3REbUTNxUt V38Q96rMmgoBcm8keQLZCfaHR6yxDfYtlQniQu+fQEmeVBVLyIy8pju1ZU9gSavawouk KD1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to:cc; bh=sttWKHk9RG+wBneu53LzTib5lnRwNlGzMM6E336TaTI=; b=cN6vmNnYLFCkuntiTinpVrPBN56vu1ooj/dgGofO5lMORQj5YTBtSacWWW0qd0Vk/t 46uTWaXY9up/FFpiQbMA6xqDzpxtL0Ohhn+vGxD3gwJRm9DcwjAle4v4bL3JpAtLLMAl +OzAr9PPCDMpCQdOGybL81A8k8yqhojgW7MsAUWwrRnoF7glq7G/aJ3QvilcR+keC9nv 5fGjNp1gku/eiIcGFVTOXGYm8sg1KrrnkcpKLDwrJkEbxGIED09VjjRLItdAJigboHI8 GZc/KXisHDTsd3FihwozBeFdGNelw9sKNmHQr6nJz84G5bexyfsdeuYzMuoy2i/xVQr/ HvxA==
X-Gm-Message-State: AHYfb5hn+IUGN9H6OCar40+eOLh2bTeoUl8fMRGreMuqr9AnP99n7+yC mJCFKDfdb+5Oz2KSFu7vodEL1QaVk6MA
X-Received: by with SMTP id p13mr7259409qkl.186.1502223642867; Tue, 08 Aug 2017 13:20:42 -0700 (PDT)
MIME-Version: 1.0
Sender: dr.h.t@ieee.org
Received: by with HTTP; Tue, 8 Aug 2017 13:20:02 -0700 (PDT)
From: Hiroshi Tsunoda <tsuno@m.ieice.org>
Date: Tue, 08 Aug 2017 22:20:02 +0200
X-Google-Sender-Auth: PuKW3p6dO3_9GwPZbx3KCdKOMfk
Message-ID: <CAPbjwkze+H7sQ43XmU98hrfjDHfne2FOGu_sR9+WpPVoh35q0A@mail.gmail.com>
To: "bess@ietf.org" <bess@ietf.org>
Cc: Glenn Mansfield Keeni <glenn@cysols.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/RxbgbDvvl7DgV-YUoYDy7zaAR_A>
Subject: [bess] A question about Tunnel Identifier in PMSI Tunnel Attribute etc.
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Aug 2017 20:20:46 -0000


Please forgive my insufficient knowledge about MVPN,
but I need some advice to answer the MIB doctor's
questions (attached in the end of this mail)

a) Format and examples of Tunnel Identifier in PMSI Tunnel Attribute

   L2L3-VPN-MCAST-TC-MIB provides a textual convention
   (L2L3VpnMcastProviderTunnelId) representing
   the Tunnel Identifier of a P-tunnel.

   a-1) I would like to know if there is  any preferred format
          when a Tunnel Identifier is printed.

   a-2) In the case that there is no preferred format,
          the MIB doctor request us to show some actual
          examples of the Tunnel Identifier.
          Is there any good reference to see the actual examples?

b) Required information to identify a particular P-tunnel

    l2L3VpnMcastPmsiTunnelAttributeTable defined in L2L3-VPN-MCAST-MIB
    is a table to provide P-tunnel information.
    Currently the index of this table is composed of
    information objects representing Flags, Tunnel Type,
    MPLS Label, and Tunnel Indentifier in
    delivered in PMSI Tunnel Attribute.
    I think the index must be composed only of minimal
    objects to identify a particular P-tunnel.
    Thus, Tunnel Type and Tunnel Indentifier are required
    for the index as described in Sec. of RFC6513,
    but Flags is not required.

    b-1) How about MPLS Label? Is it required to be included in the index?

I hope that someone could give me some help.

Thanks in advance,

-- tsuno

2017-07-09 14:11 GMT+02:00 Glenn Mansfield Keeni <glenn@cysols.com>:
> L2L3-VPN-MCAST-TC-MIB is almost OK.
> smilint gives warnings
> (snip)
>   L2L3-VPN-MCAST-TC-MIB:112: [5] {type-without-format} warning: type
>   `L2L3VpnMcastProviderTunnelId' has no format specification
> This may be avoided by specifying a format in which the
> L2L3VpnMcastProviderTunnelId should be printed.
> Is there a preferred format? How will this be printed?
> One continuous octet string?
> (snip)
> But before we go on to the next stage could you please confirm that
> A. The l2L3VpnMcastPmsiTunnelAttributeTable needs all of the following
>    four MOs as index for its rows
>              l2L3VpnMcastPmsiTunnelAttributeFlags,
>              l2L3VpnMcastPmsiTunnelAttributeType,
>              l2L3VpnMcastPmsiTunnelAttributeLabel,
>              l2L3VpnMcastPmsiTunnelAttributeId
>    The l2L3VpnMcastPmsiTunnelAttributeId by itself is inadequate? If yes
>    please explain it to me. Or point to the text that contains the
>    explanation.
> I have been unable to confirm the above from the draft - that is very
> likely due to my lack of understanding of the l2L3VpnMcast technology.