Community Wi-Fi Services Over Residential Architectures
draft-gundavelli-v6ops-community-wifi-svcs-00
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
|---|---|---|---|
| Authors | Sri Gundavelli , Mark Grayson , Pierrick Seite , Yiu Lee | ||
| Last updated | 2012-03-05 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-gundavelli-v6ops-community-wifi-svcs-00
V6OPS WG S. Gundavelli
Internet-Draft M. Grayson
Intended status: Informational Cisco
Expires: September 6, 2012 P. Seite
France Telecom - Orange
Y. Lee
Comcast
March 5, 2012
Community Wi-Fi Services Over Residential Architectures
draft-gundavelli-v6ops-community-wifi-svcs-00.txt
Abstract
The tremendous growth in Wi-Fi technology adoption over the last
decade has met the ultimate possible goal of 100% adoption rate. All
most every new mobile device is now equipped with IEEE 802.11-based
wireless interface and with pre-configured policy to prefer Wi-Fi to
cellular access. Matching this evolution is every service provider's
desire to offer Wi-Fi based broadband services; a new business
opportunity even for fixed line operators. Operators are exploring
options to monetize their existing networks, most with nation-wide
footprint, to build a high-speed Wi-Fi service that can be the basis
for offering new wireless broadband services. This document
identifies the requirements for supporting these new Wi-Fi community
services and the mobility tools which have been standardized in IETF
that can be used for enabling these architectures.
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 September 6, 2012.
Copyright Notice
Gundavelli, et al. Expires September 6, 2012 [Page 1]
Internet-Draft Community Wi-Fi Services March 2012
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions and Terminology . . . . . . . . . . . . . . . . . . 4
2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Deployment Models . . . . . . . . . . . . . . . . . . . . . . . 4
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Subscriber Service Authorization . . . . . . . . . . . . . 6
4.2. Location Services . . . . . . . . . . . . . . . . . . . . . 6
4.3. Local Services Access & Internet Traffic Offload . . . . . 6
4.4. Multiple WLAN SSID Support . . . . . . . . . . . . . . . . 6
4.5. Multiple Home Network Service (APN) Access . . . . . . . . 6
4.6. CPE Identity and Authorization . . . . . . . . . . . . . . 7
4.7. Mobility within the WLAN Access Network . . . . . . . . . . 7
4.8. Mobile Gateway Integration . . . . . . . . . . . . . . . . 7
4.9. Mobility across WLAN and Macro Access . . . . . . . . . . . 7
4.10. Differentiated Services for Users behind CPE . . . . . . . 7
4.11. Service and Network Security . . . . . . . . . . . . . . . 7
4.12. Legal Intercept . . . . . . . . . . . . . . . . . . . . . . 7
4.13. Charging & Accounting . . . . . . . . . . . . . . . . . . . 7
4.14. Policy Provisioning . . . . . . . . . . . . . . . . . . . . 8
5. Solution Approach . . . . . . . . . . . . . . . . . . . . . . . 8
5.1. PMIPv6 MAG in the Residential CPE . . . . . . . . . . . . . 8
5.2. PMIPv6 MAG in the Access Gateway . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
Gundavelli, et al. Expires September 6, 2012 [Page 2]
Internet-Draft Community Wi-Fi Services March 2012
1. Introduction
The tremendous growth in Wi-Fi technology adoption over the last
decade has met the ultimate possible goal of 100% adoption rate. All
most every new mobile device is now equipped with IEEE 802.11-based
wireless interface and with pre-configured policy to prefer Wi-Fi to
cellular access. This so called, "cheap access based on unlicensed
spectrum", is no longer considered an unreliable access, but with all
the available protocol tools and with maturity in technology,
building a reliable broadband service that can meet the committed
service-level agreements is a non-issue.
Matching this evolution is every service provider's desire to offer
Wi-Fi based broadband services; a new business opportunity even for
fixed line operators. The demand for bandwidth is only growing with
the availability of new smart devices, new technology applications
and with all the content in the Internet. Furthermore, an increasing
percentage of mobile consumption is happening in the home and so DSL/
Cable operators are exploring options to monetize their existing
networks, most with nation-wide footprint, to build a high-speed
Wi-Fi service that can be the basis for offering new wireless
broadband services and for building roaming agreements with
traditional mobile operators, who are unable to meet the mobile
subscriber growth due to the finite licensed spectrum available for
macro-cell deployments. Every residential CPE device that the
operator owns can now be enabled to provide Wi-Fi service and new
community Wi-Fi hotspots can be built in any location where there is
fixed line coverage. A wireless service based on unlicensed
spectrum, and leveraging existing transport is a huge incentive for
operators to enter this new market.
To support these business goals, operators are looking at mobility
architectures for supporting various requirements. Not all
requirements are well understood, and neither are the implications
with the chosen solution approaches for each of those requirements.
The choice of the architecture has an implication on the CPE
evolution and on the core infrastructure feature requirements.
Therefore, the sole purpose and the goal of this document is to
present all the requirements, identify the protocol tools and any
potential gaps. This analysis is important for enabling the network
vendors and the mobile operators to make the right design choices and
leverage the existing tools that the mobility groups in IETF have
already developed and discourage them from adopting proprietary, non-
standard mechanisms or developing redundant alternatives.
Work in progress ...
Gundavelli, et al. Expires September 6, 2012 [Page 3]
Internet-Draft Community Wi-Fi Services March 2012
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
This document uses the following abbreviations:
Customer Premises Equipment (CPE)
It is a network device that is located in the Customer premises.
This device is connected to service providers network and defines
the demarcation point between the provider and the customer.
Access Point Name (APN)
Its the name of a packet data network. This APN concept was first
introduced in GPRS by 3GPP to enable legacy Intelligent Networking
(IN) approaches to be applied to the newly deployed IP packet data
services. In roaming deployments, the APN construct was visible
to the visited network and allowed legacy IN charging solutions to
be supported. Defining an application specific APN then allowed
application charging to be supported.
3. Deployment Models
Figure 1 explains the community Wi-Fi deployment model.
Gundavelli, et al. Expires September 6, 2012 [Page 4]
Internet-Draft Community Wi-Fi Services March 2012
_----_ _----_ _----_
_( )_ _( )_ _( )_
(Operator-1) (Operator-2) (Operator-3)
(_ _) (_ _) (_ _)
'----' '----' '----'
| | |
| | |
| | |
+-------------. | .-------------+
| | |
| | |
| | |
| | |
+--------+ _----_
+---+ | | _( )_
|AAA|. . . . . . . | Access |----------( Internet )
+---+ | Aggreg | (_ _)
| Gateway| '----'
+--------+
|
+--------+
| CMTS |
+--------+
|
-- -- --- -- --
-- --
-- --
-- Community Wi-Fi --
-- --
-- --
| -- -- --- -- -- |
| | |
+-----+ +-----+ +-----+
| CPE | | CPE | | CPE |
| | | | | |
+-----+ +-----+ +-----+
. . .
/ \ / \ / \
MN MN MN MN
Figure 1: WLAN Service for Retail Model
4. Requirements
Gundavelli, et al. Expires September 6, 2012 [Page 5]
Internet-Draft Community Wi-Fi Services March 2012
4.1. Subscriber Service Authorization
4.2. Location Services
In many deployments, there is a need for the mobile operator 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 and ANDSF 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 Service Set Identifiers (SSID) in case of IEEE
802.11 based access networks. Other examples of location services
include the operator's ability to display a location specific Web
Page, or apply tariff based on the location.
4.3. Local Services Access & Internet Traffic Offload
In the integrated access architectures, the mobile node's IP traffic
is always tunneled back from the access network to the mobile gateway
in the home network. However, with the exponential growth in the
mobile data traffic, mobile operators are exploring new ways to
offload some of the IP traffic flows at the nearest access edge where
ever there is an internet peering point, as supposed to carrying it
all the way to the mobility anchor in the home network. Not all IP
traffic need to be routed back to the home network, some of the non-
essential traffic which does not require IP mobility support can be
offloaded at the mobile access gateway in the access network. This
approach provides greater leverage and efficient usage of the mobile
packet core which help lowering transport cost. The local mobility
anchor in the home network can potentially deliver the IP flow
selectors to the mobile access gateway in the access network, for
identifying the IP flows that need to be offloaded.
4.4. Multiple WLAN SSID Support
Every CPE in a residential home can be configured with multiple
SSID's. One SSID for the home user and the other SSID for the
community usage.
4.5. Multiple Home Network Service (APN) Access
The 3GPP system architecture supports the concept of an Access Point
Name (APN). An APN can identify a particular routing domain and can
be used by 3GPP operators to segment user traffic. APNs are included
in the session establishment signaling sent by 3GPP User Equipments
Gundavelli, et al. Expires September 6, 2012 [Page 6]
Internet-Draft Community Wi-Fi Services March 2012
(UEs), identifying which routing domain they want to be connected to.
Furthermore, 3GPP has defined a system architecture which supports
the ability of a single UE to have simultaneous connectivity to a
plurality of APNs, and be allocated multiple IPv4 addresses and/or
IPv6 prefixes from the network.
There is a need to ensure multiple APN access for a subscriber in the
community Wi-Fi network.
4.6. CPE Identity and Authorization
There are two known models with respect to CPE roll out. The
consumer may purchase a device off the shelf and plugin to the
network, or the operator at the time of service creation may have
shipped a new device with the pre-provisioned service configuration.
In either case, the operator needs to be able to identify the device
based on the IP address and associate that to a given location
4.7. Mobility within the WLAN Access Network
The mobile node should have the ability to roam within the community
wi-fi zone and be able to preserve the IP address across roaming.
4.8. Mobile Gateway Integration
Roaming users from the home network should have the ability to
4.9. Mobility across WLAN and Macro Access
TBD
4.10. Differentiated Services for Users behind CPE
TBD
4.11. Service and Network Security
TBD
4.12. Legal Intercept
TBD
4.13. Charging & Accounting
TBD
Gundavelli, et al. Expires September 6, 2012 [Page 7]
Internet-Draft Community Wi-Fi Services March 2012
4.14. Policy Provisioning
TBD
5. Solution Approach
5.1. PMIPv6 MAG in the Residential CPE
5.2. PMIPv6 MAG in the Access Gateway
6. IANA Considerations
This document does not require any IANA actions.
7. Security Considerations
This specification identifies the requirements for enabling Community
Wi-Fi Services over Residential architectures and the potential
solution approaches for addressing those requirements. The security
analysis for each of those requirements are covered in those
respective sections.
8. Acknowledgements
TBD
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
9.2. Informative References
[RFC2663] Srisuresh, P. and M. Holdrege, "IP Network Address
Translator (NAT) Terminology and Considerations",
RFC 2663, August 1999.
[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
Gundavelli, et al. Expires September 6, 2012 [Page 8]
Internet-Draft Community Wi-Fi Services March 2012
Mobile IPv6", RFC 5844, May 2010.
[TS23402] 3GPP, "Architecture enhancements for non-3GPP accesses",
2010.
Authors' Addresses
Sri Gundavelli
Cisco
170 West Tasman Drive
San Jose, CA 95134
USA
Email: sgundave@cisco.com
Mark Grayson
Cisco
11 New Square Park
Bedfont Lakes, FELTHAM TW14 8HA
ENGLAND
Email: mgrayson@cisco.com
Pierrick Seite
France Telecom - Orange
4, rue du clos courtel BP 91226
Cesson-Sevigne, 35512
France
Email: pierrick.seite@orange-ftgroup.com
Yiu L. Lee
Comcast
One Comcast Center
Philadelphia, PA 19103
U.S.A.
Email: yiu_lee@cable.comcast.com
URI: http://www.comcast.com
Gundavelli, et al. Expires September 6, 2012 [Page 9]