idnits 2.17.1 draft-bormann-6lo-rpl-mesh-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (August 01, 2014) is 3556 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-05) exists of draft-thubert-6man-flow-label-for-rpl-03 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 6lo working group C. Bormann 3 Internet-Draft Universitaet Bremen TZI 4 Intended status: Standards Track August 01, 2014 5 Expires: February 2, 2015 7 RPL Mesh Header 8 draft-bormann-6lo-rpl-mesh-00 10 Abstract 12 This short draft provides a straw man for the RPL Mesh Header. 14 Status of This Memo 16 This Internet-Draft is submitted in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF). Note that other groups may also distribute 21 working documents as Internet-Drafts. The list of current Internet- 22 Drafts is at http://datatracker.ietf.org/drafts/current/. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 This Internet-Draft will expire on February 2, 2015. 31 Copyright Notice 33 Copyright (c) 2014 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (http://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with respect 41 to this document. Code Components extracted from this document must 42 include Simplified BSD License text as described in Section 4.e of 43 the Trust Legal Provisions and are provided without warranty as 44 described in the Simplified BSD License. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 49 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Idea . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 51 3. IANA considerations . . . . . . . . . . . . . . . . . . . . . 3 52 4. Security considerations . . . . . . . . . . . . . . . . . . . 3 53 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 5.1. Normative References . . . . . . . . . . . . . . . . . . 4 55 5.2. Informative References . . . . . . . . . . . . . . . . . 4 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 58 1. Introduction 60 [I-D.thubert-6man-flow-label-for-rpl] defines a way to carry RPL 61 information in a flow label. The present draft shows how to carry 62 the same information in a RPL Mesh Header, in a slightly more 63 efficient way. 65 1.1. Terminology 67 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 68 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 69 document are to be interpreted as described in RFC 2119 [RFC2119]. 71 2. Idea 73 (Insert definitions from [I-D.thubert-6man-flow-label-for-rpl] here.) 75 Where [I-D.thubert-6man-flow-label-for-rpl] would carry the [RFC6553] 76 information in a flow label: 78 0 1 2 79 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 80 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 81 | |O|R|F| SenderRank | RPLInstanceID | 82 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 84 the RPL Mesh header carries it in a Mesh header, depending on whether 85 Rank and Inst both fit into 4 bits (S=0) or not (S=1): 87 1 2 3 88 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 89 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 90 |0 1 0 0 0 1|0|U| Rank | Inst | (continuation)... 91 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 93 1 2 3 94 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 95 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 96 |0 1 0 0 0 1|1|U| Rank | Inst | (continuation)... 97 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 99 Figure 1: RPL Mesh Header: Short and Long Version 101 The U bit controls whether an [RFC6282] IPHC dispatch follows (U=0, 102 Figure 2) or an [RFC4944] FRAG1 fragment header (U=1, Figure 3). In 103 both cases, the first three bits of the dispatch are replaced by the 104 O, R, and F bits from [I-D.thubert-6man-flow-label-for-rpl]. 106 0 1 107 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 108 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 109 | O | R | F | TF |NH | HLIM |CID|SAC| SAM | M |DAC| DAM | 110 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 112 Figure 2: continuation for U=0 114 1 2 3 115 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 |O R F 0 0| datagram_size | datagram_tag | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 120 Figure 3: continuation for U=1 122 3. IANA considerations 124 This draft requests IANA to assign the following four dispatch types 125 in the "IPv6 Low Power Personal Area Network Parameters" registry: 127 01 0001SU 129 4. Security considerations 131 The security considerations of [RFC4944], [RFC6282], and [RFC6553] 132 apply. 134 5. References 136 5.1. Normative References 138 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 139 Requirement Levels", BCP 14, RFC 2119, March 1997. 141 [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, 142 "Transmission of IPv6 Packets over IEEE 802.15.4 143 Networks", RFC 4944, September 2007. 145 [RFC6282] Hui, J. and P. Thubert, "Compression Format for IPv6 146 Datagrams over IEEE 802.15.4-Based Networks", RFC 6282, 147 September 2011. 149 [RFC6553] Hui, J. and JP. Vasseur, "The Routing Protocol for Low- 150 Power and Lossy Networks (RPL) Option for Carrying RPL 151 Information in Data-Plane Datagrams", RFC 6553, March 152 2012. 154 5.2. Informative References 156 [I-D.thubert-6man-flow-label-for-rpl] 157 Thubert, P., "The IPv6 Flow Label within a RPL domain", 158 draft-thubert-6man-flow-label-for-rpl-03 (work in 159 progress), May 2014. 161 Author's Address 163 Carsten Bormann 164 Universitaet Bremen TZI 165 Postfach 330440 166 Bremen D-28359 167 Germany 169 Phone: +49-421-218-63921 170 Email: cabo@tzi.org