1 / 12

Q, Sun, C. Xie, and Y. Lee

Deployment Considerations for Lightweight 4over6 draft-sun-softwire-lightweigh-4over6-deployment IETF 83-Paris, March 2012. Q, Sun, C. Xie, and Y. Lee. Lightweight 4over6 Deployment Considerations.

pgriffith
Télécharger la présentation

Q, Sun, C. Xie, and Y. Lee

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. Deployment Considerations for Lightweight 4over6draft-sun-softwire-lightweigh-4over6-deploymentIETF 83-Paris, March 2012 Q, Sun, C. Xie, and Y. Lee

  2. Lightweight 4over6 Deployment Considerations • Based on preliminary experimental deployment, this work describes various deployment models of Lightweight 4over6 and operational considerations for lightweight 4over6.

  3. Case Studies • Case 1: Standalone Deployment Scenario DHCPv6 RFC6334 Host Host Initiator Concentrator Host IPv4-in-IPv6 Tunnel

  4. Case Studies (Cont’d) • Case 2: Integrated Network Element with Lightweight 4over6 and DS-Lite AFTR Scenario • Option1: Separated tunnel instances with different virtual addresses for DS-Lite and lw4over6 4over6: changsha.lw4over6.aftr ds-lite: changsha.dslite.aftr DHCPv6 Host RFC6334 Initiator Concentrator /DS-Lite Host Host B4 IPv4-in-IPv6 Tunnel • Requirement: Initiator and B4 can be distinguished in one network and different FQDNs should be configured accordingly.

  5. Case Studies (Cont’d) • Case 2: Integrated Network Element with Lightweight 4over6 and DS-Lite AFTR Scenario • Option2: Separated tunnel instances for DS-Lite and lw4over6 with the same tunnel address 4over6: changsha.aftr ds-lite: changsha.aftr DHCPv6 4over6: {src addr: 202.112.0.32/24} ds-lite: {src addr: 192.0.0.0/29} Host RFC6334 Initiator Host Concentrator /DS-Lite Host B4 v6 v4 payload IPv4-in-IPv6 Tunnel • Requirement: The network element need to examine every packet on its source IPv4 address.

  6. Case Studies (Cont’d) • Case 3: DS-Lite Coexistent scenario with separated AFTRs 4over6: changsha.lw4over6.aftr ds-lite: changsha.dslite.aftr DHCPv6 Host RFC6334 Initiator Concentrator Host Host B4 DS-Lite • Requirement: Initiator and B4 can be distinguished in one network and different FQDNs should be configured accordingly.

  7. Overall Deployment Considerations • Addressing and Routing • In Lightweight 4over6, there is no inter-dependency between IPv4 and IPv6 addressing schemes. • Port-set Management • This port-set assignment should be synchronized between port management server and the Concentrator. • Concentrator Discovery • Initiator can use the same DHCPv6 option [RFC6334] to discover the FQDN of the Concentrator.

  8. Concentrator Deployment Consideration • Lightweight 4over6 and DS-Lite share similar deployment considerations. • Interface consideration • MTU • Fragment • Lawful Intercept Considerations • Blacklisting a shared IPv4 Address • AFTR's Policies • … • Refer to [I-D.ietf-softwire-dslite-deployment]

  9. Concentrator Deployment Consideration(Cont’d) • Logging at the Concentrator • Operators only log one entry per subscriber • The log should include subscriber’s IPv6 address used for the softwire, the public IPv4 address and the port-set • Reliability Considerations of Concentrator • The backup Concentrator must either have the subscriber mapping already provisioned • or notify the Initiator to create a new mapping in the backup Concentrator.

  10. Concentrator Deployment Consideration(Cont’d) • Placement of AFTR • In the "centralized model", the Concentrator could be located at the higher place. It is cost-effective and easy to manage. • In the "distributed model", Concentrator is usually integrated with the BRAS/SR. • Port set algorithm consideration • Contiguous port range may introduce security risk because hackers can make a more predictable guess of what port a subscriber may use. • Non-continuous port set algorithms can be used to improve security.

  11. Test Result • It has good scalability, supporting more than one hundred million concurrent sessions on a normal PC. • Lightweight 4over6 can be deployed rapidly, with little impact on existing addressing and routing. • It is simple to achieve traffic logging. • Lightweight 4over6 can support a majority of current IPv4 applications. • Lightweight 4over6 can be coexistent with DS-Lite easily.

  12. Conclusion and Next Steps • We have deployed it in Hunan province, China. Our test result: • It is simple and can be deployed rapidly. • It has good scalability. • It can support a majority of current IPv4 applications. • It can be coexistent with DS-Lite easily. • Adopt the document as WG item?

More Related