70 likes | 199 Views
November 2005 at IETF-64 Jari.Arkko@ericsson.com Christian.Vogt@tm.uka.de Wassim.Haddad@ericsson.com. Efficient Route Optimization via CBAs and CGAs draft-arkko-mipshop-cga-cba-02.txt. Provide improved efficiency and security Still keep everything infrastructureless
E N D
November 2005 at IETF-64 Jari.Arkko@ericsson.com Christian.Vogt@tm.uka.de Wassim.Haddad@ericsson.com Efficient Route Optimizationvia CBAs and CGAsdraft-arkko-mipshop-cga-cba-02.txt
Provide improved efficiency and security Still keep everything infrastructureless Cryptographically Generated Addresses (CGAs)for secure, fast, and infrastructure-less authentication Credit-Based Authorization (CBA) for concurrent care-of address tests (no additional handoff delay) Goals and “Ingredients”
HoTI HoTI CoTI HoT HoT CoT BU + PubKey + Sig + BAD BA + {SharedKey} + BAD The Initial Exchange Standard correspondent registration procedure With additional options for 1. Capability negotiation 2. CGA verification of home a. 3. Session key establishment Handover Result: Semi-permanent security association (good for max 24 h)
BU + CTI + BAD BA + CKGT + BAD BU + BAD BA + BAD Subsequent Exchanges Are Faster Concurrent CoA test Handover Early CoA registration Credit-Based Authorization Traffic starts here Full CoA registration
News in -02 • Extended sequence numbers not needed • If you run out of numbers, it is easy to establish new session key • Multiple CGA Parameters options concatenated to meet RFC 3775 length limits • Some text simplifications • Other news: CBA is in use in HIP-MM
Issues for Discussion • Concurrent CoA test currently realized through BU/BA options • Makes proactive handoffs difficult: • Not possible to doearly CoA registration on the old link, and CoA test + full CoA registration on the new link • Especially useful for multi-interface mobile nodes • Alternative: Standard CoTI/CoT messages Higher flexibility, but more overhead
Next Steps • We feel that the draft is technically fairly stable • Hopefully part of this WG