2021=EB=85=84 8=EC=9B=94 12=EC=9D=BC (=EB=AA=A9) =EC=98= =A4=EC=A0=84 5:29, Dino Farinacci <farinacci@gmail.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:

> First of all, than= k you very much to give detailed comments on our draft. Please check answer= s for your comments inline.

KJ, thanks for the quick response. I have cut out the text where I agree/ac= cept with your responses. See inline for additional commentary and answers = to your questions.

Once you update the spec, I'll give another thorough review. Thanks!
>
>> Which indicates that ETR only wants packets sent to C and D when A= and B are not reachable from the ITR (by using multiple mechanisms but the= most robust is RLOC-probing).
>>
>> Note the use of an RLOC-set comes in multiple forms:
>>
>> (1) A list like above (default)
>> (2) An ELP, where the RLOC-record indicates a encap-path from ITR = to ETR.
>> (3) An RLE, where the RLOC-record indicates that all RLOCs listed = are used (multicast replication).
>>
>> You could use 1 or all combinations of these with filtering/policy= support on the map-server.
>
> KJ: The priority you mentioned just represents the network-related cap= ability in the dynamic anycast viewpoint. However, if parameters to be requ= ired for selecting routing path are not only network-related metrics but al= so service-related metrics (i.e., computing loads, number of flows, etc.), = we need other indirection for that.

If you want to control where packets go on the underay, you can also consid= er draft-ietf-lisp-te. That is where ELPs are introduced and designed into = the LISP architecture.

>>
>>> <PastedGraphic-39.png>
>>
>> It is important to note that if you use equal priorities in an RLO= C-set, that the ITR can load-split traffic across RLOCs and that will break= connnection oriented applications (or applications that require remote sta= te for a session).
>>
>> So an ITR that is configured that a particular EID in its map-cach= e is an anycast-EID, it can use an RLOC-set above with each RLOC priority= =3D1 and then choose based on the implementation's idea of what is a be= tter RLOC to use.
>>
>> IMO opinion, the better way to design/implement this is using an a= nycast-EID-to-anycast-RLOC mapping. Which means you only need a register fr= om one place (an SDN controller) or each ETR registering the same RLOC (wit= hout merge semantics). So the serivce is chosen by destination address in a= packet (the anycast-EID) which maps to an anycast-RLOC where the underlay = takes you to the "closest" LISP site. But closest is just one way= of getting to a service. You may have other ways and hence why you introdu= ced a metric.
>
> KJ:=C2=A0 In my understanding, in your suggestion, anycast RLOC is all= ocated to the ETRs which can deliver packet destined to anycast-EID by inte= rnal routing and routing between those ETRs are chosen in the underlay. Is = it right?

Yes. You assign the same RLOC address to multiple ETRs and have underlay ro= uting take a source to the closest LISP site.

>>
>> Yes, it is better to gather the metrics data outside of LISP. But = yes, the control-plane could store it. I would suggest just mapping your co= llection metrics to priorities so no protocol messages would need to be mod= ified. I believe LISP already has designed in everything you need. Do you a= gree?
>
> KJ: yes. I agree with your point that LISP already has the solution to= mapping metrics to priorities. That is the one of reasons that I think tha= t it is possible to provide dynamic anycast routing using LISP without huge= modifications.

Yes agree. Then the ITR came make an RLOC selection based on existing docum= ented approaches. But if the metrics change too much then the contents of t= he RLOC-set changes which requires more frequent map-cache updates. So we h= ave to analyze this tradeoff more in depth.

> So, I think that we should not give fixed solutions on how to collect = and store metrics but we can mention possible solutions for that. Because i= t is more implemental issue. Is it right approach?

Yes, I agree.

> <PastedGraphic-45.png>
>>
>> Yes, it can, see draft-rodrigueznatal-lisp-multi-tuple-eids.
>
> KJ:=C2=A0 Thank you for giving that information. I will check and upda= te=C2=A0 =C2=A0

Thanks again,
Dino

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D

=EC=84=A0=EA=B2=BD=EC=9E=AC / Kyoungjae Sun= (KJ Sun)

=EC=97=B0=EA=B5=AC=EC=9B=90 / =ED=81=B4=EB=9D=BC=EC=9A=B0= =EB=93=9C =EB=B0=8F =EB=84=A4=ED=8A=B8=EC=9B=8C=ED=81=AC =EC=97=B0=EA=B5=AC= =EC=8B=A4

Researcher /=C2=A0Distributed Cloud and Network lab

Office : +82-2-814-= 0151=C2=A0 =C2=A0 Phone : +82-10-3643-5627

Email : gomjae@dcn.ssu.ac.kr

= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

--000000000000735d0705c9527450-- From nobody Wed Aug 11 19:03:37 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7D823A300F for ; Wed, 11 Aug 2021 19:03:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.095 X-Spam-Level: X-Spam-Status: No, score=-2.095 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, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 fDbf1_xBQg7L for ; Wed, 11 Aug 2021 19:03:29 -0700 (PDT) Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A50383A300E for ; Wed, 11 Aug 2021 19:03:29 -0700 (PDT) Received: by mail-pj1-x1035.google.com with SMTP id u13-20020a17090abb0db0290177e1d9b3f7so12753877pjr.1 for ; Wed, 11 Aug 2021 19:03:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=5fbZsjsLQ3JtPwvpRKCgVxAegr0tkmpSUOFv+boOLog=; b=R7D9pPEyWCV5+0SjCRLc/96h/D6v9LiWZQNwRFoiqJE3JbnLyErWIVHzmqX/VlFLaj V5G0gYZ4qx5oRkBuKnNhxr9/idPGkLV15Izqok54Vz4wlRgXKutMjqIZsw9/r4L6NaSA ihJvlumzA/e/cNztbVolNGLSpbRGXJKfSP1r0re5PUl/ti50NHjalZ5CNbw+WUuqTCKF IV8dIn9V4iFtapPWKLGRUNe7SWUFCMyFk9Hb70PfpBOUr2q1ecvlsLmakC6MtZcYzHTi 4NZXRYdOr8O5o8kpO3LN/6914IpMJUln+bWPIs7RFAbGHJsIUOrAaTUt459JWSJr84ho NbbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=5fbZsjsLQ3JtPwvpRKCgVxAegr0tkmpSUOFv+boOLog=; b=gKn6WmeZNnaHSm0ZQB6F0YGqEDO0DXxTMInMAizb37E/RmfLcu05NLDmFufsxLhAam Go1K8gq+Li7eKa2SrlbcYNjHyfH0DzDCH2mJatgNByQcyMfwfgiwDpHo9a16PSs0455B Q9njg27AIOC48dnaCgUJunVtDou5CEIA75YYOkkjA2Io/RgqBvcWij7MEMkjGnRJsLpY q4oPywL7AqyvnfadCxx1j9VsCRQQJhBPtKVvR3fxrZYjRiP3zvbI4j8QRwkkXwAe87GX KMTsFZxez7PIVUUeVIzZK7rCn2kRbpxenhus8+w6WROgMWtZ8d+VwJdc2941zj2YGYKG KJfw== X-Gm-Message-State: AOAM5311jyFKMy95sBhSTopRKqvKer6hEN+PHQOO9bSmw+rMTY4k2BsT MOLpax4LfrpTvuF1ojcLhs4= X-Google-Smtp-Source: ABdhPJzkxmOlsMgRzy+aesUOUbdkyWOTeJC6YwQE7ht0YMxjWRZmt4jasTmfzet7BPW9kFxG7zZcVg== X-Received: by 2002:a17:90a:8b07:: with SMTP id y7mr13461467pjn.133.1628733808117; Wed, 11 Aug 2021 19:03:28 -0700 (PDT) Received: from smtpclient.apple ([2601:646:9600:af10:2417:390d:f619:f20e]) by smtp.gmail.com with ESMTPSA id e7sm915635pfe.124.2021.08.11.19.03.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 11 Aug 2021 19:03:27 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-871EEDCA-DB81-4411-98E7-51D96A59E43E Content-Transfer-Encoding: 7bit From: Dino Farinacci Mime-Version: 1.0 (1.0) Date: Wed, 11 Aug 2021 19:03:25 -0700 Message-Id: <4BB7F1FA-3AD8-4ECD-AA3F-FA845C3C92FB@gmail.com> References: Cc: =?utf-8?B?6rmA7JiB7ZWcIOq1kOyImOuLmA==?= , "lisp@ietf.org list" In-Reply-To: To: =?utf-8?B?7ISg6rK97J6s?= X-Mailer: iPhone Mail (19A5318f) Archived-At: Subject: Re: [lisp] Comments to draft-kjsun-lisp-dyncast-00 X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2021 02:03:36 -0000 --Apple-Mail-871EEDCA-DB81-4411-98E7-51D96A59E43E Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thanks again KJ.=20 Dino > On Aug 11, 2021, at 6:14 PM, =EC=84=A0=EA=B2=BD=EC=9E=AC wrote: >=20 > =EF=BB=BF > Dino, >=20 > Thank you for discussing this topic. It was very helpful for making clear t= o our proposal. >=20 > I will update draft depending on these discussions. >=20 > Additional comments and discussion by LISP folks are always welcome. >=20 > Sincerely >=20 > KJ. > =E1=90=A7 >=20 > 2021=EB=85=84 8=EC=9B=94 12=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 5:29, D= ino Farinacci =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1: >> > First of all, thank you very much to give detailed comments on our draf= t. Please check answers for your comments inline. >>=20 >> KJ, thanks for the quick response. I have cut out the text where I agree/= accept with your responses. See inline for additional commentary and answers= to your questions. >>=20 >> Once you update the spec, I'll give another thorough review. Thanks! >>=20 >> >=20 >> >> Which indicates that ETR only wants packets sent to C and D when A and= B are not reachable from the ITR (by using multiple mechanisms but the most= robust is RLOC-probing). >> >>=20 >> >> Note the use of an RLOC-set comes in multiple forms: >> >>=20 >> >> (1) A list like above (default) >> >> (2) An ELP, where the RLOC-record indicates a encap-path from ITR to E= TR. >> >> (3) An RLE, where the RLOC-record indicates that all RLOCs listed are u= sed (multicast replication). >> >>=20 >> >> You could use 1 or all combinations of these with filtering/policy sup= port on the map-server. >> >=20 >> > KJ: The priority you mentioned just represents the network-related capa= bility in the dynamic anycast viewpoint. However, if parameters to be requir= ed for selecting routing path are not only network-related metrics but also s= ervice-related metrics (i.e., computing loads, number of flows, etc.), we ne= ed other indirection for that. >>=20 >> If you want to control where packets go on the underay, you can also cons= ider draft-ietf-lisp-te. That is where ELPs are introduced and designed into= the LISP architecture. >>=20 >> >>=20 >> >>> >> >>=20 >> >> It is important to note that if you use equal priorities in an RLOC-se= t, that the ITR can load-split traffic across RLOCs and that will break conn= nection oriented applications (or applications that require remote state for= a session). >> >>=20 >> >> So an ITR that is configured that a particular EID in its map-cache is= an anycast-EID, it can use an RLOC-set above with each RLOC priority=3D1 an= d then choose based on the implementation's idea of what is a better RLOC to= use. >> >>=20 >> >> IMO opinion, the better way to design/implement this is using an anyca= st-EID-to-anycast-RLOC mapping. Which means you only need a register from on= e place (an SDN controller) or each ETR registering the same RLOC (without m= erge semantics). So the serivce is chosen by destination address in a packet= (the anycast-EID) which maps to an anycast-RLOC where the underlay takes yo= u to the "closest" LISP site. But closest is just one way of getting to a se= rvice. You may have other ways and hence why you introduced a metric. >> >=20 >> > KJ: In my understanding, in your suggestion, anycast RLOC is allocated= to the ETRs which can deliver packet destined to anycast-EID by internal ro= uting and routing between those ETRs are chosen in the underlay. Is it right= ?=20 >>=20 >> Yes. You assign the same RLOC address to multiple ETRs and have underlay r= outing take a source to the closest LISP site. >>=20 >> >>=20 >> >> Yes, it is better to gather the metrics data outside of LISP. But yes,= the control-plane could store it. I would suggest just mapping your collect= ion metrics to priorities so no protocol messages would need to be modified.= I believe LISP already has designed in everything you need. Do you agree? >> >=20 >> > KJ: yes. I agree with your point that LISP already has the solution to m= apping metrics to priorities. That is the one of reasons that I think that i= t is possible to provide dynamic anycast routing using LISP without huge mod= ifications. >>=20 >> Yes agree. Then the ITR came make an RLOC selection based on existing doc= umented approaches. But if the metrics change too much then the contents of t= he RLOC-set changes which requires more frequent map-cache updates. So we ha= ve to analyze this tradeoff more in depth. >>=20 >> > So, I think that we should not give fixed solutions on how to collect a= nd store metrics but we can mention possible solutions for that. Because it i= s more implemental issue. Is it right approach? >>=20 >> Yes, I agree. >>=20 >> > >> >>=20 >> >> Yes, it can, see draft-rodrigueznatal-lisp-multi-tuple-eids. >> >=20 >> > KJ: Thank you for giving that information. I will check and update =20= >>=20 >> Thanks again, >> Dino >>=20 >=20 >=20 > --=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > =EC=84=A0=EA=B2=BD=EC=9E=AC / Kyoungjae Sun (KJ Sun) >=20 > =EC=97=B0=EA=B5=AC=EC=9B=90 / =ED=81=B4=EB=9D=BC=EC=9A=B0=EB=93=9C =EB=B0=8F= =EB=84=A4=ED=8A=B8=EC=9B=8C=ED=81=AC =EC=97=B0=EA=B5=AC=EC=8B=A4 >=20 > Researcher / Distributed Cloud and Network lab >=20 > Office : +82-2-814-0151 Phone : +82-10-3643-5627 >=20 > Email : gomjae@dcn.ssu.ac.kr >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --Apple-Mail-871EEDCA-DB81-4411-98E7-51D96A59E43E Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Tha= nks again KJ.

Dino

On Aug 11, 2021, at 6:14 P= M, =EC=84=A0=EA=B2=BD=EC=9E=AC <gomjae@dcn.ssu.ac.kr> wrote:

=EF=BB=BF
Dino,

Thank you for discussing this topic. It was very help= ful for making clear to our proposal.

I will update draft depending o= n these discussions.

Additional comments and discussion by LISP folks= are always welcome.

Sincerely

KJ.
=E1=90=A7

2021=EB=85=84 8=EC=9B=94 12=EC=9D=BC (=EB=AA=A9= ) =EC=98=A4=EC=A0=84 5:29, Dino Farinacci <farinacci@gmail.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:
> First of all, t= hank you very much to give detailed comments on our draft. Please check answ= ers for your comments inline.

KJ, thanks for the quick response. I have cut out the text where I agree/acc= ept with your responses. See inline for additional commentary and answers to= your questions.

Once you update the spec, I'll give another thorough review. Thanks!

>
>> Which indicates that ETR only wants packets sent to C and D when A a= nd B are not reachable from the ITR (by using multiple mechanisms but the mo= st robust is RLOC-probing).
>>
>> Note the use of an RLOC-set comes in multiple forms:
>>
>> (1) A list like above (default)
>> (2) An ELP, where the RLOC-record indicates a encap-path from ITR t= o ETR.
>> (3) An RLE, where the RLOC-record indicates that all RLOCs listed a= re used (multicast replication).
>>
>> You could use 1 or all combinations of these with filtering/policy s= upport on the map-server.
>
> KJ: The priority you mentioned just represents the network-related capa= bility in the dynamic anycast viewpoint. However, if parameters to be requir= ed for selecting routing path are not only network-related metrics but also s= ervice-related metrics (i.e., computing loads, number of flows, etc.), we ne= ed other indirection for that.

If you want to control where packets go on the underay, you can also conside= r draft-ietf-lisp-te. That is where ELPs are introduced and designed into th= e LISP architecture.

>>
>>> <PastedGraphic-39.png>
>>
>> It is important to note that if you use equal priorities in an RLOC= -set, that the ITR can load-split traffic across RLOCs and that will break c= onnnection oriented applications (or applications that require remote state f= or a session).
>>
>> So an ITR that is configured that a particular EID in its map-cache= is an anycast-EID, it can use an RLOC-set above with each RLOC priority=3D1= and then choose based on the implementation's idea of what is a better RLOC= to use.
>>
>> IMO opinion, the better way to design/implement this is using an an= ycast-EID-to-anycast-RLOC mapping. Which means you only need a register from= one place (an SDN controller) or each ETR registering the same RLOC (withou= t merge semantics). So the serivce is chosen by destination address in a pac= ket (the anycast-EID) which maps to an anycast-RLOC where the underlay takes= you to the "closest" LISP site. But closest is just one way of getting to a= service. You may have other ways and hence why you introduced a metric.
= >
> KJ: In my understanding, in your suggestion, anycast RLOC is allo= cated to the ETRs which can deliver packet destined to anycast-EID by intern= al routing and routing between those ETRs are chosen in the underlay. Is it r= ight?

Yes. You assign the same RLOC address to multiple ETRs and have underlay rou= ting take a source to the closest LISP site.

>>
>> Yes, it is better to gather the metrics data outside of LISP. But y= es, the control-plane could store it. I would suggest just mapping your coll= ection metrics to priorities so no protocol messages would need to be modifi= ed. I believe LISP already has designed in everything you need. Do you agree= ?
>
> KJ: yes. I agree with your point that LISP already has the solution to m= apping metrics to priorities. That is the one of reasons that I think that i= t is possible to provide dynamic anycast routing using LISP without huge mod= ifications.

Yes agree. Then the ITR came make an RLOC selection based on existing docume= nted approaches. But if the metrics change too much then the contents of the= RLOC-set changes which requires more frequent map-cache updates. So we have= to analyze this tradeoff more in depth.

> So, I think that we should not give fixed solutions on how to collect a= nd store metrics but we can mention possible solutions for that. Because it i= s more implemental issue. Is it right approach?

Yes, I agree.

> <PastedGraphic-45.png>
>>
>> Yes, it can, see draft-rodrigueznatal-lisp-multi-tuple-eids.
>
> KJ: Thank you for giving that information. I will check and updat= e

Thanks again,
Dino

--
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D

=EC=84=A0=EA=B2=BD=EC=9E=AC / Kyoungjae Sun (KJ Sun)
=
=EC=97=B0=EA=B5=AC=EC=9B=90 / =ED=81=B4=EB=9D=BC=EC=9A=B0=EB=93=9C =EB=B0= =8F =EB=84=A4=ED=8A=B8=EC=9B=8C=ED=81=AC =EC=97=B0=EA=B5=AC=EC=8B=A4

= Researcher / Distribute= d Cloud and Network lab

Office : +82-2-814-0151 P= hone : +82-10-3643-5627

Email : gomjae@dcn.ssu.ac.kr

=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D

= --Apple-Mail-871EEDCA-DB81-4411-98E7-51D96A59E43E-- From nobody Thu Aug 12 09:21:44 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DF4B3A1889 for ; Thu, 12 Aug 2021 09:21:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 od5tvrGYFYc7 for ; Thu, 12 Aug 2021 09:21:37 -0700 (PDT) Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBDA83A187F for ; Thu, 12 Aug 2021 09:21:36 -0700 (PDT) Received: from fraeml738-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GlsPK5vwYz6CBTL for ; Fri, 13 Aug 2021 00:20:53 +0800 (CST) Received: from msceml702-chm.china.huawei.com (10.219.141.160) by fraeml738-chm.china.huawei.com (10.206.15.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Thu, 12 Aug 2021 18:21:32 +0200 Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml702-chm.china.huawei.com (10.219.141.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 12 Aug 2021 19:21:31 +0300 Received: from msceml703-chm.china.huawei.com ([10.219.141.161]) by msceml703-chm.china.huawei.com ([10.219.141.161]) with mapi id 15.01.2176.012; Thu, 12 Aug 2021 19:21:31 +0300 From: Vasilenko Eduard To: "lisp@ietf.org" Thread-Topic: Comments on https://datatracker.ietf.org/doc/html/draft-ietf-lisp-mn-10 Thread-Index: AdePlfEkUc6zeCO+Suu8zKwBBcx4Gg== Date: Thu, 12 Aug 2021 16:21:31 +0000 Message-ID: <13e7e46d97c0401fb818bdf596964902@huawei.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.47.207.211] Content-Type: multipart/related; boundary="_004_13e7e46d97c0401fb818bdf596964902huaweicom_"; type="multipart/alternative" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: [lisp] Comments on https://datatracker.ietf.org/doc/html/draft-ietf-lisp-mn-10 X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2021 16:21:42 -0000 --_004_13e7e46d97c0401fb818bdf596964902huaweicom_ Content-Type: multipart/alternative; boundary="_000_13e7e46d97c0401fb818bdf596964902huaweicom_" --_000_13e7e46d97c0401fb818bdf596964902huaweicom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Guru, I have looked subject and have a few comments: 1. The draft does mention a few times "without triangle routing in th= e data path". But section 7.4: "As a result, packets may be natively forwarded to non-LIS= P sites by an ITR (the return path will through a PITR, however, since the = packet flow will be non-LISP site to LISP site)." Do I understand right that it is exactly "triangle routing"? Encapsulation = in both directions would be needed if you insist on "without triangle routi= ng" or you could delete the requirement. 2. All discussions are in the style that it is "handover", not "roami= ng". "Roaming" has been mentioned 28 times in the draft but it is exactly w= hat was *not* implemented. I mean: what if the next RLOC would be from a completely different administ= rative domain? What if not just link would be switched but Carrier would be= switched? IMHO: "roaming" is a mandatory case for the word "Mobile" in the title of t= he draft. Please, at least rename "roaming" to "handover" till roaming would be propo= sed. It is better to be accurate with Mobile terminology. 3. It has been mentioned that there is a requirement for "multi-homin= g", but it has not been discussed at all later. IMHO: an additional section is needed to explain how "TCP connections to st= ay alive while roaming" - probably "multi-homing" should help with this. [cid:image001.png@01D3A7DF.E7D86320] Best Regards Eduard Vasilenko Senior Architect Europe Standardization & Industry Development Department Tel: +7(985) 910-1105, +7(916) 800-5506 --_000_13e7e46d97c0401fb818bdf596964902huaweicom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Guru,

I have looked subject and have a few comments:<= /o:p>

1. &= nbsp; The draft does mention a few times “without t= riangle routing in the data path”.
But section 7.4: “As a result, packets may be natively forwarded to n= on-LISP sites by an ITR (the return path will through a PITR, however, sinc= e the packet flow will be non-LISP site to LISP site).”
Do I understand right that it is exactly “triangle routing”? En= capsulation in both directions would be needed if you insist on “with= out triangle routing” or you could delete the requirement.=

2. &= nbsp; All discussions are in the style that it is “= handover”, not “roaming”. “Roaming” has been = mentioned 28 times in the draft but it is exactly what was *not* imp= lemented.
I mean: what if the next RLOC would be from a completely different administ= rative domain? What if not just link would be switched but Carrier would be= switched?
IMHO: “roaming” is a mandatory case for the word “Mobile&= #8221; in the title of the draft.
Please, at least rename “roaming” to “handover” til= l roaming would be proposed. It is better to be accurate with Mobile termin= ology.

3. &= nbsp; It has been mentioned that there is a requirement f= or “multi-homing”, but it has not been discussed at all later.<= br> IMHO: an additional section is needed to explain how “TCP connections= to stay alive while roaming” – probably “multi-homing= 221; should help with this.

3D"cid:image001.png@01D3A7DF.E7D86320"

Best Regards

Eduard Vasilenko<= /o:p>

Senior Architect<= /o:p>

Europe Standardization= & Industry Development Department

Tel: +7(985) 910-1= 105, +7(916) 800-5506

--_000_13e7e46d97c0401fb818bdf596964902huaweicom_-- --_004_13e7e46d97c0401fb818bdf596964902huaweicom_ Content-Type: image/png; name="image001.png" Content-Description: image001.png Content-Disposition: inline; filename="image001.png"; size=4883; creation-date="Thu, 12 Aug 2021 16:21:31 GMT"; modification-date="Thu, 12 Aug 2021 16:21:31 GMT" Content-ID: Content-Transfer-Encoding: base64 iVBORw0KGgoAAAANSUhEUgAAAGYAAAAgCAIAAABvvJpEAAAAAXNSR0IArs4c6QAAEs1JREFUaEPd molzHEWWxl9VV9/duk9LtizLt7AxvgAPNwbG2Bwz2IMJYJeIJQZid4EIjoVlmGOJ2GF3OWYWYtgZ BphlYIGB4RgfgDE+8IUP2fiUTyzLsu5Wq9V3V3VX7a+VhP4IZUgZWVmZL/N9+b33sjJbcwb6JeDK BiUpbpf4vOIJpKSYdDH9EpdkRhIBcYelQnf0fE50l+iOGI4U/3WtoElexB7t4RNbs5Pi5IqdxWNq 4QKVumijb8dN0sUfFLdXF7cBAEo7Q8QlxWI2p+WG68WoFN1jZajW3aKBF291WxxTsnErkwIw2oJh AaQcTUCxQMFFDRUKzfGUwMovLq8hHkNcmhhQJucZhcx0PKJXWpqRyshwWnp7pJDLOZbj2JLPSyEp +aRoaZ8r43Ky9OLPAhjbI7a7mIsb3GBZEbjxlTQnX1TKFiuP6uLhwYs1mSJpjNCS7pNy+qR0dqdD Qf+ypdnyCr8RlsEBc7DDLVmtrFTKyiVQldL9mubHGn0FW+y8aFivKzVKMf8oa8dT0rKWA6WKvskt w6OkKHdEy1LKSccZ5/13z+/c3tfXo89qnvrw/eVXXiU5L/VnTu7WzFh1aUmgrsFunuUunazZIduR vF7kqgvKYdaG5G0BSOSPp6RjZ/iwUW9keyUflLyGwoW8JOK9a9a2f7LOPHKiLB53D/QlTxwTPJeZ dUaiPidd4nNcZjR24VSs85SWjoplQUog/955OeKzMc5iIBhnSfcR99AJJtjpQDLmjUUlmRQzJ2e+ 69i+w7zQU2MY0+tqm4JBp+O89AzIcLwQHwk4heqKQLDMm88MZbvO5TvPi23i49zprJbOSsEq0jUv Xgg77vw/oW3UGjHFdFx6B4ugxKOSTcm58/nufn8hb6dTdiIeMPNGf1QiI+L1FZKZTE+/RGKSy+q5 jDcWN+IjBAcppLVkyoglJDUiFvHBFJsAMN6SXuRYNil2wuk5d+Tfnjvzy+ck0kvYFCsXsu1YMhYq K3PhweNZVzQjsbSkssl4yjtsykg+0dHtK2i+RFqGo4Jt6lbXXz7Y/dx/yrEjkmd3lxaNOFJ0bI7j FAqFfD5v29+zzjR5VUxUjjVQb8nHCjxmMhnyHOHacVTjeDw+1pFCOp1WolS9SqoXXdRACBwaGlJy yGOxGPNRLYeH8eHFRBvaq4KqSSQS2WxWPSqBqVRKz6Zi4tfETJ/fsiW+fWdi267Cus/EykpFmF1Y XWVNPBK10rlsPO3JOhJPS2Ikl0qGTV06h7yDWW0wk44lJRRgz2pt2zy8Y1t8x46udeul61wxgORG CKAKKZfLZRiGruuUmYfHw0akmDRNUxOlQK4aK3TULP1+oq54vV4aIIFyIBAgR5SCg4ISFQqxyjZY kFQvCpZlIYf6ysrKsVFKSkqYD28ZqLy8XK0ELUnUkKtlCIfDPp9PTUzlbrdbt0txY1ah7eDpv/7N 39tTMhQ5/tEnsn2HtNSXTa33aYYft56zdJc7NRKXjCm5VGwwYo9kpSfp6bULpwZzbCwm1MmF7rPr 14V6uir6urv+tl72HihCRozQGauYlFYqMbCCiZypqwmh+VhLhW8wGFRcUECgicIICCALNbRHW7RS 0pBAoi85DVBbCQE+hTXkYqngjkJZQUYBsSRWhbfIpMCq8IqWYzxVa1wcgI295K3uXfszx043hkKT SoL2yY7IO+/Bu8mLLkmm4gGvp0gKwz3Y1yvplGTSuYG+1ACWKNKXy19ITJwwqfjtsHGzdehoVTrW 7NG9F3oyh9slC8C6zSZjVAcURg650koZCAorFozhwlvUGzMNxUp0owtAK81ZfBTjkTS2DAinrHJk oiFv1YjIV1iXlZUptceaUQYUMFVrQ47pKdIp7MiRoHqxBkzD9dSvnvGm08l1X9lHTpTkc3o2Fy4Y keFoVW2JzGjx7Ducj8WSuRQbrqiVa5g7my1csv2YPjRUgpye4UC4Ur/lh9LV1ff+Wt+5C4We84aV cVBw4sTA1VdkSstdxU/X4rTQnBkwcG9v79GjR5kKChRnMJp4PHPmTGdnJ5PDak6fPn3o0CHVRqFG m76+voMHD6I8Jqb4CBbIPHfu3Pnz56nHxMAUODo6Or777rvq6mqwYGja0P3s2bNIiEaj9fX1Cnow Rcjhw4dxgpBRTQ+s8W5M4MKFC4zb1dWFE6yrq6M9Yunu+uWvnjXSpvbNvtzJU+bQgGaa1cGKZDJ5 fqivdv58T8AfPX6UPUcilQpOqCyfOpkoaZ/rzEeGTZBM5vzzF8q0qcMfrYls393g2PnoSM7MmwGP e8bM0HU3SFmte3Tbp4xILe+aNWteeumlU6dOTZ48GZWYNzM+ceLEiy+++Mc//nHatGnTp09///33 33zzzZGRkUWLFtFAcWTjxo0vvPACGs6ePRuioTZ0OHbs2BNPPPHWW28hkHrgpsE777zz7LPP8vbi iy9W0IDg008//corr+zZs4dxJ0yYAJuwu2+++Yb6devWzZ8/n2bt7e2/+93vXn755T//+c9/GU1M iSVBMo2Z4RtvvKF7M5roofD0mSUN9S5vkcxwKsAu9HCnfLldZk/0L2z2BI0g9uVYYuckk3AN9FkD /cMjUbO+XKY0yxf74hsPuIZHrHS8MiguPk2bqmsXzpNgtQeyj8YlxRQK2OPJkye3bt26b98+1h/N eaWodOTIkW+//ba7uxtV29ratmzZAhmVr1FqRyKRzZs3b9q0SZGLSrzYhg0bqAG4tWvX7ty5k2bN zc3ksIO1gX2KaPB327Ztx48fZ+gdO3YAN0NXVFR88cUX27dvh0dTpkyBhr/97W+fe+45WsJKSEqb qqqqmpoaWIYQZkVjXTq6JGfJksUlrVOztZUjAW+3GS/xh6sK7u4NW2UkVjJ3bt5wh0tKowNDgmcK hBN9kfhgjJOemqZGYmXmi02uC5FqX2nfUGrQkFipXt46Ta67iqAix85akWIIH4MMJQEI8lMDI5Tf wUcAKGqgKhryFppTQCXc8Fj4Uw6YHDUoYD5Yyscff4yoyy67DLXh5uDgIG8vueSS2tra3bt3wxpa Il9ZJTKhOWrTDLGMAoKgv3LlSob+4IMP3n333UmTJr322muffvrp22+/jXDW4+GHH0YmpkDf4hpv /eUze372mETOh//1kZl/v3qwvkbzVmgcB3ncmWQmsn6btMyvvXhJNG/UVTRxqCYWR2olnKq5dUO7 dqls2hTpOuszdMd0vDW152vqGlbdUf6P90u0V/7j2T0/e1Lr64FZimIsFJBhZcAEFlAdvij/Ohbm aUYlnkVFKxUox3w8i08lU6c9s//666/37t27bNkyDLalpeWrr76CCHT/wQ9+cNFFF9GLR5BlLMjI klx33XVwEIeIPwVoSI3DYkq33HILgNId4Ghz5513NjY2wiwWlZkgGVGowCMo66nDR/d++Mk7//J0 7MNPjWtuuOyxJxovbu1OxTOFgkczEmf75UC7LFoULy1NW5oEKkT3xgz3kNeY/JNV0nZwaN9+r2kW bIsunsYJC1atDt6+Sjr7jz35i50v/3fVQMTNt9coy4AGsFCVnDI+5aGHHkLb66+//p577nnssccw Q7WrgAvKVakQSV9QQHPwYtKKg9Rj4H/6059g06233orPuuuuu9iXvffee7Sncvny5QjBNmkMp/CD eMnHH398xowZ8AXuMCtoiDufN28erg1XiE+g75dffokouq9YsWLVqlU333wzj0gg5rD2paWlus/S GvWwvu/cZ0++1PvMi5K0An+3aso/3VveWON19ExP1DxzTha2tqy4LmLZUlIts1p7XI6xuFWuXiwn vkt09AQ1I1xTPufu5bWPPyCTmnv//eXdDzzjbR+8qLQpMTAi5vd7H/hPQlV0psCi4V+wLNwQVoP7 RzdcMgk7UkykAMS0B0SioQIOiqkNCvzav38/OkAiUMCpU4814dEBF2jwQcCKU0M+kQTWtLa2AhAS GJS1YXQGuummmxDClKgHMvZu+FniNWGEoIHvV58KzIcCybji1hXvvPqHioI+pazx2+1bzuxtW3LL ta4F84I/vTe4a9/A/raNB9sWfDWxbtnN7kMdxTPsTCJbU7Vs5Wp7T9uR4+3VlZXBOa0yZ5pMqcmt WXfqm2+9KZkkoWgimikJzLvqSqmrg/lqy0MOBMoeFy5cSKRDMcrMGBshHh04cACvweypgXFwSu3F lROBm7hkgCANDAxga2CKicFQaIUyQAZYhD9Ih33h4HD/69evZ53gCCyjOzb76quvsqEhJgINU7ri iiuYocKL7lD+gQceYOj+/n5qWCRsGbiZNiECBHXvNYvzMyf2SiGSy5RJeZU70Ln7YNv//EGinfLD +XN+8c9Tli89sv+Y9MSm/eT2zOwGZ1L1nOW3iLt657pt4XmzJjx0t6y4XMKe1BvvEzfrI9ZEx2/Y hu0KOzMny8XTpbZCuScSMwAOzAc4KKMVuoHdrFmzUI96FVKhGzBBN2IoiGCe4AXWkAUDARoeVfCi /cyZM0EExcjZCiAWLw4icHPx4sU0+PDDD3HqyGR5eGQHg29i2/X73/8emkMxgKC+qalpyZIlsBWk QBbOXnrppXPnzr3xxhvBGpsgXn+/lf3V6694da3j9JnOgY6w4c0XzK5Ynx7wrN27I1UwGyZMrFuw ZHKoZsQqlN57h9bS6JrRUtHQaB06GdK9jddczvH/qbZdpzZvzvcMGYkcx99D2VyXYxVmNDWvXGas XCGhoHiKe+ixjzXiOhsI1u3HP/4xFlf8BM3nMR/iHdy54YYbrrrqKiYHWTArXkFP1vbzzz+HF+B1 ++23o+fzzz/PloIyjv/RRx9dvXr1fffdxwLAVvACU/ZZQENAZGNBMIW8v/nNbyAvC0ANE+jpKcYl vJvakRGdYTQ+DpPEbFkSfAW2SUssHW6y5NAT34fKPY45nNyy4Q/XXv3m5OYtc+asa6rfMH3S1sWt n0xpWN/YnPqHh53//auzY4/jJHucVLszkHYS9qEDzucbnP96YdOlC//aUr+tdUp7S9OF5ml9k2ef mnXJ8Tt/kvq/15z+Y44Tsa0kU1GJKUKTRx55BK5BMWiCOahX6H/llVcydbaRVKLkU0891dDQANZQ Un2HAvr999+P/yK0Kc/4+uuvqxMONCGn189//nPqsVM8Hbg/+OCD6svp6quvpgEejRzeTZw4EYHs Jz777DP1KU4iaP76179esGCB+mhXg5LwgHg9FhXaArqWctK5xFC5o0s8Jd91SHt7frDXqKyW/mEO 9aUrlomN5ObNKnvwnk4r5lTUcuyKpZXmCpGP19r7DtWwt68tL558MEDGkmCZtDTJlAnSVCnlAc6D /HbQrwcgNo5WfY6ADosP5y+//HK1w4JHrDmehaB52223wQ6MlEqWGnTQE67hv7AsbAc4wJq4hiZL ly5FAsLVZzZYsySEUUa5++67+TBCIGNBOlAg/CEHIIiMODhMHiPFkQEc4LIeYId14w127dql4g+N sWgME8SJPx999BF2oEUd7jBtT//A8Q0b4WtJwaovDXmGEhOzXmsgOZK0Cs1NpT+6oWzZtVJVljQL Ia5C2JBnM9aefdE1X+YPtzNlb3mJWAmprmGvn8ibxrxW/x03yYyGAXEqpNQYXxcmWr+TKhWXe2Bg /9/WrXnrrbPftnFr2egNB0esgC88ddGll65e5bnxGqmpYrvPgXeBs8Zyf/GuYHjQ2brj7JdfRfbs T3X3hksD/fGR4ZwZntay+K5VE+69QyZVx8UVEG78xtUFgOuJp58Iubwuj6+hYdLk6lotV8j0RhNZ KzB/1sz7Vi548qf+65eILyTZAqd84tb0MB/aBDZTyvza3KbSRTOSpe6oVjh9oTvlMULzW+fd+aNJ y2+UhvqcIamC5de5Vx5X9+WciHK1YTt8uBhuLtHsw0c72w5lLHPq0svd0xrTvrAtRiDnuDQfRmdm TC3o4UbcpdmOu5CRvCE5fyIh0UzvZ5t9Lnd4WpPBAVG4hFP/gm64PHw8A/C4YpnmjKQk4EkW0mbe qvD6+VEBt8BSEuLOKWHlMvmC189PKwzTyfn4kYXXl8pYLj+XbcBQcJlpT95ycb4IjfiINEGfyziP 43Zz/+vKAq1H3Pr4cmX8xGJgWMpCJgzjkGD0PtMUwqcrk0v7vX7X6DVulAMzx6zS+JGLAWHAKy55 dvRh4gD3vY6VSic8oZCmu3jLXTlXo/x4w5W0JZUmaIyzu19+YAA1Cpbt2Jpuag6fgF5HMzOWzzN6 RszeI5nkNxsciwPP0OBA0MsNQsDlcdEjm01LwQ64vRqPXHFwAcFJi5Xh2Mfv43TDA4Ljyo2NbtOK viyVTAY9YQ6cOYHnGzrE1QaHoMXTQad4+YTeGJ2T5VbS4+ZXKnqRkFyyG3qhyCpx8bbAhSUnXkXQ Kfo1gyNYPp0tsULFe4Fxlf4f3/ybFLzs5LEAAAAASUVORK5CYII= --_004_13e7e46d97c0401fb818bdf596964902huaweicom_-- From nobody Thu Aug 12 10:11:54 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F5ED3A4322 for ; Thu, 12 Aug 2021 10:11:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 0Q4bqNP08O3P for ; Thu, 12 Aug 2021 10:11:46 -0700 (PDT) Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FA1A3A4323 for ; Thu, 12 Aug 2021 10:11:46 -0700 (PDT) Received: from fraeml714-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GltW954y2z6FBQ0 for ; Fri, 13 Aug 2021 01:11:01 +0800 (CST) Received: from msceml705-chm.china.huawei.com (10.219.141.144) by fraeml714-chm.china.huawei.com (10.206.15.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Thu, 12 Aug 2021 19:11:41 +0200 Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml705-chm.china.huawei.com (10.219.141.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 12 Aug 2021 20:11:41 +0300 Received: from msceml703-chm.china.huawei.com ([10.219.141.161]) by msceml703-chm.china.huawei.com ([10.219.141.161]) with mapi id 15.01.2176.012; Thu, 12 Aug 2021 20:11:41 +0300 From: Vasilenko Eduard To: "lisp@ietf.org" Thread-Topic: Comments on https://datatracker.ietf.org/doc/html/draft-ietf-lisp-mn-10 Thread-Index: AdePlfEkUc6zeCO+Suu8zKwBBcx4GgABqDOA Date: Thu, 12 Aug 2021 17:11:41 +0000 Message-ID: <1e30dd88b7a74a92aa21b0225fd414ec@huawei.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.47.207.211] Content-Type: multipart/related; boundary="_004_1e30dd88b7a74a92aa21b0225fd414echuaweicom_"; type="multipart/alternative" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: Re: [lisp] Comments on https://datatracker.ietf.org/doc/html/draft-ietf-lisp-mn-10 X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2021 17:11:51 -0000 --_004_1e30dd88b7a74a92aa21b0225fd414echuaweicom_ Content-Type: multipart/alternative; boundary="_000_1e30dd88b7a74a92aa21b0225fd414echuaweicom_" --_000_1e30dd88b7a74a92aa21b0225fd414echuaweicom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable One additional comment: 4. I have seen assumptions that Map server and proxy to Non-LISP are on the= same box. It is a potential bottleneck in the future. DHCP would deliver only 1 Map Server IP to RLOC. Hence all overlays would s= hare the same Map Server. Proxy is a router with a low capacity CPU. It could become a bottleneck if = LISP implementation would become big enough. It is better to assume initially the general case that Map Server and Proxy= are different boxes (not collocated). Eduard From: Vasilenko Eduard Sent: Thursday, August 12, 2021 7:23 PM To: 'lisp@ietf.org' Subject: Comments on https://datatracker.ietf.org/doc/html/draft-ietf-lisp-= mn-10 Hi Guru, I have looked subject and have a few comments: 1. The draft does mention a few times "without triangle routing in th= e data path". But section 7.4: "As a result, packets may be natively forwarded to non-LIS= P sites by an ITR (the return path will through a PITR, however, since the = packet flow will be non-LISP site to LISP site)." Do I understand right that it is exactly "triangle routing"? Encapsulation = in both directions would be needed if you insist on "without triangle routi= ng" or you could delete the requirement. 2. All discussions are in the style that it is "handover", not "roami= ng". "Roaming" has been mentioned 28 times in the draft but it is exactly w= hat was *not* implemented. I mean: what if the next RLOC would be from a completely different administ= rative domain? What if not just link would be switched but Carrier would be= switched? IMHO: "roaming" is a mandatory case for the word "Mobile" in the title of t= he draft. Please, at least rename "roaming" to "handover" till roaming would be propo= sed. It is better to be accurate with Mobile terminology. 3. It has been mentioned that there is a requirement for "multi-homin= g", but it has not been discussed at all later. IMHO: an additional section is needed to explain how "TCP connections to st= ay alive while roaming" - probably "multi-homing" should help with this. [cid:image001.png@01D3A7DF.E7D86320] Best Regards Eduard Vasilenko Senior Architect Europe Standardization & Industry Development Department Tel: +7(985) 910-1105, +7(916) 800-5506 --_000_1e30dd88b7a74a92aa21b0225fd414echuaweicom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

One additional comment= :

4. I have seen assumpt= ions that Map server and proxy to Non-LISP are on the same box. It is a pot= ential bottleneck in the future.
DHCP would deliver only 1 Map Server IP to RLOC. Hence all overlays would s= hare the same Map Server.

Proxy is a router with= a low capacity CPU. It could become a bottleneck if LISP implementation wo= uld become big enough.

It is better to assume= initially the general case that Map Server and Proxy are different boxes (= not collocated).

Eduard

From: Vasilenko Eduard
Sent: Thursday, August 12, 2021 7:23 PM
To: 'lisp@ietf.org' <lisp@ietf.org>
Subject: Comments on https://datatracker.ietf.org/doc/html/draft-iet= f-lisp-mn-10

Hi Guru,

I have looked subject and have a few comments:<= /o:p>

3D"cid:image001.png@01D3A7DF.E7D86320"

Best Regards

Eduard Vasilenko<= /o:p>

Senior Architect<= /o:p>

Europe Standardization= & Industry Development Department

Tel: +7(985) 910-1= 105, +7(916) 800-5506

--_000_1e30dd88b7a74a92aa21b0225fd414echuaweicom_-- --_004_1e30dd88b7a74a92aa21b0225fd414echuaweicom_ Content-Type: image/png; name="image001.png" Content-Description: image001.png Content-Disposition: inline; filename="image001.png"; size=4883; creation-date="Thu, 12 Aug 2021 17:11:41 GMT"; modification-date="Thu, 12 Aug 2021 17:11:41 GMT" Content-ID: Content-Transfer-Encoding: base64 iVBORw0KGgoAAAANSUhEUgAAAGYAAAAgCAIAAABvvJpEAAAAAXNSR0IArs4c6QAAEs1JREFUaEPd molzHEWWxl9VV9/duk9LtizLt7AxvgAPNwbG2Bwz2IMJYJeIJQZid4EIjoVlmGOJ2GF3OWYWYtgZ BphlYIGB4RgfgDE+8IUP2fiUTyzLsu5Wq9V3V3VX7a+VhP4IZUgZWVmZL/N9+b33sjJbcwb6JeDK BiUpbpf4vOIJpKSYdDH9EpdkRhIBcYelQnf0fE50l+iOGI4U/3WtoElexB7t4RNbs5Pi5IqdxWNq 4QKVumijb8dN0sUfFLdXF7cBAEo7Q8QlxWI2p+WG68WoFN1jZajW3aKBF291WxxTsnErkwIw2oJh AaQcTUCxQMFFDRUKzfGUwMovLq8hHkNcmhhQJucZhcx0PKJXWpqRyshwWnp7pJDLOZbj2JLPSyEp +aRoaZ8r43Ky9OLPAhjbI7a7mIsb3GBZEbjxlTQnX1TKFiuP6uLhwYs1mSJpjNCS7pNy+qR0dqdD Qf+ypdnyCr8RlsEBc7DDLVmtrFTKyiVQldL9mubHGn0FW+y8aFivKzVKMf8oa8dT0rKWA6WKvskt w6OkKHdEy1LKSccZ5/13z+/c3tfXo89qnvrw/eVXXiU5L/VnTu7WzFh1aUmgrsFunuUunazZIduR vF7kqgvKYdaG5G0BSOSPp6RjZ/iwUW9keyUflLyGwoW8JOK9a9a2f7LOPHKiLB53D/QlTxwTPJeZ dUaiPidd4nNcZjR24VSs85SWjoplQUog/955OeKzMc5iIBhnSfcR99AJJtjpQDLmjUUlmRQzJ2e+ 69i+w7zQU2MY0+tqm4JBp+O89AzIcLwQHwk4heqKQLDMm88MZbvO5TvPi23i49zprJbOSsEq0jUv Xgg77vw/oW3UGjHFdFx6B4ugxKOSTcm58/nufn8hb6dTdiIeMPNGf1QiI+L1FZKZTE+/RGKSy+q5 jDcWN+IjBAcppLVkyoglJDUiFvHBFJsAMN6SXuRYNil2wuk5d+Tfnjvzy+ck0kvYFCsXsu1YMhYq K3PhweNZVzQjsbSkssl4yjtsykg+0dHtK2i+RFqGo4Jt6lbXXz7Y/dx/yrEjkmd3lxaNOFJ0bI7j FAqFfD5v29+zzjR5VUxUjjVQb8nHCjxmMhnyHOHacVTjeDw+1pFCOp1WolS9SqoXXdRACBwaGlJy yGOxGPNRLYeH8eHFRBvaq4KqSSQS2WxWPSqBqVRKz6Zi4tfETJ/fsiW+fWdi267Cus/EykpFmF1Y XWVNPBK10rlsPO3JOhJPS2Ikl0qGTV06h7yDWW0wk44lJRRgz2pt2zy8Y1t8x46udeul61wxgORG CKAKKZfLZRiGruuUmYfHw0akmDRNUxOlQK4aK3TULP1+oq54vV4aIIFyIBAgR5SCg4ISFQqxyjZY kFQvCpZlIYf6ysrKsVFKSkqYD28ZqLy8XK0ELUnUkKtlCIfDPp9PTUzlbrdbt0txY1ah7eDpv/7N 39tTMhQ5/tEnsn2HtNSXTa33aYYft56zdJc7NRKXjCm5VGwwYo9kpSfp6bULpwZzbCwm1MmF7rPr 14V6uir6urv+tl72HihCRozQGauYlFYqMbCCiZypqwmh+VhLhW8wGFRcUECgicIICCALNbRHW7RS 0pBAoi85DVBbCQE+hTXkYqngjkJZQUYBsSRWhbfIpMCq8IqWYzxVa1wcgI295K3uXfszx043hkKT SoL2yY7IO+/Bu8mLLkmm4gGvp0gKwz3Y1yvplGTSuYG+1ACWKNKXy19ITJwwqfjtsHGzdehoVTrW 7NG9F3oyh9slC8C6zSZjVAcURg650koZCAorFozhwlvUGzMNxUp0owtAK81ZfBTjkTS2DAinrHJk oiFv1YjIV1iXlZUptceaUQYUMFVrQ47pKdIp7MiRoHqxBkzD9dSvnvGm08l1X9lHTpTkc3o2Fy4Y keFoVW2JzGjx7Ducj8WSuRQbrqiVa5g7my1csv2YPjRUgpye4UC4Ur/lh9LV1ff+Wt+5C4We84aV cVBw4sTA1VdkSstdxU/X4rTQnBkwcG9v79GjR5kKChRnMJp4PHPmTGdnJ5PDak6fPn3o0CHVRqFG m76+voMHD6I8Jqb4CBbIPHfu3Pnz56nHxMAUODo6Or777rvq6mqwYGja0P3s2bNIiEaj9fX1Cnow Rcjhw4dxgpBRTQ+s8W5M4MKFC4zb1dWFE6yrq6M9Yunu+uWvnjXSpvbNvtzJU+bQgGaa1cGKZDJ5 fqivdv58T8AfPX6UPUcilQpOqCyfOpkoaZ/rzEeGTZBM5vzzF8q0qcMfrYls393g2PnoSM7MmwGP e8bM0HU3SFmte3Tbp4xILe+aNWteeumlU6dOTZ48GZWYNzM+ceLEiy+++Mc//nHatGnTp09///33 33zzzZGRkUWLFtFAcWTjxo0vvPACGs6ePRuioTZ0OHbs2BNPPPHWW28hkHrgpsE777zz7LPP8vbi iy9W0IDg008//corr+zZs4dxJ0yYAJuwu2+++Yb6devWzZ8/n2bt7e2/+93vXn755T//+c9/GU1M iSVBMo2Z4RtvvKF7M5roofD0mSUN9S5vkcxwKsAu9HCnfLldZk/0L2z2BI0g9uVYYuckk3AN9FkD /cMjUbO+XKY0yxf74hsPuIZHrHS8MiguPk2bqmsXzpNgtQeyj8YlxRQK2OPJkye3bt26b98+1h/N eaWodOTIkW+//ba7uxtV29ratmzZAhmVr1FqRyKRzZs3b9q0SZGLSrzYhg0bqAG4tWvX7ty5k2bN zc3ksIO1gX2KaPB327Ztx48fZ+gdO3YAN0NXVFR88cUX27dvh0dTpkyBhr/97W+fe+45WsJKSEqb qqqqmpoaWIYQZkVjXTq6JGfJksUlrVOztZUjAW+3GS/xh6sK7u4NW2UkVjJ3bt5wh0tKowNDgmcK hBN9kfhgjJOemqZGYmXmi02uC5FqX2nfUGrQkFipXt46Ta67iqAix85akWIIH4MMJQEI8lMDI5Tf wUcAKGqgKhryFppTQCXc8Fj4Uw6YHDUoYD5Yyscff4yoyy67DLXh5uDgIG8vueSS2tra3bt3wxpa Il9ZJTKhOWrTDLGMAoKgv3LlSob+4IMP3n333UmTJr322muffvrp22+/jXDW4+GHH0YmpkDf4hpv /eUze372mETOh//1kZl/v3qwvkbzVmgcB3ncmWQmsn6btMyvvXhJNG/UVTRxqCYWR2olnKq5dUO7 dqls2hTpOuszdMd0vDW152vqGlbdUf6P90u0V/7j2T0/e1Lr64FZimIsFJBhZcAEFlAdvij/Ohbm aUYlnkVFKxUox3w8i08lU6c9s//666/37t27bNkyDLalpeWrr76CCHT/wQ9+cNFFF9GLR5BlLMjI klx33XVwEIeIPwVoSI3DYkq33HILgNId4Ghz5513NjY2wiwWlZkgGVGowCMo66nDR/d++Mk7//J0 7MNPjWtuuOyxJxovbu1OxTOFgkczEmf75UC7LFoULy1NW5oEKkT3xgz3kNeY/JNV0nZwaN9+r2kW bIsunsYJC1atDt6+Sjr7jz35i50v/3fVQMTNt9coy4AGsFCVnDI+5aGHHkLb66+//p577nnssccw Q7WrgAvKVakQSV9QQHPwYtKKg9Rj4H/6059g06233orPuuuuu9iXvffee7Sncvny5QjBNmkMp/CD eMnHH398xowZ8AXuMCtoiDufN28erg1XiE+g75dffokouq9YsWLVqlU333wzj0gg5rD2paWlus/S GvWwvu/cZ0++1PvMi5K0An+3aso/3VveWON19ExP1DxzTha2tqy4LmLZUlIts1p7XI6xuFWuXiwn vkt09AQ1I1xTPufu5bWPPyCTmnv//eXdDzzjbR+8qLQpMTAi5vd7H/hPQlV0psCi4V+wLNwQVoP7 RzdcMgk7UkykAMS0B0SioQIOiqkNCvzav38/OkAiUMCpU4814dEBF2jwQcCKU0M+kQTWtLa2AhAS GJS1YXQGuummmxDClKgHMvZu+FniNWGEoIHvV58KzIcCybji1hXvvPqHioI+pazx2+1bzuxtW3LL ta4F84I/vTe4a9/A/raNB9sWfDWxbtnN7kMdxTPsTCJbU7Vs5Wp7T9uR4+3VlZXBOa0yZ5pMqcmt WXfqm2+9KZkkoWgimikJzLvqSqmrg/lqy0MOBMoeFy5cSKRDMcrMGBshHh04cACvweypgXFwSu3F lROBm7hkgCANDAxga2CKicFQaIUyQAZYhD9Ih33h4HD/69evZ53gCCyjOzb76quvsqEhJgINU7ri iiuYocKL7lD+gQceYOj+/n5qWCRsGbiZNiECBHXvNYvzMyf2SiGSy5RJeZU70Ln7YNv//EGinfLD +XN+8c9Tli89sv+Y9MSm/eT2zOwGZ1L1nOW3iLt657pt4XmzJjx0t6y4XMKe1BvvEzfrI9ZEx2/Y hu0KOzMny8XTpbZCuScSMwAOzAc4KKMVuoHdrFmzUI96FVKhGzBBN2IoiGCe4AXWkAUDARoeVfCi /cyZM0EExcjZCiAWLw4icHPx4sU0+PDDD3HqyGR5eGQHg29i2/X73/8emkMxgKC+qalpyZIlsBWk QBbOXnrppXPnzr3xxhvBGpsgXn+/lf3V6694da3j9JnOgY6w4c0XzK5Ynx7wrN27I1UwGyZMrFuw ZHKoZsQqlN57h9bS6JrRUtHQaB06GdK9jddczvH/qbZdpzZvzvcMGYkcx99D2VyXYxVmNDWvXGas XCGhoHiKe+ixjzXiOhsI1u3HP/4xFlf8BM3nMR/iHdy54YYbrrrqKiYHWTArXkFP1vbzzz+HF+B1 ++23o+fzzz/PloIyjv/RRx9dvXr1fffdxwLAVvACU/ZZQENAZGNBMIW8v/nNbyAvC0ANE+jpKcYl vJvakRGdYTQ+DpPEbFkSfAW2SUssHW6y5NAT34fKPY45nNyy4Q/XXv3m5OYtc+asa6rfMH3S1sWt n0xpWN/YnPqHh53//auzY4/jJHucVLszkHYS9qEDzucbnP96YdOlC//aUr+tdUp7S9OF5ml9k2ef mnXJ8Tt/kvq/15z+Y44Tsa0kU1GJKUKTRx55BK5BMWiCOahX6H/llVcydbaRVKLkU0891dDQANZQ Un2HAvr999+P/yK0Kc/4+uuvqxMONCGn189//nPqsVM8Hbg/+OCD6svp6quvpgEejRzeTZw4EYHs Jz777DP1KU4iaP76179esGCB+mhXg5LwgHg9FhXaArqWctK5xFC5o0s8Jd91SHt7frDXqKyW/mEO 9aUrlomN5ObNKnvwnk4r5lTUcuyKpZXmCpGP19r7DtWwt68tL558MEDGkmCZtDTJlAnSVCnlAc6D /HbQrwcgNo5WfY6ADosP5y+//HK1w4JHrDmehaB52223wQ6MlEqWGnTQE67hv7AsbAc4wJq4hiZL ly5FAsLVZzZYsySEUUa5++67+TBCIGNBOlAg/CEHIIiMODhMHiPFkQEc4LIeYId14w127dql4g+N sWgME8SJPx999BF2oEUd7jBtT//A8Q0b4WtJwaovDXmGEhOzXmsgOZK0Cs1NpT+6oWzZtVJVljQL Ia5C2JBnM9aefdE1X+YPtzNlb3mJWAmprmGvn8ibxrxW/x03yYyGAXEqpNQYXxcmWr+TKhWXe2Bg /9/WrXnrrbPftnFr2egNB0esgC88ddGll65e5bnxGqmpYrvPgXeBs8Zyf/GuYHjQ2brj7JdfRfbs T3X3hksD/fGR4ZwZntay+K5VE+69QyZVx8UVEG78xtUFgOuJp58Iubwuj6+hYdLk6lotV8j0RhNZ KzB/1sz7Vi548qf+65eILyTZAqd84tb0MB/aBDZTyvza3KbSRTOSpe6oVjh9oTvlMULzW+fd+aNJ y2+UhvqcIamC5de5Vx5X9+WciHK1YTt8uBhuLtHsw0c72w5lLHPq0svd0xrTvrAtRiDnuDQfRmdm TC3o4UbcpdmOu5CRvCE5fyIh0UzvZ5t9Lnd4WpPBAVG4hFP/gm64PHw8A/C4YpnmjKQk4EkW0mbe qvD6+VEBt8BSEuLOKWHlMvmC189PKwzTyfn4kYXXl8pYLj+XbcBQcJlpT95ycb4IjfiINEGfyziP 43Zz/+vKAq1H3Pr4cmX8xGJgWMpCJgzjkGD0PtMUwqcrk0v7vX7X6DVulAMzx6zS+JGLAWHAKy55 dvRh4gD3vY6VSic8oZCmu3jLXTlXo/x4w5W0JZUmaIyzu19+YAA1Cpbt2Jpuag6fgF5HMzOWzzN6 RszeI5nkNxsciwPP0OBA0MsNQsDlcdEjm01LwQ64vRqPXHFwAcFJi5Xh2Mfv43TDA4Ljyo2NbtOK viyVTAY9YQ6cOYHnGzrE1QaHoMXTQad4+YTeGJ2T5VbS4+ZXKnqRkFyyG3qhyCpx8bbAhSUnXkXQ Kfo1gyNYPp0tsULFe4Fxlf4f3/ybFLzs5LEAAAAASUVORK5CYII= --_004_1e30dd88b7a74a92aa21b0225fd414echuaweicom_-- From nobody Thu Aug 12 10:13:06 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B0193A4331 for ; Thu, 12 Aug 2021 10:13:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 VjomP8tXOE2H for ; Thu, 12 Aug 2021 10:13:00 -0700 (PDT) Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E63D73A432A for ; Thu, 12 Aug 2021 10:12:59 -0700 (PDT) Received: by mail-pj1-x1029.google.com with SMTP id j1so10766719pjv.3 for ; Thu, 12 Aug 2021 10:12:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=apq0oLT6me27nWNuoPHUjD61QG3l19/AXgu5k22CS1g=; b=W5Wjgz/YLcfehCfgbLLqXCjsW/NguniLPme1eVdorw2oru6UPB5HejSJJcIeUmxiep ZBQixOjAre+ThJFIkMJxXSj9RWTnZvg3x2/2XAO8Hua4Rxjd4ww95uj0sbX3OhrCQzaY 2o+zF39DCBVuUEcSfOZV0WJ2PW99ykptn5o41iutwYsS9NvkAR6GihoVAFOKH4GZZQaE AZzVIHcA8IFSz/Y4TnlFohSp8HfEFhljsUpywyxaMHHWy9ZbLMQOd8alSoguzE3RqRhq /E2TQmEp3ezLz//f7vLXa3uKMJOg2nW1zhfjkhclFWeQI7XMPdyN7m8KLAzJIL8skDfX gi2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=apq0oLT6me27nWNuoPHUjD61QG3l19/AXgu5k22CS1g=; b=EV/Xw3gwY4mq0uyUSk+BZ3RwnbMt0e0mx3ynxUGWZnv0+eSz+NC58ShKdsC9P+oPID /zU+ZySDwKSnRbFKhbRsF7vE3krRlCbKNG1/g9Wz7vdMx0JOvy0Rt/L2WJ7h1+YCZ9pP AfuEmeb0aCcWArpzQleoZR7quV0TcZxeZQD+eYcfpFRm7V8Cc/S3bwHDl7kiJUgIw15n ylss0b8jd6hbeXsOVV+FocDDG6Hgx43gi5Sw6TvRlWIXyRYsCkNiGAvHi3KmIJrNWBir Qt93Bti3RuSuS2++K8EVVHTfDc83BRL0IUowFwwua35cU+v6XLxc0xbz47plugYXn7db DVKg== X-Gm-Message-State: AOAM5337UGbZdokLHAS7Sh2YblRb+0O+OJG2/UG0W7byLNVYdMT341z5 cDOSI002tEIozEEMiM1N0tU= X-Google-Smtp-Source: ABdhPJw+flq1DMmk1Pd6aODXjkF83LFRPWVSObd2fM2xOBfH3GHJgo3Tz4G7RkQyIUAH+C0QcoI8ow== X-Received: by 2002:a63:475f:: with SMTP id w31mr4781392pgk.5.1628788377627; Thu, 12 Aug 2021 10:12:57 -0700 (PDT) Received: from smtpclient.apple ([98.42.171.73]) by smtp.gmail.com with ESMTPSA id k3sm4043137pfc.16.2021.08.12.10.12.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Aug 2021 10:12:57 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\)) From: Dino Farinacci In-Reply-To: <13e7e46d97c0401fb818bdf596964902@huawei.com> Date: Thu, 12 Aug 2021 10:12:55 -0700 Cc: "lisp@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: <22E36DB9-EFCD-4100-B4BB-1A64CA68EAA4@gmail.com> References: <13e7e46d97c0401fb818bdf596964902@huawei.com> To: Vasilenko Eduard X-Mailer: Apple Mail (2.3654.100.0.2.22) Archived-At: Subject: Re: [lisp] Comments on https://datatracker.ietf.org/doc/html/draft-ietf-lisp-mn-10 X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2021 17:13:05 -0000 > Hi Guru, > I have looked subject and have a few comments: Hi Eduard. > 1. The draft does mention a few times =E2=80=9Cwithout triangle = routing in the data path=E2=80=9D. > But section 7.4: =E2=80=9CAs a result, packets may be natively = forwarded to non-LISP sites by an ITR (the return path will through a = PITR, however, since the packet flow will be non-LISP site to LISP = site).=E2=80=9D Yes, it depends on PITR placement in the network. If PITRs are = distributed and placed in access networks, you avoid the suboptimal path = as well as distribute load for return packets. > Do I understand right that it is exactly =E2=80=9Ctriangle routing=E2=80= =9D? Encapsulation in both directions would be needed if you insist on = =E2=80=9Cwithout triangle routing=E2=80=9D or you could delete the = requirement. Since the non-LISP destination in the packet is NOT in the mapping = system, the ITR simply forwards the packet and assumes the underlay can = deliver it natively. Return packets from a non-LISP source to a LISP = destination must be encapsulated because the LISP destination EID IS NOT = typically in underlay routing. So the packet follows a default path or = anycasted to the closest PITR that can do the EID lookup in the mapping = system and encapsulate to the ETR of the LISP site. And the path from = the non-EID to EID may not take the shortest path to the ETR. Note when LISP-NAT is used as a interworking solution, packets are = always sent on the shortest path at the expense of path symmetry between = the EID and non-EID. > 2. All discussions are in the style that it is =E2=80=9Chandover=E2= =80=9D, not =E2=80=9Croaming=E2=80=9D. =E2=80=9CRoaming=E2=80=9D has = been mentioned 28 times in the draft but it is exactly what was *not* = implemented. To me "handover" means how you do the "roaming". "Roaming" in the = context of LISP means the EID binds to a new RLOC-set and therefore = roams around the underlay. > I mean: what if the next RLOC would be from a completely different = administrative domain? What if not just link would be switched but = Carrier would be switched? It doesn't matter, encapsulators that have the EID in their map-cache = update the RLOC-set and start sending to the new RLOC. LISP really = doesn't care how the underlay delivers packets but it can tell when the = underlay telemetry changes and can switch RLOCs from an RLOC-set without = any coordination with other nodes. > IMHO: =E2=80=9Croaming=E2=80=9D is a mandatory case for the word = =E2=80=9CMobile=E2=80=9D in the title of the draft. Well in LISP, an entire /16 of EIDs in a data center rack can move at = one time. That is mobility but not of a mobile phone which most people = assume it to be. > Please, at least rename =E2=80=9Croaming=E2=80=9D to =E2=80=9Chandover=E2= =80=9D till roaming would be proposed. It is better to be accurate with = Mobile terminology. Handover in LISP would be how short TTLs are used to update RLOC-sets, = SMRs are used to update RLOC-sets, and how PubSub is used to update = RLOC-sets. And "fast handover" is the convergence time that is better = than the term "slower handover" (or "handoff"). > 3. It has been mentioned that there is a requirement for = =E2=80=9Cmulti-homing=E2=80=9D, but it has not been discussed at all = later. > IMHO: an additional section is needed to explain how =E2=80=9CTCP = connections to stay alive while roaming=E2=80=9D =E2=80=93 probably = =E2=80=9Cmulti-homing=E2=80=9D should help with this.=20 I have said it throughout this email by referring to "RLOC-set". Which = means there is more than one RLOC that can reach the EID registered to = the mapping system. Dino From nobody Thu Aug 12 10:20:50 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 048AC3A4384 for ; Thu, 12 Aug 2021 10:20:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 WoSi42eCHPsj for ; Thu, 12 Aug 2021 10:20:43 -0700 (PDT) Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 123F53A4382 for ; Thu, 12 Aug 2021 10:20:43 -0700 (PDT) Received: by mail-pl1-x629.google.com with SMTP id a5so8162150plh.5 for ; Thu, 12 Aug 2021 10:20:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=k4bAc2MhfozTIThcVGfMtrSd32tvx1AHsfr7vuB3AVo=; b=nwqieoYClOtJ1VLE8TGkH9+l5reRf5+dxPPHFzwYFwJMd/laQ499X/F2/3thUiYGdj eCkNqx/JYEFALJB1lY3dP4jhg0rar4u6pJhzN5CWrTZP2kq8Se+zoserK9+zj/SIFtPk ult9pIyOdTzqblN33unPhSwEjvRySp3gvYOu3Qi19rHyuuHDCHO/ycxGAfJWdfnsyDqO VaxzXQKTi9JLj1vLIX24W6QP5MHzPIrO4ABCR2uMSd/2dXyFuH2vJ/Q6IvtH5urdXaEC 5R2etGzygENtd3mQKrjYQHWhEFVtcrXXW8bY6LyU+ssM99C18JdvScdfdWDbgfwEbGQd jcQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=k4bAc2MhfozTIThcVGfMtrSd32tvx1AHsfr7vuB3AVo=; b=ZGa/ml1KiW4+FZp3f0PqNU0EcYh1lXbAn3yaOvU2SY9/OPf68CPOGgGXtaKz32Pss5 +I37I/lMKO4Dy2WrJ4soPeaaj+/qHTQhL8+uG5epEDd7a+lx+9mnum/BLhJUHBPrZEDt vC58WCJZ3H1KbZFYAFUnotrxnwf/Cql0FIb9oGaQkL0c2V/xuMPaVoCyuj7lfPzOZhO+ 3k0NlPmTvpbrklv27R5BC8Qjeg9XLhGc3DP7txlmiIB5yHgVvTiH9/qkIlIaCCBKtZET nvlhkZvb1gCoWf+Pp11bBEt2SvpL/VYjlT4mpZstFiVCtlR1rdsyxYYviieoz8nAkpc+ 7e4g== X-Gm-Message-State: AOAM531stCBUP4OibP7poNPwc+hHWCZR4nUGmVtuMu04rg4YphoTAeJs QaqQFesgxJS5hIIOoguKkpY= X-Google-Smtp-Source: ABdhPJw+sMinaEzwaeg0y3Fmb6/qcxgiUkxhha/Uukjyj4THdjGMCcfZ1OMLhtX7ZdWwbGCe2lHylw== X-Received: by 2002:a17:902:b60a:b029:12c:f89b:fad3 with SMTP id b10-20020a170902b60ab029012cf89bfad3mr4415194pls.13.1628788841694; Thu, 12 Aug 2021 10:20:41 -0700 (PDT) Received: from smtpclient.apple ([98.42.171.73]) by smtp.gmail.com with ESMTPSA id l11sm4269113pfd.187.2021.08.12.10.20.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Aug 2021 10:20:41 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\)) From: Dino Farinacci In-Reply-To: <1e30dd88b7a74a92aa21b0225fd414ec@huawei.com> Date: Thu, 12 Aug 2021 10:20:40 -0700 Cc: "lisp@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: <604E5254-20BD-4651-BC7E-711B0397B0EE@gmail.com> References: <1e30dd88b7a74a92aa21b0225fd414ec@huawei.com> To: Vasilenko Eduard X-Mailer: Apple Mail (2.3654.100.0.2.22) Archived-At: Subject: Re: [lisp] Comments on https://datatracker.ietf.org/doc/html/draft-ietf-lisp-mn-10 X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2021 17:20:48 -0000 > One additional comment: > 4. I have seen assumptions that Map server and proxy to Non-LISP are = on the same box. It is a potential bottleneck in the future. That is a deployment decision and not an architectural requirement. > DHCP would deliver only 1 Map Server IP to RLOC. Hence all overlays = would share the same Map Server. Not true. The map-server(s) are configured in ETRs. They can be distinct = addresses or anycast addresses. > Proxy is a router with a low capacity CPU. It could become a = bottleneck if LISP implementation would become big enough. The PxTR needs to be built (by equipment vendors) like any other type of = router and the capacity depends where it is deployed and the speed of = links and aggregation of traffic comes to it. Clustering solutions make = PxTRs scale. > It is better to assume initially the general case that Map Server and = Proxy are different boxes (not collocated). Yes, it is assumed by default and co-locating it is a deployment = decision. Dino From nobody Thu Aug 12 14:49:30 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 041AE3A0736 for ; Thu, 12 Aug 2021 14:49:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com 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 wNsO-I4g56JF for ; Thu, 12 Aug 2021 14:49:23 -0700 (PDT) Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 EF5F53A0656 for ; Thu, 12 Aug 2021 14:49:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4Gm0hM2FSMz1ntVG for ; Thu, 12 Aug 2021 14:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1628804963; bh=unxCPeBy760Cl0xDiBezmxNqRzwcEnTjhwzlEo90vts=; h=To:From:Subject:Date:From; b=UhwFxymgHiB3EPpIPThB3enqViwMqXHKT9mUddyMSXxn78bomkdEYxwkLrSe1AwHF Zw67S63uK5n1ZyKQmnmiMDuQYRwHeHQ1lPMSlRJeMoe+R314Fq2s1wnWxnNWeca6n/ zxyhufUnj4wKVxTqGa4EUnoiFnXQ3aUqhhjwt6dI= X-Quarantine-ID: X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net Received: from [192.168.23.64] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4Gm0hL6Dgkz1ntRG for ; Thu, 12 Aug 2021 14:49:22 -0700 (PDT) To: "lisp@ietf.org" From: "Joel M. Halpern" Message-ID: Date: Thu, 12 Aug 2021 17:49:21 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [lisp] Upcoming meeting X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2021 21:49:29 -0000 Your chairs have until September 24th to request a slot at the next meeting. Participants indicated a desire for a 2 hour slot. Before requesting that, I at least (I have not asked Luigi) want evidence tha there will be actual discussion. Burning two hours for presentations that do not lead to discussion is a waste of scarce meeting time. The best evidence I know of is actual discussion on list, leading to identified open issues to be discussed. Yours, Joel From nobody Thu Aug 12 15:00:02 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21AA03A07CC for ; Thu, 12 Aug 2021 15:00:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 fdJYTjl9fQwA for ; Thu, 12 Aug 2021 14:59:56 -0700 (PDT) Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42DD13A07CB for ; Thu, 12 Aug 2021 14:59:56 -0700 (PDT) Received: by mail-pj1-x1032.google.com with SMTP id u13-20020a17090abb0db0290177e1d9b3f7so17576924pjr.1 for ; Thu, 12 Aug 2021 14:59:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=epNp4kwVURcbjaG4/Hle3s2hD9DSiiwB1WigMjyQHSU=; b=YGzg8KcW+qu1SM6T7MDPZ2e53c21cV2lFb9iNP/v6RKSUemFjOYnwQ6k/c7NTOqNGF dIiOQKAKIJev9Qznu7Ab+nA0HXM87xWiQozZz5CV2S0cR5HI3l1d+M+cLs0XmaIuioeG sQLMwKGjw1hPr9K5X1OsxX/EVj9ZZbNX/mRzMgiA1O7Ar+y7PhZv+vUVb+XNS5NMie1k 5OvbJiQscO9hB2NomWPk9QHDBujOAzUWNLOOjth33nh0PYWsjNwzes7Pbq6PsNSu9BuK PEt6wB3y/kOyemuKJ8gq/Ttk7HaFhGmZbaMsZ7XvZHINKa+2TfIN0ma/rSSMXxuQHHCu JKug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=epNp4kwVURcbjaG4/Hle3s2hD9DSiiwB1WigMjyQHSU=; b=YHVuUH6/bXjTWPD0t5HySIzyzywfmfC9EUy0tkQPruA9LdMkbXEIrMqwk7XlNB/+7Y f7f9yRRLSf6VKx/H3VdKgbpTJdv6ntA7uZnrqx92M73w6MAvn+Tf+lElahRNkQidPgmB +XCjwohO+y0MoJn003iPlgvunpgV2aaQB+D3HMyhbi/1Oq/OyEGW6KyOASkWQ88sjczA CvRgOTCUnwxzgCWRu7qDzgMUAYzbf5+Y5HcGcoqU926vwbbn7NQpuT9VPVi9Dk/mUvMM HTSjCFeJaEyKRcnL7O5KedJR1aZHfVQPF0ixd3BBYkwVIU8wDUHIG1GUO29Yed10wL3u dpPQ== X-Gm-Message-State: AOAM532LiDVkTR2JO6DTNcq6zoSA0U7oSF2QnCrrRvNlCv51mOfQr8Uh 9/Rzp/3HtQ7bDhMo8B814BKoBCeXWJA= X-Google-Smtp-Source: ABdhPJxKO52NSd9jyGIq8a4gBbqnAWdlKVKiqfxGDwviZEL/UhSzWFtSgspIGQvGltNim5sLa+4QjQ== X-Received: by 2002:a17:902:db07:b029:12c:bdf3:73a3 with SMTP id m7-20020a170902db07b029012cbdf373a3mr5134291plx.5.1628805594574; Thu, 12 Aug 2021 14:59:54 -0700 (PDT) Received: from smtpclient.apple ([96.72.181.209]) by smtp.gmail.com with ESMTPSA id 66sm4691518pfu.67.2021.08.12.14.59.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Aug 2021 14:59:53 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\)) From: Dino Farinacci In-Reply-To: Date: Thu, 12 Aug 2021 14:59:47 -0700 Cc: "lisp@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: <3A543C97-C7D0-463D-8B7A-4BB7BF875BF9@gmail.com> References: To: "Joel M. Halpern" X-Mailer: Apple Mail (2.3654.100.0.2.22) Archived-At: Subject: Re: [lisp] Upcoming meeting X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2021 22:00:01 -0000 Let's collectively make a list of topics that we can have a = 1/2-hour-to-1-hour slot to discuss. I am sure many people want to talk = about various topics. And from that discussion, we can create action = items. And I think we should open the list creation to other WGs that may look = at LISP to help solve some of their problems. And even if the topics are = tutorial in nature, that will foster discussion IMO. Dino > On Aug 12, 2021, at 2:49 PM, Joel M. Halpern = wrote: >=20 > Your chairs have until September 24th to request a slot at the next = meeting. Participants indicated a desire for a 2 hour slot. Before = requesting that, I at least (I have not asked Luigi) want evidence tha = there will be actual discussion. Burning two hours for presentations = that do not lead to discussion is a waste of scarce meeting time. >=20 > The best evidence I know of is actual discussion on list, leading to = identified open issues to be discussed. >=20 > Yours, > Joel >=20 > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp From nobody Tue Aug 24 02:32:21 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0869F3A1B55 for ; Tue, 24 Aug 2021 02:32:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20150623.gappssmtp.com 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 xziGENCaw4d2 for ; Tue, 24 Aug 2021 02:32:13 -0700 (PDT) Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51EBB3A1B54 for ; Tue, 24 Aug 2021 02:32:13 -0700 (PDT) Received: by mail-wm1-x334.google.com with SMTP id g135so3052176wme.5 for ; Tue, 24 Aug 2021 02:32:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=F4qG5GtPXffKMaBJnffsl/RJds4z+RgoGkonEEjTZtc=; b=jdnFi5U2OxerbDwC0fQmTgKCoIsuHtX2/aJiRYD+n/ab2OUHyea2zAaeZ57mz0e54S CzbtklSVy7EcZCf7FocaBpo62LlQq/gxUwG7eEMjaw1S2iNtuM+2i7QE7pD7uN7nYSLm rC2F+QY40BSLD2Q5xqvTUNUf3BWMo47QU9M/HBkju0sqFuc5cSAY+6ol/Y/mDn90KcbQ CYvQNn3nnzTSIPmkl1EcuijjbU/s8Vr8EeMjOe3DwMxQMJbVszyfbhzAHQ1H1ec8dB4H XR5NDkuE3VPsqh/DvMNB6+aSinRaOvwInVGB/OdLnd4vkE+w9s1YPUGvxLRmfjFjoWl6 vPrw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=F4qG5GtPXffKMaBJnffsl/RJds4z+RgoGkonEEjTZtc=; b=QLUd5kvnRb+hheO7NIBrGFofAI6H+vSLfc1mCyiAp70bdPeNb44jq0jgF1kKwkOdCA 4r+aBm1Cef8RbVo+SC7SpsbGlGOQkqzyFnMYBS3ArGAt+nA2nB6552Rid2f52gCjXFbp rEXfdZzfW5/4UB+avpLZ/ixuPIQCUDOGc0VNZoUiTh8g6LNh7yEtUO5Aw+hIB3L01MCN qXOGqo3iHTasJF+/mPtKTtd/QxmtKnMSJBfWNpuoRRU07qbPykF3BxoQsCVDWQ5yzuBM jKzVZaIFrfFlRNbyZg0M6xONR6CUFiYTNIqFw9rhOSd4O1lVxXvVSdrNJtW7dFGwz8kF dFvg== X-Gm-Message-State: AOAM532FgNP6a3V6mFV2bCxuBZJX1eZDptN3/xFJKkGc02Zv+oGtWxsL 11RAe5Fdj/n37XE51466wg6T/w== X-Google-Smtp-Source: ABdhPJxxp62kqyXNSC5Wg5ymVUOV0TJ4DfaW44cGqfJ3jjDG1+dgb8Pihkf+WIloDfYS0p+NnabI0A== X-Received: by 2002:a05:600c:230c:: with SMTP id 12mr3146153wmo.41.1629797530223; Tue, 24 Aug 2021 02:32:10 -0700 (PDT) Received: from smtpclient.apple ([2a01:e0a:1ec:470:a0eb:9a96:1e66:507a]) by smtp.gmail.com with ESMTPSA id o7sm1693308wmc.46.2021.08.24.02.32.08 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Aug 2021 02:32:09 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) From: Luigi Iannone In-Reply-To: <3A543C97-C7D0-463D-8B7A-4BB7BF875BF9@gmail.com> Date: Tue, 24 Aug 2021 11:32:08 +0200 Cc: "Joel M. Halpern" , "lisp@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <3A543C97-C7D0-463D-8B7A-4BB7BF875BF9@gmail.com> To: Dino Farinacci X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: Re: [lisp] Upcoming meeting X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Aug 2021 09:32:19 -0000 Hi, that is not a bad idea. So let=E2=80=99s start: What are the topics people want to talk about = during the next meeting?=20 Ciao L. > On 12 Aug 2021, at 23:59, Dino Farinacci wrote: >=20 > Let's collectively make a list of topics that we can have a = 1/2-hour-to-1-hour slot to discuss. I am sure many people want to talk = about various topics. And from that discussion, we can create action = items. >=20 > And I think we should open the list creation to other WGs that may = look at LISP to help solve some of their problems. And even if the = topics are tutorial in nature, that will foster discussion IMO. >=20 > Dino >=20 >> On Aug 12, 2021, at 2:49 PM, Joel M. Halpern = wrote: >>=20 >> Your chairs have until September 24th to request a slot at the next = meeting. Participants indicated a desire for a 2 hour slot. Before = requesting that, I at least (I have not asked Luigi) want evidence tha = there will be actual discussion. Burning two hours for presentations = that do not lead to discussion is a waste of scarce meeting time. >>=20 >> The best evidence I know of is actual discussion on list, leading to = identified open issues to be discussed. >>=20 >> Yours, >> Joel >>=20 >> _______________________________________________ >> lisp mailing list >> lisp@ietf.org >> https://www.ietf.org/mailman/listinfo/lisp >=20 > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp From nobody Tue Aug 24 12:09:04 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27AC63A0CCE for ; Tue, 24 Aug 2021 12:09:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 8-X3nKC2Jk6X for ; Tue, 24 Aug 2021 12:08:54 -0700 (PDT) Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CFF43A0CCB for ; Tue, 24 Aug 2021 12:08:54 -0700 (PDT) Received: by mail-pg1-x533.google.com with SMTP id r2so20698784pgl.10 for ; Tue, 24 Aug 2021 12:08:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=iSVbxTqiQVLY1q6GESyP+jkeOtIxV7yAU4yi8KcTeV8=; b=AkJl6UPqfTXcdAQBzJ4clwf4w7enCX/pikZlbMHx+r07su4nQlYMa/uUBM/yaJhJ4w dpELF2l+U6Fyq3Wc0db/fzUDyvv+IRtFw/Au9h+P81VHbjClMOa9Dwru9h7Qb/ZAeM1A Q1Tm+r3+8DUrMsp2+RVPC7tpU8W07RwvMbLmB6NV635lOZonf1Cw0Ta+REn7T1JLCGYU S5gNoQV4bx71EghQXF43pLiZIlV8BOqaTGX8pUzYvpWTz7nexLFpezjpTeFdHfc+KNqy q/Bkl49BueT8CdgDLf/8KyQLWMDKte1f1GI2WR+zifpjqK65VwNKGywZZSx3EhxwnrY8 RJzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=iSVbxTqiQVLY1q6GESyP+jkeOtIxV7yAU4yi8KcTeV8=; b=Wx+9ufeBurDsinnLurB8IRBzd7d+8Yt/I0ors4viVyJBH/VxlYa/uxFZPp50AABH1N n56Fu4qdWfkKG9YbmPEyFmKhVcr6SHJ9w8KaZ9bbHbp8H53Yp1VV5VxqsfC1sf1lzdWm hpsXF0Ox5doflg8uvSfw7uOjI2Ht+E/6850+5TpwRSJTXGKVRefRLie2z35AoIQVvSLJ NDFzI7AJlvmAYMxJsAA8IC3dp4tuVs07xwExQ+nzU0D6yCIK1CITd6hrU5olNq6unuGu UpiLIFUkQvxH5unmFQ5yLxIVPeY9YzNXmoOV3WK1n01njN0senyWKsN0sAT0x28naNjp K1pA== X-Gm-Message-State: AOAM532AuPxzQFgm/G5RFPSD6N92LaeKeQqzbqCC+BLxBHHzEbrrNoNv 0IvHF42/hzhJJqUIcSPYhC3dZeUWoArNVA== X-Google-Smtp-Source: ABdhPJwCPjRM0h4fn+t6K0iI3hX+0u9GKwBQct2UbsaSInw0YT6FkhEQNL6SEE9MkaX+mmcpIxY8oQ== X-Received: by 2002:a63:411:: with SMTP id 17mr29173610pge.335.1629832133041; Tue, 24 Aug 2021 12:08:53 -0700 (PDT) Received: from smtpclient.apple ([98.42.171.73]) by smtp.gmail.com with ESMTPSA id v3sm2788219pjd.27.2021.08.24.12.08.51 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Aug 2021 12:08:52 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\)) From: Dino Farinacci In-Reply-To: Date: Tue, 24 Aug 2021 12:08:48 -0700 Cc: "Joel M. Halpern" , "lisp@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <3A543C97-C7D0-463D-8B7A-4BB7BF875BF9@gmail.com> To: Luigi Iannone X-Mailer: Apple Mail (2.3654.100.0.2.22) Archived-At: Subject: Re: [lisp] Upcoming meeting X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Aug 2021 19:09:01 -0000 I can give 4 (or less) use-case presentations at any length you see fit. = Maybe the group can decide how indepth for each one and that can dictate = the time slot. Here are the 3 use-cases: (1) How LISP is used to build a blockchain network (2) How LISP is used for contact tracing (3) How LISP was used at the PyeongChang Olympics to move data around = without touching the underlay (4) How LISP was used at the Tokyo Olympics to monitor underlay = telemetry for both unicast and multicast flows But I would like to hear from others. I think we should copy the rtgwg, = dmm, coinrg, and dinrg. But I'll wait for others to comment before doing = so. WG, whatdayathink? Dino=20 > On Aug 24, 2021, at 2:32 AM, Luigi Iannone wrote: >=20 > Hi, >=20 > that is not a bad idea. >=20 > So let=E2=80=99s start: What are the topics people want to talk about = during the next meeting?=20 >=20 > Ciao >=20 > L. >=20 >=20 >> On 12 Aug 2021, at 23:59, Dino Farinacci wrote: >>=20 >> Let's collectively make a list of topics that we can have a = 1/2-hour-to-1-hour slot to discuss. I am sure many people want to talk = about various topics. And from that discussion, we can create action = items. >>=20 >> And I think we should open the list creation to other WGs that may = look at LISP to help solve some of their problems. And even if the = topics are tutorial in nature, that will foster discussion IMO. >>=20 >> Dino >>=20 >>> On Aug 12, 2021, at 2:49 PM, Joel M. Halpern = wrote: >>>=20 >>> Your chairs have until September 24th to request a slot at the next = meeting. Participants indicated a desire for a 2 hour slot. Before = requesting that, I at least (I have not asked Luigi) want evidence tha = there will be actual discussion. Burning two hours for presentations = that do not lead to discussion is a waste of scarce meeting time. >>>=20 >>> The best evidence I know of is actual discussion on list, leading to = identified open issues to be discussed. >>>=20 >>> Yours, >>> Joel >>>=20 >>> _______________________________________________ >>> lisp mailing list >>> lisp@ietf.org >>> https://www.ietf.org/mailman/listinfo/lisp >>=20 >> _______________________________________________ >> lisp mailing list >> lisp@ietf.org >> https://www.ietf.org/mailman/listinfo/lisp >=20 From nobody Tue Aug 24 12:17:24 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B8A83A0D69 for ; Tue, 24 Aug 2021 12:17:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com 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 gVmOqtE0Chxi for ; Tue, 24 Aug 2021 12:17:16 -0700 (PDT) Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 901FF3A0D60 for ; Tue, 24 Aug 2021 12:17:16 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4GvJlH6kYsz1ntrZ; Tue, 24 Aug 2021 12:17:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1629832635; bh=okg9/VUw+2jhBnUBPRI3D6FVp3qyOeU69hn5HEUhQMM=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=VCT+JnNly9wiqoeCMX+6QkGQxo1cSGCKmGiyzRrlnQ54Id49RH/S8z+8591KMPZ+R d4B8UiL/6twhph3UpIKdrGqUeSsjQsA+UXMGTSqwYqe7So7tapZ4TcnDnRxsQUR+x7 dJiFgbUqdWlFd0UhIDLZmFORpJvu75PycbCpVSVM= X-Quarantine-ID: X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net Received: from [192.168.23.64] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4GvJlH2DB0z1ntkJ; Tue, 24 Aug 2021 12:17:15 -0700 (PDT) To: Dino Farinacci , Luigi Iannone Cc: "lisp@ietf.org" References: <3A543C97-C7D0-463D-8B7A-4BB7BF875BF9@gmail.com>

From: "Joel M. Halpern" Message-ID: Date: Tue, 24 Aug 2021 15:17:13 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [lisp] Upcoming meeting X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Aug 2021 19:17:22 -0000 It wounds like we are going for very different goals. Those are all very impressive uses (except I don't care about blockchains...) But from my perspective, what I am looking for is presentations that will cause discussion in the meeting, leading to benefit for the working group. This is not a conference for talking aobut the impressive things we have accomplished (even if I grant they are impressive and useful.) So the question really for the working group is "what things do you think it is worth discussing. Not listening to. Discussing. Yours, Joel On 8/24/2021 3:08 PM, Dino Farinacci wrote: > I can give 4 (or less) use-case presentations at any length you see fit. Maybe the group can decide how indepth for each one and that can dictate the time slot. Here are the 3 use-cases: > > (1) How LISP is used to build a blockchain network > (2) How LISP is used for contact tracing > (3) How LISP was used at the PyeongChang Olympics to move data around without touching the underlay > (4) How LISP was used at the Tokyo Olympics to monitor underlay telemetry for both unicast and multicast flows > > But I would like to hear from others. I think we should copy the rtgwg, dmm, coinrg, and dinrg. But I'll wait for others to comment before doing so. > > WG, whatdayathink? > > Dino > >> On Aug 24, 2021, at 2:32 AM, Luigi Iannone wrote: >> >> Hi, >> >> that is not a bad idea. >> >> So let’s start: What are the topics people want to talk about during the next meeting? >> >> Ciao >> >> L. >> >> >>> On 12 Aug 2021, at 23:59, Dino Farinacci wrote: >>> >>> Let's collectively make a list of topics that we can have a 1/2-hour-to-1-hour slot to discuss. I am sure many people want to talk about various topics. And from that discussion, we can create action items. >>> >>> And I think we should open the list creation to other WGs that may look at LISP to help solve some of their problems. And even if the topics are tutorial in nature, that will foster discussion IMO. >>> >>> Dino >>> >>>> On Aug 12, 2021, at 2:49 PM, Joel M. Halpern wrote: >>>> >>>> Your chairs have until September 24th to request a slot at the next meeting. Participants indicated a desire for a 2 hour slot. Before requesting that, I at least (I have not asked Luigi) want evidence tha there will be actual discussion. Burning two hours for presentations that do not lead to discussion is a waste of scarce meeting time. >>>> >>>> The best evidence I know of is actual discussion on list, leading to identified open issues to be discussed. >>>> >>>> Yours, >>>> Joel >>>> >>>> _______________________________________________ >>>> lisp mailing list >>>> lisp@ietf.org >>>> https://www.ietf.org/mailman/listinfo/lisp >>> >>> _______________________________________________ >>> lisp mailing list >>> lisp@ietf.org >>> https://www.ietf.org/mailman/listinfo/lisp >> > From nobody Tue Aug 24 14:28:20 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 053CD3A140A for ; Tue, 24 Aug 2021 14:28:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 lKhgMF4kLaxW for ; Tue, 24 Aug 2021 14:28:14 -0700 (PDT) Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D91913A1407 for ; Tue, 24 Aug 2021 14:28:14 -0700 (PDT) Received: by mail-pf1-x42b.google.com with SMTP id y190so19526967pfg.7 for ; Tue, 24 Aug 2021 14:28:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mPCtrZ2T/bMoU+zf8U9zX3K3B/A1By1/6P/b2hDVRSE=; b=hSfPGqXLAolfsJkwVX8eJodW5sMJykONBxFa+PUIzgRgU/FEypGUdCruy9U5gGRMOH 6NW/G9eG5J24H3jsUpeKGskWVARge6kqBI66dLZICjMF8dPJm0ZuTf182wbqa/Y9G28E SeRU5y3+PFyHRRQ9xvAD4+ubSgc33TSZZ8FHpYdcPLUyRMMRDz4GFtxxRBlgWOc5TjNl 6H52yR+8hzQ8qCAcKA3k7p8Ss0EqqQJ1RHT00MstGr/ntRXlboU80ZSKJZjValOAB2CJ f5UB7j1mbgDpm096/cltMs/VW6Kq8oS6rlwbRTAr1Hfs4cFPlgWhBozCnMKQZvGG117a BqAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mPCtrZ2T/bMoU+zf8U9zX3K3B/A1By1/6P/b2hDVRSE=; b=Z5tTuO24G1yWAc4neL+brlnDkEgaNUet5I5RmRf/poF6UrMlIhYVZyMkOMYN9FQIha hL9z+xKlVoWC2PA7d5KX4D6fE/w+/M9Ji8atq4MBnD3b85bZfH9isivYJHdYY4R4noeN x7unZnyZ4b3SqSoQk14dmcp2AU8ajFHob+mQQ+gOX6/TzLm+KdQvfb1/42uvb2wlBiAY aRj3DpqUQQ/HV6Aepdo5Gt1fQogRErxJZwgYfNYNN8OI1sHdENQiG+xh1d4kP/63RRbq FlCz+ZYqsX6x0x2dZ/GskkYahaKAav+F+vPbUmkpxlIcJjN2m8j3ArcwdJ0bh+CGYevF tBEA== X-Gm-Message-State: AOAM532Rut5XhDWcPZB3uKjMzkl+ejainfzMytnVeCL6AgXdaov2sOzL cxuCpnYMmvNT856sQ82q8O0= X-Google-Smtp-Source: ABdhPJzNpO2sy4cl1Jv5ZfLjxRwn+BcDgxn0uT5uuXt9nl6ZXc7KMiuwM+T9tDUYij1qA/YIn+h0Fw== X-Received: by 2002:a65:434c:: with SMTP id k12mr38724440pgq.17.1629840492778; Tue, 24 Aug 2021 14:28:12 -0700 (PDT) Received: from smtpclient.apple ([2601:640:105:988f:e492:c99e:89a7:c053]) by smtp.gmail.com with ESMTPSA id v15sm20001992pff.105.2021.08.24.14.28.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Aug 2021 14:28:12 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\)) From: Dino Farinacci In-Reply-To: Date: Tue, 24 Aug 2021 14:28:11 -0700 Cc: Luigi Iannone , "lisp@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <3A543C97-C7D0-463D-8B7A-4BB7BF875BF9@gmail.com>

To: "Joel M. Halpern" X-Mailer: Apple Mail (2.3654.100.0.2.22) Archived-At: Subject: Re: [lisp] Upcoming meeting X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Aug 2021 21:28:19 -0000 > So the question really for the working group is "what things do you = think it is worth discussing. Not listening to. Discussing. The intent of these presentations is to spur discussion. And, as I said, = can be as short as 5 minutes to bootstrap discussions. The time = allocated would be for discussion and not for presentation. Dino From nobody Tue Aug 24 16:17:39 2021 Return-Path: X-Original-To: lisp@ietf.org Delivered-To: lisp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 721563A1873; Tue, 24 Aug 2021 16:17:10 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: lisp@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.36.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: lisp@ietf.org Message-ID: <162984703037.23216.1912782356576371778@ietfa.amsl.com> Date: Tue, 24 Aug 2021 16:17:10 -0700 Archived-At: Subject: [lisp] I-D Action: draft-ietf-lisp-yang-16.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Aug 2021 23:17:11 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Locator/ID Separation Protocol WG of the IETF. Title : LISP YANG Model Authors : Vina Ermagan Alberto Rodriguez-Natal Florin Coras Carl Moberg Reshad Rahman Albert Cabellos-Aparicio Fabio Maino Filename : draft-ietf-lisp-yang-16.txt Pages : 83 Date : 2021-08-24 Abstract: This document describes a YANG data model to use with the Locator/ID Separation Protocol (LISP). The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-yang/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-lisp-yang-16 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-yang-16 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Aug 24 20:49:34 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6E503A237C for ; Tue, 24 Aug 2021 20:49:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.596 X-Spam-Level: X-Spam-Status: No, score=-9.596 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=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=YKuceLRq; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ejvwY9o5 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 dqCXVQDML4_7 for ; Tue, 24 Aug 2021 20:49:26 -0700 (PDT) Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47EA13A237A for ; Tue, 24 Aug 2021 20:49:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1118; q=dns/txt; s=iport; t=1629863366; x=1631072966; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=s5j5cjtuklKW34M++bqMfpoEIhUBgUnnp8qHMAlnHP8=; b=YKuceLRqFTE41yHBrz29YfCS9IBMhqiVH/3VLsp1Kdi1UUgQr7MFllds 86Q/y7GY6ndYeTXyD8z5ZG1pB/lS4NRuhPzakAjYpOR45ecPUz0WspLPW m69+2S8yphCM0JQpfE3suPENpzQ4CEQ0XCjdo/YnvVNM7UX3xp1edSb/d M=; IronPort-PHdr: =?us-ascii?q?A9a23=3AzvzTrBbPWr/Nj2qNcvHaS2H/LTDHhN3EVzX9o?= =?us-ascii?q?rIljL9Kcq2n55n4OgrU4vA+xFPKXICO7fVChqKWtq37QmUP7N6Ht2xKa51DU?= =?us-ascii?q?RIJyKB01wwtCcKIEwv3efjtaSFpHsNPUF9s+2m2K04TE8H7NBXep3So5msUH?= =?us-ascii?q?RPyfQN+OuXyHNvUiMK6n+C/8pHeeUNGnj24NLhzNx6x6w7Ws5p+vA=3D=3D?= IronPort-HdrOrdr: =?us-ascii?q?A9a23=3AHgqEeqHRA8IxIuYgpLqFsJLXdLJyesId70?= =?us-ascii?q?hD6qkvc31om52j+fxGws516fatskdvZJkh8erwX5VoMkmsi6KdhrNhfYtKPT?= =?us-ascii?q?OW+VdASbsD0WKM+UyaJ8STzJ856U4kSdkDNDSSNyk4sS+Z2njDLz9I+rDum8?= =?us-ascii?q?rE6Za8vhVQpENRGtxdBmxCe2Cm+zhNNXF77O0CZeOhD6R81l6dUEVSSv7+Km?= =?us-ascii?q?gOXuDFqdGOvonhewQ6Cxku7xTLpS+06ZbheiLonCs2Yndq+/MP4GLFmwv26u?= =?us-ascii?q?GIqPeg0CLR0GfV8tB/hMbh8N1eH8aB4/JlbwkEyzzYILiJaYfy+gzdk9vfsW?= =?us-ascii?q?rCV+O8+yvICv4DrE85uFvF+icFlTOQigrGoEWSuGNwyUGT0fARAghKVvaoQe?= =?us-ascii?q?liA0TkA41KhqAh7EsD5RPri7NHSRzHhyjz/N7OSlVjkVe1u2MrlaoJg2VYSp?= =?us-ascii?q?Z2Us4dkWUzxjIfLH47JlOx1GnnKpgYMOjMoPJNNV+KZXHQuWdihNSqQ3QoBx?= =?us-ascii?q?+DBkwPoNac3TRalG1wixJw/r1Rol4QsJYmD5VU7eXNNapl0LlIU88NdKp4QO?= =?us-ascii?q?MMW9G+BGDBSQ/FdGiSPVPkHqcaPG+lke+63JwloOWxPJAYxpo7n5rMFFteqG?= =?us-ascii?q?4pYkrrTdaD2ZVamyq9CFlVnQ6dg/22wqIJ9IEUaICbRBFreWpe5fdI+c9vcP?= =?us-ascii?q?Ezc8zDTK5rPw=3D=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CIAAD7vCVh/4MNJK1aHQEBAQEJARI?= =?us-ascii?q?BBQUBQIFFCAELAYFSUQd3WjcxhEeDSAOEWWCICIpej2eBLoElA1QLAQEBDQE?= =?us-ascii?q?BKgsMBAEBhGoCF4IUAiU0CQ4BAgQBAQESAQEFAQEBAgEGBIERE4VoDYZCAQE?= =?us-ascii?q?BAQIBAQEQEREMAQEsCwEECwIBCBgCAhkNAgICHwYLFRACBA4FIoJPAYJVAw4?= =?us-ascii?q?hAQ6dcAGBOgKKH3qBMYEBggcBAQYEBIJRgjkNC4I0AwaBECoBgn2CboEihmg?= =?us-ascii?q?nHIFJRIE8HIJmPoIgQgEBhHc2gi6HT1sLC1EcJpVzp2BegzSYc4VmBSehTIU?= =?us-ascii?q?spg2VKQIEAgQFAg4BAQaBYTuBWXAVOyoBgj5QGQ+OIAwWg1CFFIVKdDgCBgE?= =?us-ascii?q?KAQEDCY9jAQE?= X-IronPort-AV: E=Sophos;i="5.84,349,1620691200"; d="scan'208";a="927912412" Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Aug 2021 03:49:24 +0000 Received: from mail.cisco.com (xbe-aln-007.cisco.com [173.36.7.22]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 17P3nO5m001885 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Wed, 25 Aug 2021 03:49:24 GMT Received: from xfe-aln-001.cisco.com (173.37.135.121) by xbe-aln-007.cisco.com (173.36.7.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Tue, 24 Aug 2021 22:49:24 -0500 Received: from xfe-rcd-001.cisco.com (173.37.227.249) by xfe-aln-001.cisco.com (173.37.135.121) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Tue, 24 Aug 2021 22:49:24 -0500 Received: from NAM12-MW2-obe.outbound.protection.outlook.com (72.163.14.9) by xfe-rcd-001.cisco.com (173.37.227.249) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15 via Frontend Transport; Tue, 24 Aug 2021 22:49:24 -0500 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=BA7yh7qIKlZT+BA1kq+EqWsW2nf9n2CQVJYNomkVzUVrM8pgtZ2lWwtYuboaMxhUqVDEOq+8LZVkfLKi2hcM/C49v0LVcFMJobeXrY1NL5yNwRBrIFiAGJ+yO6AuwFhB2b18PKEGX8VskLkqgz7319AjKcuGjnJ6pvwtRYhWsRG5/V9nMfpGNnYgiz0AO0otnWNcHen0xKWZ27h3rme2LlqiO54QSFVcv9KZACjox+9WjAXrk+bd2rdmuNFQqjsV0fXE2RrReUEC05jZeX4XVOGZpfyQsQjMKavygpLk05uQ0uzUmrPJSJQlk/4OrPYdtg6HhjtkrW+kIcIRSZLq4A== 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=s5j5cjtuklKW34M++bqMfpoEIhUBgUnnp8qHMAlnHP8=; b=HNGOWu0bcudAwLjhNSC/RiV20IvBQ3+n+MhliLy5Tqgf9DEPlj5yAnbBZrZBn+7TUXGHwfu2iK6uLyO4PVhLvJ9yHkutBclnq8M8KzkCUUcAf058asva4ztv9klHgRMXxh0HtWjkmDFzy7DNVgM5Yd51bWkku+pHKgQMoG+ajFtF+YiUPg8/XtNuJ++dcyn3I+9Yo0s82GwKJkCd35fICjj9zAiWLRuCBcgM/M6pxjcXhVkP/InjVEnDLPpY4qdwB7On3w3CdvoSTOIW9C8aKPuoGAODuP14r+LFn55cbq8z53zhp1zPZJ3B8evrKkbDt/IUUiaGr6Nmz93gcPorPg== 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=s5j5cjtuklKW34M++bqMfpoEIhUBgUnnp8qHMAlnHP8=; b=ejvwY9o5KdpIhmufianRBB/eGWixDCWNqomNXzdp8j0DwIN2aevSeXNZ1FychLCXD404a56xitkFuYm66ZtB65AcASyYecvXNN9DpJrCd02RuoC7+3Wpk0s9MES00H1s3MLuYVT49mL9dPTw+LPDXS/aK5rVmntu3Tpaxv7Kvok= Received: from BY5PR11MB4227.namprd11.prod.outlook.com (2603:10b6:a03:1c3::17) by BY5PR11MB4039.namprd11.prod.outlook.com (2603:10b6:a03:18b::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4436.19; Wed, 25 Aug 2021 03:49:23 +0000 Received: from BY5PR11MB4227.namprd11.prod.outlook.com ([fe80::f40e:7fa2:37d3:d9c4]) by BY5PR11MB4227.namprd11.prod.outlook.com ([fe80::f40e:7fa2:37d3:d9c4%4]) with mapi id 15.20.4436.026; Wed, 25 Aug 2021 03:49:23 +0000 From: "Victor Moreno (vimoreno)" To: Dino Farinacci CC: "Joel M. Halpern" , "lisp@ietf.org" Thread-Topic: [lisp] Upcoming meeting Thread-Index: AQHXj8P5umRqC1qVhkuHT6dFd9qoyKtwazKAgBILFgCAAKEfAIAAAlqAgAAkl4CAAGqBQw== Date: Wed, 25 Aug 2021 03:49:22 +0000 Message-ID: <80C85C05-F004-46E2-A1DE-3ADF1D048343@cisco.com> References: <3A543C97-C7D0-463D-8B7A-4BB7BF875BF9@gmail.com>

In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: joelhalpern.com; dkim=none (message not signed) header.d=none;joelhalpern.com; dmarc=none action=none header.from=cisco.com; x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: d8d7e89a-6ced-407e-6a07-08d9677b5392 x-ms-traffictypediagnostic: BY5PR11MB4039: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: em2lYfKgMCQWi2iCP89X0Z/V45E4vfNDb5ipp0mrwOI5rcQlyUMEjPoNsD42HpQYFfYuPFqkTt0KyuFN47dAs1mzavuL83bIzrf5Arra33I1ZQ1caew3l3naIldroIFsgHJ3BuGHf81MLvzz3sqsFngXyVjpIeZjL7R5iYJvzcuvRz8ZOXghsmXfWteEqo9cF3fuLLtE6yBOCH2nVHpUhjyiI1df+S5qZhYlm/Na2bT6TQbn5NaNLU1WPn7rsaXExTttpExjDLTeXSdmrsZX0c+y3HR+2hDn1HaIvHeWA/4ktrEua5Tfeb5up12snxrv0R6FVtiuSeqL+a8jQ+scrH7b5rj1ikU7XHIvQcWKgn6Z3xo8L2FZCP/DapkNHfuP8DCT8mcDnCKZ6LQs9V4a1u+RD/AuNtuyonLvYFWi5yMfCXIuV8padYv6Ju3TYuFC7bigcwek09Sbz6B7XnUlvRWAt1GsQRA1CtGYg+KoR4/Ec0Y+kMcY0/WMW+3kRmnFLnSJs8k+dfT8N0AbtH4axwhk6uAy8TeMevrF/fUcKPqkm9Uo5Ko98wDeVMCxyxfEVRz8znQ6Lsu9TAj91Az7AgJz009+Oxok38S2dR+edPonQ7KX2t07rGYkIi1x7rmX0JUQnsfKBJAJuj5R/+7RFYBl2U9RYmvV9ofb+FQXzDR7xWvyokIZx9j9sXw6QnB2OqgY9lPOXQZj63X2YCa1mPYDkbD8LFXXmsR3zpxUtbwKeGAo2RBs8/o4vd32Ho24DvA45VWd180LswG0Hk8wfmow/CFz7LXUPNVHFsoLU//spx+4M4N6roBAugHVPr4N x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY5PR11MB4227.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(366004)(136003)(376002)(346002)(39860400002)(396003)(4744005)(66556008)(5660300002)(54906003)(86362001)(38100700002)(66476007)(122000001)(26005)(6916009)(76116006)(71200400001)(4326008)(8676002)(6512007)(2616005)(53546011)(38070700005)(966005)(8936002)(64756008)(478600001)(2906002)(186003)(6506007)(66946007)(66446008)(6486002)(316002)(33656002)(36756003)(45980500001); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?utf-8?B?eFQ0dGw2TURnelUwaW90ZUsxNmZpall4QVFZY2NCRENncG8vOVRkM2tNUWt3?= =?utf-8?B?VXNrVmk4b2tNVlpUY2Z1YVBjR0lOakgxclVqQ1pPb1NZTXRYUi8zdmljeDUv?= =?utf-8?B?cXF4OXE1emIyKyt4ZGhlWCt6YVluTHhDYWhZYmsvU0tTOGxMaG5hb3FJN0Fi?= =?utf-8?B?aFFmMy9DeHB3UVUyaHNmTmZxYWR0UzA0Z3Bla3o1UEVGa29pY3NLKy9tbTdC?= =?utf-8?B?N3pHb0NGKytkZDBWQU9SRktJemZmU1Y5ditYTk14LytGSE5PYXV1TThkbWx2?= =?utf-8?B?UzA0ak91b3owelpXbll3c2dYd0pvMW9IUC9PZE0vOXJGOS9rV1UwU2xQT3Ju?= =?utf-8?B?U3JSSGJyZDVBZkozNU1YMVVMd2VDZkJGclBVY1RuNURoT1E2ZkZHRDg2Um00?= =?utf-8?B?TEwzcXlhTGJoWWprZnRPODFFSlUwZzZkcUZiWVpQQ3dvNnJPZ1dVMGtSTWMr?= =?utf-8?B?UytRbmYyb1BmVjJVY0s0Ty8zRXozdjl1R2JWLzZjeWNzT05DaFZscnMrUGs0?= =?utf-8?B?SG84OWt0d1I5cW5ERXJrK0ZPL2RoMWxpRUNpRVFTZFNJa1Y5YThnTkJ6VHN5?= =?utf-8?B?amwrYi9rV0hUNHRHdTJvemhVZzhGODNremVTQndXNUhnb1l0dEVrc1Q3UVhO?= =?utf-8?B?SkZqalpvNnRKRkUrYjhqejY4c1p5SERWbk9KdnAyb01GL29UcE90RmExMWdY?= =?utf-8?B?OE9xWjdZdVBFSTlDS0RIYllYMjZha0dtT0VScWVFaENQV0c4ZEhUa1dzMWRj?= =?utf-8?B?YXRZaEFDNUluaTZUUCtKOHJCSk9sWGFHbFI0MmcxSWdiL094Y0VGNGdmUEFt?= =?utf-8?B?RkVLN0Z6UCt2aFNyQ1hIZWI2cnlYVzFJL2ZPTWNvSW1ZU2pWRUFBNFc0aXlD?= =?utf-8?B?RGc3L1Y5Zis5VEZ1OVF6SWx5MEYwSUJTWjhzNjJ3amVmZktyVStoeDFybnFs?= =?utf-8?B?S1NBODA5YzFSM0xJL3NJR3ZmY1ViMGdZb3pvVVJDR0h2TkVGUVFsTTlDL1Yv?= =?utf-8?B?c2dpUCttWjB1VElYTTVGUWVkbk1MTjZVaTJ0MGlQUG1YeHROZVZMeWFPMERp?= =?utf-8?B?YkRSZDcwbkdoN0VzNG5SMUxudmJJckpUdUhTWmp1bEFFK2U4dXg0emxUZjlK?= =?utf-8?B?MEdLT04xSWthbTJNM2VsVnNqb0pOUzk0YndYbU5wUGRtdExkZ1NwWUVDZ2hD?= =?utf-8?B?elRyWWFaV0FTREpXZ0FKWlVTYmVMcm1XM0xzT0tTTVlCRm55c1crZWJnaTJa?= =?utf-8?B?MUMySGxFeVZmeDNieDFHQjJCckpDMVovNUhMdEllZ3hvWnpHZ0dmcTNvV3lP?= =?utf-8?B?RDRBcjVubDRndGJuWGJTaTM1VHJYVVdLV3NRRzgycytsVnQ4L0g0SjIxRW1h?= =?utf-8?B?cmt4eGdUMzdOVG5rcjVrMC9mUE44QnRZdW9nRWJPNzNZNWV3a2VOeWJ5Nm1i?= =?utf-8?B?VjRKOGs2Rkc5VEFoY1NiNStHbk9TRStES3RGR3U0am5tWGh3WW1YR09wcTcx?= =?utf-8?B?U2FnU3VScGdDS21ZMFdCY29EK2RlSVYvNEhrY1ZONGlIenVBdXJzd2l6alN5?= =?utf-8?B?dUNRTHNxUDhteVN1blhtYlV1VnpFS2hZNkVzTXZGdVpzOGtaa2FwcDVNNWNO?= =?utf-8?B?MW0xcENzR25DYUZzUzVFa1JMcnVIak8vSFQycGlrOWpmbzhQSUdadnBPTTR6?= =?utf-8?B?K3Y3cFE0Y25CMDVDUGVlSmFodWZCTWVqRWhIWjU2ZkNISHB3ZnRtRmN6YUlr?= =?utf-8?Q?ARKHHPU1sKnwaB9Lem8/lLXot/8e7uviARTKuww?= 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-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: BY5PR11MB4227.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: d8d7e89a-6ced-407e-6a07-08d9677b5392 X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Aug 2021 03:49:22.7390 (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: lqWB518Ydur1jQwCzBY0B8ojZr2D21iB5mTd8ONIopIirNpCWUs14EXHYriSkhpHj8csd3T8ZL+/n7SNytijkQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB4039 X-OriginatorOrg: cisco.com X-Outbound-SMTP-Client: 173.36.7.22, xbe-aln-007.cisco.com X-Outbound-Node: alln-core-1.cisco.com Archived-At: Subject: Re: [lisp] Upcoming meeting X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Aug 2021 03:49:32 -0000 V2Ugc2hvdWxkIGRpc2N1c3MgdGhlIHRvcGljIG9mIGJhY2tib25lIHBlZXJpbmdzIGFuZCBob3cg dGhvc2UgbWF5IGJlIGVuZm9yY2VkIGluIGFuIG92ZXJsYXkuIA0KV2Ugc2hvdWxkIGFsc28gaGF2 ZSBhIGRpc2N1c3Npb24gb24gdGhlIHBvbGljaWVzIHJlcXVpcmVkIGZvciB0aGUgYWlyIHRyYWZm aWMvb3BlcmF0aW9ucyBjb250cm9sIGFwcGxpY2F0aW9ucy4NCg0KDQpTZW50IGZyb20gbXkgaVBo b25lDQoNCj4gT24gQXVnIDI0LCAyMDIxLCBhdCAyOjI4IFBNLCBEaW5vIEZhcmluYWNjaSA8ZmFy aW5hY2NpQGdtYWlsLmNvbT4gd3JvdGU6DQo+IA0KPiDvu78NCj4+IA0KPj4gU28gdGhlIHF1ZXN0 aW9uIHJlYWxseSBmb3IgdGhlIHdvcmtpbmcgZ3JvdXAgaXMgIndoYXQgdGhpbmdzIGRvIHlvdSB0 aGluayBpdCBpcyB3b3J0aCBkaXNjdXNzaW5nLiAgTm90IGxpc3RlbmluZyB0by4gIERpc2N1c3Np bmcuDQo+IA0KPiBUaGUgaW50ZW50IG9mIHRoZXNlIHByZXNlbnRhdGlvbnMgaXMgdG8gc3B1ciBk aXNjdXNzaW9uLiBBbmQsIGFzIEkgc2FpZCwgY2FuIGJlIGFzIHNob3J0IGFzIDUgbWludXRlcyB0 byBib290c3RyYXAgZGlzY3Vzc2lvbnMuIFRoZSB0aW1lIGFsbG9jYXRlZCB3b3VsZCBiZSBmb3Ig ZGlzY3Vzc2lvbiBhbmQgbm90IGZvciBwcmVzZW50YXRpb24uDQo+IA0KPiBEaW5vDQo+IA0KPiBf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBsaXNwIG1h aWxpbmcgbGlzdA0KPiBsaXNwQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt YW4vbGlzdGluZm8vbGlzcA0K From nobody Wed Aug 25 15:15:15 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 346D33A16C2 for ; Wed, 25 Aug 2021 15:15:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net 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 VC07KItYIZ2t for ; Wed, 25 Aug 2021 15:15:05 -0700 (PDT) Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB6203A16B9 for ; Wed, 25 Aug 2021 15:15:04 -0700 (PDT) Received: by mail-lj1-x233.google.com with SMTP id w4so1226252ljh.13 for ; Wed, 25 Aug 2021 15:15:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ELqYhSxu4rCN1K97OPTfh5PJ346TZQxd62Lr6HBU5us=; b=KJbuokIpE4xNz7UC9+nic9zZlBybQbOScG80HmtagRR/htftBaU1gpM/GdZkX4Osoc dDhxUL9vV7AEMhz1qqSVYILEnlhZcimKN2bvzLdZk3ZOfAvpPOSkot27FyBwmXEI52wq JZLoXbWKA8/215sofoZ+z/e+PzDf/htqyaaXnOSpdHlrAjbWDaootj1iEh8CoHCpsaxV 2ov+HUWR6xnWTNlhtxCSLqy3bMqhAiquA2VlmXyYexerDpdEqPyGtvDn41bflQYNYveK cuJFdyg1dBRN7g1BXSMbbyBxoSb75H25lyA6lyJHyxXAVn+/4ssyiuNF91Veb+MAvDNY lGQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ELqYhSxu4rCN1K97OPTfh5PJ346TZQxd62Lr6HBU5us=; b=gzEF8tgJ3hoZJPs79hD+irqFSwn/vXyPo/OcNR2/Cd8PYa4h1T+70KbqyHr/FScduX 0+DLn+7DuvWUIXkZWQ3m+NYwuEuww5YM85aYaxtxPx7uvtFIO8tK++shAtaOJrWNmB4h 9N3q8JA4Wd0FUC/etNk3RUUkjPQGzyTzgke+Wr+OuWM/3F259pIpE+gDP4Fn2ofVeAAR WKUUkx9Q6K0raiWqekRwZFYytK7RIh2Ojz3tWLR68osUk0rhpvOOG2RcAr3IifBZdEKy CyL/aMJdtbDwYLg16DperiM0JWi1IO/6YZefm+KmAtx0Q4k/NNXPPNh0OUXJM31xX2px +QRA== X-Gm-Message-State: AOAM530mgCaXaYAcR8mn9Ve1b9NFub2xY7j1PsgfWoLF7qBq3DzhRvZ8 3eRDweeqa7a7tJztgz/QDEmGEp4Fw5S5vCD9QvY2RA6VaMDnsQ== X-Google-Smtp-Source: ABdhPJwHUeRJQIq1janwn8zwQflK1VKN0F9W9IwpXUlMsXOOf/29rrQ4kC5K+VCXmJzWiiRh1jSchcu/k7hpadT7d5A= X-Received: by 2002:a2e:9594:: with SMTP id w20mr342963ljh.361.1629929700885; Wed, 25 Aug 2021 15:15:00 -0700 (PDT) MIME-Version: 1.0 References: <3A543C97-C7D0-463D-8B7A-4BB7BF875BF9@gmail.com>

In-Reply-To: From: Robert Raszuk Date: Thu, 26 Aug 2021 00:15:00 +0200 Message-ID: To: Dino Farinacci Cc: Luigi Iannone , "lisp@ietf.org" Content-Type: multipart/alternative; boundary="000000000000d49d3e05ca699483" Archived-At: Subject: Re: [lisp] Upcoming meeting X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Aug 2021 22:15:14 -0000 --000000000000d49d3e05ca699483 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dino, Victor, all, > (4) How LISP was used at the Tokyo Olympics to monitor underlay telemetry for both unicast and multicast flows I would love to "discuss" more on this one (on-line or offline or both). It is fascinating to have overlay assisting in underlay monitoring. > We should discuss the topic of backbone peerings and how those may be enforced in an overlay. Very interesting with few real use cases I can think of already. Very useful for triggering not only discussions but perhaps some real work to pop-out of this. Thx, R. On Tue, Aug 24, 2021 at 9:09 PM Dino Farinacci wrote: > I can give 4 (or less) use-case presentations at any length you see fit. > Maybe the group can decide how indepth for each one and that can dictate > the time slot. Here are the 3 use-cases: > > (1) How LISP is used to build a blockchain network > (2) How LISP is used for contact tracing > (3) How LISP was used at the PyeongChang Olympics to move data around > without touching the underlay > (4) How LISP was used at the Tokyo Olympics to monitor underlay telemetry > for both unicast and multicast flows > > But I would like to hear from others. I think we should copy the rtgwg, > dmm, coinrg, and dinrg. But I'll wait for others to comment before doing = so. > > WG, whatdayathink? > > Dino > > > On Aug 24, 2021, at 2:32 AM, Luigi Iannone wrote: > > > > Hi, > > > > that is not a bad idea. > > > > So let=E2=80=99s start: What are the topics people want to talk about d= uring the > next meeting? > > > > Ciao > > > > L. > > > > > >> On 12 Aug 2021, at 23:59, Dino Farinacci wrote: > >> > >> Let's collectively make a list of topics that we can have a > 1/2-hour-to-1-hour slot to discuss. I am sure many people want to talk > about various topics. And from that discussion, we can create action item= s. > >> > >> And I think we should open the list creation to other WGs that may loo= k > at LISP to help solve some of their problems. And even if the topics are > tutorial in nature, that will foster discussion IMO. > >> > >> Dino > >> > >>> On Aug 12, 2021, at 2:49 PM, Joel M. Halpern > wrote: > >>> > >>> Your chairs have until September 24th to request a slot at the next > meeting. Participants indicated a desire for a 2 hour slot. Before > requesting that, I at least (I have not asked Luigi) want evidence tha > there will be actual discussion. Burning two hours for presentations tha= t > do not lead to discussion is a waste of scarce meeting time. > >>> > >>> The best evidence I know of is actual discussion on list, leading to > identified open issues to be discussed. > >>> > >>> Yours, > >>> Joel > >>> > >>> _______________________________________________ > >>> lisp mailing list > >>> lisp@ietf.org > >>> https://www.ietf.org/mailman/listinfo/lisp > >> > >> _______________________________________________ > >> lisp mailing list > >> lisp@ietf.org > >> https://www.ietf.org/mailman/listinfo/lisp > > > > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp > --000000000000d49d3e05ca699483 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Dino, Victor, all,=C2=A0

> (4) How L= ISP was used at the Tokyo Olympics to monitor underlay telemetry for both u= nicast and multicast flows

I would love to &qu= ot;discuss" more on this one (on-line or offline or both). It is fasci= nating to have overlay assisting in underlay=C2=A0monitoring.=C2=A0

> We should discuss the topic of backbone peerings and= how those may be enforced in an overlay.

Very= interesting with few real use cases I can=C2=A0think of already.=C2=A0 Ver= y useful for triggering not only=C2=A0discussions but perhaps some real wor= k to pop-out of this.=C2=A0

Thx,

On Tue, Aug 24, 2021 at 9:09 PM Dino Farinacci <farinacci@gmail.com> wrote:

I can give 4 (or less) use-case presenta= tions at any length you see fit. Maybe the group can decide how indepth for= each one and that can dictate the time slot. Here are the 3 use-cases:

(1) How LISP is used to build a blockchain network
(2) How LISP is used for contact tracing
(3) How LISP was used at the PyeongChang Olympics to move data around witho= ut touching the underlay
(4) How LISP was used at the Tokyo Olympics to monitor underlay telemetry f= or both unicast and multicast flows

But I would like to hear from others. I think we should copy the rtgwg, dmm= , coinrg, and dinrg. But I'll wait for others to comment before doing s= o.

WG, whatdayathink?

Dino

> On Aug 24, 2021, at 2:32 AM, Luigi Iannone <ggx@gigix.net> wrote:
>
> Hi,
>
> that is not a bad idea.
>
> So let=E2=80=99s start: What are the topics people want to talk about = during the next meeting?
>
> Ciao
>
> L.
>
>
>> On 12 Aug 2021, at 23:59, Dino Farinacci <farinacci@gmail.com> wrote:
>>
>> Let's collectively make a list of topics that we can have a 1/= 2-hour-to-1-hour slot to discuss. I am sure many people want to talk about = various topics. And from that discussion, we can create action items.
>>
>> And I think we should open the list creation to other WGs that may= look at LISP to help solve some of their problems. And even if the topics = are tutorial in nature, that will foster discussion IMO.
>>
>> Dino
>>
>>> On Aug 12, 2021, at 2:49 PM, Joel M. Halpern <jmh@joelhalpern.com> wro= te:
>>>
>>> Your chairs have until September 24th to request a slot at the= next meeting.=C2=A0 Participants indicated a desire for a 2 hour slot.=C2= =A0 Before requesting that, I at least (I have not asked Luigi) want eviden= ce tha there will be actual discussion.=C2=A0 Burning two hours for present= ations that do not lead to discussion is a waste of scarce meeting time. >>>
>>> The best evidence I know of is actual discussion on list, lead= ing to identified open issues to be discussed.
>>>
>>> Yours,
>>> Joel
>>>
>>> _______________________________________________
>>> lisp mailing list
>>> lisp@ietf.o= rg
>>> https://www.ietf.org/mailman/listinfo/lisp
>>
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp >

_______________________________________________
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

--000000000000d49d3e05ca699483-- From nobody Mon Aug 30 10:55:49 2021 Return-Path: X-Original-To: lisp@ietfa.amsl.com Delivered-To: lisp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA9543A1BF4 for ; Mon, 30 Aug 2021 10:55:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com 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 xfe9lSsbIKi1 for ; Mon, 30 Aug 2021 10:55:42 -0700 (PDT) Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 024E33A1BF3 for ; Mon, 30 Aug 2021 10:55:41 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4GyyfP5pbjz6G9kC for ; Mon, 30 Aug 2021 10:55:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1630346141; bh=q3AdYWemcsubtqeC3ODtQPrdTC82OjUuihrbqVd+xyQ=; h=Subject:References:To:From:Date:In-Reply-To:From; b=jAZm+YMugzYs3eeZzsJNN0wDJb2wUNcIkh5oEStMk50VjtZ07dhTjnDODDYNbXl9U 87NZffcmFcPzZomi5nopdKQKg8Dzjd94Ch20ckqH7xWtekJkX+RZIcgAFxX+wd5u+U b72EW1n8RORJyFPpvnyNdh2ausF6Y8BF3VculAxg= X-Quarantine-ID: <49-tVrq83P1D> X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net Received: from [192.168.23.64] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4GyyfP2Rkbz6G87b for ; Mon, 30 Aug 2021 10:55:41 -0700 (PDT) References: <163033223438.8507.13442799687479808565@ietfa.amsl.com> To: "lisp@ietf.org" From: "Joel M. Halpern" X-Forwarded-Message-Id: <163033223438.8507.13442799687479808565@ietfa.amsl.com> Message-ID: <20152d59-53e6-f0fe-59f6-dc5c5e169da2@joelhalpern.com> Date: Mon, 30 Aug 2021 13:55:39 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: <163033223438.8507.13442799687479808565@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Archived-At: Subject: [lisp] Fwd: NomCom 2021-2022 Call for Nominations X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2021 17:55:48 -0000 Please do volunteer and nominate others. Also, when they get to calling for feedback, please do comment. Yours, Joel -------- Forwarded Message -------- Subject: NomCom 2021-2022 Call for Nominations Date: Mon, 30 Aug 2021 07:03:54 -0700 From: NomCom Chair 2021 Reply-To: ietf@ietf.org To: IETF Announcement List CC: ietf@ietf.org Finally! The moment we've all been waiting for: C A L L F O R N O M I N A T I O N S ! ! ! The 2021-22 IETF Nominating Committee (NomCom) is seeking nominations from now until Monday, October 11, 2021. The open positions and more information are found at the NomCom web site: https://datatracker.ietf.org/nomcom/2021/ They are also included below for convenience. Nominations may be made by selecting the Nominate link at the top of the NomCom 2021 home page, or by visiting the following URL: https://datatracker.ietf.org/nomcom/2021/nominate/ Self-nomination is welcome! Note: Nominations made using the web tool require an ietf.org datatracker account. You can create a datatracker ietf.org account if you don't have one already by visiting the following URL: https://datatracker.ietf.org/accounts/create/ If you are unable to use the web form, nominations may instead be made by email to nomcom-2021 at ietf dot org. If using email, please include the word "Nominate" in the Subject and indicate in the email who is being nominated, their email address (to confirm acceptance of the nomination), and the position for which you are making the nomination. If you are nominating someone other than yourself, please tell us if we may tell the nominee that you were the one who made the nomination. If you wish to nominate someone via email for more than one position, please use separate emails to do so. Willing nominees will be asked to fill out a questionnaire specific to the position for which they are nominated. The finalized questionnaires will be available no later than Monday, September 6, 2021 (preliminary versions are already posted) and have a submission deadline of Monday, October 18, 2021. NomCom 2021-22 will follow the policy for "Open Disclosure of Willing Nominees" described in BCP 10/RFC 8713: "The list of nominees willing to be considered for positions under review in the current NomCom cycle is not confidential". Willing nominees for each position will be listed in a publicly accessible way, e.g., anyone with a datatracker account may access the lists. Additionally, the nomination form asks if we may share your own name with the nominee. In all other ways, the confidentiality requirements of BCP 10 remain in effect. All feedback and all NomCom deliberations will remain confidential and will not be disclosed. There is a field on the form you can mark in order to allow the NomCom to tell the nominee that you were the one who made the nomination. This defaults to “no” - so if you don't mark the field we won’t tell. In order to ensure time to collect sufficient community feedback about each of the willing nominees, nominations must be received by the NomCom on or before Monday, October 11, 2021. Please submit your nominations as early as possible for the sake of your nominees. Note that nominations should not wait for nominee management permission, as it is easier to decline the nomination than put one in late. The NomCom appoints individuals to fill open slots on the IAB, IESG, the IETF Trust and the LLC Board: ART AD: 1 position INT AD: 1 position OPS AD: 1 position RTG AD: 1 position SEC AD: 1 position TSV AD: 1 position IETF Trust: 1 position IETF LLC: 1 position IAB: 6 positions The list of people and posts whose terms end with the March 2022 IETF meeting, and thus the positions for which this NomCom is responsible, is: [An asterisk (*) next to a person's name indicates they do not intend to accept renomination.] LLC Board (3-year term) Jason Livingood IETF Trust (3-year term) Kathleen Moriarty IAB (2-year term) Ben Campbell * Cullen Jennings Mirja Kühlewind Jared Mauch Tommy Pauly Jiankang Yao IESG (2-year term) Murray Kucherawy, ART AD Erik Kline, INT AD Robert Wilton, OPS AD Martin Vigoureux, RTG AD Benjamin Kaduk, SEC AD * Martin Duke, TSV AD Please be resourceful in identifying possible candidates for these positions, as developing our talent is a very crucial requirement for the IETF, and also, please consider accepting a nomination. You'll find extensive information about specific positions, in individual tabs at: https://datatracker.ietf.org/nomcom/2021/requirements/ In addition to nominations, the NomCom seeks community input on the positions themselves. We need and welcome the community's views and input on the jobs within each organization. If you have ideas on the positions’ responsibilities (more, less, different), please let us know. Please send suggestions and feedback about this to nomcom-2021 at ietf dot org. Thank you for your help in identifying qualified nominees! Thanks, Gabriel Montenegro IETF NomCom Chair 2021-22 nomcom-chair-2021 at ietf dot org _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From nobody Mon Aug 30 14:24:01 2021 Return-Path: X-Original-To: lisp@ietf.org Delivered-To: lisp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D191A3A22F5; Mon, 30 Aug 2021 14:23:36 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: lisp@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.36.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: lisp@ietf.org Message-ID: <163035861678.8800.11029579097907414861@ietfa.amsl.com> Date: Mon, 30 Aug 2021 14:23:36 -0700 Archived-At: Subject: [lisp] I-D Action: draft-ietf-lisp-ecdsa-auth-06.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2021 21:23:38 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Locator/ID Separation Protocol WG of the IETF. Title : LISP Control-Plane ECDSA Authentication and Authorization Authors : Dino Farinacci Erik Nordmark Filename : draft-ietf-lisp-ecdsa-auth-06.txt Pages : 18 Date : 2021-08-30 Abstract: This draft describes how LISP control-plane messages can be individually authenticated and authorized without a a priori shared- key configuration. Public-key cryptography is used with no new PKI infrastructure required. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-ecdsa-auth/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-lisp-ecdsa-auth-06 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-ecdsa-auth-06 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Aug 31 08:51:33 2021 Return-Path: X-Original-To: lisp@ietf.org Delivered-To: lisp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 158613A19C2; Tue, 31 Aug 2021 08:51:24 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: lisp@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.36.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: lisp@ietf.org Message-ID: <163042508400.11783.8369772489369360843@ietfa.amsl.com> Date: Tue, 31 Aug 2021 08:51:24 -0700 Archived-At: Subject: [lisp] I-D Action: draft-ietf-lisp-6834bis-09.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2021 15:51:24 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Locator/ID Separation Protocol WG of the IETF. Title : Locator/ID Separation Protocol (LISP) Map-Versioning Authors : Luigi Iannone Damien Saucez Olivier Bonaventure Filename : draft-ietf-lisp-6834bis-09.txt Pages : 17 Date : 2021-08-31 Abstract: This document describes the LISP (Locator/ID Separation Protocol) Map-Versioning mechanism, which provides in-packet information about Endpoint ID to Routing Locator (EID-to-RLOC) mappings used to encapsulate LISP data packets. The proposed approach is based on associating a version number to EID-to-RLOC mappings and the transport of such a version number in the LISP-specific header of LISP-encapsulated packets. LISP Map-Versioning is particularly useful to inform communicating Ingress Tunnel Routers (ITRs) and Egress Tunnel Routers (ETRs) about modifications of the mappings used to encapsulate packets. The mechanism is optional and transparent to implementations not supporting this feature, since in the LISP- specific header and in the Map Records, bits used for Map-Versioning can be safely ignored by ITRs and ETRs that do not support or do not want to use the mechanism. This document obsoletes RFC 6834 "Locator/ID Separation Protocol (LISP) Map-Versioning", which is the initial experimental specifications of the mechanisms updated by this document. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-6834bis/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-lisp-6834bis-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-6834bis-09 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Aug 31 09:28:19 2021 Return-Path: X-Original-To: lisp@ietf.org Delivered-To: lisp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 373AA3A1BBD; Tue, 31 Aug 2021 09:28:12 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: lisp@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.36.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: lisp@ietf.org Message-ID: <163042729208.24803.12566044063500182885@ietfa.amsl.com> Date: Tue, 31 Aug 2021 09:28:12 -0700 Archived-At: Subject: [lisp] I-D Action: draft-ietf-lisp-introduction-14.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.29 List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2021 16:28:13 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Locator/ID Separation Protocol WG of the IETF. Title : An Architectural Introduction to the Locator/ID Separation Protocol (LISP) Authors : Albert Cabellos Damien Saucez (Ed.) Filename : draft-ietf-lisp-introduction-14.txt Pages : 29 Date : 2021-08-31 Abstract: This document describes the architecture of the Locator/ID Separation Protocol (LISP), making it easier to read the rest of the LISP specifications and providing a basis for discussion about the details of the LISP protocols. This document is used for introductory purposes, more details can be found in RFC6830, the protocol specification. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-introduction/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-lisp-introduction-14 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-introduction-14 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/