On Feb 13, 2012, at 12:58 PM, mike wakerly wrote:
> No problem. Let's go with more condensed version of my example:
> struct llcp_phdr {
>guint8 adapter; /* Adapter number, typically 0. */
>guint8 flags;/* Direction flag (TX/RX) and future use. */
> };
>
> The least significant b
On Mon, Feb 13, 2012 at 12:58 PM, mike wakerly wrote:
> [sorry for the broken threading, I was not previously subscribed.]
>
> On Thu, Feb 9, 2012 at 6:36 AM, Guy Harris wrote:
>> On Feb 8, 2012, at 3:26 AM, mike wakerly wrote:
>>> Hosts need to record frame directionality in addition to
>>> raw
[sorry for the broken threading, I was not previously subscribed.]
On Thu, Feb 9, 2012 at 6:36 AM, Guy Harris wrote:
> On Feb 8, 2012, at 3:26 AM, mike wakerly wrote:
>> Hosts need to record frame directionality in addition to
>> raw frame data. As an example, a psuedo-header prepended to
>> ind
On Feb 8, 2012, at 3:26 AM, mike wakerly wrote:
> I'd like to request a new encapsulation type for NFC Logical Link
> Control Protocol (LLCP) [1].
...
> A new encapsulation type is needed for reasons similar to i2c and
> bluetooth.
No, it's needed because no existing link-layer header
Hi there!
I'd like to request a new encapsulation type for NFC Logical Link
Control Protocol (LLCP) [1].
LLCP is a layer 2 protocol for near-field communication (NFC) devices.
It is used in Android [2] (among other platforms), and there are a
few usermode implementations ([3], [4]) for various h
