We expect that the readers understand encryption, data integrity, host authentication, and other basic cryptographic properties. The readers should also be familiar with network security protocol requirements such as protection against man-in-the-middle, replay, connection hijacking, and
denial of service attacks. We also expect the readers to have some knowledge of the IPsec terminology.
The next chapter describes the framework for multicast security de- veloped at the IRTF SMuG Research Group and IETF MSEC Working Group. Problem area 1, that is, secure multicast data handling, is the topic of Chapter 3. Management of keying material, otherwise known as problem area 2, is introduced in Chapter 4, with further coverage in the following two chapters. Chapter 5 describes group key management architectures and protocols, and Chapter 6 discusses group key management algorithms. Secure group policy, labeled as problem area 3, is the subject of Chapter 7. Infrastructure protection is the topic of the next two chapters. Routing protocol security is covered in Chapter 8, and Reliable Multicast protocol security is the subject of Chapter 9. Applications of secure multicasting is the topic of the following chapter. Chapter 11 concludes the book with a discussion on future topics.
There are a number of ways to read the material presented here. The chapters on each problem area are more or less independent. The current chapter and Chapter 2 provide an insight into the problem space of multicast security. Chapters 8 and 9 provide a summary of the multicast infrastructure security requirements and solutions. They are independent of the other chapters and could be read separately.
References
[1] Cain, B., et al., ‘‘Internet Group Management Protocol, Version 3,’’ draft-ietf- idmr-igmp-v3-09.txt, IETF, January 2002, work in progress.
[2] Deering, S., et al., ‘‘The PIM Architecture for Wide-Area Multicast Routing,’’
IEEE/ACM Trans. on Networking, Vol. 4, No. 2, 1996, pp. 153–162.
[3] Estrin, D., et al., ‘‘Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification,’’ RFC 2362 (experimental), IETF, June 1998.
[4] Diot, C., et al., ‘‘Deployment Issues for the IP Multicast Service and Architecture,’’ IEEE Network, Special Issue on Multicasting, January/February 2000.
[5] Kent, S., and R. Atkinson, ‘‘IP Encapsulating Security Payload (ESP),’’ RFC 2406 (proposed standard), IETF, November 1998.
[6] Krawczyk, H., M. Bellare, and R. Canetti, ‘‘HMAC: Keyed-Hashing for Message Authentication,’’ RFC 2104 (informational), IETF, February 1997. [7] Canetti, R., et al., ‘‘Multicast Security: A Taxonomy and Efficient Construc-
tions,’’ inProc. of IEEE INFOCOM, New York, March 1999.
[8] Canetti, R., P. Rohatgi, and P. Cheng, ‘‘Multicast Data Security Transforma- tions: Requirements, Considerations, and Proposed Design,’’ draft-irtf-smug- data-transforms-00.txt, IRTF, June 2000, work in progress.
[9] Harkins, D., and D. Carrel, ‘‘The Internet Key Exchange (IKE),’’ RFC 2409 (proposed standard), IETF, November 1998.
[10] Baugher, M., et al., ‘‘Group Key Management Architecture,’’ draft-ietf-msec- gkmarch-02.txt, IETF, March 2002, work in progress.
[11] Kent, S., and R. Atkinson, ‘‘Security Architecture for the Internet Protocol,’’ RFC 2401 (proposed standard), IETF, November 1998.
[12] Hardjono, T., M. Baugher, and H. Harney, ‘‘Group Security Association (GSA) Management in IP Multicast,’’ inProc. of the 16th International Conference on Information Security (IFIP/SEC), Paris, France, June 2001.
[13] Mittra, S., ‘‘Iolus: A Framework for Scalable Secure Multicasting,’’ inProc. of ACM SIGCOMM, Cannes, France, September 1997, pp. 277–288.
[14] Hardjono, T., B. Cain, and I. Monga, ‘‘Intra-Domain Group Key Management Protocol,’’ draft-ietf-ipsec-intragkm-02.txt, IETF, February 2000, work in progress.
[15] Baugher, M., et al., ‘‘Group Domain of Interpretation for ISAKMP,’’ draft-ietf- msec-gdoi-04.txt, IETF, March 2002, work in progress.
[16] Harney, H., et al., ‘‘Group Secure Association Key Management Protocol,’’ draft-ietf-msec-gsakmp-sec-00.txt, IETF, March 2001, work in progress. [17] Wallner, D., E. Harder, and R. Agee, ‘‘Key Management for Multicast: Issues
and Architectures,’’ RFC 2627 (informational), IETF, June 1999.
[18] Yang, Y. R., et al., ‘‘Reliable Group Rekeying: Design and Performance Analysis,’’ inProc. of ACM SIGCOMM, San Diego, CA, August 2001.
[19] Setia, S., et al., ‘‘Kronos: A Scalable Rekeying Approach for Secure Multicast,’’ inProc. of IEEE Symposium on Security and Privacy, Oakland, CA, May 2000. [20] Dinsmore, P. T., et al., ‘‘Policy-Based Security Management for Large Dynamic
Groups: An Overview of the DCCM Project,’’ inProc. of the DARPA Information Survivability Conference & Exposition, Vol. I of II (DISCEX), Hilton Head, SC, January 2000, pp. 64–73.
[21] McDaniel, P., and A. Prakash, Ismene: Provisioning and Policy Reconciliation in Secure Group Communication, Technical Report CSE-TR-438-00, Electrical Engineering and Computer Science, University of Michigan, December 2000. [22] Holbrook, H., and B. Cain, ‘‘Source Specific Multicast for IP,’’ draft-ietf-ssm-
arch-00.txt, IETF, November 2001, work in progress.
[23] Miller, K., et al., ‘‘Starburst Multicast File Transfer Protocol (MFTP) Specification,’’ draft-miller-mftp-spec-03.txt, IRTF, April 1998, work in progress.
Framework for multicast
and group security
T
he problem of security for multicast and group security concerns not only content protection of the data or traffic being delivered to a group through IP multicast, but also concerns the protection of the network infrastructure that implements the multicast-related protocols. Therefore, one of the first tasks in looking at multicast security is to understand the landscape and define a reasonable scope or definition of the problems at hand.Consequently, the aim of this chapter is to subdivide the complex problem of multicast and group security into manage- able pieces. This chapter also reports on the IETF’s approach in addressing these pieces. The subdivision also provides a road- map for subsequent chapters dealing with specific issues.