[mpls] Query regarding MPLS P2MP ID usage

venkatesan mahalingam <venkatflex@gmail.com> Tue, 27 July 2010 12:45 UTC

Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CDC23A68D9; Tue, 27 Jul 2010 05:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level:
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O2L8DC6uvTqK; Tue, 27 Jul 2010 05:45:44 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 5A88E3A68D4; Tue, 27 Jul 2010 05:45:44 -0700 (PDT)
Received: by pxi20 with SMTP id 20so520675pxi.31 for <multiple recipients>; Tue, 27 Jul 2010 05:46:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=W54rN0Sj7JYNuI1mWW73Faby87kpTnWJmwCoeCFdDMM=; b=DPlzGkk0uDDv1AW4aXECbTCb8q3l0Ug/ZKIXbbTqQNEqjsUxHoVTEejPMr2jaY9x3k qZEbfKKFwqzrTx/zUpreljbmz/Eld3AzeEcmH//8xJQGGi38u1c50ztDRc+JkLv8X3TQ p2G68D0J2p4WjqtOyffwbsJKXS0Z6vGNY1+cg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=SnAbJVp20x4rVcW5b1keqeziKP6loS7c8kaOKG8qHebJ0AW3aU01nE7168JVSGkMsB JQoPKCsoD+Yv0FwwHxtPPjHn1DZ+0+NHrY2UCi9EYVQMD+t8Uc1dIhi+7scfmSF4Lo69 gqwqO7A6pMPOdFWQ/arkhf9H4JKhECx/gjG/g=
MIME-Version: 1.0
Received: by 10.142.199.20 with SMTP id w20mr3799222wff.176.1280234766096; Tue, 27 Jul 2010 05:46:06 -0700 (PDT)
Received: by 10.142.77.1 with HTTP; Tue, 27 Jul 2010 05:46:05 -0700 (PDT)
Date: Tue, 27 Jul 2010 18:16:05 +0530
Message-ID: <AANLkTimNy3X8PB-Un9cEmgKFv=EGA_PX=s_GYxKiunEv@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: mpls-tp@ietf.org, mpls <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="000e0cd258827659d0048c5de2d0"
Subject: [mpls] Query regarding MPLS P2MP ID usage
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 12:45:46 -0000

Hi,

As per draft-ietf-mpls-p2mp-te-mib-09.txt<http://tools.ietf.org/html/draft-ietf-mpls-p2mp-te-mib-09.txt>
draft,
P2MP MPLS-TE MIB is extended from MPLS-TE-STD-MIB.

So, mplsTunnelTable table can contain the informations for both normal MPLS
tunnels and MPLS P2MP tunnels.
How the two entries can be differentiated, do we need to check the entry
existence in the P2MP tunnel to
confirm the entry in the mplsTunnelTable is for P2MP tunnel?

 P2MP tunnel information in mplsTunnelTable is as follows:
     {
       mplsTunnelIndex              = 4,
       mplsTunnelInstance           = 0,
       mplsTunnelIngressLSRId       = "192.0.2.1",
       -- The tunnel egress LSR ID is used to
       -- hold the P2MP ID for the P2MP LSP tunnel
 *      mplsTunnelEgressLSRId        = 328,*
*       .........................*
*       .........................*
   }

What if the mplsTunnelEgressLSRId unsigned 32 bit integer matches with the
normal MPLS-TE tunnel's egress-id (Egress node IP address)?
Are we assuming that P2MP Id (mplsTunnelEgressLSRId) will not overlap the
valid IP address range?

-- 
Best Regards,
Venkatesan Mahalingam.