Thanks a lot. 

Dino

> On Oct 15, 2022, at 11:51 AM, Prakash Jain (prakjain) <[email protected]> 
> wrote:
> 
> 
> 
> We would like to present draft-jain-lisp-site-external-connectivity. 
> 
> Thanks,
> Prakash
> 
> 
> From: lisp <[email protected]> on behalf of Dino Farinacci 
> <[email protected]>
> Sent: Saturday, October 15, 2022, 10:37 AM
> To: Sharon Barkai <[email protected]>
> Cc: [email protected] <[email protected]>; [email protected] <[email protected]>
> Subject: Re: [lisp] lisp - Requested session has been scheduled for IETF 115
> 
> I would like to give an update on draft-farinacci-lisp-satellite-network. 
> 
> And I would like to request WG document for draft-farinacci-lisp-geo again. 
> It has been around for a long time and has an LCAF encoding code point in RFC 
> 8060. I can present this draft too in London. 
> 
> I would like  to make it official because it tracks the same encoding of 
> geo-coordinates that is proposed for OSPF, ISIS, and BGP. Like name-encoding 
> it’s a very short draft. So I encourage the WG to please review it. 
> 
> Thanks,
> Dino
> 
> > On Oct 15, 2022, at 2:20 AM, Sharon Barkai 
> > <[email protected]> wrote:
> > 
> > 
> > Dear Chairs,
> > 
> > Would like to give update on ietf-lisp-nexagon progress since Vienna:
> > 
> > 1) H3 EID LCAF specification added 
> > 
> > 2) H3geo.org and BDD reviews and fixes 
> > - calculating H3EID from H3 detection ID
> > - enumerating frequently changing signs 
> > 
> > 3) Public AECC PoC by Nexar, KDDI, Oracle
> > - detect free parking spaces 
> > - KDDI Access RTRs, Oracle Edge RTRs
> > - Nexar AICam, Edge application stacks
> > - Next: + lane blockages, Equinix, P5G
> > 
> > 4) LISP nexagon RTM economics:
> > - app-routing own mobility and elasticity
> > - 15x cost reduction (commercially viable)
> > - 100x frequency increase (ext. use-cases)
> > 
> > *RTM: realtime mapping enumerated channels of road conditions and base-map 
> > change detections tile by tile. 
> > 
> > --szb
> > Cell: +972.53.2470068
> > WhatsApp: +1.650.492.0794
> > 
> >> On Oct 15, 2022, at 01:48, IETF Secretariat <[email protected]> wrote:
> >> 
> >> Dear Luigi Iannone,
> >> 
> >> The session(s) that you have requested have been scheduled.
> >> Below is the scheduled session information followed by
> >> the original request. 
> >> 
> >> 
> >>   lisp Session 1 (1:00 requested)
> >>   Tuesday, 8 November 2022, Session IV 1630-1730
> >>   Room Name: Richmond 2 size: 80
> >>   ---------------------------------------------
> >> 
> >> 
> >> iCalendar: https://datatracker.ietf.org/meeting/115/sessions/lisp.ics
> >> 
> >> Request Information:
> >> 
> >> 
> >> ---------------------------------------------------------
> >> Working Group Name: Locator/ID Separation Protocol
> >> Area Name: Routing Area
> >> Session Requester: Luigi Iannone
> >> 
> >> 
> >> Number of Sessions: 1
> >> Length of Session(s): 
> >> Number of Attendees: 30
> >> Conflicts to Avoid: 
> >> 
> >> 
> >> Can't meet: Wednesday morning, Wednesday early afternoon, Wednesday late 
> >> afternoon, Thursday morning, Thursday early afternoon, Thursday late 
> >> afternoon, Friday morning, Friday early afternoon, Friday late afternoon
> >> 
> >> People who must be present:
> >> Alvaro Retana
> >> Joel M. Halpern
> >> Luigi Iannone
> >> Padma Pillay-Esnault
> >> 
> >> Resources Requested:
> >> 
> >> Special Requests:
> >> Would be preferable if LISP can meet Monday or Tuesday because of 
> >> unavailability of one of the main contributors the other days. Yet, no big 
> >> deal if not possible.
> >> ---------------------------------------------------------
> >> 
> >> 
> >> _______________________________________________
> >> lisp mailing list
> >> [email protected]
> >> https://www.ietf.org/mailman/listinfo/lisp
> > 
> > _______________________________________________
> > lisp mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/lisp
> 
> _______________________________________________
> lisp mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/lisp
> 
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp

Reply via email to