| Re: Reserved bits and fields | <– Date –> <– Thread –> |
|
From: Bob O'Hara (boohara) (boohara |
|
| Date: Tue, 15 Aug 2006 11:22:09 -0700 (PDT) | |
Not really, remember the receiver of an implementation that is unaware of the use of the reserved field to fix a bug in the protocol will still ignore it (and still suffer from the hypothetical bug in the protocol). -Bob -----Original Message----- From: Nelson, David [mailto:dnelson [at] enterasys.com] Sent: Tuesday, August 15, 2006 11:01 AM To: capwap [at] frascone.com Subject: Re: [Capwap] Reserved bits and fields Bob O'Hara writes... > Without the transmitter requirement, small > protocol problems found only after wide deployment > might be able to be fixed by using a previously > reserved bit or field. Without revising the protocol version number? Without revising the specification? Seems pretty hazardous to interoperability, IMHO. Regards, Dave _________________________________________________________________ To unsubscribe or modify your subscription options, please visit: http://lists.frascone.com/mailman/listinfo/capwap Archives: http://lists.frascone.com/pipermail/capwap
-
Reserved bits and fields Bob O'Hara (boohara), August 14 2006
- Re: Reserved bits and fields Scott G Kelly, August 15 2006
- Re: Reserved bits and fields Bob O'Hara (boohara), August 15 2006
- Re: Reserved bits and fields Nelson, David, August 15 2006
- Re: Reserved bits and fields Bob O'Hara (boohara), August 15 2006
- Re: Reserved bits and fields Nelson, David, August 15 2006
- Re: Reserved bits and fields Pat Calhoun (pacalhou), August 28 2006
- Re: Reserved bits and fields Bob O'Hara (boohara), August 28 2006
- Re: Reserved bits and fields Pat Calhoun (pacalhou), August 28 2006
Results generated by Tiger Technologies using MHonArc.