Network Connection Object TCP Extension

["Jordan, Bret" <bret.jordan@bluecoat.com>]

Given that the 90-95+% use case for the network connection object will be TCP and UDP, the src/dst port information was moved to the base object instead of having a UDP extension and a TCP extension.  However, when this was done two fields were left in the new somewhat errant TCP extension. Namely the src/dst "flags"

I would propose that it does not make sense to have this TCP extension with just 2 properties that are flags, when the port information was merged down to the base object.  

So I see two proposals to this issue:

1) We also merge down the TCP flags and leave them as optional, similarly to what we did with the port information. 

2) We rename the TCP Extension to be TCP/UDP Extension and put the port information back in it.  

Thanks,

Bret

Bret Jordan CISSP

Director of Security Architecture and Standards | Office of the CTO

Blue Coat Systems

PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050

"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg." 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail