
From nobody Thu Apr  1 02:37:26 2021
Return-Path: <ted.ietf@gmail.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D1F63A126C for <architecture-discuss@ietfa.amsl.com>; Thu,  1 Apr 2021 02:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 i5xgeULVabGB for <architecture-discuss@ietfa.amsl.com>; Thu,  1 Apr 2021 02:37:19 -0700 (PDT)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (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 0725C3A122C for <architecture-discuss@ietf.org>; Thu,  1 Apr 2021 02:37:18 -0700 (PDT)
Received: by mail-ot1-x330.google.com with SMTP id h6-20020a0568300346b02901b71a850ab4so1561298ote.6 for <architecture-discuss@ietf.org>; Thu, 01 Apr 2021 02:37:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+nob+s9zW14gpmKc7xV7orUhfiPgoHPnMIhz8/Aa6n0=; b=QXmO5F6MdiTHLElhhpX6ey2xEsbCEBYGE0EcNV0Ur8UjbccDqBeQ+3KNQL2JzMFzwR sjKnZVtvb3qhQT6AYVQjMNrsECs3tGhm6n9SP5oA/ZtITQYU9+Nyj5IPGx+2u2I/LWuh izl8rUv3PhPxMa2QcGIgWG/iojMOFLwG74JIDmxhNblpFJcr5aMc93G0oJecYCc2nyO2 hIlbGa3qrCIlWRMFeHBMiX17KnJkRGjOztP+0QmdVK/5r+v9DziQv0xLZHaD4FWn4gAd cwpZ1km/i54ojzyzNjB3qY6sgRbuFrGHyAOx3RnDSCbXIab2jHMqJaFLCHPlVRgyJ4BX jxhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+nob+s9zW14gpmKc7xV7orUhfiPgoHPnMIhz8/Aa6n0=; b=PgkuLf6GHq3SSIjz/edz71sKaSPekEtZIk1XJT8NzeqL5Q1qUGtc8cP/AivM46iwm7 GvGWR/ynR5qm+nuzE1u1L2WU19Uf2i7yBDu52F5CVdXOsGHY1wM+JkRVA7Ku0OOwkWd+ d9zDnmJp03Ufvjds+qs9mNlZ4wV47NWhOzyLsaeQQciuI4CrAxuCvL8oOBK+nH7PKX3d miLawtyd81hRS7pJXOGt0uI4Q75+dEsn9C6t/dVixujUDReLGgPPUQtuyZM4ZYL2RbFE s1NyGmQWu5s/wv7YVhRPqjawmX+HxoFkpahP/TxjkXbCn0SMy/LuRB+JI3hERkZGQK5b sTvw==
X-Gm-Message-State: AOAM530Mbr/5mm/WxV/C0DfJkNBVYUTYRiWkfpU2/d7iD4GpbbOoFCn1 DZ0K5PM76m2kqUE56PquPYhoGuwLWZO3YG3yGyOnUjVu5TtuuQ==
X-Google-Smtp-Source: ABdhPJxqdQm8Sx/bLTpKiIQEcn8UuNjnNx8yiRi9H2YG3uAyPEEY5oAPipw13wQiT4vPr0fCPokB0HdNLE4y1vycH10=
X-Received: by 2002:a05:6830:1515:: with SMTP id k21mr6077982otp.269.1617269836560;  Thu, 01 Apr 2021 02:37:16 -0700 (PDT)
MIME-Version: 1.0
References: <4329d51a-d5ba-45b3-9fb0-6795dc6fccd3@www.fastmail.com> <CAMGpriWA4B8AThNKBOHo-bfAdQ2s5iYv8rBOB7X8UVc5GsqENA@mail.gmail.com> <CAMGpriUJkWYPyw7=oAj_GnGu2J14T3=VZYNWPZtAs870P=x0sg@mail.gmail.com> <a68636c2-5df0-46eb-8147-79ec6a992f8a@www.fastmail.com> <CAMGpriU_L8HbLFX_mMBtBXxy=XOc5BAnYgVR9R8TQO=DPvRD_g@mail.gmail.com> <F59E2FC3-19CE-4D14-9F1C-9F7125D89455@mnot.net> <CAMGpriVJCsird15oBfT=gSDTr59_yf9TkLmOSO7a9DGX0VRjOg@mail.gmail.com> <CA+9kkMB2iOA-QaCidJHVN=qqZ8TtPXV=xyfuKh+i44VzZLWG3w@mail.gmail.com> <c88bbb17-4a30-4241-af98-436ddf01ca5c@www.fastmail.com>
In-Reply-To: <c88bbb17-4a30-4241-af98-436ddf01ca5c@www.fastmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 1 Apr 2021 10:36:50 +0100
Message-ID: <CA+9kkMD0AGtzCFRTJDAHZODadBqeFhAGircz6EppVs4Rj9U2sQ@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: architecture-discuss@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001d3ba405bee5fa59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/o-6BBhU3rYq7EypoqK1ahroRHk8>
Subject: Re: [arch-d] Treating "private" address ranges specially
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Apr 2021 09:37:24 -0000

--0000000000001d3ba405bee5fa59
Content-Type: text/plain; charset="UTF-8"

I've snipped almost everything to give a narrow response to your follow-up
question.

On Thu, Apr 1, 2021 at 12:53 AM Martin Thomson <mt@lowentropy.net> wrote:


> The question I'm now interested in answering is whether using these as
> part of a heuristic in order to limit the scope of a change like the
> proposed is tolerable.
>
> The goal here is to close off a security loophole in how browser make
> request for a tiny slice of the total set of requests that are made.  The
> ultimate goal might be to remove the loopholes uniformly.  However, that
> would break so much stuff that a change like that would never stick.  This
> is a more narrowly-scoped approach that tries to identify conditions where
> the requests are a) more dangerous in general, and b) rare enough that any
> breaks would not be widely felt.
>
> I've pointed out some of the limitations of this approach (and several
> more have been identified, thanks!), but I haven't seen reasons here why a
> heuristic like that proposed would be strictly problematic.  Assuming that
> these shortcoming are acknowledged properly (they are not currently) is
> there any reason not to use some sort of address-based heuristic for this
> sort of purpose?
>
> I can see how building on top of this simplistic base for other purposes
> might be harmful, but is the specific action being taken inherently bad, or
> is it just not very good?  It not being very good is a totally fair
> criticism, but that will be balanced against the apparent utility here.
> This design protects the badly-secured router provided by my ISP from
> requests from the big bad Internet.  That is a tangible outcome against
> which "addressing is more complex than this design allows for" doesn't
> weigh very heavily.
>

My personal take is that this does not do what it says on the tin, and that
deploying a security mitigation that doesn't do what it says it does is
inherently bad.

As Toerless pointed out, the simple designations tell you whether something
is *potentially* globally routable or *potentially* private.  In
organizations that got lots of globally routable space, parts of it were
carved into limited reachability domains.  Those are just as private for
those organizations as those marked in the IANA registry.  They are not
protected by this, but in the presence of this method, the organizations
might assume those private addresses were (and the number of organizations
with sufficient address space to do this in IPv6-land is not small).  There
are lots of other organizations that have deployed methods to make IP
address space that is nominally private actually have a greater scope.
They would lose the ability to reference resources that should be
reachable.  That breaks the character of the web.

Mapping the reachability overlap of two hosts on the network is,
unfortunately, a complex problem in the current Internet.  I don't think
that this registry-based approach is a sound basis for tackling the
problem.

Just my two cents,

Ted Hardie

--0000000000001d3ba405bee5fa59
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I&#39;ve snipped almost everything to give a narrow r=
esponse to your follow-up question.<br></div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Apr 1, 2021 at 12:53 AM Mart=
in Thomson &lt;<a href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&g=
t; wrote:<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
The question I&#39;m now interested in answering is whether using these as =
part of a heuristic in order to limit the scope of a change like the propos=
ed is tolerable. <br>
<br>
The goal here is to close off a security loophole in how browser make reque=
st for a tiny slice of the total set of requests that are made.=C2=A0 The u=
ltimate goal might be to remove the loopholes uniformly.=C2=A0 However, tha=
t would break so much stuff that a change like that would never stick.=C2=
=A0 This is a more narrowly-scoped approach that tries to identify conditio=
ns where the requests are a) more dangerous in general, and b) rare enough =
that any breaks would not be widely felt.<br>
<br>
I&#39;ve pointed out some of the limitations of this approach (and several =
more have been identified, thanks!), but I haven&#39;t seen reasons here wh=
y a heuristic like that proposed would be strictly problematic.=C2=A0 Assum=
ing that these shortcoming are acknowledged properly (they are not currentl=
y) is there any reason not to use some sort of address-based heuristic for =
this sort of purpose?<br>
<br>
I can see how building on top of this simplistic base for other purposes mi=
ght be harmful, but is the specific action being taken inherently bad, or i=
s it just not very good?=C2=A0 It not being very good is a totally fair cri=
ticism, but that will be balanced against the apparent utility here.=C2=A0 =
This design protects the badly-secured router provided by my ISP from reque=
sts from the big bad Internet.=C2=A0 That is a tangible outcome against whi=
ch &quot;addressing is more complex than this design allows for&quot; doesn=
&#39;t weigh very heavily.<br></blockquote><div><br></div><div>My personal =
take is that this does not do what it says on the tin, and that deploying a=
 security mitigation that doesn&#39;t do what it says it does is inherently=
 bad.</div><div><br></div><div>As Toerless pointed out, the simple designat=
ions tell you whether something is *potentially* globally routable or *pote=
ntially* private.=C2=A0 In organizations that got lots of globally routable=
 space, parts of it were carved into limited reachability domains.=C2=A0 Th=
ose are just as private  for those organizations as those marked in the IAN=
A registry.=C2=A0  They are not protected by this, but in the presence of t=
his method, the organizations might assume those private addresses were (an=
d the number of organizations with sufficient address space to do this in I=
Pv6-land is not small).=C2=A0 There are lots of other organizations that ha=
ve deployed methods to make IP address space that is nominally private actu=
ally have a greater scope.=C2=A0 They would lose the ability to reference r=
esources that should be reachable.=C2=A0 That breaks the character of the w=
eb.</div><div><br></div><div>Mapping the reachability overlap of two hosts =
on the network is, unfortunately, a complex problem in the current Internet=
.=C2=A0 I don&#39;t think that this registry-based approach is a sound basi=
s for tackling the problem.=C2=A0 <br></div><div><br></div><div>Just my two=
 cents,</div><div><br></div><div>Ted Hardie<br></div><div><br></div></div><=
/div>

--0000000000001d3ba405bee5fa59--


From nobody Thu Apr  1 08:31:27 2021
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51D8C3A18D2 for <architecture-discuss@ietfa.amsl.com>; Thu,  1 Apr 2021 08:31:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 jofat_0jGINb for <architecture-discuss@ietfa.amsl.com>; Thu,  1 Apr 2021 08:31:21 -0700 (PDT)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 BE5E53A18D0 for <architecture-discuss@ietf.org>; Thu,  1 Apr 2021 08:31:21 -0700 (PDT)
Received: by mail-yb1-xb31.google.com with SMTP id i144so2215853ybg.1 for <architecture-discuss@ietf.org>; Thu, 01 Apr 2021 08:31:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iSNr5/MGT2u4/1dJsmpu/+B0vkjMkJL1PkqnKvejm1w=; b=e4k/jKCoNAxyAba1RyTpF/t3UalwJW9bnbIKHwSAQzMmuJfv0q03Xk3YYqBQjxWLfb Jy55BmibZSaCLR2D8V4fi4UwqjZUl6URY/CuacLy+KhfQZrYEYU227Teu2BuLhswAeeh WeRqiHlER4yhGlKz6U12wjbnp9uQ6AX1dqO7PyeRVUu/AjmvegVV6Ksc8Fpynn2g8ai1 AfY6xmGw/ONFLa5HaA3ZAOb3Cc+4WhGFgcBpD1PSuLOR86hX2sEUsXUSqbYoTfjbCK6N s+x61tGslmo/SOjCVe/ln9dkEE/Pn1ama/S50qz6gQvPlGvpFbgAArGyyS7MXHJj31N9 MhiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iSNr5/MGT2u4/1dJsmpu/+B0vkjMkJL1PkqnKvejm1w=; b=sZqlcWvbiSmPeeeSkcCwiOBlqFlEifpMF9Ym2naLHlUUMDwt89LNpsI6rDQWFl2mJE VyqBE0MYqbbBU+l1mVhqOB/4vZdO25hw2Cp7UeKFUbem/Y/WBGlrspcUVdVl/gOGVwCF Jn3eVSeVEWwQRGa2GGAviK/y8mdai8pK7lHmMJPfw2ighinOQTABfabWjLieEhISksLj M6TzuobreYDxlgTg7SjgfKV17rh2P3CjRPivKO2TA39roW9kfeiGMgPMO3YNjhw9GlB1 N6lIAwtYZO1huCQveG02/al3JxTdG1b1CUyRlMcNvvOPk0UXsb5lqHzhuxMPFDANrdCX EToA==
X-Gm-Message-State: AOAM530QtRl/QtLkFljb3zQY0fFlOZmGPAiuai0lkOb7l/Zq4/njm3gP fXM0dzRd00wfdBxaIlA1PvXm9VRvt3uUzai9kYHfQ0lcL9Y=
X-Google-Smtp-Source: ABdhPJybIYzPm/HNR6stO3Ha+MA7YvT12rBGzjfNxxJx327ty7y/YdnikJ09X7siCoXd8j04ZrIYetzuY17BFZuCEgs=
X-Received: by 2002:a25:6814:: with SMTP id d20mr12950056ybc.53.1617291078524;  Thu, 01 Apr 2021 08:31:18 -0700 (PDT)
MIME-Version: 1.0
References: <4329d51a-d5ba-45b3-9fb0-6795dc6fccd3@www.fastmail.com> <CAMGpriWA4B8AThNKBOHo-bfAdQ2s5iYv8rBOB7X8UVc5GsqENA@mail.gmail.com> <CAMGpriUJkWYPyw7=oAj_GnGu2J14T3=VZYNWPZtAs870P=x0sg@mail.gmail.com> <a68636c2-5df0-46eb-8147-79ec6a992f8a@www.fastmail.com> <CAMGpriU_L8HbLFX_mMBtBXxy=XOc5BAnYgVR9R8TQO=DPvRD_g@mail.gmail.com> <F59E2FC3-19CE-4D14-9F1C-9F7125D89455@mnot.net> <CAMGpriVJCsird15oBfT=gSDTr59_yf9TkLmOSO7a9DGX0VRjOg@mail.gmail.com> <CA+9kkMB2iOA-QaCidJHVN=qqZ8TtPXV=xyfuKh+i44VzZLWG3w@mail.gmail.com> <c88bbb17-4a30-4241-af98-436ddf01ca5c@www.fastmail.com>
In-Reply-To: <c88bbb17-4a30-4241-af98-436ddf01ca5c@www.fastmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 1 Apr 2021 10:30:52 -0500
Message-ID: <CAKKJt-c8SsHLu+0F3czh8sx2uFnTOZEE_FXZXAAwHsnYxDVVPw@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: architecture-discuss@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003be1b205beeaecf7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/kxj1sDj6m6CZkS8XK3N6waDFaBc>
Subject: Re: [arch-d] Treating "private" address ranges specially
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Apr 2021 15:31:26 -0000

--0000000000003be1b205beeaecf7
Content-Type: text/plain; charset="UTF-8"

I shouldn't ask, but I'd feel worse if I didn't.

On Wed, Mar 31, 2021 at 6:53 PM Martin Thomson <mt@lowentropy.net> wrote:

> Thanks everyone for the insights.
>
> I'll reply to Ted as he hit the crux of the issue most adroitly...
>
> On Wed, Mar 31, 2021, at 20:07, Ted Hardie wrote:
> > What I think this proposal would actually like to do is to determine
> > whether a resource referenced by a specific web server would also be
> > reachable by that server.
>
> That's exactly it.
>
> Brian's point about the inherent folly of making such guesses is well
> taken.
>
> It's quite clear that it is generically bad to make these sorts of
> inferences from addresses.  That's good information.
>
> The question I'm now interested in answering is whether using these as
> part of a heuristic in order to limit the scope of a change like the
> proposed is tolerable.
>
> The goal here is to close off a security loophole in how browser make
> request for a tiny slice of the total set of requests that are made.  The
> ultimate goal might be to remove the loopholes uniformly.  However, that
> would break so much stuff that a change like that would never stick.  This
> is a more narrowly-scoped approach that tries to identify conditions where
> the requests are a) more dangerous in general, and b) rare enough that any
> breaks would not be widely felt.
>
> I've pointed out some of the limitations of this approach (and several
> more have been identified, thanks!), but I haven't seen reasons here why a
> heuristic like that proposed would be strictly problematic.  Assuming that
> these shortcoming are acknowledged properly (they are not currently) is
> there any reason not to use some sort of address-based heuristic for this
> sort of purpose?
>
> I can see how building on top of this simplistic base for other purposes
> might be harmful, but is the specific action being taken inherently bad, or
> is it just not very good?  It not being very good is a totally fair
> criticism, but that will be balanced against the apparent utility here.
> This design protects the badly-secured router provided by my ISP from
> requests from the big bad Internet.  That is a tangible outcome against
> which "addressing is more complex than this design allows for" doesn't
> weigh very heavily.
>
> > First, I'm not a huge fan
> > of "ask the user" in decisions that rely on an understanding of opaque
> > inner workings of the net, and this runs that risk.
>
> I made the same comment myself.  "Not a huge fan" doesn't really cover it
> :)  I think that the "ask the user" provisions here are entirely
> misguided.  Thankfully, my understanding is that this might be implemented
> without any such controls, which would be good - at least to the extent
> that you are not happy with "ask the user" as a component in any design.
>
> Eliot raised the converse question about consent, which is to say, is
> there an override so that users can enable access to stuff that doesn't
> provide consent on its own, such as old gear.  I agree that this would be
> desirable and made similar comments; I don't know what provision is being
> made there though.
>
> > Second, I don't understand the intended client behavior
> > here if it accesses web resources via a proxy, and I didn't find any
> > mention of proxy behavior in the text.  Text about this in the final
> > document would be useful.
>
> Good point; I had not considered that, but I believe that this does not
> make special provisions for proxies.  This protection would apply if proxy
> configuration says not to use a proxy, I think.  However, this could not
> apply if the vulnerable server were contacted via proxy, that is true.
>
> > This is especially true in the
> > unfortunately large number of organizations who have repurposed
> > unrouted addresses as "extra" private address space
> > (https://teamarin.net/2015/11/23/to-squat-or-not-to-squat/ is old, but
> > the practice is far from dead).
>
> Oh yeah, I had forgotten about that.  Another good point to add to those
> Brian makes.
>

Those notes are destined to go to W3C, in some way?

I had the privilege of including "The People Who Were Unable to See the
Elephant" in
https://datatracker.ietf.org/doc/html/draft-dawkins-quic-multipath-questions-01#section-1.1
last year, and that's what this conversation feels like - I wouldn't mind
seeing the final list of comments ("this is what the private addressing
elephant looks like") after everyone finishes reporting on what they know.

There seems to be a lot to report, and the discussion seems to be jogging
the understanding of some pretty experienced people.

Best,

Spencer

--0000000000003be1b205beeaecf7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I shouldn&#39;t ask, but I&#39;d feel worse if I didn=
&#39;t.=C2=A0</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D=
"gmail_attr">On Wed, Mar 31, 2021 at 6:53 PM Martin Thomson &lt;<a href=3D"=
mailto:mt@lowentropy.net" target=3D"_blank">mt@lowentropy.net</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks everyon=
e for the insights.<br>
<br>
I&#39;ll reply to Ted as he hit the crux of the issue most adroitly...<br>
<br>
On Wed, Mar 31, 2021, at 20:07, Ted Hardie wrote:<br>
&gt; What I think this proposal would actually like to do is to determine <=
br>
&gt; whether a resource referenced by a specific web server would also be <=
br>
&gt; reachable by that server.=C2=A0 <br>
<br>
That&#39;s exactly it.<br>
<br>
Brian&#39;s point about the inherent folly of making such guesses is well t=
aken.<br>
<br>
It&#39;s quite clear that it is generically bad to make these sorts of infe=
rences from addresses.=C2=A0 That&#39;s good information.<br>
<br>
The question I&#39;m now interested in answering is whether using these as =
part of a heuristic in order to limit the scope of a change like the propos=
ed is tolerable. <br>
<br>
The goal here is to close off a security loophole in how browser make reque=
st for a tiny slice of the total set of requests that are made.=C2=A0 The u=
ltimate goal might be to remove the loopholes uniformly.=C2=A0 However, tha=
t would break so much stuff that a change like that would never stick.=C2=
=A0 This is a more narrowly-scoped approach that tries to identify conditio=
ns where the requests are a) more dangerous in general, and b) rare enough =
that any breaks would not be widely felt.<br>
<br>
I&#39;ve pointed out some of the limitations of this approach (and several =
more have been identified, thanks!), but I haven&#39;t seen reasons here wh=
y a heuristic like that proposed would be strictly problematic.=C2=A0 Assum=
ing that these shortcoming are acknowledged properly (they are not currentl=
y) is there any reason not to use some sort of address-based heuristic for =
this sort of purpose?<br>
<br>
I can see how building on top of this simplistic base for other purposes mi=
ght be harmful, but is the specific action being taken inherently bad, or i=
s it just not very good?=C2=A0 It not being very good is a totally fair cri=
ticism, but that will be balanced against the apparent utility here.=C2=A0 =
This design protects the badly-secured router provided by my ISP from reque=
sts from the big bad Internet.=C2=A0 That is a tangible outcome against whi=
ch &quot;addressing is more complex than this design allows for&quot; doesn=
&#39;t weigh very heavily.<br>
<br>
&gt; First, I&#39;m not a huge fan <br>
&gt; of &quot;ask the user&quot; in decisions that rely on an understanding=
 of opaque <br>
&gt; inner workings of the net, and this runs that risk.=C2=A0 <br>
<br>
I made the same comment myself.=C2=A0 &quot;Not a huge fan&quot; doesn&#39;=
t really cover it :)=C2=A0 I think that the &quot;ask the user&quot; provis=
ions here are entirely misguided.=C2=A0 Thankfully, my understanding is tha=
t this might be implemented without any such controls, which would be good =
- at least to the extent that you are not happy with &quot;ask the user&quo=
t; as a component in any design.<br>
<br>
Eliot raised the converse question about consent, which is to say, is there=
 an override so that users can enable access to stuff that doesn&#39;t prov=
ide consent on its own, such as old gear.=C2=A0 I agree that this would be =
desirable and made similar comments; I don&#39;t know what provision is bei=
ng made there though.<br>
<br>
&gt; Second, I don&#39;t understand the intended client behavior <br>
&gt; here if it accesses web resources via a proxy, and I didn&#39;t find a=
ny <br>
&gt; mention of proxy behavior in the text.=C2=A0 Text about this in the fi=
nal <br>
&gt; document would be useful.<br>
<br>
Good point; I had not considered that, but I believe that this does not mak=
e special provisions for proxies.=C2=A0 This protection would apply if prox=
y configuration says not to use a proxy, I think.=C2=A0 However, this could=
 not apply if the vulnerable server were contacted via proxy, that is true.=
<br>
<br>
&gt; This is especially true in the <br>
&gt; unfortunately large number of organizations who have repurposed <br>
&gt; unrouted addresses as &quot;extra&quot; private address space <br>
&gt; (<a href=3D"https://teamarin.net/2015/11/23/to-squat-or-not-to-squat/"=
 rel=3D"noreferrer" target=3D"_blank">https://teamarin.net/2015/11/23/to-sq=
uat-or-not-to-squat/</a> is old, but <br>
&gt; the practice is far from dead).<br>
<br>
Oh yeah, I had forgotten about that.=C2=A0 Another good point to add to tho=
se Brian makes.<br></blockquote><div><br></div><div>Those notes are destine=
d to go to W3C, in some way?</div><div><br></div><div>I had the privilege o=
f including &quot;The People Who Were Unable to See the Elephant&quot; in <=
a href=3D"https://datatracker.ietf.org/doc/html/draft-dawkins-quic-multipat=
h-questions-01#section-1.1">https://datatracker.ietf.org/doc/html/draft-daw=
kins-quic-multipath-questions-01#section-1.1</a> last year, and that&#39;s =
what this conversation feels like - I wouldn&#39;t mind seeing the final li=
st of comments (&quot;this is what the private addressing elephant looks li=
ke&quot;) after everyone finishes reporting on what they know.=C2=A0</div><=
div><br></div><div>There seems to be a lot to report, and the discussion se=
ems to be jogging the understanding of some pretty experienced people.=C2=
=A0</div><div><br></div><div>Best,</div><div><br></div><div>Spencer</div></=
div></div>

--0000000000003be1b205beeaecf7--


From nobody Thu Apr  1 09:15:39 2021
Return-Path: <mcr@sandelman.ca>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 704073A1A44 for <architecture-discuss@ietfa.amsl.com>; Thu,  1 Apr 2021 09:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 XX4WbQ1dgHUU for <architecture-discuss@ietfa.amsl.com>; Thu,  1 Apr 2021 09:15:31 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D43D03A1A41 for <architecture-discuss@ietf.org>; Thu,  1 Apr 2021 09:15:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 6C90D39151; Thu,  1 Apr 2021 12:21:56 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Dq9Tbx-d6P8k; Thu,  1 Apr 2021 12:21:55 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id AB12239149; Thu,  1 Apr 2021 12:21:55 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 8CD968EE; Thu,  1 Apr 2021 12:15:28 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Ted Hardie <ted.ietf@gmail.com>, Erik Kline <ek.ietf@gmail.com>, architecture-discuss@ietf.org
In-Reply-To: <20210331221054.GG8957@faui48f.informatik.uni-erlangen.de>
References: <4329d51a-d5ba-45b3-9fb0-6795dc6fccd3@www.fastmail.com> <CAMGpriWA4B8AThNKBOHo-bfAdQ2s5iYv8rBOB7X8UVc5GsqENA@mail.gmail.com> <CAMGpriUJkWYPyw7=oAj_GnGu2J14T3=VZYNWPZtAs870P=x0sg@mail.gmail.com> <a68636c2-5df0-46eb-8147-79ec6a992f8a@www.fastmail.com> <CAMGpriU_L8HbLFX_mMBtBXxy=XOc5BAnYgVR9R8TQO=DPvRD_g@mail.gmail.com> <F59E2FC3-19CE-4D14-9F1C-9F7125D89455@mnot.net> <CAMGpriVJCsird15oBfT=gSDTr59_yf9TkLmOSO7a9DGX0VRjOg@mail.gmail.com> <CA+9kkMB2iOA-QaCidJHVN=qqZ8TtPXV=xyfuKh+i44VzZLWG3w@mail.gmail.com> <0cfae1b5-378d-1b28-9a60-89ef15cd793a@gmail.com> <20210331221054.GG8957@faui48f.informatik.uni-erlangen.de>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <17555.1617293728.1@localhost>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 01 Apr 2021 12:15:28 -0400
Message-ID: <17556.1617293728@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/kk3neTko5tvlnalW5MXf3z7NK_M>
Subject: Re: [arch-d] Treating "private" address ranges specially
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Apr 2021 16:15:36 -0000

Toerless Eckert <tte@cs.fau.de> wrote:
    > c) There is actually (IMHO) a good discussion that should be had abo=
uut
    > how browser security could
    > better support the needs of limited domains (rfc8799), but i fear th=
e mayority of contributors
    > to w3c / browser security in ietf still think everything required is=
 just what fits the global
    > Internet web-pki and Internet cloud services centric browser securit=
y
    > architecture we have today.

There is a SIG of IOTSecurityFoundation called manysecured, which is
attempting to have this conversation.

   https://manysecured.net/


From nobody Thu Apr  1 13:29:09 2021
Return-Path: <mt@lowentropy.net>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 570523A2241 for <architecture-discuss@ietfa.amsl.com>; Thu,  1 Apr 2021 13:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=lowentropy.net header.b=cwnY/mYm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ADYtN2VT
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 2iU0QiQ_a7qG for <architecture-discuss@ietfa.amsl.com>; Thu,  1 Apr 2021 13:29:03 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67C493A2240 for <architecture-discuss@ietf.org>; Thu,  1 Apr 2021 13:29:03 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8EEEA5C0091; Thu,  1 Apr 2021 16:29:02 -0400 (EDT)
Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Thu, 01 Apr 2021 16:29:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm1; bh=471hBX/jUcyEiI4uVR6/n+uaGiuh Mdm6jdR0KXX1Rxg=; b=cwnY/mYmXoJRKLnsWdM3CyBfcwRZujXV5NLJFKf5xjzj XxA7hj5n9jkMpQ6gSrGoyyNklGVZI6kiRCfmL/yk/EaC47LcQG7YsHVp4MlO+WD9 Q1yhM6DgbyyCuHex20so09kXOjBjIeonDvpihoEDLbNoknS15bZRsV0T+hW1PGsm qXyY8XU55swBGOfCQpWWVzfpyhlYZYy5jgecc4MJFOT2umqt6FK8g9KpaXe3S6xK V1+XEpTo3lAr4+qxCBKCEJo3wPKbnUdgM2ivZB+vth/TycH+jJr1zsU5VI7rhS3F W8Vxiv0dwNBsa+8O5P9kidzP87Ojido4ONqb8pVXkQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=471hBX /jUcyEiI4uVR6/n+uaGiuhMdm6jdR0KXX1Rxg=; b=ADYtN2VTEFXQwOwIeBwXQq S0kK43/8oZm0pIP0VPWg3mEIe41CQBdbtJUNY6nOXdxVg74WDziD3F2dCt7IkgFH lW5+8RC1FZDsl7qkZInb186otbIGtK742SxAU/MDRXPnS6Kg9rGQVQu0Pvp9QX/B uo0CTTqrziedAtoOIZ2TiOBGMfTLvJJsBeAfWpgvvI1NqLIp2ykxoygzEd8t3Itp ZJP7YRnWzJGsYI4684i87Dy69rIaCdHRsS7BBK/xX84LpLYEjGL9HHzoLk8cO/28 a5ouPSo0sGIIV7KfmKeJGeZHfpD9sdBQ2hulZQXSC8NmErwnm+XJz6PAEokt4fOA ==
X-ME-Sender: <xms:DS1mYPafXnmGPgSekdnI0c_62CYipY8p9n9dEDarJAe6NQUm7oB3sQ> <xme:DS1mYOY7v8MhZ_xgxAU5cDSbgx4QKxNLUB9J3E0ci9bGOnAGYck43P9m7Q5OzBJab mfVzpvBgvz07uUVgrk>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeigedgudegudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfofgr rhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigvnhhtrhhophihrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtgefhkeegfffhteefjeekveefteehheelgeehheevleefteef ieekfefgjedvgeenucffohhmrghinhepghhithhhuhgsrdgtohhmnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhp hidrnhgvth
X-ME-Proxy: <xmx:DS1mYB99pcv1P7v6JdWlZZ1VjemUzjrUwLOhuoNsIb4qOkJ9IlrIFA> <xmx:DS1mYFqMV-PsQFvnS_ArlqpoOKYKqbnwIESU_xlEzKwJUndVEh1aXQ> <xmx:DS1mYKpimx8mtBW0AZFgll5IUSYftwTrxctZrbOkBxGNA3bVdMfZFQ> <xmx:Di1mYIHF3POa5FXlNoGlPx_EWhk0ixPqU3Qxw8J5l1AjHK8KjfU0gg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id E399D4E02B7; Thu,  1 Apr 2021 16:29:01 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-273-g8500d2492d-fm-20210323.002-g8500d249
Mime-Version: 1.0
Message-Id: <24de9a74-5f57-4328-aa0a-6dab888025d2@www.fastmail.com>
In-Reply-To: <CAKKJt-c8SsHLu+0F3czh8sx2uFnTOZEE_FXZXAAwHsnYxDVVPw@mail.gmail.com>
References: <4329d51a-d5ba-45b3-9fb0-6795dc6fccd3@www.fastmail.com> <CAMGpriWA4B8AThNKBOHo-bfAdQ2s5iYv8rBOB7X8UVc5GsqENA@mail.gmail.com> <CAMGpriUJkWYPyw7=oAj_GnGu2J14T3=VZYNWPZtAs870P=x0sg@mail.gmail.com> <a68636c2-5df0-46eb-8147-79ec6a992f8a@www.fastmail.com> <CAMGpriU_L8HbLFX_mMBtBXxy=XOc5BAnYgVR9R8TQO=DPvRD_g@mail.gmail.com> <F59E2FC3-19CE-4D14-9F1C-9F7125D89455@mnot.net> <CAMGpriVJCsird15oBfT=gSDTr59_yf9TkLmOSO7a9DGX0VRjOg@mail.gmail.com> <CA+9kkMB2iOA-QaCidJHVN=qqZ8TtPXV=xyfuKh+i44VzZLWG3w@mail.gmail.com> <c88bbb17-4a30-4241-af98-436ddf01ca5c@www.fastmail.com> <CAKKJt-c8SsHLu+0F3czh8sx2uFnTOZEE_FXZXAAwHsnYxDVVPw@mail.gmail.com>
Date: Fri, 02 Apr 2021 07:28:41 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: "Spencer Dawkins at IETF" <spencerdawkins.ietf@gmail.com>
Cc: architecture-discuss@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/FaeX2MxLFcGzF2rKiekEHlWAkuw>
Subject: Re: [arch-d] Treating "private" address ranges specially
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Apr 2021 20:29:08 -0000

On Fri, Apr 2, 2021, at 02:30, Spencer Dawkins at IETF wrote:
> Those notes are destined to go to W3C, in some way?

This is in response to a request from the TAG for consideration.  It's part of a review they are conducting here: https://github.com/w3ctag/design-reviews/issues/572

I've referenced Ted's recent summary in that thread, so I think that the feedback thus far has been received.

I don't think that the TAG would object to receiving more comments there if they add new information, but it seems like most of the key points have been covered already.


From nobody Wed Apr  7 14:39:25 2021
Return-Path: <execd@iab.org>
X-Original-To: architecture-discuss@ietf.org
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7C23A2AAF; Wed,  7 Apr 2021 14:39:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IAB Executive Administrative Manager <execd@iab.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: architecture-discuss@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.27.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: architecture-discuss@ietf.org, iab@iab.org
Message-ID: <161783156502.9164.12605972874915695547@ietfa.amsl.com>
Date: Wed, 07 Apr 2021 14:39:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/Ka7ABdiDvj-2OzahFbNhftad9II>
Subject: [arch-d] IAB Adoption of draft-iana-arpa-authoritative-servers-02
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Apr 2021 21:39:25 -0000

The IAB will discuss adoption of draft-iana-arpa-authoritative-
servers-02 (Nameservers for the Address and Routing Parameter Area 
("arpa") Domain) at its meeting on 2021-04-21.

The draft can be found here: 
https://datatracker.ietf.org/doc/draft-iana-arpa-authoritative-servers/

The agenda for the meeting will be posted 48 hours ahead of the meeting 
here: https://www.iab.org/wiki/index.php/Agenda

Feedback about this draft can be sent in response to this mail on 
architecture-discuss@ietf.org, or to the IAB directly at iab@iab.org.


From nobody Wed Apr  7 23:01:52 2021
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD733A3B3C for <architecture-discuss@ietfa.amsl.com>; Wed,  7 Apr 2021 23:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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=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 m1HbFqNYNuYq for <architecture-discuss@ietfa.amsl.com>; Wed,  7 Apr 2021 23:01:45 -0700 (PDT)
Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (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 7ECA03A3B3B for <architecture-discuss@ietf.org>; Wed,  7 Apr 2021 23:01:43 -0700 (PDT)
Received: by mail-yb1-xb34.google.com with SMTP id x189so1384703ybg.5 for <architecture-discuss@ietf.org>; Wed, 07 Apr 2021 23:01:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TMg+EQxQ1/23LC+F9154qQiM8i4ZvchCsvFTWXJynXs=; b=Yvk8QFa/X+bcUU3pP1+KFdR6ZEzm6JMjEFVn3OsKbb+GsgAlOUnwAI14XTNq1YIRJc x9I7EnzVPCbjWgIm8ASYVsn/TNrq1lcd/699RIeGZ7BGxINKuHllLWuvPhPT9MWhaVu7 ZPCKbfaUuM0MIe8vRfyZTRVlb/uL9161ZOhcQRkECiBP7vKaNZriZIcHHvbRIEAguRK+ mhKfwiaxvsp+fDXp5SDXEWvy2UMDNWryfoWYwJOjFsss3drftxki9yYslnPRyDmF9lUn MNEgqk3+xZH3Wv/TFmGDr22XHqMltincTt1RditnhACiPvzQTBUjnWwZzI3CfxOU0v+l ujhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TMg+EQxQ1/23LC+F9154qQiM8i4ZvchCsvFTWXJynXs=; b=tivg5Rzqwwgu1WS0KMfDB+dooF5hqCazVqf3vOCg37Cq4i/6wCmY2acCCaurpTDCqB okgM2ljoqQ/A1mXhHWDb9QJ+8Mdv6Sq8tAWTD7AhjLs6wj/JMuvOUcJcwO5wodtvdVEQ 49+vlhMTTJ/iq17EzgIyzlyMVrE+9ngiViy9z2CBs+MqfCHH+eObZeJxVnV7mP62RT25 1CM8xVwCaeDJxlxODGyNE5vk53/eiSDfSuyFaXvMfrb6WQasMRxYga5VyAT7D+hLwxQT IbeJfkNf21oYraj4wju4bW1T5ZWUJb1Sun7q0TxNVAEMXEHceNSSqU5iGclMs1Itx/kh wFyg==
X-Gm-Message-State: AOAM5322bB80LaGPxj7UnrQI0jW3v15obNL/byPigy2Rf44WvqV23vt/ oQuW5R8JQiUZPEaR7fMF6jzaqhsp221unl0sD19CSGuZ
X-Google-Smtp-Source: ABdhPJyL88fEeqtKKVXvGf/GcA3N+n0rGdFCrG54dyDNndm+XbYEbtkBG4yU1TZp+pSVxQwRqLAEEkDNttmWW2kWi6A=
X-Received: by 2002:a25:fc4:: with SMTP id 187mr9843267ybp.84.1617861700645; Wed, 07 Apr 2021 23:01:40 -0700 (PDT)
MIME-Version: 1.0
References: <4329d51a-d5ba-45b3-9fb0-6795dc6fccd3@www.fastmail.com> <CAMGpriWA4B8AThNKBOHo-bfAdQ2s5iYv8rBOB7X8UVc5GsqENA@mail.gmail.com> <CAMGpriUJkWYPyw7=oAj_GnGu2J14T3=VZYNWPZtAs870P=x0sg@mail.gmail.com> <a68636c2-5df0-46eb-8147-79ec6a992f8a@www.fastmail.com> <CAMGpriU_L8HbLFX_mMBtBXxy=XOc5BAnYgVR9R8TQO=DPvRD_g@mail.gmail.com> <F59E2FC3-19CE-4D14-9F1C-9F7125D89455@mnot.net> <CAMGpriVJCsird15oBfT=gSDTr59_yf9TkLmOSO7a9DGX0VRjOg@mail.gmail.com> <CA+9kkMB2iOA-QaCidJHVN=qqZ8TtPXV=xyfuKh+i44VzZLWG3w@mail.gmail.com> <c88bbb17-4a30-4241-af98-436ddf01ca5c@www.fastmail.com> <CAKKJt-c8SsHLu+0F3czh8sx2uFnTOZEE_FXZXAAwHsnYxDVVPw@mail.gmail.com> <24de9a74-5f57-4328-aa0a-6dab888025d2@www.fastmail.com>
In-Reply-To: <24de9a74-5f57-4328-aa0a-6dab888025d2@www.fastmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 8 Apr 2021 01:01:14 -0500
Message-ID: <CAKKJt-e51KosuYJEZkaXMpAOPv0QnbfM4_+nCVcNyKTxwA8NeA@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: architecture-discuss@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f6778305bf6fc7aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/NfrDFuOxbvgk9Xj0mHWIFlNMUog>
Subject: Re: [arch-d] Treating "private" address ranges specially
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2021 06:01:51 -0000

--000000000000f6778305bf6fc7aa
Content-Type: text/plain; charset="UTF-8"

Martin,

My apologies for not hitting "send" sooner, but I wanted to thank you for
this answer. It was helpful.

Best,

Spencer

On Thu, Apr 1, 2021 at 3:29 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Fri, Apr 2, 2021, at 02:30, Spencer Dawkins at IETF wrote:
> > Those notes are destined to go to W3C, in some way?
>
> This is in response to a request from the TAG for consideration.  It's
> part of a review they are conducting here:
> https://github.com/w3ctag/design-reviews/issues/572
>
> I've referenced Ted's recent summary in that thread, so I think that the
> feedback thus far has been received.
>
> I don't think that the TAG would object to receiving more comments there
> if they add new information, but it seems like most of the key points have
> been covered already.
>

--000000000000f6778305bf6fc7aa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Martin,=C2=A0<div><br></div><div>My apologies for not hitt=
ing &quot;send&quot; sooner, but I wanted to thank you for this answer. It =
was helpful.</div><div><br></div><div>Best,</div><div><br></div><div>Spence=
r</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Thu, Apr 1, 2021 at 3:29 PM Martin Thomson &lt;<a href=3D"mailto:=
mt@lowentropy.net">mt@lowentropy.net</a>&gt; wrote:<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex">On Fri, Apr 2, 2021, at 02:30, Spencer =
Dawkins at IETF wrote:<br>
&gt; Those notes are destined to go to W3C, in some way?<br>
<br>
This is in response to a request from the TAG for consideration.=C2=A0 It&#=
39;s part of a review they are conducting here: <a href=3D"https://github.c=
om/w3ctag/design-reviews/issues/572" rel=3D"noreferrer" target=3D"_blank">h=
ttps://github.com/w3ctag/design-reviews/issues/572</a><br>
<br>
I&#39;ve referenced Ted&#39;s recent summary in that thread, so I think tha=
t the feedback thus far has been received.<br>
<br>
I don&#39;t think that the TAG would object to receiving more comments ther=
e if they add new information, but it seems like most of the key points hav=
e been covered already.<br>
</blockquote></div>

--000000000000f6778305bf6fc7aa--


From nobody Thu Apr  8 01:25:46 2021
Return-Path: <kolkman@isoc.org>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3AC53A3FFB for <architecture-discuss@ietfa.amsl.com>; Thu,  8 Apr 2021 01:25:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.3
X-Spam-Level: 
X-Spam-Status: No, score=0.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MSGID_FROM_MTA_HEADER=0.001, PDS_OTHER_BAD_TLD=1.999, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=isoc.org
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 DhDwDUDurR2D for <architecture-discuss@ietfa.amsl.com>; Thu,  8 Apr 2021 01:25:40 -0700 (PDT)
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10on2055.outbound.protection.outlook.com [40.107.94.55]) (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 1E1E13A3FF0 for <architecture-discuss@ietf.org>; Thu,  8 Apr 2021 01:25:40 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TP0oK6SwgO05sTe8ukM6O9/quC98gBNrgCdzFjaSC0kf/s9gDDvf0yE5i5Z8GO9pJoMWlFDVir6PR/lfxShUa1noFIL7Hmrh3PZNcvkMSdVqZGa/FjokTw2GkmyI10gRREwvJl3lBbx0yGnWr1FLl9f7BpMehJoZkzE/rDAmm8Q0qmPXcZ8BzSDP46C3lEuQVz8YnTKafKaPCReMCWvq4KfRawi0THFIdRDrOJMdgf7EeIDVVE0+jGrP2k3RXKIjp34q90lZJY+N6rx65dUAGr2xFp2n+JeOPoziZzavMYoxQxO1dybUTnRDjXlbdSJH2f/MEg2xIW+/WzX8smMe3Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KqTRkOO0Eb5OEQJqGy7IW60Q75TZiUmNfyKbqJfCcRQ=; b=f+UvjyKUVHBslDGBAQo+btTc0WEj73LbP6ZGhPZLfRm7UbtPTTYkoOJ9lM4iRTJzFlpIknI36zlX9NS9UqzZA4YwzCRdwl+fz88WorR/6K+/05pHsTSE09Xt7lZ3pUovUt5CH1uV801W7TpPcN2IkpdRcbMoZwQU8buKOVP/K0OdSEb+pJjcZb8kNFqHgR+QlEBuSB6oq41g5lN/VnGUdSS8vnbLVq3VfTVQs4PXQjUVEZ2m2qRcbZlKzShVMjm3bEMWp+U1cmuR2eLEb5nsniM5BgNnKhuEzwcmQkQDopcbXaexKbNTCAATVyWWyoL823pPN/ne689XVgYKAAs0Xw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=isoc.org; dmarc=pass action=none header.from=isoc.org; dkim=pass header.d=isoc.org; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector2;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KqTRkOO0Eb5OEQJqGy7IW60Q75TZiUmNfyKbqJfCcRQ=; b=niv1GLXOaZ8ukELpB+qHhHUUynn9O4LE2p82NjVtaiFg7Fef/5O5NBa8GvcI2yEox4T8bQMLhp/VodCQ04r0RU/8BUt/zpQoN4gEWDTgMbRTVWnkgjTv3z7UBmAWYhRVOhR8eWkXBZhEqG74ONAmTQwqt7ElNLoF5eWLuDBeuY8=
Authentication-Results: huitema.net; dkim=none (message not signed) header.d=none;huitema.net; dmarc=none action=none header.from=isoc.org;
Received: from BYAPR06MB5336.namprd06.prod.outlook.com (2603:10b6:a03:c6::29) by SJ0PR06MB6832.namprd06.prod.outlook.com (2603:10b6:a03:278::6) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4020.18; Thu, 8 Apr 2021 08:25:35 +0000
Received: from BYAPR06MB5336.namprd06.prod.outlook.com ([fe80::5dc7:7c0c:5f9b:90f9]) by BYAPR06MB5336.namprd06.prod.outlook.com ([fe80::5dc7:7c0c:5f9b:90f9%3]) with mapi id 15.20.3999.032; Thu, 8 Apr 2021 08:25:35 +0000
From: "Olaf Kolkman" <kolkman@isoc.org>
To: "Christian Huitema" <huitema@huitema.net>
Cc: "Martin Thomson" <mt@lowentropy.net>, architecture-discuss@ietf.org
Date: Thu, 08 Apr 2021 10:25:28 +0200
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <444673BB-8C10-4AA0-9995-857398D43E23@isoc.org>
In-Reply-To: <8195e468-6507-e500-4a25-fcd90f81e759@huitema.net>
References: <4329d51a-d5ba-45b3-9fb0-6795dc6fccd3@www.fastmail.com> <CAMGpriWA4B8AThNKBOHo-bfAdQ2s5iYv8rBOB7X8UVc5GsqENA@mail.gmail.com> <CAMGpriUJkWYPyw7=oAj_GnGu2J14T3=VZYNWPZtAs870P=x0sg@mail.gmail.com> <a68636c2-5df0-46eb-8147-79ec6a992f8a@www.fastmail.com> <CAMGpriU_L8HbLFX_mMBtBXxy=XOc5BAnYgVR9R8TQO=DPvRD_g@mail.gmail.com> <F59E2FC3-19CE-4D14-9F1C-9F7125D89455@mnot.net> <CAMGpriVJCsird15oBfT=gSDTr59_yf9TkLmOSO7a9DGX0VRjOg@mail.gmail.com> <CA+9kkMB2iOA-QaCidJHVN=qqZ8TtPXV=xyfuKh+i44VzZLWG3w@mail.gmail.com> <c88bbb17-4a30-4241-af98-436ddf01ca5c@www.fastmail.com> <2c2367b2-bbe1-7d4d-9edd-c7975420a540@huitema.net> <955f0978-7416-4d20-9d8a-27dace821092@www.fastmail.com> <8195e468-6507-e500-4a25-fcd90f81e759@huitema.net>
Content-Type: multipart/signed; boundary="=_MailMate_D91FF869-DCF6-41DA-A1D5-219B745607B0_="; micalg=pgp-sha512; protocol="application/pgp-signature"
X-Originating-IP: [2a10:3781:5a:1:113f:6df0:4c68:9111]
X-ClientProxiedBy: AM9P195CA0027.EURP195.PROD.OUTLOOK.COM (2603:10a6:20b:21f::32) To BYAPR06MB5336.namprd06.prod.outlook.com (2603:10b6:a03:c6::29)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [169.254.233.172] (2a10:3781:5a:1:113f:6df0:4c68:9111) by AM9P195CA0027.EURP195.PROD.OUTLOOK.COM (2603:10a6:20b:21f::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4020.18 via Frontend Transport; Thu, 8 Apr 2021 08:25:33 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: da7d5162-eea0-4b0e-1f82-08d8fa67e145
X-MS-TrafficTypeDiagnostic: SJ0PR06MB6832:
X-Microsoft-Antispam-PRVS: <SJ0PR06MB6832DCD845A26451F3317200D9749@SJ0PR06MB6832.namprd06.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:7691;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: YzTpBMkH5j3qyiLukD1LLNmdRhFCBKvV9VVqtrpqg2yRBYv9RnAZ9YWgbwtgHpxnHzGZ1Z1RsThp7m6RLZ1tzRHzBIcngGD4ReuyU2xKwEnpTJtFink4ATMNSvi8dyeX5eIEbg2irVKdWT/uDXSuxJYHmq4qf4/7s2uBnc4SQx3UPfXJ1FylFFiRuYqj4Snn9HZK+QjagUGgPMtg4YXpdXHnjkQlbV+T4s7INW5b7L2s4vLzIPYB8VnoQw03eODGLwYBBhCFHmzkYdPWJf1r/++0ggc+9IhgAkeQ3dhkjG6b8EK+3O+5q1uFP9F+yajH6ya/PRceb3R25s4ijcCtLLPCFhKa5ZRwSmOWfUeGu7E20DkTmas0FR8tkjLmDoDKcEY7i/GGJDBAH3zQDWCwcfqOwzYTQZclGwPXOWZ6Q5swaofWkgP5HjrJaIMTFVDm71uikczLOnZ6jOQgbx4hzaBI7NF03C05Y32zAhl5BEv7IVnVHXQcTsg1CjlKz0ueSUeF5eVrena6ZIO2Xep7eeWHGBKglEmYuWhMOZ3wfZuUYCAMsLJ/0ZtPMWaH/YRBYnwnJHrmUxIxl5QCa94by0ogY+zuYM3yw125Xhe3c8F76r7OXSGy8T5VU7sgC0Xs4FNzzRactSq0CwTkbGUkH7SLvtw+aBTqskTiYIIo3V772z4OmVNn4EqDL7tEOQX2wrTeDd5+V2la/KKxZEW+JaFE+uFyP+J4i8fnFXKxm4X7hnT4JHd5Uyj56LVLtPaRxb+P4cio+1VmoNIFFpdA3XNAiNj7Pgt2bwZRymHt+flvTfABeXVkoHIA0apCjUgW
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BYAPR06MB5336.namprd06.prod.outlook.com; PTR:; CAT:NONE;  SFS:(366004)(346002)(376002)(396003)(39850400004)(136003)(66476007)(66946007)(66556008)(478600001)(4326008)(86362001)(36756003)(33656002)(166002)(316002)(2906002)(2616005)(966005)(5660300002)(8676002)(235185007)(6916009)(8936002)(52116002)(33964004)(6666004)(6486002)(186003)(38100700001)(16526019)(78286007)(45980500001)(72826003); DIR:OUT; SFP:1101; 
X-MS-Exchange-AntiSpam-MessageData: =?utf-8?B?bGs0WENUNUJGbVNiRTFIbThjangxRWQvRHh4QSsxZFpDUHRsbzc1OWY5Vk4z?= =?utf-8?B?cDdEbnZmc1R6eDdDZGRxZllQKzdXTHBXdUtFdGh1WWFkbTAyQ0ZuVTBkclBt?= =?utf-8?B?VkFZQmRhcUEwRGhrUDZJemh1RlJadFdJUjFydU5ucU9vZnMrTTB4OFJhT1pN?= =?utf-8?B?dC9jam5jNUFCRnl3a1E3OG5lQTIvVi9Oek5uTmhEZGh1OGsrOFNZbHB6RHpG?= =?utf-8?B?dGgrbk5nbTdsV015UEMyM2lvRjVPTTRIak9RVlQwU0MzS3RIKzhGQVc1TWFS?= =?utf-8?B?UGp2ZklnaW5CSzVDVGdJSVY5UjNXdnBvZGhONDRuZy8wUDRkMEZXOFUzenZU?= =?utf-8?B?Z3VqNUI3MG80WVkvdjZQVlZScDQyTHYra0NqTlNyaVlFWm1SUEc1cmt6Ty9Y?= =?utf-8?B?dGJBMDVFYVB3dFFFV0hCR1hWQXNNZGV0R1RJNkxTTVRnclU2U1RHNHVnaFlk?= =?utf-8?B?a3BBT1JyUnNrV3ZNYTdMYVlNSEtYemVpZS83eE9qQ0dZS1ZMeHV1VWM3dzZr?= =?utf-8?B?WWR1REpVOVJoRUVvbyt4SlJhMDQrNkZ1MnR5eGh4YnFwVDRzTW44b1VjdkdH?= =?utf-8?B?TWRNN08xNnpUWEJPbVMwMkFYN1hjUHU2WFdNc1RZR1dyNnhtWms0bzlCSnY3?= =?utf-8?B?YjBLZWEySkx1WDMrWUE5SW56M1lHTTFudGYrNUYwbVJJNHF5VkVQNnRNWjYr?= =?utf-8?B?MVFaa21xbXcvYkc1YWV4aGg4MUFXWlpSQ0ZzVERmcUNnMTJwTGFnMUpjdGNz?= =?utf-8?B?YnlqL3phUkM3cW5ybU1hSkRic3orUC8zMll4bEdTTmpGTFlPL2ZMQXV0U2U4?= =?utf-8?B?eHpNZHBONm9YNUFmMVR6bGtMczJjTWhUdE12V0IxVFd5MjhLdTdjZW5tSWNO?= =?utf-8?B?MHIrRldWbjlqcExzU3dtNHYrTU54OUh2QXViNUN1MUVYZVAreWU5MUlhK0py?= =?utf-8?B?Y3pSMTA4RU9ibDJ5OVZvZXpGMDZUV29PZnF6MldOZS91ajJXVEVDc2krd2VC?= =?utf-8?B?V3B6dVJDYU9OdG0wRGU2VG1FWEo0OFBBb3pUYnk0MzNFdDhVYnEzOEtuWVpx?= =?utf-8?B?azMyQit3L0tWK3d4cEM3S1hZY1Y2ek1taVMrblRIMjRMNTltci9YWXJSUXJQ?= =?utf-8?B?MkNHN3drdG9oMGVuUWt1ZnBRQjJxcUQwdjFxbW9uSnRDMXdVQWlxZGZjUEkz?= =?utf-8?B?Vnd5WkxEYnRlM3k1ejJPdnpDWmdQczE2QThPS0Q3U0lwb25jVDdBVU9WRnE2?= =?utf-8?B?amxOaDY2bDEwYjJOUGZOSkZDSWM0RUt1endXQmVUcm9HcW01UmxvaTJXQ1l0?= =?utf-8?B?NXVwYnoyMTdxdllBYllSbVg2U0U3TUFFK2VRSFJSOHA4VTRHeVlyR1M4UW94?= =?utf-8?B?VkRhQmhBaEdFdWx6aFl3QlFBZXZucnZDSTZ5T0Z2ZEJhWndYY1pTNnBkM2Fu?= =?utf-8?B?VkJhQ0h5cHJIVXcyc0tDWXBkMFY3cXk2NUtJS2IrMWdGUTBjSVY4Z1QzaHF0?= =?utf-8?B?dWQ4UzR1SkZOU2ovSm1YQlJXdjhEK0t5bnQwNUFWQ21zMFBFQUIvbDNJb1RT?= =?utf-8?B?emoyTE8xQzFCNjVheTlKSWtvYWk3UlpZQUhvczFMcnBRZHNkYWVMWlZRTk5z?= =?utf-8?B?S0pXSXZuK0NKRHFoZnE5Vk1vZmt6aHYzL1VUcVp2ZkE3QnB1RFhvL294eCtS?= =?utf-8?B?Ry9rS3hEd1RXVjgrWkx3WTRQWUh0UXJxVkt6aGh0bnk2TlBwVWwrS1BjbmNx?= =?utf-8?B?OU0xNlI4cDFycVhqRjMweC9LU2pCV3ZhWDdGQWM5UXEzWXhmbGJRNVRqbUNE?= =?utf-8?B?VXpkN2UwRzYrMVhQczlndERjRHVKN29rVlpTSGtrWUI2MEZPczBybmZ1Q3Yz?= =?utf-8?Q?xyqBywvCFGXYd?=
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-Network-Message-Id: da7d5162-eea0-4b0e-1f82-08d8fa67e145
X-MS-Exchange-CrossTenant-AuthSource: BYAPR06MB5336.namprd06.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Apr 2021 08:25:34.9099 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: I5SrN52GtNmoz8y7MtXXdMOhXnieP43TTNqVDkb6ZsOfFb+0Brj9hnKAm6IRmY6Luz3EmYZAHer+ZAXmWNar6A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SJ0PR06MB6832
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/sgRPGoFb2g3YzbfTIMUEhI3I7Hs>
Subject: Re: [arch-d] Treating "private" address ranges specially
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2021 08:25:45 -0000

--=_MailMate_D91FF869-DCF6-41DA-A1D5-219B745607B0_=
Content-Type: multipart/alternative;
 boundary="=_MailMate_89866DDC-1C13-4D65-A803-7C424DCBF8A6_="


--=_MailMate_89866DDC-1C13-4D65-A803-7C424DCBF8A6_=
Content-Type: text/plain; charset="UTF-8"; markup=markdown
Content-Transfer-Encoding: quoted-printable





Christian wrote:
> I found a copy of the SOHO Pharming paper at http://courses.isi.jhu.edu=
/netsec/papers/Driveby_Pharming.pdf.


That is the DRIVE-BY-PHARMING reference.

I think that [this is](https://331.cybersec.fun/TeamCymruSOHOPharming.pdf=
) the Team Cymru paper on Soho Pharming that us referred to as SOHO-PHARM=
ING in the paper.

(Public service msg)

=E2=80=94Olaf
--=_MailMate_89866DDC-1C13-4D65-A803-7C424DCBF8A6_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Christian wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">I found a copy of the SOHO Pharming paper at <a href=3D"h=
ttp://courses.isi.jhu.edu/netsec/papers/Driveby_Pharming.pdf" style=3D"co=
lor:#777">http://courses.isi.jhu.edu/netsec/papers/Driveby_Pharming.pdf</=
a>.</p>
</blockquote>

<p dir=3D"auto">That is the DRIVE-BY-PHARMING reference.</p>

<p dir=3D"auto">I think that <a href=3D"https://331.cybersec.fun/TeamCymr=
uSOHOPharming.pdf" style=3D"color:#3983C4">this is</a> the Team Cymru pap=
er on Soho Pharming that us referred to as SOHO-PHARMING in the paper.</p=
>

<p dir=3D"auto">(Public service msg)</p>

<p dir=3D"auto">=E2=80=94Olaf</p>
</div>
</div>
</body>
</html>

--=_MailMate_89866DDC-1C13-4D65-A803-7C424DCBF8A6_=--

--=_MailMate_D91FF869-DCF6-41DA-A1D5-219B745607B0_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCgAvFiEEhLIIi9unO2bLJDsVzN4E5OAtL70FAmBuvfgRHGtvbGttYW5A
aXNvYy5vcmcACgkQzN4E5OAtL72Quw//bUzPglYkWQQMCrxrtlP62qcFiUtVi7Aw
SZRWNxaTv77Q67a0/9Eu7zkK1ZXjD+KpvETK45TIWcSau6FiHTsOLp8DbwE+o0+v
bxovpbSVTeLRn6uWlXl6AgjPshr87QkSv/SRwvDoyzwn1HdT+aOPaj8PGhgkGdgD
UFUX8SEZZTrcvBgPjtZFxxO7DwLn8jCr5zKlkMROzQ9tFlncwW6/hsRTETDLHDGC
CpidnWAd/xDOdec5HY+pd7M5RHPOYNYCwWyO7T6ifJ0NiNVMRHUOytF8PsiU/whU
naDND4nv/QRCdFahYO7GWoEiF1QVv8RVDVVcg2i/8bHcnubRSOPL0Jnq6L2XV5k1
n9UPMcn9KOt6L9+GWZ/2+ADrwMYOcR6lFMnalE3C/1XGGxwL65vR2MyrEkJdTXRX
S4riB4JkUuvt74c3wOtpl3GOHKVdH7uZXLV6gVvyeeTo3ZAf4Ms/e4I4xyV/P/FN
EMtT8xDZKByfE9PTl7cAsh/QjXU/+Pr3CaqyLrYY4lP1yEyhC/UiR/aQFEh2EjI7
QURo5zZVr6s95d05r+StwVwypzDZ7RbH7ra2VoKqutjBrFkxLiCZGgAdEL1BVvVO
TSyGRUeCs81g0g1bB8VZlr6I+xaaa5cXth4a3qzsW+I+njr+7NQ35d1nMv59sJb6
+jc8/yXQ2ik=
=vY8w
-----END PGP SIGNATURE-----

--=_MailMate_D91FF869-DCF6-41DA-A1D5-219B745607B0_=--


From nobody Tue Apr 13 15:40:14 2021
Return-Path: <jmaimon@jmaimon.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4CE63A13AF; Tue, 13 Apr 2021 15:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 k26V8CP3OhbM; Tue, 13 Apr 2021 15:40:07 -0700 (PDT)
Received: from smtp.chl.com (smtp.ttec.chl.com [216.222.148.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 338033A13A7; Tue, 13 Apr 2021 15:40:04 -0700 (PDT)
Received: from [216.222.150.100] (joe.jmaimon.com [216.222.150.100]) by smtp.chl.com (8.13.6/8.13.6) with ESMTP id 13DMKwif005598; Tue, 13 Apr 2021 18:20:58 -0400
To: architecture-discuss@ietf.org, iab@iab.org, IETF Announcement List <ietf-announce@ietf.org>
References: <161783156502.9164.12605972874915695547@ietfa.amsl.com>
From: Joe Maimon <jmaimon@jmaimon.com>
Message-ID: <6076194A.2000602@jmaimon.com>
Date: Tue, 13 Apr 2021 18:20:58 -0400
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40
MIME-Version: 1.0
In-Reply-To: <161783156502.9164.12605972874915695547@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/SnG3XaPP5-BFv9smqQkb_JXq03I>
Subject: Re: [arch-d] IAB Adoption of draft-iana-arpa-authoritative-servers-02
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>,  <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2021 22:40:12 -0000

Servers are leaving the premise now. If you want to use iDRAC in the 
NOC, I will be cabling it to the same vlan.

I would recommend utilizing a utility vm, such as provided previous, or 
another of your servers to DHCP the idrac into a private subnet only 
securely accessible.

We can do this from our systems, but only if that is your preference.

Joe

IAB Executive Administrative Manager wrote:
> The IAB will discuss adoption of draft-iana-arpa-authoritative-
> servers-02 (Nameservers for the Address and Routing Parameter Area
> ("arpa") Domain) at its meeting on 2021-04-21.
>
> The draft can be found here:
> https://datatracker.ietf.org/doc/draft-iana-arpa-authoritative-servers/
>
> The agenda for the meeting will be posted 48 hours ahead of the meeting
> here: https://www.iab.org/wiki/index.php/Agenda
>
> Feedback about this draft can be sent in response to this mail on
> architecture-discuss@ietf.org, or to the IAB directly at iab@iab.org.
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>
>

