RFC 7371 on Updates to the IPv6 Multicast Addressing Architecture

rfc-editor@rfc-editor.org Fri, 19 September 2014 19:18 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5092C1A8759 for <ietf-announce@ietfa.amsl.com>; Fri, 19 Sep 2014 12:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.554
X-Spam-Level:
X-Spam-Status: No, score=-103.554 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.652, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uYtWv6g92y_8 for <ietf-announce@ietfa.amsl.com>; Fri, 19 Sep 2014 12:18:35 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id DA1751A8722 for <ietf-announce@ietf.org>; Fri, 19 Sep 2014 12:18:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 31058182548; Fri, 19 Sep 2014 12:17:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7371 on Updates to the IPv6 Multicast Addressing Architecture
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140919191753.31058182548@rfc-editor.org>
Date: Fri, 19 Sep 2014 12:17:53 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/XedMhLsMBl5noDYHS6mBnZlzpU8
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 19:18:41 -0000

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

        
        RFC 7371

        Title:      Updates to the IPv6 Multicast 
                    Addressing Architecture 
        Author:     M. Boucadair, S. Venaas
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2014
        Mailbox:    mohamed.boucadair@orange.com, 
                    stig@cisco.com
        Pages:      10
        Characters: 18327
        Updates:    RFC 3306, RFC 3956, RFC 4291

        I-D Tag:    draft-ietf-6man-multicast-addr-arch-update-08.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7371.txt

This document updates the IPv6 multicast addressing architecture by
redefining the reserved bits as generic flag bits.  The document also
provides some clarifications related to the use of these flag bits.

This document updates RFCs 3956, 3306, and 4291.

This document is a product of the IPv6 Maintenance 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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

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