hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.2 Technical Requirements Summary | Two network components are involved in the end-to-end DS-Lite communication, the AFTR and the CPE. Considerations for the definition of requirements for the AFTR and the network itself are listed below. A detailed analysis of CPE requirements is following from clause 10.1.9. |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.2.1 AFTR | The AFTR is the LSN device that is placed at the edge of the network (IPE connected to the internal MPLS PE/LER) as the IPv6/IPv4 gateway. For egress packets, the AFTR performs de-capsulation from a 4in6 packet to a IPv4 packet while translating ports and address. Requirement considerations for AFTR deployment are: • H... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.2.2 Core Network, Access Aggregation and Internet | For the purposes of the present document, the network is assumed to be composed of a Core Network, Access Aggregation and Internet. The Core Network is the central BGP or/and MPLS network edge-to-edge to the peering points. Access Aggregation is the portion of the network between the internal PE and the CMTS IP side. W... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.3 Technical Definition | DS-Lite uses IPv6-only links between the provider and the customer to carry IPv4 privately addressed packets. The DS-Lite home gateway (CPE) is provisioned with only an IPv6 address on its WAN interface. At the LAN-side interface, the CPE operates its own DHCP server handing out RFC 1918 private IPv4 addresses [i.23] t... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.4 AFTR Hardware Features/Topology | • Role / Location In some cases the AFTR performs the role of a 6PE. The AFTR should be placed at the network edge as close to the external peering points as possible. In case the network realm has multiple exit points, a balanced path should be implemented to all exit points (AFTR nodes will only be added based on cap... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.5 AFTR DS-Lite Specific Software Requirements | • Tunnel Identifiers / Client-Customer ID For data retention purposes, tunnel identifiers should be uniquely associated with a single CPE. • DS-Lite Timers Timers have to be configurable. Default values are defined in [i.46]. • Softwire Initialization (DS-Lite Timers Extended) Quick drop quick pickup approach is prefer... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.6 Integrated Topology/Transport Requirements | The following list of features has to be supported by the DS-Lite architecture for both IPv4 and IPv6 / L2 and L3 in an integrated topology solution. Features marked with an asterisk (*) are topology dependent. Generally, all forwarding functionality should be implemented in hardware to prevent performance issues. Howe... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.7 Feature Development Requirements | Table 3 presents features that have been identified to be in development aiming at enhancement of the AFTR capabilities. They are generalized and more analysis needs to be done to validate their scope and their necessity for deployment. ETSI ETSI TR 101 569 V1.1.1 (2012-12) 54 Table 3: AFTR features under development F... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.8 Performance Requirements and Comparison | Table 4: Downstream throughput example measurement for an MSO Country A B C D E F G H I J Hub Site1 27 036 296 89 42 1 841 473 136 88 18 34 Site2 37 645 364 97 42 1 982 576 140 143 23 33 Site3 17 235 239 50 34 1 176 303 113 65 11 17 Site4 10 918 100 31 13 757 210 49 33 4 17 Site5 2 066 231 65 31 1 394 452 119 98 5 22 S... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.9 DS-Lite CPE Requirements | DS-Lite is used to provide end-to-end IPv4 connectivity across an IPv6 network. The CPE Router is enabled to establish IPv4 connectivity to remote servers even if the access network is IPv6 only; and the CPE Router is not provisioned with a public IPv4 address. Since the encapsulation functions are performed in the CPE... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.9.1 Feature Synopsis for DS-Lite in the Access Network | Requirements on the host are determined by the available connectivity in the Home Network. The Home Network may be dual stack or IPv4 only or IPv6 only. In the case that IPv4 is used, the Home Network has to support private addressing [i.23]. The following requirements apply to the CPE Router: • WAN interface facing th... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.9.2 Feature Development Requirements | Additional functionality to allow UPnP NAT Traversal and static port allocations to function correctly require the use of the Port Control Protocol (PCP). Additional development on the CPE Router is required to allow the customer to configure these features or to pass UPnP/PMP messages from the hosts to the AFTR. |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.9.3 Software and Hardware Requirements | All DS-Lite packets that traverse the CMTS are IPv6. The CMTS should therefore support native IPv6 connectivity on the Access Network. There are no additional specific requirements on the CMTS to support DS-Lite. DS-Lite requires additional processing on the CPE Router to encapsulate / decapsulate the IPv6 packets. To ... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.1.9.4 Performance Requirements and Comparison | The DS-Lite B4 functionality should not introduce any degradation in performance from a native IPv4 connection. There is a significant amount of additional processing required on the CPE to encapsulate and decapsulate the IPv4 packets. This will introduce additional latency in the end-to-end communication. The B4 funct... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.2 NAT64 | |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.2.1 Technical Summary | Global IPv4 address space is currently projected to be depleted around the middle of 2012 to 2015 for most MSOs. As part of the resulting rollout of IPv6 in worldwide networks, specific measures should be taken to allow a smooth transition and coexistence between IPv4 and IPv6. NAT64 is one of the technologies the curr... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.2.2 Technical Definition | NAT64 uses IPv6-only links between the provider and the customer to carry IPv6 or IPv4 packets. The home gateway (CPE) is provisioned with only an IPv6 address on its WAN-side interface. At the LAN-side interface, the CPE operates its own DHCP server, handing out IPv6 addresses to home devices. The CPE performs native ... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.2.3 Feature Synopsis | NAT64 features are based mainly on software requirements. As there is no specific CPE in a NAT64 architecture, the intelligence has to come from either client or a separate entity to provide separation between ordinary IPv6 native traffic and NAT64 traffic. This is achieved through DNS initialization and features that ... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.2.3.1 NAT64 Hardware Features/Topology | • Role / location In some cases the NAT64 device performs the role of a 6PE or a 6VPE. In this case, the NAT64 device is placed at the network edge as close to the external peering points as possible. If the operator's topology includes multiple exit points, a balanced path should be implemented to all exit points (NAT... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.2.3.2 NAT64 Specific Software Requirements | • Client-Customer ID For data retention purposes, tunnel identifiers should be uniquely associated with a single CPE. • NAT Timers The appropriate timers should be implemented to ensure proper operation of UDP, TCP, ICMP. • Softwire Initialization (NAT64 Timers Extended) Quick drop quick pick-up approach is preferred. ... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.2.4 Performance Requirements and Comparison | NAT64 performance evaluated against lowest acceptable benchmarks and the actual delivery of throughput, convergence, failover and latency for all aspects and features within the chassis. All performance requirements are based on peak capacity and average throughput which are considered for the capacity the platform is ... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.2.5 Development and Deployment Status | Product solutions for NAT64/DNS64 are widely available. But deployments are limited due to the fact that the technology is only applicable to IPv6-only devices. There are a number of applications which do not operate via DNS which further limits the applicability of NAT64/DNS64. |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.2.6 Failings/Issues of NAT64 | There is a number of well-known issues with NAT64 which present topics for further development. • The main issue with this technology is the fact that it does not operate on IPv4-only devices and that applications need to run via DNS. Applications like P2P do not consult the DNS and, thus, fail to operate since the NAT... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.2.7 Summary Assessment | NAT64 is less preferred as transition technology as only DNS based application will work at present. The CPE requirements, however, are limited. The only indispensable requirement is the support of IPv6. The NAT64 device itself, if deployed centrally, does not represent a major investment. Example figures indicate the ... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.3 Teredo | Although Teredo is not a transition technology for deployment from an MSO's point of view but the industry might be forced into considering its effects on its own transition technologies and native IPv6 deployment and thus in this clause we analyse the technology. There have been examples recently of customers bypassin... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.3.1 Technical Summary | Teredo is a transition technology that gives full IPv6 connectivity for IPv6-capable hosts which have no direct native connection to an IPv6 network. Compared to other similar technologies Teredo's distinguishing feature is that it is able to perform its function even from behind Network Address Translation (NAT) devic... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.3.2 Technical Requirements Summary | Two network components are involved in the end-to-end Teredo communication, the Teredo client and the Teredo relay. A Teredo relay is a device that is placed at the edge of the network (IPE connected to the internal MPLS PE/LER) as the IPv6/IPv4 gateway to perform Teredo tunnel termination and IPv6 forwarding. Requirem... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.3.3 Technical Definition | Teredo uses IPv4-only links between the provider and the customer to carry IPv6 over IPv4. The home gateway (CPE) is provisioned with only an IPv4 address on its WAN interface. At the LAN-side interface, the CPE operates its own DHCP server, handing out IPv4 addresses to home devices. The CPE performs native IPv4 packe... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.3.4 Performance Requirements and Comparison | Teredo performance is evaluated against lowest acceptable benchmarks and the actual delivery of throughput, convergence, failover and latency for all aspects and features within the chassis. All performance requirements are based on peak capacity and average throughput which are considered for the capacity the platform... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.3.5 Development and Deployment Status | Teredo is a solution that is specifically implemented for integration into the Microsoft Windows Operating System. It is not widely adopted in devices beyond those running this Operating System. ETSI ETSI TR 101 569 V1.1.1 (2012-12) 73 |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.3.6 Failings/Issues of Teredo | There is a number of well-known issues with Teredo which present topics for further development. • The main issue with this technology is the fact that it does not mitigate the depletion of IPv4 addresses and does not provide native IPv6 forwarding. As such, this technology can support fast IPv6 introduction but operat... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.3.7 Summary Assessment | Teredo is a transition technology that supports fast IPv6 introduction. It does not require any update of the CPEs. The Teredo relay and Teredo server do not have a high cost. As such, Teredo can be considered a simple and low-cost transition mechanism. The main weakness of Teredo is its reliance on ICMPv6. When traver... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.4 dIVI | |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.4.1 Technical Summary | dIVI is a 4464 solution focusing on the CPE to enforce the transitional functionality. Its concepts are in part reused and enhanced by the future MAP-T/E technologies. It is a stateless IPv6 transition technology. Dual IVI (dIVI) enables a service provider to offer IPv4 services to IPv6 enabled hosts. This approach uti... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.4.2 Address Family Translation (AFT) | Address Family Translation (AFT) refers to the mapping of an IP address from one address family to another IP address from another address family, for instance mapping an IPv4 address into an IPv6 address or vice versa. This translation is sometimes denoted as NAT46 (when the initiator is on the IPv4 side) or NAT64 (wh... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.4.3 Technical Definition | There is a significant difference between stateful NAT464 and stateless NAT464 also called dIVI or dIVI-pd if prefix delegation is required. dIVI-pd is used by A+P to share an IPv4 public address among multiple users/CPE without the help of NAT or double NAT. Stateless NAT464 (dIVI, dIVI-pd) is intended to enable netwo... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.4.4 dIVI Hardware Features/Topology | • Role/Location In some cases the AFT device performs the role of a 6PE. The AFT device should be placed at the network edge as close to the external peering points as possible. In case the network realm has multiple exit points, a balanced path should be implemented to all exit points. In case the AFT device does not ... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.4.5 AFTR dIVI Specific Software Requirements | • Tunnel Identifiers / Client-Customer ID For data retention purposes, tunnel identifiers should be uniquely associated with a single CPE. • dIVI Timers Timers have to be configurable. • Softwire Initialization (dIVI Timers Extended) Quick drop quick pickup approach is preferred. • Port Block Allocation per IP Address ... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.4.6 Feature Development Requirements | Table 7 presents features that have been identified to be in development aiming at enhancement of the AFTR capabilities. They are generalized and more analysis needs to be done to validate their scope and their necessity for deployment. Table 7: dIVI features under development FEATURE DESCRIPTION IPv6 Filtering IPv6 fi... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.4.7 Performance Requirements and Comparison | The AFTR performance is evaluated against lowest acceptable benchmarks and the actual delivery of throughput, convergence, failover and latency for all aspects and features within the chassis. All performance requirements are based on peak capacity and average throughput which are considered for the capacity the platfo... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.4.8 dIVI CPE Requirements | dIVI is a dual stateless IPv4 / IPv6 translation mechanism. It is an extension of the 1:1 stateless IPv4 / IPv6 translation (IVI) mechanism. dIVI uses IPv4 to IPv6 address mapping at the CPE to translate an IPv4 header into IPv6. This packet is sent across an IPv6 access network to the XLAT / CGN. A translation back fr... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.4.8.1 Feature Synopsis for dIVI in the Access Network | Requirements on the host are determined by the available connectivity in the Home Network. The Home Network may be dual stack or IPv4 only or IPv6 only. In the case that IPv4 is used, the Home Network has to support private addressing [i.23]. The following requirements apply to the CPE Router: • WAN interface facing th... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.4.9 Failings/Issues of dIVI | The main limitation of dIVI is the lack of focus it has received within the IETF. It is an attractive technology for IPv6 transition. Still, the MTU and fragmentation issues remain undefined. The ability to provide static port mapping is limited as the NAT44 functionality on the CPE Router can only utilize the port ran... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 10.5 Technical Comparison | As a result from the analysis above, a technical comparison of the introduced transition technologies takes into account the functionality of the technologies, their applicability for the environment of a Cable Network and the current state of development for vendor products. In Table 8 each transition technology is as... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.1 464XLAT | |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.1.1 Technical Summary | 464XLAT is one of the future transition technologies. The main reason for considering 464XLAT for further analysis is its ability to operate without inter-communication between IPv4 and IPv6. This technology will allow customers to access services natively over IPv6 and through translation over IPv4. As IPv6 is not "ba... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.1.2 Technical Requirements Summary | Two network components are involved in the end-to-end 464XLAT communication, the PLAT and the CPE (CLAT). The PLAT is the LSN device that is placed at the edge of the network (IPE connected to the internal MPLS PE/LER) as the IPv6/IPv4 gateway. For egress packets, the PLAT performs address family translation from an IP... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.1.3 Technical Definition | 464XLAT uses IPv6-only links between the provider and the customer to carry IPv4 privately addressed packets. The 464XLAT home gateway (CPE) is provisioned with only an IPv6 address on its WAN interface. At the LAN-side interface, the CPE operates its own DHCP server handing out RFC 1918 private IPv4 addresses [i.23] t... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.1.4 PLAT Hardware Features/Topology | • Role / Location In some cases the PLAT performs the role of a 6PE or 6VPE. The PLAT should be placed at the network edge as close to the external peering points as possible. In case the network realm has multiple exit points, a balanced path should be implemented to all exit points (PLAT nodes will only be added base... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.1.5 PLAT 464XLAT Specific Software Requirements | • NAT Timers Timers have to be configurable. • Port Block Allocation per IP Address Port block allocation is configurable to allow for any ratio assignment. ETSI ETSI TR 101 569 V1.1.1 (2012-12) 88 • Static / Dynamic Port Allocation (STDPA) 464XLAT requires efficiency and scalability not only with regard to throughput ... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.1.6 Integrated Topology/Transport Requirements | The following list of features has to be supported by the 464XLAT architecture for both IPv4 and IPv6 / L2 and L3 in an integrated topology solution. Features marked with an asterisk (*) are topology dependent. Generally, all forwarding functionality should be implemented in hardware to prevent performance issues. Howe... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.1.7 Failings/Issues of 464XLAT | There is a number of well-known issues with 464XLAT which present topics for further development. • The cost, particularly of the CPE (CLAT), is expected to be increased due to the extension of the required functionality. MSOs that are not deploying WiFi solutions and stick to bridging CPE devices will face the issue o... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.1.8 Summary Assessment | 464XLAT is extremely usable as a transition technology where the biggest concern remaining to be the additional cost of the CPE. The PLAT itself, if deployed centrally, does not represent a major investment. 464XLAT saves on public IPv4 addresses and allows for an IPv6-only Access Network with the potential of reducing... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.2 Stateless DS-Lite | |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.2.1 Technical Summary | Stateless DS-Lite is one of the future transition technologies. The main reason for considering Stateless DS-Lite for further analysis is its ability to operate without inter-communication between IPv4 and IPv6. This technology will allow customers to access services natively over IPv6 and through translation over IPv4... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.2.2 Technical Requirements Summary | Two network components are involved in the end-to-end Stateless DS-Lite communication, the AFTR and the CPE Router (B4). The AFTR is the device that is placed at the edge of the network (IPE connected to the internal MPLS PE/LER) as the IPv6/IPv4 gateway to perform IPv4 decapsulation upstream and IPv4 over IPv6 encapsu... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.2.3 Technical Definition | Stateless DS-Lite uses IPv6-only links between the provider and the customer to carry IPv4 packets. The B4 home gateway (CPE) is provisioned with only an IPv6 address on its WAN interface. At the LAN-side interface, the CPE operates its own DHCP server handing out RFC 1918 private IPv4 addresses [i.23] to home devices.... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.2.4 AFTR Hardware Features/Topology | • Role/Location In some cases the AFTR performs the role of a 6PE or 6VPE. The AFTR should be placed at the network edge as close to the external peering points as possible. In case the network realm has multiple exit points, a balanced path should be implemented to all exit points (AFTR nodes will only be added based ... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.2.5 B4/AFTR Specific Software Requirements | • NAT Timers Timers have to be configurable. • Port Block Allocation per IP Address Port block allocation is configurable to allow for any ratio assignment. • MTU Size / TCP MSS TCP MSS support is mandatory for the B4 due to the removal and end-to-end MTU sizing functionality. This will avoid the need for excessive fra... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.2.6 Failings/Issues of Stateless DS-Lite | There is a number of well-known issues with Stateless DS-Lite which present topics for further development. • Per Flow logging needs to be provided by an external DPI platform. • Users which require to run servers or other traffic sources on well-known ports need special address/port range allocation considerations as ... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.2.7 Summary Assessment | Stateless DS-Lite is usable as a transition technology where the biggest concern appearing to be the cost/complexities of the CPE. The AFTR itself, if deployed centrally, does not represent a major investment. Stateless DS-Lite saves on public IPv4 addresses and allows for an IPv6-only Access Network with the potential... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.3 MAP-T | |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.3.1 Technical Definition | MAP-T uses an IPv4/IPv6 address and port mapping technique as defined in [i.16] to encapsulate the IPv4 address suffix bits and port set ID within the IPv6 prefix. ETSI ETSI TR 101 569 V1.1.1 (2012-12) 97 Figure 17: IPv6 address for MAP address and port mapping Provisioning of the CPE Router requires the following attr... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.3.2 Feature Synopsis of MAP-T | The following requirements apply to the CPE Router: • Native IPv6 on the WAN interface facing the Access Network • Dual stack IPv4 / IPv6 on the LAN interface facing the Home Network • IPv4 to IPv6 header translation in accordance with [i.41] • IPv6 to IPv4 header translation • NAPT44 to translate private IPv4 addresse... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.3.3 Development and Deployment Status | MAP-T is currently in active development and - if adopted by the IETF - is likely to replace dIVI. There are currently no Border Relays or CPE Routers available for deployment. |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.3.4 Summary Assessment | MAP-T provides a good method of dual translation between IPv4 and IPv6. It has benefits over existing technologies since it allows for address sharing as well as fixed IPv4 address assignments. The stateless design adds improvements for scalability and reliability within the service provider network. A MAP-T CPE Router... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.4 MAP-E | |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.4.1 Technical Definition | MAP-E uses an IPv4/IPv6 address and port mapping technique as defined in [i.16] to associate an IPv4 address with an IPv6 address. This allows the automatic creation of tunnels between the Border Relay and the CPE Router. The format of the IPv6 address is the same as for MAP-T and shown in Figure 17. In order to perfor... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.4.2 Feature Synopsis of MAP-E | The following requirements apply to the CPE Router: • Native IPv6 on the WAN interface facing the Access Network • Dual stack IPv4 / IPv6 on the LAN interface facing the Home Network • IPv4 to IPv6 header translation in accordance with [i.41] • IPv6 to IPv4 header translation • NAPT44 to translate private IPv4 addresse... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.4.3 Development and Deployment Status | MAP-E is currently in active development and - if adopted by the IETF - is likely to replace 4RD. There are currently no Border Relays or CPE Routers available for deployment. |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 11.4.4 Summary Assessment | MAP-E provides a good method of dual translation between IPv4 and IPv6. It has benefits over existing technologies since it allows for address sharing as well as fixed IPv4 address assignments. The stateless design adds improvements for scalability and reliability within the service provider network. ETSI ETSI TR 101 5... |
99aa706f8230f5c604e7f0af22e3e90d | 101 569 | 12 Technical Conclusion | The time is rapidly approaching when the last of the IPv4 addresses will be allocated worldwide. Consequently, the Cable Industry has to meet the new challenges in adopting IPv6 into its end-to-end networks including the home networks and end-user equipment. The most immediate investment being made is to transition a C... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 1 Scope | The present document provides an overview of Cloud/virtual services and studies. This includes Lawful Interception (LI) and Retained Data (RD) aspects of these services in the converged Cloud/virtual service environment, the challenges and obstacles of complying with those obligations, what implementations can be achie... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 2 References | |
825197b2b229c1f4310a03df8459b4de | 101 567 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 3 Definitions and abbreviations | |
825197b2b229c1f4310a03df8459b4de | 101 567 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions given in ETSI TR 121 905 [i.15] and the following apply: appliance: self-contained IT system that can be plugged into an existing IT infrastructure to carry out a single purpose application virtualization: virtual implementation of the applic... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 3.2 Abbreviations | For the purposes of the present document, the following terms and definitions given in ETSI TR 121 905 [i.15] and the following apply: AAA Authentication, Authorization, and Audit AMQP Advanced Message Queuing Protocol ANDSF Access Network Discovery and Selection Function ANSDF Access Network Discovery and Selection Fu... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 4 Cloud Services Overview | |
825197b2b229c1f4310a03df8459b4de | 101 567 | 4.1 Introduction | Cloud services are very diverse and constantly evolving. Work is on-going in many different industry standards forums listed in annex B on service conceptualization, reference architectures, infrastructure models and resource management. Many of the service definitions that have achieved a level of stability are includ... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 4.2 Perspectives on Cloud services | |
825197b2b229c1f4310a03df8459b4de | 101 567 | 4.2.1 Introduction | Cloud computing, including distributed virtual services, is an evolving paradigm that is fundamentally and rapid changing communication services and infrastructure. The diversity of these services and the underlying infrastructure has itself produced different perspectives. Enterprises User Cloud Providers (SaaS, PaaS)... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 4.2.2 General characteristics of Cloud services | On-demand self-service: A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider. Broad network access: Capabilities are available over the network and accessed through standard mechanism... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 4.2.3 Service models for Cloud services | Cloud computing enables hardware and software to be delivered as "services" that are provided on demand or sold on a usage basis. The following are common service models, which are defined in detail in clause 3.1: • Communications as a Service (CaaS) • Data as a Service (DaaS) • Infrastructure as a Service (IaaS) • Net... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 4.2.4 Deployment models for Cloud services | Private Cloud: The Cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (e.g. business units). It may be owned, managed and operated by the organization, a third party or some combination of them and it may exist on or off premises. Community Cloud: The Cloud infr... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 4.3 Cloud reference architectures and infrastructures | The Cloud architecture meets several needs to enable sustained innovation and development of Cloud services. With multiple stakeholders involved, the Cloud architecture be flexible to fit the needs of infrastructure C(L)SPs, CSPs and service resellers. The following high-level needs are broadly envisioned for the Cloud... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 4.4 Resource management | Resource management is necessary for maintaining processing, storage and I/O capabilities - physical and virtual - within or across Cloud environments. Cloud infrastructure should provide a unified resource management function for the upper-layers (including virtualized and physical computing resource, storage resource... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 4.5 Enabling Mobile Cloud | The Cloud ecosystem is already taking shape and a number of players from IT, as well as Over-The-Top (OTT) players already offer agility and scalability through their service offerings. The fixed and mobile telecommunications network operators have deployed an extensive infrastructure (distributed data centres, broadba... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 5 Network Virtual Services Overview | |
825197b2b229c1f4310a03df8459b4de | 101 567 | 5.1 Introduction | Virtualized Services, in the present document, refer to the work being studied by ETSI's Network Functions Virtualization Industry Specification Group (NFV ISG). Network Functions Virtualization aims to address operator problems of increasingly complex and proprietary hardware by leveraging standard IT virtualization t... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 5.2 NFV relationship to Cloud Services | There are instances in existing networks where network operators have pooled resources (e.g. MSC Pooling); virtualization and Cloud services use the concept of resource pooling as well. Network virtualization allows new business opportunities similar to Cloud service models. A CSP could offer so or all of its NFV Infra... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 5.3 NFV standardization | The telecommunications industry uses traditional standardization procedures to develop specifications on which prototyping and testing efforts are based. The information technology industry embraces an "open source" model where a community of developers contribute and integrate pieces of software under terms that facil... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 6 Lawful Interception | |
825197b2b229c1f4310a03df8459b4de | 101 567 | 6.1 Introduction | The on-going work in the industry and standards forums dealing with Cloud and virtual services recognize that a broad array of existing legal obligations apply to the services being provided, including lawful interception. This clause describes lawful interception obligations. |
825197b2b229c1f4310a03df8459b4de | 101 567 | 6.2 LEA | |
825197b2b229c1f4310a03df8459b4de | 101 567 | 6.2.1 Identify and communicate with the responsible service providers | The most fundamental need for LEAs is to be able to identify and communicate with the service provider(s) responsible for the communications involving specific targets. Cloud environments are especially challenging because the relevant C(L)SP providers are often not subject to registration, regulatory or CSP partnershi... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 6.2.2 Facilitate access and delivery across different jurisdictions | While the legal and regulatory aspects of multi and cross jurisdictional handovers is out of scope of the present document, the implementation of common structured expressions for the eWarrant and handover information can provide the technical underpinnings for facilitating such implementations. Due to the nomadic acce... |
825197b2b229c1f4310a03df8459b4de | 101 567 | 6.3 CSP / C(L)SP Provider Obligations | |
825197b2b229c1f4310a03df8459b4de | 101 567 | 6.3.1 Overview | CSPs typically have a number of responsibilities which can be roughly summarized into two areas: • Provision and Maintenance of lawful interception capability. • Protection of information and activities pursuant to this responsibility. In accordance to national law, CSPs are still responsible to provide the "access" in... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.