Direct%20Data%20Placement%20(DDP)%20over%20Reliable%20Transports

1
Direct Data Placement (DDP) over Reliable
Transports

• 56th IETF San Francisco
• 20th March 2003
• draft-shah-rddp-ddp-00
• Hemal V. Shah, Intel Corporation
• hemal.shah_at_intel.com

2
Changes since last draft (IETF-55)

• draft-shah-iwarp-ddp-01 was renamed to
  draft-shah-rddp-ddp-00 (official WG draft)
• One error description (Error Type0x1, Error
  Code0x02) was corrected to use DDP Stream
  instead of RDMA Stream
• STag not associated with DDP Stream
• Text was added in Security section on association
  of an STag and a DDP Stream

3
Association of an STag a DDP Stream

• Protection Domain (PD) Association
• DDP Stream Association

4
Protection Domain (PD) Association

• A unique Protection Domain Identifier (PD ID) is
  used to associate an STag with a set of DDP
  Streams
• Use of STag is only permitted on the DDP Streams
  that have the same PD ID as the STag
• For an incoming Tagged DDP Segment
• Use of STag is only permitted if PD IDs match
• If PD IDs do not match, then the DDP layer MUST
  surface a local error to ULP

5
DDP Stream Association

• DDP Stream is identified locally by a unique
  identifier (ID)
• STag is associated with a DDP Stream using DDP
  Stream ID
• For an incoming Tagged DDP Segment
• Use of STag is only permitted if DDP Stream IDs
  match
• If IDs do not match, DDP MUST surface a local
  error to ULP

6
Requirements

• ULP MUST associate an STag and a DDP Stream
• DDP MUST support Protection Domain Association
  and DDP Stream Association mechanisms