New IPv6 Multicast Addresses for Switch ML
draft-hsingh-ipv6-coin-ml-02

Document Type Active Internet-Draft (individual)
Last updated 2019-06-10
Stream (None)
Intended RFC status (None)
Formats plain text 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)
COIN                                                            H. Singh
Internet-Draft                                            MNK Consulting
Intended status: Standards Track                           June 10, 2019
Expires: December 12, 2019

               New IPv6 Multicast Addresses for Switch ML
                      draft-hsingh-ipv6-coin-ml-02

Abstract

   Recently, in-network aggregation to scale distributed machine
   learning (ML) has been presented.  A network switch implementation
   uses IPv4 broadcast messages from switch to the hosts to send updates
   to all workers.  IPv6 does not support broadcast addresses.  This
   document proposes, IPv6 implementations use the IPv6 link-local all-
   nodes multicast address, until a new IPv6 link-local multicast
   address is assigned by IANA for switch to hosts multicast
   communications.

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 https://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 December 12, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Singh                   Expires December 12, 2019               [Page 1]
Internet-Draft                   IPv6 ML                       June 2019

   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.

Table of Contents

   1.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Additional Information  . . . . . . . . . . . . . . . . . . .   2
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   3
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

2.  Introduction

   New computing in the network for ML uses IPv4 broadcast
   communications between switch to hosts.  [Switch-ML].  With IPv6,
   multicast communications would be used.  This document proposes a new
   well-known multicast address be defined for such communications.
   Until a new address is defined, the IPv6 link-local all-nodes
   multicast address may be used.  By definition, a layer-2 switch
   operates in the link-local subnet.  Thus, the IPv6 link-local
   multicast address defined by this document suffices for switch to
   host multicast communications.

3.  Additional Information

   It is common when new networking protocols such as RPL [RFC6550] and
   Babel [RFC6126] were developed, each protocol requested IANA for a
   new IPv6 link-local multicast address for use.  Switch ML does not
   have a protocol defined by IETF just yet and may never define one.
   However, experiments in switch ML are already using IP or layer-2
   broadcast communications.  For IPv6, switch ML experiments should use
   IPv6 link-local multicast communications.  A new IPv6 link-local
   multicast address for switch ML facilitates efficient filtering by
   hosts.

Singh                   Expires December 12, 2019               [Page 2]
Internet-Draft                   IPv6 ML                       June 2019

   If a switch is configured in layer-3 mode and if switch ML
   communicates with hosts to another IPv6 subnet, an IPv6 Site-Local
Show full document text