Link Management Protocol (LMP) Management Information Base (MIB)
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: Internet Architecture Board <firstname.lastname@example.org>, RFC Editor <email@example.com>, ccamp mailing list <firstname.lastname@example.org>, ccamp chair <email@example.com> Subject: Protocol Action: 'Link Management Protocol Management Information Base' to Proposed Standard The IESG has approved the following document: - 'Link Management Protocol Management Information Base ' <draft-ietf-ccamp-lmp-mib-11.txt> as a Proposed Standard This document is the product of the Common Control and Measurement Plane Working Group. The IESG contact persons are Bert Wijnen and Ross Callon. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ccamp-lmp-mib-11.txt
Technical Summary This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling the Link Management Protocol (LMP). Working Group Summary The Working Group has consensus to publish this document as an RFC at Proposed Standard level. Protocol Quality This document was reviewed for the IESG by Bert Wijnen RFC-Editor note: 1. Pleas clarify text. Section 2, 2nd sentence OLD: Along with Generalized MPLS (GMPLS) [RFC3471], the Link Management Protocol [LMP], which primary purpose is to manage traffic engineering (TE) links, is one of the key components of this stan dardization activity. NEW: Generalized MPLS (GMPLS) [RFC3471] and the Link Management Protocol [LMP] are key components of this standardization activity. The primary purpose of LMP is to manage traffic engineering (TE) links.