<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pim-sm-linklocal" target="https://datatracker.ietf.org/doc/html/draft-ietf-pim-sm-linklocal-10">
   <front>
      <title>Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode (PIM-SM) Link-Local Messages</title>
      <author initials="J. W." surname="Atwood" fullname="J. William Atwood">
         <organization>Concordia University/CSE</organization>
      </author>
      <author initials="M." surname="Siami" fullname="Maziar Siami">
         <organization>Concordia University/CIISE</organization>
      </author>
      <author initials="S." surname="Islam" fullname="Salekul Islam">
         <organization>IRS-EMT</organization>
      </author>
      <date month="December" day="16" year="2009" />
      <abstract>
	 <t>RFC 4601 mandates the use of IPsec to ensure authentication of the link-local messages in the Protocol Independent Multicast - Sparse Mode (PIM-SM) routing protocol.  This document specifies mechanisms to authenticate the PIM-SM link-local messages using the IP security (IPsec) Encapsulating Security Payload (ESP) or (optionally) the Authentication Header (AH).  It specifies optional mechanisms to provide confidentiality using the ESP.  Manual keying is specified as the mandatory and default group key management solution.  To deal with issues of scalability and security that exist with manual keying, optional support for an automated group key management mechanism is provided.  However, the procedures for implementing automated group key management are left to other documents.  This document updates RFC 4601. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pim-sm-linklocal-10" />
   
</reference>
