PCP Working Group T. Reddy
Internet-Draft P. Patil
Intended status: Standards Track R. Chandrasekaran
Expires: August 15, 2013 D. Wing
Cisco
February 11, 2013
PCP Server Discovery with IPv4 traffic offload for Proxy Mobile IPv6
draft-rpcw-pcp-pmipv6-serv-discovery-02
Abstract
This document proposes a solution to PCP Server Discovery problems in
Proxy Mobile IPv6 (PMIPv6) networks when both home network traffic
and traffic off-loaded to local access network require traversing a
gateway implementing NAT and/or Firewall. This draft proposes
enhancements to DHCPv4 Relay Agent by introducing a new sub-option
under DHCPv4 Relay Option and to PMIPv6 signaling through additional
options to Proxy Binding Update/Acknowledgement messages.
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 August 15, 2013.
Copyright Notice
Copyright (c) 2013 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
Reddy, et al. Expires August 15, 2013 [Page 1]
Internet-Draft PCP Server Discovery for PMIPv6 February 2013
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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Solution overview . . . . . . . . . . . . . . . . . . . . . . 4
4. Mobility Options . . . . . . . . . . . . . . . . . . . . . . . 6
5. DHCPv4 Relay Agent co-located with MAG . . . . . . . . . . . . 8
5.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.2. Relay Agent behavior . . . . . . . . . . . . . . . . . . . 9
5.3. DHCPv4 Server behavior . . . . . . . . . . . . . . . . . . 9
6. DHCPv4 Server co-located with MAG . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
10. Change History . . . . . . . . . . . . . . . . . . . . . . . . 11
10.1. Changes from draft-rpcw-pcp-pmipv6-serv-discovery-01
to -02 . . . . . . . . . . . . . . . . . . . . . . . . . . 11
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
11.1. Normative References . . . . . . . . . . . . . . . . . . . 11
11.2. Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
Reddy, et al. Expires August 15, 2013 [Page 2]
Internet-Draft PCP Server Discovery for PMIPv6 February 2013
1. Introduction
Given the exponential growth in the mobile data traffic, Mobile
Operators are looking for ways to offload some of the IP traffic
flows at the nearest access edge that has an Internet peering point.
This approach results in efficient usage of the mobile packet core
and helps lower the transport cost.
[I-D.ietf-netext-pmipv6-sipto-option] defines a way to signal the
Traffic Offload capability of a Mobile Access Gateway (MAG) to the
Local Mobility Anchor (LMA) in Proxy Mobile IP Networks. There are
scenarios in PMIPv6 Mobile Networks where the traffic going through