< draft-ietf-netext-rfc5149bis-01.txt   draft-ietf-netext-rfc5149bis-02.txt >
Network-Based Mobility Extensions J. Korhonen Network-Based Mobility Extensions J. Korhonen
(Netext) Nokia Siemens Networks (Netext) Nokia Siemens Networks
Internet-Draft U. Nilsson Internet-Draft U. Nilsson
Obsoletes: 5149 (if approved) TeliaSonera Obsoletes: 5149 (if approved) TeliaSonera
Updates: 5213 (if approved) V. Devarapalli Updates: 5213 (if approved) V. Devarapalli
Intended status: Standards Track June 12, 2012 Intended status: Standards Track August 2, 2012
Expires: December 14, 2012 Expires: February 3, 2013
Service Selection for Mobile IPv6 and Proxy Mobile IPv6 Service Selection for Mobile IPv6 and Proxy Mobile IPv6
draft-ietf-netext-rfc5149bis-01.txt draft-ietf-netext-rfc5149bis-02.txt
Abstract Abstract
In some Mobile IPv6 deployments, identifying the mobile node or the In some Mobile IPv6 deployments, identifying the mobile node or the
mobility service subscriber is not enough to distinguish between mobility service subscriber is not enough to distinguish between
multiple services possibly provisioned to the mobile node and its multiple services possibly provisioned to the mobile node and its
mobility service subscription. A capability to specify different mobility service subscription. A capability to specify different
services in addition to the mobile node identity can be leveraged to services in addition to the mobile node identity can be leveraged to
provide flexibility for mobility service providers on provisioning provide flexibility for mobility service providers on provisioning
multiple services to one mobility service subscription. This multiple services to one mobility service subscription. This
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 December 14, 2012. This Internet-Draft will expire on February 3, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 3, line 25 skipping to change at page 3, line 25
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. Normative references . . . . . . . . . . . . . . . . . . . 10 7.1. Normative references . . . . . . . . . . . . . . . . . . . 10
7.2. Informative references . . . . . . . . . . . . . . . . . . 10 7.2. Informative references . . . . . . . . . . . . . . . . . . 10
Appendix A. Changes from RFC5149 . . . . . . . . . . . . . . . . 11 Appendix A. Changes from RFC5149 . . . . . . . . . . . . . . . . 11
A.1. Service Selection option in a PBA . . . . . . . . . . . . 11 A.1. Service Selection option in a PBA . . . . . . . . . . . . 11
A.2. Service Selection Identifier encoding . . . . . . . . . . 11 A.2. Service Selection Identifier encoding . . . . . . . . . . 11
A.3. Using Service Selection as a BCE lookup key . . . . . . . 11 A.3. Using Service Selection as a BCE lookup key . . . . . . . 11
A.4. Addition of a new Status Code . . . . . . . . . . . . . . 11 A.4. Addition of a new Status Code . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 A.5. Change of the document category from Informational to
Standards Track . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
Mobile IPv6 [RFC6275] can identify mobile nodes in various ways, Mobile IPv6 [RFC6275] can identify mobile nodes in various ways,
including home addresses, Network Access Identifiers (NAIs) including home addresses, Network Access Identifiers (NAIs)
[RFC4282][RFC4283], and credentials suitable for the Internet Key [RFC4282][RFC4283], and credentials suitable for the Internet Key
Exchange Protocol version 2 (IKEv2) [RFC4877]. Proxy Mobile IPv6 Exchange Protocol version 2 (IKEv2) [RFC4877]. Proxy Mobile IPv6
[RFC5213] uses Home Network Prefix (HNP) and/or Mobile Node [RFC5213] uses Home Network Prefix (HNP) and/or Mobile Node
Identifier [RFC4283]. In some Mobile IPv6 deployments, identifying Identifier [RFC4283]. In some Mobile IPv6 deployments, identifying
the mobile node or the mobility service subscriber via a Proxy Mobile the mobile node or the mobility service subscriber via a Proxy Mobile
skipping to change at page 6, line 29 skipping to change at page 6, line 29
Service Selection Mobility Option in octets, excluding the Option Service Selection Mobility Option in octets, excluding the Option
Type and Option Length fields. A value of zero (0) is not Type and Option Length fields. A value of zero (0) is not
allowed. allowed.
o Identifier: A variable-length encoded service identifier string o Identifier: A variable-length encoded service identifier string
used to identify the requested service. The identifier string used to identify the requested service. The identifier string
length is between 1 and 255 octets. This specification allows length is between 1 and 255 octets. This specification allows
international identifier strings that are based on the use of international identifier strings that are based on the use of
Unicode characters, encoded as UTF-8 [RFC3269], and formatted Unicode characters, encoded as UTF-8 [RFC3269], and formatted
using Normalization Form KC (NFKC) as specified in [NFKC]. using Normalization Form KC (NFKC) as specified in [NFKC].
Alternatively, based on the local configuration, the identifier Alternatively, based on the local configuration, the identifier
string can be encoded using the [RFC1035] domain name encoding string can be encoded using the domain name style encoding
[TS.23003]. The selection of the encoding is controlled by the described in Section 3.1 of [RFC1035]. However, the terminating
ServiceSelectionMobilityOptionFormat configuration object, see length of zero octet (i.e. the '\0' octet) is not included into
Section 4. the encoded identifier since the option length implicitly tells
when the identifier string ends [TS.23003]. The selection of the
encoding is controlled by the ServiceSelectionMobilityOptionFormat
configuration object, see Section 4.
'ims', 'voip', and 'voip.companyxyz.example.com' are valid 'ims', 'voip', and 'voip.companyxyz.example.com' are valid
examples of Service Selection option Identifiers. At minimum, the examples of Service Selection option Identifiers. At minimum, the
Identifier MUST be unique among the home agents to which the Identifier MUST be unique among the home agents to which the
mobile node is authorized to register. mobile node is authorized to register.
3. Processing Considerations 3. Processing Considerations
3.1. Binding Cache Entry Lookup Considerations 3.1. Binding Cache Entry Lookup Considerations
skipping to change at page 11, line 26 skipping to change at page 11, line 31
A.1. Service Selection option in a PBA A.1. Service Selection option in a PBA
3GPP EPC PMIPv6-based interfaces echo the Service Selection option 3GPP EPC PMIPv6-based interfaces echo the Service Selection option
always back in Proxy Binding Acknowledgements. This is clarified always back in Proxy Binding Acknowledgements. This is clarified
from the RFC5149, which did not say anything about the Service from the RFC5149, which did not say anything about the Service
Selection option in Proxy Binding Acknowledgement messages. Selection option in Proxy Binding Acknowledgement messages.
A.2. Service Selection Identifier encoding A.2. Service Selection Identifier encoding
3GPP EPC decided to encode their Service Selection Identifiers using 3GPP EPC decided to encode their Service Selection Identifiers using
the [RFC1035] domain name encoding [TS.23003]. Implementations has the [RFC1035] domain name style encoding [TS.23003]. Implementations
to take this into account when they intend to interoperate with 3GPP has to take this into account when they intend to interoperate with
EPC. 3GPP EPC.
A.3. Using Service Selection as a BCE lookup key A.3. Using Service Selection as a BCE lookup key
3GPP EPC use the Service Selection option as one of the BCE lookup 3GPP EPC use the Service Selection option as one of the BCE lookup
keys. This is additional to RFC5213 defined set of BCE lookup keys. keys. This is additional to RFC5213 defined set of BCE lookup keys.
A.4. Addition of a new Status Code A.4. Addition of a new Status Code
RFC5149 did not make a difference between a service authorization RFC5149 did not make a difference between a service authorization
failure (SERVICE_AUTHORIZATION_FAILED) and a service not being failure (SERVICE_AUTHORIZATION_FAILED) and a service not being
provisioned in a home agent/local mobility agent or otherwise unknown provisioned in a home agent/local mobility agent or otherwise unknown
(MISSING_OR_UNKNOWN_SERVICE). (MISSING_OR_UNKNOWN_SERVICE).
A.5. Change of the document category from Informational to Standards
Track
RFC5149 has implementations by multiple vendors and there are several
deployments. Furthermore, RFC5149 is not specific to 3GPP networks
anymore.
Authors' Addresses Authors' Addresses
Jouni Korhonen Jouni Korhonen
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
FIN-02600 Espoo FIN-02600 Espoo
Finland Finland
Email: jouni.nospam@gmail.com Email: jouni.nospam@gmail.com
 End of changes. 8 change blocks. 
12 lines changed or deleted 25 lines changed or added

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