draft-ietf-softwire-dslite-mib-00.txt   draft-ietf-softwire-dslite-mib-01.txt 
Softwire Y. Fu Softwire Y. Fu
Internet Draft S. Jiang Internet Draft S. Jiang
Intended status: Standards Track Huawei Technologies Co., Ltd Intended status: Standards Track Huawei Technologies Co., Ltd
Expires: January 14, 2013 J. Dong Expires: July 13, 2013 J. Dong
Y. Chen Y. Chen
Tsinghua University Tsinghua University
July 11, 2012 January 10, 2013
DS-Lite Management Information Base (MIB) DS-Lite Management Information Base (MIB)
draft-ietf-softwire-dslite-mib-00 draft-ietf-softwire-dslite-mib-01
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute working Task Force (IETF). Note that other groups may also distribute working
documents as Internet-Drafts. The list of current Internet-Drafts is documents as Internet-Drafts. The list of current Internet-Drafts is
at http://datatracker.ietf.org/drafts/current/. at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 14, 2013. This Internet-Draft will expire on July 13, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 26 skipping to change at page 2, line 26
4. Difference from the IP tunnel MIB and NAT MIB ................ 3 4. Difference from the IP tunnel MIB and NAT MIB ................ 3
5. Relationship to the IF-MIB ................................... 5 5. Relationship to the IF-MIB ................................... 5
6. Structure of the MIB Module .................................. 5 6. Structure of the MIB Module .................................. 5
6.1. The dsliteTunnel Subtree ................................ 5 6.1. The dsliteTunnel Subtree ................................ 5
6.2. The dsliteNAT Subtree ................................... 5 6.2. The dsliteNAT Subtree ................................... 5
6.3. The dsliteInfo Subtree .................................. 6 6.3. The dsliteInfo Subtree .................................. 6
6.4. The dsliteTrap Subtree .................................. 6 6.4. The dsliteTrap Subtree .................................. 6
6.5. The dsliteConformance Subtree ........................... 6 6.5. The dsliteConformance Subtree ........................... 6
7. MIB modules required for IMPORTS ............................. 6 7. MIB modules required for IMPORTS ............................. 6
8. Definitions .................................................. 6 8. Definitions .................................................. 6
9. Extending this MIB for Gateway Initiated Dual-Stack Lite..... 27 9. Extending this MIB for Gateway Initiated Dual-Stack Lite .....27
10. IANA Considerations ........................................ 27 10. IANA Considerations......................................... 27
11. Security Consideration ..................................... 28 11. Security Considerations .................................... 28
12. References ................................................. 28 12. References ................................................. 28
12.1. Normative References .................................. 28 12.1. Normative References .................................. 28
12.2. Informative References ................................ 29 12.2. Informative References ................................ 29
Author's Addresses ............................................. 30 Author's Addresses ............................................. 30
1. Introduction 1. Introduction
Dual-Stack Lite [RFC 6333] is a solution to offer both IPv4 and IPv6 Dual-Stack Lite [RFC 6333] is a solution to offer both IPv4 and IPv6
connectivity to customers crossing IPv6 only infrastructure. One of connectivity to customers crossing IPv6 only infrastructure. One of
its key components is an IPv4-over-IPv6 tunnel, which is used to its key components is an IPv4-over-IPv6 tunnel, which is used to
provide IPv4 connection across service provider IPv6 network. Another provide IPv4 connection across service provider's IPv6 network.
key component is a carrier-grade IPv4-IPv4 NAT to share service Another key component is a carrier-grade IPv4-IPv4 NAT to share
provider IPv4 addresses among customers. service provider IPv4 addresses among customers.
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for using with network management protocols in the Internet
community. This MIB module may be used for configuration and community. This MIB module may be used for configuration and
monitoring the devices in the Dual-Stack Lite scenario. monitoring the devices in the Dual-Stack Lite scenario.
This MIB also can be extended to the application for Gateway This MIB also can be extended to the application for Gateway
Initiated Dual-Stack Lite. Initiated Dual-Stack Lite [RFC 6674].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
[RFC3410]. [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the MIB. MIB objects are generally accessed through the Simple the MIB. MIB objects are generally accessed through the Simple
Network Management Protocol (SNMP). Network Management Protocol (SNMP).
skipping to change at page 4, line 26 skipping to change at page 4, line 26
requirements for DS-Lite, as below. requirements for DS-Lite, as below.
In DS-Lite scenario, the tunnel type is IP in IP, more In DS-Lite scenario, the tunnel type is IP in IP, more
precisely, is IPv4 in IPv6. Therefore, it is unnecessary to precisely, is IPv4 in IPv6. Therefore, it is unnecessary to
describe tunnel type in DS-Lite MIB. describe tunnel type in DS-Lite MIB.
In DS-Lite scenario, the translation type is IPv4 private In DS-Lite scenario, the translation type is IPv4 private
address to IPv4 public address. Therefore, it is unnecessary to address to IPv4 public address. Therefore, it is unnecessary to
describe the type of address in the corresponding describe the type of address in the corresponding
tunnelIfLocalInetAddress and tunnelIfRemoteInetAddress objects tunnelIfLocalInetAddress and tunnelIfRemoteInetAddress objects
in DS-Lite MIB. which are defined in tunnel MIB in DS-Lite MIB.
In DS-Lite scenario, the AFTR is not only the tunnel end In DS-Lite scenario, the AFTR is not only the tunnel end
concentrator, but also a 4-4 translator. Within the AFTR, concentrator, but also a 4-4 translator. Within the AFTR,
tunnel information and translation information MUST be mapped tunnel information and translation information MUST be mapped
each other. Two independent MIB is not able to reflect this each other. Two independent MIB is not able to reflect this
mapping relationship. Therefore, a combined MIB is necessary. mapping relationship. Therefore, a combined MIB is necessary.
If the Gateway Initiated Dual-Stack Lite scenario[I-D.ietf- If the Gateway Initiated Dual-Stack Lite scenario[RFC 6674] is
softwire-gateway-init-ds-lite] is required, the MIB defined in required, the MIB defined in this document could be easily
this document could be easily extended for GI-DS-Lite. CID extended for GI-DS-Lite. CID (Context Identifier) can be
(Context Identifier) can be extended to the tunnel MIB to extended to the tunnel MIB to identifier the access devices
identifier the access devices which have the same IPv4 address. which have the same IPv4 address. And both CID and SWID
And both CID and SWID (Softwire Identifier) can be extended to (Softwire Identifier) can be extended to the NAT MIB for
the NAT MIB for performing the NAT binding look up. performing the NAT binding look up.
The implementation of the IP Tunnel MIB is required for DS-Lite. The The implementation of the IP Tunnel MIB is required for DS-Lite. The
tunnelIfEncapsMethod in the tunnelIfEntry should be set to tunnelIfEncapsMethod in the tunnelIfEntry should be set to
dsLite("xx"), and corresponding entry in the DS-Lite module will dsLite("xx"), and corresponding entry in the DS-Lite module will
exist for every tunnelIfEntry with this tunnelIfEncapsMethod. The exist for every tunnelIfEntry with this tunnelIfEncapsMethod. The
tunnelIfRemoteInetAddress must be set to ::. tunnelIfRemoteInetAddress must be set to "::".
5. Relationship to the IF-MIB 5. Relationship to the IF-MIB
The Interfaces MIB [RFC2863] defines generic managed objects for The Interfaces MIB [RFC2863] defines generic managed objects for
managing interfaces. Each logical interface (physical or virtual)has managing interfaces. Each logical interface (physical or virtual)has
an ifEntry. Tunnels are handled by creating a logical interface an ifEntry. Tunnels are handled by creating a logical interface
(ifEntry) for each tunnel. DS-Lite tunnel also acts as a virtual (ifEntry) for each tunnel. DS-Lite tunnel also acts as a virtual
interface, which has corresponding entries in IP Tunnel MIB and interface, which has corresponding entries in IP Tunnel MIB and
Interface MIB. Those corresponding entries are indexed by ifIndex. Interface MIB. Those corresponding entries are indexed by ifIndex.
The ifOperStatus in ifTable would be used to represent whether the The ifOperStatus in ifTable would be used to represent whether the
DS-Lite tunnel function has been originated. The ifInUcastPkts DS-Lite tunnel function has been originated. The ifInUcastPkts
defined in ifTabel will represent the number of IPv6 packets which defined in ifTabel will represent the number of IPv4 packets which
have been encapsulated with IPv4 packets in it. The ifOutUcastPkts have been encapsulated into IPv6 packets sent to B4. The
defined in ifTabel contains the number of IPv6 packets which can be ifOutUcastPkts defined in ifTabel contains the number of IPv6 packets
decapsulated to IPv4 in the virtual interface. Also, the IF-MIB which can be decapsulated to IPv4 in the virtual interface. Also, the
defines ifMtu for the MTU of this tunnel interface, so DS-Lite MIB IF-MIB defines ifMtu for the MTU of this tunnel interface, so DS-Lite
does not need to define the MTU for tunnel. MIB does not need to define the MTU for tunnel.
6. Structure of the MIB Module 6. Structure of the MIB Module
The DS-Lite MIB provides a way to configure and manage the devices The DS-Lite MIB provides a way to configure and manage the devices
(AFTRs)in DS-Lite scenario through SNMP. (AFTRs)in DS-Lite scenario through SNMP.
DS-Lite MIB is configurable on a per-interface basis. It depends on DS-Lite MIB is configurable on a per-interface basis. It depends on
several parts of the IF-MIB [RFC2863], tunnel MIB [RFC4087], and NAT several parts of the IF-MIB [RFC2863], tunnel MIB [RFC4087], and NAT
MIB [RFC4008]. MIB [RFC4008].
skipping to change at page 5, line 46 skipping to change at page 5, line 46
Tunnel MIB are not access, a few new objects are defined in DS-Lite Tunnel MIB are not access, a few new objects are defined in DS-Lite
MIB. MIB.
6.2. The dsliteNAT Subtree 6.2. The dsliteNAT Subtree
The dsliteNAT Subtree describes managed objects used for The dsliteNAT Subtree describes managed objects used for
configuration as well as monitoring of AFTR which is capable of NAT configuration as well as monitoring of AFTR which is capable of NAT
function. Because the NAT MIB supports the NAT management function in function. Because the NAT MIB supports the NAT management function in
DS-Lite, we may reuse it in DS-Lite MIB. The dsliteNAT Subtree also DS-Lite, we may reuse it in DS-Lite MIB. The dsliteNAT Subtree also
provides the information of mapping relationship between the tunnel provides the information of mapping relationship between the tunnel
MIB and NAT MIB by extending B4 address to the bind table in NAT MIB and NAT MIB by extending the IPv6 address of B4 to the bind table
MIB. in NAT MIB.
6.3. The dsliteInfo Subtree 6.3. The dsliteInfo Subtree
The dsliteInfo Subtree provides the statistical information for DS- The dsliteInfo Subtree provides the statistical information for DS-
lite. lite.
6.4. The dsliteTrap Subtree 6.4. The dsliteTrap Subtree
The dsliteTrap Subtree provides trap information in DS-lite instance. The dsliteTrap Subtree provides trap information in DS-lite instance.
skipping to change at page 7, line 8 skipping to change at page 7, line 8
natAddrMapLocalPortFrom, natAddrMapLocalPortTo, natAddrMapLocalPortFrom, natAddrMapLocalPortTo,
natAddrMapGlobalAddrFrom, natAddrMapGlobalAddrTo, natAddrMapGlobalAddrFrom, natAddrMapGlobalAddrTo,
natAddrMapGlobalPortFrom, natAddrMapGlobalPortTo natAddrMapGlobalPortFrom, natAddrMapGlobalPortTo
natAddrPortBindGlobalAddr, natAddrPortBindGlobalPort, natAddrPortBindGlobalAddr, natAddrPortBindGlobalPort,
NatBindId, natAddrPortBindSessions, NatBindId, natAddrPortBindSessions,
natAddrPortBindMaxIdleTime, natAddrPortBindCurrentIdleTime, natAddrPortBindMaxIdleTime, natAddrPortBindCurrentIdleTime,
natAddrPortBindInTranslates, natAddrPortBindOutTranslates natAddrPortBindInTranslates, natAddrPortBindOutTranslates
FROM natMIB FROM natMIB
dsliteMIB MODULE-IDENTITY dsliteMIB MODULE-IDENTITY
LAST-UPDATED "201207110000Z" -- July 11, 2012 LAST-UPDATED "201307100000Z" -- January 10, 2013
ORGANIZATION "IETF Softwire Working Group" ORGANIZATION "IETF Softwire Working Group"
CONTACT-INFO CONTACT-INFO
"Yu Fu "Yu Fu
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
Huawei Building, 156 Beiqing Rd., Hai-Dian District Huawei Building, 156 Beiqing Rd., Hai-Dian District
Beijing, P.R. China 100095 Beijing, P.R. China 100095
EMail: eleven.fuyu@huawei.com EMail: eleven.fuyu@huawei.com
Sheng Jiang Sheng Jiang
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
skipping to change at page 27, line 28 skipping to change at page 27, line 28
Similar to DS-lite, GI-DS-lite enables the service provider to Similar to DS-lite, GI-DS-lite enables the service provider to
share public IPv4 addresses among different customers by combining share public IPv4 addresses among different customers by combining
tunneling and NAT. GI-DS-lite extends existing access tunnels tunneling and NAT. GI-DS-lite extends existing access tunnels
beyond the access gateway to an IPv4-IPv4 NAT using softwires with beyond the access gateway to an IPv4-IPv4 NAT using softwires with
an embedded context identifier that uniquely identifies the end host an embedded context identifier that uniquely identifies the end host
the tunneled packets belong to. The MIB defined in this document can the tunneled packets belong to. The MIB defined in this document can
easily extended to use for GI-DS-Lite scenario. New object as CID easily extended to use for GI-DS-Lite scenario. New object as CID
SHOULD be extended to the dsliteTunnelTable. And a new object as SHOULD be extended to the dsliteTunnelTable. And a new object as
dsliteTunnelID can be defined in DS-Lite MIB as SWID in GI-DS-Lite. dsliteTunnelID can be defined in DS-Lite MIB as SWID in GI-DS-Lite.
Both CID and SWID SHOULD be extended to the dsliteNATBindTable. It Both CID and SWID SHOULD be extended to the dsliteNATBindTable.The
will use the combination of CID and SWID as the unique identifier for combination of CID and SWID will be used as the unique identifier for
the end host and store it in the NAT binding entry. the end host and store it in the NAT binding entry.
10. IANA Considerations 10. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry, and OBJECT IDENTIFIER values recorded in the SMI Numbers registry, and
the following IANA-assigned tunnelType values recorded in the the following IANA-assigned tunnelType values recorded in the
IANAtunnelType-MIB registry: IANAtunnelType-MIB registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
skipping to change at page 29, line 37 skipping to change at page 29, line 37
[RFC4008] Rohit, R., Srisuresh, P., Raghunarayan,R., Pai, N., and [RFC4008] Rohit, R., Srisuresh, P., Raghunarayan,R., Pai, N., and
Wang, C., "Definitions of Managed Objects for Network Wang, C., "Definitions of Managed Objects for Network
Address Translators (NAT)", RFC 4008, March 2005. Address Translators (NAT)", RFC 4008, March 2005.
[RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005. [RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005.
[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4 Stack Lite Broadband Deployments Following IPv4
Exhaustion", RFC6333, August 2011. Exhaustion", RFC6333, August 2011.
[RFC6674] Brockners, F., Gundavelli, S., Speicher, S., Ward, D.
"Gateway-Initiated Dual-Stack Lite Deployment", RFC 6674,
July 2012.
12.2. Informative References 12.2. Informative References
[I-D.ietf-softwire-gateway-init-ds-lite] [I-D.ietf-softwire-gateway-init-ds-lite]
Brockners, F., Gundavelli, S., Speicher, S., and D. Ward, Brockners, F., Gundavelli, S., Speicher, S., and D. Ward,
"Gateway Initiated Dual-Stack Lite Deployment", "Gateway Initiated Dual-Stack Lite Deployment",
draft-ietf-softwire-gateway-init-ds-lite-08 (work in draft-ietf-softwire-gateway-init-ds-lite-08 (work in
progress), July 2011. progress), July 2011.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
 End of changes. 17 change blocks. 
33 lines changed or deleted 37 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/