Hi, I had a look to this document and have a couple of comments.
- The document does not explain why the original destination of the packet that experiences congestion has to be put in an IPv6 extension header. What is the technical reason? Because in principle that information can be retrieved in the Infiniband Address Vector using the destination QPN which can be found in the BTH sent back with the Fast CNP packet. - In section 4 the text seems to imply that the sender is able to categories addresses as receivers vs non-receivers. Is my understanding correct? - In the Security section it is mentioned that implementations have to implement an access list to for source address checking, but such an access list does not protect against an attacker spoofing the source address. Any hint how to solve the issue? Thanks Ciao L. > On 25 Apr 2024, at 11:01, [email protected] wrote: > > Hi all, > > > > This is a new I-D that specifies the fast congestion notification packet used > in RoCEv2 networks. > > Appreciate your review and comments. > > > Best Regards, > > Xiao Min > > Original > From: [email protected] <[email protected]> > To: 李和松10335167;肖敏10093570;李和松10335167; > Date: 2024年04月25日 16:43 > Subject: New Version Notification for draft-xiao-rtgwg-rocev2-fast-cnp-00.txt > A new version of Internet-Draft draft-xiao-rtgwg-rocev2-fast-cnp-00.txt has > been successfully submitted by Xiao Min and posted to the > IETF repository. > > Name: draft-xiao-rtgwg-rocev2-fast-cnp > Revision: 00 > Title: Fast Congestion Notification Packet (CNP) in RoCEv2 Networks > Date: 2024-04-25 > Group: Individual Submission > Pages: 12 > URL: > https://www.ietf.org/archive/id/draft-xiao-rtgwg-rocev2-fast-cnp-00.txt > Status: https://datatracker.ietf.org/doc/draft-xiao-rtgwg-rocev2-fast-cnp/ > HTMLized: > https://datatracker.ietf.org/doc/html/draft-xiao-rtgwg-rocev2-fast-cnp > > > Abstract: > > This document describes a Remote Direct Memory Access (RDMA) over > Converged Ethernet version 2 (RoCEv2) congestion control mechanism, > which is similar to Really Explicit Congestion Notification (RECN) > described in RFC 7514, also known as Fast Congestion Notification > Packet (CNP). By extending the RoCEv2 CNP, Fast CNP can be sent by > the switches directly to the sender, advising the sender to reduce > the transmission rate at which it sends the flow of RoCEv2 data > traffic. > > > > The IETF Secretariat > > > > _______________________________________________ > rtgwg mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/rtgwg
_______________________________________________ rtgwg mailing list -- [email protected] To unsubscribe send an email to [email protected]
