IP Tunnel 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> Subject: Protocol Action: 'IP Tunnel MIB' to Proposed Standard The IESG has approved the following document: - 'IP Tunnel MIB ' <draft-ietf-ipv6-inet-tunnel-mib-04.txt> as a Proposed Standard This document is the product of the IP Version 6 Working Group. The IESG contact persons are Margaret Wasserman and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipv6-inet-tunnel-mib-04.txt
Technical Summary This memo defines a Management Information Base (MIB) for use with network management protocols in the Internet community.Â In particular, it describes managed objects used for managing tunnels of any type over IPv4 and IPv6 networks.Â Extension MIBs may be designed for managing protocol-specific objects. Likewise, extension MIBs may be designed for managing security-specific objects.Â This MIB does not support tunnels over non-IP networks. Management of such tunnels may be supported by other MIBs. Working Group Summary The IPv6 working group has reviewed this document and this document reflects the consensus of the group. Protocol Quality This document has been reviewed by members of the firstname.lastname@example.org mailing list, the IPv6 working group chairs, and members of the ipv6mib mailing list. A MIB Doctor review was performed by Bert Wijnen. This document was reviewed for the IESG by Margaret Wasserman. RFC Editor Note Please make the following change: OLD: Note: instead of the name tunnelIfTOS, a better name would have been tunnelIfDSCPMethod, but the existing name appeared in RFC 2776 and existing objects cannot be renamed." NEW: Note: instead of the name tunnelIfTOS, a better name would have been tunnelIfDSCPMethod, but the existing name appeared in RFC 2667 and existing objects cannot be renamed."