draft-ietf-softwire-map-06.txt   draft-ietf-softwire-map-07.txt 
Network Working Group O. Troan, Ed. Network Working Group O. Troan, Ed.
Internet-Draft W. Dec Internet-Draft W. Dec
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: November 11, 2013 X. Li Expires: November 30, 2013 X. Li
C. Bao C. Bao
CERNET Center/Tsinghua University CERNET Center/Tsinghua University
S. Matsushima S. Matsushima
SoftBank Telecom SoftBank Telecom
T. Murakami T. Murakami
IP Infusion IP Infusion
T. Taylor, Ed. T. Taylor, Ed.
Huawei Technologies Huawei Technologies
May 10, 2013 May 29, 2013
Mapping of Address and Port with Encapsulation (MAP) Mapping of Address and Port with Encapsulation (MAP)
draft-ietf-softwire-map-06 draft-ietf-softwire-map-07
Abstract Abstract
This document describes a mechanism for transporting IPv4 packets This document describes a mechanism for transporting IPv4 packets
across an IPv6 network using IP encapsulation, and a generic across an IPv6 network using IP encapsulation, and a generic
mechanism for mapping between IPv6 addresses and IPv4 addresses and mechanism for mapping between IPv6 addresses and IPv4 addresses and
transport layer ports. transport layer ports.
Status of This Memo Status of This Memo
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is 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 November 11, 2013. This Internet-Draft will expire on November 30, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
skipping to change at page 2, line 30 skipping to change at page 2, line 30
4. Architecture . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Architecture . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Mapping Algorithm . . . . . . . . . . . . . . . . . . . . . . 7 5. Mapping Algorithm . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Port mapping algorithm . . . . . . . . . . . . . . . . . . 8 5.1. Port mapping algorithm . . . . . . . . . . . . . . . . . . 8
5.2. Basic mapping rule (BMR) . . . . . . . . . . . . . . . . . 9 5.2. Basic mapping rule (BMR) . . . . . . . . . . . . . . . . . 9
5.3. Forwarding mapping rule (FMR) . . . . . . . . . . . . . . 12 5.3. Forwarding mapping rule (FMR) . . . . . . . . . . . . . . 12
5.4. Destinations outside the MAP domain . . . . . . . . . . . 12 5.4. Destinations outside the MAP domain . . . . . . . . . . . 12
6. The IPv6 Interface Identifier . . . . . . . . . . . . . . . . 13 6. The IPv6 Interface Identifier . . . . . . . . . . . . . . . . 13
7. MAP Configuration . . . . . . . . . . . . . . . . . . . . . . 13 7. MAP Configuration . . . . . . . . . . . . . . . . . . . . . . 13
7.1. MAP CE . . . . . . . . . . . . . . . . . . . . . . . . . . 14 7.1. MAP CE . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.2. MAP BR . . . . . . . . . . . . . . . . . . . . . . . . . . 14 7.2. MAP BR . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.3. Backwards compatibility . . . . . . . . . . . . . . . . . 14 7.3. Backwards compatibility . . . . . . . . . . . . . . . . . 15
8. Forwarding Considerations . . . . . . . . . . . . . . . . . . 15 8. Forwarding Considerations . . . . . . . . . . . . . . . . . . 15
8.1. Receiving Rules . . . . . . . . . . . . . . . . . . . . . 15 8.1. Receiving Rules . . . . . . . . . . . . . . . . . . . . . 15
8.2. ICMP . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 8.2. ICMP . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.3. Fragmentation and Path MTU Discovery . . . . . . . . . . . 16 8.3. Fragmentation and Path MTU Discovery . . . . . . . . . . . 16
8.3.1. Fragmentation in the MAP domain . . . . . . . . . . . 16 8.3.1. Fragmentation in the MAP domain . . . . . . . . . . . 16
8.3.2. Receiving IPv4 Fragments on the MAP domain borders . . 17 8.3.2. Receiving IPv4 Fragments on the MAP domain borders . . 17
8.3.3. Sending IPv4 fragments to the outside . . . . . . . . 17 8.3.3. Sending IPv4 fragments to the outside . . . . . . . . 17
9. NAT44 Considerations . . . . . . . . . . . . . . . . . . . . . 18 9. NAT44 Considerations . . . . . . . . . . . . . . . . . . . . . 18
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
11. Security Considerations . . . . . . . . . . . . . . . . . . . 18 11. Security Considerations . . . . . . . . . . . . . . . . . . . 18
skipping to change at page 12, line 18 skipping to change at page 12, line 18
the IPv4 address and the IPv6 address. In addition the length of o the IPv4 address and the IPv6 address. In addition the length of o
MAY be zero (no EA bits embedded in the End-User IPv6 prefix), MAY be zero (no EA bits embedded in the End-User IPv6 prefix),
meaning that also the PSID is provisioned using e.g. the DHCP meaning that also the PSID is provisioned using e.g. the DHCP
option. option.
See Appendix A for an example of the Basic Mapping Rule. See Appendix A for an example of the Basic Mapping Rule.
5.3. Forwarding mapping rule (FMR) 5.3. Forwarding mapping rule (FMR)
The Forwarding Mapping Rule is optional, and used in mesh mode to The Forwarding Mapping Rule is optional, and used in mesh mode to
merit direct CE to CE connectivity. enable direct CE to CE connectivity.
On adding an FMR rule, an IPv4 route is installed in the Rules table On adding an FMR rule, an IPv4 route is installed in the Rules table
for the Rule IPv4 prefix. for the Rule IPv4 prefix.
On forwarding an IPv4 packet, a best matching prefix look up is done On forwarding an IPv4 packet, a best matching prefix look up is done
in the Rules table and the correct FMR is chosen. in the Rules table and the correct FMR is chosen.
| 32 bits | | 16 bits | | 32 bits | | 16 bits |
+--------------------------+ +-------------------+ +--------------------------+ +-------------------+
| IPv4 destination address | | IPv4 dest port | | IPv4 destination address | | IPv4 dest port |
skipping to change at page 14, line 15 skipping to change at page 14, line 20
In addition the MAP CE MUST be configured with the IPv6 address(es) In addition the MAP CE MUST be configured with the IPv6 address(es)
of the MAP BR (Section 5.4). of the MAP BR (Section 5.4).
7.1. MAP CE 7.1. MAP CE
The MAP elements are set to values that are the same across all CEs The MAP elements are set to values that are the same across all CEs
within a MAP domain. The values may be configured in a variety of within a MAP domain. The values may be configured in a variety of
manners, including provisioning methods such as the Broadband Forum's manners, including provisioning methods such as the Broadband Forum's
"TR-69" Residential Gateway management interface, an XML-based object "TR-69" Residential Gateway management interface, an XML-based object
retrieved after IPv6 connectivity is established, or manual retrieved after IPv6 connectivity is established, or manual
configuration by an administrator. This document describes how to configuration by an administrator. This document focuses on how to
configure the necessary parameters via a single IPv6 DHCP option. A configure the necessary parameters via IPv6 DHCP. A CE that allows
CE that allows IPv6 configuration by DHCP SHOULD implement this IPv6 configuration by DHCP SHOULD implement this option. Other
option. Other configuration and management methods may use the configuration and management methods may use the format described by
format described by this option for consistency and convenience of this option for consistency and convenience of implementation on CEs
implementation on CEs that support multiple configuration methods. that support multiple configuration methods.
The only remaining provisioning information the CE requires in order The only remaining provisioning information the CE requires in order
to calculate the MAP IPv4 address and enable IPv4 connectivity is the to calculate the MAP IPv4 address and enable IPv4 connectivity is the
IPv6 prefix for the CE. The End-user IPv6 prefix is configured as IPv6 prefix for the CE. The End-user IPv6 prefix is configured as
part of obtaining IPv6 Internet access. part of obtaining IPv6 Internet access.
The MAP provisioning parameters, and hence the IPv4 service itself,
is tied to the End-user IPv6 prefix lease; thus, the MAP service is
also tied to this in terms of authorization, accounting, etc. The
MAP IPv4 address, prefix or shared IPv4 address and port set has the
same lifetime as its associated End-user IPv6 prefix.
A single MAP CE MAY be connected to more than one MAP domain, just as A single MAP CE MAY be connected to more than one MAP domain, just as
any router may have more than one IPv4-enabled service provider any router may have more than one IPv4-enabled service provider
facing interface and more than one set of associated addresses facing interface and more than one set of associated addresses
assigned by DHCP. Each domain a given CE operates within would assigned by DHCP. Each domain a given CE operates within would
require its own set of MAP configuration elements and would generate require its own set of MAP configuration elements and would generate
its own IPv4 address. its own IPv4 address.
The MAP DHCP option is specified in [I-D.ietf-softwire-map-dhcp]. The MAP DHCP option is specified in [I-D.ietf-softwire-map-dhcp].
7.2. MAP BR 7.2. MAP BR
 End of changes. 8 change blocks. 
12 lines changed or deleted 18 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/