<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.wing-tram-turn-mobility" target="https://datatracker.ietf.org/doc/html/draft-wing-tram-turn-mobility-03">
   <front>
      <title>Mobility with TURN</title>
      <author initials="D." surname="Wing" fullname="Dan Wing">
         <organization>Cisco</organization>
      </author>
      <author initials="P." surname="Patil" fullname="Prashanth Patil">
         <organization>Cisco</organization>
      </author>
      <author initials="T." surname="Reddy.K" fullname="Tirumaleswar Reddy.K">
         <organization>Cisco</organization>
      </author>
      <author initials="P." surname="Martinsen" fullname="Paal-Erik Martinsen">
         <organization>Cisco</organization>
      </author>
      <date month="May" day="6" year="2015" />
      <abstract>
	 <t>   It is desirable to minimize traffic disruption caused by changing IP
   address during a mobility event.  One mechanism to minimize
   disruption is to expose a shorter network path to the mobility event
   so only the local network elements are aware of the changed IP
   address but the remote peer is unaware of the changed IP address.

   This draft provides such an IP address mobility solution using
   Traversal Using Relays around NAT (TURN).  This is achieved by
   allowing a client to retain an allocation on the TURN server when the
   IP address of the client changes.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-wing-tram-turn-mobility-03" />
   
</reference>
