Re: [6lo] recoverable fragments: use page 1
Michael Richardson <mcr+ietf@sandelman.ca> Tue, 21 May 2019 13:49 UTC
Return-Path: <mcr+ietf@sandelman.ca>
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 91547120260 for <6lo@ietfa.amsl.com>; Tue, 21 May 2019 06:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 4FMxvRfXS-yp for <6lo@ietfa.amsl.com>; Tue, 21 May 2019 06:49:34 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04208120265 for <6lo@ietf.org>; Tue, 21 May 2019 06:49:33 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 84DC338279; Tue, 21 May 2019 09:48:39 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 4BFA4D93; Tue, 21 May 2019 09:49:31 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 4740C85; Tue, 21 May 2019 09:49:31 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
cc: "6lo@ietf.org" <6lo@ietf.org>, Laurent Toutain <laurent.toutain@imt-atlantique.fr>
In-Reply-To: <MN2PR11MB3565E8D7F8A43817D5436AE4D8070@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <MN2PR11MB3565E8D7F8A43817D5436AE4D8070@MN2PR11MB3565.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 21 May 2019 09:49:31 -0400
Message-ID: <10563.1558446571@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/Bbo4QvQJVAqQpzwViDf8EhqVJrk>
Subject: Re: [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:49:43 -0000
Pascal Thubert (pthubert) <pthubert@cisco.com> wrote: > During the review by Laurent, a question came up on whether we could use page > 1 for fragments. This implies to me that we'd allocate code points for fragments from page 1. > 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 exactly does it mean to support page 1? Duplicate code points? Starting in page 1 mode for fragments? Allocating all fragment code points from page 1? Maybe we should have a document about source routing fragments end to end for projected DAO, and then we can see the full picture. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [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)