Last Call: <draft-ietf-lpwan-coap-static-context-hc-12.txt> (LPWAN Static Context Header Compression (SCHC) for CoAP) to Proposed Standard

The IESG <> Thu, 06 February 2020 20:11 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id A568C120106; Thu, 6 Feb 2020 12:11:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Last Call: <draft-ietf-lpwan-coap-static-context-hc-12.txt> (LPWAN Static Context Header Compression (SCHC) for CoAP) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.117.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <>
CC:,, Pascal Thubert <>,,,
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <>
Date: Thu, 06 Feb 2020 12:11:17 -0800
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 06 Feb 2020 20:11:18 -0000

The IESG has received a request from the IPv6 over Low Power Wide-Area
Networks WG (lpwan) to consider the following document: - 'LPWAN Static
Context Header Compression (SCHC) for CoAP'
  <draft-ietf-lpwan-coap-static-context-hc-12.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the mailing lists by 2020-02-20. Exceptionally, comments may
be sent to instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.


   This draft defines the way SCHC header compression can be applied to
   CoAP headers.  The CoAP header structure differs from IPv6 and UDP
   protocols since CoAP uses a flexible header with a variable number of
   options, themselves of variable length.  The CoAP protocol messages
   format is asymmetric: the request messages have a header format
   different from the one in the response messages.  This document
   explains how to use the SCHC compression mechanism for CoAP.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc7967: Constrained Application Protocol (CoAP) Option for No Server Response (Informational - Independent Submission Editor stream)