One document matched: draft-jpdionne-behave-nat64-mib-00.xml
<?xml version="1.0" encoding="UTF-8"?>
<rfc category="std" ipr="trust200902" updates='4008'
docName="draft-jpdionne-behave-nat64-mib-00">
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<front>
<title abbrev="NAT64 Management Information Base (MIB)">NAT64 Management Information Base (MIB)</title>
<author initials='J.P.D' surname="Dionne" fullname='Jean-Philippe Dionne'>
<organization>Viagenie Inc.</organization>
<address>
<postal>
<street>2875 boul. Laurier, suite D2-630</street>
<city>Quebec</city>
<country>Canada</country>
</postal>
<phone>+1-418-656-9254</phone>
<email>jean-philippe.dionne@viagenie.ca</email>
</address>
</author>
<author initials="M." surname="Blanchet" fullname="Marc Blanchet">
<organization>Viagenie</organization>
<address>
<postal>
<street>2875 boul. Laurier, suite D2-630</street>
<city>Quebec</city>
<region>QC</region>
<code>G1V 2M2</code>
<country>Canada</country>
</postal>
<email>Marc.Blanchet@viagenie.ca</email>
<uri>http://viagenie.ca</uri>
</address>
</author>
<date day="4" month="March" year="2011"/>
<abstract><t>This memo describes the NAT64 Management Information Base. It reuses the NAT-MIB and add specific NAT64 variables.</t></abstract>
</front>
<middle>
<section title="Introduction">
<t>
To enable IPv6-only nodes to access to IPv4-only nodes, a NAT64 <xref target="I-D.ietf-behave-v6v4-xlate-stateful"/> is used. This NAT64 requires a Management Information Base (MIB) for the purpose of managing the device. </t>
<t>The NAT-MIB <xref target="RFC4008"/> is designed to carry translation from any address family to any address family, therefore supports IPv6 to IPv4 translation such as NAT64. </t>
<t>Some specifics of NAT64 are not present in the NAT-MIB. This document describes the changes to fully support NAT64.</t>
</section>
<section title="Modifications to NAT-MIB">
<t>A revision of <xref target="RFC4008"/> is proposed.</t>
<section title="Pref64">
<t>The NAT64 uses a special prefix, named Pref64 <xref target="RFC6052"/>, to carry IPv4 destination addresses into an IPv6 address. This prefix is required for the joint operation of NAT64 and DNS64<xref target="I-D.ietf-behave-dns64"/>. The operator can choose to use the Well-Known prefix (64:ff9b::/96) or a Network-Specific Prefix.</t>
<t>We propose to include this prefix to the NatAddrMapEntry. For other type of NATs, this value will be ignored and have a null value (::/0)</t>
</section>
</section>
<section title="Configuring NAT64">
<t>This section presents considerations regarding NAT64 that doesn't require modification of the NAT-MIB.</t>
<section title="NatTranslationEntity">
<t> NatTranslationEntity is: "An indication of a) the direction of a session for which an address map entry, address bind or port bind is applicable, and b) the entity (source or destination) within the session that is subject to translation."</t>
<t>For NAT64, both the source and destination is translated. Hence, two bits must be set:</t>
<t>"inboundSrcEndPoint" and "inboundDstEndPoint" if the operator chooses to configure the NAT64 address map entry on the IPv4 network interface.</t>
<t>or</t>
<t>"outboundSrcEndPoint" and "outboundDstEndPoint" if the operator chooses to configure the NAT64 address map entry on the IPv6 Internet interface.</t>
</section>
<section title="Local and Private Terminology">
<t>Throughout <xref target="RFC4008"/> "private" and "public" are used interchangeably with "local" and "global" to refer to the networks the translator is operating on.
"local" refer to the network where the NAT sessions are initiated.
With NAT64, The IPv6 network corresponds to the "local" side and the "IPv4 Internet to the "global" side.</t>
</section>
</section>
<section title="RFC4008 Proposed Changes">
<section title="Changes to Section 3: Terminology">
<t>
<list>
<t>NAT Session:<list>
<t>"NAT sessions in the document are restricted to sessions based on TCP and UDP only." Add "ICMP". No changes needs to be made to the MIB definition ICMP can be specified as a protcocol session.</t>
<t>The "session" terminology also differs with <xref target="I-D.ietf-behave-v6v4-framework"/> definition: An "end-to-end session" in rfc4008 is a "session" in xlate.</t>
</list>
</t>
</list>
</t>
</section>
<section title="Changes to Section 4: Overview">
<t>"The address map entry also identifies the end-point of the session that must be subject to translation.". For NAT64, this sentence implies the address map entry would contain pref64:: destination address. However, the real end-point is the ipv4 destination address.
</t>
<section title="Changes to Section 4.2: natAddrMapTable">
<t>Add a paragraph for pref64 variables. Refer to <xref target="NatAddrMapEntry"/></t>
<t>Rephrase the last sentence to explain how to use NatTranslationEntity to describe NAT64.</t>
</section>
<section title="Changes to Section 4.5: natSessionTable">
<t>
"Session" terminology differs with draft-ietf-behave-v6v4-xlate-stateful's
definition. A "end-to-end session" in rfc4008 is a "session" in xlate.
</t>
</section>
<section title="Changes to Section 4.7: Notifications">
<t>"natPacketDiscard notifies the end user/manager of packets being discarded due to lack of address mappings.". We must add: "or incompatibilities in IPv4/IPv6 translation.
</t>
</section>
<section title="Changes to Section 4.9: Configuration via the MIB">
<t>TBD: Add a point about how to configure the pref64 if its NAT64.</t>
</section>
</section>
<section title="Changes to Section 5: Definitions">
<section title="IMPORT">
<t>
<figure><artwork><![CDATA[
Ipv6AddressPrefix,
FROM IPV6-TC;
]]></artwork></figure>
</t>
</section>
<section title="Update to NatAddrMapEntry" anchor="NatAddrMapEntry">
<t><figure><artwork><![CDATA[
natAddrMapEntry OBJECT-TYPE
SYNTAX NatAddrMapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This entry represents an address map to be used for
NAT and contributes to the dynamic and/or static
address mapping tables of the NAT device."
INDEX { ifIndex, natAddrMapIndex }
::= { natAddrMapTable 1 }
NatAddrMapEntry ::= SEQUENCE {
natAddrMapIndex NatAddrMapId,
natAddrMapName SnmpAdminString,
natAddrMapEntryType NatAssociationType,
natAddrMapTranslationEntity NatTranslationEntity,
natAddrMapLocalAddrType InetAddressType,
natAddrMapLocalAddrFrom InetAddress,
natAddrMapLocalAddrTo InetAddress,
natAddrMapLocalPortFrom InetPortNumber,
natAddrMapLocalPortTo InetPortNumber,
natAddrMapGlobalAddrType InetAddressType,
natAddrMapGlobalAddrFrom InetAddress,
natAddrMapGlobalAddrTo InetAddress,
natAddrMapGlobalPortFrom InetPortNumber,
natAddrMapGlobalPortTo InetPortNumber,
natAddrMapProtocol NatProtocolMap,
natAddrMapInTranslates Counter64,
natAddrMapOutTranslates Counter64,
natAddrMapDiscards Counter64,
natAddrMapAddrUsed Gauge32,
natAddrMapStorageType StorageType,
natAddrMapRowStatus RowStatus
natAddrMapPref64 Ipv6AddressPrefix
natAddrMapPref64Length INTEGER (0..128),
}
natAddrMapPref64 OBJECT-TYPE
SYNTAX Ipv6AddressPrefix
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the IPv6 address part of the Pref64
for NAT64. For a NAT64, the default value is the Well-known
prefix 64:ff9b::. For other NAT types, the prefix is ::.
The associated prefix length is found in
natAddrMapPref64Length.
::= { natAddrMapEntry 22 }
natAddrMapPref64Length OBJECT-TYPE
SYNTAX INTEGER (0..128)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The prefix length of natAddrMapPref64. For NAT64, allowed values
are: 32, 40, 48, 56, 64 and 96.". For other NAT types, value is
0."
::= { natAddrMapEntry 23 }
]]></artwork></figure>
</t>
</section>
</section>
<section title="Complete updated NAT-MIB">
<t>Update is done in conformance to section 10 of <xref target="RFC2578"/>.</t>
<t><figure><artwork><![CDATA[
TBD
]]></artwork></figure></t>
</section>
</section>
<section title="Security Considerations">
<t>No additionnal security issues. See <xref target="RFC4008"/> section 7.</t>
</section>
</middle>
<back>
<references title='Normative References'>
<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.4008.xml"?>
<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.6052.xml"?>
<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2578.xml"?>
</references>
<references title='Informative References'>
<?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-behave-v6v4-framework-10.xml"?>
<?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-behave-v6v4-xlate-stateful-12.xml"?>
<?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-behave-dns64-11.xml"?>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 04:42:18 |