Re: [Anima] Erik Kline's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)

Erik Kline <ek.ietf@gmail.com> Sun, 27 September 2020 21:52 UTC

Return-Path: <ek.ietf@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D5883A0832; Sun, 27 Sep 2020 14:52:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-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 G8vQNOoNzyE2; Sun, 27 Sep 2020 14:52:29 -0700 (PDT)
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 0B3AE3A07BD; Sun, 27 Sep 2020 14:52:28 -0700 (PDT)
Received: by mail-ot1-x32b.google.com with SMTP id u25so7770113otq.6; Sun, 27 Sep 2020 14:52:28 -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=skdPSHNnd7/JHNwSyx67EZSmblNsZkSTBIyLF9XR2h4=; b=cqvIvJh1aUCeeImf6QssESU/BIsUb8GF6zJHvc+EEH0qZYHnOAQbtLSrzxTQOKUboA M5R+wKaPy28GptqR+Ii2xLlwj+EZ38+I6G8UolOb9Jn/ASYCXeOIGw5AF/nwaT8RwM9Z NZ0uxZ6Aon+9T7ZD5njAz0S7YgRkh9zE6DSWXVQ6SCd/kfbY+VCtjDLLExQ6fP1dcXtF 0PcbawFDadlFyZ/wK9fI9QFYZJmYmeg0wmvwCCFAd0xul97OXy7w1vyoybn1syPcPpRW 6GHP95XLjLh72J809krKBeWpY1nbT1BQE2LIbfOK4HLc9UVwpJZiycNi2na1x99mb/1G Piwg==
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=skdPSHNnd7/JHNwSyx67EZSmblNsZkSTBIyLF9XR2h4=; b=BHvMbuZBo8ZHII9S0Za5zg8j2eKKWRl8cq95aMj7xLHmSKIu2RM5CboiBtD/5g7kPG OdQoLReBebNb3jpH6WLxfF9wl8DOMFduvAsuee9UUuFXuC8IYxDv40j2fMok430Ed/yR 1s5EbfedpiQTm2yrbmLAyezCDDQZDgJskUJK5BMEKlubXuh3UTxXEt31OatQY4cytOZJ sLrx9q5HrBClRsY6EXa2FgAejaMtA4hQIa8VSwlSe40U6JOb/ofdDsk8v1vh1ahhPEbw imWOq7Bkq0mj9/EB3NrLOrLXXeme2NUrT5quT3it3giyqciZKe8zyCQwTNPUODAOY7gR pf1g==
X-Gm-Message-State: AOAM533gF6/akPR1JdDdea4dkvJykwYTXfwvECO1lQZZiZ7jpXQa2WrQ Kr7YXXlSF+L4AmN9AxNDCHWg7yU9U8iKo5KBQNQ=
X-Google-Smtp-Source: ABdhPJwO7jRwiVJtWFDu2KF9da/PsYUM51jVMYmyJiu7SV0pkCFWY5DUQJEDdgBDvQdEN3+EbNZg4EtiWtC20g5kjH4=
X-Received: by 2002:a9d:51c2:: with SMTP id d2mr7106360oth.191.1601243548202; Sun, 27 Sep 2020 14:52:28 -0700 (PDT)
MIME-Version: 1.0
References: <159730676576.12387.18205135091671983859@ietfa.amsl.com> <20200911130023.GA64542@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20200911130023.GA64542@faui48f.informatik.uni-erlangen.de>
From: Erik Kline <ek.ietf@gmail.com>
Date: Sun, 27 Sep 2020 14:52:17 -0700
Message-ID: <CAMGpriVX12nhjwPzATRCkntmH5DQNjtQ3M2d490ya2_yJ75CLA@mail.gmail.com>
To: Toerless Eckert <tte@cs.fau.de>
Cc: The IESG <iesg@ietf.org>, draft-ietf-anima-autonomic-control-plane@ietf.org, anima-chairs@ietf.org, anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>
Content-Type: multipart/alternative; boundary="000000000000e3bcdf05b05290c2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/x5ANKRD4PJkib3gSLOz8rHtiLBI>
Subject: Re: [Anima] Erik Kline's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Sep 2020 21:52:31 -0000

Toerless,

Thanks for taking the time to go through all this.  Generally LGTM, but I
would like to iterate on the ULA text (nothing major).


> > [ section 2 ]
> >
> > * "It is the approximate IPv6 counterpart of the IPv4 private address
> >   ([RFC1918])."
> >
> >   I understand the intent but I don't think this statement is complete. I
> >   think we shouldn't let this sentence out into the wild as is since it
> could
> >   be read without any context nor even any pretense of interest in
> nuance.
> >
> >   May I suggest:
> >
> >   "It is often thought of as the approximate IPv6 counterpart of the IPv4
> >   private address space ([RFC1918]), though it is in fact meaningfully
> >   different in important and subtle ways [and upon which this document
> relies]."
>
> Thanks for not trying to talk me out of the comparison, which i
> successfully
> used to explain ULA to many customers. Your proposal is a bit too verbose
> for
> the terminoloy section, so it's now:
>
> It is often thought of as the approximate IPv6 counterpart of the IPv4
> private address (<xref target="RFC1918" format="default"/>). There are
> important differences though that are beneficial for and exploited by the
> ACP, such as the ULA Global ID prefix, which are the first 48-bits of a ULA
> address. In this document it is abbreviated as "ULA prefix".
>

It's a statement of fact that this is how people unfamiliar with this space
view this space.  It's apparently also a statement of fact that people are
still actively being told this.  ;-)

But I still think it's not quite right.  For one, the real counterpart to
1918 in IPv6 is the deprecated site-local prefix.  Also, to say it's "often
thought of" in an IETF document implies more IETF folks think of this way,
when in reality I'm not sure that's the case.

If you really want to leave this notion in (removing the sentence
altogether is good by me), perhaps we can wordsmith it a bit more.  If I
may propose:

OLD:

   ULA: (Global ID prefix)  A "Unique Local Address" (ULA) is an IPv6
      address in the block fc00::/7, defined in [RFC4193].  It is often
      thought of as the approximate IPv6 counterpart of the IPv4 private
      address ([RFC1918]).  There are important differences though that
      are beneficial for and exploited by the ACP, such as the ULA
      Global ID prefix, which are the first 48-bits of a ULA address.
      In this document it is abbreviated as "ULA prefix".

NEW:

   ULA: (Global ID prefix)  A "Unique Local Address" (ULA) is an IPv6
      address in the block fc00::/7, defined in [RFC4193].  Sometimes
      thought of as the approximate IPv6 counterpart of the IPv4 private
      address ([RFC1918]), there are important differences that are
      beneficial for and exploited by the ACP.  In this document, the
      "ULA prefix" refers to Locally Assigned Global ID prefixes, which
      are the first 48-bits of the ULA address [RFC4193 section 3.2.1].

(I didn't think it was worth trying to get into the fc00::/8 vs fd00::/8
distinction in this glossary text.)

> [ section 8.1.3 ]
> >
> > * Why is an RIO for ::/0 with a lifetime of 0 required?  Doesn't it
> suffice
> >   it set the default router lifetime to 0?  Separately, are all nodes
> required
> >   to be Type C?
>
> Check the new text, i hope it explains everything.
>
> Yes, type A and B do not support per-prefix auto selection of router,
> The lifetime of 0 is used so only Type C hosts will invalidate the
> default route for the ACP edge node, but not Type A/B hosts. Maybe there
> is another parameter combination that achieves this goal, but this was
> the easiest for me to assess/describe.
>

This looks better, thank you.

To be honest, I don't know what the point of Type A/B hosts is anymore (and
if it were possible to declare these anima deployments greenfield I would
recommend saying the default router lifetime MUST be zero in the RA header
to force clients to use a stack that works -- but that's just me).