OAM for LPWAN using Static Context Header Compression (SCHC)
draft-barthel-lpwan-oam-schc-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Dominique Barthel , Laurent Toutain , Arunprabhu Kandasamy , Diego Dujovne , Juan-Carlos Zúñiga | ||
| Last updated | 2020-09-10 (latest revision 2020-03-09) | ||
| Replaces | draft-barthel-oam-schc | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-barthel-lpwan-oam-schc-01.txt
Abstract
With IP protocols now generalizing to constrained networks, users expect to be able to Operate, Administer and Maintain them with the familiar tools and protocols they already use on less constrained networks. OAM uses specific messages sent into the data plane to measure some parameters of a network. Most of the time, no explicit values are sent is these messages. Network parameters are obtained from the analysis of these specific messages. This can be used: o To detect if a host is up or down. o To measure the RTT and its variation over time. o To learn the path used by packets to reach a destination. OAM in LPWAN is a little bit trickier since the bandwidth is limited and extra traffic added by OAM can introduce perturbation on regular transmission. Two scenarios can be investigated: o OAM coming from internet. In that case, the NGW should act as a
Authors
Dominique Barthel
(dominique.barthel@orange.com)
Laurent Toutain
(laurent.toutain@imt-atlantique.fr)
Arunprabhu Kandasamy
(arun@ackl.io)
Diego Dujovne
(diego.dujovne@mail.udp.cl)
Juan-Carlos Zúñiga
(juancarlos.zuniga@sigfox.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)