RE: Interested in wireless ?

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 01 June 2020 15:44 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E56503A11DA for <ipv6@ietfa.amsl.com>; Mon, 1 Jun 2020 08:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=JvaMlLE2; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=YpfD3jmL
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 pIWUSMYbuP5V for <ipv6@ietfa.amsl.com>; Mon, 1 Jun 2020 08:44:06 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A4503A11DB for <ipv6@ietf.org>; Mon, 1 Jun 2020 08:44:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8954; q=dns/txt; s=iport; t=1591026245; x=1592235845; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=NDDU/nmBz3XtS+KLibmCcMiQUxZACwVnB5RiowYNlAw=; b=JvaMlLE2eqrxUhidQo4dNlGolBQLAimEDkiVq3XokksEzkU8YK/gteZa /yNMzd8MLnfaW0lO13gSm3tDK10JVq07w6okJyzKMMD9HiAZNkQmDJ/qG EKD6OsOPR34cxCWfpvQWxuJpeQgbMkIK9D5JEyd+iKs10n9bETPqhG3tt g=;
IronPort-PHdr: 9a23:+pYSdBNlNwwvB+cHyS8l6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEvKw13lbVQcPQ7PcXw+bVsqW1X2sG7N7BtX0Za5VDWlcDjtlehA0vBsOJSCiZZP7nZiA3BoJOAVli+XzoOFRJXs35Yg6arni79zVHHBL5OEJ8Lfj0HYiHicOx2qiy9pTfbh8OiiC6ZOZ5LQ69qkPascxFjA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CyAACQIdVe/5pdJa1mGgEBAQEBAQEBAQEDAQEBARIBAQEBAgIBAQEBQIFKgVBSB29YLyyEJYNGA41EiX2OT4FCgRADVQsBAQEMAQEjBgQCBAEBhEQCF4IPAiQ4EwIDAQELAQEFAQEBAgEGBG2FWQyFcgEBAQEDEhERDAEBLAsBCwQCAQgRBAEBAQICJgICAh8RFQgIAgQBDQUIGoMFgksDLgEOoxsCgTmIYXaBMoMBAQEFhR4NC4IOAwaBDiqCZIJLg3ODJRqBQT+BEUOBT34+gh5JBBqBDzyDEjOCLY5qIYJroF4zTAqCV4gxi1+EfYJmjhaNHJBfiXaCTo0ghBYCBAIEBQIOAQEFgWoigVZwFTuCaVAXAg2QQINyilZ0AgEUIAIGAQcBAQMJfIxzAQE
X-IronPort-AV: E=Sophos;i="5.73,461,1583193600"; d="scan'208";a="766933854"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Jun 2020 15:44:04 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 051Fi3vW013611 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 1 Jun 2020 15:44:03 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 1 Jun 2020 10:44:02 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 1 Jun 2020 10:44:01 -0500
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 1 Jun 2020 10:44:01 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=akFS3kUv0YyvGY2T1E/j4FCZsiseFoLxxLcNaJyYcH5m5y5P0mw7fijtTRscNggaW3Tv6TbpEm9B39/FmXVBp1gxWaD63L2K7BrS/PVhL3oyUHOUo8xzfdjkmUqdUc+KmQqlV9CB3WXxHQNzqDk5OjcrYraW8TRsMhLyMU/8i9+2jl+Sxz3U7W/2krd6S7oRc9FvDcg958eIa7gxZBccjJZhS1NwyaMxNDIfMc+m8eZkZpiCMlhcblKGS/vf1Oc4BnHr/Qzt9mBxgwYQJFLNq/E6Nk9TLxZUY2o1TTSBpNE7AytnXj8hmMIu+DMwVSvxlDP4m7oCkrPe/Y4W+tPDSA==
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=NDDU/nmBz3XtS+KLibmCcMiQUxZACwVnB5RiowYNlAw=; b=DM1QACX1C6iTvnnliJt+mt7QyCt8/2nypqP9BdweycajuBUobCE1zERfUpqffNeaHJMqkpTbC2c7bEkvjZcI/a6ocj0j9AAF0F+N0bDmrSD48FgEcPOK6Kgf586aBfdgag2BQaVPQdA1KMU/RRgDD4iaD+tOMGvNAZRmfHKje8ULK2eNVPHPTavT262BvYbV8l/ffUpCLOLz9Kg7C/7+MEMdFek9Vdautfe7Ew32vpcwhetFB0L+jWFeSPy3Pnc61FXdt3UgyhzZi+lAxLUBSOHM1F5AuGoK2MmdRQcXdqnMYADOab2UTf9p8v14sG0ahSf4qcjauHTDYScOcM3WoQ==
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=NDDU/nmBz3XtS+KLibmCcMiQUxZACwVnB5RiowYNlAw=; b=YpfD3jmLTUSNqBD0KCtpBVD67nP16xRNFqKSIANxGLqrC3jRImKStagb9uNcfQFDoaoDAGyoQPA8RnPDE1hk+U+hQFT06ZUc/fHUae5Vx1A+oFlBPhSKukMQnUWwMO2FM1KaP8BQk+/ywpHsCEroWFnmdg2IRxxfrA5OUtWBHso=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (2603:10b6:208:ea::31) by MN2PR11MB3853.namprd11.prod.outlook.com (2603:10b6:208:ea::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.19; Mon, 1 Jun 2020 15:44:00 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::55bb:b065:86c1:1108]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::55bb:b065:86c1:1108%6]) with mapi id 15.20.3045.022; Mon, 1 Jun 2020 15:44:00 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "STARK, BARBARA H" <bs7652@att.com>, 'Brian E Carpenter' <brian.e.carpenter@gmail.com>
CC: '6man WG' <ipv6@ietf.org>
Subject: RE: Interested in wireless ?
Thread-Topic: Interested in wireless ?
Thread-Index: AQHWNnfqX/nhVMuy1Ea+e7RI89I6LqjBGiqAgAFNXKuAAG+3AIAAlhmwgAB1GICAAAUx0A==
Date: Mon, 01 Jun 2020 15:43:49 +0000
Deferred-Delivery: Mon, 1 Jun 2020 15:43:05 +0000
Message-ID: <MN2PR11MB35657D5A64F886C0AC206600D88A0@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <A26FA9F8-72B8-4728-B978-6DDD271EC64D@cisco.com> <d157e481-f5d0-7f54-2f62-7400e0394688@gmail.com> <49E329AB-5060-46A3-BEC9-66EC80056565@cisco.com> <2c94c310-28ba-01e5-a874-029509e9b653@gmail.com> <MN2PR11MB3565BC3BF415667EB2D75870D88A0@MN2PR11MB3565.namprd11.prod.outlook.com> <4594894861b54c3ab6a3644829440a5f@att.com>
In-Reply-To: <4594894861b54c3ab6a3644829440a5f@att.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: att.com; dkim=none (message not signed) header.d=none;att.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2a01:cb1d:4ec:2200:75db:189b:5b62:e086]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0f4669bb-130a-4a04-0b10-08d806429aa9
x-ms-traffictypediagnostic: MN2PR11MB3853:
x-microsoft-antispam-prvs: <MN2PR11MB38536B269B0CAD36F3B54ACBD88A0@MN2PR11MB3853.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:3968;
x-forefront-prvs: 0421BF7135
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 3XsAxPwRSO2c3y/UMhw8DPpDUtAFVqe4K2W9umIUL6b98D0bmyoHv7hs0eUGMlPgmh7kruY7rmv851J+gnQbzFYIFxvVDt7kDoK2M3rnF0wINzAOag42dRbfynqsbPOOLdDRP0d7LoORucW/OqWnXvK8NBnIkUW2akp52/tyKbmgf2vTw4zQAmeYBGKX7liqkjHPyk6WY1/TKy2Qa6LyqhxrNTR+bJCva1yq8mJtJ4jQYjjA2yxvGOInUbWWRCbvDHW/XHX0zQGThy5ytfsk5brLznAn7rLx/MFtvt8I3TwvWPLknrCH0OQW5rlg2yUYJmBmgIdvN1SMLqAHhsCnRk8TIPxpTW6vqJTbYGHRW6/GGaxV846a4nDArLi832xjHtMjb9f2Pepm59w3gI+joA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR11MB3565.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(39860400002)(376002)(346002)(396003)(136003)(366004)(6666004)(83380400001)(110136005)(7696005)(7116003)(76116006)(3480700007)(66946007)(66556008)(66476007)(8936002)(478600001)(316002)(4326008)(19627235002)(66574014)(33656002)(71200400001)(966005)(8676002)(5660300002)(52536014)(64756008)(2906002)(53546011)(6506007)(66446008)(186003)(86362001)(55016002)(9686003); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: uqC/tyhL/4HTvsXuOVpWkWqs0gJfzBkjf4H+WNPGLDbl1YxujtzPsyZn/TmPOyXViQRmQFQ6mzBwiazLDpXW+4c5/vzhm7X3hsi0FEPtmcYCY0RSk/GlCoKKZpWjwNay0b71cpv/5+A7T0CUS07I8YT9NaRxMcgf4rnpch1H50JdK6dVxpsoBY2iHDHojyMhy0taa9ixtOorfSM/gouJ5bOhFmrLXJvI7hD2q2nYYZqB2qjCedFdCyFyeboK/aEjW/qVOp37B+iJH16xxIKrs/V/B9UPXU7zd1ZKULEjMaJSMhGrIfTZEGQ7VpltxYeS0Z6qW70PYFQkPKP53l7x9raUY5JiS+d+o6Rs93lzuNJU9eI2s6f61pbnlcKYjKWRZO4BvGFc81Y6PzumYQB9StsDYtjBca6cnEnXftN9GK1T4kEDkvodaECTTMyu5sAZTRe5KNl1iADwJSmm152uDTCYaZdOTehk+4hYnSGlDWO2NO2h5SeSDplh9stXqnrRMY7zZNIMySqZWxjKa/GoPHPq9zdUtSHawa1L/T4GR6kSUuzLpg8j0KJCVfmYjCfT
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: 0f4669bb-130a-4a04-0b10-08d806429aa9
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Jun 2020 15:44:00.1505 (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: /ko7m1EJK6OBmXP0AeJZVMM5lOpnx8CSjOQ+CVUYeEki9Uk88RfYOacaunVrqJ1onyvPzhh6QCeDdKJ6ILQ/dQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3853
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/oXzlObwGutYhoAnF0tIeh9VtSM8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2020 15:44:16 -0000

Hello Barbara:

RFC 8505 and the 2 following drafts (Backbone Router and Address Protection) are already referenced by the upcoming IEEE Std. 802.11 revision, the last 2 as draft-ietf-* for now. This is why we care to get the other RFC numbers soon (the 2 drafts are in RFCed queue). I expect that this means an automatic pick by WFA?

We'll note that the IEEE references are informational, like, it is recommended to do ND proxy and informationally, here's how you can do it.
But still it's a step. We need to convince the stacks. For all I know some routers are ready to engage.

Take care,

Pascal

> -----Original Message-----
> From: STARK, BARBARA H <bs7652@att.com>
> Sent: lundi 1 juin 2020 17:17
> To: Pascal Thubert (pthubert) <pthubert@cisco.com>; 'Brian E Carpenter'
> <brian.e.carpenter@gmail.com>
> Cc: '6man WG' <ipv6@ietf.org>
> Subject: RE: Interested in wireless ?
> 
> > Neat!
> >
> > Many thanks Brian.
> >
> > Pascal
> 
> Oh, good. I'd just like to say that Brian very eloquently expressed some of the
> thoughts I had when reading through the draft. This is an important topic. I'd
> like to see it presented in a way that drives deployment, if it really will help to
> solve the problem.
> 
> I suspect that to really get high rates of good, interoperable implementations
> in deployed Wi-Fi products, it might need to get picked up by Wi-Fi Alliance. An
> applicability statement that helps them understand the use case would be
> useful. I wonder, though, if that would be more v6ops than 6man? That is, it
> seems more about using (and implementing/deploying) existing protocols to
> improve operation of a network.
> Barbara
> 
> > > From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> > >
> > > Pascal,
> > >
> > > There is a category of standards track documents foreseen in RFC2026
> > > called "applicability statements", described at
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_
> > > ht
> > > ml_rfc2026-23section-2D3.2&d=DwIGaQ&c=LFYZ-
> > o9_HUMeMTSQicvjIg&r=LoGzhC-
> > >
> > 8sc8SY8Tq4vrfog&m=_i8eV1zjwa6e9U_4dG_Ehj8deR5jGNQadCAX4NyOVRg
> > &s=S88z1M
> > > klplQDukKNZjL75ub8LZnYm9ZJBYq_cafJfzY&e=
> > >
> > > I think that is perhaps where your draft could fit. A little bit
> > > stronger than Informational and little bit different than Best
> > > *Current*
> > Practice.
> > >
> > > Regards
> > >    Brian
> > >
> > > On 01-Jun-20 04:40, Pascal Thubert (pthubert) wrote:
> > > > Hello Brian
> > > >
> > > > We may have to split the doc but for the most part I agree it is
> > > > an
> > > informational.
> > > >
> > > > For now I suggest to just change the intended status accordingly
> > > > and aim at
> > > BCP or something.
> > > >
> > > > Let’s discuss in parallel the coexistence and if there’s a need
> > > > for an std track
> > > somewhere. There’s at least the use of a 6LBR for address looking up
> > > in unicast.
> > > >
> > > > Take care,
> > > > Pascal
> > > >
> > > >> Le 30 mai 2020 à 22:47, Brian E Carpenter
> > > >> <brian.e.carpenter@gmail.com>
> > > a écrit :
> > > >>
> > > >> Hi,
> > > >>
> > > >> I believe that this is an important topic that 6MAN should take up.
> > > >> The draft
> > > is a good basis.
> > > >>
> > > >> At the moment I find the draft a bit confusing in one way. It's
> > > >> aimed at
> > > standards track, but it mainly doesn't read like a standard. There's
> > > a lot of discussion but not much specification. If I was a coder, I
> > > wouldn't really know where to start. For example, the end of the
> > Introduction says:
> > > >>
> > > >> "This document discusses the applicability of IPv6 ND over
> > > >> wireless links, as compared with routing-based alternatives such
> > > >> as prefix-per node and multi-link subnets (MLSN), and with
> > > >> Wireless ND (WiND), that is similar to the Wi-Fi association and
> > > >> reduces the need for Network-Layer multicast."
> > > >>
> > > >> If it's a standard, IMHO it shouldn't do that. It should specify
> > > >> what WiND is,
> > > with normative references as needed. Section 5 is the important part.
> > > It's fine to have a descriptive section about why WiND is needed,
> > > but that is almost better as an appendix. The main text should be
> > > essentially the instructions for a kernel programmer.
> > > >>
> > > >> Regards
> > > >>   Brian Carpenter
> > > >>
> > > >>> On 30-May-20 23:46, Pascal Thubert (pthubert) wrote:
> > > >>> Dear all
> > > >>>
> > > >>> Since there’s so much energy on the list these days, could we
> > > >>> consider the adoption of
> > > >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.
> > > >>> or
> > > >>> g_html_draft-2Dthubert-2D6man-2Dipv6-2Dover-2Dwireless-
> > 2D05&d=DwIG
> > > >>> aQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=LoGzhC-
> > 8sc8SY8Tq4vrfog&m=_i8eV1zjwa6
> > > >>>
> > e9U_4dG_Ehj8deR5jGNQadCAX4NyOVRg&s=zhmY1Y4gPkDO08iqReP1D3y6I
> > UQ2eCR
> > > >>> cItaE6PV0kzU&e=
> > > >>> ?
> > > >>>
> > > >>> I got only positive feedback, there’s no politics, there no
> > > >>> label, it’s all about
> > > IPv6 models for wireless. This may appear useful in a world where
> > > the vast majority of devices are connected that way.
> > > >>>
> > > >>> Keep safe,
> > > >>>
> > > >>> Pascal
> > > >>>
> > > >>> ----------------------------------------------------------------
> > > >>> --
> > > >>> -- IETF IPv6 working group mailing list ipv6@ietf.org
> > > >>> Administrative
> > > >>> Requests:
> > > >>> https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_
> > > >>> mailman_listinfo_ipv6&d=DwIGaQ&c=LFYZ-
> > o9_HUMeMTSQicvjIg&r=LoGzhC-8
> > > >>>
> > sc8SY8Tq4vrfog&m=_i8eV1zjwa6e9U_4dG_Ehj8deR5jGNQadCAX4NyOVRg&
> > s=d4r
> > > >>> J3C_jWlTRhy2Hr3SeRSeCEeyC8wNfKBtnuG7VCeU&e=
> > > >>> ----------------------------------------------------------------
> > > >>> --
> > > >>> --
> > > >>>
> > > >>
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests:
> > https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_mailman_listinfo_ipv6&d=DwIGaQ&c=LFYZ-
> > o9_HUMeMTSQicvjIg&r=LoGzhC-
> > 8sc8SY8Tq4vrfog&m=_i8eV1zjwa6e9U_4dG_Ehj8deR5jGNQadCAX4NyOVRg
> > &s=d4rJ3C_jWlTRhy2Hr3SeRSeCEeyC8wNfKBtnuG7VCeU&e=
> > --------------------------------------------------------------------