2017
DOI: 10.17487/rfc8137
|View full text |Cite
|
Sign up to set email alerts
|

IEEE 802.15.4 Information Element for the IETF

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
10
0
1

Year Published

2019
2019
2023
2023

Publication Types

Select...
4
1

Relationship

0
5

Authors

Journals

citations
Cited by 14 publications
(12 citation statements)
references
References 1 publication
0
10
0
1
Order By: Relevance
“…As it is presented in Figure 4, the general 802.15.4 MAC frame format defines IEs to be between the end of the MAC Header and the Frame Payload. The IEs are structured containers as Type, Length, Value fields (TLV) and they have two types, named Header IEs and Payload IEs [32]. Header IEs are the part of the MAC header and according to [32], most of their processing is done by the MAC and IETF protocols should not have any direct effect on that processing.…”
Section: B Int Information Elementsmentioning
confidence: 99%
See 3 more Smart Citations
“…As it is presented in Figure 4, the general 802.15.4 MAC frame format defines IEs to be between the end of the MAC Header and the Frame Payload. The IEs are structured containers as Type, Length, Value fields (TLV) and they have two types, named Header IEs and Payload IEs [32]. Header IEs are the part of the MAC header and according to [32], most of their processing is done by the MAC and IETF protocols should not have any direct effect on that processing.…”
Section: B Int Information Elementsmentioning
confidence: 99%
“…The IEs are structured containers as Type, Length, Value fields (TLV) and they have two types, named Header IEs and Payload IEs [32]. Header IEs are the part of the MAC header and according to [32], most of their processing is done by the MAC and IETF protocols should not have any direct effect on that processing. On the other side, Payload IEs are the part of the MAC payload and they may be encrypted and authenticated.…”
Section: B Int Information Elementsmentioning
confidence: 99%
See 2 more Smart Citations
“…This decision is left to the particular Scheduling Function. [25], and defines how 6P content is encapsulated within. The development of this IE container for the IETF was triggered by the 6TiSCH WG and is a proof of the close liaison between the IETF and the IEEE.…”
Section: A 6top Protocol (6p)mentioning
confidence: 99%