Thanks Sue to advance this work, Samier, let me know if you want to add LLDP topo model in the appendix, which is augmented from L2 topo model, similar to OSPF topology example is defined in the Appendix B of RFC8346. If we reach agreement on this (whether not needed or add an example in the appendix), I think we are ready to go.
-Qin 发件人: Susan Hares [mailto:[email protected]] 发送时间: 2020年3月10日 1:29 收件人: Qin Wu <[email protected]>; 'SAMIER BARGUIL GIRALDO' <[email protected]>; [email protected]; [email protected] 抄送: 'Oscar González de Dios' <[email protected]>; Dongjie (Jimmy) <[email protected]>; 'Cristian Felipe Rosero Carvajal (COMMS-EGM)' <[email protected]> 主题: RE: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology Qin and Samier: I’m excited to see that L2 Data model is being implemented. If it turns out that the L2 topology model needs to be augmented with additional LLDP topology drafts, then I suggest you simply write an augmentation for the L2 model. I will be glad to support you and work with on the LLDP. With this in mind, I will close the shepherd’s report and send this long overdue RFC to the IESG. If the I2RS WG closes, then the On the BGP-LS information, I suggest sending a note to IDR to determine if anyone has collected LLDP information across domains. If you wish, I can (as co-chair of IDR) send that information for you. Susan Hares From: i2rs [mailto:[email protected]] On Behalf Of Qin Wu Sent: Monday, February 10, 2020 1:12 AM To: SAMIER BARGUIL GIRALDO; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: Oscar González de Dios; Dongjie (Jimmy); Cristian Felipe Rosero Carvajal (COMMS-EGM) Subject: Re: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology SAMIER: Come back for this comment, I think similar to L3 Topology, L2 network topology model is independent of layer 2 protocol type, e.g., LLDP. But Layer 2 topology model can be augmented with addition definitions for LLDP topology type. One OSPF topology example is defined in the Appendix B of RFC8346. LLDP topology model can be defined in the same way. Regarding your question, I think H-SDN-C should have boundary node information from its inventory model collected by each IP controller and it is the job of H-SDN-C to be responsible for topology stitching in different domains, there are many protocols that can be used to expose topology from IP controller to H-SDN-C, e.g., BGP-LS routing protocol. We haven’t seen LLDP can be used to collect cross inter-domain neighbourhood,e.g.,peer IP controller. -Qin 发件人: SAMIER BARGUIL GIRALDO [mailto:[email protected]] 发送时间: 2020年1月23日 22:27 收件人: Qin Wu <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> 抄送: Oscar González de Dios <[email protected]<mailto:[email protected]>>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <[email protected]<mailto:[email protected]>>; Dongjie (Jimmy) <[email protected]<mailto:[email protected]>> 主题: RE: Mail regarding draft-ietf-i2rs-yang-l2-network-topology Hi Qin, I hade made a mistake. I was trying to say LLDP neighbour. A I will try to explain it again to avoid confusions. As your mentioned the LLDP can be enabled in the network and create the L2 Links (this is our intention). However, We have not seen in the model the way to express this inter-domain neighbourhood, for example: [cid:[email protected]] In this network scenario: * Each domain controller will expose a L2 Topology * IP Controller-1 have not in its node DB the Node B * IP Controller-2 have not in its node DB the Node A How the H-SDNc can join the two L2-topo (each from a controller) to generate the common view? It is possible with this model? Regards, -- Samier Barguil Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte | Móvil +57 3017026430 Móvil +34 665416074 E-mail [email protected]<mailto:[email protected]> E-mail [email protected]<mailto:[email protected]> ________________________________ De: Qin Wu <[email protected]<mailto:[email protected]>> Enviado: miércoles, 22 de enero de 2020 20:44 Para: SAMIER BARGUIL GIRALDO <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Cc: Oscar González de Dios <[email protected]<mailto:[email protected]>>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <[email protected]<mailto:[email protected]>>; Dongjie (Jimmy) <[email protected]<mailto:[email protected]>> Asunto: RE: Mail regarding draft-ietf-i2rs-yang-l2-network-topology Hi, Samier: L2 topo is used to describe neighbor relationship and can be collected by LLDP or any other Layer 2 protocol, are you sure LDP protocol should be part of L2 topo model? If there is a use case for LDP, L2 topo model could be augmented in the separate model to support such use case. BTW, L2 topo has completed WGLC. The token is in the document shepherd’s hand. -Qin 发件人: SAMIER BARGUIL GIRALDO [mailto:[email protected]] 发送时间: 2020年1月21日 0:36 收件人: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> 抄送: Oscar González de Dios <[email protected]<mailto:[email protected]>>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <[email protected]<mailto:[email protected]>> 主题: Mail regarding draft-ietf-i2rs-yang-l2-network-topology Hello authors, We have been using your model to describe our L2 Topology in a single domain IP scenario. During the last month we have been exporting this topology to a centralized entity in order to build a multi-domain (two IP domain controllers) L2-Topology. However, In order to build this end-to-end L2 view of our networks we were expecting to use the LDP neighbour relationship, however in the draft-ietf-i2rs-yang-l2-network-topology there is not such possibility. Do you have any plan to include this information in the model? If not how do you expect a centralized entity (Network Orchestator) can build an end-to-end L2 view of the network if the L2 Topo is reported by two domain controllers? Thanks in advance for your answer. Regards, Samier Barguil Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte | Móvil +57 3017026430 Móvil +34 665416074 E-mail [email protected]<mailto:[email protected]> E-mail [email protected]<mailto:[email protected]> ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
