Subject: draft-ietf-ppvpn-mpls-vpn-04.txt

From: Joan Cucchiara <[email-masked]>
Date: Tue, 03 Sep 2002 18:01:55 -0400

Hi,

Had a few questions on this MIB.

1) the name of the mib is 'MPLS/BGP Virtual
Private Network Management Information Base
using SMIv2' and the abstract says that
this MIB is based upon draft-ietf-ppvpn-rfc2547bis-02.txt
which has the title of:

'BGP/MPLS VPNs'

So my question is: could this MIB follow the draft
that is associated with it and be called 
'BGP/MPLS ...' ?

(also section 6.0 refers to BGP/MPLS VPN and not MPLS/BGP VPN)

2) The MplsVpnName which is a 32 Octet string, which 
may or may not be the VPN ID.  Could the description be
clarified to say if the VPN ID is not used as the value,
what the value is supposed to be?  (If not in the TC then
maybe in the index itself).

Also, I do not understand how this index could be
a NULL string for more than one VPN, otherwise, it 
would be difficult to interpret which VPN an interface
belongs to.
 
Is this possible?  

3) The following objects might work better
as Gauge32:

mplsVpnVrfActiveInterfaces
mplsVpnVrfAssociatedInterfaces
mplsVpnVrfPefCurrNumRoutes

4) There are references to an MPLS-VPN Interface and
yet the MIB uses mpls(166) or mplsTunnel(150)
for the ifType.

Was a new  Mpls-VPN ifType considered?   (The reason
a new ifType might want to be considered is because
if 2 (or more?) ifTypes are possible
to uniquely identify a BGP/MPLS interface, a new ifType
might be cleaner, especially if the MplsVpnName is allowed 
to be NULL.

Thanks, 
 -Joan