Hi David, UDP Source port need to be unique only as per 4 tuple.
Cheers, Jeff > On Feb 6, 2023, at 12:53 PM, Zhe Lou <[email protected]> wrote: > > Hi Jeff, > > Good point, thanks! We will update the draft accordingly. > > One potential issue might be that UDP source port has 2-byte and QP has > 3-byte. Since there are only 2^16 UDP source ports, each UD QP should choose > a source port number smaller than 65535. And the total number of UD QPs > should not exceed 65536. Otherwise, it will have problems. > > Regards > David > > > -----Original Message----- > From: Jeff Tantsura <[email protected]> > Sent: Saturday, 4 February 2023 21:08 > To: zhouyujing (A) <[email protected]> > Cc: [email protected]; [email protected]; Zhe Lou <[email protected]> > Subject: Re: [sfc] New draft about In-network Computing Solution > (draft-zhou-sfc-sinc) > > Hey, > > QPs are never exposed to the Eth/IP/UDP RoCEv2 network/devices, however, in > most cases, to preserve ordering within QPs, QPs are mapped into 5 tuples, > since the only mutable header in RoCEv2(or similar RDMA over IP/UDP > protocols) is the UDP source port (destination is set to 4791), each QP > between a given pair of sender and receiver gets its own UDP source port > (which also allows to per QP/flow hashing in the network). > > Cheers, > Jeff > >> On Oct 28, 2022, at 01:37, zhouyujing (A) >> <[email protected]> wrote: >> >> Hi all, >> >> We submitted a new draft about In-Network Computing >> (https://datatracker.ietf.org/doc/draft-zhou-sfc-sinc/). In this draft, we >> want to discuss a mechanism "Signaling In-Network Computing operations" >> (SINC) to enable in-packet operation signaling for in-network computing for >> specific scenarios. >> >> Hope to get your review and comments. >> >> Many thanks! >> >> Best, >> Yujing Zhou >> >> -----Original Message----- >> From: [email protected] <[email protected]> >> Sent: 2022年10月24日 9:56 >> To: Zhangcuimin <[email protected]>; Luigi IANNONE >> <[email protected]>; zhouyujing (A) <[email protected]>; >> Zhangcuimin <[email protected]>; Zhe Lou <[email protected]> >> Subject: New Version Notification for draft-zhou-sfc-sinc-00.txt >> >> >> A new version of I-D, draft-zhou-sfc-sinc-00.txt has been successfully >> submitted by Yujing Zhou and posted to the IETF repository. >> >> Name: draft-zhou-sfc-sinc >> Revision: 00 >> Title: Signaling In-Network Computing operations (SINC) >> Document date: 2022-10-23 >> Group: Individual Submission >> Pages: 19 >> URL: https://www.ietf.org/archive/id/draft-zhou-sfc-sinc-00.txt >> Status: https://datatracker.ietf.org/doc/draft-zhou-sfc-sinc/ >> Html: https://www.ietf.org/archive/id/draft-zhou-sfc-sinc-00.html >> Htmlized: https://datatracker.ietf.org/doc/html/draft-zhou-sfc-sinc >> >> >> Abstract: >> This memo introduces "Signaling In-Network Computing operations" >> (SINC), a mechanism to enable in-packet operation signaling for in- >> network computing for specific scenarios like NetReduce, >> NetDistributedLock, NetSequencer, etc. In particular, this solution >> allows to flexibly communicate computation parameters to be used in >> conjunction with the packets' payload, to signal to in-network SINC- >> enabled devices the computing operations to be performed. >> >> >> >> >> The IETF Secretariat >> >> >> >> _______________________________________________ >> rtgwg mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/rtgwg _______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
