Internet Engineering Task Force (IETF)                       J. Doe, Ed.
Request for Comments: 0000                                 February 2021
Category: Informational                                                 
ISSN: 2070-1721


                               Test File

Abstract

   This document has an abstract.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are candidates for any level of Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc0000.

Copyright Notice

   Copyright (c) 2021 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Example (from draft-ietf-extra-imap4rev2-30)
   2.  Example (from 8866)
   3.  References
     3.1.  Normative References
     3.2.  Informative References
   Author's Address

1.  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: 
                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

   ----------- (B) using ul empty="true"

   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 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

2.  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

3.  References

3.1.  Normative References

3.2.  Informative References

Author's Address

   John Doe (editor)