RFC 4947 on Address Resolution Mechanisms for IP Datagrams over MPEG-2 Networks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A new Request for Comments is now available in online RFC libraries.



        

        RFC 4947



        Title:      Address Resolution Mechanisms for IP 

                    Datagrams over MPEG-2 Networks 

        Author:     G. Fairhurst, M. Montpetit

        Status:     Informational

        Date:       July 2007

        Mailbox:    gorry@erg.abdn.ac.uk, 

                    mmontpetit@motorola.com

        Pages:      41

        Characters: 102717

        Updates/Obsoletes/SeeAlso:   None



        I-D Tag:    draft-ietf-ipdvb-ar-06.txt



        URL:        http://www.rfc-editor.org/rfc/rfc4947.txt



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.



This document is a product of the IP over DVB

Working Group of the IETF.





INFORMATIONAL: This memo provides information for the Internet community. 

It does not specify an Internet standard of any kind. Distribution

of this memo is unlimited.



This announcement is sent to the IETF list and the RFC-DIST list.

Requests to be added to or deleted from the IETF distribution list

should be sent to IETF-REQUEST@IETF.ORG.  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.



Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 



help: ways_to_get_rfcs. For example:



        To: rfc-info@RFC-EDITOR.ORG

        Subject: getting rfcs



        help: ways_to_get_rfcs



Requests for special distribution should be addressed to either the

author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.



Submissions for Requests for Comments should be sent to

RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC

Authors, for further information.





The RFC Editor Team

USC/Information Sciences Institute



...





_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux