Forwarder Policy for Multicast with Admin-Local Scope in the Multicast Protocol for Low-Power and Lossy Networks (MPL)
RFC 7732
Internet Engineering Task Force (IETF) P. van der Stok
Request for Comments: 7732 Consultant
Category: Informational R. Cragie
ISSN: 2070-1721 ARM Ltd.
February 2016
Forwarder Policy for Multicast with Admin-Local Scope
in the Multicast Protocol for Low-Power and Lossy Networks (MPL)
Abstract
The purpose of this document is to specify an automated policy for
the routing of Multicast Protocol for Low-Power and Lossy Networks
(MPL) multicast messages with Admin-Local scope in a border router.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7732.
Copyright Notice
Copyright (c) 2016 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
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
van der Stok & Cragie Informational [Page 1]
RFC 7732 MPL Admin-Local Policy February 2016
Table of Contents
1. Introduction ....................................................2
1.1. Requirements Language ......................................4
1.2. Terminology and Acronyms ...................................4
2. Network Identifier ..............................................4
2.1. IEEE 802.15.4 ..............................................5
2.2. IEEE 802.11 ................................................5
2.3. ITU-T G.9959 ...............................................5
2.4. BLUETOOTH(R) Low Energy ....................................5
3. MPL4 Router .....................................................5
3.1. MPL Interface Parameters ...................................6
3.2. Determination of MPL4 Zone .................................6
4. Admin-Local Policy ..............................................7
4.1. Legal Multicast Messages ...................................7
4.2. Forwarding Legal Packets ...................................8
4.2.1. MPL Message .........................................8
4.2.2. Multicast Messages without MPL Option ...............9
4.3. Encryption Rules ...........................................9
5. MPL Domains and Zones ...........................................9
6. Default Parameter Values .......................................10
7. Security Considerations ........................................11
8. References .....................................................12
8.1. Normative References ......................................12
8.2. Informative References ....................................14
Acknowledgements ..................................................15
Authors' Addresses ................................................15
1. Introduction
Multicast scopes are defined in [RFC4291]. [RFC7346] extends the
scope definition with this text:
"Interface-Local, Link-Local, and Realm-Local scope boundaries are
automatically derived from physical connectivity or other
non-multicast-related configurations. Global scope has no boundary.
The boundaries of all other non-reserved scopes of Admin-Local or
larger are administratively configured."
The Admin-Local scope must therefore be administratively configured.
In this document, "administratively configured" does not imply
actions by a human beyond installing the protocol specified herein.
"Administratively configured" means an automatic derivation as
described in this document.
van der Stok & Cragie Informational [Page 2]
RFC 7732 MPL Admin-Local Policy February 2016
Show full document text