<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-tcpm-converters" target="https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-converters-02">
   <front>
      <title>0-RTT TCP Convert Protocol</title>
      <author initials="O." surname="Bonaventure" fullname="Olivier Bonaventure">
         <organization>Tessares</organization>
      </author>
      <author initials="M." surname="Boucadair" fullname="Mohamed Boucadair">
         <organization>Orange</organization>
      </author>
      <author initials="S." surname="Gundavelli" fullname="Sri Gundavelli">
         <organization>Cisco</organization>
      </author>
      <author initials="S." surname="Seo" fullname="SungHoon Seo">
         <organization>Korea Telecom</organization>
      </author>
      <date month="July" day="2" year="2018" />
      <abstract>
	 <t>   This document specifies an application proxy, called Transport
   Converter, to assist the deployment of TCP extensions such as
   Multipath TCP.  This proxy is designed to avoid inducing extra delay
   when involved in a network-assisted connection (that is, 0-RTT).
   This specification assumes an explicit model, where the proxy is
   explicitly configured on hosts.

   -- Editorial Note (To be removed by RFC Editor)

   Please update these statements with the RFC number to be assigned to
   this document:
   [This-RFC]

   Please update TBA statements with the port number to be assigned to
   the Converter Protocol.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-tcpm-converters-02" />
   
</reference>
