draft-ietf-netlmm-lma-discovery-02.txt   draft-ietf-netlmm-lma-discovery-03.txt 
Network-based Localized Mobility J. Korhonen Network-based Localized Mobility J. Korhonen
Management (NetLMM) Nokia Siemens Networks Management (NetLMM) Nokia Siemens Networks
Internet-Draft V. Devarapalli Internet-Draft V. Devarapalli
Intended status: Informational WiChorus Intended status: Informational WiChorus
Expires: March 6, 2010 September 2, 2009 Expires: August 28, 2010 February 24, 2010
LMA Discovery for Proxy Mobile IPv6 LMA Discovery for Proxy Mobile IPv6
draft-ietf-netlmm-lma-discovery-02.txt draft-ietf-netlmm-lma-discovery-03.txt
Abstract
Large Proxy Mobile IPv6 deployments would benefit from a
functionality, where a Mobile Access Gateway could dynamically
discover a Local Mobility Anchor for a Mobile Node attaching to a
Proxy Mobile IPv6 domain. The purpose of the dynamic discovery
functionality is to reduce the amount of static configuration in the
Mobile Access Gateway. This specification describes a number of
possible dynamic Local Mobility Anchor discovery solutions.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 33 skipping to change at page 1, line 43
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 6, 2010. This Internet-Draft will expire on August 28, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
Large Proxy Mobile IPv6 deployments would benefit from a described in the BSD License.
functionality, where a Mobile Access Gateway could dynamically
discover a Local Mobility Anchor for a Mobile Node attaching to a
Proxy Mobile IPv6 domain. The purpose of the dynamic discovery
functionality is to reduce the amount of static configuration in the
Mobile Access Gateway. This specification describes a number of
possible dynamic Local Mobility Anchor discovery solutions.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. AAA-based Discovery Solutions . . . . . . . . . . . . . . . . 3 2. AAA-based Discovery Solutions . . . . . . . . . . . . . . . . 3
2.1. Receiving LMA Address during the Network Access 2.1. Receiving LMA Address during the Network Access
Authentication . . . . . . . . . . . . . . . . . . . . . . 4 Authentication . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Receiving LMA FQDN during the Network Access 2.2. Receiving LMA FQDN during the Network Access
Authentication . . . . . . . . . . . . . . . . . . . . . . 4 Authentication . . . . . . . . . . . . . . . . . . . . . . 4
3. Lower Layers based Discovery Solutions . . . . . . . . . . . . 5 3. Lower Layers based Discovery Solutions . . . . . . . . . . . . 5
3.1. Constructing the LMA FQDN from a mobile node Identity . . 5 3.1. Constructing the LMA FQDN from a mobile node Identity . . 5
3.2. Receiving LMA FQDN or IP Address from Lower Layers . . . . 6 3.2. Receiving LMA FQDN or IP Address from Lower Layers . . . . 6
3.3. Constructing the LMA FQDN from a Service Name . . . . . . 6 3.3. Constructing the LMA FQDN from a Service Name . . . . . . 6
4. Domain Name System Considerations . . . . . . . . . . . . . . 6 4. Domain Name System Considerations . . . . . . . . . . . . . . 6
5. Handover Considerations . . . . . . . . . . . . . . . . . . . 7 5. Handover Considerations . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
9. Informative References . . . . . . . . . . . . . . . . . . . . 9 9. Informative References . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
Large Proxy Mobile IPv6 (PMIPv6) [RFC5213] deployments would benefit Large Proxy Mobile IPv6 (PMIPv6) [RFC5213] deployments would benefit
from a functionality, where a Mobile Access Gateway (MAG) could from a functionality, where a Mobile Access Gateway (MAG) could
dynamically discover a Local Mobility Anchor (LMA) for a Mobile Node dynamically discover a Local Mobility Anchor (LMA) for a Mobile Node
(MN) attaching to a PMIPv6 domain. The purpose of the dynamic (MN) attaching to a PMIPv6 domain. The purpose of the dynamic
discovery functionality is to reduce the amount of static discovery functionality is to reduce the amount of static
skipping to change at page 6, line 11 skipping to change at page 6, line 11
not embed any LMA hosting entity information, the MAG might use a not embed any LMA hosting entity information, the MAG might use a
local database to map MN identities to corresponding LMAs. However, local database to map MN identities to corresponding LMAs. However,
this solution is unlikely to scale outside a limited PMIPv6 domain. this solution is unlikely to scale outside a limited PMIPv6 domain.
3.2. Receiving LMA FQDN or IP Address from Lower Layers 3.2. Receiving LMA FQDN or IP Address from Lower Layers
The solution described in this section is similar to the solution The solution described in this section is similar to the solution
discussed in Section 3.1. Instead of deriving the LMA FQDN from the discussed in Section 3.1. Instead of deriving the LMA FQDN from the
MN identity, the MAG receives a LMA FQDN or an IP address information MN identity, the MAG receives a LMA FQDN or an IP address information
from lower layers, for example, as a part of the normal lower layer from lower layers, for example, as a part of the normal lower layer
signaling when the MN attaches to the network. One existing example signaling when the MN attaches to the network. IKEv2 could be
of such lower layer functionality is the Access Point Name existing example of such lower layer signaling when IPsec is the
Information Element (APN IE) in 3GPP radio's network access signaling "lower layer" for the MN. IKEv2 has an IKEv2 IDr payload, which is
capable of carrying a FQDN [3GPP.24.008]. However, in general this used by the IKEv2 initiator (i.e. the MN in this case) to specify
means the MN is also the originator of the LMA information. The LMA which of the responder's identities (i.e. the LMA in this case) it
information content as such can be transparent to the MN, meaning the wants to talk to. And here the responder indentity could be an FQDN
MN has no knowledge it being anything LMA related. or an IP address of the LMA (as the IKEv2 identification payload can
be an IP address or an FQDN). Another existing example is the Access
Point Name Information Element (APN IE) in 3GPP radio's network
access signaling capable of carrying a FQDN [3GPP.24.008]. However,
in general this means the MN is also the originator of the LMA
information. The LMA information content as such can be transparent
to the MN, meaning the MN has no knowledge it being anything LMA
related.
3.3. Constructing the LMA FQDN from a Service Name 3.3. Constructing the LMA FQDN from a Service Name
Some network access technologies (including tunneling solutions) Some network access technologies (including tunneling solutions)
allow the MN to signal the service name that identifies a particular allow the MN to signal the service name that identifies a particular
service or the external network it wants to access. If the MN service or the external network it wants to access. If the MN
originated service name also embeds the information of the entity originated service name also embeds the information of the entity
hosting the service or the hosting information can be derived from hosting the service or the hosting information can be derived from
other information available at the same time (e.g., see Section 3.1), other information available at the same time (e.g., see Section 3.1),
then the MAG can construct a generic LMA FQDN (e.g., based on some then the MAG can construct a generic LMA FQDN (e.g., based on some
skipping to change at page 9, line 18 skipping to change at page 9, line 25
3GPP, "Numbering, addressing and identification", 3GPP 3GPP, "Numbering, addressing and identification", 3GPP
TS 23.003 8.2.0, September 2008. TS 23.003 8.2.0, September 2008.
[3GPP.24.008] [3GPP.24.008]
3GPP, "Mobile radio interface Layer 3 specification", 3GPP 3GPP, "Mobile radio interface Layer 3 specification", 3GPP
TS 24.008 8.6.0, June 2009. TS 24.008 8.6.0, June 2009.
[I-D.ietf-dime-pmip6] [I-D.ietf-dime-pmip6]
Korhonen, J., Bournelle, J., Chowdhury, K., Muhanna, A., Korhonen, J., Bournelle, J., Chowdhury, K., Muhanna, A.,
and U. Meyer, "Diameter Proxy Mobile IPv6: Mobile Access and U. Meyer, "Diameter Proxy Mobile IPv6: Mobile Access
Gateway and Local Mobility Anchor Interaction with Gateway and Local Mobility Anchor Interaction with
Diameter Server", draft-ietf-dime-pmip6-03 (work in Diameter Server", draft-ietf-dime-pmip6-04 (work in
progress), August 2009. progress), September 2009.
[I-D.ietf-mipshop-pfmipv6] [I-D.ietf-mipshop-pfmipv6]
Yokota, H., Chowdhury, K., Koodli, R., Patil, B., and F. Yokota, H., Chowdhury, K., Koodli, R., Patil, B., and F.
Xia, "Fast Handovers for Proxy Mobile IPv6", Xia, "Fast Handovers for Proxy Mobile IPv6",
draft-ietf-mipshop-pfmipv6-08 (work in progress), draft-ietf-mipshop-pfmipv6-12 (work in progress),
July 2009. December 2009.
[RFC2136] Vixie, P., Thomson, S., Rekhter, Y., and J. Bound, [RFC2136] Vixie, P., Thomson, S., Rekhter, Y., and J. Bound,
"Dynamic Updates in the Domain Name System (DNS UPDATE)", "Dynamic Updates in the Domain Name System (DNS UPDATE)",
RFC 2136, April 1997. RFC 2136, April 1997.
[RFC2308] Andrews, M., "Negative Caching of DNS Queries (DNS [RFC2308] Andrews, M., "Negative Caching of DNS Queries (DNS
NCACHE)", RFC 2308, March 1998. NCACHE)", RFC 2308, March 1998.
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for [RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
specifying the location of services (DNS SRV)", RFC 2782, specifying the location of services (DNS SRV)", RFC 2782,
 End of changes. 9 change blocks. 
31 lines changed or deleted 42 lines changed or added

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