When to use RFC 6553, 6554 and IPv6-in-IPv6
draft-ietf-roll-useofrplinfo-23
|
| Document |
Type |
|
Active Internet-Draft (roll WG)
|
|
Last updated |
|
2018-05-01
|
|
Replaces |
|
draft-robles-roll-useofrplinfo
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Peter Van der Stok
|
|
Shepherd write-up |
|
Show
(last changed 2018-02-07)
|
| IESG |
IESG state |
|
AD Evaluation::AD Followup
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alvaro Retana
|
|
Send notices to |
|
Peter Van der Stok <consultancy@vanderstok.org>
|
ROLL Working Group M. Robles
Internet-Draft Ericsson
Updates: 6553, 6550, 8138 (if approved) M. Richardson
Intended status: Standards Track SSW
Expires: November 2, 2018 P. Thubert
Cisco
May 1, 2018
When to use RFC 6553, 6554 and IPv6-in-IPv6
draft-ietf-roll-useofrplinfo-23
Abstract
This document looks at different data flows through LLN (Low-Power
and Lossy Networks) where RPL (IPv6 Routing Protocol for Low-Power
and Lossy Networks) is used to establish routing. The document
enumerates the cases where RFC 6553, RFC 6554 and IPv6-in-IPv6
encapsulation is required. This analysis provides the basis on which
to design efficient compression of these headers. This document
updates RFC 6553 adding a change to the RPL Option Type.
Additionally, this document updates RFC 6550 to indicate about this
change and updates RFC8138 as well to consider the new Option Type
when RPL Option is decompressed.
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 November 2, 2018.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
Robles, et al. Expires November 2, 2018 [Page 1]
Internet-Draft Useof6553 May 2018
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 and Requirements Language . . . . . . . . . . . . 4
2.1. hop-by-hop IPv6-in-IPv6 headers . . . . . . . . . . . . . 5
3. Updates to RFC6553, RFC6550 and RFC 8138 . . . . . . . . . . 5
3.1. Updates to RFC 6553 . . . . . . . . . . . . . . . . . . . 5
3.2. Updates to RFC 8138 . . . . . . . . . . . . . . . . . . . 7
3.3. Updates to RFC 6550: Indicating the new RPI in the DODAG
Configuration Option Flag. . . . . . . . . . . . . . . . 7
4. Sample/reference topology . . . . . . . . . . . . . . . . . . 8
5. Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6. Storing mode . . . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Storing Mode: Interaction between Leaf and Root . . . . . 14
6.1.1. SM: Example of Flow from RPL-aware-leaf to root . . . 15
6.1.2. SM: Example of Flow from root to RPL-aware-leaf . . . 16
6.1.3. SM: Example of Flow from root to not-RPL-aware-leaf . 16
6.1.4. SM: Example of Flow from not-RPL-aware-leaf to root . 17
6.2. Storing Mode: Interaction between Leaf and Internet . . . 18
6.2.1. SM: Example of Flow from RPL-aware-leaf to Internet . 18
6.2.2. SM: Example of Flow from Internet to RPL-aware-leaf . 18
6.2.3. SM: Example of Flow from not-RPL-aware-leaf to
Internet . . . . . . . . . . . . . . . . . . . . . . 19
6.2.4. SM: Example of Flow from Internet to non-RPL-aware-
leaf . . . . . . . . . . . . . . . . . . . . . . . . 20
6.3. Storing Mode: Interaction between Leaf and Leaf . . . . . 21
6.3.1. SM: Example of Flow from RPL-aware-leaf to RPL-aware-
leaf . . . . . . . . . . . . . . . . . . . . . . . . 21
6.3.2. SM: Example of Flow from RPL-aware-leaf to non-RPL-
aware-leaf . . . . . . . . . . . . . . . . . . . . . 22
6.3.3. SM: Example of Flow from not-RPL-aware-leaf to RPL-
aware-leaf . . . . . . . . . . . . . . . . . . . . . 23
Show full document text