Re: [Roll] unware leaves --- terminology and expectations
"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 17 September 2019 20:04 UTC
Return-Path: <pthubert@cisco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEDA21208B8 for <roll@ietfa.amsl.com>; Tue, 17 Sep 2019 13:04:54 -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, RCVD_IN_DNSWL_HI=-5, 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 header.b=Bl+bWqxb; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=PENwywG1
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 8tLDCCY-F0RO for <roll@ietfa.amsl.com>; Tue, 17 Sep 2019 13:04:52 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 914E1120072 for <roll@ietf.org>; Tue, 17 Sep 2019 13:04:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2078; q=dns/txt; s=iport; t=1568750692; x=1569960292; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=sGFZK8EWjWc45CluhZNklp+YWJ5wT2kjMcXYczFnvsU=; b=Bl+bWqxb3u6J1cvtGw/bajKmU22WmOmOlQVYhjOwMehBGT559NfEOvei 1DskgcUbAbeJdUffTUnH41GY4SWzKzWIi/XG7X4OLuVCvCtInmC5ftV0l LgOYP/EdP9cT5E8ibzggGEtZmOuRyjPOwDy5smXe1tY/eJ7WgjPWzPHWf c=;
IronPort-PHdr: 9a23:dfwsVR2Rvvr/ATHosmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxKGt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQEVH7MfTndTASF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DVAADeO4Fd/5BdJa1lHAEBAQQBAQcEAQGBVQUBAQsBgURQA21WIAQLKgqEF4NHA4p3TYIPl3KBLoEkA1QJAQEBDAEBGAsKAgEBgUuCdAIXgmUjNgcOAgMJAQEEAQEBAgEFBG2FLgyFSgEBAQMBAQEQEREMAQEqAggEBAsCAQgYAgImAgICJQsVEAIEEyKDAAGBagMODwECAQujagKBOIhhc4Eygn0BAQWCSIJMGIIXAwaBDCgBi3cYgUA/gREnH4IeLj6CYQEBgWGDCzKCJoxqgmeFSZdZCoIilQEbmRqEL6JfAgQCBAUCDgEBBYFZBC2BWHAVOyoBgkGCQgwXg0+FFIU/c4EpjioBgSIBAQ
X-IronPort-AV: E=Sophos;i="5.64,518,1559520000"; d="scan'208";a="632533514"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 17 Sep 2019 20:04:51 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x8HK4pL0006294 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Tue, 17 Sep 2019 20:04:51 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 17 Sep 2019 15:04:51 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 17 Sep 2019 15:04:50 -0500
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 17 Sep 2019 15:04:50 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mJYwR2L8Qivo8BrbbzohaynWPQRTdeXJyyfrK9iEmmOCTzuCMsItCqXuwpGufUuw0IrGDUj9FZSK7neRD0dcIKhg95iwAZp44c9hP38zmJubYOAQxFrJQJShJhpsEarBr/mo/GAa2mjl2tagfQPB8QHtHotzVDSBaol5/HL+39g8bBwvFM3UX8wh2035u06YyF9PXkb7vCyofrPgfoNoTwES6wbEVgayJ6tWY8CUm0D5pGF3+JBRdhQ758pRp1MfXX/HpxF9as0ThFBdXwKXVs0ftSfkEoa5+xqbYetWKQJKt6ALX+bGq07G3vY77pipbiwAevJZg11pna3oKmWBNg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=sGFZK8EWjWc45CluhZNklp+YWJ5wT2kjMcXYczFnvsU=; b=mBrxJyLGdGGew8Ypt66z3U9PvlA6JKwcHuGFksV8vnNVa0EPVgQyQfg3jLCvfWrlO1eiC49PoyWf6sAS0Xc/beEgRy3gOTx+0unJDGd0iLOVbcymgWkQVCt0IZxE72G7WlYcv2lXk2MkgSGtxpOLTsrO74ZC0mi8GeJk7HMHCUnNV5bag8DCp1gOc9o0QzcHz+Rs+zAkY9bYuaQ6FFCvIhUD33x63mNGXu+0fC08WL1j5e+fXiisUn8mOAUHqx83ad2T1CJ9nVBPYvoReRjA2VOEBFqrBybatWykkYvrbVRBYrT1U54ObICoNKDWMy++0OJBzgMOAQrijQgpU3dQqA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
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=sGFZK8EWjWc45CluhZNklp+YWJ5wT2kjMcXYczFnvsU=; b=PENwywG1zRnunPxYTJ6yBdm2tAZerGBK30nnt4TISlBbEQHbzFZINaV5BQmGCEIfYt0rWkCFOixIwDvvTBNzj1uimTr8f88UBssFrq2OVsJrfX7axRjUTrN+oPMXToUlobi+v5BxVAcaZ0G+8cDGN1c8CHSPA/4+sqHAL5RSdig=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB4398.namprd11.prod.outlook.com (52.135.37.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2263.20; Tue, 17 Sep 2019 20:04:49 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::6986:12d5:b54f:f5ee]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::6986:12d5:b54f:f5ee%7]) with mapi id 15.20.2263.023; Tue, 17 Sep 2019 20:04:49 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] unware leaves --- terminology and expectations
Thread-Index: AQHVabgO8hNPEXUEJ0WuVmRkiBF6qKcpegHwgAUYq4CAABUS24ABjyUAgAAb/gU=
Date: Tue, 17 Sep 2019 20:04:49 +0000
Message-ID: <0FB4BDD1-D950-46CA-B585-B2F0CFBA905B@cisco.com>
References: <MN2PR11MB35659CC421169CC79891D1B3D8BB0@MN2PR11MB3565.namprd11.prod.outlook.com> <3940.1567790341@dooku.sandelman.ca> <MN2PR11MB3565016C170EC68801B54ED6D8B70@MN2PR11MB3565.namprd11.prod.outlook.com> <5102.1568314634@dooku.sandelman.ca> <MN2PR11MB3565B466ACDA4AC77BC720A8D8B30@MN2PR11MB3565.namprd11.prod.outlook.com>, <25877.1568654437@localhost> <786C0A95-6D6E-4847-ACBC-B59E312F29BB@cisco.com>, <20887.1568744678@localhost>
In-Reply-To: <20887.1568744678@localhost>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [91.69.164.91]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3ae4c40a-f780-4ef8-6670-08d73baa4bb4
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600167)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR11MB4398;
x-ms-traffictypediagnostic: MN2PR11MB4398:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR11MB439875AEEE15EAFF45D216B3D88F0@MN2PR11MB4398.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01630974C0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(376002)(39860400002)(346002)(136003)(396003)(199004)(189003)(6512007)(256004)(186003)(8676002)(64756008)(66066001)(6486002)(3846002)(6116002)(476003)(6916009)(6506007)(8936002)(14454004)(6246003)(86362001)(99286004)(6436002)(81156014)(102836004)(81166006)(76176011)(66574012)(71200400001)(33656002)(7736002)(36756003)(305945005)(26005)(6306002)(2616005)(966005)(316002)(229853002)(2906002)(71190400001)(446003)(5660300002)(11346002)(486006)(25786009)(478600001)(66946007)(91956017)(76116006)(66476007)(66556008)(66446008); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4398; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: vnsVKlvBh1PxpRShwUUCNAdy5tfED76SaBO+Ucq+m+lI1LYdFocxdf3iWPkZv7+f5MB5GFS0Ynyr6+QJyuoWu5JrtLRvWqe4/uHd5wTj3sYi3K5evZdGtZ/LWiWXxoIn3ehOCrjlO93qnr6lmVjzHrtjU/R6ew4MsuDsgycAuu+AVngsuQNQLsrAP9LMxM63kinRs4BzcP+1mzOPX+vRF3vkZiM0nQl75EuRGuZoEzcgVWRExOAvJaQQvDpRp3G2pI2b9K/VyN5V0Qw5f5KKFNObibXXJ8YutE5UujI1CDIcQ+UsBhxzIuUVnDXQAbF7U8LLfectPhdLz4JKyJTGejA9vIjMvL8rnQkuRIbdSsLENQzULl1X/59iGLyK/2wGXfCatS5ILsgjWS3jEUUF2hyWy84GSPxQUU47lgrtvgM=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3ae4c40a-f780-4ef8-6670-08d73baa4bb4
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Sep 2019 20:04:49.4948 (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-CrossTenant-userprincipalname: EQWblHaFI7b//yi9Pw2DDV2hSzznJy9uZY7dlh9SIpMYdbIWX9hRfVe3N0sctyy4ePDGS+Jf4SqTbCU5NQD5iA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4398
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.30, xch-rcd-020.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/hoE-0tpk7yGH0i7dmhnQk-JQ5Aw>
Subject: Re: [Roll] unware leaves --- terminology and expectations
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 20:04:55 -0000
Actually the draft as it stands does a lot to show that IP in IP to what I call a RUL does not need to happen. The change I’m asking is that if IP in IP is used then it goes to the parent. This is why non storing must always be used. So the thing I call a RUL stays within rfc 8200 / 8504 mandates. I see value in your RAL that inserts the RPI. I did not have a taxonomy for a node that does not send it’s DAOs but still inserts RPIs. Happy to add this guy in out bestiary. Regards, Pascal > Le 17 sept. 2019 à 20:25, Michael Richardson <mcr+ietf@sandelman.ca> a écrit : > > > Pascal Thubert (pthubert) <pthubert@cisco.com> wrote: >> Yes we are trying to accomplish the same thing. >> Note that the RPL data plane the the RxL supports is just following RFC >> 8200. That does not mean any RPL awareness. So I really do not see why >> it would have RPL aware in its name... > > Neither RFC8200 nor RFC8504 mandate that a node must be able to handle > IP{dst=me}headers,IP{dst=me}. > > If we can't handle that in the leaf, then I think we gain nothing by writing this document. > > Further, if an RPL-aware-leaf can insert RPI on outgoing packets, then that > also saves inserting an IPIP header at the first 6LR. > > -- > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works > -= IPv6 IoT consulting =- > > > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll
- [Roll] unware leaves --- terminology and expectat… Michael Richardson
- Re: [Roll] unware leaves --- terminology and expe… Pascal Thubert (pthubert)
- Re: [Roll] unware leaves --- terminology and expe… Pascal Thubert (pthubert)
- Re: [Roll] unware leaves --- terminology and expe… Michael Richardson
- Re: [Roll] unware leaves --- terminology and expe… Pascal Thubert (pthubert)
- Re: [Roll] unware leaves --- terminology and expe… Michael Richardson
- Re: [Roll] unware leaves --- terminology and expe… Pascal Thubert (pthubert)