Re: [6lo] Advocating a generalization of RFC8505 to non-6lo LANs

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 08 July 2019 15:06 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 4CD4412018A; Mon, 8 Jul 2019 08:06:12 -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=PvM6jjpt; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=KyXyuwFL
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 4nnYgZcnRJNY; Mon, 8 Jul 2019 08:06:09 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3138120221; Mon, 8 Jul 2019 08:05:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2020; q=dns/txt; s=iport; t=1562598344; x=1563807944; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hg7xvtcpeynrYClSC+UDzbmgtXb/t+R3EukyfGRwTFQ=; b=PvM6jjptgV8PdU4uAR1NLXl26DauxfCiu45CQrDGqJlKN2mJOmRNDRmK oaOTMKUD9bLtx6XjcbOrZd2/NKospNvcreDD76stnJ+SH6r85XgRn5nbu n31DpPTRHyWUb8EVYGLYkp0qF44P62Sxuzv4AdJj/5gOiSpWk8y8dUG2o w=;
IronPort-PHdr: =?us-ascii?q?9a23=3AL64VoBfhcRdg+4Nvu1mZPt21lGMj4e+mNxMJ6p?= =?us-ascii?q?chl7NFe7ii+JKnJkHE+PFxlwGQD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFn?= =?us-ascii?q?pnwd4TgxRmBceEDUPhK/u/dzA6Ac5PTkNN9HCgOk8TE8H7NBXf?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AIAABKWyNd/49dJa1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUwUBAQEBCwGBQ1ADgT8gBAsohByDRwOEUol2gluJTY15gS6?= =?us-ascii?q?BJANUCQEBAQwBAS0CAQGEQAIXgiEjNAkOAQMBAQQBAQIBBW2KNwyFSgEBAQE?= =?us-ascii?q?DEhERDAEBKwwBCwQCAQYCDgMEAQEBAgImAgICHxEVCAgCBA4FCBqEawMdAQK?= =?us-ascii?q?OH5BgAoE4iGBxgTKCeQEBBYR6DQuCEgmBDCgBhHGGbReBQD+BV4IeLj6BBIE?= =?us-ascii?q?WgiyDCDKCJo5wmyZACQKCF5ARhA6XfpZjjgoCBAIEBQIOAQEFgVA4gVhwFTu?= =?us-ascii?q?CbIJBg3GKU3KBKY1IAQE?=
X-IronPort-AV: E=Sophos;i="5.63,466,1557187200"; d="scan'208";a="591287212"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Jul 2019 15:05:24 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id x68F5OCJ011969 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 8 Jul 2019 15:05:24 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 8 Jul 2019 10:05:23 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 8 Jul 2019 11:05:13 -0400
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 8 Jul 2019 11:05:13 -0400
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=hg7xvtcpeynrYClSC+UDzbmgtXb/t+R3EukyfGRwTFQ=; b=KyXyuwFLhJwZVlNYfbmcJOV5t0ZiAQBvMxeFGWjp3Nv0eHD5wMdjbikk5zy34waYxefnPIQFR9tZqbcPNHRHLxcKU421QAF26lOl2vOoeaJrhY2trC5yJh4F4EmsxCcnStKWDIBoDkPVMl1uFVhCRBIckgJ3meF0LdYSsHR6DfE=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3952.namprd11.prod.outlook.com (10.255.181.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.19; Mon, 8 Jul 2019 14:31:51 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::1ce9:1582:146c:c50a]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::1ce9:1582:146c:c50a%6]) with mapi id 15.20.2052.020; Mon, 8 Jul 2019 14:31:51 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Carsten Bormann <cabo@tzi.org>
CC: Mark Smith <markzzzsmith@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>, 6man <6man@ietf.org>, V6 Ops List <v6ops@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: [6lo] Advocating a generalization of RFC8505 to non-6lo LANs
Thread-Index: AdUyXLsjbUS9G1zfTQuzwoWpAiUtYQACLMYAAAC/GgAATi6UAAB5DMJQAAGdWgAAAAZqIA==
Date: Mon, 8 Jul 2019 14:31:27 +0000
Deferred-Delivery: Mon, 8 Jul 2019 12:54:09 +0000
Message-ID: <MN2PR11MB3565024FB59678424C230307D8F60@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <MN2PR11MB3565AC3DE6B4480D296D500FD8FA0@MN2PR11MB3565.namprd11.prod.outlook.com> <CAO42Z2y50fxNO6q7LX6K+-PW-At8SQ0U+RTsuTwa5EGsn42c3A@mail.gmail.com> <MN2PR11MB3565F85F6E989972B92045CBD8FA0@MN2PR11MB3565.namprd11.prod.outlook.com> <CAO42Z2yZ1Fv4ynU_KS4+cej5bYnxN=gLzsJPH9iDWpEBR4jeLw@mail.gmail.com> <MN2PR11MB3565657D1E28F1572BC546D0D8F60@MN2PR11MB3565.namprd11.prod.outlook.com> <C4E210C6-42D4-4456-BE5D-233200E3B005@tzi.org>
In-Reply-To: <C4E210C6-42D4-4456-BE5D-233200E3B005@tzi.org>
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:c0c0:1001::89]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 40cac201-2e2a-44db-f9c0-08d703b10483
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3952;
x-ms-traffictypediagnostic: MN2PR11MB3952:
x-microsoft-antispam-prvs: <MN2PR11MB3952CC3CED73ED3FE3AA1832D8F60@MN2PR11MB3952.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 00922518D8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(136003)(39860400002)(396003)(346002)(376002)(199004)(189003)(13464003)(71190400001)(446003)(71200400001)(11346002)(476003)(46003)(486006)(5660300002)(81166006)(52536014)(8676002)(81156014)(53546011)(7696005)(76176011)(316002)(6506007)(102836004)(186003)(99286004)(6916009)(76116006)(305945005)(14454004)(66574012)(6666004)(256004)(66556008)(8936002)(74316002)(66476007)(7736002)(66446008)(64756008)(2906002)(66946007)(73956011)(6246003)(25786009)(6436002)(4326008)(33656002)(478600001)(229853002)(54906003)(6116002)(9686003)(53936002)(55016002)(68736007)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3952; 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: neEiE/2ZjpW2yWi+XSb96MGrH8K0EsTexeXNEDx9LkRqkd0GGNO6/vJQxkRqLmRGowmXt0bjsdb2m0ZVJKMrbFiMjscziKFtE1fifS1SK/yy5DAmGuxjFImRXHWj2fmWC90ncHalaNKpPdbfltNOP6VCKaWu/TVUj8G5W4iVuRtN5koi9UdYXV+VC+pCOPWEI+4nTpG3/Sid/UI5v1idsNYudZqdN9Jpma4y8rW/EK6lHDhC2Nk0BPLLi3fEyMEDeOLSZpJwIiyymYgPneUId6yRsdiYZKapN1uWaPiBFZ/ke6lgkZ4chsYP4ehDb3LkR3/phEjUvCziS4IBZq/dqwUusVT5vWxQdUHZpOv3tnI0FnFhLY5ItfFYaDshT5rYkI7Et64gRCcMmxnA2vIFpIIFXSMk0bSOZhPgp/QmLhg=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 40cac201-2e2a-44db-f9c0-08d703b10483
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jul 2019 14:31:51.4887 (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: pthubert@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3952
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.24, xch-rcd-014.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/2g9suQZR-ZwjqDQufW6H4_qoFyI>
Subject: Re: [6lo] Advocating a generalization of RFC8505 to non-6lo LANs
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: Mon, 08 Jul 2019 15:06:13 -0000

Hello Carsten:

The 6LR, or 6LBR, are logical functions. A L3-switch is a box that has its differences with a router.

All the best,

Pascal

> -----Original Message-----
> From: Carsten Bormann <cabo@tzi.org>;
> Sent: lundi 8 juillet 2019 14:51
> To: Pascal Thubert (pthubert) <pthubert@cisco.com>;
> Cc: Mark Smith <markzzzsmith@gmail.com>;; Michael Richardson
> <mcr+ietf@sandelman.ca>;; 6man <6man@ietf.org>;; V6 Ops List
> <v6ops@ietf.org>;; 6lo@ietf.org
> Subject: Re: [6lo] Advocating a generalization of RFC8505 to non-6lo LANs
> 
> On Jul 8, 2019, at 14:41, Pascal Thubert (pthubert) <pthubert@cisco.com>;
> wrote:
> >
> >> What sort of device is a "L3AP"? In RFC 8200 we don't have that sort
> >> of device defined, we just have links, hosts, routers and nodes (IPv6 host or
> router).
> >
> > Like a L3-switch but wireless. An AP is a bridge that is proactively
> programmed on the wireless side with the association process, as opposed to
> a learning (transparent) bridge that requires the broadcast. RFC 6775 / 8505 is
> the same thing at L3. If you add L3 features like an SVI to the AP, and L3
> functions in there like RFC8505, routing, and/or ND proxy, then you have an
> L3-AP.
> 
> Hi Pascal,
> 
> out there again confusing everyone with needlessly invented terminology? :-)
> 
> These things are called 6LRs in RFC 6775/8505, for people who want to look
> up what they do (or do you mean 6LBRs?).
> 
> Grüße, Carsten