<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.curran-lisp-emacs" target="https://datatracker.ietf.org/doc/html/draft-curran-lisp-emacs-00">
   <front>
      <title>EID Mappings Multicast Across Cooperating Systems for LISP</title>
      <author initials="S. W." surname="Brim" fullname="Scott W. Brim">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="D." surname="Farinacci" fullname="Dino Farinacci">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="D." surname="Meyer" fullname="David Meyer">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="J." surname="Curran" fullname="John Curran">
         <organization>ServerVault</organization>
      </author>
      <date month="November" day="9" year="2007" />
      <abstract>
	 <t>One of the potential problems with the &quot;map-and-encapsulate&quot;
approaches to routing architecture is that there is a significant
chance of packets being dropped while a mapping is being retrieved.
Some approaches pre-load ingress tunnel routers with at least part of
the mapping database.  Some approaches try to solve this by providing
intermediate &quot;default&quot; routers which have a great deal more knowledge
than a typical ingress tunnel router.  This document proposes a
scheme which does not drop packets yet does not require a great deal
of knowledge in any router.  However, there are still some issues
that need to be worked out.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-curran-lisp-emacs-00" />
   
</reference>
