Re: [IPv6] [v6ops] RFC for fec0:0:0:ffff::1?
Mark Smith <markzzzsmith@gmail.com> Wed, 30 November 2022 20:48 UTC
Return-Path: <markzzzsmith@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 8913BC157B3F; Wed, 30 Nov 2022 12:48:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.415
X-Spam-Level:
X-Spam-Status: No, score=0.415 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.999, HK_RANDOM_FROM=0.999, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 te_25pWcpaGd; Wed, 30 Nov 2022 12:48:42 -0800 (PST)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 816D3C1527B7; Wed, 30 Nov 2022 12:48:42 -0800 (PST)
Received: by mail-pg1-x52e.google.com with SMTP id f3so17199535pgc.2; Wed, 30 Nov 2022 12:48:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2MzTA2vzD7EmJeiZMz6s2uxUcotaEhpd8jjwjHRFU+U=; b=VEvHLF/ZdKdl5MvefZBAJjigwntGYvcpoS2e4/CsJjCDkZ2mDSBzTqr/0uqLu3dEV/ SJW5pMgClzKHqTC4bQOf5Ai4PEamYW7lU7o3t/nKMnQpRrE6kOyV7/udDwyEkFnf1jxv y69ZRWNafg29PrIGoW/A//vUcVlLUGGNTwbzYsLC203+UTD1KukCNRPPAozj2vFiVma3 FjtHHzcdEDrSz7jr51TuIDo3FAjabQM55POz5wtlAfZP5CEDxwrF2uhOj5SPPd6ug8uV 3KYaHzZm8GIEYSD2g1sGOw0hVA18PV82DDMgnCoy4wnWQN5TLkrw09Ip9Qt2qZgJPokp oMlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2MzTA2vzD7EmJeiZMz6s2uxUcotaEhpd8jjwjHRFU+U=; b=jl2NZBi3q9M1XTOv/Tbfb/P9jCU1o3Qxsy2/P+AyT31SGrBAH6JbEvjQuHHjnqCGh2 O8CNno27RxRWKLE02jvSr8jiMSQiN5suW7eebmGMb5NWsjVUiv8HhXMk/H2iQ+Pkahs4 Kv+fmsb+3E4Eomj5sb9zx9fU+MngKrEuBE89/Ce57rIId/dSOT0JHqqrMeIu0YlgQNj3 ZFemu+Wsn5Gm4kLnnU7SVgLhDfa1n6uHYu/DTKDXKCUuUreJE9sw1isOn/e1Leb3z5aG +5QaTFnLfpHyQpU7f9SeS6svTON9g/hCHhH2kZHnIKWoR8+8nnl+S3fYNtzdusUfeSmY 4D2Q==
X-Gm-Message-State: ANoB5pmc2cJpGf2oclyKuS9PIoURcAQVwDeMmKguTAV/lLLgL5pf3iRo dSkjcLxOcNz1AWzLy8fNIOWCdBTRZBLSpyQ9XJI=
X-Google-Smtp-Source: AA0mqf7pT+6VaC3fqEfMI/x/1ROGs+4aBaQjjA1djWhU999HLT0Mo/veY98rwlvzLr/Cdr+hpg85HZ+vq3KrJLoDU8Q=
X-Received: by 2002:a05:6a00:338c:b0:56b:a319:7b52 with SMTP id cm12-20020a056a00338c00b0056ba3197b52mr44132672pfb.21.1669841321809; Wed, 30 Nov 2022 12:48:41 -0800 (PST)
MIME-Version: 1.0
References: <324539dd-37f6-fbd9-ea98-c51320f38603@posteo.de> <Y4d8VaEbNV43BGRl@dwc-laptop-2.local> <CAM5+tA-9-kchyifny_pfHLi7n4by3-xCkhmxq8sRHCm=NshbsA@mail.gmail.com> <CAE=N4xd0gEmZB7JY25J8kBYiCio36KqQpr3dwymV30ibeWttOg@mail.gmail.com> <CAN-Dau1tiKhpvW_oWVZ-zPrhSEFvh2CX_R7-2kwfgUn8gXJ2Qg@mail.gmail.com>
In-Reply-To: <CAN-Dau1tiKhpvW_oWVZ-zPrhSEFvh2CX_R7-2kwfgUn8gXJ2Qg@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 01 Dec 2022 07:48:31 +1100
Message-ID: <CAO42Z2yQZuCTZiuF4Ppe7Xmx0kjq3yCs+wdW1b6UsDAqauuZ+A@mail.gmail.com>
To: David Farmer <farmer=40umn.edu@dmarc.ietf.org>
Cc: Ed Horley <ed@hexabuild.io>, v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d15b7305eeb63a5f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vnKFTOS2HxYH2alNWYflOGgi6ao>
Subject: Re: [IPv6] [v6ops] RFC for fec0:0:0:ffff::1?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 30 Nov 2022 20:48:46 -0000
I think it is a problem that should be fixed by Microsoft. Bothering this mailing list about it has created a cost that shouldn't have been incurred, because site-locals have been deprecated. If the OP had lodged a ticket with Microsoft then the cost would have been paid where it was caused. However instead it was asked about on 2 IETF mailing lists. On Thu, 1 Dec 2022, 06:52 David Farmer, <farmer=40umn.edu@dmarc.ietf.org> wrote: > Furthermore, based on RFC 6724 Address Selection, all other known DNS > server addresses will be tried before these. They are the last resort, and > therefore, they probably won't hurt anything, not that they are likely to > help much, either. > > On Wed, Nov 30, 2022 at 1:29 PM Ed Horley <ed@hexabuild.io> wrote: > >> From an email exchange with Dave Thaler (Microsoft) back in 2015 when I >> asked about this: >> >> "I’m not in any hurry to see it removed (under the “if it ain’t broke >> don’t fix it” principle). >> Even the RFC section you cite says: >> Existing implementations and deployments MAY continue to use this >> prefix. " >> >> So I don't see Microsoft removing this from the OS unless there is a >> specific existing security exploit or concern that is demonstrated to be >> exploitable. >> Also, the draft you found has Dave listed as a co-author. Perhaps that >> helps close the loop? >> >> NOTE - I'm not speaking for Dave or Microsoft - just trying to provide >> some context. >> >> Out of my list of IPv6 asks for the Windows OS, this one isn't high on my >> personal list to get "fixed". I feel it is a cosmetic issue more than >> anything else at this point. >> >> On Wed, Nov 30, 2022 at 8:36 AM Nick Buraglio <buraglio@es.net> wrote: >> >>> I have also heard through the grapevine that those pre-dated the >>> deprecation of site-local and that there is "no plan to remove them". This >>> is anecdotal, I have never seen reference to it, just side conversations I >>> have had over the years. >>> >>> >>> ---- >>> nb >>> >>> ᐧ >>> >>> On Wed, Nov 30, 2022 at 9:53 AM Dale W. Carder <dwcarder@es.net> wrote: >>> >>>> Thus spake Klaus Frank (klaus.frank@posteo.de) on Wed, Nov 30, 2022 at >>>> 04:08:07AM +0000: >>>> > does anyone know what RFC is responsible for the IPv6 DNS server >>>> > configuration on all windows clients defaulting to fec0:0:0:ffff::1, >>>> I was >>>> > unable to find any. Nor is it listed in the iana special-purpose >>>> address >>>> > registry. >>>> > >>>> > I however found a draft (draft-ietf-ipv6-0dns-discovery-07) from >>>> 2002, but >>>> > no actual RFC. >>>> >>>> That draft matches my memory. Recall that was well before rfc5006 >>>> which was quite late to the party to address a glaring oversight >>>> as the ra vs dhcpv6 holy wars raged on. >>>> >>>> Having well-known resolver addresses be site-local (and anycasted, >>>> despite what the draft claims on that issue) could have been a >>>> logical design pattern for local networks. >>>> >>>> But more generally, no two people could ever be expected to agree on >>>> a common definition of what a "site" is. rfc3879 documents the pain >>>> very well. (see a generalized incarnation of this issue in rfc8799). >>>> >>>> Dale >>>> >>>> -------------------------------------------------------------------- >>>> IETF IPv6 working group mailing list >>>> ipv6@ietf.org >>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >>>> -------------------------------------------------------------------- >>>> >>> -------------------------------------------------------------------- >>> IETF IPv6 working group mailing list >>> ipv6@ietf.org >>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >>> -------------------------------------------------------------------- >>> >> >> >> -- >> Ed Horley >> ed@hexabuild.io | (925) 876-6604 >> Advancing Cloud, IoT, and Security with IPv6 >> https://hexabuild.io >> And check out the IPv6 Buzz Podcast at >> https://packetpushers.net/series/ipv6-buzz/ >> _______________________________________________ >> v6ops mailing list >> v6ops@ietf.org >> https://www.ietf.org/mailman/listinfo/v6ops >> > > > -- > =============================================== > David Farmer Email:farmer@umn.edu > Networking & Telecommunication Services > Office of Information Technology > University of Minnesota > 2218 University Ave SE Phone: 612-626-0815 > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > =============================================== > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- >
- [IPv6] RFC for fec0:0:0:ffff::1? Klaus Frank
- Re: [IPv6] [v6ops] RFC for fec0:0:0:ffff::1? Erik Kline
- Re: [IPv6] [v6ops] RFC for fec0:0:0:ffff::1? nalini.elkins@insidethestack.com
- Re: [IPv6] [v6ops] RFC for fec0:0:0:ffff::1? Dale W. Carder
- Re: [IPv6] [v6ops] RFC for fec0:0:0:ffff::1? Nick Buraglio
- Re: [IPv6] [v6ops] RFC for fec0:0:0:ffff::1? Ed Horley
- Re: [IPv6] [v6ops] RFC for fec0:0:0:ffff::1? David Farmer
- Re: [IPv6] [v6ops] RFC for fec0:0:0:ffff::1? Mark Smith
- Re: [IPv6] [v6ops] RFC for fec0:0:0:ffff::1? Owen DeLong