| Internet-Draft | ((TO BE COMPLETED)) | June 2025 |
| Gallagher | Expires 27 December 2025 | [Page] |
This document specifies ((TO BE COMPLETED))¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at ((GITLAB PAGE URL)). Status information for this document may be found at https://datatracker.ietf.org/doc/draft-gitlab-template/.¶
Source for this draft and an issue tracker can be found at ((REPO URL)).¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 27 December 2025.¶
Copyright (c) 2025 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
((TO BE COMPLETED))¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
This document uses Kramdown-rfc2629 format.
Put one sentence per line, this makes git diff work better.
You can refer to an anchor link (such as a section or table) using Section 3.
You can refer to a normative or informative document using [RFC4880], [SHAMBLES].¶
| Field | Description |
|---|---|
| version | the version of this output format |
| count | the number of items |
This section contains some sample text for testing the reflow script.¶
This is a list.¶
This is a sub-list.¶
This is a multiline list entry. Multiline items should have their continuation lines indented like this.¶
This is also a list.¶
This is also a sub-list.¶
The same rules apply to lists with different kinds of bulletpoints. For example, multi-line items should also work.¶
This is a numbered list.¶
Numbered list bulletpoints should not be line-split.¶
Even if they get the numbering wrong.¶
Common abbreviation such as e.g. and i.e. should not cause a line-split. Nor should names like Phil R. Zimmermann or John Q. Public.¶
Exclamations should also be handled gracefully! What about questions? Them too.¶
What if e.g. a question ends with a single letter such as A? Exclamations can also end with A! And sometimes a sentence ends with A. All the above should work.¶
((TO BE COMPLETED))¶
This document assigns the following identifiers: ((TO BE COMPLETED))¶
The authors would like to thank ((TO BE COMPLETED)).¶