Internet-Draft draft-ietf-lisp-eid-mobility-14.txt is now available. It is a
work item of the Locator/ID Separation Protocol (LISP) WG of the IETF.
Title: LISP L2/L3 EID Mobility Using a Unified Control Plane
Authors: Marc Portoles Comeras
Vrushali Ashtaputre
Fabio
I didn't and believe it doesn't need to go at the beginning of the document.
Dino
> On Apr 30, 2024, at 12:23 PM, Luigi Iannone wrote:
>
>
>
>> On 30 Apr 2024, at 17:41, Dino Farinacci wrote:
>>
>> I'll make all your chnages but this one comment:
>>
>>> On Apr 30, 2024, at 7:58 AM, Luigi I
> On 30 Apr 2024, at 17:41, Dino Farinacci wrote:
>
> I'll make all your chnages but this one comment:
>
>> On Apr 30, 2024, at 7:58 AM, Luigi Iannone wrote:
>>
>> routing protocols, namely OSPF [I-D.acee-ospf-geo-location], IS-IS
>> [I-D.shen-isis-geo-coordinates],
>
> It is not true.
I had to IAAN request Type value 17 (and not 15 since RFC8060 had already
spec'ed type values 15 and 16). And I wasn't sure if it was implied by Luigi's
comments, but the name of this encoding needs to be different than the
"Geo-Coordinates type 15" in RFC8060, so it is called "Geo-Location".
D
Internet-Draft draft-ietf-lisp-geo-05.txt is now available. It is a work item
of the Locator/ID Separation Protocol (LISP) WG of the IETF.
Title: LISP Geo-Coordinate Use-Cases
Author: Dino Farinacci
Name:draft-ietf-lisp-geo-05.txt
Pages: 15
Dates: 2024-04-30
Abstract:
I'll make all your chnages but this one comment:
> On Apr 30, 2024, at 7:58 AM, Luigi Iannone wrote:
>
> routing protocols, namely OSPF [I-D.acee-ospf-geo-location], IS-IS
> [I-D.shen-isis-geo-coordinates],
It is not true. Only the GPS encoding is the same. The general encoding that
wraps
Hi Dino,
Below you can find my suggestions. Should be easy and quick but let me know if
you need any clarification.
Ciao
L.
>
>
>
>
> Network Working Group D. Farinacci
> Internet-Draft lispers.net
> Inte
