MPL forwarder policy for multicast with admin-local scope
draft-ietf-roll-admin-local-policy-01

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03

roll                                                     P. van der Stok
Internet-Draft                                                Consultant
Intended status: Informational                                 R. Cragie
Expires: April 25, 2015                                        Gridmerge
                                                        October 22, 2014

       MPL forwarder policy for multicast with admin-local scope
                 draft-ietf-roll-admin-local-policy-01

Abstract

   The purpose of this document is to specify an automated policy for
   the routing of MPL multicast messages with admin-local scope in a
   border router.

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 April 25, 2015.

Copyright Notice

   Copyright (c) 2014 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    Expires April 25, 2015                 [Page 1]

Internet-Draft           MPL admin-local policy             October 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology and Acronyms  . . . . . . . . . . . . . . . .   3
   2.  Network identifier  . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  IEEE 802.15.4 . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  IEEE 802.11 . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  ITU-T G.9959  . . . . . . . . . . . . . . . . . . . . . .   4
     2.4.  BLUETOOTH Low Energy  . . . . . . . . . . . . . . . . . .   5
   3.  MPL4 router . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  MPL interface parameters  . . . . . . . . . . . . . . . .   5
     3.2.  Determination of MPL zone . . . . . . . . . . . . . . . .   5
   4.  Admin-Local policy  . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Legal multicast messages  . . . . . . . . . . . . . . . .   6
     4.2.  Forwarding legal packets  . . . . . . . . . . . . . . . .   7
       4.2.1.  MPL message . . . . . . . . . . . . . . . . . . . . .   7
       4.2.2.  Multicast messages without MPL option . . . . . . . .   8
   5.  MPL domains and zones . . . . . . . . . . . . . . . . . . . .   8
   6.  Default parameter values  . . . . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   10. Change log  . . . . . . . . . . . . . . . . . . . . . . . . .  10
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     11.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Multicast scopes are defined in [RFC4291].  The [RFC7346] extends the
   scope definition with the text:

   "Interface-Local, Link-Local, and Realm-Local scope boundaries are
   automatically derived from physical connectivity or other, non-
   multicast related configuration.  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.
   This draft describes an automated policy for the MPL forwarding of
   multicast messages with admin-local scope within a border router.
   This wish is in line with the autonomous networking ideas presented
   in [I-D.irtf-nmrg-an-gap-analysis].