Re: 6MAN WG Last Call: <draft-ietf-6man-ug-01.txt>

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 22 July 2013 22:01 UTC

Return-Path: <brian.e.carpenter@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 C88D311E8169 for <ipv6@ietfa.amsl.com>; Mon, 22 Jul 2013 15:01:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QaFjL5aDgat8 for <ipv6@ietfa.amsl.com>; Mon, 22 Jul 2013 15:01:05 -0700 (PDT)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 4B05011E8167 for <ipv6@ietf.org>; Mon, 22 Jul 2013 15:01:02 -0700 (PDT)
Received: by mail-pd0-f174.google.com with SMTP id 10so7287156pdc.5 for <ipv6@ietf.org>; Mon, 22 Jul 2013 15:01:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DUuFhbBYrNctCbmCLZjZ148Yod48jYJPig5aCwz2j4w=; b=tRZnOkbmJ/152CyrtxslKx3DYQZIxQdP1/JVaEaJwWnNUxL5QuIEIlhzAbQS1bupOC l3grdpxOjK5guPYkV4VZKQHsgV2tGtxosN2rZeVfBUghfO1cH/mFE9OrWImcKy4Qp/Sq E/ZvZ9yKbIKIySFlGMVyC64dCdzihZ/PZzuEpeUMK7bjGjtrTD6c67z22KD9GP9gh2N6 uWpAhHUQgzxldob11cf03Rm5eu9fwyKE7SE7HebXtuHnXI3lOKRBHqpI7Fde9iAzvNiX psGeviX4PM8ke5ErOjBLnYPTp3iEqUMbGSZ7FhV8THqnOaKFFEueozfYOChnMn7ZT2rM PZjw==
X-Received: by 10.66.144.161 with SMTP id sn1mr17935983pab.30.1374530460058; Mon, 22 Jul 2013 15:01:00 -0700 (PDT)
Received: from [172.24.31.170] (wireless-nat-1.auckland.ac.nz. [130.216.30.112]) by mx.google.com with ESMTPSA id y9sm37730025pbb.46.2013.07.22.15.00.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Jul 2013 15:00:59 -0700 (PDT)
Message-ID: <51EDAB9B.9010004@gmail.com>
Date: Tue, 23 Jul 2013 10:00:59 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-ug-01.txt>
References: <BAC50B63-3A45-4F49-BD95-812D230EA427@gmail.com> <1374527534.81451.YahooMailNeo@web142503.mail.bf1.yahoo.com>
In-Reply-To: <1374527534.81451.YahooMailNeo@web142503.mail.bf1.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: IPv6 IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 22 Jul 2013 22:01:06 -0000

On 23/07/2013 09:12, Mark ZZZ Smith wrote:
> Hi,
> 
> Firstly, I support advancing this draft.
> 
> Some suggested changes:
> 
> "  This has no known harmful effect as long as the
>    replicated MAC addresses and IIDs are used on different layer 2
>    links.  If they are used on the same link, of course there will be a
>    problem, to be detected by duplicate address detection [RFC4862], but
>    such a problem can usually only be resolved by human intervention."
> 
> I think it would be worth pointing out that the link layer is most likely to fail to operate with duplicate link layer addresses, before DAD has a chance to detect duplicate IPv6 addresses.

OK.

> 
> "  Also, there is
>    evidence from the field that IEEE MAC addresses with "u" = 0 are
>    sometime incorrectly assigned to multiple MAC interfaces.  Firstly,
>    there are recurrent reports of manufacturers assigning the same MAC
>    address to multiple devices. Secondly, significant re-use of the
>    same virtual MAC address is reported in virtual machine environments. "
> 
> I found this text a bit confusing. The '"u" = 0' term read like it was referring to locally unique IEEE MAC addresses ("unique equals no"), and then the 2nd sentence is referring to globally unique (but duplicated and therefore not actually globally unique) MAC addresses, u = 1 in an IPv6 IID, the opposite of what the previous sentence was referring to. Then the third sentence seems to be describing to what the first sentence was referring to. I think the cause of the confusion might be that IEEE use the "locally assigned" bit to distinguish locally generated or not (i.e., "l" = 0 for globally unique), where as IPv6 IIDs have renamed it to "u" bit when the value is inverted. I'd suggest trying to ensure the IEEE terminology is used when IEEE addresses are discussed to make it clearer what the properties of the IEEE address are.

Yep. I remember complaining when the bit inversion was first proposed
that it would lead to years of confusion. Which IEEE standard is the
basic reference for their terminology?

    Brian