| Thaler, D., Fenner, B., and B. Quinn, "Socket Interface Extensions for Multicast Source Filters, RFC 3678, January 2004. |
....for an SSM session must include a source address as well as a group address. Also, applications subscribing to an SSM channel must be capable of specifying a source address in addition to an group address. In other words, applications must be SSMaware. Specific API requirements are identified in [20]. Address Allocation: For IPv4, the address range of 232=8 has been assigned by IANA for SSM. Sessions expecting SSM functionality must allocate addresses from the 232=8 range. To ensure global SSM functionality in 232=8, including in networks where edge routers run IGMPv2 (i.e. do no support ....
D. Thaler, B. Fenner, and B. Quinn, "Socket interface extensions for multicast source filters." Internet Engineering Task Force (IETF), draft-ietf-idmr-msf-api-*.txt, June 2000.
No context found.
Thaler, D., Fenner, B., and B. Quinn, "Socket Interface Extensions for Multicast Source Filters, RFC 3678, January 2004.
No context found.
Thaler, D., Fenner, B. and B. Quinn, "Socket Interface Extensions for Multicast Source Filters", RFC 3678, January 2004.
No context found.
D. Thaler, B. Fenner, and B. Quinn, "Socket Interface Extensions for Multicast Source Filters draft-ietf-magma-msfapi -03.txt," Dec. 2002.
No context found.
D. Thaler, B. Fenner and B. Quinn. "Socket Interface Extensions for Multicast Source Filters". INTERNETDRAFT. February 2000.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC