RFC 6085 on Address Mapping of IPv6 Multicast Packets on Ethernet

rfc-editor@rfc-editor.org Fri, 28 January 2011 17:30 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 502A23A6901 for <ietf-announce@core3.amsl.com>; Fri, 28 Jan 2011 09:30:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.008
X-Spam-Level:
X-Spam-Status: No, score=-102.008 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nw8QlVuxMQUK for <ietf-announce@core3.amsl.com>; Fri, 28 Jan 2011 09:30:38 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 8D6763A67C2 for <ietf-announce@ietf.org>; Fri, 28 Jan 2011 09:30:38 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8DD67E072D; Fri, 28 Jan 2011 09:33:45 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6085 on Address Mapping of IPv6 Multicast Packets on Ethernet
From: rfc-editor@rfc-editor.org
Message-Id: <20110128173345.8DD67E072D@rfc-editor.org>
Date: Fri, 28 Jan 2011 09:33:45 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 28 Jan 2011 17:30:39 -0000

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

        
        RFC 6085

        Title:      Address Mapping of IPv6 Multicast 
                    Packets on Ethernet 
        Author:     S. Gundavelli, M. Townsley,
                    O. Troan, W. Dec
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2011
        Mailbox:    sgundave@cisco.com, 
                    townsley@cisco.com, 
                    ot@cisco.com,  wdec@cisco.com
        Pages:      3
        Characters: 4968
        Updates:    RFC2464

        I-D Tag:    draft-gundavelli-v6ops-l2-unicast-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6085.txt

When transmitting an IPv6 packet with a multicast destination
address, the IPv6 destination address is mapped to an Ethernet
link-layer multicast address.  This document clarifies that a mapping of
an IPv6 packet with a multicast destination address may in some
circumstances map to an Ethernet link-layer unicast address.  
[STANDARDS-TRACK]

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://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