[core] Collecting CoAP packet traces
Carsten Bormann <cabo@tzi.org> Mon, 13 November 2017 02:47 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4683712741D for <core@ietfa.amsl.com>; Sun, 12 Nov 2017 18:47:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lBZ1_bDWPq_t for <core@ietfa.amsl.com>; Sun, 12 Nov 2017 18:47:18 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1902127871 for <core@ietf.org>; Sun, 12 Nov 2017 18:47:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id vAD2lAY9015572 for <core@ietf.org>; Mon, 13 Nov 2017 03:47:10 +0100 (CET)
Received: from dhcp-8241.meeting.ietf.org (dhcp-8241.meeting.ietf.org [31.133.130.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3yZw5n3MBNzDWw8; Mon, 13 Nov 2017 03:47:09 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
X-Mao-Original-Outgoing-Id: 532234023.972065-1a985596cf0ac9c4f9ed5f55da1e9bff
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 13 Nov 2017 10:47:04 +0800
Message-Id: <6F0E7754-C9C1-404B-80C2-5A3B8A7677A1@tzi.org>
To: "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/TJ0Gnfc4myOKfvFnDdVC-ogJNqw>
Subject: [core] Collecting CoAP packet traces
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2017 02:47:23 -0000
I’m sitting in the LPWAN meeting, where a header compression technique for CoAP (SCHC) is being designed. When we did similar work in 6LoWPAN, we collected a few packet traces in a central repository that allowed us to evaluate GHC (RFC 7400, see the examples in there). Should we do something similar for real-world CoAP traces? Looking for people interested in organizing this. Grüße, Carsten
- [core] Collecting CoAP packet traces Carsten Bormann