Re: [**EXTERNAL**] Re: the race to the bottom problem

Ca By <cb.list6@gmail.com> Fri, 06 November 2020 16:29 UTC

Return-Path: <cb.list6@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 0EFD03A0808; Fri, 6 Nov 2020 08:29:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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=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 r5Pu54yIJ03s; Fri, 6 Nov 2020 08:29:21 -0800 (PST)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 EF18B3A07F5; Fri, 6 Nov 2020 08:29:20 -0800 (PST)
Received: by mail-io1-xd29.google.com with SMTP id s24so2031186ioj.13; Fri, 06 Nov 2020 08:29:20 -0800 (PST)
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=dZTNfc+woodXdr6YKNypEdYuwxwVHHApd07jDt/v0hQ=; b=bsMzHz/4SEIFoKng9bZWcWBI+Yor717/g7lAiDWJ9EA1Esy2cA7zth4QxF4NFcor0U LzuFS51srvm+RpohqHCF9iLXWl832yDYCJM0ckOb1nT/1kNdhIxP/Hciw4Jfqhk1clOt T+3oiJOE1mls6TbhGn4lLUlebp1oh8ov6G0tXHxIXfNQPAjcd3xM8HY4gSsmSwXqnY4C aW676KpHr2TRd3ciR0z411ndrDGhbCENf0Now7GyO3CSAn78h9aznZ2QXZvDzi9/7ZdW /xEQEBTIopODANwJHTlF0Kw9oSfrPgJ57CSFeSAT77T7S72C7aVE/WFgBRqWUxyig0cU 5G6w==
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=dZTNfc+woodXdr6YKNypEdYuwxwVHHApd07jDt/v0hQ=; b=sYkpbVXZUqybUd8CM2cd14U2hQTpZrIITDXUbNXG+L59VnO4nlI+Ra9K9YSsNCkEY0 qR/E+VFDakxqBdCaoe85MZe0+fcmqav4DoJ44uGxdYW+Y3R5mbr8uwgfYdim0MEAfTmG STJsEuri1zpXwme0WO6B/IGIiNqALFAXKfgl148LqxsSTn4gxtujstcrOL8AL4HtujCO 9Y5xcjoiyTgZ+4wqegS5dNA6p5fUMAxg+z7ODzb0yAu6FjYEXkOo15uPKjbwsxL6Dru9 Rjl2U+enZ39p4YtMr8e8fXUT9LNTQndoAaEd/taKUAyU7E/+YsdR0SoiXg0TZefoSCDi NHcA==
X-Gm-Message-State: AOAM533gJ63vsciIVGWDb83ONki8g40EYajJxWvnyjIInd5d1tiaNZ4i PaXvye/QP4rl2K39keyKKcYL+demPnWb6l6h6rM=
X-Google-Smtp-Source: ABdhPJzPifVOw1VDF1zfR8jcx2LpB9LUAd4aN+dDmP/FX8NkxbgUdlvdml/SHGwjZIuH2dvweDJU2xj7JsBj0dIO76A=
X-Received: by 2002:a6b:6001:: with SMTP id r1mr1972054iog.144.1604680160103; Fri, 06 Nov 2020 08:29:20 -0800 (PST)
MIME-Version: 1.0
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <3c1c3ab5-5726-b141-e7ed-618984bbbdb1@gmail.com> <CABNhwV1zoZpZNjb54rEys4+49H3vpebZW2g9JbO1_58eR+WnQg@mail.gmail.com> <CABNhwV3L7kz=cWu8s3X=djVf4MCwewzbEgx09TWaKzCULCjYUQ@mail.gmail.com> <9A9CE8E7-3552-4FD8-A50E-1BDCA2CB813F@employees.org> <CABNhwV0LxM7EuKo2wNtVacjewsVqdhrmSiVBmB_EL-mqJYdU3A@mail.gmail.com> <CD9F9F09-2CBC-4A72-99C0-4A9A470357ED@employees.org> <9e787ed0-a221-e413-e030-ac2553dffc8e@gmail.com> <a21c9447-730b-e2c0-81f6-46deda57f507@gmail.com> <f4635fa9-45ca-f7ec-40a2-41764e1ca74f@si6networks.com> <905bcc26-a223-53d0-6675-c35579b9a8be@gmail.com> <AAE75F7F-F8DF-4B7F-9C50-3D6C91544997@ciena.com> <SN6PR02MB45129EE49060E5DBFEC9FBD0C3ED0@SN6PR02MB4512.namprd02.prod.outlook.com>
In-Reply-To: <SN6PR02MB45129EE49060E5DBFEC9FBD0C3ED0@SN6PR02MB4512.namprd02.prod.outlook.com>
From: Ca By <cb.list6@gmail.com>
Date: Fri, 06 Nov 2020 08:29:09 -0800
Message-ID: <CAD6AjGRq-1GSRy+wGfyixz7e1Q-7Faj5+Erc1m+Khm7LcZB0PA@mail.gmail.com>
Subject: Re: [**EXTERNAL**] Re: the race to the bottom problem
To: "STARK, BARBARA H" <bs7652@att.com>
Cc: 6man WG <ipv6@ietf.org>, "draft-mishra-6man-variable-slaac@ietf.org" <draft-mishra-6man-variable-slaac@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ebd24605b372b6f8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/E6cgE7MRedp8BR6t1arlrHrbNHM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 06 Nov 2020 16:29:23 -0000

On Fri, Nov 6, 2020 at 8:21 AM STARK, BARBARA H <bs7652@att.com> wrote:

> > Would it help if the problem statemen clarifies that:
> >
> > - There is no race to the bottom. We are not trying to solve ISP problem
> by
> > allowing longer than 64bit prefixes,
> > - It is not about restricting the ISP prefix assignments to minimum one
> 64bit
> > prefix, by imposing 64bit SLAAC prefix limitation on the clients,
> > - Minimum of one 64bit prefix limitation should be imposed by other
> > network elements, rather than clients. Edge routers can block >64bit
> > prefixes,
> > - Clients should be enabled to use >64bit prefixes for SLAAC to address
> X, Y, Z
> > problems, and
> > - Operators engineering >64bit subnets need to evaluate how low is the
> IID;
> > should maximum prefix length be 70 or 96 or ... (for security or other
> > reasons)?
> >
> > Dusan
>
> I'm thinking it might be reasonable to impose a requirement on CE routers
> (and devices in similar roles) that it MUST NOT accept delegation of a
> prefix longer than 64 bits on any interface using a technology that only
> exists on WAN links (e.g., DSL, PON, DOCSIS). This doesn't fully solve the
> problem. But if it's hard to get routers that will accept such delegations
> on WAN-only links, it will discourage most operators from doing them. From
> a business analysis case, the cost of providing prefixes with length <= 64
> would be less than the cost of making sure all their customers have CE
> routers in place that do not have this limitation.
> Barbara
>

I would prefer to not set traps for network operators like this.

CB


> >
> > On 2020-11-06, 9:15 AM, "Alexandre Petrescu"
> > <alexandre.petrescu@gmail.com> wrote:
> >
> >
> >
> > Le 06/11/2020 à 11:36, Fernando Gont a écrit :
> > > On 6/11/20 07:04, Alexandre Petrescu wrote:
> > >> I have been reminded in private about 'race to the bottom'.
> > >>
> > >> In the Variable SLAAC solution draft we do touch on the problem:
> > >>
> > >>> The "race to the bottom problem" - is the problem where allowing
> > >>>  prefixes longer than 64 to be used in SLAAC will lead to 65, 66
> > >>> and so on, up to 127 and 128 allocations.  At that point the
> > >>> bottom would be reached and thus impossible to extend the network
> > >>> further.
> > >>
> > >> A solution is then proposed in section 8 titled "Greater than 64
> > >> bit prefix usage by ISPs is strictly prohibited".
> > >
> > > Then we'd need an RFC for formally creating the Internet
> > > police/militia. (possibly a very bad timing for an already bad
> > > idea).
> >
> > So we need to attenuate that 'strictly prohibited' wording and improve a
> > way forward.
> >
> > Alex
> >
> > >
> > > Thanks,
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests:
> > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ipv6__
> > ;!!BhdT!wVq_pzyE528tYQ87Kjxz_9O56DPf2t4bw1c6tQSvzc64sLdjOExbP4XV4
> > smz_A$
> > --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>