%% You should probably cite rfc8895 instead of this I-D.
@techreport{ietf-alto-incr-update-sse-20,
    number =    {draft-ietf-alto-incr-update-sse-20},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-alto-incr-update-sse/20/},
    author =    {Wendy Roome and Y. Richard Yang},
    title =     {{ALTO Incremental Updates Using Server-Sent Events (SSE)}},
    pagetotal = 56,
    year =      2020,
    month =     feb,
    day =       21,
    abstract =  {The Application-Layer Traffic Optimization (ALTO) {[}RFC7285{]} protocol provides network related information, called network information resources, to client applications so that clients can make informed decisions in utilizing network resources. For example, an ALTO server can provide network and cost maps so that an ALTO client can use the maps to determine the costs between network endpoints when choosing communicating endpoints. However, the ALTO protocol does not define a mechanism to allow an ALTO client to obtain updates to the information resources, other than by periodically re-fetching them. Because some information resources (e.g., the aforementioned maps) may be large (potentially tens of megabytes), and because only parts of the information resources may change frequently (e.g., only some entries in a cost map), complete re-fetching can be inefficient. This document presents a mechanism to allow an ALTO server to push updates to ALTO clients, to achieve two benefits: (1) updates can be incremental, in that if only a small s ection of an information resource changes, the ALTO server can send just the changes; and (2) updates can be immediate, in that the ALTO server can send updates as soon as they are available.},
}