This page (revision-10) was last changed on 29-Nov-2024 16:16 by Administrator

This page was created on 29-Nov-2024 16:16 by -jim

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
10 29-Nov-2024 16:16 2 KB Administrator to previous
9 29-Nov-2024 16:16 2 KB -jim to previous | to last
8 29-Nov-2024 16:16 2 KB -jim to previous | to last
7 29-Nov-2024 16:16 2 KB -jim to previous | to last
6 29-Nov-2024 16:16 2 KB -jim to previous | to last
5 29-Nov-2024 16:16 1 KB -jim to previous | to last
4 29-Nov-2024 16:16 1 KB -jim to previous | to last
3 29-Nov-2024 16:16 826 bytes -jim to previous | to last
2 29-Nov-2024 16:16 808 bytes -jim to previous | to last
1 29-Nov-2024 16:16 176 bytes -jim to last

Page References

Incoming links Outgoing links
Thread network layer
Thread network layer

Version management

Difference between version and

At line 7 added 2 lines
[{$pagename}] (or really [6LoWPAN]) is based on the use of a connecting [router], called an edge [router]. [{$pagename}] calls their edge routers Border [Routers]. Unlike other proprietary networks, [6LoWPAN], like any network with edge routers, does not maintain any [Application Layer] [state], because such networks forward [datagrams] at the [Network Layer]. This means that [6LoWPAN] remains unaware of [Application Layer] [protocols] and changes. This lowers the processing [power] burden on edge [routers]. It also means that Thread does not need to maintain an [Application Layer]. [{$pagename}] states that multiple [Application Layers] can be supported, as long as they are low-bandwidth and are able to operate over IPv6
This page (revision-10) was last changed on 29-Nov-2024 16:16 by AdministratorTop