<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.manral-rpsec-existing-crypto" target="https://datatracker.ietf.org/doc/html/draft-manral-rpsec-existing-crypto-05">
   <front>
      <title>Issues with existing Cryptographic Protection Methods for Routing Protocols</title>
      <author initials="V." surname="Manral" fullname="Vishwas Manral">
         <organization>IP Infusion</organization>
      </author>
      <date month="February" day="11" year="2008" />
      <abstract>
	 <t>Routing protocols are designed to use cryptographic mechanisms to 
   authenticate data being received from a neighboring router to ensure 
   that it has not been modified in transit, and actually originated 
   from the neighboring router purporting to have originating the data.  
   Most of the cryptographic mechanisms defined to date rely on hash 
   algorithms applied to the data in the routing protocol packet, which 
   means the data is transported, in the clear, along with a signature 
   based on the data itself.  These mechanisms rely on the manual 
   configuration of the keys used to seed, or build, these hash based 
   signatures.  This document outlines some of the problems with manual 
   keying of these cryptographic algorithms.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-manral-rpsec-existing-crypto-05" />
   
</reference>
