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

Thomas Morin <thomas.morin@orange.com> Fri, 11 August 2017 14:50 UTC

Return-Path: <thomas.morin@orange.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA73F132681 for <bess@ietfa.amsl.com>; Fri, 11 Aug 2017 07:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level:
X-Spam-Status: No, score=-2.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_BRBL_LASTEXT=1.449, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 1CciKdJJLC-Z for <bess@ietfa.amsl.com>; Fri, 11 Aug 2017 07:50:54 -0700 (PDT)
Received: from r-mail1.rd.orange.com (r-mail1.rd.orange.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id A6CCA132674 for <bess@ietf.org>; Fri, 11 Aug 2017 07:50:53 -0700 (PDT)
Received: from r-mail1.rd.orange.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 17BAAA44087; Fri, 11 Aug 2017 16:50:52 +0200 (CEST)
Received: from FTRDCH01.rd.francetelecom.fr (unknown [10.194.32.11]) by r-mail1.rd.orange.com (Postfix) with ESMTP id 03D6EA44057; Fri, 11 Aug 2017 16:50:52 +0200 (CEST)
Received: from l-fipglop (10.193.71.46) by FTRDCH01.rd.francetelecom.fr (10.194.32.11) with Microsoft SMTP Server id 14.3.352.0; Fri, 11 Aug 2017 16:50:51 +0200
Message-ID: <1502463051.5254.3.camel@orange.com>
From: Thomas Morin <thomas.morin@orange.com>
To: Hiroshi Tsunoda <tsuno@m.ieice.org>, "bess@ietf.org" <bess@ietf.org>
CC: Glenn Mansfield Keeni <glenn@cysols.com>
Date: Fri, 11 Aug 2017 16:50:51 +0200
In-Reply-To: <CAPbjwkze+H7sQ43XmU98hrfjDHfne2FOGu_sR9+WpPVoh35q0A@mail.gmail.com>
References: <CAPbjwkze+H7sQ43XmU98hrfjDHfne2FOGu_sR9+WpPVoh35q0A@mail.gmail.com>
Organization: Orange S.A.
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.22.6-1
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/HogKfVjjvjQi4RdyXF27dPpbM7g>
Subject: Re: [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: Fri, 11 Aug 2017 14:50:56 -0000

Hi Tsuno,

(below)

Hiroshi Tsunoda, 2017-08-08 22:20:
> 
> 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.

For each different type, there is a natural/preferred format, but
there is no format valid across all different types.

When the type is for IP multicast tree, it would be natural to display
it as an IP adress, but when the type is for an LSP, it depends on the
MPLS signaling protocol (mLDP, P2MP RSVP-TE)...

I don't know if there is a better solution than to display a
hexadecimal byte string.

>    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?

Not as far as I know.
I don't think there is any canonical way to display, e.g. the <Extended
Tunnel ID, Reserved, Tunnel ID, P2MP ID> tuple of an RSVP-TE P2MP LSP
SESSION Object.

> 
> 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. 7.4.1.1 of RFC6513,
>     but Flags is not required.
> 
>     b-1) How about MPLS Label? Is it required to be included in the
> index?

Doing lookups in this table based on an MPLS label does not look like
something natural to do, given that the label allocated may change over
time. I would be tempted to answer no to your question.

-Thomas



> 2017-07-09 14:11 GMT+02:00 Glenn Mansfield Keeni <glenn@cysols.com>om>:
> > 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.
> 
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess