RFC 1112:Host Extensions for IP Multicasting
RFC-Ref

datagram


Click on the red underlined text to get to the source

... IP multicasting is the transmission of an IP datagram to a "host group ...
... destination address. A multicast datagram is delivered to all members of its destination host group ...
... reliability as regular unicast IP datagrams, i.e., the datagram is not guaranteed to arrive intact at all members of the destination ...
... reliability as regular unicast IP datagrams, i.e., the datagram is not guaranteed to arrive intact at all members of the destination ...
... destination group or in the same order relative to other datagrams. ...
... host need not be a member of a group to send datagrams to it. ...
... Internetwork forwarding of IP multicast datagrams is handled by "multicast routers" which may be co-resident with, or separate from, ...
... gateways. A host transmits an IP multicast datagram as a local network multicast ...
... members of the destination host group. If the datagram has an IP time-to-live ...
... delivery by transmitting the datagram as a local multicast. ...


... hosts may cause misdelivery of multicast IP datagrams to level 0 hosts. Such datagrams ...
... IP datagrams to level 0 hosts. Such datagrams can easily be identified by the presence of a class D IP address in their destination address field ...
... Level 1: support for sending but not receiving multicast IP datagrams. ...
... host groups, as well as send IP datagrams to host groups. It requires implementation of the ...


... IP implementation must support the transmission of multicast IP datagrams. To provide level 2 multicasting, a host ...
... host must also support the reception of multicast IP datagrams. Each of these two new services is described in a separate section, below. For each service ...


... SENDING MULTICAST IP DATAGRAMS ...
... Multicast IP datagrams are sent using the same "Send IP" operation used to send unicast ...
... IP" operation used to send unicast IP datagrams; an upper-layer protocol module merely specifies an IP ...
... time-to-live of an outgoing multicast datagram, if such a capability does not already exist. If the upper-layer protocol chooses not to specify a time-to-live ...
... time-to-live, it should default to 1 for all multicast IP datagrams, so that an explicit choice is required to multicast beyond a single network ...
... host is itself a member of a group to which a datagram is being sent, the service interface should provide a way for the upper-layer ...
... upper-layer protocol to inhibit local delivery of the datagram; by default, a copy of the datagram is looped back. This is a performance ...
... delivery of the datagram; by default, a copy of the datagram is looped back. This is a performance optimization for upper-layer ...
... To support the sending of multicast IP datagrams, the IP module must be extended to recognize IP ...
... group addresses when routing outgoing datagrams. Most IP implementations include the following logic: ...
... destination is on the same local network, send datagram locally to IP-destination ...
... destination else send datagram locally to GatewayTo( IP-destination ) ...
... host group, send datagram locally to IP-destination ...
... destination else send datagram locally to GatewayTo( IP-destination ) ...
... group on the outgoing interface, a copy of the outgoing datagram must be looped-back for local delivery, unless inhibited by the sender ...
... The IP source address of the outgoing datagram must be one of the individual addresses corresponding to the outgoing interface ...
... source route or record route option of an outgoing IP datagram. ...
... interface is required to support the sending of multicast IP datagrams. The IP module merely specifies an IP ...
... destination field of Ethernet packets. All that is needed to support the sending of multicast IP datagrams is a procedure for mapping IP host group addresses ...
... way as Ethernet for the purpose of sending multicast IP datagrams. For a network that supports broadcast ...


... RECEIVING MULTICAST IP DATAGRAMS ...
... Incoming multicast IP datagrams are received by upper-layer protocol modules using the same "Receive IP ...
... IP" operation as normal, unicast datagrams. Selection of a destination upper-layer protocol is based ...
... protocol field in the IP header, regardless of the destination IP address. However, before any datagrams destined to a particular group can be received, an upper-layer ...
... will apply to the default interface for sending multicast datagrams (see section 6.1). ...
... interface, in which case duplicate multicast datagrams may be received. It is also permissible for more than one upper-layer protocol to request ...
... To support the reception of multicast IP datagrams, the IP module must be extended to maintain a list of host ...
... group memberships associated with each network interface. An incoming datagram destined to one of those groups is processed exactly the same way as ...
... destined to one of those groups is processed exactly the same way as datagrams destined to one of the host's individual addresses. ...
... Incoming datagrams destined to groups to which the host does not ...
... entry. On hosts with more than one network interface, if a datagram arrives via one interface, destined for a group ...
... host belongs only on a different interface, the datagram is quietly discarded. (These cases should occur only as a result of inadequate multicast address ...
... An incoming datagram is not rejected for having an IP time-to-live of ...
... 1 (i.e., the time-to-live should not automatically be decremented on arriving datagrams that are not being forwarded). An incoming datagram with an IP ...
... arriving datagrams that are not being forwarded). An incoming datagram with an IP host group address ...
... Destination Unreachable, Time Exceeded, Parameter Problem, Source Quench, or Redirect) is never generated in response to a datagram destined to an IP host ...
... (Datagrams addressed to the all-hosts group are recognized as a ...
... To support the reception of multicast IP datagrams, an Ethernet module must be able to receive packets addressed to the Ethernet ...
... Ethernet for the purpose of receiving multicast IP datagrams. For pure broadcast networks, such as the Experimental ...
... store-and-forward networks, multicast IP datagrams will arrive as local network unicasts ...


... specification. IGMP messages are encapsulated in IP datagrams, with an IP protocol number of 2. All IGMP messages ...
... multicast routers receive all IP multicast datagrams, and therefore need not be addressed explicitly. Further note that the routers need not know which hosts ...


... In general, a host cannot assume that datagrams sent to any host group address ...
... group address will reach only the intended hosts, or that datagrams received as a member of a transient host group ...



Google
Web
RFC-Ref