hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.1.2.2 Recommendations | The renderer assumes that the following conditions are met: β’ The screen lies entirely between the Left and Right loudspeakers. β’ For all loudspeaker configurations in table A.1 with num_top > 0, the screen lies entirely between the ceiling and floor loudspeakers (or the floor, if no floor loudspeakers are present). Th... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.1.2.3 Algorithmic details | Pseudocode 1 (object_position_X; object_position_Y; object_position_Z) = screen_scale (object_position_X ,object_position_Y ,object_position_Z ,object_screen_factor ,y_position_exponent ,target_screen_width_ratio ,target_screen_origin_X ,target_screen_height_ratio ,target_screen_origin_Z) { if (object_screen_factor > 0... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.1.3 Zone constraints | |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.1.3.1 Introduction | Zone constraints provide the means of specifying a spatial region to be excluded from rendering an object. They are indicated by the zone_mask and b_enable_elevation metadata items. Zone constraints can reduce the number of available panner targets for the supported loudspeaker configurations that are listed in table A... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.1.3.2 Requirements | The renderer shall modify the output loudspeaker configuration that is sent to the source panner by performing the following steps: β’ For the combination of output_speaker_config and zone_mask value, as listed in table 4, exclude loudspeakers listed in the third column and reduce the num_speakers value as listed in the... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.1.4 Snap | |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.1.4.1 Introduction | The snap metadata indicates whether the position of the object is modified ("snapped") and assigned to the closest among a fixed set of locations. This set of locations is intended to coincide with the panner_target locations for the largest loudspeaker configuration supported by the renderer. A weighted Euclidean dist... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.1.4.2 Requirements | The renderer shall create a list of snap target locations, corresponding to the panner target coordinates in table A.9: β’ snap_target_Xk = panner_target_Xk; β’ snap_target_Yk = panner_target_Yk; and β’ snap_target_Zk = panner_target_Zk; β’ where k β0; num_snap_targets β1. The num_snap_targets value shall be ... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.1.4.3 Algorithmic details | Pseudocode 2 min_dist = Inf; weight_X = 1/16; weight_Y = 4; weight_Z = 32; /* find the closest loudspeaker */ for (j = 0; j < num_speaker; j++) /* for each loudspeaker */ { /* weighted Euclidean distance using Cartesian object * and loudspeaker positions*/ dist = weight_X * pow((object_position_X - snap_target_X(j)), 2... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.1.5 Metadata for future use cases | Some of the metadata specified at the metadata interface is reserved for future use cases. The renderer shall ignore object_priority. The renderer should ignore b_ducking_disabled. The renderer should ignore object_sound_category. The renderer should ignore master_screen_size_ratio. |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2 Source panner | |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.1 Source panner architecture | |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.1.1 Introduction | The source panner consists of the following parallel blocks utilizing different panning algorithms: 1) Speaker-anchored coordinates panner. 2) Divergence panner. 3) Size panner. ETSI ETSI TS 103 448 V1.1.1 (2016-09) 20 4) Point source panner. Figure 3 |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.1.2 Requirements | To choose a panning algorithm, the conditions below shall be evaluated in the following order: 5) If the position of an object is specified by channel, use the speaker-anchored coordinates panner, as specified in clause 5.2.5. 6) If object_divergence > 0, use the divergence panner, as specified in clause 5.2.4. 7) If o... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.2 Rendering point sources | |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.2.1 Introduction | The point panner can create the impression of an auditory event at any point inside the room. It provides a logical extension to the surround sound production tools used today. The point panner calculates a gain coefficient for each active loudspeaker in the output loudspeaker layout, given an object position. ETSI ETS... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.2.2 Requirements | The requirements in this clause apply if β’ the object position is specified by object_position_X, object_position_Y and object_position_Z. β’ object_divergence, object_width, object_width_X, object_width_Y and object_width_Z are not present at the metadata interface, or all their values are 0. Let mdu β0; num_obj_info_... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.2.3 Algorithmic details | The source point panning algorithm consists of a 3D extension of the panner concept that is widely used in 5.1- and 7.1- channel surround sound production. Pseudocode 3 for (mdu = 0; mdu < num_obj_info_blocks; mdu++) /* for each metadata update */ { for (j = 0; j < num_speakers; j++) { panner_gain[mdu][j] = panner_gain... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.3 Rendering objects with size | |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.3.1 Introduction | Objects with size are rendered by the size panner. The size panner calculates a gain coefficient for each active loudspeaker in the output loudspeaker layout, given the position and size of an object. The size of an object is in the range [0; 2,8]. To perform the calculation, the size panner considers virtual positions... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.3.2 Requirements | The requirements in this clause apply if β’ the object position is specified by object_position_X, object_position_Y and object_position_Z. β’ object_divergence is not present at the metadata interface or its value is 0. β’ one of object_width, object_width_X, object_width_Y or object_width_Z is greater than 0. If object_... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.3.3 Algorithmic details | Pseudocode 7 y = size_scale (x) { epsilon = 1e-5; if (x < epsilon) { y = 0; } else if (x <= 0.2) { y = 1.5 * x; } else if (x <= 0.5) { y = 7/3 * x - 1/6; } else if (x <= 0.75) { y = 3.2 * x - 0.6; } else { y = 4 * x - 1.2; } } ETSI ETSI TS 103 448 V1.1.1 (2016-09) 26 Pseudocode 8 y = weight (a, b, c) { if (c > 0) { tmp... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.4 Rendering objects with divergence | |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.4.1 Introduction | Divergence converts one object into two objects, with the following three-dimensional position coordinates: object_position_X Β± object_divergence 2 ; object_position_Y; object_position_Z. These two objects are panned by the divergence panner and the resulting loudspeaker gains are normalized in an energy-preserving w... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.4.2 Requirements | The requirements in this clause apply if β’ the object position is specified by object_position_X, object_position_Y and object_position_Z. β’ object_divergence > 0. ETSI ETSI TS 103 448 V1.1.1 (2016-09) 29 Let j β0; num_speakers β1 and mdu β0; num_obj_info_blocks β1. The source panner shall set object_width_Xmdu =... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.4.3 Algorithmic details | Pseudocode 15 for (mdu = 0; mdu < num_obj_info_blocks; mdu++) /* for each metadata update */ { tmp_div = min(object_divergence[mdu], 1 - abs(object_position_X[mdu] β 0.5) * 2); x1 = object_position_X[mdu] + tmp_div / 2; x2 = object_position_X[mdu] β tmp_div / 2; total = 0; /* scalar multiplication for the vectors panne... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.5 Rendering objects with speaker-anchored coordinates | |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.5.1 Introduction | Speaker-anchored coordinates specify a location in the listening room that is related to the position of a specific loudspeaker. The speaker-anchored coordinates are assigned to a specific loudspeaker and are indicated by a label that specifies a channel corresponding to that loudspeaker. Ideally, the loudspeaker corre... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.2.5.2 Requirements | The requirements in this clause apply if the object position is specified by channel. Let mdu be the metadata update in range 0; num_object_info_blocks β1. Let = . If Lb and Rb are present, as specified in ETSI TS 103 190-2 [1], clause 6.3.2.9.5, 6.3.2.9.8 or 6.3.2.9.9, let ! = ; otherwise, let ! = 1. Let j be in ... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.3 Trim | |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.3.1 Introduction | Trim can be used to lower the level of out-of-screen elements that are included in the mix. This can be desirable when immersive mixes are reproduced in layouts with few loudspeakers (for example, stereo, 5.1- or 7.1-channel). Trim can preserve intelligibility of on-screen located objects and can avoid the effect of an... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.3.2 Requirements | Based on the num_top and num_mid values for the set output_speaker_config specified in table A.1, the renderer shall set trim_cfg, as specified in table 7. If the position metadata is specified by object_position_X, object_position_Y and object_position_Z, the trim_gain shall be calculated as follows: β’ If trim_modetr... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.3.3 Algorithmic details | Pseudocode 16 start_effect_Y = 0.0; full_effect_Y = 0.6; start_effect_Z = 0.2; full_effect_Z = 1.0; max_trim = min(0, - 4.5 + 3 * min (1, num_mid / 4) + 1.5 * min(1, num_top / 4); for (mdu = 0; mdu < num_obj_info_blocks; mdu++) { gY = clamp((object_position_Y[mdu] - start_effect_Y) / (full_effect_Y - start_effect_Y)); ... |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.4 Gain mixer | |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.4.1 Introduction | The gain mixer creates speaker gain values by combining gain values calculated by the source panner with the trim gain values and the custom gain values. The resulting loudspeaker gain values are input to the ramp mixer. |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.4.2 Requirements | If b_object_not_active is true, the renderer shall set object_gain = ββ. The renderer shall calculate the speaker gain values as specified in Pseudocode 18. |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.4.3 Algorithmic details | Pseudocode 18 for (mdu= 0; mdu < num_obj_info_blocks; mdu++) { for (j = 0; j < num_speakers; j++) { speaker_gain[mdu][j] = panner_gain[mdu][j] * trim_gain[mdu] * db_to_linear(object_gain[mdu]); } } |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.5 Ramp mixer | |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.5.1 Introduction | The ramp mixer creates output loudspeaker feeds y[j] from the object audio essence, attenuated with speaker_gain[j] values calculated in clause 5.2.2.3. The effective mixing gains mix_gain[j] crossfade to the speaker_gain[j] values over a period of time specified by ramp_duration. |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.5.2 Requirements | The renderer shall calculate start_smp[mdu] = sample_offset + block_offset_factor[mdu] Γ 32 for each incoming metadata update mdu β[0; num_obj_info_blocks β1]. The renderer shall calculate loudspeaker feeds y(j) as specified in Pseudocode 19. |
b5b05b02fba36b97227fe9de42765664 | 103 448 | 5.5.3 Algorithmic details | Pseudocode 19 mdu = 0; for (smp = 0; smp < frame_size; smp++) { /* check for new metadata update starting at the current sample */ if (smp == start_smp[mdu]) { /* set new ramp duration */ ramp_dur = ramp_duration[mdu]; remain_ramp_dur = ramp_dur; /* calculate new ramp delta values */ for (j = 0; j < num_speakers; j++) ... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 1 Scope | The present document presents the engineering and operational requirements for the application of the IPv6 transition technology 6RD as defined by ETSI TS 101 569-1 [1] (IPv6 Transition Requirements) implemented within an integrated broadband cable network end to end across its network domains. The present document is ... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 2 References | |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 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... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 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... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 3 Definitions and abbreviations | |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: 4in6: encapsulation of IPv4 packets within IPv6 packet format NAT44: network address translation from an IPv4 address to another IPv4 address P Router: label switching router acting as a transit router in the core network of an MPLS ne... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 6PE IPv6 Provider Edge 6RD IPv6 Rapid Deployment 6VPE IPv6 VPN Provider Edge AAA Authentication, Authorization and Accounting ALG Application Layer Gateway AMPS Amplifiers AS Autonomous System ASCII American Standard Code for Information Inter... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 4 General Considerations | |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 4.1 Background | The present document is part of a series of ETSI technical specifications specifying requirements to engineer and operate the 6RD transition technology end to end across a cable operator's network. Its implementation would ensure the network provider can continue to provide business continuity throughout the depletion ... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 4.2 General Overview | An objective of deploying the IPv6 transition technology is to provide a seamless experience to users accessing IPv6 network services through IPv4 only networks and to enable current and new content to be delivered seamlessly to IPv6 users by encapsulating the IPv6 to IPv4 (6RD). It should be noted that Cable broadband... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 4.3 Vendor Considerations | 6RD was the easiest delivery of IPv6 transition technologies introduced to the industry, it was the earliest primary technology to be exposed to the market. Many off-the-shelf vendors and network vendors supported the concept from an early stage. Many vendor supported, and still do today, 6RD as a mechanism within thei... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 5 Gap Analysis | |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 5.1 Consideration | The engineering and operational requirements applying ETSI TS 101 569-1 [1] need to be specified with the following design objective to define the logical and physical parameters to allow for customers to access the public IP Internet across an IPv6 network using 6RD. |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 5.2 Overview | 6RD is defined in IETF RFC 5969 [17] and it is one of the incremental methods for deploying IPv6. IPv6 native traffic is tunnelled over IPv4 access network. The IPv4 tunnel end points are the RG/CPE and the Border Router. These two elements perform encapsulation/decapsulation of IPv6-in-IPv4 traffic. BR is placed at IP... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 6 Domain Functionality | |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 6.1 End to End Network Domains | In order to operate the IPv6 transition technology is has to be engineered and verified end to end across the cable broadband network addressing each of the domains as illustrated in figure 2. Figure 2: Illustration of the Cable Broadband Network Domains |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 6.2 CPE Home Network Domain | 6RD enables a customer's device that is V6 to be supported across the Cable network when communicating to a V6 service across an IPv4 cable network. A device that is V4 only can communicate natively with a V4 service without the use of the 6RD-CE and 6RD-BR resources. Functionality to be engineered in the cable network... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 6.3 Access Network Domain | Functionality to be engineered in the cable network: β’ The cable headend CMTS shall be capable of IPv6 connectivity for customer traffic. β’ The DOCSIS management between the Cable Modem and CMTS would be IPv4. NOTE: There are no additional requirements on the HFC distribution network i.e. AMPS, taps, etc. |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 6.4 Core Network Domain | Functionality required: β’ The core network routers shall support IPv4 routing and forwarding capabilities. β’ 6RD-BR shall be implemented as specified by IETF RFC 5969 [17]. Operation: A v4 client communicating with v4 service has direct native end to end connectivity and does not utilize the 6RD resources, however a v6... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 6.5 Data Centre Domain | Functionality to be engineered in the cable network: There are no changes to be engineered when considering 6RD as the network elements remain supporting IPv4 thus there are no additions engineered within the cable network elements. |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 6.6 DMZ Service Domain | Functionality to be engineered in the cable network: There are no changes to be engineered when considering 6RD as the network elements remain supporting IPv4 thus there are no additions engineered within the cable network elements. |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 6.7 Transit and Peering Service Domain | Functionality to be engineered in the cable network: There are no changes to be engineered when considering the transit and peering domain since the transmit and peering links are dual stack and support both IPv6 and IPv4 packets simultaneously and therefore no specific additional requirements are needed to be defined ... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 6.8 Management and Monitoring Domain | Functionality to be engineered in the cable network: β’ DOCSIS management between the CMTS and Cable Modem is using IPv4 addresses. β’ There is the additional functionality to monitor and manage the 6RD-CE within the RG and monitor and manage the 6RD-BR in order to provide sufficient capacity to scale with the traffic th... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 6.9 Security Domain | Functionality to be engineered in the cable network: β’ The continuity of the security of the end to end service shall be maintained when operating 6RD, however the operational implications from 6RD shall be minimized as specified in IETF RFC 5969 [17] section 12. β’ The logging of IPv6 addresses is required for LI and D... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 7 Technical Considerations | |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 7.1 Hardware | There is no change in hardware requirements at the edge, only software dependent forwarding, although the 6RD relays, LSNs, are required but this is usually a software upgrade with no extra hardware needed due to the simplicity of the technology. |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 7.2 MTU and fragmentation | The maximum DOCSIS MTU size is 1 518 bytes long and the MTU of the 6rd traffic needs to be modified so that the MTU of the DOCSIS transport is not exceeded. The 6rd tunnel MTU has to be reduced to 1 480 bytes. If a packet is received on the LAN interface which exceeds this, it has to be dropped and an ICMP 'fragmentati... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 7.3 Reliability | As explained in clause 6.2, when the 20 bytes (IPv4 header) is added for the 6RD encapsulation, the packet size increases to 1 520 which exceeds the DOCSIS 3.0 IP MTU size of 1 500. MTU size of 1 520 is a major issue for the transit network with unmanaged devices. For operators, the decision to use Cold Standby mode or... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 7.4 Quality of Service | The QoS policies defined by the cable operator for their network shall be engineered to operate properly with the new 6RD environment. A 6RD tunnel can be viewed as a particular case of uniform conceptual tunnel model, as described in IETF RFC 2983 [19]. This uniform model views an IP tunnel only as a necessary mechani... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 8 LSN and CPE Requirements | |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 8.1 General | The requirements of the 6RD implementation are based on enabling seamless 6RD connections without degradation in service, access, functionality or speed. Two network components are involved in the end-to-end 6RD approach; the LSN and the CPE. Requirement considerations for both are listed below. |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 8.2 LSN | The LSN device placed in the edge of the network (IXPE) as the IPv4 gateway to perform de-capsulation on the egress from a 4in6 packet to a pure IPv4 packet. Requirement considerations for LSN are: β’ Hardware Topology β’ Logical Topology ETSI ETSI TS 103 443-6 V1.1.1 (2016-08) 17 β’ Software/Hardware Features β’ Scalabili... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 8.3 CPE | The CPE is a device in customer's home to encapsulate the traffic on egress from a pure IPv4 packet to a 4in6 packet. Requirement considerations for 6RD CPE are: β’ Hardware Topology β’ Logical Topology β’ Software/Hardware Features β’ Scalability β’ Stability β’ IP Allocation/DHCP (v4 and v6) β’ Forwarding performance |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 9 6RD Feature Requirements | The 6RD features are as summarized in table 1 detailing for each function the requirement as required or optional with a brief description of each of the named functions. Table 1: Summary of 6RD Features Requirements Functional Name Requirement Description NAT44 - IETF RFC 4787 [21] (UDP) Required Compliance with NAT b... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 10 Network node Requirements | |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 10.1 BR Network node Hardware Feature and Topology | BR is an implementation of an IPv4/IPv6 transition protocol based on 6RD, and is the CORE node that all CPE/CEs running 6RD and creating softwares for the technology connect to. It is the termination for the IPv4 tunnel for native IPv6 traffic and it is the IPv4 NAT device egressing traffic towards the destination on I... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 10.2 Network node specific requirements | |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 10.2.1 General considerations | In 6RD architecture, only the routers (Border Relay) need a public IPv4 address, so even if subscribers were assigned private IPv4 addresses from the ISP, this would not hinder the connectivity of 6RD tunnels. Users can build 6RD tunnels with Border Relays using private IPv4 addresses, so the scale will not be bounded ... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 10.2.2 Integrated topology requirements | List of features required for both IPv4 and IPv6/L2 and L3 for an integrated topology solution: β’ MP BGP (as well 6PE and 6VPE) β’ BGP Community/32 bit AS β’ MPLS LDP (potentially only v4 native at present but the requirement for v6 native MPLS may become an absolute) β’ ECMP β’ QoS (v4/v6) - classification, priority queui... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 10.2.3 Hairpin topology requirements | List of features required for both IPv4 and IPv6/L2 and L3 for a "hairpin topology" solution: β’ SNMP (transport over v4 and v6) v1/v2/v3 β’ ACLs/Prefix Listing (both v4/v6) β’ TACACS/RADIUS (v4/v6) β’ Syslog (event reporting for v4 & v6 as well as transporting over both protocols) β’ CoPP (v4/v6) β’ Netflowv9 (potentially p... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 10.3 Scalability | The scalability requirements are dependent on the cable network build and delivery requirements. The values given are examples and would need to be scaled dependent on the network traffic. Example to illustrate the scalability considerations for a network build should take account of: 1) Minimum number flows per NPU. 2... |
f0b3181a55a53ae14a1f4d6cbf796452 | 103 443-6 | 10.4 Performance | The BR performance should be based on lowest acceptable benchmarks and the actual delivery of throughput, convergence, failover and latency for all aspects and features within the chassis interoperable on the network. ETSI ETSI TS 103 443-6 V1.1.1 (2016-08) 24 All performance requirements should be based on peak capaci... |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 1 Scope | The present document specifies a protocol to enable secure transparent communication sessions between network endpoints with one or more middleboxes between these endpoints, using data encryption and integrity protection, as well as authentication of the identity of the endpoints and the identity of any middlebox prese... |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 2 References | |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 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... |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 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... |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 3 Definition of terms, symbols and abbreviations | |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 3.1 Terms | For the purposes of the present document, the following terms apply: 1-sided authorization: middlebox traffic observability enabled unilaterally by one endpoint such that the other endpoint is not able to reject or negotiate the traffic observability, other than by ceasing the communication NOTE: See [i.5]. 2-sided aut... |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: A || B concatenation of binary strings A and B bn n-bit string consisting of the binary value b (0 or 1), repeated n times B-TID GBA-defined B-TID value (obtained during GBA bootstrapping, identifies key material) ctxt_id TLMSP container header cont... |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP Third Generation Partnership Project AAD Additional Authenticated Data AEAD Authenticated Encryption Additional Data AES Advanced Encryption Standard AES Advanced Encryption Standard AES-CBC Advanced Encryption Standard - Cipher Blocker C... |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 4 TLMSP specification | |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 4.1 Introduction | The Transport Layer Middlebox Security Protocol (TLMSP) specified in the present document is derived from the published mcTLS protocol [i.1] and [i.2]. The objective is to provide data privacy, data integrity and authentication controls of communication similar to that provided by TLS whilst also providing access to th... |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 4.2 The Record protocol | |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 4.2.1 Overview | |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 4.2.1.1 General | Akin to TLS, the Record protocol is a layered protocol that fragments data from higher level protocols (e.g. Handshake protocol, Application protocol), into TLMSP records, applies the agreed data integrity checks and encryption, and then transmits the resultant records over the transport layer. EXAMPLE: TCP can be used... |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 4.2.1.2 Records, containers and contexts | For TLMSP to allow the traffic optimizations it seeks to enable, TLMSP allows data fragments associated with multiple contexts to be "packaged" into one single TLMSP record and also allows for data associated with a single context to be split across records. Thus, a TLMSP record comprises protected data corresponding t... |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 4.2.1.3 Record and container construction and processing overview | +------+---------+------------+-------+---------~+~~~~+ | type | version | tot_length |hbh_id | fragment | hm | +------+---------+------------+-------+---------~+~~~~+ <-------- TLMSP header -------> NOTE: The field hm is the hop-by-hop MAC and is present only for Handshake records occurring after ChangeCipherSpec. The... |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 4.2.2.1 General | |
5e8571d38f1f624a189a961ac92403df | 103 523-2 | 4.2.2.1.1 Session and cryptographic state identification | In the sequel, the term message unit shall denote a TLMSP record, for protocols that do not use containers (Handshake and ChangeCipherSpec), and shall denote a container, for protocols that do use containers (Application and Alert). Each TLMSP session is associated with a state, i.e. cryptographic parameters that inclu... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.