Re: Proposal: make init optional

Another area that would have to be reworked in the standard is the
state tables. The state tables define what is and is not legal at
various points in the conversation. We use the state tables to work
out what responses we are allowed to send. It might not be that hard
to update the state tables - maybe say "any of these packets in the
init state immediately jumps to the connected state" or whatever.
But it should be worked out.

>  - services: this actually always bothered me.  
>       What does a server do now with a client that ignores
>       the option bits? Oh yes - if good OSI targets they shut down cause
>       it is a "bad" client.

Our clients use ther services returned by the server to make sure we
don't send packets that the server does not want to receive. So the
client can adapt dynamically.

>  - protocol version: actually this is interesting.  But so far I don't think
>      we use it? That is, PDUs aren't laid out differently in the different
>      versions - they just have new features added...

Again, we make our clients adapt dynamically.

But I guess you are arguing that if clients want to use init they can,
but if they don't, then they can except whatever comes their way.
(So if the client wants to adapt dynamically, it should send an init?)

ajk

Received on Monday, 8 January 2001 18:29:19 UTC