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
3/20/2003
56th IETF- San Francisco, California, USA

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 Type=0x1, Error Code=0x02) 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/20/2003
56th IETF- San Francisco, California, USA

3. Association of an STag & a DDP Stream
Protection Domain (PD) Association
DDP Stream Association
3/20/2003
56th IETF- San Francisco, California, USA

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
3/20/2003
56th IETF- San Francisco, California, USA

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
3/20/2003
56th IETF- San Francisco, California, USA

6. 56th IETF- San Francisco, California, USA
Requirements
ULP MUST associate an STag and a DDP Stream
DDP MUST support Protection Domain Association and DDP Stream Association mechanisms
3/20/2003
56th IETF- San Francisco, California, USA