Skip to main content

Minutes IETF120: lisp: Wed 00:30
minutes-120-lisp-202407240030-01

Meeting Minutes Locator/ID Separation Protocol (lisp) WG
Date and time 2024-07-24 00:30
Title Minutes IETF120: lisp: Wed 00:30
State Active
Other versions markdown
Last updated 2024-09-09

minutes-120-lisp-202407240030-01

IETF 120 LISP WG Minutes

CHAIR(s):

Padma Pillay-Esnault ( padma.ietf AT gmail.com )
Luigi Iannone ( ggx AT gigix.net )

SECRETARY: Alberto Rodriguez-Natal ( natal AT cisco.com )

AGENDA

Session 1/1 (60 Minutes)
Tuesday, July 23, 2024

    17:30 - 18:30 Vancouver (PDT), Session IV, 60 Minutes
    17:30 -> 18:30 PDT (San Francisco)
    20:30 -> 21:30 EDT (New York time)
    00:30 -> 01:30 UTC (NOTE this is July 24 morning)
    02:30 -> 03:30 CEST (Paris time NOTE this is July 24 morning)
    08:30 -> 09:30 CST (Beijing time NOTE this is July 24 morning)
    10:30 -> 11:30 AEDT (Sydney time NOTE this is July 24 morning)

Room: Georgia B

Status reports for WG drafts
  • LISP Traffic Engineering: Review addressed and shepherd writeup
    ongoing. Ready for WGLC.
  • LISP Name Encoding: ASCII vs UTF-8 encoding still open issue.
    Waiting feedback from the IESG.
  • LISP Geo: Kiran (shepherd) ready to move forward.
  • LISP LCAF bis documents: Anton Smirnov to take care of that but no
    news.
  • LISP DDT and NAT: Asked Albert Cabellos to be appointed editor. No
    news.
WG Items

Padma: There is no determinism on the protocol choice. Make the
capabilities exchange more explicit.
Luigi: How to extend the protocol? Document should contain hint on how
to do it.
Darrel Lewis: Alternatives to the use of TCP are limited, so few
reserved bits can be used for that.
Dino Farinacci: If we use bits for protocols let's allocate 3 of them
for TCP, QUIC and Multicast QUIC.
Marc Portoles Comeras: Is the bits based solution definitive?
Luigi: We can ask the mailing list, reporting this discussion and
asking if there are different opinions.

Marc Portoles Comeras: is the use of terms withdraw and rejection ok?
Luigi: As an individual, the words are OK, just the document was not
clear about them. Adding clarifying text would suffice.
Padma: Add more examples on how it works.

Marc Portoles Comeras: DO we need a sub registry for the message types?
Luigi: I will look at the IANA section and suggest action.

Document needs to address comments from Yangdoctors then ready for WGLC.

Padma: For documents that are ready to move forward would be good if
authors review the related parts in the yang document.

Non WG Items

Prasad Govindan: 6831bis has a new part about head-end replication that
was not in the original 6831 document.
Dino Farinacci: Correct.

Luigi: We have several call requests that will be serialized.

Discussion

Dino Farinacci: I have a set of drafts for which I am responsible.

  • LISP Decent: will be submitted to ISE
  • LISP Mobile Network: let to expire
  • LISP Telemetry: let to expire
  • LISP Satellite: not sure what to do

Luigi: Satellite can be merged in the use case document.
Dino: Need help to do it.

Dino: Set of draft that need to be assigned to move forward, here is my
proposal:

  • LISP Mobile Node: Marc
  • LISP VPN: Marc/Victor
  • LISP EID Anonymity: Padma
  • LISP Predictive RLOCs: Padma
  • LISP ECDSA AUTH Luigi/Erik
  • LISP perspective: Luigi

Luigi: Careful about chairs being editor of documents.
Jim: OK if then the document is handled by the other chair that manages
the calls on consensus.