{
  "draft": "draft-ietf-taps-interface-26",
  "doc_id": "RFC9622",
  "title": "An Abstract Application Programming Interface (API) for Transport Services",
  "authors": [
    "B. Trammell, Ed.",
    "M. Welzl, Ed.",
    "R. Enghardt",
    "G. Fairhurst",
    "M. K\u00fchlewind",
    "C. S. Perkins",
    "P.S. Tiesel",
    "T. Pauly"
  ],
  "format": [
    "XML",
    "TEXT",
    "HTML",
    "PDF"
  ],
  "page_count": "84",
  "pub_status": "PROPOSED STANDARD",
  "status": "PROPOSED STANDARD",
  "source": "Transport Services",
  "abstract": "This document describes an abstract Application Programming Interface (API) to the transport layer that enables the selection of transport protocols and network paths dynamically at runtime.  This API enables faster deployment of new protocols and protocol features without requiring changes to the applications.  The specified API follows the Transport Services Architecture by providing asynchronous, atomic transmission of Messages.  It is intended to replace the BSD Socket API as the common interface to the transport layer, in an environment where endpoints could select from multiple network paths and potential transport protocols.",
  "pub_date": "January 2025",
  "keywords": [
    "Happy Eyeballs",
    "Transport Selection"
  ],
  "obsoletes": [],
  "obsoleted_by": [],
  "updates": [],
  "updated_by": [],
  "see_also": [],
  "doi": "10.17487/RFC9622",
  "errata_url": "https://www.rfc-editor.org/errata/rfc9622"
}