[6tisch] tagging join traffic wih DSCP: why inside IP header?

Thomas Watteyne <thomas.watteyne@inria.fr> Tue, 14 November 2017 06:44 UTC

Return-Path: <thomas.watteyne@inria.fr>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43B40129417 for <6tisch@ietfa.amsl.com>; Mon, 13 Nov 2017 22:44:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] 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 mym1jiDvkFx2 for <6tisch@ietfa.amsl.com>; Mon, 13 Nov 2017 22:44:38 -0800 (PST)
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) (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 66F21127735 for <6tisch@ietf.org>; Mon, 13 Nov 2017 22:44:38 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.44,393,1505772000"; d="scan'208,217";a="244519385"
Received: from mail-vk0-f51.google.com ([209.85.213.51]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 14 Nov 2017 07:44:36 +0100
Received: by mail-vk0-f51.google.com with SMTP id 22so7921827vkq.4 for <6tisch@ietf.org>; Mon, 13 Nov 2017 22:44:36 -0800 (PST)
X-Gm-Message-State: AJaThX7U4328DwXHZ7EqvRv/S4wcKPD5E8Ngj0thZX4kkk4wQUxmGgU+ qcE6o2oKBatPGt/MFMPzsW5MeqP+BpwEmgXcbd4=
X-Google-Smtp-Source: AGs4zMZJVBnFzuzxO80+p5FpJCzBSQFcQH80Hyos02ZLcbfM3zweW8qzq7rmhBlYZtA7bKkxnoZxXfxYA3o/hAxkgk0=
X-Received: by 10.31.106.70 with SMTP id f67mr6171273vkc.3.1510641875380; Mon, 13 Nov 2017 22:44:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.45.143 with HTTP; Mon, 13 Nov 2017 22:44:14 -0800 (PST)
From: Thomas Watteyne <thomas.watteyne@inria.fr>
Date: Tue, 14 Nov 2017 07:44:14 +0100
X-Gmail-Original-Message-ID: <CADJ9OA_cKxWZLvfpNXhjNgL1HurfdK-Oqj1M-wU9pK5t+1kU4g@mail.gmail.com>
Message-ID: <CADJ9OA_cKxWZLvfpNXhjNgL1HurfdK-Oqj1M-wU9pK5t+1kU4g@mail.gmail.com>
To: "6tisch@ietf.org" <6tisch@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0933ac5d7228055debb8c9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/upAVol3Tgo8DHV_8ikvypj3_UYE>
Subject: [6tisch] tagging join traffic wih DSCP: why inside IP header?
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Nov 2017 06:44:40 -0000

Pascal,

During the WG meeting yesterday, we discussed using DSCP bits as a way to
identify join request/reply messages. We talked about mapping, in the
minimal-security spec, the different DSCP values to scheduling behavior.

But you indicated the DSCP bits would be in the inside IPv6 header. That
doesn't make sense to me, can you please provide more info? The outside
IPv6 header looks to me like the right place to put the bits.

Thomas

-- 
_______________________________________

Thomas Watteyne, PhD
Research Scientist & Innovator, Inria
Sr Networking Design Eng, Linear Tech
Founder & co-lead, UC Berkeley OpenWSN
Co-chair, IETF 6TiSCH

www.thomaswatteyne.com
_______________________________________