<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.sriram-replay-protection-design-discussion" target="https://datatracker.ietf.org/doc/html/draft-sriram-replay-protection-design-discussion-00">
   <front>
      <title>Design Discussion and Comparison of Replay-Attack Protection Mechanisms for BGPSEC</title>
      <author initials="K." surname="Sriram" fullname="Kotikalapudi Sriram">
         </author>
      <author initials="D." surname="Montgomery" fullname="Doug Montgomery">
         </author>
      <date month="September" day="21" year="2012" />
      <abstract>
	 <t>   The BGPSEC protocol requires a method for protection from replay
   attacks, at least to control the window of exposure.  In the context
   of BGPSEC, a replay attack occurs when an adversary suppresses a
   prefix withdrawal (implicit or explicit) or replays a previously
   received BGPSEC announcement for a prefix that has since been
   withdrawn.  This informational document provides design discussion
   and comparison of multiple alternative replay-attack protection
   mechanisms weighing their pros and cons.  It is meant to be a
   companion document to the standards track I-D.-ietf-sidr-bgpsec-
   rollover that will specify a method to be used with BGPSEC for
   replay-attack protection.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-sriram-replay-protection-design-discussion-00" />
   
</reference>
