1. Mobility in Content Delivery 79 th IETF Beijing, November 2010 Gyu Myoung Lee (gm.lee@it-sudparis.eu) 1

2. Until now  Device mobility, user mobility, session mobility  Multicast source mobility for future work The PMIP MN may be a multicast source. LMA which is a fixed node for MN can act as RP. SPT can also refreshed in a network-based manner. 2 New item proposal  Content mobility Multicast server handoff Content moving

3. c1 user1 c2 User 1user1 c1 User mobility C1 C1,C2 c2 C1 c1 user1User 1user1 c2 c3 User mobility C1 c2 c3 C1C1,C2 C1,C2,C3 signaling Content from same server (without content mobility) Content mobility (content moving) C: Content Part or whole of content

4. U4 c2 c1 User mobility C1 c2c3 Multicast C1 C2 C2,C3 signaling U3U6U1U4U2U5U3U4U7U3 U4 U4 moves and join another multicast group retrieving the same content U4 moves. No available multicast group for the same content. So continue with unicast session Multicast Unicast G1 G2 G3 G4 C1 c1 Content moving Multicast server handoff Proposal: Content mobility (multicast server handoff, content moving) C: Content G: Multicast Group U: User Distributed multicast sources  Benefits Lower delay, Network resource optimization, Local routing  Challenge Maintaining user’s mobility while changing multicast sources

5. Next Steps  Discussion Is this topic acceptable in the multimob WG for future work?  Plan Develop an I-D on this topic for next meeting 5 Q&A