RFC 4947: Address Resolution Mechanisms for IP Datagrams over MPEG-2 Networks
In plain English — editorial summary, not part of the RFC
This document describes the process of binding/associating IPv4/IPv6 addresses with MPEG-2 Transport Streams (TS). This procedure is known as Address Resolution (AR) or Neighbor Discovery (ND). Such address resolution complements the higher-layer resource discovery tools that are used to advertise IP sessions. In MPEG-2 Networks, an IP address must be associated with a Packet ID (PID) value and a specific Transmission Multiplex. This document reviews current methods appropriate to a range of technologies (such as DVB (Digital Video Broadcasting), ATSC (Advanced Television Systems Committee), DOCSIS (Data-Over-Cable Service Interface Specifications), and variants). It also describes the interaction with well-known protocols for address management including DHCP, ARP, and the ND protocol. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4947
- Published
- July 2007
- Authors
- G. Fairhurst; M. Montpetit
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 41
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5494IANA Allocation Guidelines for the Address Resolution Protocol (ARP)Current
April 2009
- RFC 4391Transmission of IP over InfiniBand (IPoIB)Updated
April 2006
- RFC 2834ARP and IP Broadcast over HIPPI-800Updated
May 2000
- RFC 2625IP and ARP over Fibre ChannelObsoleted
June 1999
- RFC 4952Overview and Framework for Internationalized EmailObsoleted
July 2007
- RFC 4918HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)Updated
June 2007
- RFC 4978The IMAP COMPRESS ExtensionCurrent
August 2007
- RFC 4991A Common Schema for Internet Registry Information Service Transfer ProtocolsCurrent
August 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?