idnits 2.17.1 draft-vanderstok-roll-admin-local-policy-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: ---------------------------------------------------------------------------- == It seems as if not all pages are separated by form feeds - found 0 form feeds but 8 pages 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 (February 14, 2014) is 3723 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC4007' is defined on line 285, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-ietf-6lo-lowpanz-02 == Outdated reference: A later version (-12) exists of draft-ietf-roll-trickle-mcast-06 == Outdated reference: A later version (-07) exists of draft-ietf-6man-multicast-scopes-02 == Outdated reference: A later version (-17) exists of draft-ietf-6lo-btle-00 -- Obsolete informational reference (is this intentional?): RFC 4601 (Obsoleted by RFC 7761) Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 roll P. van der Stok 3 Internet-Draft Consultant 4 Intended status: Informational February 14, 2014 5 Expires: August 18, 2014 7 MPL forwarder policy for multicast with admin-local scope 8 draft-vanderstok-roll-admin-local-policy-00 10 Abstract 12 The purpose of this document is to specify a policy for the routing 13 of mmulticast messages with admin-local scope. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on August 18, 2014. 32 Copyright Notice 34 Copyright (c) 2014 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 51 1.2. Required Reading . . . . . . . . . . . . . . . . . . . . 3 52 2. Network identifier . . . . . . . . . . . . . . . . . . . . . 3 53 2.1. IEEE 802.15.4 . . . . . . . . . . . . . . . . . . . . . . 3 54 2.2. IEEE 802.11 . . . . . . . . . . . . . . . . . . . . . . . 4 55 2.3. ITU-T G.9959 . . . . . . . . . . . . . . . . . . . . . . 4 56 2.4. BLUETOOTH Low Energy . . . . . . . . . . . . . . . . . . 4 57 3. Admin-Local policy . . . . . . . . . . . . . . . . . . . . . 4 58 3.1. Legal incoming packets . . . . . . . . . . . . . . . . . 4 59 3.2. Forwarding legal packets . . . . . . . . . . . . . . . . 5 60 3.2.1. Packet with MPL option . . . . . . . . . . . . . . . 5 61 3.2.2. Packet without MPL option . . . . . . . . . . . . . . 5 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 64 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 65 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 66 7.1. Normative References . . . . . . . . . . . . . . . . . . 6 67 7.2. Informative References . . . . . . . . . . . . . . . . . 8 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 70 1. Introduction 72 Multicast scopes are defined in [RFC4291]. The 73 [I-D.ietf-6man-multicast-scopes] extends the scope definition with 74 the text: 76 "Interface-Local, Link-Local, and Realm-Local scope boundaries are 77 automatically derived from physical connectivity or other, non- 78 multicast related configuration. Global scope has no boundary. The 79 boundaries of all other non-reserved scopes of Admin-Local or larger 80 are administratively configured." 82 The admin-local scope with value 4 must be administratively 83 configured. This draft shows how the policy that specifies the 84 admin-local scope can be automated. 86 Scope 3 multicast address is currently used by MPL to distribute the 87 multicast message to all receivers and forwarders within a mesh 88 network. The multicast distribution is limited to a mesh network 89 with a common layer-2. For example, the LoWPAN is defined by the 90 IEEE 802.15.4 layer-2 mesh network, composed of all connected nodes 91 sharing the same PANID [RFC4944]. 93 In current and projected deployments, the multicast message needs to 94 be distributed outside the single mesh over a multi-link network. 96 For example, distribution is wanted over two meshes with an edge 97 router each, where the two edge routers are connected with an 98 ethernet link. Another example of a multi-link network is: one edge 99 router with two interfaces where each interface is connected to a 100 different mesh. A message with a scope 4 multicast address can be 101 distributed over this multi-link networks. The boundary of the scope 102 4 is administratively configured. 104 The purpose of this document is to specify an automated policy for 105 the admin-local scope. This draft specifies conditions under which 106 multicast packets arriving over a given interface of a router are 107 forwarded over other interfaces of the same router. The concept of 108 mesh network is mapped to various lowpan networks. 110 1.1. Terminology 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 114 document are to be interpreted as described in [RFC2119]. 116 Additionally, this document uses terminology 117 [I-D.ietf-roll-trickle-mcast]. 119 1.2. Required Reading 121 Admin-local multicast scope is defined in 122 [I-D.ietf-6man-multicast-scopes]. MPL is described in 123 [I-D.ietf-roll-trickle-mcast] 125 2. Network identifier 127 Links have the concept of channel associated with a communication 128 frequency. For some link technologies, several networks can coexist 129 using the same channel. For these link technologies, a network 130 identifier exists. The network identifier is determined by the link 131 technology specification. When no network identifier exists for a 132 given link, the network identifier has the value "undefined". 134 2.1. IEEE 802.15.4 136 IPv6 over IEEE 802.15.4 is described in [RFC4944]. A LoWPAN is 137 composed of the nodes connected by an IEEE 802.15.4 mesh sharing the 138 same PANID. The PANID identifies a network in the IEEE 802.15.4 139 mesh. Several networks with different PANIDs can coexist on the same 140 channel [IEEE802.15.4]. The PANID of an interface is defined when 141 the interface is switched on. The value of the network identifier of 142 a IEEE 802.15.4 link is the value of the PANID. 144 2.2. IEEE 802.11 146 IP over IEEE 802.11 is described in [RFC5416]. The SSID identifies a 147 network in the IEEE 802.11 link. Several networks with different 148 SSIDs can coexist on the same channel [IEEE802.11]. The SSID of an 149 interface is defined when the interface is switched on. The value of 150 the network identifier of a IEEE 802.11 link is the value of the 151 SSID. 153 2.3. ITU-T G.9959 155 IPv6 over ITU-T G.9959 is specified in [I-D.ietf-6lo-lowpanz]. The 156 HomeID identifies a network of connected nodes [G.9959]. Several 157 HomeIDs can coexist within communication range, but nodes adhering to 158 a network with a given HomeID cannot communicate with nodes adhering 159 to a network with a different HomeID. The value of the network 160 identifier of a G.9959 link is the value of the HomeID. 162 2.4. BLUETOOTH Low Energy 164 IPv6 over BLUETOOTH low energy (btle) is specified in 165 [I-D.ietf-6lo-btle]. The medium is specified in [btle]. 167 BTLE does know the concept of multiple networks in one channel. 169 3. Admin-Local policy 171 The section starts with specifying what multicast packets arriving 172 over a link are legal. It continues with the forwarding of the legal 173 packets over the interfaces for packets with multicast destination 174 addresses with Admin -local scope 4. 176 The admin-local policy is specified as function of the state of a 177 destination link and the multicast packet. The state of the packet 178 is determined by the presence of the MPL option and the destination 179 Multicast address. The state of the interface is determined by the 180 subscribed multicast addresses and the value of the 181 PROACTIVE_FORWARDING parameter of the interface. 183 3.1. Legal incoming packets 185 A packet created in a source (seed) is legal when it conforms to the 186 conditions described in section 9.1 of [I-D.ietf-roll-trickle-mcast]. 188 A packet received over a given link with a multicast destination 189 address, is legal when: 191 o The packet carries the MPL option and the incoming interface is 192 subscribed to the destination multicast address. 194 o The packet does not carry the MPL option and the interface has 195 expressed interest to receive packets with the specified multicast 196 address via MLD [RFC3810] or via IGMP [RFC3376]. Packet was sent 197 on according to PIM-DM [RFC3973] or according to PIM-SM [RFC4601]. 198 The packet forwarded with unicast has been decapsulated. 200 Illegal packets are discarded. 202 3.2. Forwarding legal packets 204 A legal packet that arrived over a link is associated with a network 205 identifier with a value copied from the network identifier of the 206 interface of the incoming link . A packet that is created locally has 207 a network identifier with value "any". 209 Two types of legal packets are considered: (1) packets which carry 210 the MPL option, and (2) packets which do NOT carry the MPL option. 212 3.2.1. Packet with MPL option 214 The packet is forwarded over the link of an interface according to 215 the Trickle algorithm, when: 217 o The packet with a multicast address with scope 2 (link-local) is 218 not forwarded. 220 o Packet with a multicast scope of 5 or higher is out of scope. 222 o The packet with MPL option and a Multicast address MC4 with a 223 scope value of 4, is transmitted over all interfaces that are 224 subscribed to the same multicast address MC4, and have 225 PROACTIVE_FORWARDING set to true. 227 o The packet with MPL option and a Multicast address MC3 with a 228 scope value of 3, is transmitted over all interfaces that are 229 subscribed to the same multicast address MC3, have 230 PROACTIVE_FORWARDING set to true, and the network identifier of 231 the packet is identical to the network-identifier of the 232 interface, or the network identifier of the packet is "any". 234 3.2.2. Packet without MPL option 236 The legal packet without MPL option is handled according to the 237 following rules: 239 o The packet with a multicast address with scope 2 (link-local) or 240 scope 3( Realm-local) is not forwarded. 242 o Packet with a multicast scope of 5 or higher is out of scope. 244 o The packet with a multicast address MC4 with scope 4 is 245 encapsulated with a header carrying the MPL option, and is 246 forwarded according to the Trickle algorithm, over all interfaces 247 that are subscribed to multicast address MC4, and have 248 PROACTIVE_FORWARDING set to true. 250 4. Security Considerations 252 Refer to the security considerations of 253 [I-D.ietf-roll-trickle-mcast]. 255 5. IANA Considerations 257 No considerations for IANA are formulated in this document. 259 6. Acknowledgements 261 This document reflects discussions and remarks from several 262 individuals including (in alphabetical order): 264 7. References 266 7.1. Normative References 268 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 269 Requirement Levels", BCP 14, RFC 2119, March 1997. 271 [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery 272 Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. 274 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 275 Architecture", RFC 4291, February 2006. 277 [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, 278 "Transmission of IPv6 Packets over IEEE 802.15.4 279 Networks", RFC 4944, September 2007. 281 [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. 282 Thyagarajan, "Internet Group Management Protocol, Version 283 3", RFC 3376, October 2002. 285 [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and 286 B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, 287 March 2005. 289 [RFC5416] Calhoun, P., Montemurro, M., and D. Stanley, "Control and 290 Provisioning of Wireless Access Points (CAPWAP) Protocol 291 Binding for IEEE 802.11", RFC 5416, March 2009. 293 [I-D.ietf-6lo-lowpanz] 294 Brandt, A. and J. Buron, "Transmission of IPv6 packets 295 over ITU-T G.9959 Networks", draft-ietf-6lo-lowpanz-02 296 (work in progress), February 2014. 298 [I-D.ietf-roll-trickle-mcast] 299 Hui, J. and R. Kelsey, "Multicast Protocol for Low power 300 and Lossy Networks (MPL)", draft-ietf-roll-trickle- 301 mcast-06 (work in progress), January 2014. 303 [I-D.ietf-6man-multicast-scopes] 304 Droms, R., "IPv6 Multicast Address Scopes", draft-ietf- 305 6man-multicast-scopes-02 (work in progress), November 306 2013. 308 [I-D.ietf-6lo-btle] 309 Nieminen, J., Savolainen, T., Isomaki, M., Patil, B., 310 Shelby, Z., and C. Gomez, "Transmission of IPv6 Packets 311 over BLUETOOTH Low Energy", draft-ietf-6lo-btle-00 (work 312 in progress), November 2013. 314 [IEEE802.15.4] 315 "IEEE 802.15.4 - Standard for Local and metropolitan area 316 networks -- Part 15.4: Low-Rate Wireless Personal Area 317 Networks", . 319 [IEEE802.11] 320 "IEEE 802.11 - Telecommunications and information exchange 321 between systems Local and metropolitan area networks -- 322 Part 11: Wireless LAN Medium Access Control (MAC) and 323 Physical Layer (PHY) Specifications", . 326 [G.9959] "ITU-T G.9959 Short range narrow-band digital 327 radiocommunication transceivers - PHY and MAC layer 328 specifications", . 330 [btle] "BLUETOOTH Specification Version 4.0", . 333 7.2. Informative References 335 [RFC3973] Adams, A., Nicholas, J., and W. Siadak, "Protocol 336 Independent Multicast - Dense Mode (PIM-DM): Protocol 337 Specification (Revised)", RFC 3973, January 2005. 339 [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, 340 "Protocol Independent Multicast - Sparse Mode (PIM-SM): 341 Protocol Specification (Revised)", RFC 4601, August 2006. 343 Author's Address 345 Peter van der Stok 346 Consultant 348 Email: consultancy@vanderstok.org