Hi Jeff,
Open/R
(https://engineering.fb.com/2017/11/15/connectivity/open-r-open-routing-for-modern-networks/
) is actually an in-house link-state routing protocol.
The following text is quoted from the above article.
"For many years, Facebook has been operating these large-scale fabrics
Hi Daniele,
Thanks a lot for your careful review and comments. Please see my replies inline
[Chongfeng]:
-Original Message-
From: Daniele Ceccarelli via Datatracker [mailto:nore...@ietf.org]
Sent: Friday, November 24, 2023 10:21 PM
To: rtg-...@ietf.org
Cc:
operational points to understand what support is in network duly noted and
yes, yang is probably best angle for now to include the capability per tlv
however, some observations below ...
On Tue, Nov 28, 2023 at 2:18 PM wrote:
> Hi,
>
>
>
> This draft proposes advertisements which are out of
Hi Aijun,
> On Nov 26, 2023, at 7:05 PM, Aijun Wang wrote:
>
> Some additional questions:
>
> The draft say “The contents of a multi-part TLV MUST be processed as if they
> were concatenated. If the internals of the TLV contain key information, then
> replication of the key information
Hi,
This draft proposes advertisements which are out of spec from the point of
existing RFCs and implementations.
Enabling one router to send such advertisement while not all routers are
upgraded to support this extension will harm the network, potentially very
significantly and likely by
Les,
Thanks for your message and the clarifications.
I feel a bit obliged to answer. Please see inline.
From: Les Ginsberg (ginsberg)
Sent: Friday, November 24, 2023 10:25 PM
To: DECRAENE Bruno INNOV/NET ; Tony Li
Cc: draft-pkaneria-lsr-multi-...@ietf.org; lsr
Subject: RE:
Hi Jeff,
5 topology hops is 5/3->66% worse than 3 hops for latency, reliability, and
cost.
Why do you assume 5 hops if the needed scale is possible to achieve by 3 hops?
In fact, modern 1-ASIC switches (4.8Tbps, 51.2Tbps) permit 390k 100GE
end-points for Megafly 3-hops topology (with 50%
Hi Shuping,
Thanks for the review. Please see my response below inline.
Thanks,
Yingzhen
On Fri, Nov 24, 2023 at 12:37 AM Shuping Peng via Datatracker <
nore...@ietf.org> wrote:
> Reviewer: Shuping Peng
> Review result: Has Issues
>
> Hello,
>
> I have been selected as the Routing Directorate
Dhruv –
Thanx for finding this and updating the IETF case – I had looked and indeed saw
the issue in the minutes of other WGs.
Also thanx to Yingzhen for uploading the chat history – you can now see a more
readable format in the LSR Minutes.
Les
From: Dhruv Dhody
Sent: Monday, November
