Another way to address this (if the request and
response Id is one octet long) the request using
the first 7 bits (form 0.. bit 6)
and use bit 7 only for response... I mean set the
most significant bit 1 when is a response ID....
Bad example:
request: 0x00
response 0x80
This expands the number of request and response to
use. Also, same criteria applies to a 16bit
request/response ID.
P.S. Also, this is just a thought..
-- Masaru
On 10/13/2010 5:36 AM, Carsten Bormann wrote:
One usual way of handling this is to split the code space in half, i.e. using 0
to 127 for requests and 128 to 255 for response statuses. Obviously, we don't
need request codes yet -- but maybe we can use the opportunity to get rid of
the strange language about using the size of the message to distinguish
different kinds of requests.
Just a thought (and no WG chair hats involved).
Gruesse, Carsten
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
---
avast! Antivirus: Inbound message clean.
Virus Database (VPS): 101013-0, 10/13/2010
Tested on: 10/13/2010 9:16:40 AM
avast! - copyright (c) 1988-2010 AVAST Software.
http://www.avast.com
--
Ubilogix S.A. de R.L.
Avenida Obregon #110-4
Zona Centro. C.P. 22800
Ensenada B.C. México
[email protected]
---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 101013-0, 10/13/2010
Tested on: 10/13/2010 10:08:17 AM
avast! - copyright (c) 1988-2010 AVAST Software.
http://www.avast.com
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
