Hi Pablo, It seems like your main justification for attempting to put routing into LLDP is condensed in the below quote from the draft:
*"This requires the provisioning of a BGP stack on the host, the configuration * *a BGP session between the host and the leaf router."* Well as you know these days we have BGP stacks easily downloadable to any host OS. Even smart NICs and DPUs are talking BGP as well. And as to the point of BGP session configuration it can be all seamless and automated on both sides - compute and TOR/Leaf switch/router. Today you are only asking to carry few things: IPv4 addresses, IPv4 prefixes, IPv6 addresses, IPv6 prefixes, Anycast Flags, SRv6 Locator Flags, IGP Algorithm Type, Prefix Metrics, But as you know this list is never complete and you always will need to keep extending it - just like we keep extending BGP or IGPs. And the above list just focuses on host to TOR direction. Then there are real use cases where a multihomed compute would like to get dynamic routing info from TOR to host direction too. If so why not just run BGP there and be done. After all computes are becoming L3 entities for the last few years in any new modern DC deployment each running kubernetes PODs (as example). Alternatively you could run instance of an IGP there too and as it has been recently posted there is number of open source ISIS implementations too. Cheers, Robert On Thu, Mar 13, 2025 at 10:29 AM Pablo Camarillo (pcamaril) <pcamaril= 40cisco....@dmarc.ietf.org> wrote: > Hi all, > > We have submitted a draft describing an extension to LLDP to allow hosts > to advertise their IP prefixes to their attached routers, which can then > propagate the reachability of those host prefixes into routing protocols > for enabling network-wide connectivity. > Any feedback is welcomed. > > Thanks, > Pablo. > > -----Original Message----- > From: internet-dra...@ietf.org <internet-dra...@ietf.org> > Sent: Monday, March 3, 2025 9:27 AM > To: cf(mailer list) <c...@cisco.com>; Bernier, Daniel < > daniel.bern...@bell.ca>; Pablo Camarillo (pcamaril) <pcama...@cisco.com> > Subject: New Version Notification for > draft-filsfils-rtgwg-lightweight-host-routing-00.txt > > A new version of Internet-Draft > draft-filsfils-rtgwg-lightweight-host-routing-00.txt has been successfully > submitted by Pablo Camarillo and posted to the IETF repository. > > Name: draft-filsfils-rtgwg-lightweight-host-routing > Revision: 00 > Title: Lightweight Host Routing using LLDP > Date: 2025-03-03 > Group: Individual Submission > Pages: 11 > URL: > https://www.ietf.org/archive/id/draft-filsfils-rtgwg-lightweight-host-routing-00.txt > Status: > https://datatracker.ietf.org/doc/draft-filsfils-rtgwg-lightweight-host-routing/ > HTMLized: > https://datatracker.ietf.org/doc/html/draft-filsfils-rtgwg-lightweight-host-routing > > > Abstract: > > Link Layer Discovery Protocol (LLDP) is widely deployed today for > discovery of information across network elements like routers, > switches, and hosts. This document extends LLDP to allow hosts to > advertise their IP prefixes to their attached routers which can then > propagate the reachability of these host prefixes into routing > protocols for enabling network-wide connectivity. > > > > The IETF Secretariat > > > _______________________________________________ > rtgwg mailing list -- rtgwg@ietf.org > To unsubscribe send an email to rtgwg-le...@ietf.org >
_______________________________________________ rtgwg mailing list -- rtgwg@ietf.org To unsubscribe send an email to rtgwg-le...@ietf.org
