Re: [6gip] IP Address Mobility Project

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 23 February 2023 09:59 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: 6gip@ietfa.amsl.com
Delivered-To: 6gip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F6E3C14F736 for <6gip@ietfa.amsl.com>; Thu, 23 Feb 2023 01:59:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.629
X-Spam-Level:
X-Spam-Status: No, score=-1.629 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DIET_1=0.001, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B-bRx8up9JvF for <6gip@ietfa.amsl.com>; Thu, 23 Feb 2023 01:59:53 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DDE4C14F739 for <6gip@ietf.org>; Thu, 23 Feb 2023 01:59:52 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 31N9xcbr059786; Thu, 23 Feb 2023 10:59:38 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D7C1A203824; Thu, 23 Feb 2023 10:59:38 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BF4622038DB; Thu, 23 Feb 2023 10:59:38 +0100 (CET)
Received: from [10.11.242.10] ([10.11.242.10]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 31N9xcMZ017926; Thu, 23 Feb 2023 10:59:38 +0100
Message-ID: <10ec5cee-986d-f0af-5ced-e6742ea7842f@gmail.com>
Date: Thu, 23 Feb 2023 10:59:38 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0
Content-Language: fr
To: David Lake <d.lake@surrey.ac.uk>
Cc: Hesham ElBakoury <helbakoury@gmail.com>, Giles Heron <giles=40layerfree.net@dmarc.ietf.org>, Toerless Eckert <tte@cs.fau.de>, "6gip@ietf.org" <6gip@ietf.org>, Sridhar Bhaskaran <sridhar.bhaskaran@gmail.com>
References: <20AC1ED3-1548-4AE2-B09C-70340B114A26@gmail.com> <FAC27F50-B4C4-4AC6-89F1-9F1707B5D8A8@gmail.com> <CAC8QAcf8ykJhBSotyUhSimtWek=bjcWbppGV3e8VJ_bpgDjb=Q@mail.gmail.com> <47bb3ac7-6c83-0aa7-5a02-5aa3c6791a95@kit.edu> <Y/PEsg5z+HEHgn4Y@faui48e.informatik.uni-erlangen.de> <032102c1-6f76-5ad4-2cbd-d384bf201e6f@gmail.com> <Y/T/TJMfECp+G3Yn@faui48e.informatik.uni-erlangen.de> <9aea3d6f-f1a0-2516-2de6-5d52cdc38ce5@gmail.com> <4BE47593-D44B-4D2D-8403-E113B8CC50D0@layerfree.net> <DBAPR06MB68556D55FE112DC8301AE99BB5AA9@DBAPR06MB6855.eurprd06.prod.outlook.com> <b3cfcdf5-e020-0f11-4ef1-641f3ef63d97@gmail.com> <CAFvDQ9r9O==3=SmO0eTq8Wwx62JPK2vCuQoyOgw1MTYO3Z9f3g@mail.gmail.com> <22fcd717-fd31-c5ae-7da1-ca9e4ffab47b@gmail.com> <CA+3a8OZ+2THHDV-oe0QcS+PheV9thptKUN7DC0jmskykOaxAxg@mail.gmail.com> <5aeaa5ac-6a5c-b60d-82f9-3ae4d1e4ba1d@gmail.com> <DBAPR06MB6855B27D1E39C4CD57439025B5AB9@DBAPR06MB6855.eurprd06.prod.outlook.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <DBAPR06MB6855B27D1E39C4CD57439025B5AB9@DBAPR06MB6855.eurprd06.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/6gip/6Ev3nlOTOZeiHW3bJNLIw1eNsVg>
Subject: Re: [6gip] IP Address Mobility Project
X-BeenThere: 6gip@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IP Issues in 6th Generation Mobile Network System \(6gip\)" <6gip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6gip>, <mailto:6gip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6gip/>
List-Post: <mailto:6gip@ietf.org>
List-Help: <mailto:6gip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6gip>, <mailto:6gip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2023 09:59:57 -0000


Le 23/02/2023 à 10:27, David Lake a écrit :
> Alex
> 
> QCI is set by the network as it is aware of the requirements of the 
> application.

Ah the all-knowing network... :-)

Since GPRS and until 4G I used clients on windows to connect to cellular
networks.  All clients offered some parameters for QoS settings on
cellular.  These parameters were never respected, because the network
seemed to know better.

It should be the other way around :-)

> It is not just network capabilities but also the RF numerology.
> VoLTE, for example, travels over a more robust numerology than the
> numerology on the default bearer.  This is why voice over LTE is much
> better in terms of jitter and loss than voice over WhatsApp (for
> example).
> 
> Personally, I would like to see the ability to carry out such mapping
>  across the wider Internet - I worked on proposals for H.325 to do
> just that many years ago - not just in the operator/cellular domain
> but as application needs <<<<< available bandwidth (and bandwidth has
> been relatively cheap) we haven't really had to deal with this
> problem.
> 
> We absolutely do in cellular because SLAs are based on it.

Carrying out mappings across the wider Internet is a great idea and I
support it.

I understand a little bit VoLTE, yet I dont see precisely why would it
be better than a WhatsApp voice calls, a whatsapp that I understand even
less.

I would like to know whether both VoLTE and WhatsApp work ok on IPv6 or
not.  The latter <(whatsapp) I can check myself right now, but the
former no - VoLTE is a concept bound to a particular operator, if I
understand correctly.  I am not at that operator.

That means that I can try right away a handover of an ongoing whatsapp
call between wifi and 4G.  I can show right away whether it breaks or
not.  If it breaks, I can formulate right away a requirement for it not
to break.  If it keeps up, but there are some audio glitches, then I can
formulate a requirement for these glitches to go away.

For VoLTE I cant do any of these immediately obvious steps.

But I can agree with you, based on trust, that probably VoLTE is a great
performing tool.

Alex

> 
> David
> 
> Sent from Outlook for iOS <https://aka.ms/o0ukef> 
> ------------------------------------------------------------------------
>
> 
*From:* Alexandre Petrescu <alexandre.petrescu@gmail.com>
> *Sent:* Thursday, February 23, 2023 9:12:36 AM *To:* Sridhar
> Bhaskaran <sridhar.bhaskaran@gmail.com> *Cc:* Hesham ElBakoury
> <helbakoury@gmail.com>; Lake, David (PG/R - Comp Sci & Elec Eng)
> <d.lake@surrey.ac.uk>; Giles Heron 
> <giles=40layerfree.net@dmarc.ietf.org>; Toerless Eckert
> <tte@cs.fau.de>; 6gip@ietf.org <6gip@ietf.org> *Subject:* Re: [6gip]
> IP Address Mobility Project For the traffic class mutability: the
> routers in an xGPP (3GPP) network are all under the same authority.
> This means that that authority can easily configure all intermediary
> routers to not touch on the traffic class.
> 
> Alex
> 
> Le 23/02/2023 à 05:00, Sridhar Bhaskaran a écrit :
>>> Are there proposals to replace GTP?
>> 
>> <SB> See 3GPP TR 29.892 - 
>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.3gpp.org%2Fftp%2FSpecs%2Farchive%2F29_series%2F29.892%2F29892-g00.zip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HEUdsqLk%2Fkf60NXbK%2FXjeI79BHgIWA3KDsVnH%2B1CZIw%3D&reserved=0
>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.3gpp.org%2Fftp%2FSpecs%2Farchive%2F29_series%2F29.892%2F29892-g00.zip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HEUdsqLk%2Fkf60NXbK%2FXjeI79BHgIWA3KDsVnH%2B1CZIw%3D&reserved=0>
>>
>> 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.3gpp.org%2Fftp%2FSpecs%2Farchive%2F29_series%2F29.892%2F29892-g00.zip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HEUdsqLk%2Fkf60NXbK%2FXjeI79BHgIWA3KDsVnH%2B1CZIw%3D&reserved=0 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.3gpp.org%2Fftp%2FSpecs%2Farchive%2F29_series%2F29.892%2F29892-g00.zip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HEUdsqLk%2Fkf60NXbK%2FXjeI79BHgIWA3KDsVnH%2B1CZIw%3D&reserved=0>>
>> SRv6 was proposed and the outcome of the study is in this TR. After
>> this IETF DMM worked on this draft independently - 
>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-dmm-srv6-mobile-uplane&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1%2FfkVw58e7Sg3xExGaL%2BMEyLnh6W5XdlGl8a5Ga7Ydc%3D&reserved=0
>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-dmm-srv6-mobile-uplane&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1%2FfkVw58e7Sg3xExGaL%2BMEyLnh6W5XdlGl8a5Ga7Ydc%3D&reserved=0>
>>
>> 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-dmm-srv6-mobile-uplane&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1%2FfkVw58e7Sg3xExGaL%2BMEyLnh6W5XdlGl8a5Ga7Ydc%3D&reserved=0 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-dmm-srv6-mobile-uplane&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1%2FfkVw58e7Sg3xExGaL%2BMEyLnh6W5XdlGl8a5Ga7Ydc%3D&reserved=0>>
>> 
>> 
>>> I can say that QoS can also be done with flow labels and traffic
>>> 
>> classes
>>> in IPv6 headers, without GTP.
>> <SB> Flow labels and traffic classes can be changed by on path IP 
>> devices (routers etc). 3GPP endpoints require an unmodified flow 
>> identifier. That is why they keep the flow identifier in additional
>>  layer of encapsulation (i.e in GTP header). The flow identifier
>> marked by the first 3GPP entrypoint gateway (UPF) is kept all the
>> way upto radio network in the downlink direction so that, radio
>> network can directly use that as index to look up the resource
>> allocation scheme / scheduler and RRM details. For certain services
>> like voice media (which is marked by QOS flow identifier
>> corresponding to QCI/5QI 1), mission critical services (QFI --> 5QI
>> --> 69) etc, strict SLAs are there. Network cant afford to let on
>> path routers meddle with QoS flow markers.
>> 
>> Regards Sridhar On Thu, Feb 23, 2023 at 1:16 AM Alexandre Petrescu
>>  <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com
>> 
> <mailto:alexandre.petrescu@gmail.com>>> wrote:
>> 
>> 
>> 
>> Le 22/02/2023 à 19:43, Hesham ElBakoury a écrit :
>> 
>> I can try to find that out.  I remember some relatively recent 
>> presentations at IETF about replacing GTP, or reducing the number
>> of headers.  It might have been in the (precursor?) of the DMM WG. 
>> (distributed mobility mgmt).
>> 
>> A related question, IMHO, would be too whether there is an RFC for
>> GTP in a first place...
>> 
>> I can remember an Internet Draft of year 2000 about GTP - named
>> simply draft-casati-gtp - but it was not pursued at IETF.
>> 
>> If there were a GTP RFC, then we could think about improving it, 
>> replacing it, etc.
>> 
>> When there is no GTP RFC, one can think about what should an ideal
>> xGPP (3GPP) network use instead.
>> 
>> Or maybe another way...
>> 
>> Alex
>> 
>>> Hesham
>>> 
>>> On Wed, Feb 22, 2023, 10:39 AM Alexandre Petrescu 
>>> <alexandre.petrescu@gmail.com
>> <mailto:alexandre.petrescu@gmail.com
>> <mailto:alexandre.petrescu@gmail.com>> 
>> <mailto:alexandre.petrescu@gmail.com 
>> <mailto:alexandre.petrescu@gmail.com
> <mailto:alexandre.petrescu@gmail.com>>>> wrote:
>>> 
>>> David, Giles,
>>> 
>>> Le 22/02/2023 à 14:35, David Lake a écrit :
>>>> This:
>>>> 
>>>> “…the 5G UPF terminates the GTP tunnel but also does QoS,
>> charging,
>>>> lawful intercept etc. ”
>>>> 
>>>> … is a VERY important point.  GTP enables a number of very
>> low-level
>>>> RF features which MNOs need to control their allocation of
>> spectrum
>>>> and more importantly the numerology associated with an
>> application.
>>>> It is also used in shared solutions such a CoMP.
>>> 
>>> I can agree with the importance of the point above.  I can
>> agree about
>>> improvements there might be necessary.
>>> 
>>> I can say that QoS can also be done with flow labels and
>> traffic classes
>>> in IPv6 headers, without GTP.
>>> 
>> 
>>> But I agree with the importance of the topic.
>>> 
>>>> If we are to replace GTP (and I think there is a reason to
>> do that)
>>>> we have to provide the interactions to the layer 1 that
>> MNOs need.
>>> 
>>> I agree.
>>> 
>>> [...] Giles said:
>>>> I’m not sure that your electricity analysis is correct.
>>>> 
>>>> Doing e.g. an MPLS exact match lookup across a FIB with a few 
>>>> thousand labels rather than an IPv6 longest-match lookup
>> across a FIB
>>>> with a few million prefixes, for example, may well more
>> than offset
>>>> the extra electricity consumption caused by the extra 4
>> bytes of
>>>> header.
>>>> 
>>>> And then of course there’s all the electricity consumed by the 
>>>> control plane updates hitting the router CPUs.
>>> 
>>> I can agree.  But I do not take that as an invitation to ignore 
>>> electricity consumption.  Rather, all points you mention
>> (exact match
>>> lookup consumption, ctl plane) should be measured and told
>> who consumes
>>> more, and then decide what to reduce.
>>> 
>>> I do not take your remark as giving up electricity savings in
>> front of
>>> too much complexity of understanding what's happening.
>>> 
>>> I do not take your remark as freedom to add more headers when
>> it becomes
>>> necessary to add more functionality.
>>> 
>>> [...]
>>> 
>>>>> More details about this performance degradation can be
>> provided if
>>>>> absolutely necessary, but some times trust might also
>> help for a
>>>>> quicker understanding towards realizing a common goal.  (the 
>>>>> development of trust is another matter that we can discuss 
>>>>> separately :-)
>>>> 
>>>> Trust takes time to earn, and I’d tend to suggest that
>> arguing that
>>>> it makes sense to inject a host route for a UE into OSPF
>> may not be
>>>> the best way to earn it.
>>> 
>>> Given this apparent disparate understanding about routing -
>> you seem to
>>> be more people to be saying the contrary of what I say - I
>> give up this
>>> topic discussion on host based routes.  Maybe for later for
>> another G,
>>> maybe never.
>>> 
>>> Alex
>>> 
>>> -- 6gip mailing list 6gip@ietf.org <mailto:6gip@ietf.org
>>> <mailto:6gip@ietf.org>> <mailto:6gip@ietf.org
>> <mailto:6gip@ietf.org <mailto:6gip@ietf.org>>>
>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ1SLim7OAFhk%2BmkMe2gMhHYi29UO1LKWN%2ByYi%2BKKc%3D&reserved=0
>>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ1SLim7OAFhk%2BmkMe2gMhHYi29UO1LKWN%2ByYi%2BKKc%3D&reserved=0>
>>
>>> 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ1SLim7OAFhk%2BmkMe2gMhHYi29UO1LKWN%2ByYi%2BKKc%3D&reserved=0 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ1SLim7OAFhk%2BmkMe2gMhHYi29UO1LKWN%2ByYi%2BKKc%3D&reserved=0>>
>>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ1SLim7OAFhk%2BmkMe2gMhHYi29UO1LKWN%2ByYi%2BKKc%3D&reserved=0
>>
>>> 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ1SLim7OAFhk%2BmkMe2gMhHYi29UO1LKWN%2ByYi%2BKKc%3D&reserved=0 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ1SLim7OAFhk%2BmkMe2gMhHYi29UO1LKWN%2ByYi%2BKKc%3D&reserved=0>>>
>>> 
>> 
>> -- 6gip mailing list 6gip@ietf.org <mailto:6gip@ietf.org
>> <mailto:6gip@ietf.org>> 
>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ1SLim7OAFhk%2BmkMe2gMhHYi29UO1LKWN%2ByYi%2BKKc%3D&reserved=0
>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ1SLim7OAFhk%2BmkMe2gMhHYi29UO1LKWN%2ByYi%2BKKc%3D&reserved=0>
>>
>> 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ1SLim7OAFhk%2BmkMe2gMhHYi29UO1LKWN%2ByYi%2BKKc%3D&reserved=0 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&data=05%7C01%7Cd.lake%40surrey.ac.uk%7C8951b6e70f0b432512c008db157e24f0%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638127403752290988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ1SLim7OAFhk%2BmkMe2gMhHYi29UO1LKWN%2ByYi%2BKKc%3D&reserved=0>>
>> 
>> 
>> 
>> -- o__ _>  /__ (_) \(_)... Burn fat not fuel - Bike along to a
>> healthier life and cleaner world! :)
>> 
>> Sridhar Bhaskaran
>>