14
1 NetLMM Vidya Narayanan [email protected] Jonne Soininen [email protected]

1 NetLMM Vidya Narayanan [email protected]@qualcomm.com Jonne Soininen [email protected]@nsn.com

Embed Size (px)

Citation preview

Page 2: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

2

Agenda

• WG DRAFT DISCUSSIONS (ca. 1h)– Proxy Mobile IPv6 (draft-ietf-netlmm-proxymip6-11.txt)– IPv4 Support for Proxy Mobile IPv6 (draft-ietf-netlmm-pmip6-ipv4-

support-02.txt)– Interface between a Proxy MIPv6 Mobility Access Gateway and a

Mobile Node (draft-ietf-netlmm-mn-ar-if-03.txt)

• RECHARTERING– The priorities for the next 12 months

• Discussion on what items have to be done first

– Other rechartering considerations

• NEXT STEPS and WRAP UP

Page 3: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

3

Rechartering Discussions

• Discuss charter principles that need any updates• Decide on the work items to be taken up for the next 12

months• Discuss scope of each item to be included and explicitly

decide what is in and out of scope• Discuss items that may need to be dealt with outside the

WG– e.g., SDO-specific informational documents– Work in other WGs with cross review by NETLMM, etc.

Page 4: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

4

Focusing the discussion

• We are discussing about timing

• We are not discussing if a single work item is important or not– Assume all items to be important

• Concentrate on the question “What has to be done first?”

Page 5: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

5

Charter Principles – A Recap• Local mobility management protocol that does not involve changing

the MN– LMM protocols that affect the MN have already been defined

• Independent of global mobility management protocols– Can be layered under any GMM protocol

• Link layer agnostic – General IETF philosophy– Protocol can be used over heterogeneous link layers– Link layer specific handover indications may be used

• Not designed for inter-interface handover on MNs– Such handoffs not involving the IP stack on MNs is not within IETF

scope (can already be handled with the base protocol)– Affecting the MN IP stack is a specific non-goal

• IETF has developed other mobility protocols with MN involvement

Page 6: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

6

Question on Principles

• Let’s do a pragmatic discussion on what has to be done

• Let’s discuss the principles only if they have to be discussed– If we’re about to take a work item that calls for

principle discussion

Page 7: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

7

Candidates for the New Charter (1/5)

• LMA Discovery Dynamic discovery of a suitable LMA for an MN Multiple LMA connectivity from a MAG

• AAA extensions MAG-AAA and LMA-AAA interfaces RADIUS and Diameter support to:

Allow MAG/LMA to obtain the MN policy profile AAA server may provide configuration information such as

the home network prefix, etc.

Set up a mutually authenticated channel between MAG and LMA

Page 8: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

8

Candidates for the New Charter (2/5)

• GRE Extensions to PMIPv6 Enable MNs from overlapping IPv4 address

spaces to coexist under a given LMA

• Binding Revocation LMA initiated revocation of PMIP binding to

cleanup MAG state and force detachment of MN

• MAG-LMA Heartbeats Keepalive messages to detect failure at either end

Page 9: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

9

Candidates for the New Charter (3/5)• Interactions with MIP6

Scenario A: PMIP6 as local mobility protocol; MIP6 as global mobility protocol (hierarchical system)

Scenario B: Supporting MIP6 and PMIP6 in the same domain

Scenario C: PMIP6 support on MIP6 home link (extending the MIP6 home link to have the HoA be the PMIP6 IP address of the MN)

• Interactions with MIP4 Transitions between PMIP6 and MIP4 Handling MIP4 FAs with MAGs and ARs

Page 10: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

10

Candidates for the New Charter (4/5)• Multihoming

Multihoming scenarios Supporting multiple interfaces with PMIP6 Handovers across various interfaces

• Handover optimizations FMIP support for PMIP6 (taken up by MIPSHOP?) Context transfer between MAGs (taken up by MIPSHOP?) Forwarding ingress traffic from a different MAG

Relation to multiple CoA registrations? Transient CoA or secondary binding

Inter-technology handoffs using PMIP6

Page 11: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

11

Candidates for the New Charter (5/5)• NEMO and PMIP6

Supporting a prefix on the ingress interface of the MN Re-use of the PMIP6 prefix on the egress interface of the MN

vs. new ingress prefix

• Route optimization for PMIP6 Intra-MAG RO Inter-MAG, intra-LMA RO Inter-LMA RO

Page 12: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

12

OK, what should be done first?

• Pick work for the next 12 months• Please, be realistic

– We are not going to get 20 items in a year– Things don’t always go in parallel

• So, think around 4 (+/-1) items

Page 13: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

13

Input from some of our friends

• 3GPP– draft-korhonen-dime-pmip6– draft-muhanna-mip6-binding-revocation– draft-muhanna-netlmm-grekey-option– draft-giaretta-netlmm-mip-interactions

• 3GPP2– Nothing outside pmip6 and IPv4 support

• Wimax Forum– ?

Page 14: 1 NetLMM Vidya Narayanan vidyan@qualcomm.comvidyan@qualcomm.com Jonne Soininen jonne.soininen@nsn.comjonne.soininen@nsn.com

14

Discussion