File: single-source-multicast

package info (click to toggle)
doc-iana 2001.08-1
  • links: PTS
  • area: main
  • in suites: woody
  • size: 8,176 kB
  • ctags: 954
  • sloc: perl: 1,057; makefile: 83; sh: 27
file content (43 lines) | stat: -rw-r--r-- 1,948 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43


Single-source IP Multicast Address Range

Description:

The IP multicast address range 232.X.X.X is to be designated for
single-source multicast applications and protocols.  This means that
an IP multicast packet sent by host S to an address E in this range
should be delivered to each host H that has done a source-specific
join to (S,E) as supported in the proposed IGMPv3 and PIM.  The
delivery semantics for other cases of IP multicast packets sent to an
address E in this range are undefined.  In particular, a router is
free to drop (rather than forward) a packet sent by S to E in this
range if no host has communicated a source-specific join to this
router for (S,E).  Multiple sources can use the same address E in this
range with the above semantics and without conflict: packets from each
source Si are delivered only to hosts that joined to (Si,E).

Plan:

1) IANA recharacterizes this address range as single-source multicast
   addresses from its current VMTP multicast designation, updating the
   assigned  number documents accordingly, and citing the above
   description for their semantics.  No further action is required by
   IANA.  In particular, no additional address allocation within this
   range is required.

2) No transition plan is required because VMTP use of this address
   range is compatible with the above single-source semantics, and no
   other protocols are assigned for use in this address range.
   Moreover, current IP multicast routing protocols provide a superset
   of these semantics, so are compatible.

3) Experimental work will proceed with protocols for supporting
   single-source multicast and source-specific joins, as in IGMPv3,
   leading to protocol proposals for suitable review and consideration
   by the IETF.  Any higher-level (than IP) protocol may use this
   space, within the specified single-source semantics.



[DRC3]  David Cheriton, <cheriton@DSG.Stanford.EDU>, October 1998.