[Docs] [txt|pdf|xml|html] [Tracker] [Email] [Nits]

Versions: 00

Network Working Group                                          J. Dionne
Internet-Draft                                             Viagenie Inc.
Updates: 4008 (if approved)                                  M. Blanchet
Intended status: Standards Track                                Viagenie
Expires: September 5, 2011                                 March 4, 2011


                NAT64 Management Information Base (MIB)
                   draft-jpdionne-behave-nat64-mib-00

Abstract

   This memo describes the NAT64 Management Information Base.  It reuses
   the NAT-MIB and add specific NAT64 variables.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 5, 2011.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.





Dionne & Blanchet       Expires September 5, 2011               [Page 1]


Internet-Draft   NAT64 Management Information Base (MIB)      March 2011


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Modifications to NAT-MIB . . . . . . . . . . . . . . . . . . .  4
     2.1.  Pref64 . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Configuring NAT64  . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  NatTranslationEntity . . . . . . . . . . . . . . . . . . .  5
     3.2.  Local and Private Terminology  . . . . . . . . . . . . . .  5
   4.  RFC4008 Proposed Changes . . . . . . . . . . . . . . . . . . .  6
     4.1.  Changes to Section 3: Terminology  . . . . . . . . . . . .  6
     4.2.  Changes to Section 4: Overview . . . . . . . . . . . . . .  6
       4.2.1.  Changes to Section 4.2: natAddrMapTable  . . . . . . .  6
       4.2.2.  Changes to Section 4.5: natSessionTable  . . . . . . .  6
       4.2.3.  Changes to Section 4.7: Notifications  . . . . . . . .  6
       4.2.4.  Changes to Section 4.9: Configuration via the MIB  . .  6
     4.3.  Changes to Section 5: Definitions  . . . . . . . . . . . .  7
       4.3.1.  IMPORT . . . . . . . . . . . . . . . . . . . . . . . .  7
       4.3.2.  Update to NatAddrMapEntry  . . . . . . . . . . . . . .  7
     4.4.  Complete updated NAT-MIB . . . . . . . . . . . . . . . . .  8
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     6.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     6.2.  Informative References . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11



























Dionne & Blanchet       Expires September 5, 2011               [Page 2]


Internet-Draft   NAT64 Management Information Base (MIB)      March 2011


1.  Introduction

   To enable IPv6-only nodes to access to IPv4-only nodes, a NAT64
   [I-D.ietf-behave-v6v4-xlate-stateful] is used.  This NAT64 requires a
   Management Information Base (MIB) for the purpose of managing the
   device.

   The NAT-MIB [RFC4008] is designed to carry translation from any
   address family to any address family, therefore supports IPv6 to IPv4
   translation such as NAT64.

   Some specifics of NAT64 are not present in the NAT-MIB.  This
   document describes the changes to fully support NAT64.






































Dionne & Blanchet       Expires September 5, 2011               [Page 3]


Internet-Draft   NAT64 Management Information Base (MIB)      March 2011


2.  Modifications to NAT-MIB

   A revision of [RFC4008] is proposed.

2.1.  Pref64

   The NAT64 uses a special prefix, named Pref64 [RFC6052], to carry
   IPv4 destination addresses into an IPv6 address.  This prefix is
   required for the joint operation of NAT64 and
   DNS64[I-D.ietf-behave-dns64].  The operator can choose to use the
   Well-Known prefix (64:ff9b::/96) or a Network-Specific Prefix.

   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)





































Dionne & Blanchet       Expires September 5, 2011               [Page 4]


Internet-Draft   NAT64 Management Information Base (MIB)      March 2011


3.  Configuring NAT64

   This section presents considerations regarding NAT64 that doesn't
   require modification of the NAT-MIB.

3.1.  NatTranslationEntity

   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."

   For NAT64, both the source and destination is translated.  Hence, two
   bits must be set:

   "inboundSrcEndPoint" and "inboundDstEndPoint" if the operator chooses
   to configure the NAT64 address map entry on the IPv4 network
   interface.

   or

   "outboundSrcEndPoint" and "outboundDstEndPoint" if the operator
   chooses to configure the NAT64 address map entry on the IPv6 Internet
   interface.

3.2.  Local and Private Terminology

   Throughout [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.



















Dionne & Blanchet       Expires September 5, 2011               [Page 5]


Internet-Draft   NAT64 Management Information Base (MIB)      March 2011


4.  RFC4008 Proposed Changes

4.1.  Changes to Section 3: Terminology

      NAT Session:

         "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.

         The "session" terminology also differs with
         [I-D.ietf-behave-v6v4-framework] definition: An "end-to-end
         session" in rfc4008 is a "session" in xlate.

4.2.  Changes to Section 4: Overview

   "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.

4.2.1.  Changes to Section 4.2: natAddrMapTable

   Add a paragraph for pref64 variables.  Refer to Section 4.3.2

   Rephrase the last sentence to explain how to use NatTranslationEntity
   to describe NAT64.

4.2.2.  Changes to Section 4.5: natSessionTable

   "Session" terminology differs with
   draft-ietf-behave-v6v4-xlate-stateful's definition.  A "end-to-end
   session" in rfc4008 is a "session" in xlate.

4.2.3.  Changes to Section 4.7: Notifications

   "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.

4.2.4.  Changes to Section 4.9: Configuration via the MIB

   TBD: Add a point about how to configure the pref64 if its NAT64.






Dionne & Blanchet       Expires September 5, 2011               [Page 6]


Internet-Draft   NAT64 Management Information Base (MIB)      March 2011


4.3.  Changes to Section 5: Definitions

4.3.1.  IMPORT


   Ipv6AddressPrefix,
           FROM IPV6-TC;

4.3.2.  Update to NatAddrMapEntry


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),
}




Dionne & Blanchet       Expires September 5, 2011               [Page 7]


Internet-Draft   NAT64 Management Information Base (MIB)      March 2011


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 }


4.4.  Complete updated NAT-MIB

   Update is done in conformance to section 10 of [RFC2578].


   TBD






















Dionne & Blanchet       Expires September 5, 2011               [Page 8]


Internet-Draft   NAT64 Management Information Base (MIB)      March 2011


5.  Security Considerations

   No additionnal security issues.  See [RFC4008] section 7.
















































Dionne & Blanchet       Expires September 5, 2011               [Page 9]


Internet-Draft   NAT64 Management Information Base (MIB)      March 2011


6.  References

6.1.  Normative References

   [RFC2578]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Structure of Management Information
              Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

   [RFC4008]  Rohit, R., Srisuresh, P., Raghunarayan, R., Pai, N., and
              C. Wang, "Definitions of Managed Objects for Network
              Address Translators (NAT)", RFC 4008, March 2005.

   [RFC6052]  Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X.
              Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052,
              October 2010.

6.2.  Informative References

   [I-D.ietf-behave-dns64]
              Bagnulo, M., Sullivan, A., Matthews, P., and I. Beijnum,
              "DNS64: DNS extensions for Network Address Translation
              from IPv6 Clients to IPv4 Servers",
              draft-ietf-behave-dns64-11 (work in progress),
              October 2010.

   [I-D.ietf-behave-v6v4-framework]
              Baker, F., Li, X., Bao, C., and K. Yin, "Framework for
              IPv4/IPv6 Translation",
              draft-ietf-behave-v6v4-framework-10 (work in progress),
              August 2010.

   [I-D.ietf-behave-v6v4-xlate-stateful]
              Bagnulo, M., Matthews, P., and I. Beijnum, "Stateful
              NAT64: Network Address and Protocol Translation from IPv6
              Clients to IPv4 Servers",
              draft-ietf-behave-v6v4-xlate-stateful-12 (work in
              progress), July 2010.














Dionne & Blanchet       Expires September 5, 2011              [Page 10]


Internet-Draft   NAT64 Management Information Base (MIB)      March 2011


Authors' Addresses

   Jean-Philippe Dionne
   Viagenie Inc.
   2875 boul. Laurier, suite D2-630
   Quebec
   Canada

   Phone: +1-418-656-9254
   Email: jean-philippe.dionne@viagenie.ca


   Marc Blanchet
   Viagenie
   2875 boul. Laurier, suite D2-630
   Quebec, QC  G1V 2M2
   Canada

   Email: Marc.Blanchet@viagenie.ca
   URI:   http://viagenie.ca































Dionne & Blanchet       Expires September 5, 2011              [Page 11]


Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/