Exploiting Packet Replication and Elimination in Complex Tracks in LLNs
draft-papadopoulos-paw-pre-reqs-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-01-28
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
PAW G. Papadopoulos, Ed.
Internet-Draft N. Montavont
Intended status: Standards Track IMT Atlantique
Expires: August 1, 2019 P. Thubert
Cisco
January 28, 2019
Exploiting Packet Replication and Elimination in Complex Tracks in LLNs
draft-papadopoulos-paw-pre-reqs-00
Abstract
Packet Replication and Elimination mechanism consists in duplicating
data packets into several paths in the network to increase
reliability and provide low jitter. Over a wireless medium, this
technique can take advantage of communication overhearing, when
parallel transmissions over two adjacent paths are scheduled. This
document presents the concept and details the required changes to the
current specifications that will be necessary to enable this.
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 August 1, 2019.
Copyright Notice
Copyright (c) 2019 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
Papadopoulos, et al. Expires August 1, 2019 [Page 1]
Internet-Draft PRE Requirements in PAW January 2019
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Tracks . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Tracks Overview . . . . . . . . . . . . . . . . . . . . . 3
3.2. Complex Tracks . . . . . . . . . . . . . . . . . . . . . 3
4. Packet Replication and Elimination principles . . . . . . . . 3
4.1. Packet Replication . . . . . . . . . . . . . . . . . . . 4
4.2. Packet Elimination . . . . . . . . . . . . . . . . . . . 5
4.3. Promiscuous Overhearing . . . . . . . . . . . . . . . . . 5
5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Requirements Related to Alternative Parent Selection . . 5
5.2. Requirements Related to Propagated Information . . . . . 6
5.3. Requirements Related to Cell Reservation . . . . . . . . 7
5.4. Requirements Related to Cells without ACKs . . . . . . . 8
5.5. Requirements Related to Packet Elimination . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Informative references . . . . . . . . . . . . . . . . . 9
8.2. Other Informative References . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
This draft describes industrial use cases which require deterministic
flows over wireless multi-hop paths.
The PAW use cases explicitly do not propose or suggest any specific
solution or design for PAW architecture or protocols. These are
subjects of other PAW drafts. The PAW use cases are not considered
as concrete requirements by the PAW Working Group.
The industrial use cases covered in this draft are professional
audio, wireless for industrial applications and amusement parks.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Papadopoulos, et al. Expires August 1, 2019 [Page 2]
Show full document text