| inline |
displayed automatically |
[RFC2183] |
| attachment |
user controlled display |
[RFC2183] |
| form-data |
process as form response |
[RFC7578] |
| signal |
tunneled content to be processed silently |
[RFC3204] |
| alert |
the body is a custom ring tone to alert the
user |
[RFC3261] |
| icon |
the body is displayed as an icon to the user |
[RFC3261] |
| render |
the body should be displayed to the user |
[RFC3261] |
| recipient-list-history |
the body contains a list of URIs that
indicates the recipients of the request |
[RFC5364] |
| session |
the body describes a communications session,
for example, an RFC2327 SDP body |
[RFC3261] |
| aib |
Authenticated Identity Body |
[RFC3893] |
| early-session |
the body describes an early communications
session, for example, and [RFC2327] SDP body |
[RFC3959] |
| recipient-list |
The body includes a list of URIs to which
URI-list services are to be applied. |
[RFC5363] |
| notification |
the payload of the message carrying this
Content-Disposition header field value is
an Instant Message Disposition Notification
as requested in the corresponding Instant
Message. |
[RFC5438] |
| by-reference |
The body needs to be handled according to a
reference to the body that is located in
the same SIP message as the body. |
[RFC5621] |
| info-package |
The body contains information associated with an
Info Package |
[RFC6086] |
| recording-session |
The body describes either metadata about the RS or the reason
for the metadata snapshot request as determined by the MIME
value indicated in the Content-Type. |
[RFC7866] |