<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v5 rel. 3 U (http://www.xmlspy.com)
     by Daniel M Kohn (private) -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>
<rfc category="std" docName="draft-yang-alto-transport-analysis-00"
     ipr="trust200902">
  <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

  <?rfc toc="yes" ?>

  <?rfc symrefs="yes" ?>

  <?rfc sortrefs="yes"?>

  <?rfc iprnotified="no" ?>

  <?rfc strict="yes" ?>

  <front>
    <title abbrev="ALTO Performance Cost Metrics">ALTO Transport Analysis</title>


    <author fullname="Y. Richard Yang" initials="Y." surname="Yang">
      <organization>Yale University</organization>

      <address>
        <postal>
          <street>51 Prospect St</street>

          <city>New Haven</city>

          <region>CT</region>

          <code>06520</code>

          <country>USA</country>
        </postal>

        <email>yry@cs.yale.edu</email>
      </address>
    </author>


    <date day="24" month="October" year="2021"/>

    <area>TSV Area</area>

    <workgroup>ALTO Working Group</workgroup>

    <keyword>RFC</keyword>

    <keyword>Request for Comments</keyword>

    <keyword>I-D</keyword>

    <keyword>Internet-Draft</keyword>

    <keyword>ALTO</keyword>

    <abstract>
       <t>Exposing network information to applications can be a basic function of computer networking.
          Such network information can be exposed to applications through either the data path or 
          the control path. This informational document conducts a survey and analysis of existing capabilities and performance of protocols transporting network information to applications.
        </t>

    </abstract>

    <note title="Requirements Language">
        <t>
          The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
          "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY",
          and "OPTIONAL" in this document are to be interpreted as described
          in BCP 14 <xref target="RFC2119"/><xref target="RFC8174"/> when,
          and only when, they appear in all capitals, as shown here.
        </t>
    </note>

  </front>

  <middle>
    <section anchor="secintro" title="Introduction">
      <t>Application-Layer Traffic Optimization (ALTO)  
         provides a means for network applications 
         to obtain network status information so that the applications can 
         identify efficient application-layer traffic patterns using the networks. 
         Recently, multiple extensions are proposed to the ALTO base protocol 
         <xref target="RFC7285"/> 
         to extend the ability of ALTO to transport network information to applications. 
         The objective of this document is to put ALTO transport in the general context of 
         transporting network information to applications, and evaluate ALTO and related 
         protocols in their transport capabilities and efficiencies.
      </t>
    </section>

    <section anchor="secmechanisms" title="Transport Designs">
      <t>There can be a large design space to transport network information to applications. Broadly, the designs can be classified into two types: data path transport and control path transport. An example of data path transport is TCP ECN options, which allows networks to convey network information to applications (i.e., endhosts). In a general data path design, as data packets traverse a network, the network elements update the field(s) of the data packets to provide network information. The recent development of in-network telemetry (INT) focuses on data path transport. This document focuses on TCP options based data path transport.</t>

      <t>ALTO base protocol, on the other hand, is a control path design. In a general control path design, the network information is collected by a service and exposed to applications. This document focuses on ALTO transport and 3GPP NEF. </t>

      <section anchor="secdptcp" title="Data Path Transport: TCP Options">
      </section>

      <section anchor="seccpalto" title="Control Path Transport: ALTO">
      </section>

      <section anchor="seccpnef" title="Control Path Transport: 3GPP NEF">
      </section>

    </section>


    <section anchor="seccap" title="Capabilities">
      <section title="Information Model">

        <t>The information model includes the following abilities: information availability, information selection, update control, etc.</t>

      </section>

      <section title="Latency">
      </section>

      <section title="Encoding Efficiency">
      </section>
      

    </section>

    <section anchor="secsecconsider" title="Security Considerations">
      <t>There can be substantial security issues when transporting network information to applications.
      </t>
    </section>

    <section anchor="ianaconsider" title="IANA Considerations">
      <t>This informational document does not have IANA consideration.</t>

    </section>

    <section title="Acknowledgments">
      <t>The author thanks many reviewers for their comments.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">

      <?rfc include="reference.RFC.2119.xml"?>  <!-- requirements words -->
      <?rfc include="reference.RFC.2818.xml"?>  <!-- iana --> 
      <?rfc include="reference.RFC.8174.xml"?>  <!-- iana --> 

    </references>

    <references title="Informative References">
            
      <?rfc include="reference.RFC.7285.xml"?>  <!-- base alto -->

      <?rfc include="reference.RFC.8446.xml"?>  <!-- TLS 1.3 -->

      <reference anchor="Prophet">
          <front>
            <title>Prophet: Fast, Accurate Throughput Prediction with Reactive Flows</title>
            <author initials='K' surname='Gao' />
            <author initials='J' surname='Zhang' />
            <author initials='YR' surname='Yang' />
            <date year="2020" />
          </front>
          <seriesInfo name='ACM/IEEE Transactions on Networking' value='July'/>
      </reference>

      <reference anchor="Prometheus">
          <front>
            <title>Prometheus: A Next-Generation Monitoring System</title>
            <author initials='J' surname='Volz' />
            <author initials='B' surname='Rabenstein' />
            <date year="2015" />            
          </front>
        </reference>


    </references>
  </back>
</rfc>