RE: Questions about draft-ietf-ccamp-lmp-mib-00.txt

[Fugui Wang <fwang@axiowave.com>]

Martin,

Thanks for the clarification. But isn't 
lmpDataBearingLinkEncodingType also redundant with
dataBearingChannelEncodingType and teLinkEncodingType 
in the link bundling MIB? 

Thanks,
Fugui

-----Original Message-----
From: Martin Dubuc [mailto:martin.dubuc@edgeflow.com]
Sent: Wednesday, October 24, 2001 2:09 PM
To: Fugui Wang
Cc: sudheer@nayna.com; tnadeau@cisco.com; jplang@calient.net;
evan@calient.net; ccamp@ops.ietf.org
Subject: RE: Questions about draft-ietf-ccamp-lmp-mib-00.txt


Fugui,

The lmpRemoteTeLinkId and lmpRemoteTeLinkType was removed from the
latest LMP MIB because it was redundant with information stored in the
link bundling MIB (see
http://www.ietf.org/internet-drafts/draft-ietf-mpls-bundle-mib-00.txt).
The link bundling MIB contains a TE link table (teLinkTable) which
captures the information you are looking for. The remote TE link type is
found in the  teLinkNumberingType object and the remote TE link
identifier is either teLinkRemoteIpAddr or teLinkIncomingIfId depending
on whether or not the TE link is numbered or unnumbered.

Regards,

Martin

-----Original Message-----
From: Fugui Wang [mailto:fwang@axiowave.com]
Sent: Wednesday, October 24, 2001 12:08 PM
To: Martin Dubuc; 'sudheer@nayna.com'; 'tnadeau@cisco.com';
'jplang@calient.net'; 'evan@calient.net'
Cc: 'ccamp@ops.ietf.org'
Subject: Questions about draft-ietf-ccamp-lmp-mib-00.txt


I noticed that lmpRemoteTeLinkId and lmpRemoteTeLinkType were
taken away from the TE Link Table in this version. Is there
any special reason for that? In the latest LMP draft
draft-ietf-ccamp-lmp-01.txt, when we do link verification or
link summary, we still need the remote TE link ID infomation.
Would you suggest that we store the remote TE link ID in other
places instead of in the TE link Table?

Thanks,
Fugui