OAM for LPWAN using Static Context Header Compression (SCHC)
draft-barthel-lpwan-oam-schc-02
lpwan Working Group D. Barthel
Internet-Draft Orange SA
Intended status: Informational L. Toutain
Expires: 6 May 2021 IMT Atlantique
A. Kandasamy
Acklio
D. Dujovne
Universidad Diego Portales
JC. Zuniga
SIGFOX
2 November 2020
OAM for LPWAN using Static Context Header Compression (SCHC)
draft-barthel-lpwan-oam-schc-02
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:
* To detect if a host is up or down.
* To measure the RTT and its variation over time.
* 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:
* OAM coming from internet. In that case, the NGW should act as a
proxy and handle specifically the OAM traffic.
* OAM coming from LPWAN devices: This can be included into regular
devices but some specific devices may be installed in the LPWAN
network to measure its quality.
Barthel, et al. Expires 6 May 2021 [Page 1]
Internet-Draft SCHC OAM for LPWAN November 2020
The primitive functionalities of OAM are achieved with the ICMPv6
protocol.
ICMPv6 defines messages that inform the source of IPv6 packets of
errors during packet delivery. It also defines the Echo Request/
Reply messages that are used for basic network troubleshooting (ping
command). ICMPv6 messages are transported on IPv6.
This document describes how basic OAM is performed on Low Power Wide
Area Networks (LPWANs) by compressing ICMPv6/IPv6 headers and by
protecting the LPWAN network and the Device from undesirable ICMPv6
traffic.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 6 May 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Barthel, et al. Expires 6 May 2021 [Page 2]
Internet-Draft SCHC OAM for LPWAN November 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Detailed behavior . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Device does a ping . . . . . . . . . . . . . . . . . . . 4
4.1.1. Rule example . . . . . . . . . . . . . . . . . . . . 6
4.2. Device is ping'ed . . . . . . . . . . . . . . . . . . . . 6
4.2.1. Rule example . . . . . . . . . . . . . . . . . . . . 7
4.3. Device is the source of an ICMPv6 error message . . . . . 7
Show full document text