<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.atkinson-teas-rsvp-auth-v2" target="https://datatracker.ietf.org/doc/html/draft-atkinson-teas-rsvp-auth-v2-00">
   <front>
      <title>RSVP Cryptographic Authentication, Version 2</title>
      <author initials="R." surname="Atkinson" fullname="Ran Atkinson">
         <organization>Consultant</organization>
      </author>
      <author initials="T." surname="Li" fullname="Tony Li">
         <organization>Juniper Networks</organization>
      </author>
      <date month="October" day="21" year="2024" />
      <abstract>
	 <t>   This document provides an algorithm-independent description of the
   format and use of RSVP&#x27;s INTEGRITY object.  The RSVP INTEGRITY object
   is widely used to provide hop-by-hop integrity and authentication of
   RSVP messages, particularly in MPLS deployments using RSVP-TE.  This
   replaces and obsoletes RFC 2747 and RFC 3097.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-atkinson-teas-rsvp-auth-v2-00" />
   
</reference>
