datatracker.ietf.org/doc/html/rfc955

Preview meta tags from the datatracker.ietf.org website.

Linked Hostnames

3

Search Engine Appearance

Google

https://datatracker.ietf.org/doc/html/rfc955

RFC 955: Towards a transport service for transaction processing applications

Towards a transport service for transaction processing applications (RFC 955, )



Bing

RFC 955: Towards a transport service for transaction processing applications

https://datatracker.ietf.org/doc/html/rfc955

Towards a transport service for transaction processing applications (RFC 955, )



DuckDuckGo

https://datatracker.ietf.org/doc/html/rfc955

RFC 955: Towards a transport service for transaction processing applications

Towards a transport service for transaction processing applications (RFC 955, )

  • General Meta Tags

    8
    • title
      RFC 955 - Towards a transport service for transaction processing applications
    • charset
      utf-8
    • X-UA-Compatible
      IE=edge
    • viewport
      width=device-width, initial-scale=1
    • description
      Towards a transport service for transaction processing applications (RFC 955, )
  • Open Graph Meta Tags

    5
    • og:title
      RFC 955: Towards a transport service for transaction processing applications
    • og:url
      https://datatracker.ietf.org/doc/html/rfc955
    • og:site_name
      IETF Datatracker
    • og:description
      The DoD Internet protocol suite includes two alternative transport service protocols, TCP and UDP, which provide virtual circuit and datagram service, respectively. These two protocols represent points in the space of possible transport service attributes which are quite "far apart". We want to examine an important class of applications, those which perform what is often called "transaction processing". We will see that the communication needs for these applications fall into the gap "between" TCP and UDP -- neither protocol is very appropriate. This RFC is concerned with the possible design of one or more new protocols for the ARPA-Internet, to support kinds of applications which are not well supported at present. The RFC is intended to spur discussion in the Internet research community towards the development of new protocols and/or concepts, in order to meet these unmet application requirements. It does not represent a standard, nor even a concrete protocol proposal.
    • og:type
      article
  • Link Tags

    12
    • alternate
      /feed/document-changes/rfc955/
    • apple-touch-icon
      https://static.ietf.org/dt/12.40.0/ietf/images/ietf-logo-nor-180.png
    • canonical
      https://datatracker.ietf.org/doc/html/rfc955
    • icon
      https://static.ietf.org/dt/12.40.0/ietf/images/ietf-logo-nor-32.png
    • icon
      https://static.ietf.org/dt/12.40.0/ietf/images/ietf-logo-nor-16.png

Emails

1

Links

13