< draft-mrw-nat66-15.txt   draft-mrw-nat66-16.txt >
Network Working Group M. Wasserman Network Working Group M. Wasserman
Internet-Draft Painless Security Internet-Draft Painless Security
Intended status: Experimental F. Baker Intended status: Experimental F. Baker
Expires: October 26, 2011 Cisco Systems Expires: October 28, 2011 Cisco Systems
April 24, 2011 April 26, 2011
IPv6-to-IPv6 Network Prefix Translation IPv6-to-IPv6 Network Prefix Translation
draft-mrw-nat66-15 draft-mrw-nat66-16
Abstract Abstract
This document describes a stateless, transport-agnostic IPv6-to-IPv6 This document describes a stateless, transport-agnostic IPv6-to-IPv6
Network Prefix Translation (NPTv6) function that provides the address Network Prefix Translation (NPTv6) function that provides the address
independence benefit associated with IPv4-to-IPv4 NAT (NAPT44), and independence benefit associated with IPv4-to-IPv4 NAT (NAPT44), and
in addition provides a 1:1 relationship between addresses in the in addition provides a 1:1 relationship between addresses in the
"inside" and "outside" prefixes, preserving end to end reachability "inside" and "outside" prefixes, preserving end to end reachability
at the network layer. at the network layer.
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 October 26, 2011. This Internet-Draft will expire on October 28, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 4, line 14 skipping to change at page 4, line 14
1. Introduction 1. Introduction
This document describes a stateless IPv6-to-IPv6 Network Prefix This document describes a stateless IPv6-to-IPv6 Network Prefix
Translation (NPTv6) function, designed to provide address Translation (NPTv6) function, designed to provide address
independence to the edge network. It is transport-agnostic with independence to the edge network. It is transport-agnostic with
respect to transports that don't checksum the IP header, such as respect to transports that don't checksum the IP header, such as
SCTP, and to transports that use the TCP/UDP/DCCP pseudo-header and SCTP, and to transports that use the TCP/UDP/DCCP pseudo-header and
checksum [RFC1071]. checksum [RFC1071].
Note that, for reasons discussed in [RFC2993] and Section 5, the IETF For reasons discussed in [RFC2993] and Section 5, the IETF does not
does not generally recommend the use of Network Address Translation recommend the use of Network Address Translation technology for IPv6.
technology for IPv6. Where Network Address Translation is Where translation is implemented, however, this specification
implemented, however, this specification provides a mechanism that provides a mechanism that has less architectural problems than merely
has less architectural problems than merely implementing a implementing a traditional stateful Network Address Translator in an
traditional IPv4 NAT in an IPv6 environment. Some problems remain, IPv6 environment. It also provides a useful alternative to the
however, and the reader should consult Section 5, [RFC4864], and complexities and costs imposed by multihoming using provider-
[RFC5902], for the implications and approaches that help avoid all independent addressing, and the routing and network management issues
types of NATs. of overlaid ISP address space. Some problems remain, however. The
reader should consider the alternatives suggested in [RFC4864], and
the considerations of [RFC5902], for improved approaches.
The stateless approach described in this document has several The stateless approach described in this document has several
ramifications: ramifications:
o Any security benefit that NAPT44 might offer is not present in o Any security benefit that NAPT44 might offer is not present in
NPTv6, necessitating the use of a firewall to obtain those NPTv6, necessitating the use of a firewall to obtain those
benefits if desired. An example of such a firewall is described benefits if desired. An example of such a firewall is described
in [RFC6092]. in [RFC6092].
o End to end reachability is preserved, although the address used o End to end reachability is preserved, although the address used
 End of changes. 4 change blocks. 
13 lines changed or deleted 15 lines changed or added

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