Pass chrome version and channel in CHLO message to server.

net/quic/crypto/crypto_protocol.h

Index: net/quic/crypto/crypto_protocol.h
diff --git a/net/quic/crypto/crypto_protocol.h b/net/quic/crypto/crypto_protocol.h
index 49194e90b3d71dfb6c2b2142953028ae446d89d2..255184d6f0baa004593d520d3a198c319ae9b6b8 100644
--- a/net/quic/crypto/crypto_protocol.h
+++ b/net/quic/crypto/crypto_protocol.h
@@ -93,6 +93,8 @@ const QuicTag kCCRT = TAG('C', 'C', 'R', 'T');  // Cached certificate
 const QuicTag kEXPY = TAG('E', 'X', 'P', 'Y');  // Expiry
 const QuicTag kIFCW = TAG('I', 'F', 'C', 'W');  // Initial flow control receive
                                                 // window.
+const QuicTag kCVER = TAG('C', 'V', 'E', 'R');  // Client Version.

[Ryan Hamilton, 2014/06/04 22:31:15]

Heh, we used to have a CVER tag in an earlier version of the version negotiation
spec :>

That being said, I'm not in love with "VER" as part of this tag name, but I'm
not really sure why. I wonder if we should have something like Client
Description (CDSC) because it's more of a description than a version, or it will
be once more than one browser supports QUIC. You could almost use User Agent
(UA) though that might suggest that the *full* UA string, which we don't want.

Anyway, minor point. 

[jar (doing other things), 2014/06/05 02:16:23]

As a matter of course... for these "less important" items, and most critically,
for items that don't vary from CHLO to CHLO, it is nice to have alphabetically
large initial letters, to best ensure the tags will be late in the tag listing.

Perhaps a nice unification (avoding a previously used tag??) would be:

User Agent Chrome Version
UACV

Other suggestions?  
YMMV (which is not a suggestion ;-) )

[ramant (doing other things), 2014/06/05 02:51:55]

Used kCDSC.
Done.

[ramant (doing other things), 2014/06/05 02:51:55]

Changed CDSC to UACV
Done.

+
 
 // Server hello tags
 const QuicTag kCADR = TAG('C', 'A', 'D', 'R');  // Client IP address and port