1 / 11

Use cases for MAP-T

Use cases for MAP-T. draft-maglione-softwire-map-t-scenarios-01 R. Maglione. Motivations. The purpose of this draft is to describe some use cases that would benefit from a translation based approach The following scenarios are based on IPv4 services currently deployed in Broadband networks.

mrainey
Télécharger la présentation

Use cases for MAP-T

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. Use cases for MAP-T draft-maglione-softwire-map-t-scenarios-01 R. Maglione

  2. Motivations • The purpose of this draft is to describe some use cases that would benefit from a translation based approach • The following scenarios are based on IPv4 services currently deployed in Broadband networks

  3. Use cases Access Control Lists Layer4 Redirection DPI and Cache devices

  4. AAA/RADIUS NAT44 +4V6 4V6 Gateway IPv4-Public BNG IPv4-Private Customer + IPv6 RG IPv6 IPv6 Access Control List • Access Control Lists matching TCP/UDP ports are used to identify different types of traffic • Use Cases/Applications: • to deny/permit specific flows • to define QoS bandwith profile • Per Subscriber Access Control Lists are dinamically applied to a PPP Subscriber Session via AAA/RADIUS interface

  5. AAA/RADIUS NAT44 +4V6 4V6 Gateway IPv4-Public BNG IPv4-Private Customer + IPv6 RG IPv6 IPv6 Access Control List Tunneling New BNG functionality necessary to process IPinIP traffic Requires to wait for vendors to implement new features and to upgrade the BNG Translation ipv6 access-list extended ANTISPAM deny tcp any any eq smtp permit ip any any ipv6 access-list extended VIDEOACL permit tcp any eq 1755 any permit tcp any eq 554 any Works TODAY on IPv6 capable BNG’s with ACL applied via RADIUS interface

  6. Layer 4 Redirection NAT44 +4V6 4V6 Gateway IPv4-Public BNG IPv6 IPv4-Private Customer + IPv6 TCP Server RG IPv6 • Layer 4/HTTP Redirect user’s traffic to SP’s Web Portal • Use Cases/Applications: • to inform the customer about new service offers • to allow the customer to re-charge his account after his credit has expired

  7. Layer 4 Redirection NAT44 +4V6 4V6 Gateway IPv4-Public BNG IPv6 IPv4-Private Customer + IPv6 Server RG TCP IPv6 IPv6 = 2001:beef:<xx.xx.121.20> Port 8094 Translation server-group Provisioning-server server 2001:beef:<xx.xx.121.20> 8094 ! redirect port-list WebPorts to Provisioning-server… Same service configuration for native IPv6 and 4V6 traffic Tunneling Redirection needs to happen at/after 4V6 Gateway IPv4 and IPv6 traffic redirection happen in different locations Change the service and/or architecture Server with IPinIP functionality Change the server

  8. DPI and Cache devices DPI Cache NAT44 +4V6 4V6 Gateway IPv4-Public IPv4-Private Customer + IPv6 BNG RG IPv6 IPv6 • Use Cases/Applications: • DPI devices are used to classify traffic flows based on layer 4-7 identifiers. Classification is needed to provide different treatment for different traffic flows • Cache device are used to save bandwidth • DPI and cache devices are usually located at the edge of the network • DPI and cache devices available today in the market are not able to analyze encapsulated traffic like IPinIP

  9. DPI and Cache devices DPI Cache NAT44 +4V6 4V6 Gateway IPv4-Public IPv4-Private Customer + IPv6 BNG RG IPv6 IPv6 Tunneling New DPI/caching functionalities necessary to inspect IPinIP traffic Requires to wait for vendors to implement new features and to upgrade the DPI/cache devices Inspection/caching of IPv4 traffic needs to happen at/after 4V6 Gateway Change the architecture: separate DPI/cache devices for IPv4 and IPv6 traffic Translation Works on IPv6 capable DPI/cache devices without any change to the architecture No need to add new DPI/cache devices in separate locations

  10. Summary Both encapsulation and translation can provide IPv4 connectivity to customers in an IPv6 only environment However: in some cases translation can reduce operational costs by allowing the Service Provider to re-use currently deployed network architecture for both IPv4 and IPv6

  11. Questions?

More Related