datatracker.ietf.org/doc/html/rfc4884

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

Linked Hostnames

4

Thumbnail

Search Engine Appearance

Google

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

RFC 4884: Extended ICMP to Support Multi-Part Messages

Extended ICMP to Support Multi-Part Messages (RFC 4884, )



Bing

RFC 4884: Extended ICMP to Support Multi-Part Messages

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

Extended ICMP to Support Multi-Part Messages (RFC 4884, )



DuckDuckGo

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

RFC 4884: Extended ICMP to Support Multi-Part Messages

Extended ICMP to Support Multi-Part Messages (RFC 4884, )

  • General Meta Tags

    12
    • title
      RFC 4884 - Extended ICMP to Support Multi-Part Messages
    • charset
      utf-8
    • X-UA-Compatible
      IE=edge
    • viewport
      width=device-width, initial-scale=1
    • description
      Extended ICMP to Support Multi-Part Messages (RFC 4884, )
  • Open Graph Meta Tags

    10
    • og:title
      RFC 4884: Extended ICMP to Support Multi-Part Messages
    • og:url
      https://datatracker.ietf.org/doc/html/rfc4884
    • og:site_name
      IETF Datatracker
    • og:description
      This document redefines selected ICMP messages to support multi-part operation. A multi-part ICMP message carries all of the information that ICMP messages carried previously, as well as additional information that applications may require. Multi-part messages are supported by an ICMP extension structure. The extension structure is situated at the end of the ICMP message. It includes an extension header followed by one or more extension objects. Each extension object contains an object header and object payload. All object headers share a common format. This document further redefines the above mentioned ICMP messages by specifying a length attribute. All of the currently defined ICMP messages to which an extension structure can be appended include an "original datagram" field. The "original datagram" field contains the initial octets of the datagram that elicited the ICMP error message. Although the original datagram field is of variable length, the ICMP message does not include a field that specifies its length. Therefore, in order to facilitate message parsing, this document allocates eight previously reserved bits to reflect the length of the "original datagram" field. The proposed modifications change the requirements for ICMP compliance. The impact of these changes on compliant implementations is discussed, and new requirements for future implementations are presented. This memo updates RFC 792 and RFC 4443. [STANDARDS-TRACK]
    • og:type
      article
  • Twitter Meta Tags

    1
    • twitter:card
      summary_large_image
  • Link Tags

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

Emails

5
  • rbonica%40juniper.net
  • dhg%40juniper.net
  • cpignata%40gmail.com
  • dan.tappan%40gmail.com
  • [email protected]?subject=rfc4884

Links

28