Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 23 February 2019 00:26 UTC

Return-Path: <brian.e.carpenter@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 676C8130DD3 for <ipv6@ietfa.amsl.com>; Fri, 22 Feb 2019 16:26:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 UorYe0on10VM for <ipv6@ietfa.amsl.com>; Fri, 22 Feb 2019 16:25:57 -0800 (PST)
Received: from mail-pl1-x643.google.com (mail-pl1-x643.google.com [IPv6:2607:f8b0:4864:20::643]) (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 2AA86130DE4 for <ipv6@ietf.org>; Fri, 22 Feb 2019 16:25:57 -0800 (PST)
Received: by mail-pl1-x643.google.com with SMTP id s1so1789864plp.9 for <ipv6@ietf.org>; Fri, 22 Feb 2019 16:25:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=bkaeYXDIDBT1wM4YrzSpdEZMrIQOW9kdpq0tUbOFlPE=; b=WZCsK1bnC9C7+77nBN5Ke89cM0b/rMiMd7WhGaqZRnUMXyCJIQFzruePC24z/xiNy6 5afb+IH5L74vFgu8+/kWQSazC8fHsqtTWJpMV0d5BLh7OXooZ8bCSnlbKdkCZwQwl0NC JfnpAtlnSdaKh/kcQYiHIHTf1qpMfZiffXfz7BcHspwy+Ux9mkbuXhba/q58UUP5d1ku wN5+YDQRYEMZtPyzW3c7RhZaKyKWYGm5FUMdYka3AZSNCZgKuAnuz/QkT38TXtwFolA1 ZdCVwGyjpp7dk2hQY0GLdOnvzXWxUPbDxoPuiGug5sHqNbIsuzNJimF7GbOOspAMAni9 QLww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bkaeYXDIDBT1wM4YrzSpdEZMrIQOW9kdpq0tUbOFlPE=; b=gk1enqX/1ymAa00ZsVvQUf8HC5HIwaWSXLseFQ+G5BoaBjDXe3UEHNxpqLckRKydGO B5oVz2yHUWa7u/Al361nNDoCbjdSl04V1T6dVR0KdFBKlwBQgnhOK1LnJmspuvrwsUNM QpyKC9Zr/cLl1aCcuMep6ncjq2AfGufpG/pFJ0UYCR+MoBL7xbtbGCogMHlMIZSdCqd4 CR6zrfGQ30yYeB1V2O3cWBVMtPgSW+digKMM2G3ZuVp2BAmHVF8spzOhsRGBGZKFXguj ZprJzrN9I/hXXm61TwpMz0k2VdCKf9qAsQEfQa44W5BhwlkLE07jbTrrdr1ifg7vdLK1 nbpg==
X-Gm-Message-State: AHQUAubmW8Z7MkbW+FdidJktBkwY2ocNT8b6NwX9M19RrZ4yhodB2qXB eKEHgQgHhzP7ZlOvisHUQjK+A8+B
X-Google-Smtp-Source: AHgI3IYnV491N3r6ACdKhbjZ11ZcXravMcR1XQP8HW/CYYVlstQ+fqE2tYvvVEHgnD9N1OkxjLHWlQ==
X-Received: by 2002:a17:902:4225:: with SMTP id g34mr7053840pld.152.1550881555740; Fri, 22 Feb 2019 16:25:55 -0800 (PST)
Received: from [192.168.178.30] ([118.148.79.176]) by smtp.gmail.com with ESMTPSA id d5sm4383323pfo.83.2019.02.22.16.25.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Feb 2019 16:25:54 -0800 (PST)
Subject: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios
To: Jan Zorz - Go6 <jan@go6.si>, ipv6@ietf.org
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <CAFU7BAS1_veTu-ZXAF0MF4niJwz149nGipx3ep_6fh1bewOzgg@mail.gmail.com> <d9503983-6524-a13a-2cb0-cdcb95f76ea6@si6networks.com> <CAFU7BAQfg712UfgW9wi9pd3eVeZP9cqJEXd6=FDmchuSdauv+g@mail.gmail.com> <82c00442-bbc4-581b-2054-2d02d50d20ad@si6networks.com> <CAFU7BASDgmSwY=SLiabSqyiTOphxU0COtFLQvT8drm0iTxM+-Q@mail.gmail.com> <76c488e0-5be7-3b81-d4c3-7af826f0dbef@si6networks.com> <CAAedzxq5d0fgOq5KZu7aCL9wxoDij6C-1Ad9+nQbYyhu2aMt-Q@mail.gmail.com> <da1c6391-5e69-f09b-dee5-83d25f1cd8cd@si6networks.com> <CAAedzxouCqcmW0rA6KwDZEO-n5yVZUYHc+GSetJ8O7=Liou4tA@mail.gmail.com> <0DDB4538-62F8-442A-A12C-D3C176540884@jisc.ac.uk> <a0a4246c-24cd-905c-4cde-0428b83ba5a3@si6networks.com> <CAOSSMjVtOXOOCHVvofsMQH5=bjV_tupqCKed6C4fXiS_ZnCSQg@mail.gmail.com> <eaea9418-cd5d-714f-9332-8b7de49d5d8b@si6networks.com> <90dd7fee-77cc-3411-7079-60a6edf488d9@gmail.com> <29b2f8fb-f75f-a9e6-b0a2-5651fa2a6427@go6.si>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <fd358b7d-b219-5f74-b5c5-217260fae9f1@gmail.com>
Date: Sat, 23 Feb 2019 13:25:48 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <29b2f8fb-f75f-a9e6-b0a2-5651fa2a6427@go6.si>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/AVcPM5aTtnWx0rY0JDscIsF2I0w>
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: Sat, 23 Feb 2019 00:26:02 -0000

On 2019-02-23 09:36, Jan Zorz - Go6 wrote:
> On 21/02/2019 22:14, Brian E Carpenter wrote:
>> Of course, SHOULD means "that there
>> may exist valid reasons in particular circumstances to ignore a
>> particular item, but the full implications must be understood and
>> carefully weighed...". In other words, do RFC8028 and Rule 5.5
>> unless there's a good reason not to.
> 
> Unfortunately not all vendors understand SHOULD in this way. 
> Implementing more options is expensive and lowers the profits, so it's 
> quite easy to fall into "implement all the MUSTS, declare compliancy 
> with RFCs and ship the product" trap.

Sure. I dealt with a lot of development managers during my years
at a 3-letter company, so this error in thinking is quite familiar
to me. But there is nothing the IETF can really do about that.

    Brian