Tony,
Thanks for the document. Certainly an interesting topic to discuss.
1. Is there any specific reason to bring this up now, e.g.: urgency to
avoid running out of headroom or the like ? Would be good to add that
to the text for motivation. right now it reads very architectural.
2. There is
> On Feb 25, 2022, at 12:02 AM, Toerless Eckert wrote:
>
>> Abstract
>>
>>Routing and addressing are inexorably tied, and the scalability of
>
> ^
> Nit:
>prepend "In the Internet architecture"
>
> E.g.: If we would have a better architecture, including LISP, we would
> arguably h
Hi Toerless,
> 1. Is there any specific reason to bring this up now, e.g.: urgency to
> avoid running out of headroom or the like ? Would be good to add that
> to the text for motivation. right now it reads very architectural.
Yes. My hair is turning gray. AFAICT, this is not written down elsew
I primarily thought that the document wasn't improving by making statements
about routing and addressing in general given how it does specifically seem
to want to improve the situation for the Internet Architecture, so non-Internet
Architecture considerations would be derailments ?!
Aka: Avoid for
On Fri, Feb 25, 2022 at 08:34:29AM -0800, Tony Li wrote:
> > Aka: In one possible universe (where less-stupid router vendors finally
> > start putting powerful enough control plane CPU/memory into routers),
> > i may not predominantly have a scalability issue of the routing subsystem,
> > but only
> On Feb 25, 2022, at 9:38 AM, Toerless Eckert wrote:
>
> I just ran against control plane resource limitations in products way more
> often during the decades than i felt necessary knowing what control plane
> performane would be possible with appropriately scaled CPU/memory.
Well, here’s t
> b) auto-aggregation within routers from routing-plane to forwarding
> plane. Aka: Just don't populate the poor HW tables with all those
> non-aggregated prefixes, but calculate the minimum number of
> sufficient shorter prefixes.
We did that in year 2000. It is/was called FIB compression.
> We use all three in the Internet (longest prefix, ARP/LISP, and RIP/OSPF,
> respectively).
But we haven't used ML. Wonder what people think about that?
Dino
___
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area
> Yes. My hair is turning gray. AFAICT, this is not written down elsewhere. If
> not published, the concept of an abstraction action boundary might be lost.
> Noel, who deserves 100% of the credit for this has already passed the point
> of caring.
I will vouch for this since the last networking
> Is LISP really part of the Internet Architecture ? I thought (unfortunately)
> not. E.g.: i don't think i can become an Internet transit ISP without
> participating
> in the "native" BGP routing. "Hey, i don't want these gigantic BGP Internet
> routing tables, and my customers don't need it. I j
> On Feb 25, 2022, at 3:07 PM, Dino Farinacci wrote:
>
>
>>
>> We use all three in the Internet (longest prefix, ARP/LISP, and RIP/OSPF,
>> respectively).
>
> But we haven't used ML. Wonder what people think about that?
Machine learning?
As in the failed DARPA Intelligent Nets effort?
I
>
>
>> On Feb 25, 2022, at 3:07 PM, Dino Farinacci wrote:
>>
>>
>>>
>>> We use all three in the Internet (longest prefix, ARP/LISP, and RIP/OSPF,
>>> respectively).
>>
>> But we haven't used ML. Wonder what people think about that?
>
> Machine learning?
Yes.
> As in the failed DARPA In
Dear Wassim Haddad,
The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request.
intarea Session 1 (1:00 requested)
Tuesday, 22 March 2022, Afternoon Session II 1430-1630
Room Name: Grand Klimt Hall 2 size:
Hi, Dino,
Yes, ML can help deal with unpredictable link issues *if* there are some
underlying statistics at work. However, it’s generally more useful to track
such links as faulty and replace them than to use AI to “adapt” to their
failure patterns.
I looked at ML techniques for predicting con
FWIW...
> On Feb 25, 2022, at 3:10 PM, Dino Farinacci wrote:
>
>> Is LISP really part of the Internet Architecture ? I thought (unfortunately)
>> not. E.g.: i don't think i can become an Internet transit ISP without
>> participating
>> in the "native" BGP routing. "Hey, i don't want these gigan
15 matches
Mail list logo
