Re: [6lo] [SPF:fail] RE: uncompressed form

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 23 May 2019 13:36 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E3C01200B1; Thu, 23 May 2019 06:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, SPF_PASS=-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 header.b=Hxc82d3H; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=T6+UTjkd
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 BSKwNwiuWfy7; Thu, 23 May 2019 06:36:28 -0700 (PDT)
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 C2CB312008A; Thu, 23 May 2019 06:36:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=34330; q=dns/txt; s=iport; t=1558618588; x=1559828188; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=h7DFBVdyYwA72tALDN44lL5YG+e0mAriWq3d2I2Igco=; b=Hxc82d3HA+5e/Kf9QNaKDreRJ3y4fGdmaPi/7nMHHR9HBqKU/hJtkc8i l7EtJYHLARcU1CcaXJkVpJX4YaRRQ0VIXOHivtiSGRmVtRYKwPyn2wyZ3 TfGb8VPFJJxytS1rHYoQOj7aAXDqLE/jXY9tOSLv8hVptXui/iTp2Pv6I E=;
X-Files: image001.jpg : 7789
IronPort-PHdr: =?us-ascii?q?9a23=3A6/gRYxJ0mME8171xnNmcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeBvKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXFXnLOPgYjYmNM9DT1RiuXq8NBsdFQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AXAAA4oeZc/5hdJa1lGwEBAQEDAQE?= =?us-ascii?q?BBwMBAQGBUQYBAQELAYEOL1ADaVUgBAsohBODRwOEUoojgleGHoMijWmBLhS?= =?us-ascii?q?BEANUAgcBAQEJAQIBAR8OAgEBhEACF4IhIzQJDgEDAQEEAQECAQRtHAyFSgE?= =?us-ascii?q?BAQEDBQ0RAggBEgEBJRIBDwIBCBEEAQEGAQEBChUDAgICBRABCQMCDBQJCAI?= =?us-ascii?q?EDgQBBgIGFIMBgWoDHQECDJtMAoE3iF9xgS+CeQEBBYUIDQuCCAcDBoE0AYd?= =?us-ascii?q?hglKBHheBQD8makeBTi5QPoEXgQNHAoEpBQESASEkBwmCVDKCJok/gWgcgkS?= =?us-ascii?q?EXogihlQDSoVgOgkCgg2FLgEFgSaGHYI2g3yCHoZgE40ni0iJbo0NAgQCBAU?= =?us-ascii?q?CDgEBBYFPOGZxcBWDJ4EXeINwilNygSmKaoJDAQE?=
X-IronPort-AV: E=Sophos;i="5.60,503,1549929600"; d="jpg'145?scan'145,208,217,145";a="561604005"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 May 2019 13:36:25 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x4NDaPxR021841 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 23 May 2019 13:36:25 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 23 May 2019 08:36:24 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 23 May 2019 08:36:24 -0500
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 23 May 2019 08:36:24 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=R4UA/174HOad7OuPFFdJFeKyE8nMXm5qKh5qT8IUoNQ=; b=T6+UTjkdlR+EJHwt9fHiOp3RgDdQYOEbedCM9vEB6SlavOpkUbZtUb+dnIO4TpXHJcP0poKItz2sAWkn620f2MmcXo7lL++scL/EUVytsm6JRh9t2WDi+Am2qzVMXiEd/bKBPl0tdGd/v+tWsQZMYNE0h7CbQymdIu5rW68kg9k=
Received: from BYAPR11MB3558.namprd11.prod.outlook.com (20.178.206.75) by BYAPR11MB2776.namprd11.prod.outlook.com (52.135.228.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1900.18; Thu, 23 May 2019 13:36:23 +0000
Received: from BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::b587:2f5d:3be6:656f]) by BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::b587:2f5d:3be6:656f%7]) with mapi id 15.20.1922.018; Thu, 23 May 2019 13:36:23 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Lijo Thomas <lijo@cdac.in>
CC: "draft-ietf-6lo-deadline-time@ietf.org" <draft-ietf-6lo-deadline-time@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: [6lo] [SPF:fail] RE: uncompressed form
Thread-Index: AQHVEWm7qCKKTwI11US8FAKAcBqwMqZ4tTeA
Date: Thu, 23 May 2019 13:34:59 +0000
Deferred-Delivery: Thu, 23 May 2019 13:34:32 +0000
Message-ID: <BYAPR11MB3558116BE1473911F84262D5D8010@BYAPR11MB3558.namprd11.prod.outlook.com>
References: <MN2PR11MB35653193798C9BA9DD1525A7D8010@MN2PR11MB3565.namprd11.prod.outlook.com> <CADnDZ8_aBKp0yH22K0HiRPPZUrjcqJ2vezKpXjdd+tGwMvobpA@mail.gmail.com> <BYAPR11MB35580DE13386308CD7B2698ED8010@BYAPR11MB3558.namprd11.prod.outlook.com> <000001d51169$ac4048b0$04c0da10$@cdac.in>
In-Reply-To: <000001d51169$ac4048b0$04c0da10$@cdac.in>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [2001:420:c0c0:1007::229]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 575468a9-0407-439a-0209-08d6df83a5a4
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(49563074)(7193020); SRVR:BYAPR11MB2776;
x-ms-traffictypediagnostic: BYAPR11MB2776:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BYAPR11MB2776EF56682CA2391A9A878ED8010@BYAPR11MB2776.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 00462943DE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(366004)(396003)(376002)(39860400002)(346002)(51444003)(189003)(199004)(4326008)(81166006)(236005)(25786009)(8936002)(99286004)(7696005)(9686003)(966005)(6116002)(790700001)(14454004)(71190400001)(6666004)(71200400001)(66946007)(64756008)(66446008)(66556008)(73956011)(76116006)(74316002)(66476007)(66616009)(2906002)(86362001)(52536014)(5660300002)(7736002)(478600001)(46003)(14444005)(6506007)(11346002)(486006)(476003)(81156014)(8676002)(102836004)(33656002)(68736007)(76176011)(256004)(53546011)(446003)(6436002)(733005)(316002)(6246003)(229853002)(54556002)(53936002)(55016002)(6306002)(54896002)(99936001)(186003)(6916009)(54906003)(606006); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2776; H:BYAPR11MB3558.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Btakdbo5NkNaR96hYd58utqC2c8wAICfbnrDDVaoRBwDGtqa49o5n5QmIo12oSAOKrrE3O8ajCUgNPNzQbi9Syie8IVMBGXJB79KhvUqjqasDAgklvjlBnr/90aZerjpfgTD6ZmaoTy0YUI1xADYCpazpMsxkQE+VOSkaLjREYdZ1LNvXmuzUUHXRMMQh5H1O/JNQOAlR5IFVgLXcLaRLTudz52F7gSzf5+wR6H5B+7His67PjtzQiyEbRdG2hj3osqMvOmdZRE7vsOBCdSWASts0DO5ythFb+UlN9tqItexbConzo/822WupHQOIqi7kxYVhRTDovhao4Z/ZbzI9+XAlPUErEMGidL1UFSJ50i2RF79EuDKhYIkZbSLOlmLHwz01nlwuV/qTQbvIIwWagv0IYcogfNsgd7jha9vGxc=
Content-Type: multipart/related; boundary="_004_BYAPR11MB3558116BE1473911F84262D5D8010BYAPR11MB3558namp_"; type="multipart/alternative"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 575468a9-0407-439a-0209-08d6df83a5a4
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2019 13:36:23.1273 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2776
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/f9ZwdZ09wagglhGHr134syAm8Vg>
Subject: Re: [6lo] [SPF:fail] RE: uncompressed form
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2019 13:36:36 -0000

Great!

Point is you need to provide the format of the uncompressed form so the root can uncompress and forward.

All the best,

Pascal

From: 6lo <6lo-bounces@ietf.org>; On Behalf Of Lijo Thomas
Sent: jeudi 23 mai 2019 15:16
To: Pascal Thubert (pthubert) <pthubert@cisco.com>;
Cc: draft-ietf-6lo-deadline-time@ietf.org; 'Abdussalam Baryun' <abdussalambaryun@gmail.com>;; 6lo@ietf.org
Subject: Re: [6lo] [SPF:fail] RE: uncompressed form

Hi Pascal,

Thanks for your inputs.

The draft specifies variable length deadline-time representation, only required no. of bits to be carried and no compression methods are followed . The current revision is capable of carrying deadline time in ntp format also.

We envisaged to use dispatch routing header for transporting deadline time.

We agree your point that once the packet leaves the RPL network, then the deadline information has to be carried in hop-by-hop header. In fact we mentioned required text for calculating deadline time, while traversing  through different time zones.

  Thanks & Regards,
  Lijo Thomas

From: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>
Sent: 23 May 2019 17:38
To: Abdussalam Baryun <abdussalambaryun@gmail.com<mailto:abdussalambaryun@gmail.com>>
Cc: draft-ietf-6lo-deadline-time@ietf.org<mailto:draft-ietf-6lo-deadline-time@ietf.org>; 6lo@ietf.org<mailto:6lo@ietf.org>
Subject: [SPF:fail] RE: [6lo] uncompressed form

Dear all

The use case is when the data sync is not in the RPL domain or the packet has to fly outside the RPL domain. E.g., A PLC virtualized in a MEC. The root needs to uncompress the packet and forward. The draft is missing the uncompressed form.

All the best,

Pascal

From: Abdussalam Baryun <abdussalambaryun@gmail.com<mailto:abdussalambaryun@gmail.com>>
Sent: jeudi 23 mai 2019 13:31
To: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>
Cc: draft-ietf-6lo-deadline-time@ietf.org<mailto:draft-ietf-6lo-deadline-time@ietf.org>; 6lo@ietf.org<mailto:6lo@ietf.org>
Subject: Re: [6lo] uncompressed form



On Thu, May 23, 2019 at 7:54 AM Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Dear all:

I was rereading deadline and realized that the draft does not provide an umcompressed form. What of the packet flies beyond the RPL domain? I think the information should be useful there too.

why useful? could you explain the use case?

Also we always claimed that RFC8138 is an encoding and that we can always turn a packet to uncompressed and back. Deadline creates an exception to that rule, which changes RFC 8138 into a sub IP protocol as opposed to a compression.
All in all, I think that an IPv6 header (e.g., a new option in a hop-by-hop header) should be provided, even if for now it appears to be for completeness only.

What do others think?

I need to know the use case.

Best regards,
AB






[150th Anniversary Mahatma Gandhi]
------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
------------------------------------------------------------------------------------------------------------