[Softwires] RFC 8638 on IPv4 Multicast over an IPv6 Multicast in Softwire Mesh Network

rfc-editor@rfc-editor.org Tue, 10 September 2019 03:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 64CBD1200BA; Mon, 9 Sep 2019 20:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id QUzhZVJIxDhC; Mon, 9 Sep 2019 20:40:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8678E120020; Mon, 9 Sep 2019 20:40:44 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1E06BB816DE; Mon, 9 Sep 2019 20:40:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, softwires@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190910034043.1E06BB816DE@rfc-editor.org>
Date: Mon, 9 Sep 2019 20:40:43 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/zjGsiEIFnmyMvK8XNmo9zYnTcPU>
Subject: [Softwires] =?utf-8?q?RFC_8638_on_IPv4_Multicast_over_an_IPv6_Mu?= =?utf-8?q?lticast_in_Softwire_Mesh_Network?=
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2019 03:40:46 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8638

        Title:      IPv4 Multicast over an IPv6 Multicast
                    in Softwire Mesh Networks
        Author:     M. Xu,
                    Y. Cui,
                    J. Wu,
                    S. Yang,
                    C. Metz
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2019
        Mailbox:    xumw@tsinghua.edu.cn, 
        Pages:      19
        Characters: 41530
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-mesh-multicast-25.txt

        URL:        https://www.rfc-editor.org/info/rfc8638

        DOI:        10.17487/RFC8638

During the transition to IPv6, there are scenarios where a backbone
network internally running one IP address family (referred to as the
internal IP or I-IP family) connects client networks running another
IP address family (referred to as the external IP or E-IP family).
In such cases, the I-IP backbone needs to offer both unicast and
multicast transit services to the client E-IP networks.

This document describes a mechanism for supporting multicast across
backbone networks where the I-IP and E-IP protocol families differ.
The document focuses on the IPv4-over-IPv6 scenario, due to lack of
real-world use cases for the IPv6-over-IPv4 scenario.

This document is a product of the Softwires Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC