Protocol Action: 'Address Mapping of IPv6 multicast packets on Ethernet' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Tue, 19 October 2010 18:22 UTC

Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id EFBD73A68EE; Tue, 19 Oct 2010 11:22:52 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Address Mapping of IPv6 multicast packets on Ethernet' to Proposed Standard
Message-Id: <20101019182252.EFBD73A68EE@core3.amsl.com>
Date: Tue, 19 Oct 2010 11:22:52 -0700
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <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: Tue, 19 Oct 2010 18:22:53 -0000

The IESG has approved the following document:

- 'Address Mapping of IPv6 multicast packets on Ethernet '
   <draft-gundavelli-v6ops-l2-unicast-06.txt> as a Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Ron Bonica.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-gundavelli-v6ops-l2-unicast-06.txt

    Technical Summary 

   When transmitting an IPv6 packet to a multicast group, the
   destination address in the link-layer header is typically set to the
   corresponding mapped address of the destination address from the IP
   header.  However, it is not mandatory that the destination address in
   the link-layer header is always a mapped multicast equivalent of its
   IP destination address.  There are various deployment scenarios where
   there a need to transmit an IPv6 multicast message as an unicast
   message on the link-layer.  Unfortunately, the IPv6 specifications do
   not clearly state this.  This document explicitly clarifies this
   point and makes such packet construct and transmission legal and
   valid.
 
    Working Group Summary 

The working group reviewed and discussed the draft. There was a point of
rough consensus, but in general respondents said the document was
relevant, useful, and appropriate.

    Document Quality 

The document is readable to a native speaker of English. It is very
simple, and its two recommendations are clearly stated.

   Personel

Fred Baker is shepherd.