Multicast Network Address Translation
draft-jholland-mboned-mnat-00

Document Type Active Internet-Draft (individual)
Author Jake Holland 
Last updated 2020-11-02
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
Mboned                                                        J. Holland
Internet-Draft                                 Akamai Technologies, Inc.
Intended status: Standards Track                        October 31, 2020
Expires: May 4, 2021

                 Multicast Network Address Translation
                     draft-jholland-mboned-mnat-00

Abstract

   This document defines a method for a network to maintain Network
   Address Translation address mappings for the transport of globally
   addressed multicast traffic within a network that can't otherwise
   forward the globally addressed traffic.  A new Multicast Network
   Address Translation (MNAT) service is defined to communicate the
   address mappings to ingress and egress points within the network, and
   considerations for operation of the MNAT service are described.

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 May 4, 2021.

Copyright Notice

   Copyright (c) 2020 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
   include Simplified BSD License text as described in Section 4.e of

Holland                    Expires May 4, 2021                  [Page 1]
Internet-Draft                    MNAT                      October 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Background  . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   4
     1.4.  Notes for Contributors and Reviewers  . . . . . . . . . .   5
       1.4.1.  Venues for Contribution and Discussion  . . . . . . .   5
   2.  Protocol Operation  . . . . . . . . . . . . . . . . . . . . .   6
     2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   6
       2.1.1.  Egress Node Operational Modes . . . . . . . . . . . .   6
     2.2.  Service Discovery . . . . . . . . . . . . . . . . . . . .   7
       2.2.1.  Detecting Invalid Services  . . . . . . . . . . . . .   7
     2.3.  RESTCONF Bootstrap  . . . . . . . . . . . . . . . . . . .   8
     2.4.  Message Handling  . . . . . . . . . . . . . . . . . . . .   8
       2.4.1.  Notification Subscription . . . . . . . . . . . . . .   8
       2.4.2.  Egress Keys . . . . . . . . . . . . . . . . . . . . .   8
       2.4.3.  Egress Group Management . . . . . . . . . . . . . . .   9
       2.4.4.  Ingress Considerations  . . . . . . . . . . . . . . .   9
       2.4.5.  MNAT Service Considerations . . . . . . . . . . . . .   9
       2.4.6.  Example Messaging Walkthrough . . . . . . . . . . . .  10
   3.  YANG Model  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     3.1.  Yang Tree . . . . . . . . . . . . . . . . . . . . . . . .  10
     3.2.  Yang Module . . . . . . . . . . . . . . . . . . . . . . .  12
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
     4.1.  The YANG Module Names Registry  . . . . . . . . . . . . .  17
     4.2.  The XML Registry  . . . . . . . . . . . . . . . . . . . .  17
     4.3.  The Service Name and Transport Protocol Port Number
           Registry  . . . . . . . . . . . . . . . . . . . . . . . .  17
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  18
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  18
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  20
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   Network Address Translation is very widely used for unicast traffic
   in a variety of networks and according to a variety of mechanisms.
   [RFC2663] is recommended reading for background on the ways unicast
Show full document text