Subject: Second Byte of TPKT should be zero

From: "Rosen, Brian" <[email-masked]>
Date: Wed, 21 Feb 2001 19:12:54 -0500

Implementations should be setting the second byte of TPKT to zero.  
This is listed as "reserved" in the RFC, but many subsequent uses, 
including H.323 specify that it should be zero.  In the spirit of 
strict in what you send, lenient in what you accept, I suggest that 
you set it to zero, but ignore it on reception.

This came up before, but happened again here.

Brian