[6lo] recoverable fragments: use page 1
"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 21 May 2019 13:11 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 349B51201FA for <6lo@ietfa.amsl.com>; Tue, 21 May 2019 06:11:25 -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=NNl0yWyI; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=RskGbJFD
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 aoaVFrbNP9Vo for <6lo@ietfa.amsl.com>; Tue, 21 May 2019 06:11:22 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5349612016F for <6lo@ietf.org>; Tue, 21 May 2019 06:11:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3187; q=dns/txt; s=iport; t=1558444282; x=1559653882; h=from:to:subject:date:message-id:mime-version; bh=sUBPa/d03Br4Uo6E1NuAOiPpLbnJuyf030HvYwnhvF0=; b=NNl0yWyIhU9JdGxlCHXpZ9xcd9Q6cDBaxIUKsIdMfH4EMb36ifMKQq+i QeRM/u+D7ZeoG1dyBnWabtZnaycLpBDsQYr5rkDE/SPIfakEI9p9wz9MQ Yb23esoFkZ+zhY6n5Ua7iQ3dvK6bLyoM5Yq3p81dQw/nfAyawnqI3MmT6 w=;
IronPort-PHdr: 9a23:Qd8q4RLZIXkqtWTyA9mcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeBvKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXFXnLOPgYjYmNM9DT1RiuXq8NBsdFQ==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ChAAD09+Nc/5xdJa1lHAEBAQQBAQcEAQGBUwUBAQsBgQ4vUANpVSAECyiHWgOOdJIzgn2EToEuFIEQA1QJAQEBDAEBLQIBAYRAAoImIzYHDgEDAQEEAQECAQRtHAyFYxsTAQE4EQEMdCYBBAEaGoMBgR1NAx0BApteAoE1iF+CIIJ5AQEFhQYYgg8JgTQBi1AXgUA/gVeCTD6EDDqDOoImkliVTwkCgg2MboYtliyMVpVIAgQCBAUCDgEBBYFWCSiBV3AVgyeCD4NvilNygSmNEwEB
X-IronPort-AV: E=Sophos;i="5.60,495,1549929600"; d="scan'208,217";a="565557566"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 May 2019 13:11:20 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x4LDBJcP007138 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 21 May 2019 13:11:20 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 21 May 2019 08:11:19 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 21 May 2019 09:11:17 -0400
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 21 May 2019 08:11:16 -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=AcPlRpxFrQWfDoNvJAthex+c2v2kFl5tza2Wqi31uG8=; b=RskGbJFDyaACbjL/chqoO0OxnFBC5FN03umfxFKC1kl/k2oT2e2056KMGYWzIQzquhnxyHUwTs/BOQSgxxjysC1ITnOFC2mbmECmY0jxo2GMZAvIQsM3tsUWSRIffCbzBQt1sKlgKn/vNv/x4TZTKo6eAl4aEHvnjZl02arypDY=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3808.namprd11.prod.outlook.com (20.178.254.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1900.17; Tue, 21 May 2019 13:11:16 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::7cc2:b440:8820:f0fc]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::7cc2:b440:8820:f0fc%7]) with mapi id 15.20.1900.020; Tue, 21 May 2019 13:11:16 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "6lo@ietf.org" <6lo@ietf.org>, Laurent Toutain <laurent.toutain@imt-atlantique.fr>
Thread-Topic: recoverable fragments: use page 1
Thread-Index: AdUP1gzlIrZMHym8RcaRfjXlYt4JtA==
Date: Tue, 21 May 2019 13:10:50 +0000
Deferred-Delivery: Tue, 21 May 2019 13:09:59 +0000
Message-ID: <MN2PR11MB3565E8D7F8A43817D5436AE4D8070@MN2PR11MB3565.namprd11.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [2001:420:44f3:1300:552f:ff32:b86:aad7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 59536fc3-313b-40c0-580f-08d6ddedce94
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:MN2PR11MB3808;
x-ms-traffictypediagnostic: MN2PR11MB3808:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB3808D71D06635F7B1354F64CD8070@MN2PR11MB3808.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 0044C17179
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(376002)(346002)(136003)(396003)(366004)(189003)(199004)(9686003)(110136005)(14454004)(54896002)(68736007)(55016002)(46003)(66446008)(6116002)(316002)(76116006)(186003)(73956011)(66946007)(53936002)(6306002)(6436002)(33656002)(478600001)(2501003)(7736002)(256004)(64756008)(99286004)(5660300002)(4744005)(86362001)(6506007)(476003)(486006)(2906002)(52536014)(102836004)(74316002)(81156014)(81166006)(66556008)(71200400001)(25786009)(8936002)(7696005)(71190400001)(66476007)(8676002)(6666004)(790700001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3808; H:MN2PR11MB3565.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: MWx6Cb8WDxZM8yxqtkPX0vshEMVGott1NmsfyTxFbneQ0W7xuUWDI2mP7GAbUfgR8klfK1H7HwPqYxwBIR2cqL9kERjWKzgOtlu6AmbH4TZenkGUhRyHSCJKvsXjRndaoIhiGACs+rG2kZRr9UZb8dkOnnQCqd0ZTEidffluCusXfVIubwXwJUlXd3H5YuMRbwRpgp/9/ZuWykQryxYGwns4vBqAaeYtyFDxqSgmNJwzPdcUBf2Y0Lt6Y1IiApx2Yn52PrIFwkJv7HxUUQ/zVlh7BjULj+1mk2i3iQEtMsPEwZfhjA/r8dumMh99AGEdC3nZlu4IZ9g/RQ93Jk6nRYB8p0hhwPWvlsCq57WuKJenU9/u4HOznt1nw2OkGgKI9kr4QayES9GDdboTAGiF2NMsjDD2LBL/fGHZjluKhYI=
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB3565E8D7F8A43817D5436AE4D8070MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 59536fc3-313b-40c0-580f-08d6ddedce94
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 May 2019 13:11:16.0460 (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: MN2PR11MB3808
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.22, xch-aln-012.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/IGn2omkneXI2A5o42WOSf7t8OVU>
Subject: [6lo] recoverable fragments: use page 1
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: Tue, 21 May 2019 13:11:31 -0000
Dear all: During the review by Laurent, a question came up on whether we could use page 1 for fragments. At the moment the fragment is always before the 6lo routing header so there is no point. But say that we source route the fragments end to end with a 6loRH, e.g., for projected DAO. Then supporting page 1 as well would save a page switch. What do you all think? Pascal
- [6lo] recoverable fragments: use page 1 Pascal Thubert (pthubert)
- Re: [6lo] recoverable fragments: use page 1 Michael Richardson
- Re: [6lo] recoverable fragments: use page 1 Pascal Thubert (pthubert)