Please provide text and tell me where you prefer the paragraph starting with "This document proposes …" to go.
Dino > On May 2, 2024, at 6:07 AM, Luigi Iannone <g...@gigix.net> wrote: > > Dino, > > You missed the important part, the fact that the document updates 8060 and > deprecates types 5. > The current text still say that the format is specified in 8060, which is not > the case anymore. > Here is the suggested text again: > > This document proposes a new LCAF encoding for geo-coordinates, which is > compatible with the one used in other > routing protocols, namely OSPF [I-D.acee-ospf-geo-location], IS-IS > [I-D.shen-isis-geo-coordinates], > and BGP [I-D.chen-idr-geo-coordinates]. This document updates [RFC8060]. In > particular, the use of geo-coordinates > encoding defined in Section 4.3 of [RFC8060] and identified by LCAF type 5 is > deprecated. > > > Two additional points: > > 1. The abstract must be updated. You are now proposing a new format. You also > need to state “This document updates RFC 8060”. > > 2. Section 5: Type 17 is suggested, not requested. > > > Ciao > > L. > > >> On 30 Apr 2024, at 18:31, Dino Farinacci <farina...@gmail.com> wrote: >> >> 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 <g...@gigix.net> wrote: >>> >>> >>> >>>> On 30 Apr 2024, at 17:41, Dino Farinacci <farina...@gmail.com> wrote: >>>> >>>> I'll make all your chnages but this one comment: >>>> >>>>> On Apr 30, 2024, at 7:58 AM, Luigi Iannone <g...@gigix.net> 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 the GPS encoding is LCAF. You do not want to mislead that OSPF >>>> and ISIS use LCAF. >>> >>> Agreed. You can add exactly this details. >>> >>> Thanks >>> >>> Luigi >>> >>>> >>>> Dino >>>> >>> >> > _______________________________________________ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
