{
  "draft": "draft-ietf-taps-arch-19",
  "doc_id": "RFC9621",
  "title": "Architecture and Requirements for Transport Services",
  "authors": [
    "T. Pauly, Ed.",
    "B. Trammell, Ed.",
    "A. Brunstrom",
    "G. Fairhurst",
    "C. S. Perkins"
  ],
  "format": [
    "XML",
    "TEXT",
    "HTML",
    "PDF"
  ],
  "page_count": "29",
  "pub_status": "PROPOSED STANDARD",
  "status": "PROPOSED STANDARD",
  "source": "Transport Services",
  "abstract": "This document describes an architecture that exposes transport protocol features to applications for network communication.  The Transport Services Application Programming Interface (API) is based on an asynchronous, event-driven interaction pattern.  This API uses Messages for representing data transfer to applications and describes how a Transport Services Implementation can use multiple IP addresses, multiple protocols, and multiple paths and can provide multiple application streams.  This document provides the architecture and requirements.  It defines common terminology and concepts to be used in definitions of a Transport Services API and a Transport Services Implementation.",
  "pub_date": "January 2025",
  "keywords": [],
  "obsoletes": [],
  "obsoleted_by": [],
  "updates": [],
  "updated_by": [],
  "see_also": [],
  "doi": "10.17487/RFC9621",
  "errata_url": "https://www.rfc-editor.org/errata/rfc9621"
}