IETF Logo Mail Archive

Re: [v6ops] Same interface ID under several prefixes

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 02 July 2022 02:57 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83142C157B44 for <v6ops@ietfa.amsl.com>; Fri, 1 Jul 2022 19:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.981
X-Spam-Level:
X-Spam-Status: No, score=-3.981 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-1.876, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LtAlvOtpLurM for <v6ops@ietfa.amsl.com>; Fri, 1 Jul 2022 19:57:39 -0700 (PDT)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 320D6C14CF0F for <v6ops@ietf.org>; Fri, 1 Jul 2022 19:57:39 -0700 (PDT)
Received: by mail-pg1-x52b.google.com with SMTP id 9so4019868pgd.7 for <v6ops@ietf.org>; Fri, 01 Jul 2022 19:57:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=x1j6cerCkxUqz+NTJtoAvBhtGUWTj4HpoOWBIunLHeE=; b=nRqFYqmQKBBPGVi6sEoFz7UvjMtJyEmDeeSafy4+bnu8Z/DgZQSUeEbFiz7wp6LvuX YaCg1gEB6IEHzPT6YVPKcSth4nL71EvSDdD3j4ezNXfavR1W44S7Wr1VOhhcAwM/hqk0 3sWp4UOxi24UzUJoRfZ/c5F9UEO6TSFYVJsPgON9dO9RskOrRXhQuVjtc8I3Ash31TNe LrT2qIuU1Z2jQ40W97DvW9RQPU06yUM02zzuKEHZNlpdte9ta7YyeOOula/t8xk+4FYT eMZVVUcVMNyYCn2nFwJFbRx5rYufhf74P9x6EaRaNajeDcBW7GHSG0EXPPsvQH48j9Pz cN5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=x1j6cerCkxUqz+NTJtoAvBhtGUWTj4HpoOWBIunLHeE=; b=elxp86Q/MQDQE0JEbgxmRZcAJPRpXUIy1m7jINu75AH+rR7/LELNbiiIPHTbZ1X89y EqVjnbrQjiiifhbOA9FdXZhS/NJmU41wuLsmCWLftb5fZ45qjDuBgwM4fIS2scnRGzW2 5ia8zmBbEAgH6rYaJvzD7ZRsW9nzb2/tJH+9KBMIF5GP29xSzhLzWTR8Pcln9BoBcqf2 x5t1DAxEBNCEjqALdke7RZY6UmuP7LGiz2LVHAxZIUmA26F0qrKf+TPfC+z6TD9/mBfJ 3J3JY/s5mtqKEl9wXmURqglxtxspyttokTe3cbZP7Shww0tUo4bx9aJs7C35UZuNhnGS 60gw==
X-Gm-Message-State: AJIora+F+h4suN1GEu0l6xOCysIjMnmtdCC2yeoy21NKkvWeMNPWcII6 HLDvUdtEtkj5meOQ43/0lP5Q0UR+iuXbFI9c
X-Google-Smtp-Source: AGRyM1tEiPuwFZmrNYPQAaOvO8hXgLvVGw32wYYraCqU/EJdHSYzMdFov86aXhYrSWBHtWgly/lJIQ==
X-Received: by 2002:a63:2254:0:b0:40d:d291:7710 with SMTP id t20-20020a632254000000b0040dd2917710mr14693043pgm.269.1656730658130; Fri, 01 Jul 2022 19:57:38 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id e7-20020a170902784700b0015eab1b097dsm16317076pln.22.2022.07.01.19.57.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 01 Jul 2022 19:57:37 -0700 (PDT)
Message-ID: <5a4d686f-f5ce-9f69-46e7-e807a79315c2@gmail.com>
Date: Sat, 02 Jul 2022 14:57:33 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Mark Smith <markzzzsmith@gmail.com>
Cc: IPv6 Operations <v6ops@ietf.org>
References: <1f96f6d6-1c9a-0b18-acf2-dc7d0041ee3b@gmail.com> <CAO42Z2xUyCQ5gpoo2AMjh75OzgP8a4KC8ybYx-5mnsppU5Y_6A@mail.gmail.com> <CAO42Z2z5b-ud1H0aCCsS1NszSeAxrpDNAeWROXuoqEYPgfvG0Q@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <CAO42Z2z5b-ud1H0aCCsS1NszSeAxrpDNAeWROXuoqEYPgfvG0Q@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/GlOSv74unXebENJnpNIuNSzKmtk>
Subject: Re: [v6ops] Same interface ID under several prefixes
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jul 2022 02:57:43 -0000

Thanks. So it seems that Windows 10 and 11 are identical for this.

Regards
    Brian

On 02-Jul-22 14:39, Mark Smith wrote:
> On Fri, 17 Jun 2022 at 16:58, Mark Smith <markzzzsmith@gmail.com> wrote:
>>
>> Hi,
>>
>> On Fri, 17 Jun 2022, 14:46 Brian E Carpenter, <brian.e.carpenter@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> As a side effect of a WG Last Call over on 6man, I've come up with a question about SLAAC implementations.
>>>
>>> On Windows 10 (patched up to date), if you find the Interface ID in a stable GUA or ULA, it is also the Interface ID in the device's link-local address. I see the same identifier used for three different prefixes right now (GUA, ULA, LL). All you have to do is type "ipconfig" at the Windows command prompt.
>>>
>>> However, it seems to me that this practice violates RFC 7217, which says:
>>> "   o  The resulting Interface Identifiers must change when addresses are
>>>          configured for different prefixes. "
>>>
>>> Am I right to consider this a bug?
>>
>>
>> Yes, if they're claiming to comply with RFC7217, which is now the default for SLAAC per RFC8064.
>>
>> Looking at a Windows 10 PC I've got here, that should be up to date (corporate maintained), I'm seeing with 'ipconfig':
>>
>> - Same IID for GUA and ULA listed as 'IPv6 Address'.
>>
>> - Same IID for GUA and ULA listed as 'Temporary IPv6 Address', however different IID than the previous 'IPv6 Address'
>>
>> - Different IID than all of the above for the Link-Local address.
>>
>> None of the IIDs have embedded FF:FE, so Windows 10 has certainly moved on from EUI-64 based IIDs.
>>
>> I'll have a look at a Window 11 PC over the weekend.
> 
> Did look over that weekend, forgot to update.
> 
> Same for Windows 11 IIDs as above, e.g. IIDs across the set of
> prefixes for the same type of address match i.e. "Same IID for GUA and
> ULA listed as 'Temporary IPv6 Address', however different IID than the
> previous 'IPv6 Address'"
> 
> Regards,
> Mark.
>>
>> Regards,
>> Mark.
>>
>>
>>
>>
>>
>>
>>>
>>> Regards
>>>      Brian Carpenter
>>>
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email