Sean, if look at the proposal it shows 2 ways to address this.
1. Have 2 protocols. One just send SRC IP address and port, and provdie 64 bytes to ULP. Another one send both SRC and DEST info and leaves 48(+-) bytes of private data for ULP. 2. Have 2 protocols. Split IPv4 and IPv6 methods. For IPv4 send SRC and DST addressing and 64 bytes of ULP private data. For IPv6 we have several options. a. GID=IPv6 address b. use second CM frame to have carry ULP private data. c. others But having multiple versions supported is not pleasant. It looses a simple backwards compatibility of current protocol which just formats CM private data field. Arkady Kanevsky email: [EMAIL PROTECTED] Network Appliance phone: 781-768-5395 375 Totten Pond Rd. Fax: 781-895-1195 Waltham, MA 02451-2010 central phone: 781-768-5300 > -----Original Message----- > From: Sean Hefty [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 19, 2005 1:00 PM > To: Richard Frank > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; > openib-general@openib.org; Davis, Arlin R > Subject: Re: [dat-discussions] RE: [openib-general] Re: iWARP > emulationprotocol > > > Richard Frank wrote: > > Oracle currently depends on 64 bytes of private data for connect and > > accept. > > Is any of that data used to exchange address information? > > It's impossible to provide both the source and destination > address in the CM REQ > private data and still give the user 64 bytes. The source > address is needed for > the reverse GID->IP lookup. Can we make due without the > destination address? > > - Sean > _______________________________________________ > openib-general mailing list > openib-general@openib.org > http://openib.org/mailman/listinfo/openib-general > > To unsubscribe, please visit > http://openib.org/mailman/listinfo/openib-general > _______________________________________________ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general