Skip to content

Could boilerplate be moved to the end of the RFC? #53

@ajeanmahoney

Description

@ajeanmahoney

Is the boilerplate fixed? Could it be moved to the end of the RFC so that the reader can access technical information more quickly, or is it fixed due to legal considerations?

Current placement guidance

Trust Legal Provisions 5 says:

  1. Text To Be Included in IETF Documents. The following text must be included in each IETF Document as specified below. The IESG shall specify the manner and location of such text for Internet-Drafts. The RFC Editor shall specify the manner and location of such text for RFCs. The copyright notice specified in 6.b below shall be placed so as to give reasonable notice of the claim of copyright.

RFC Style Guide lists the order of required sections.

Some history

The boilerplate used to be placed on the last page of the RFC per RFC 2223, but during the subsequent revision of RFC 2223 (draft-rfc-editor-rfc2223bis, portions of which were in force before its eventual replacement by RFC 7322), it was moved to where it is today.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions