<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ymbk-l3vpn-origination" target="https://datatracker.ietf.org/doc/html/draft-ymbk-l3vpn-origination-02">
   <front>
      <title>Authenticating L3VPN Origination Signaling</title>
      <author initials="R." surname="Bush" fullname="Randy Bush">
         <organization>Internet Initiative Japan</organization>
      </author>
      <author initials="K." surname="Patel" fullname="Keyur Patel">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Mehta" fullname="Pranav Mehta">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="A." surname="Sreekantiah" fullname="Arjun Sreekantiah">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="L." surname="Jalil" fullname="Luay Jalil">
         <organization>Verizon</organization>
      </author>
      <date month="October" day="22" year="2012" />
      <abstract>
	 <t>   A BGP-signaled Layer-3 VPN&#x27;s prefix bindings sent over BGP are
   subject to unintentional errors, both by the legitimate originator
   and by non-legitimate origins.  This is of special concern if the VPN
   traverses untrusted networks.  This document describes how the sender
   of the Prefix/VPN binding may sign it so that recipient of the
   binding may authenticate it.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ymbk-l3vpn-origination-02" />
   
</reference>
