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

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 16 November 2017 00:05 UTC

Return-Path: <pthubert@cisco.com>
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 0112B128656 for <6tisch@ietfa.amsl.com>; Wed, 15 Nov 2017 16:05:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level:
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 SZlYf-NqWlGf for <6tisch@ietfa.amsl.com>; Wed, 15 Nov 2017 16:04:58 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 475B6126CF6 for <6tisch@ietf.org>; Wed, 15 Nov 2017 16:04:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4349; q=dns/txt; s=iport; t=1510790698; x=1512000298; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=UP9GYZwEAr70Q8SIv4nICYrKXlYchdsAwaHBtv3tVuA=; b=RlIHq1awGeF99ezUSC/D30GMWbv0g2P8RBdSVQLHvPqO2t63M6K6Ftlk mdHTH2o4DRWFsHs/a38aMCN9NzepFI+aUDWm32q9O+bCldjcqo4j0ua+T N2yhVTiLGfi04itIzMxWsE96rHrSMAsERmPrrLt1n6mOTyvvxZ8jLbZjQ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DxAACx1Qxa/4YNJK1eGQEBAQEBAQEBAQEBAQcBAQEBAYM2gVIng3+KH48ggVeROoVJEIIBCoIBgzoCGoR0PxgBAQEBAQEBAQFrKIUfBiNWEAIBCAQ7AwICAjAUEQIEDgWJQGSpe4InixABAQEBAQEBAQEBAQEBAQEBAQEBAQEdgzSCB4FVgWkpC4J2hQCDLTGCMgWiNwKVBJNElgECERkBgTgBHziBdHoVdgGCNoJcHIFnd4saAQEB
X-IronPort-AV: E=Sophos;i="5.44,401,1505779200"; d="scan'208,217";a="319319222"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 Nov 2017 00:04:44 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id vAG04ipP009581 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 16 Nov 2017 00:04:44 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 15 Nov 2017 18:04:43 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1320.000; Wed, 15 Nov 2017 18:04:43 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: Thomas Watteyne <thomas.watteyne@inria.fr>, "6tisch@ietf.org" <6tisch@ietf.org>
Thread-Topic: [6tisch] tagging join traffic wih DSCP: why inside IP header?
Thread-Index: AQHTXX7XkXA3VPJ770+1uJQzOJ8GOaMUpmAwgADiMID//5+aMIAAfJ0AgACraoD//9HUJA==
Date: Thu, 16 Nov 2017 00:04:43 +0000
Message-ID: <4794F61D-EE1C-4D39-8225-31546ACC8F38@cisco.com>
References: <CADJ9OA_cKxWZLvfpNXhjNgL1HurfdK-Oqj1M-wU9pK5t+1kU4g@mail.gmail.com> <20396.1510678103@obiwan.sandelman.ca> <32033.1510687749@obiwan.sandelman.ca> <92bca0456cb746c995733131edad10a2@XCH-RCD-001.cisco.com> <CADJ9OA_b2fHUg=3utnCv8iTMZcwL-n3J_H2N6uU=v8SjenjmFA@mail.gmail.com> <361109c852ca4d8e983f19899648c811@XCH-RCD-001.cisco.com> <CADJ9OA-JgzSpDKSbZ=7P91beoThvVh+0_HgLvVRiaWMhHmv+iQ@mail.gmail.com>, <32611.1510778999@obiwan.sandelman.ca>
In-Reply-To: <32611.1510778999@obiwan.sandelman.ca>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_4794F61DEE1C4D39822531546ACC8F38ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/rrKIcDkCVYMzqOTl6QR1u4WHQMY>
Subject: Re: [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: Thu, 16 Nov 2017 00:05:00 -0000

Hello Michael:

Could we leverage the use of RPL information draft to indicate that the RPL info can be safely removed on RPL packets outgoing the domain ? I think that would pass.

We can also indicate that insertion in allowed on incoming packets and see what pushback we get now.

This would avoid having too many flag days as the rules become more realistic. The times they are a-changing..,

Pascal

Le 16 nov. 2017 à 04:50, Michael Richardson <mcr+ietf@sandelman.ca<mailto:mcr+ietf@sandelman.ca>> a écrit :


Thomas Watteyne <thomas.watteyne@inria.fr<mailto:thomas.watteyne@inria.fr>> wrote:
You're saying that I can be exchanging data between motes in the mesh
and hosts on the Internet, while inserting/deleting RPI and RPL routing
headers en-route, i.e. without IPIP?

We did not say that in useofrplinfo!

Pascal is, I think, overstating the compromise/ambiguous text in RFC8200.


--
Michael Richardson <mcr+IETF@sandelman.ca<mailto:mcr+IETF@sandelman.ca>>, Sandelman Software Works
-= IPv6 IoT consulting =-