1 / 9

IPv6 Deployment Scenarios in 802.16(e) Networks

This draft discusses various deployment scenarios for IPv6 in 802.16(e) networks, including mobile access, point-to-point links, and fixed/nomadic deployment. It covers infrastructure changes, addressing, transport, routing, and mobility considerations.

virginiav
Download Presentation

IPv6 Deployment Scenarios in 802.16(e) Networks

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. IPv6 Deployment Scenarios in 802.16(e) Networksdraft-ietf-v6ops-802-16-deployment-scenarios-01 Myung-Ki Shin, ETRI Youn-Hee Han, KUT Sang-Eon Kim, KT DomagojPremec, Siemens Mobile IETF-67 v6ops WG@ San Diego, CA, USA

  2. Changes since IETF-66 • Sang-Eon (KT) and Domagoj (Siemens) are added as co-authors • Authors discussed about scenarios with 16ng experts • Myung-Ki talked about this draft at 16ng interim (Sep. 12) • Reviewed by three v6ops experts (Jonne, Alain, Jordi) • Scenarios and terms were more clearly defined • Mobile Access Deployment Scenario • Shared IPv6 Prefix Link Model and Point-to-point Link Model • Fixed/Nomadic Deployment Scenario • CS type per scenario was recommended • The following IPv6 impacts were described • IPv6 Related Infrastructure Changes • Addressing • IPv6 Transport • Routing • Mobility, etc.

  3. Mobile Access Deployment • Shared IPv6 Prefix Link Model • All MSs and corresponding interface of AR share the same IPv6 prefix +-----+ | MS1 |<-(16)-+ +-----+ | +-----+ | +-----+ +-----+ +--------+ | MS2 |<-(16)-+----| BS1 |--+->| AR |----| Edge | ISP +-----+ +-----+ | +-----+ | Router +==>Network | +--------+ +-----+ +-----+ | | MS3 |<-(16)-+----| BS2 |--+ +-----+ | +-----+ +-----+ | | MS4 |<-(16)-+ +-----+

  4. Mobile Access Deployment, cont. • Point-to-Point Link Model • Each connection to a mobile node is treated as a single link. +-----+ | MS1 |<-(16)---------+ +-----+ | +-----+ +-----+ +-----+ +--------+ | MS2 |<-(16)------| BS1 |--+->| AR |----| Edge | ISP +-----+ +-----+ | +-----+ | Router +==>Network | +--------+ +-----+ +-----+ | | MS3 |<-(16)------| BS2 |--+ +-----+ +-----+ +-----+ | | MS4 |<-(16)---------+ +-----+

  5. IPv6 Impact • IPv6 Related Infrastructure Changes • MS, AR, ER should be upgraded to IPv6 (BS is L3 unaware) • If the IP aware equipments between the AR and the ER do not support IPv6, the service providers can deploy IPv6-in-IPv4 tunneling to transport IPv6 packets between the AR and the ER. • Addressing • Shared Prefix : Single prefix can be shared for all the attached MSs. • P-to-P : A unique prefix can be allocated to each link.

  6. IPv6 Impact, cont. • IPv6 Transport • Shared Prefix : DAD optimization is required / P-to-P : DAD is easy • IPv6 CS is preferred • Routing • MS is configured with a default route that points to the AR • The AR should support IPv6 routing protocol such as OSPFv3 or IS-IS for IPv6 when connected to the ER with multiple links. Prefix summarization should be done at the ER.

  7. Fixed/Nomadic Deployment • Ethernet like Link Model • Hot zone Deployment (broader than Hot spot) • Wireless DSL (DSL Replacement) +-----+ +---+ +-----+ +-----+ ISP 1 | MS1 |<-(16)+ | | +-->| AR |----| ER1 |===>Network +-----+ | | b| | +-----+ +-----+ +-----+ | +-----+ |E r| | | MS2 |<-(16)+-----| BS1 |-----|t i| | +-----+ +-----+ |h d|--+ | g| | +-----+ +-----+ ISP 2 +-----+ +-----+ | e| +-->| BRAS|----| ER2 |===>Network |MS/GW|<-(16)------| BS2 |-----| | | +-----+ +-----+ +-----+ +-----+ +---+ | | +-----+ +-----+ | | TE |<-(DSL)-----|DSLAM|------------+ +-----+ +-----+ +-----+ |Hosts|<--> +-----+ This network behind MS may exist

  8. IPv6 Impact • IPv6 Related Infrastructure Changes • BRAS provides the functionality of the AR • Ethernet bridge may provide some IPv6 specific functions to increase link efficiency of the 802.16 link (e.g., DAD optimization) • Addressing • Multiple prefixes can be shared to all the attached MSs. • Prefix delegation can be required since networks can exist behind MS • IPv6 Transport • DAD optimization is required • Ethernet CS is preferred • Routing • IPv6 multi-homing considerations exist • If there exist multiple ARs to support MSs, a default router must be selected.

  9. Next Steps • The draft is stable and well-written. • It is ready to go to WGLC.

More Related