Asymmetric AODV-P2P-RPL in Low-Power and Lossy Networks (LLNs)
draft-ietf-roll-aodv-rpl-04
ROLL S. Anamalamudi
Internet-Draft SRM University-AP
Intended status: Standards Track M. Zhang
Expires: January 3, 2019 Huawei Technologies
AR. Sangi
Huaiyin Institute of Technology
C. Perkins
Futurewei
S.V.R.Anand
Indian Institute of Science
B. Liu
Huawei Technologies
July 2, 2018
Asymmetric AODV-P2P-RPL in Low-Power and Lossy Networks (LLNs)
draft-ietf-roll-aodv-rpl-04
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 both hop-by-hop routing and source
routing: Ad Hoc On-demand Distance Vector Routing (AODV) based RPL
protocol. Paired 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 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 January 3, 2019.
Anamalamudi, et al. Expires January 3, 2019 [Page 1]
Internet-Draft AODV-RPL July 2018
Copyright Notice
Copyright (c) 2018 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Overview of AODV-RPL . . . . . . . . . . . . . . . . . . . . 6
4. AODV-RPL DIO Options . . . . . . . . . . . . . . . . . . . . 7
4.1. AODV-RPL DIO RREQ Option . . . . . . . . . . . . . . . . 7
4.2. AODV-RPL DIO RREP Option . . . . . . . . . . . . . . . . 9
4.3. AODV-RPL DIO Target Option . . . . . . . . . . . . . . . 10
5. Symmetric and Asymmetric Routes . . . . . . . . . . . . . . . 11
6. AODV-RPL Operation . . . . . . . . . . . . . . . . . . . . . 13
6.1. Route Request Generation . . . . . . . . . . . . . . . . 13
6.2. Receiving and Forwarding RREQ messages . . . . . . . . . 14
6.2.1. General Processing . . . . . . . . . . . . . . . . . 14
6.2.2. Additional Processing for Multiple Targets . . . . . 15
6.3. Generating Route Reply (RREP) at TargNode . . . . . . . . 16
6.3.1. RREP-DIO for Symmetric route . . . . . . . . . . . . 16
6.3.2. RREP-DIO for Asymmetric Route . . . . . . . . . . . . 16
6.3.3. RPLInstanceID Pairing . . . . . . . . . . . . . . . . 16
6.4. Receiving and Forwarding Route Reply . . . . . . . . . . 17
7. Gratuitous RREP . . . . . . . . . . . . . . . . . . . . . . . 18
8. Operation of Trickle Timer . . . . . . . . . . . . . . . . . 19
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
9.1. New Mode of Operation: AODV-RPL . . . . . . . . . . . . . 19
9.2. AODV-RPL Options: RREQ, RREP, and Target . . . . . . . . 19
10. Security Considerations . . . . . . . . . . . . . . . . . . . 20
Show full document text