PREFIX64 PCP Option for NAT64
draft-boucadair-pcp-nat64-prefix64-option-00
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2012-09-06
|
|
Replaced by |
|
rfc7225, draft-ietf-pcp-nat64-prefix64
|
|
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 M. Boucadair
Internet-Draft France Telecom
Intended status: Standards Track September 6, 2012
Expires: March 10, 2013
PREFIX64 PCP Option for NAT64
draft-boucadair-pcp-nat64-prefix64-option-00
Abstract
This document defines a new PCP option to learn the Prefix64 used by
a PCP-controlled NAT64 device to build IPv4-embedded IPv6 addresses.
This option is needed for successful communications when IPv4
addresses are used in referrals (e.g., SIP).
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 March 10, 2013.
Copyright Notice
Copyright (c) 2012 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
(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.
Boucadair Expires March 10, 2013 [Page 1]
Internet-Draft PREFIX64 PCP Option September 2012
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 4
3. PREFIX64 Option . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Behaviour . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8
Boucadair Expires March 10, 2013 [Page 2]
Internet-Draft PREFIX64 PCP Option September 2012
1. Introduction
This document defines a new PCP option [I-D.ietf-pcp-base] to inform
PCP Clients about the Prefix64 [RFC6052] used by a PCP-controlled
NAT64 device [RFC6146].
This option is required to help establishing communications between
IPv6-only hosts and remote IPv4-hosts. An illustration example is
shown in Figure 1. In this example, NAT64 is co-located with a PCP
server while IPv6-only SIP UA interacts with a PCP Client.
In Figure 1, the PCP Client issues a PCP MAP request with
PORT_RESERVATION_OPTION to reserve a pair of ports preserving parity
and contiguity [I-D.boucadair-pcp-rtp-rtcp]. A pair of ports and an
external IPv4 address are then returned by the PCP server to the
requesting PCP Client. This information is used by the IPv6-only SIP
UA to build its SDP offer which contains exclusively IPv4 addresses
(especially in the "c=" line, the port indicated for media port is
the external port assigned by the PCP server). The INVITE request
including the SDP offer is then forwarded by the NAT64 to the Proxy
Server which will relay it to the called party (i.e., IPv4-only SIP
UA) (Steps (1) to (3)). IPv4-only SIP UA accepts the offer and sends
back its SDP answer in a "200 OK" message which is relayed by the SIP
Proxy Server and NAT64 until being delivered to IPv6-only SIP UA
(Steps (4) to (6)). At the end of this process, IPv4-only SIP UA can
send media streams to the IPv4 address/port as indicated in the SDP
Show full document text