AD review of draft-ietf-rddp-sctp-03

headers Lars Eggert | 15 Jun 2006 08:29

On Jun 15, 2006, at 1:45, Caitlin Bestler wrote:
>> Section 6., paragraph 3:
>>>    The local interface MAY associate a DDP Endpoint with the DDP
>>>    Stream based upon the initial exchanges of a DDP Session, and
>>>    terminate that association at the session's end.
>>
>>          Is that an RFC2119 "MAY", or maybe a MUST or SHOULD?
>
> The local interface MAY *dynamically* associate a DDP Endpoint
> with the DDP stream *based upon the initital exchanges*, or there
> may be a static mapping from DDP Endpoint to DDP Stream. The
> latter would only meet the needs of specialized applications,
> but such applications are allowed to use the protocol.

This paragraph would be good to add to the document.

> Conventional RDMA APIs require that the application be able to
> select the DDP Endpoint ("QP") after receiving the connection
> request. But that is an API convention that has no relation
> to the wire protocols, beyond a brief mention as to why
> private data is supported.
>
> The RDDP Working Group made a deliberate decision NOT to
> standardize the local interface requiremenets beyond what
> was required for interoperability and/or security. Therefore
> even a "SHOULD" would be inappropriate here. It is definitely
> not a "MUST".

And maybe a condensed version of this as well.

Lars
--

-- 
Lars Eggert                                     NEC Network Laboratories

Re: RE: AD review of draft-ietf-rddp-sctp-03