Re: RFC6085 update to rfc2464bis
Bob Hinden <bob.hinden@gmail.com> Tue, 10 January 2017 18:12 UTC
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54307129D78 for <ipv6@ietfa.amsl.com>; Tue, 10 Jan 2017 10:12:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 gqbbzJ1rZczU for <ipv6@ietfa.amsl.com>; Tue, 10 Jan 2017 10:12:10 -0800 (PST)
Received: from mail-wj0-x22a.google.com (mail-wj0-x22a.google.com [IPv6:2a00:1450:400c:c01::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EFA2129D77 for <ipv6@ietf.org>; Tue, 10 Jan 2017 10:12:10 -0800 (PST)
Received: by mail-wj0-x22a.google.com with SMTP id kq3so41601422wjc.0 for <ipv6@ietf.org>; Tue, 10 Jan 2017 10:12:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=c6g/2QY/3uJp7PD4UhwMPAs5zzqzj4l8jq4sFDSjkxE=; b=TZcJQpuxxkrT5dCfG+84Bp8vdSeF62KFmjPYAOPXddYUEnXSr4dFKy+RMc9CtKaVji LMiK0GLyuWfjQszSEwER3h4eOI3vOd8ptLyGPMyWPwj9nAVc2hIK1NkGCgD276Z4lRHP cvpa2nxZu4mb1oYFQBWpR76+ew5wN4Hv8dqDt5KHUbNyS36YbH6gW3mi8TV+GV2hSv97 01IeKvox9v0nCyRSin50wyBMx/lknG7HQxqkFEhEYRLYuigVq50bLQIuHmlrVMQbUBSs /Srk/KxKt7DyOEYTne+A9W3FsPzXy+Mg4jeQP5Ugv2PyZeveg8oSbEEotbem8446LiDI WgbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=c6g/2QY/3uJp7PD4UhwMPAs5zzqzj4l8jq4sFDSjkxE=; b=jiBsIhxL/bw7YuPnqf77bMbo54ZgLlHdSb3WlvNBRvWpL1XCGWWrbchXfO4/ILoIde Vc2S3RP24+TBedoJNtrodPW72SP9kNtv7SmE5mRxGrk060LM2JDAa0FppsXPntGVaqx+ TjdQ6Wm+e4R+pkQmec5kyUdN282tOe/6Sw95bS7BnIj+NkIQo8gydcUiTJuzY7/UxOpC 2EVAAa35FXS83mduNx4CvxbCPA0+sPqrqRR2sKgolmfhzDbwBPScHNQmaTmYL7IqWGJI bSAdVKMr1P5dYagbELvAhX489exDjJRFveqN5poFDtohOB4vbi7vhtIichbrA4V7Ks9r GdtQ==
X-Gm-Message-State: AIkVDXIt/UUIaYbO7X5U3Rp30tDLLjf7qJMDQ6MEH9rozlF0O2Bx1psjUvF7mItuqqBzGA==
X-Received: by 10.194.0.97 with SMTP id 1mr1892191wjd.223.1484071928798; Tue, 10 Jan 2017 10:12:08 -0800 (PST)
Received: from ?IPv6:2601:647:4d01:db10:9484:498c:2a79:f755? ([2601:647:4d01:db10:9484:498c:2a79:f755]) by smtp.gmail.com with ESMTPSA id js10sm4494357wjb.19.2017.01.10.10.12.06 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 10 Jan 2017 10:12:07 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_B7CD6F82-7B96-4079-B49E-834AC9066468"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: RFC6085 update to rfc2464bis
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CAJE_bqc4LBxeJFupiG=P0WiXqmM2Y-pyDN9skggGPd9c_N=AbQ@mail.gmail.com>
Date: Tue, 10 Jan 2017 10:12:01 -0800
Message-Id: <76C7F51B-4025-4741-BAFC-E98BF6AEEAC7@gmail.com>
References: <C2C9A241-BBE1-4DC1-BA9D-B6D20EF75FD6@gmail.com> <CAJE_bqc4LBxeJFupiG=P0WiXqmM2Y-pyDN9skggGPd9c_N=AbQ@mail.gmail.com>
To: 神明達哉 <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/zbN0i1N3-R-_NPRuEcezyE_lAp4>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jan 2017 18:12:12 -0000
Jinmei-san, > On Jan 10, 2017, at 9:26 AM, 神明達哉 <jinmei@wide.ad.jp> wrote: > > At Mon, 9 Jan 2017 13:53:54 -0800, > Bob Hinden <bob.hinden@gmail.com> wrote: > >>> 7. Address Mapping -- Multicast >>> >>> An IPv6 packet with a multicast destination address DST, consisting >>> of the sixteen octets DST[1] through DST[16], is transmitted to the >>> Ethernet multicast address whose first two octets are the value 3333 >>> hexadecimal and whose last four octets are the last four octets of >>> DST. >>> >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> |0 0 1 1 0 0 1 1|0 0 1 1 0 0 1 1| >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | DST[13] | DST[14] | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | DST[15] | DST[16] | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> >> An IPv6 multicast packet may also be mapped to a unicast Ethernet >> Link layer address as defined in Section 6. > > I think it's more helpful to refer to RFC6085 explicitly here. > Otherwise the proposed text looks good to me. RFC6085 doesn’t actually say very much. The only real content in Section 3: 3. Receiving IPv6 Multicast Packets An IPv6 node receiving an IPv6 packet with a multicast destination address and an Ethernet link-layer unicast address MUST NOT drop the packet as a result of the use of this form of address mapping. There is some text in the Introduction that says more: This document extends this mapping to explicitly allow for a mapping of an IPv6 packet with a multicast destination address into an Ethernet link- layer unicast address, when it is clear that only one address is relevant. Unfortunately, there isn’t anything like that in the main part of the document. I will add an informational reference to RFC6085, but I don’t think it helps very much. Thanks, Bob > >> An IPv6 node receiving an IPv6 packet with a multicast destination >> address and an Ethernet link-layer unicast address must not drop the >> packet as a result using of this form of address mapping. > > -- > JINMEI, Tatuya > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > --------------------------------------------------------------------
- RFC6085 update to rfc2464bis Bob Hinden
- Re: RFC6085 update to rfc2464bis Sander Steffann
- Re: RFC6085 update to rfc2464bis 神明達哉
- Re: RFC6085 update to rfc2464bis Bob Hinden
- Re: RFC6085 update to rfc2464bis 神明達哉
- Re: RFC6085 update to rfc2464bis Bob Hinden
- Re: RFC6085 update to rfc2464bis otroan
- Re: RFC6085 update to rfc2464bis Alexandre Petrescu
- Re: RFC6085 update to rfc2464bis - Ethernet or Wi… Alexandre Petrescu
- Re: RFC6085 update to rfc2464bis - Ethernet or Wi… Carsten Bormann
- Re: RFC6085 update to rfc2464bis Mark Smith
- Re: RFC6085 update to rfc2464bis - Ethernet or Wi… Fred Baker
- Re: RFC6085 update to rfc2464bis - Ethernet or Wi… Brian E Carpenter
- Re: RFC6085 update to rfc2464bis Bob Hinden