2007
DOI: 10.17487/rfc4947
|View full text |Cite
|
Sign up to set email alerts
|

Address Resolution Mechanisms for IP Datagrams over MPEG-2 Networks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

2008
2008
2015
2015

Publication Types

Select...
4
2
2

Relationship

2
6

Authors

Journals

citations
Cited by 12 publications
(8 citation statements)
references
References 10 publications
0
8
0
Order By: Relevance
“…The addressing issues resemble those for DVB-H (Section 4.2.4) [48]. The issues for using GSE resemble those for ULE (except the PID is not available as a mechanism for filtering traffic).…”
Section: Tv Broadcast and Satellite Networkmentioning
confidence: 99%
“…The addressing issues resemble those for DVB-H (Section 4.2.4) [48]. The issues for using GSE resemble those for ULE (except the PID is not available as a mechanism for filtering traffic).…”
Section: Tv Broadcast and Satellite Networkmentioning
confidence: 99%
“…A mandatory Type field directly precedes the GSE PDU ( Figure 4 [22], but this has limited use for discovery. After bootstrap, a receiver may move to one of several network services, and it may be natural to assign different address to each service.…”
Section: Allocation Of a Dedicated Gse Type Field Valuementioning
confidence: 99%
“…The system would also increase complexity when other GSE extensions are present (e.g., timestamps). Well-known IP multicast destination addresses are used in many IP bootstrap procedures, and when present, these would normally result in a mapping to well-known MAC addresses [22].…”
Section: Allocation Of a Dedicated Gse Type Field Valuementioning
confidence: 99%
“…These issues are not considered here, but this operation may be simplified in GSE by ensuring that all SNDUs that carry this Extension Header are placed before other data within the BBFrame DataField [GSE]. The need for consistency in the use of PIDs and the related service information is described in section 4.2 of [RFC4947].…”
Section: -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+mentioning
confidence: 99%
“…Since this attack requires access to the link and/or layer 2 equipment, such an attack could also directly attack signalling information sent as native TS Packets (not encapsulated by ULE/GSE). Security issues relating to the transmission and interpretation of layer 2 signalling information (including Address Resolution) within a TS Multiplex are described in [RFC4947]. GSE provides functions that are equivalent to those of the Unidirectional Lightweight Encapsulation (ULE) [RFC4326].…”
Section: Iana Considerationsmentioning
confidence: 99%