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

Internet Protocol, Version 6 (IPv6) Specification

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
181
0
21

Year Published

2019
2019
2019
2019

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 487 publications
(202 citation statements)
references
References 11 publications
0
181
0
21
Order By: Relevance
“…The IETF specified the 6LoWPAN protocol [4] to allow for transmissions of IPv6 packets over IEEE 802.15.4 [3] networks-a widely used link layer technology in the IoT. While IPv6 requires a Maximum Transmission Unit (MTU) of at least 1280 bytes [2], IEEE 802.15.4 is only able to handle link layer packets of up to 127 bytes-including the link layer header-which in the worst case only leaves 33 bytes for application data [8]. To enable IPv6 communication in such a restrictive environment, 6LoWPAN provides both header compression [9], [10] and datagram fragmentation [4].…”
Section: Problem Statement and Related Workmentioning
confidence: 99%
See 3 more Smart Citations
“…The IETF specified the 6LoWPAN protocol [4] to allow for transmissions of IPv6 packets over IEEE 802.15.4 [3] networks-a widely used link layer technology in the IoT. While IPv6 requires a Maximum Transmission Unit (MTU) of at least 1280 bytes [2], IEEE 802.15.4 is only able to handle link layer packets of up to 127 bytes-including the link layer header-which in the worst case only leaves 33 bytes for application data [8]. To enable IPv6 communication in such a restrictive environment, 6LoWPAN provides both header compression [9], [10] and datagram fragmentation [4].…”
Section: Problem Statement and Related Workmentioning
confidence: 99%
“…The naive approach to handle fragmented datagrams in a multihop network is hop-wise reassembly (HWR) [2], [4]. In HWR, each intermediate hop between source and destination assembles and re-fragments the original datagram completely.…”
Section: B Fragment Forwarding For Low-power Lossy Networkmentioning
confidence: 99%
See 2 more Smart Citations
“…Due to the restrictions imposed by the LLN devices and their underlying technologies, initially the Internet Protocol version 6 (IPv6) [34] was considered to be too resource intensive for such constrained devices [35]. Alternative proprietary solutions tended to implement complex application gateways to translate the non-IP format, understood by such networks, to the IP world [36].…”
Section: ) 6lowpan (Layer 25)mentioning
confidence: 99%