[dcc2] Final connection negotiation changes (WAS: Is DCC2 Dead?)

[codemastr]

> I think we are pretty much near the end of the drafting for the connection 
> negotiation.  I am just waiting to hear back about the final notes i sent 
> out.
>
> http://six.pairlist.net/pipermail/dcc2/2004-September/000274.html

Ok then...

> Are we in agreement on adding a message id in addition to the session id?
I think so, it seems this is necessary.

> should the IRCFile and IRCChat application tokens be placed in the 
> connection negotiation draft or in a new supplemental
I think it is best of all the tokens are described in a draft separate from 
the connection negotiation.

> Third, some tokens used in the connection process will usually have the 
> same value.  Can we give some tokens default values and assign the default 
> unless otherwise specified?
I think this would be fine. Yeah, default values can hurt readability, but 
we do have the 512 limit to take into account. My question is though, which 
tokens are you referring to? The only one I can think of is Network=. 
However, making this a default value is tricky. Today, Network=IPv4 is going 
to be 99% of all DCC2 connections. However, 5 years from now, it will most 
likely be Network=IPv6. Meaning, if we default to v4 now, we're only saving 
bandwidth until v6 catches on, and if we default to v6, we're not saving 
bandwidth until v6 catches on, it's a Catch 22. So I guess it is useful to 
know which tokens you are considering to give a default value before we 
decide.

-- codemastr