A 6loRH for BitStrings
draft-thubert-6lo-bier-dispatch-03
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-07-24
|
|
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)
|
6lo P. Thubert, Ed.
Internet-Draft Cisco
Intended status: Standards Track Z. Brodard
Expires: January 25, 2018 Ecole Polytechnique
H. Jiang
G. Texier
Telecom Bretagne
July 24, 2017
A 6loRH for BitStrings
draft-thubert-6lo-bier-dispatch-03
Abstract
This specification extends the 6LoWPAN Routing Header to signal
BitStrings such as utilized in Bit Index Explicit Replication and its
Traffic Engineering variant.
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 January 25, 2018.
Copyright Notice
Copyright (c) 2017 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
(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
Thubert, et al. Expires January 25, 2018 [Page 1]
Internet-Draft A 6loRH for BitStrings July 2017
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. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 3
4. The BIER-6LoRH encoding . . . . . . . . . . . . . . . . . . . 4
4.1. The Bit-by-bit BitStrings . . . . . . . . . . . . . . . . 4
4.2. Bloom Filters . . . . . . . . . . . . . . . . . . . . . . 5
4.3. Types of BIER-6LoRH header . . . . . . . . . . . . . . . 5
5. Implementation Status . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
The type of information that needs to be present in a packet inside
the LLN but not outside of the LLN varies with the routing operation,
but there is overall a need for an extensible compression technique
that would simplify the IP-in-IP encapsulation, when needed, and
optimally compress existing routing artifacts found in LLNs.
The 6LoWPAN Routing Header (6LoRH) [RFC8025] [RFC8138] is such a
technique, that extends the 6lo adaptation layer framework [RFC4944],
[RFC6282] so as to carry routing information for Route-over use
cases. The original specification includes the formats necessary for
RPL such as the Source Route Header (SRH) and is intended to be
extended for additional routing artifacts.
The Bit Index Explicit Replication (BIER), as introduced in the BIER
Architecture [I-D.ietf-bier-architecture], can be used as an
alternate artifact to route multicast as well as unicast traffic.
The Traffic Engineering for Bit Index Explicit Replication
[I-D.eckert-bier-te-arch] (BIER-TE) adds support for traffic
engineering by explicit hop-by-hop forwarding and loose hop
forwarding of packets along a unicast route.
This specification provides additional formats for the 6LoRH
Show full document text