Asymmetric AODV-P2P-RPL in Low-Power and Lossy Networks (LLNs)
draft-ietf-roll-aodv-rpl-01
ROLL S. Anamalamudi
Internet-Draft Huaiyin Institute of Technology
Intended status: Standards Track M. Zhang
Expires: September 13, 2017 AR. Sangi
Huawei Technologies
C. Perkins
Futurewei
S.V.R.Anand
Indian Institute of Science
March 12, 2017
Asymmetric AODV-P2P-RPL in Low-Power and Lossy Networks (LLNs)
draft-ietf-roll-aodv-rpl-01
Abstract
Route discovery for symmetric and asymmetric Point-to-Point (P2P)
traffic flows is a desirable feature in Low power and Lossy Networks
(LLNs). For that purpose, this document specifies a reactive P2P
route discovery mechanism for hop-by-hop routing (storing mode) based
on Ad Hoc On-demand Distance Vector Routing (AODV) based RPL
protocol. Two separate Instances are used to construct directional
paths in case some of the links between source and target node are
asymmetric.
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 http://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 September 13, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
Anamalamudi, et al. Expires September 13, 2017 [Page 1]
Internet-Draft draft-ietf-ROLL-AODV-RPL March 2017
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Overview of AODV-RPL . . . . . . . . . . . . . . . . . . . . 5
4. AODV-RPL Mode of Operation (MoP) . . . . . . . . . . . . . . 5
5. RREQ Message . . . . . . . . . . . . . . . . . . . . . . . . 8
6. RREP Message . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Gratuitous RREP . . . . . . . . . . . . . . . . . . . . . . . 11
8. Operation of Trickle Timer . . . . . . . . . . . . . . . . . 12
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
9.1. New Mode of Operation: AODV-RPL . . . . . . . . . . . . . 12
9.2. AODV-RPL Options: RREQ and RREP . . . . . . . . . . . . . 12
10. Security Considerations . . . . . . . . . . . . . . . . . . . 12
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
11.1. Normative References . . . . . . . . . . . . . . . . . . 13
11.2. Informative References . . . . . . . . . . . . . . . . . 14
Appendix A. ETX/RSSI Values to select S bit . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
RPL[RFC6550], the IPv6 distance vector routing protocol for Low-power
and Lossy Networks (LLNs), is designed to support multiple traffic
flows through a root-based Destination-Oriented Directed Acyclic
Graph (DODAG). For traffic flows between routers within the DODAG
(i.e., Point-to-Point (P2P) traffic), this means that data packets
either have to traverse the root in non-storing mode (source
routing), or traverse a common ancestor in storing mode (hop-by-hop
routing). Such P2P traffic is thereby likely to flow along sub-
optimal routes and may suffer severe traffic congestion near the DAG
Show full document text