RE: [Non-DoD Source] Re: question: are the various IETF web sites IPv6 enabled? If not, why not?

"Baird, John M CTR OSD HPCMP (USA)" <john.m.baird10.ctr@mail.mil> Wed, 10 March 2021 01:20 UTC

Return-Path: <john.m.baird10.ctr@mail.mil>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DD903A1540 for <ietf@ietfa.amsl.com>; Tue, 9 Mar 2021 17:20:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.346
X-Spam-Level:
X-Spam-Status: No, score=-2.346 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.248, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mail.mil
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 SeqDj-W-oGiR for <ietf@ietfa.amsl.com>; Tue, 9 Mar 2021 17:20:35 -0800 (PST)
Received: from USAT19PA24.eemsg.mail.mil (USAT19PA24.eemsg.mail.mil [214.24.22.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9DB73A153B for <ietf@ietf.org>; Tue, 9 Mar 2021 17:20:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mail.mil; i=@mail.mil; q=dns/txt; s=EEMSG2018v1a; t=1615339234; x=1646875234; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=3uf1wRBpRjx0/RclHirT0f1/Ugj8ej5653v4elw0nuA=; b=kP+1G/pJspkcRl5F0ZzAt800+YdouLTzxloxYrtLDmEaWXWIbRKPAkJJ ZlOARZZA61fzXQhqzIWCU+61ftmya+bKRtX9WKYigvku99LwoyeT8+XMj LMszQRcO6T20mHzoDA72HAeah8jLeHT2+h5wm22dmBAtHAvpyP7YtdAyF gGqoALkKiqw8ZijRSJyrNSgKumnL0y8URorKowUhRybJQfaGgxHeWhO23 bNzK7DZpzayAsvVwWAnKVkquhXbsD2wMhoKW26NmBpg9OBqH/PEAbcSIu yecJHEOkpgyB0HTgXiZS/yHG6WA6io6T/D27jje3t0+VpcXppli3T48K9 g==;
IronPort-SDR: SPbEEFkhpL6qztR0uZT14Y/C4n8sudxg2LRJsl9iX09/7J0PDi2H7VMGfLtllUiG9YbUpoN+RY PEKLALo3KUxg==
X-EEMSG-check-017: 201025185|USAT19PA24_ESA_OUT05.csd.disa.mil
X-IronPort-AV: E=Sophos;i="5.81,236,1610409600"; d="scan'208,217";a="201025185"
Received: from edge-mech02.mail.mil ([214.21.130.228]) by USAT19PA24.eemsg.mail.mil with ESMTP/TLS/ECDHE-RSA-AES256-SHA384; 10 Mar 2021 01:20:30 +0000
Received: from UMECHPAPA.easf.csd.disa.mil (214.21.130.170) by edge-mech02.mail.mil (214.21.130.228) with Microsoft SMTP Server (TLS) id 14.3.498.0; Wed, 10 Mar 2021 01:20:25 +0000
Received: from UMECHPA7F.easf.csd.disa.mil ([169.254.8.64]) by umechpapa.easf.csd.disa.mil ([214.21.130.170]) with mapi id 14.03.0513.000; Wed, 10 Mar 2021 01:20:25 +0000
From: "Baird, John M CTR OSD HPCMP (USA)" <john.m.baird10.ctr@mail.mil>
To: Matt Mathis <mattmathis=40google.com@dmarc.ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [Non-DoD Source] Re: question: are the various IETF web sites IPv6 enabled? If not, why not?
Thread-Topic: [Non-DoD Source] Re: question: are the various IETF web sites IPv6 enabled? If not, why not?
Thread-Index: AQHXFJhVDNDSJ25SeUmX9mjEe7nAn6p8HnBQgAAqkFGAAB2PQA==
Date: Wed, 10 Mar 2021 01:20:25 +0000
Message-ID: <E6A1C61CFBA23B449020E298B04EBF501514697C@UMECHPA7F.easf.csd.disa.mil>
References: <20210309033054.6D9756FD971F@ary.qy> <c5406178-e38f-eed0-7cb6-1f799a6c93e6@gmail.com> <E6A1C61CFBA23B449020E298B04EBF501514692A@UMECHPA7F.easf.csd.disa.mil> <AEAE9C1B-5E7B-4F89-BEC7-2B92FEE304DF@consulintel.es> <CAH56bmBOxOcUSOzmmmoanwBnxKuh7qG+0TKW8wZNUKv3tZaYSQ@mail.gmail.com>
In-Reply-To: <CAH56bmBOxOcUSOzmmmoanwBnxKuh7qG+0TKW8wZNUKv3tZaYSQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [214.21.44.14]
Content-Type: multipart/alternative; boundary="_000_E6A1C61CFBA23B449020E298B04EBF501514697CUMECHPA7Feasfcs_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0oMtPScYIA-pIi3m3zCPSmDbAnI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2021 01:20:39 -0000

Matt,
I have done some more testing, and have found that when I am connected to the open Internet correctly (not via the VPN used by my office), many of the IETF sites are indeed IPv6 enabled.

However, https://www.irtf.org/  reports “no address” and https://www.rfc-editor.org/ reports “access denied”, so there are still some unexpected results.

Thanks for the feedback.
John
From: Matt Mathis <mattmathis=40google.com@dmarc.ietf.org>
Sent: Tuesday, March 9, 2021 6:08 PM
To: Baird, John M CTR OSD HPCMP (USA) <john.m.baird10.ctr@mail.mil>
Cc: ietf@ietf.org
Subject: Re: [Non-DoD Source] Re: question: are the various IETF web sites IPv6 enabled? If not, why not?

All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.
________________________________

Another possible reason is that your CPE (modem, home router, etc) doesn't properly support IPv6, or isn't configured to do so.

It is taking a long time but we (US and europe) are approaching 50% IPv6.  See Caution-https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption < Caution-https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption >

If you are on net 26/8, you may have other issues as well.

Thanks,
--MM--
The best way to predict the future is to create it.  - Alan Kay

We must not tolerate intolerance;
       however our response must be carefully measured:
            too strong would be hypocritical and risks spiraling out of control;
            too weak risks being mistaken for tacit approval.


On Tue, Mar 9, 2021 at 12:59 PM JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org < Caution-mailto:40consulintel.es@dmarc.ietf.org <mailto:jordi.palet=40consulintel.es@dmarc.ietf.org %3c Caution-mailto:40consulintel.es@dmarc.ietf.org > > > wrote:
There may be several reasons for that.

Right now, it comes to my mind:
1) Your upstream provider IPv6 connectivity is not able to reach the IETF upstream provider with IPv6.
2) The latency of IPv6 is higher than the IPv4 one.

In those cases, happy eyeballs will prefer IPv4 so you will get IPvfoo extension showing IPv4 as preferred, but if you click, you can still see both the IPv4 and IPv6 addresses as provided by the DNS resolution.

Unfortunately, I've seen way too many ISPs that don't monitor IPv6 with the same degree of quality as IPv4, they rely on customers complains which don't happen because happy eyeballs ...

Regards,
Jordi
@jordipalet



El 9/3/21 21:52, "ietf en nombre de Baird, John M CTR OSD HPCMP (USA)" <ietf-bounces@ietf.org < Caution-mailto:ietf-bounces@ietf.org <mailto:ietf-bounces@ietf.org %3c Caution-mailto:ietf-bounces@ietf.org > >  en nombre de john.m.baird10.ctr=40mail.mil@dmarc.ietf.org<mailto:john.m.baird10.ctr=40mail.mil@dmarc.ietf.org> < Caution-mailto:40mail.mil@dmarc.ietf.org > > escribió:

    Brian,
    Thanks for the quick response. You mention the Firefox "six or not" extension, and that is why I asked the question about IPv6 and IETF websites.

    When I browse the websites you cited, and also Caution-https://tools.ietf.org < Caution-https://tools.ietf.org > , IPvFoo lists several IPv4 addresses, but makes no mention of any IPv6 addresses.

    I can see the IPv6 addresses in DNS, but for some reason IPvFoo reports that the websites respond to web browsers only via IPv4.

    Any theories as to why this is so?

    John

    -----Original Message-----
    From: Brian E Carpenter <brian.e.carpenter@gmail.com < Caution-mailto:brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com %3c Caution-mailto:brian.e.carpenter@gmail.com > > >
    Sent: Monday, March 8, 2021 10:57 PM
    To: Baird, John M CTR OSD HPCMP (USA) <john.m.baird10.ctr@mail.mil < Caution-mailto:john.m.baird10.ctr@mail.mil <mailto:john.m.baird10.ctr@mail.mil %3c Caution-mailto:john.m.baird10.ctr@mail.mil > > >
    Cc: ietf@ietf.org<mailto:ietf@ietf.org> < Caution-mailto:ietf@ietf.org >
    Subject: [Non-DoD Source] Re: question: are the various IETF web sites IPv6 enabled? If not, why not?
    ----

    On 09-Mar-21 16:30, John Levine wrote:
    > In article <4CC47F19-3063-430F-8378-B00EB7E2708F@gmail.com < Caution-mailto:4CC47F19-3063-430F-8378-B00EB7E2708F@gmail.com <mailto:4CC47F19-3063-430F-8378-B00EB7E2708F@gmail.com %3c Caution-mailto:4CC47F19-3063-430F-8378-B00EB7E2708F@gmail.com > > > you write:
    >> -=-=-=-=-=-
    >>
    >> It is my understanding that they all are, and have been for some
    >> time. I might suggest that you ping6 (or ping -6 depending on your OS) to see whether you get a response.
    >
    > Yes, they all are.  The mail is, too.

    Caution-Caution-https://www.irtf.org/ < Caution-https://www.irtf.org/ >  too.
    Caution-Caution-https://www.rfc-editor.org/ < Caution-https://www.rfc-editor.org/ >  too.
    Caution-Caution-https://www.internetsociety.org/ < Caution-https://www.internetsociety.org/ >  too.

    The "six or not" FireFox extension tells me that the ISOC site invokes a couple of IPv4 services, so needs dual stack. The IETF site is clean in that regard.

       Brian




**********************************************
IPv4 is over
Are you ready for the new Internet ?
Caution-http://www.theipv6company.com < Caution-http://www.theipv6company.com >
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.