<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-lisp-deployment" target="https://datatracker.ietf.org/doc/html/draft-ietf-lisp-deployment-12">
   <front>
      <title>Locator/Identifier Separation Protocol (LISP) Network Element Deployment Considerations</title>
      <author initials="L." surname="Jakab" fullname="Loránd Jakab">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="A." surname="Cabellos-Aparicio" fullname="Albert Cabellos-Aparicio">
         <organization>Technical University of Catalonia</organization>
      </author>
      <author initials="F." surname="Coras" fullname="Florin Coras">
         <organization>Technical University of Catalonia</organization>
      </author>
      <author initials="J." surname="Domingo-Pascual" fullname="Jordi Domingo-Pascual">
         <organization>Technical University of Catalonia</organization>
      </author>
      <author initials="D." surname="Lewis" fullname="Darrel Lewis">
         <organization>Cisco Systems</organization>
      </author>
      <date month="January" day="17" year="2014" />
      <abstract>
	 <t>This document is a snapshot of different Locator/Identifier Separation Protocol (LISP) deployment scenarios.  It discusses the placement of new network elements introduced by the protocol, representing the thinking of the LISP working group as of Summer 2013.  LISP deployment scenarios may have evolved since then.  This memo represents one stable point in that evolution of understanding.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-lisp-deployment-12" />
   
</reference>
