Hi,
> * operate in unreliable mode. This can be satisfied
>
> by passing this requirement from the QoS-NSLP
> layer to the GIST layer via the API
> transfer-attributes.
>
> Okay, no problem here, I can set the Sendmsg() flag
> fine.
Correct.
> * do not create a message association state. This
> requirement can be satisfied by a local policy,
> e.g., the QNE is configured to do not
> create a message association state
I am not sure here. The message association state needs
to be created and maintained if, and only if, you want
to have a message association (e.g. TCP) between the peers.
If you choose the unreliable transport (i.e. UDP), which is
the datagram mode (D-Mode), then there is no message associate
and therefore no state (well, in fact, we have a minimal
state too). On the other hand, if you want to have reliable
transport (e.g. TCP), then you WANT a message association and
therefore GIST NEEDS to maintain a message association state.
Thus, I am not sure, what the authors mean here. If you do not
know either, can you tell me the section of the draft where this
is written?
> * do not create any NTLP routing state. This can be
> satisfied by passing this requirement from the
> QoS-NSLP layer to the GIST layer via the API.
Well, this is correct. At least in theory. The GIST specification
lists this, but we have not yet implemented the stateless mode.
Christian Dickmann