Multiple IPv4 - IPv6 address mapping encapsulation - prefix translator (M46E-PT)
draft-matsuhira-m46e-pt-03
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-08-13
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group N. Matsuhira
Internet-Draft Fujitsu Limited
Intended status: Informational August 14, 2017
Expires: February 15, 2018
Multiple IPv4 - IPv6 address mapping encapsulation - prefix translator
(M46E-PT)
draft-matsuhira-m46e-pt-03
Abstract
This document specifies Multiple IPv4 - IPv6 mapping encapsulation -
Prefix Translator (M46E-PT) specification. M46E-PT expand IPv4
network plane by connecting M46E-FP domain and M46E-PR domain.
M46E-PT translate prefix part of M46E-FP address and M46E-PR address
both are IPv6 address. M46E-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 February 15, 2018.
Copyright Notice
Copyright (c) 2017 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
Matsuhira Expires February 15, 2018 [Page 1]
Internet-Draft M46E-PT August 2017
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Basic Network Configuration . . . . . . . . . . . . . . . . . 3
3. Basic function of M46E-PT . . . . . . . . . . . . . . . . . . 4
3.1. Translation processing . . . . . . . . . . . . . . . . . . 5
3.2. M46A architecture . . . . . . . . . . . . . . . . . . . . 5
3.3. Resolving translate prefix . . . . . . . . . . . . . . . . 5
3.4. Destination address resolution . . . . . . . . . . . . . . 6
3.5. Source address resolution . . . . . . . . . . . . . . . . 6
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 February 15, 2018 [Page 2]
Internet-Draft M46E-PT August 2017
1. Introduction
This document provide M46E Prefix Translator (M46E-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.
M46E-FP [I-D.draft-matsuhira-m46e-fp] provide such methods. In
addition, M46E-PR [I-D.draft-matsuhira-m46e-pr] also provide such
Show full document text