<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.perrault-behave-natv2-mib" target="https://datatracker.ietf.org/doc/html/draft-perrault-behave-natv2-mib-05">
   <front>
      <title>Definitions of Managed Objects for Network Address Translators (NATs)</title>
      <author initials="S." surname="Perreault" fullname="Simon Perreault">
         <organization>Jive Communications</organization>
      </author>
      <author initials="T." surname="Tsou" fullname="Tina Tsou (Ting ZOU)">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="S." surname="Sivakumar" fullname="Senthil Sivakumar">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="T." surname="Taylor" fullname="Tom Taylor">
         <organization>PT Taylor Consulting</organization>
      </author>
      <date month="June" day="16" year="2015" />
      <abstract>
	 <t>This memo defines a portion of the Management Information Base (MIB) for devices implementing the Network Address Translator (NAT) function.  The new MIB module defined in this document, NATV2-MIB, is intended to replace module NAT-MIB (RFC 4008).  NATV2-MIB is not backwards compatible with NAT-MIB, for reasons given in the text of this document.  A companion document deprecates all objects in NAT-MIB.  NATV2-MIB can be used for the monitoring of NAT instances on a device capable of NAT function.  Compliance levels are defined for three application scenarios: basic NAT, pooled NAT, and carrier-grade NAT (CGN).
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-perrault-behave-natv2-mib-05" />
   
</reference>
