Revised paragraph in Introduction: Mobile users are, more than ever, consuming Internet content; such traffic imposes new requirements on mobile core networks for data traffic delivery. The presence of content providers closer to the mobile/fixed Internet Service Providers network requires taking into account local Content Delivery Networks (CDNs) while providing mobility services. Moreover, when the traffic demand exceeds available capacity, service providers need to implement new strategies such as selective traffic offload (e.g. 3GPP work items LIPA/SIPTO [TS.23829]) through alternative access networks (e.g. WLAN) [Paper-Mobile.Data.Offloading]. Gateway selection mechanism is also taking the user proximity into account within EPC [TS.29303]. These mechanisms were not pursued in the past owing to charging and billing reasons. However assigning a gateway anchor node from a visited network in roaming scenario has until recently been done and are limited to voice services only. Issues such as charging and billing require solutions beyond the mobility protocol.
H Anthony Chan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of jouni korhonen Sent: Monday, November 12, 2012 3:33 PM To: [email protected] Subject: [DMM] comments on draft-ietf-dmm-requirements-02 Hi, <as an individual contributor and not wearing any hats> In Introduction it says: ".. capacity, service providers need to implement new strategies such as selective traffic offload (e.g. 3GPP work items LIPA/SIPTO [TS.23829]) through alternative access networks (e.g. WLAN) [Paper- Mobile.Data.Offloading]. Moreover, the presence of content providers closer to the mobile/fixed Internet Service Providers network requires taking into account local Content Delivery Networks (CDNs) while providing mobility services." o I would also mention here that the gateway selection mechanism can take the user proximity into account at least within EPC [29.303].. as we are already referencing to 3GPP as an example. o One another aspect I would mention here is the commercial deployment reality. While we have means for selecting and using more optimally located gateways those are not pursued due charging and billing reasons; here I mean that while assigning a gateway anchor node from a visited network while the MN is roaming is not done until recently (and still only limited to voice services). That kind of issues are not solved by a mobility protocol but a different trust and/or billing models between network operators. _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
