%% You should probably cite draft-salsano-ictp-02 instead of this revision.
@techreport{salsano-ictp-00,
    number =    {draft-salsano-ictp-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-salsano-ictp/00/},
    author =    {Stefano Salsano and Andrea Detti and Nicola Blefari-Melazzi and Matteo Cancellieri},
    title =     {{ICTP - Information Centric Transport Protocol for CONET ICN}},
    pagetotal = 12,
    year =      2012,
    month =     may,
    day =       28,
    abstract =  {Let us consider an Information Centric Networking (ICN) solution, in which an End Node requests for a content sending "content requests" (or "interest packets"). The content is provided back to the requestor by the "origin" node or by an intermediate node that had cached the content. The content is usually divided into "chunks" that can be individually requested, sent back to the requester, cached into intermediate nodes. The sending rate of content requests can be adjusted in order to perform congestion control, implementing a receiver driven transport protocol. As it can be useful to have large chunks (significantly larger than the Maximum Tranfer Unit across the network), the transport protocol should also be used to further segment the chunks rather than relying to IP fragmentation. In this memo we define ICTP (Information Centric Transport Protocol), a receiver driven transport protocol for ICN, which relies on the CONET ICN solution described in a companion draft.},
}