No indexed CRs are linked to the primary Work Item at or before this release.
Rel-8 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-8; they are not automatically attributed to the feature.
29.281 · CR 0001
Correction on GTP-U path failure
revised
29.281 · CR 0001 rev.1
Correction on GTP-U path failure
approved
29.281 · CR 0002
UDP Port Extension Header
approved
29.281 · CR 0003
Correction to IP support
revised
29.281 · CR 0003 rev.1
Correction to IP support
approved
29.281 · CR 0004
The Definition of GTP path
noted
29.281 · CR 0005
Default value for unused field of GTP header
withdrawn
29.281 · CR 0006
Handling of End Marker packet
approved
29.281 · CR 0007
GTP-U tunnelling over X2
revised
29.281 · CR 0007 rev.1
GTP-U tunnelling over X2
revised
29.281 · CR 0007 rev.2
GTP-U tunnelling over X2
revised
29.281 · CR 0007 rev.3
GTP-U tunnelling over X2
approved
29.281 · CR 0008
GTP-U updates for MBMS HSPA Evolution
revised
29.281 · CR 0008 rev.1
GTP-U updates for MBMS HSPA Evolution
revised
29.281 · CR 0008 rev.2
GTP-U updates for MBMS HSPA Evolution
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.