Test File
This document has an abstract.
Example (from draft-ietf-extra-imap4rev2-30)
-------------- using br
- Arguments:
- user name
password
- Responses:
- no specific responses for this command
- Result:
-
- OK
- - login completed, now in authenticated state
- NO
- - login failure: user name or password rejected
- BAD
- - command unknown or arguments invalid
-------------- using t
- Arguments:
-
user name
password
- Responses:
- no specific responses for this command
- Result:
-
- OK
- - login completed, now in authenticated state
- NO
- - login failure: user name or password rejected
- BAD
- - command unknown or arguments invalid
--------------- (A) using ul empty="true" bare="true"
- Arguments:
-
- Responses:
- no specific responses for this command
- Result:
-
- OK
- - login completed, now in authenticated state
- NO
- - login failure: user name or password rejected
- BAD
- - command unknown or arguments invalid
----------- (B) using ul empty="true"
- Arguments:
-
- Responses:
- no specific responses for this command
- Result:
-
- OK
- - login completed, now in authenticated state
- NO
- - login failure: user name or password rejected
- BAD
- - command unknown or arguments invalid
--------------- using ul empty="true" bare="true"
- Arguments:
- mailbox name
- Responses:
-
- REQUIRED untagged responses: FLAGS, EXISTS, LIST
-
REQUIRED OK untagged responses: PERMANENTFLAGS, UIDNEXT, UIDVALIDITY
- Result:
-
- OK
- - select completed, now in selected state
- NO
- - select failure, now in authenticated state: no such mailbox, can't access mailbox
- BAD
- - command unknown or arguments invalid
--------------- using ul empty="true" bare="true"
- Arguments (basic):
-
- reference name
- mailbox name with possible wildcards
- Arguments (extended):
-
- selection options (OPTIONAL)
- reference name
- mailbox patterns
- return options (OPTIONAL)
- Responses:
- untagged responses: LIST
- Result:
-
- OK
- - list completed
- NO
- - list failure: can't list that reference or mailbox name
- BAD
- - command unknown or arguments invalid
Example (from 8866)
- Type name:
- application
- Subtype name:
- sdp
- Required parameters:
- None.
- Optional parameters:
- None.
- Encoding considerations:
- 8-bit text.
SDP files are primarily UTF-8 format text. The "a=charset:"
attribute may be used to signal the presence of other character
sets in certain parts of an SDP file (see x of RFC
8866). Arbitrary binary content cannot be directly
represented in SDP.
- Security considerations:
-
See y of RFC 8866.
- Interoperability considerations:
-
See RFC 8866.
- Published specification:
-
See RFC 8866.
- Applications which use this media type:
Voice over IP, video teleconferencing, streaming media, instant
messaging, among others. See also y of RFC 8866.- Fragment identifier considerations:
- None
- Additional information:
- Deprecated alias names for this type:
- N/A
- Magic number(s):
- None.
- File extension(s):
- The extension ".sdp" is commonly used.
- Macintosh File Type Code(s):
- "sdp"
- Person & email address to contact for further information:
IETF MMUSIC working group
<mmusic@ietf.org>- Intended usage:
- COMMON
- Restrictions on usage:
- None
- Author/Change controller: [using br]
Authors of RFC 8866
IETF MMUSIC working group delegated from the IESG
- Author/Change controller: [using ul]
- Authors of RFC 8866
- IETF MMUSIC working group delegated from the IESG
References
Normative References
Informative References