NETEXT WG S. Gundavelli
Internet-Draft Cisco
Intended status: Standards Track J. Korhonen
Expires: June 28, 2012 Nokia Siemens Networks
M. Grayson
K. Leung
R. Pazhyannur
Cisco
December 26, 2011
Access Network Identifier Option for Proxy Mobile IPv6
draft-ietf-netext-access-network-option-01.txt
Abstract
This specification defines a mechanism and a related mobility option
for carrying the access network identifier and the access operator
identification information from the mobile access gateway to the
local mobility anchor over Proxy Mobile IPv6. Based on the received
information, the local mobility anchor is able to provide access
network and access operator specific handling or policing for the
mobile node traffic.
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 June 28, 2012.
Copyright Notice
Copyright (c) 2011 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
Gundavelli, et al. Expires June 28, 2012 [Page 1]
Internet-Draft Access Network Identifier Option December 2011
(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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 4
2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
3. Access Network Identifier Option . . . . . . . . . . . . . . . 4
3.1. Access Network Identifier Sub-Option . . . . . . . . . . . 5
3.2. Network-Identifier Sub-Option . . . . . . . . . . . . . . 6
3.3. Geo-Location ANI Sub-Option . . . . . . . . . . . . . . . 6
3.4. Operator-Identifier Sub-Option . . . . . . . . . . . . . . 7
4. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
Gundavelli, et al. Expires June 28, 2012 [Page 2]
Internet-Draft Access Network Identifier Option December 2011
1. Introduction
In many deployments there is a need for the local mobility anchor to
provide differentiated services and policing to the mobile nodes
based on the access network to which they are attached. Policy
systems in mobility architectures such as PCC [TS23203] and ANDSF
[TS23402] in 3GPP system allow configuration of policy rules with
conditions based on the access network information. For example, the
service treatment for the mobile node's traffic may be different when
they are attached to a access network owned by the home operator than
when owned by a roaming partner. The service treatment can also be
different based on the configured SSID in case of IEEE 802.11 based
access networks.
The Proxy Mobile IPv6 specification [RFC5213] allows carrying of the
Access Technology Type (ATT) information from the mobile access
gateway (MAG) to the local mobility anchor (LMA). However, the
Access Technology Type alone is not sufficient for correct policy to
be applied at the LMA and there is a need to ensure additional
information related to the access network is available. Learning the
access network operator identity may not be possible for an LMA
without a support of an additional policy framework that is able to
provide required information out of band to the LMA. Such a policy
framework may not be required for all Proxy Mobile IPv6 deployments
and hence an alternative approach for carrying such information is
required to ensure that additional information related to the access
network is available.
This document defines a new mobility option, Access Network
Identifier (ANI) option for Proxy Mobile IPv6 (PMIPv6), that can be
used by mobile access gateway for carrying the access network
information to the local mobility anchor. The specific details on
how the local mobility anchor uses this information is out-of-scope
for this document.
Access-Net-1: Network-Id, Location, Operator-Id
+--+
|AP|-------. {Access Specific Policies)
+--+ | _-----_ |
+-----+ _( )_ +-----+
| MAG |-=====( PMIPv6 )======-| LMA |-
+-----+ (_ Tunnel_) +-----+
+--+ | '-----'
|AP|-------'
+--+
Access-Net-2: Network-Id, Location, Operator-Id
Gundavelli, et al. Expires June 28, 2012 [Page 3]
Internet-Draft Access Network Identifier Option December 2011
Figure 1: Access Networks attached to MAG
In Figure 1, the mobile access gateway can potentially deliver the
information elements related to the access network to the local
mobility anchor over Proxy Mobile IPv6 signaling messages.
2. Conventions and Terminology
2.1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2.2. Terminology
All the mobility related terms used in this document are to be
interpreted as defined in the Proxy Mobile IPv6 specifications
[RFC5213] and [RFC5844]. Additionally, this document uses the
following abbreviations:
Service Set Identifier
Service Set Identifier (SSID) identifies the name of the IEEE
802.11 network. SSID differentiates from one network to the
other.
Vendor ID
The Vendor ID is the SMI Network Management Private Enterprise
Code of the IANA-maintained Private Enterprise Numbers registry
[SMI].
ANDSF
Access Network Discovery and Selection Function.
PCC
Policy and Charging Control Framework.
3. Access Network Identifier Option
The Access Network Identifier is a mobility option defined for
carrying it in Proxy Binding Update (PBU) and Proxy Binding
Acknowledgement (PBA) messages exchanged between a local mobility
Gundavelli, et al. Expires June 28, 2012 [Page 4]
Internet-Draft Access Network Identifier Option December 2011
anchor and a mobile access gateway. This mobility option is used for
carrying one or more Access Network Identifier Sub-options. The
format of the Access Network Identifier Sub-option is defined in
Section 3.1. There can only be a single instance of this mobility
option in a mobility message.
The alignment requirement for this option is 4n.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
... ANI Sub-option(s) ... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Access Network Identifier Option
Type: (IANA-1)
Length: 8-bit unsigned integer indicating the length in octets of
the option, excluding the type and length fields.
3.1. Access Network Identifier Sub-Option
The Access Network Identifier Sub-Option is defined for carrying it
in the Access Network Identifier mobility option. This sub-option is
used for carrying information elements related to the access network
to which the mobile node is attached. The format of the Access
Network Identifier Sub-option is defined as follows.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type | ANI Length | Option Data ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Access Network Identifier Sub-Option
ANI Type: 8-bit unsigned integer indicating the type of the Access
Network Identifier sub-option. This specification defines the
following types:
Gundavelli, et al. Expires June 28, 2012 [Page 5]
Internet-Draft Access Network Identifier Option December 2011
1 - Network-Identifier Sub-option
2 - Geo-Location Sub-option
3 - Operator-Identifier Sub-option
ANI Length: 8-bit unsigned integer indicating the number of octets
needed to encode the Network Identifier sub-option excluding the
ANI Type and ANI Length fields of the sub-option.
3.2. Network-Identifier Sub-Option
The Network-Identifier is a mobility sub-option that can be carried
in Access Network Identifier option defined in Section 3. This sub-
option can be used for carrying the IEEE 802.11 SSID name of the
network to which the mobile node is attached. There can only be a
single instance of this specific sub-option in any Access Network
Identifier option. The format of this option is defined below.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type=1 | ANI Length | SSID ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Network-Identifier Sub-option
ANI Type: It should be set to value of (1), indicating that its a
Network-Identifier sub-option
ANI Length: Total length of this sub option, excluding the ANI Type
and ANI length fields. The value can be in the range of 2 to 32
octets.
SSID: SSID of the access network to which the mobile node is
attached. The string is carried in UTF-8 representation.
3.3. Geo-Location ANI Sub-Option
The Geo-Location is a mobility sub-option that can be carried in
Access Network Identifier option defined in Section 3. This sub-
option can be used for carrying the Geo-location of the network to
which the mobile node is attached. There can only be a single
instance of this specific sub-option in any Access Network Identifier
option. The format of this option is defined below.
Gundavelli, et al. Expires June 28, 2012 [Page 6]
Internet-Draft Access Network Identifier Option December 2011
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type=2 | ANI Length=8 |N| Latitude Degrees |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| La-Minutes | La-Seconds |E| Longitude Degrees |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lo-Minutes | Lo-Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Geo-Location ANI sub-option
ANI Type: It should be set to value of (2), indicating that its Geo-
Location sub-option
ANI Length: Total length of this sub-option, excluding the ANI Type
and ANI length fields. It should be set to a value of (8).
N: When the flag (N) is set to a value of (1), it means North, else
its South
Latitude Degrees: Allowed range from 0 to 90 degrees, northern or
southern hemisphere as qualified by the (N) flag
La-Minutes: Allowed range is 0 to 59
La-Seconds: Allowed range is 0 to 59
E: When the flag (E) is set to a value of (1), it means East, else
its West
Longitude Degrees: Allowed range from 0 to 90 degrees, eastern or
western hemisphere as qualified by the (E) flag
Lo-Minutes: Allowed range is 0 to 59
Lo-Seconds: Allowed range is 0 to 59
3.4. Operator-Identifier Sub-Option
The Operator-Identifier is a mobility sub-option that can be carried
in Access Network Identifier option defined in Section 3. This sub-
option can be used for carrying the operator identifier of the access
network to which the mobile node is attached. There can only be a
single instance of this specific sub-option in any Access Network
Identifier option. The format of this option is defined below.
Gundavelli, et al. Expires June 28, 2012 [Page 7]
Internet-Draft Access Network Identifier Option December 2011
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type=3 | ANI Length | Op-ID Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Operator Identifier ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Operator-Identifier Sub-option
ANI Type: It should be set to value of (3), indicating that its
Operator-Identifier sub-option
ANI Length: Total length of this sub option, excluding the ANI Type
and ANI length fields.
Operator Identifier (Op-ID) Type: 8-bit unsigned integer indicating
the type of the Operator Identifier. Currently the following
types are defined:
0 - reserved.
1 - Vendor ID as a four octet Private Enterprise Number [SMI].
2 - Realm of the operator. Realm names are required to be
unique, and are piggybacked on the administration of the DNS
namespace. Realms are encoded using a domain name encoding
defined in [RFC1035].
Operator Identifier: Up to 253 octets of the operator identifier.
The encoding of the identifier depends on the used Operator-ID
Type. Numeric values are encoded in network byte order and
strings have no terminating '\0' mark.
4. Protocol Considerations
The following considerations apply to the local mobility anchor and
the mobile access gateway.
o The conceptual Binding Cache entry data structure maintained by
the local mobility anchor, described in Section 5.1 of [RFC5213],
MUST be extended to store the access network information
associated with the current session. Specifically, the following
parameters must be defined.
Gundavelli, et al. Expires June 28, 2012 [Page 8]
Internet-Draft Access Network Identifier Option December 2011
Network Identifier
Operator Identifier
Geo-location
o The conceptual Binding Update List entry data structure maintained
by the mobile access gateway, described in Section 6.1 of
[RFC5213], MUST be extended to store the access network
information associated with the current session. Specifically,
the following parameters must be defined.
Network Identifier
Operator Identifier
Geo-location
o The mobile access gateway may be statically configured with the
access network information related to the access links its
attached to. In access systems where the mobile access gateway is
attached to a micro-mobility domain such as IEEE 802.11 WLAN
domain, the DHCP relay agent function in that micro-mobility
domain may be configured to add the access network information in
DHCP option (82), which is the DHCP Relay Agent Information option
[RFC3046]. The mobile access gateway may learn the access network
information from this option. The specifics on how this DHCP
option 82 is encoded is outside the scope of this document.
o If the mobile access gateway is configured to support to Access
Network Information option, it SHOULD include this option in all
Proxy Binding Update message that it sends to the local mobility
anchor. The Access Network Information option SHOULD be
constructed as specified in Section 3. It should include the
relevant ANI sub-options that the mobile access gateway is
configured to carry them in the Proxy Mobile IPv6 signaling
messages.
o On receiving a Proxy Binding Update message [RFC5213] from a
mobile access gateway with the Access Network Information option,
the local mobility anchor must process the option and update the
corresponding fields in the Binding Cache entry.
o If the received Proxy Binding Update message does not include the
Access Network Information option, but the mobility session
associated to that request has the previously notified access
network specific information elements, the same MUST be updated
and those information elements previously received MUST be
Gundavelli, et al. Expires June 28, 2012 [Page 9]
Internet-Draft Access Network Identifier Option December 2011
removed.
o The local mobility anchor MAY choose to use the access network
information options for applying any access operator specific
handling or policing of the mobile node traffic.
5. IANA Considerations
This document requires the following IANA actions.
Action-1: This specification defines a new Mobility Header option,
the Access Network Identifier. This mobility option is described
in Section 3. The Type value for this option needs to be assigned
from the same numbering space as allocated for the other mobility
options, as defined in [RFC6275].
Action-2: This specification defines a new mobility sub-option
format, Access Network Information (ANI) sub-option. The format
of this mobility sub-option is described in Section 3.1. This
sub-option can be carried in Access Network Information option.
The type value for this sub-option needs to be managed by IANA,
under the Registry, Access Network Information sub-option. This
specification reserves the type values of (1), (2) and (3).
Approval of new Access Network Information (ANI) sub-option type
values are to be made through IANA Expert Review.
Action-3: This specification defines a new mobility sub-option,
Operator-Identifier sub-option. The format of this mobility sub-
option is described in Section 3.4. The Operator Identifier
(Op-Id) Type field of this sub-option introduces a new number
space. This number space needs to be managed by IANA, under the
Registry, Operator Identifier Type Registry. This specification
reserves the type values of (0), (1) and (2). Approval of new
Operator Identifier Type values are to be made through IANA Expert
Review.
6. Security Considerations
The Access Network Information option defined in this specification
is for use in Proxy Binding Update and Proxy Binding Acknowledgement
messages. This option is carried like any other mobility header
option as specified in [RFC6275] and does not require any special
security considerations.
The Geo-location sub-option carried in the Access Network Information
option exposes the geo-location of the mobile node as presented by
Gundavelli, et al. Expires June 28, 2012 [Page 10]
Internet-Draft Access Network Identifier Option December 2011
the mobile access gateway and this information should be considered
as very sensitive. Care must be taken to secure the Proxy Mobile
IPv6 signaling messages when carrying this sub-option. The base
Proxy Mobile IPv6 specification [RFC6275] specifies the use of IPsec
for securing the signaling messages and those mechanisms can be
enabled for protecting this information.
7. Acknowledgements
The authors would also like to acknowledge all the discussions
related to carrying Access Network Information option in Proxy Mobile
IPv6 protocol signaling. Additionally, the authors would like to
thank Carlos Bernardos, Stefano Faccin, Ryuji Wakikawa, Basavaraj
Patil, Gerardo Gieratta, and Eric Voit for all the discussions around
this topic.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,
and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy
Mobile IPv6", RFC 5844, May 2010.
8.2. Informative References
[RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987.
[RFC3046] Patrick, M., "DHCP Relay Agent Information Option",
RFC 3046, January 2001.
[RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support
in IPv6", RFC 6275, July 2011.
[SMI] IANA, "PRIVATE ENTERPRISE NUMBERS", SMI Network Management
Private Enterprise Codes, February 2011.
[TS23203] 3GPP, "Policy and Charging Control Architecture", 2010.
[TS23402] 3GPP, "Architecture enhancements for non-3GPP accesses",
Gundavelli, et al. Expires June 28, 2012 [Page 11]
Internet-Draft Access Network Identifier Option December 2011
2010.
Authors' Addresses
Sri Gundavelli
Cisco
170 West Tasman Drive
San Jose, CA 95134
USA
Email: sgundave@cisco.com
Jouni Korhonen
Nokia Siemens Networks
Linnoitustie 6
Espoo FIN-02600
Finland
Email: jouni.nospam@gmail.com
Mark Grayson
Cisco
11 New Square Park
Bedfont Lakes, FELTHAM TW14 8HA
ENGLAND
Email: mgrayson@cisco.com
Kent Leung
Cisco
170 West Tasman Drive
San Jose, CA 95134
USA
Email: kleung@cisco.com
Gundavelli, et al. Expires June 28, 2012 [Page 12]
Internet-Draft Access Network Identifier Option December 2011
Rajesh Pazhyannur
Cisco
170 West Tasman Drive
San Jose, CA 95134
USA
Email: rpazhyan@cisco.com
Gundavelli, et al. Expires June 28, 2012 [Page 13]
