Hi,
I am not aware of any undisclosed IPR relevant to this draft.
Regards,
Shay
On Thu, Feb 1, 2024 at 6:36 PM Joel Halpern wrote:
> 1) This email initiates an IPR call for the subject document. All
> authors and contributors, please confirm explicitly to the list that all
> known relevent
Hi Joel, Hi WG,
I support the WG LC.
We believe the draft is ready to progress.
Both NEXT and REPLACE functionalities are implemented in the Broadcom DNX*
based platforms and it has been deployed in multiple networks.
Broadcom DNX*: Jericho line
Regards,
Shay
On Mon, Jan 22, 2024 at 4:28 PM
Hi Joel and WG,
We consider this resolution sufficient to close the issue.
Regards,
Shay
On Tue, Aug 8, 2023 at 6:00 PM Joel Halpern wrote:
> Issue #4 reads:
>
> In some cases it is possible that the SR policy can be expressed purely
> with C-SIDs without requiring an SRH. In this case, to
Hi Joel and WG,
The new wording is aligned with our understanding and Jericho line
implementation.
OK to close the issue.
Thanks,
Shay
On Tue, Aug 8, 2023 at 6:00 PM Joel Halpern wrote:
> Issue #3 in the datatracker reads
>
> The definition for the SegmentsLeft field of the SRH as currently
Hi Joel and WG,
Issue answered in draft-ietf-6man-sids, OK to close.
Best Regards,
Shay
On Mon, Aug 21, 2023 at 10:55 PM wrote:
> Dear WG,
>
>
>
> I’d think this issue is resolved by draft-ietf-6man-sids.
>
>
>
> Best regards, Martin
>
>
>
> *Von: *spring im Auftrag von Joel Halpern <
>
Hi Joel and team,
We agree that issue#1 can be closed.
Different SID types coexist in the same SRH: implemented and aligned with
the Broadcom Jericho line implementation.
Best Regards,
Shay
On Tue, Aug 22, 2023 at 11:26 AM Satoru Matsushima <
satoru.matsush...@gmail.com> wrote:
> This issue
Dear WG,
We would like to update on the production support by the StrataDNX
products of both flavors REPLACE and NEXT as defined in CSID draft, as well
as non-compressed "Classic" SRv6.
StrataDNX products include:
Jericho2/Jericho2c/Qumran2c/Qumran2a/Qumran2u/Qumran2n/Jericho2c+ and any
future
