1 / 7

Multiple Provisioning Domain (MPVD) Architecture status & next steps

Multiple Provisioning Domain (MPVD) Architecture status & next steps. Dmitry Anipko (architecture document editor) IETF 89 MIF WG London, March 6 th 2014. MPVD architecture updates and re-cap. - - - - - - - - - - - - - - - - - | | | |

siran
Download Presentation

Multiple Provisioning Domain (MPVD) Architecture status & next steps

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Multiple Provisioning Domain (MPVD) Architecturestatus & next steps Dmitry Anipko (architecture document editor) IETF 89 MIF WG London, March 6th2014 draft-ietf-mif-mpvd-arch-00

  2. MPVD architecture updates and re-cap - - - - - - - - - - - - - - - - - | | | | | PVD1, PVD2 | | No explicit PVD | | | | | - - - - - - - - - - - - - - - - - | | | Wi-Fi | Cellular | | -------------------------- | MPVD aware host | | | | PVD1EX, PVD2EX, PVD3IM | -------------------------- • After the MIF re-charter, Multiple Provisioning Domain architecture draft adopted and published asdraft-ietf-mif-mpvd-arch-00 on Feb 02, 2014 PVD := (PREF, DNSSUF, DNSIP, PROXY, ...) PVDs can be explicit or implicit PVD used by hosts to separate configurations and select appropriate PVD(s) by: policy / user choice / probing 3 API support levels for apps: basic, intermediate, advanced draft-ietf-mif-mpvd-arch-00

  3. Path to WGLC • Goal – identify areas (if any), where more work needed • Tool – validation of the architecture in well-understood reference scenarios: • What are the representative network topologies / scenarios • What are the PVD element values and number of PVDs • What specific host behavior changed • Are all architecture pieces in place to propagate PVD info • Does the PVD elements and identifier definition meet scenarios functional needs • How are the security requirements met Collected based on MIF/DT discussions. Maps to -00 empty section 4. Other topics? Particular proposals in this deck – to help start a discussion. • Each topic – 1) Does it need more work? 2) If yes, does that work belong to the arch doc or other docs? draft-ietf-mif-mpvd-arch-00

  4. Homenet / one ISP - # of PVDs, their elements • 1 PVD – Internet PVD1 := PREF=GUA1/64, DNS=ISP, DNSSUF=homenet1.isp.com, (or separated private and guest with different /64) • 2 PVDs –Internet + Local network (ULA, UE assigned) PVD2 := ULA/64, DNS=UE, DNSSUF=? • 3 PVDs: ISP Internet, Private, Guest PVD2 :=PREF=GUA2/64, DNS=CPE, DNSSUF=private.homenet1.isp.com PVD3 :=…., DNSSUF=guest.homenet1.isp.com Second ISP: add PVDX – ISP2 Internet ISP | ------------------------------- | CPE/UE | ------------------------------- | SSID_HOME | SSID_GUEST | | PVD1, PVD2, | PVD1, PVD2 | | | | ------------------------------- Wi-Fi | | Wi-Fi ------------------ ------------------ | MPVD-aware host | | MPVD-aware host | | PVD1, PVD2 | | PVD1, PVD2 | ------------------ ------------------ draft-ietf-mif-mpvd-arch-00

  5. Homenet / one ISP – ID, integrity check Use for access control? List of networks Does PVD ID need human-friendly representation / label for hosts UI? Machine-friendly form for special app connectivity / match by policy? How is PVD propagated from ISP to the UE? What protocol? Is replay protection for PVD authentication needed? Is it implementable? (how?) draft-ietf-mif-mpvd-arch-00

  6. Public network / multiple SPs PVD1 – Internet PVD2 – MO w/g for video calling and streaming Do the propagation/ID/security answers still hold? ISP1 MO2 | | ---------------------- | AP | ---------------------- | SSID_TRAIN | | PVD1, PVD2 | | | ----------------------- Wi-Fi | ------------------ | MPVD-aware host | | PVD1, PVD2 | ------------------ draft-ietf-mif-mpvd-arch-00

  7. Comments / volunteers ?Mail list is mif@ietf.org, see https://www.ietf.org/mailman/listinfo/mif draft-ietf-mif-mpvd-arch-00

More Related