Hi Jose,

when writing the draft we consulted one of the authors of 15.4e about the
same issue. His answer said that the original intent when the spec was
drafted was that the termination IE was only required when a header IE was
followed by something. The problem is, if we get a frame with no header IE,
how do we know what follows is a payload IE, or it is just payload that
looks like a payload IE? In 15.4, where any frame could come at any time,
we need a header terminator to tell us how to parse the rest of the packet.

so that is the reason for having it there. Any thoughts?

regards,
Xavi

2015-06-16 16:56 GMT+02:00 Thomas Watteyne <[email protected]>:

> Jose,
>
> I believe you need to add a header termination IE before sending a payload
> IE. This was pointed out during our recent discussion; I'll let the authors
> confirm.
>
> The specs for the plugtest have been distributed on the plugtest ML,
> please contact me offline if you didn't receive them.
>
> Thomas
>
> On Tue, Jun 16, 2015 at 9:18 AM, José Ángel Miranda <[email protected]>
> wrote:
>
>> Hi,
>>
>> Looking at the new minimal conf (07- 08 - 09), we have observed in the
>> IEs example with and without security that a termination Header IE,
>> indicating Payload IE coming next, is added. We would like to know where,
>> within the standard, this is described, or if you have taken this
>> configuration due to any specific reason. Actually, there is no need to add
>> the termination Header IE, as within the Payload IE you can easily
>> distinguish the type in the outer IE descriptor.
>> It would be nice to know if this configuration will be required for the
>> plugtest 17 - 18 Jul.
>>
>> Another question related to the test specification document for the this
>> plugtest, have you already released this document ? and in that case, where
>> can we find it?
>>
>> Cheers,
>> Jose.
>>
>> _______________________________________________
>> 6tisch mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/6tisch
>>
>>
>
> _______________________________________________
> 6tisch mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/6tisch
>
>
_______________________________________________
6tisch mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6tisch

Reply via email to