1 / 4

iWARP Interoperability

iWARP Interoperability. John Carrier 8 November 2004. Interoperability on the wire. DDP & RDMAP The IETF & RDMAC protocols have the same semantics and wire protocol format, but have different version numbers. IETF version better clarifies the security issues. MPA

audra
Download Presentation

iWARP Interoperability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. iWARP Interoperability John Carrier 8 November 2004

  2. Interoperability on the wire • DDP & RDMAP • The IETF & RDMAC protocols have the same semantics and wire protocol format, but have different version numbers. • IETF version better clarifies the security issues. • MPA • If a ULP generates MPA Request/Reply messages for an RDMAC RNIC it could interoperate with an IETF RNIC depending on how the RNIC implementation validated the version fields • No standard way for ULPs to exchange version information that could be used to configure the RNICs

  3. Interoperability above RDDP • Applications should interoperate regardless of whether they are written to DAPL, IT-API, or Windows APIs. • DAPL & IT-API, for example, propose using private data to exchange connection resource information (eg IRD & ORD). • IT-API considering using private data to exchange RNIC version information too.

  4. Proposal • Create an informational RFC to formalize exchange of parameters necessary to ensure interoperability.

More Related