[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
MPLS objects in GMPLS MIB modules
- To: <mreview@ops.ietf.org>
- Subject: MPLS objects in GMPLS MIB modules
- From: <jcucchiara@mindspring.com>
- Date: Wed, 28 Sep 2005 22:00:21 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=s84QCGz8kQni8/8T0nbKUETWVy92HuS00u0nbswIjpJ3kql/OO9cIv8xSbZB5sdL; h=Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Greetings,
This is a little difficult to explain, but here it is:
* GMPLS is a superset of MPLS
* MPLS became a working group prior to GMPLS,
and thus, several (proposed standard) RFCs
containing MIB modules exist in MPLS already.
* the GMPLS working group now has a few draft
MIBs which are being reviewed and I have found
a few objects (in at least 3 different tables)
which could (should?) be in MPLS MIB module(s).
In other words, if an implementation only
supports MPLS, then these objects might
be useful to that MPLS implementation, although
they are defined in the GMPLS MIBs. (These objects
do apply to GMPLS also.)
Personally, I am okay with leaving the objects in
the GMPLS MIB modules because
implementations that support MPLS will probably
also support GMPLS at some future point, and also
because of the evolution of MPLS followed by GMPLS.
I would appreciate some guidance on this:
would this be acceptable to other MIB reviewers?
thank you,
-Joan