Internet DRAFT - draft-matsuhira-sa46t-pt-spec
draft-matsuhira-sa46t-pt-spec
Network Working Group N. Matsuhira
Internet-Draft Fujitsu Limited
Intended status: Standards Track July 23, 2015
Expires: January 24, 2016
SA46T Prefix Translator (SA46T-PT)
draft-matsuhira-sa46t-pt-spec-05
Abstract
This document specifies SA46T Prefix Translator (SA46T-PT)
specification. SA46T-PT expand IPv4 network plane by connecting
SA46T domain and SA46T-PR domain. SA46T-PT translate prefix part of
SA46T address and SA46T-PR address both are IPv6 address. SA46T-PT
does not translate IPv4 packet which is encapsulated, so transparency
of IPv4 packet is not broken.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
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 January 24, 2016.
Copyright Notice
Copyright (c) 2015 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
Matsuhira Expires January 24, 2016 [Page 1]
Internet-Draft SA46T-PT July 2015
(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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Basic Network Configuration . . . . . . . . . . . . . . . . . 3
3. Basic function of SA46T-PT . . . . . . . . . . . . . . . . . . 4
3.1. Translation processing . . . . . . . . . . . . . . . . . . 5
3.2. Address format of SA46T and SA46T-PR . . . . . . . . . . . 5
3.3. Resolving translate prefix . . . . . . . . . . . . . . . . 6
3.4. Destination address resolution . . . . . . . . . . . . . . 6
3.5. Source address resolution . . . . . . . . . . . . . . . . 7
4. Sample Configuration . . . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10
Matsuhira Expires January 24, 2016 [Page 2]
Internet-Draft SA46T-PT July 2015
1. Introduction
This document provide SA46T Prefix Translator (SA46T-PT)
specification.
The basic strategy for IPv6 deployment is dual stack. However,
because of exhaustion of IPv4 address, there will be no IPv4
addresses for configuring dual stack in near future. That means
there will be IPv6 only networks automatically.
However, there are many IPv4 only networks still exist and those
seems continuous use in near future. That means methods continuous
use of IPv4 network over IPv6 only network will be required.
SA46T [I-D.draft-matsuhira-sa46t-spec] provide such methods. In
addition, SA46T-PR [I-D.draft-matsuhira-sa46t-pr-spec] also provide
such methots. SA46T is backbone network based approach, on the other
hand, SA46T-PR is stub network based approach.
SA46T-PT expand IPv4 network plane by connecting SA46T domain and
SA46T-PR domain. SA46T-PT translate prefix part of SA46T address and
SA46T-PR address both are IPv6 address. SA46T-PT does not translate
IPv4 packet which is encapsulated, so transparency of IPv4 packet is
not broken.
2. Basic Network Configuration
Figure 1 shows network configuration with SA46T-PT. At large view,
the network consists three parts, SA46T domain, SA46T-PR domain, and
SA46T-PT. SA46T-PT connect SA46T domain and SA46T-PR domain.
Matsuhira Expires January 24, 2016 [Page 3]
Internet-Draft SA46T-PT July 2015
<------ SA46T Domain ------------> <--------- SA46T-PR Domain ---->
/-------------------------------/ /-----------------------------\
| | | |
| Backbone Network +----------+ Backbone Network |
| | SA46T-PT | |
| +----------+ |
| +----------+ +----------+ | | |
\---| SA46T |--| SA46T |--/ /-----------------------------/
+----------+ +----------+ | |
| | | |
| | | |
| | +----------+ +----------+
/--------------\/--------------/ /-| SA46T-PR |-\/-| SA46T-PR |-\
| || | | +----------+ || +----------+ |
| || | | || |
| Stub Network || Stub Network | | Stub Network || Stub Network |
| || | | (IPv4 only) || (Dual Stack) |
| || | | || |
\--------------//--------------/ \--------------/\--------------/
Figure 1
SA46T domain consists three parts, backbone network, stub network and
SA46T. Backbone network can be operated with IPv6 only. Stub network
has three cases, IPv4 only, Dual Stack (both IPv4 and IPv6), and IPv6
only.SA46T connects backbone network and stub network in case IPv4
still works in that stub network. If stub network is IPv6 only,
SA46T is not needed. SA46T is a backbone network based approach,
that mean SA46T advertise special route for SA46T.
And also, SA46T-PR domain consists three parts, backbone network,
stub network and SA46T. Backbone network can be operated with IPv6
only. Stub network has three cases, IPv4 only, Dual Stack (both IPv4
and IPv6), and IPv6 only.SA46T connects backbone network and stub
network in case IPv4 still works in that stub network. If stub
network is IPv6 only, SA46T-PR is not needed. SA46T-PR is a stub
network based approach.
3. Basic function of SA46T-PT
This section describe basic function of SA46T-PT.
Matsuhira Expires January 24, 2016 [Page 4]
Internet-Draft SA46T-PT July 2015
3.1. Translation processing
SA46T-PT translate between SA46T packet and SA46T-PT packet. SA46T
packet and SA46T-PT packet are almost the same, however IPv6 address
are different.
Fig shows packet format of SA46T domain and SA46T-PT domain.
+--------+--------+------------+ +--------+--------+------------+
|IPv6 Hdr|IPv4 Hdr| Data | --> |IPv6 Hdr|IPv4 Hdr| Data |
+--------+--------+------------+ +--------+--------+------------+
+--------+--------+------------+ +--------+--------+------------+
|IPv6 Hdr|IPv4 Hdr| Data | <-- |IPv6 Hdr|IPv4 Hdr| Data |
+--------+--------+------------+ +--------+--------+------------+
/-------------------\ +----------+ /---------------------------\
| SA46T Domain |--| SA46T-PT |--| SA46T-PR Domain |
| | +----------+ | |
\-------------------/ \---------------------------/
Figure 2
3.2. Address format of SA46T and SA46T-PR
figure Figure 3 shows SA46T address format and Figure 4 shows
SA46T-PR address format. These format almost the same except SA46T
address prefix in SA46T address and SA46T-PR address prefix in
SA46T-PR address.
| 96 - m bits | m bits | 32 bits |
+--------------------------+------------------------+--------------+
| SA46T address prefix | IPv4 network plane ID | IPv4 address |
+--------------------------+------------------------+--------------+
Figure 3
| 96 - m bits | m bits | 32 bits |
+--------------------------+------------------------+--------------+
| SA46T-PR address prefix | IPv4 network plane ID | IPv4 address |
+--------------------------+------------------------+--------------+
Figure 4
Matsuhira Expires January 24, 2016 [Page 5]
Internet-Draft SA46T-PT July 2015
3.3. Resolving translate prefix
SA46T-PT translate from SA46T prefix to SA46T-PR prefix, or from
SA46T-PR prefix to SA46T prefix using SA46T Prefix Translation
(SA46T-PT) table. fig Figure 5shows address resolution manner and fig
Figure 6shows SA46T-PT table.
| 96 - m bits | m bits | 32 bits |
+--------------------------+------------------------+--------------+
| SA46T / SA46T-PR prefix | IPv4 network plane ID | IPv4 address |
+--------------------------+------------------------+--------------+
\--------------------------/\--------------------------------------/
^ |
| |
| v
+------------------------------------------------------------------+
| |
| SA46T Prefix Translation Table (SA46T-PT Table) |
| |
+------------------------------------------------------------------+
Figure 5
SA46T-AT table is similar with SA46T-PR table, however SA46T-AT table
may contain SA46T prefix.
+---------------------+------------+-------++-----------------------+
|IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix|
+---------------------+------------+-------++-----------------------+
|IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix|
+---------------------+------------+-------++-----------------------+
|IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix|
+---------------------+------------+-------++-----------------------+
|IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix|
+---------------------+------------+-------++-----------------------+
: : :
+---------------------+------------+-------++-----------------------+
|IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix|
+---------------------+------------+-------++-----------------------+
Figure 6
3.4. Destination address resolution
For address resolution for destination address, SA46T-PT use SA46T-PT
table.
Matsuhira Expires January 24, 2016 [Page 6]
Internet-Draft SA46T-PT July 2015
3.5. Source address resolution
For address resolution for source address, SA46T-PT use interface
information, not SA46T-PT table. From SA46T domain to SA46T-PR
domain, SA46T-PT use IPv6 address prefix of the interface which
belong SA46T-PR domain. From
4. Sample Configuration
Figure Figure 7shows sample confiuration of SA46T-PT. In this
example, there are four IPv4 stub network with the same IPv4 network
plane, and two of four are in SA46T domain and other two of four are
in SA46T-PR domain.
In this example, SA46T prefix is 2001:0db8:0:46::/64.
Matsuhira Expires January 24, 2016 [Page 7]
Internet-Draft SA46T-PT July 2015
/------------\
| +--------+ /----------------------\
| Backbone | | |Stub Network#1 |
| Network |SA46T |--|10.1.1.0/24(plane 1) |
|(IPv6 only)| | |2001:0db8:1:1::/64 |
| +--------+ \----------------------/
| <--[2001:0db8:1:1::/64]
| <--[2001:0db8:0:46:0:1:10.1.1.0/120]
| |
| +--------+ /----------------------\
| | | |Stub Network#2 |
| |SA46T |--|10.1.2.0/24(plane 1) |
| | | |2001:0db8:1:2::/64 |
| +--------+ \----------------------/
| <--[2001:0db8:1:2::/64]
| <--[2001:0db8:0:46:0:1:10.1.2.0/120]
| |
| <--[2001:0db8:0:46:0:1:10.1.4.0/120]
| <--[2001:0db8:0:46:0:1:10.1.5.0/120]
| +------------+
| | SA46T-PT |
| +------------+
\------------/ |
| |Stub Network #0
/------------\ | 2001:0db8:2:0::/64
| |----+
| | /--------------------------------------/
| | | Stub Network #3 |
| | | 2001:0db8:2:1::/64 |
| | | +--------+ /----------------------\ |
| |--| |SA46T-PR|--|10.1.3.0/24(plane 1) | |
| | | +--------+ /----------------------/ |
| <--[2001:0db8:2:1::/64] |
| | /--------------------------------------/
| |
| | /--------------------------------------/
| | | Stub Network #4 |
| | | 2001:0db8:2:2::/64 |
| Backbone | | +--------+ /----------------------\ |
| Network |--| |SA46T-PR|--|10.1.4.0/24(plane 1) | |
| | | +--------+ \----------------------/ |
| <--[2001:0db8:2:2::/64] |
| | /--------------------------------------/
\------------/
Figure 7
Matsuhira Expires January 24, 2016 [Page 8]
Internet-Draft SA46T-PT July 2015
Figure Figure 8 shows SA46T-PT table for this example. This example
is default free case.
+---------------------+------------+-------++-----------------------+
|IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix|
+---------------------+------------+-------++-----------------------+
| 1 | 10.1.1.0 | /120 || 2001:0db8:0:46 |
| 1 | 10.1.2.0 | /120 || 2001:0db8:0:46 |
| 1 | 10.1.3.0 | /120 || 2001:0db8:2:1 |
| 1 | 10.1.4.0 | /120 || 2001:0db8:2:2 |
+---------------------+------------+-------++-----------------------+
Figure 8
Fig Figure 9shows another SA46T-PT table for this example. This
example use default for SA46T. If there are many stub network in
SA46T domain, by using default as SA46T prefix, reduction of SA46T-PT
table size can be possible.
+---------------------+------------+-------++-----------------------+
|IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix|
+---------------------+------------+-------++-----------------------+
| 1 | 10.1.3.0 | /120 || 2001:0db8:2:1 |
| 1 | 10.1.4.0 | /120 || 2001:0db8:2:2 |
| 1 | 0.0.0.0 | /0 || 2001:0db8:0:46 |
+---------------------+------------+-------++-----------------------+
Figure 9
5. IANA Considerations
This document makes no request of IANA.
Note to RFC Editor: this section may be removed on publication as an
RFC.
6. Security Considerations
Security Considerations does not discussed in this memo.
7. Acknowledgements
8. References
Matsuhira Expires January 24, 2016 [Page 9]
Internet-Draft SA46T-PT July 2015
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
8.2. Informative References
[I-D.draft-matsuhira-sa46t-pr-spec]
Matsuhira, N., "SA46T Prefix Resolution (SA46T-PR)",
January 2014.
[I-D.draft-matsuhira-sa46t-spec]
Matsuhira, N., "Stateless Automatic IPv4 over IPv6
Encapsulation / Decapsulation Technology: Specification",
January 2014.
Author's Address
Naoki Matsuhira
Fujitsu Limited
1-1, Kamikodanaka 4-chome, Nakahara-ku
Kawasaki, 211-8588
Japan
Phone: +81-44-754-3466
Fax:
Email: matsuhira@jp.fujitsu.com
Matsuhira Expires January 24, 2016 [Page 10]