Thank you Albert. These are very good comments. See inline: --szb Cell: +972.53.2470068 WhatsApp: +1.650.492.0794
> On Feb 5, 2021, at 12:26, Albert López <[email protected]> wrote: > > > Hi all, > > After reading the draft, I believe it is a really good idea, but I think that > the document needs more work to be done. > > Some comments and questions that I have when reading the document are the > following ones: > > In section 6, the structure of a "Nexgon packet" is introduced with the > Nexgon header but no description is provided of the fields of this header. > After reading the document you can deduce the use of some of these fields but > not all of them. I will add more text on the nexagon header. In principle these are: Type: we specify two types only here kv, kv, kv... basic and default use v, k, k, k .. for large area with same value proprietary extensions add more types Gzip: is a flag if the k,v where zipped. In close by tiles the compression is high Reserved: Pair count: how many kv are we sending, in kv kv or v kkk form > > "EdgeRTRs then re-encapsulates annotation packets either to remote EdgeRTR > (option 1) or to homed H3ServiceEID ServerXTR (option 2)" but I think no more > information is provided about option1 and option2. The scenario is clear for > me when we have one EdgeRTR between client-XTR and server-XTR but when we > have to reencapsulate packets from EdgeRTR to another EdgeRTR I don't > understand when to use it and the process to implement it. Is it using ELPs? The LISP default is option1 clients and servers are not homed to the same RTR. This is for example in a MEC or Wavelength type deployment. In this option the servers EID are registered in the mapping with the RLOC of their RTR. The ServerXTR is just a tunnel to the RTR and does not participate in the lisp control plane. The clientXTR and ServerXTR solve NAT traversal between mobile and edge providers. We left the door open to a more distributed implementation for example by cell towers or RSU. In this case there is only one RTR between clients and servers. > > "EdgeRTRs do not register MobilityClients’ EIDs at the mapping service as > these are temporary-renewed while using the mobility network.": Does the > Client-XTR send Map Registers to the EdgeRTR? If not, how does it know the > Client-xTR's RLOCs and its changes?. Otherwise, If it sends Map-Register, can > we consider the EdgeRTR as the MS of the Client-xTR? At this point we do not allow unicast between clients, only publish clients to servers, and signal free feed servers to clients. > > Is there any mechanism contemplated for the MobilityClient to change the > associated EdgeRTRs? for instance repeating the procedure explained in > section 4 when changing to a new H3.9 section? > Yes clients can repeat AAA procedure and are supposed to renew AAA. > I think that more references need to be added to the document like the > DIAMETER RFC. > Will add > I hope these comments could help to improve the document. > They do. I will clarify the language and send update as soon as all inputs are in. Thank you for devoting the time and attention. > Best regards > > Albert López > > > > >> On 3/2/21 16:25, Luigi Iannone wrote: >> Hi All, >> >> The authors of draft-ietf-lisp-nexagon submitted the current version back >> in October solving issues raised during SECDIR review. >> No further comments have been raised and the authors consider the document >> stable and ready for WG Last Call. >> >> This email open the usual two weeks Working Group Last Call, to end February >> 17th, 2021. >> >> Please review this WG document and let the WG know if you agree that it is >> ready to be handed over to the AD. >> If you have objections, please state your reasons why, and explain what it >> would take to address your concerns. >> >> NOTE: silence IS NOT consensus! >> >> Thanks >> >> Luigi & Joel >> >> >> _______________________________________________ >> 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
