Capwap Mailing List: Re: Issue 209: Dealing with Reserved Bits

[Bob O'Hara (boohara) (boohara]

Pat,  

This is good, as far as it goes.  There are many more reserved fields in
the message elements.

 -Bob
 
-----Original Message-----
From: Pat Calhoun (pacalhou) 
Sent: Thursday, August 31, 2006 6:39 AM
To: capwap [at] frascone.com
Subject: [Capwap] Issue 209: Dealing with Reserved Bits

Here is the proposed new text:

4.1.  CAPWAP Transport Header
[...]
   Flags:  A set of reserved bits for future flags in the CAPWAP header.
      All implementations complying with version zero of this protocol
      MUST set these bits to zero.  Receivers MUST ignore all bits not
      defined for the version of the protocol they support
[...]
   Reserved:  The 3-bit Reserved field is reserved and set to 0 in this
      version of the CAPWAP protocol.  Receivers MUST ignore all bits
      not defined for the version of the protocol they support 
 
Comments?

Pat Calhoun
CTO, Wireless Networking Business Unit
Cisco Systems
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap