No indexed CRs are linked to the primary Work Item at or before this release.
Rel-11 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-11; they are not automatically attributed to the feature.
29.281 · CR 0060
Length of PDCP PDU number
revised
29.281 · CR 0043
Default inner MTU size
approved
29.281 · CR 0045
Reference RFC update
revised
29.281 · CR 0045 rev.1
Reference RFC update
approved
29.281 · CR 0046
Defination of C-TEID in 29.281
revised
29.281 · CR 0046 rev.1
Defination of C-TEID in 29.281
approved
29.281 · CR 0047
GTP-U traffic over aggregated Ethernet links and ECMP routes
withdrawn
29.281 · CR 0048
Dynamic allocation of UDP source ports
revised
29.281 · CR 0048 rev.1
Dynamic allocation of UDP source ports
approved
29.281 · CR 0049
29.281 CR Requirement for sending Error Indication
approved
29.281 · CR 0050
Tunnelling between eNodeB and RNC
approved
29.281 · CR 0051
Service Type in GTP-U for SIRIG
revised
29.281 · CR 0051 rev.1
Service Type in GTP-U for SIRIG
postponed
29.281 · CR 0052
Addition of GTP based S2a
revised
29.281 · CR 0052 rev.1
Addition of GTP based S2a
approved
Traceability limits
What this lineage is not claiming
The reviewed topic-to-specification mapping is Atlas-curated and non-normative even when its source is an official 3GPP record.
When an explicit stage classification is unavailable, specification layers are inferred from the TS/TR series and are labelled inferred rather than presented as official 3GPP stage assignments.
Connected Work Items and release-context Change Requests share mapped specifications; only the topic source Work Item is treated as primary evidence for the reviewed topic mapping.
This is traceability evidence and navigation, not a clause-by-clause normative feature definition.