IP TUNNEL MIB Extention for softwire
draft-shishio-softwire-rfc4087update-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Shishio Tsuchiya , Jacni Qin | ||
| Last updated | 2013-01-10 (Latest revision 2012-07-09) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo defines a Management Information Base (MIB) module 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. IP TUNNEL MIB[RFC4087] provides provisioning capability for IPv4 and IPv6 tunnel by SNMP. But it is not eqnough to support modern tunnel protocol such as 6rd[RFC5969] and MAP[draft-ietf-softwire-map]. The document describes extention of IP TUNNEL MIB[RFC4087] to support 6rd[RFC5969] and MAP[draft-ietf-softwire-map].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)