RFC Process - redengin/enmesh GitHub Wiki

The internet evolved via RFC managed by the Internet Engineering Task Force (IETF) which is an open community

The overall goal of the IETF is to make the Internet work better. Its mission is to produce high quality, relevant technical and engineering documents that influence the way people design, use, and manage the Internet in such a way as to make the Internet work better. These documents include protocol standards, best current practices, and informational documents of various kinds. - RFC 3935: A Mission Statement for the IETF

To mature LoRa, we should engage with the IETF to leverage their knowledge.

Proposing a new RFC

Rather than over-stress the IETF, we handle proposals here - organically readying them for IETF review.

RFC Submission Process

LoRa RFCs

To coordinate proposals toward gaining IESG role, this wiki is used to curate proposals.

  • Active (current RFCs accepted as standards)

    • RFC-8376 [Informational] - Low-Power Wide Area Network (LPWAN) Overview
    • RFC-8724 [Proposed] - SCHC: Generic Framework for Static Context Header Compression and Fragmentation
    • RFC-8824 [Proposed] - Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)
    • RFC-9011 [Proposed] - Static Context Header Compression and Fragmentation (SCHC) over LoRaWAN
    • RFC-9441 [Proposed] - Static Context Header Compression (SCHC) Compound Acknowledgement (ACK)
    • RFC-9442 [Proposed] - Static Context Header Compression (SCHC) over Sigfox Low-Power Wide Area Network (LPWAN)
  • Drafts (locally curated proposals)

  • Proposed (sent to IETF upon community consensus)

    • None