Re: [v6ops] "all hosts SHOULD implement address configuration via DHCPv6", as per BCP 220 (was: Implementation Status of PREF64)

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sat, 16 October 2021 20:00 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3244E3A0B2A for <v6ops@ietfa.amsl.com>; Sat, 16 Oct 2021 13:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.667
X-Spam-Level:
X-Spam-Status: No, score=0.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 ap97r2jtEVHE for <v6ops@ietfa.amsl.com>; Sat, 16 Oct 2021 12:59:58 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 7B5933A0B21 for <v6ops@ietf.org>; Sat, 16 Oct 2021 12:59:58 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 19GJxtdj033126 for <v6ops@ietf.org>; Sat, 16 Oct 2021 21:59:55 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id DDD9B202C5C for <v6ops@ietf.org>; Sat, 16 Oct 2021 21:59:55 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id D4C36200C25 for <v6ops@ietf.org>; Sat, 16 Oct 2021 21:59:55 +0200 (CEST)
Received: from [10.14.0.58] ([10.14.0.58]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 19GJxtSu032300 for <v6ops@ietf.org>; Sat, 16 Oct 2021 21:59:55 +0200
To: v6ops@ietf.org
References: <EFC78F4B-873B-42EE-8DC5-04C29758B0D0@consulintel.es> <YVNhdioAbeO9p2/G@Space.Net> <CAKD1Yr2+Y59v81mPBn4Y3u0LRX7TzahbnaF1hVUZ+NSf0Jj_4g@mail.gmail.com> <20210930.082006.177771395.sthaug@nethelp.no> <d0c441c6-68fa-52ef-7c60-e8f0cff80ba0@gmail.com> <64E83A09-C4DC-428C-88D1-79FAD6AAB72E@delong.com> <d1e5aa61-c61b-6e5f-9c6f-50f88d7a28a2@gmail.com> <F4F2E2BA-C07C-457C-A244-8A3220B32226@delong.com> <C34C198D-51F5-4189-8913-305733B6AA90@thehobsons.co.uk> <CAO42Z2wAKoyC0pssr9To+cAHavCMEZGh9FHb+yG7x8rWw5cU5g@mail.gmail.com> <CAN-Dau2medOLeCFCpSuUC9f+=Dn-kf8uN5RnkFKTS1T7uj9SUQ@mail.gmail.com> <6693BB0F-76E6-44B7-BCC3-99BF6FC6DACA@thehobsons.co.uk>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <dd6a5200-b0ad-7d2c-bba6-15d56d888cd5@gmail.com>
Date: Sat, 16 Oct 2021 21:59:54 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <6693BB0F-76E6-44B7-BCC3-99BF6FC6DACA@thehobsons.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/-Aw_YE1CEta9p4Kk6GrUQofSDy4>
Subject: Re: [v6ops] "all hosts SHOULD implement address configuration via DHCPv6", as per BCP 220 (was: Implementation Status of PREF64)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Oct 2021 20:00:04 -0000


Le 15/10/2021 à 16:17, Simon a écrit :
> David Farmer <farmer@umn.edu> wrote:
> 
>>>> Not to put too fine a point on it, but I have seen no argument
>>>> against Android including standards compliance
> 
>> Mark Smith <markzzzsmith@gmail.com> wrote:
>>> DHCPv6 is not required. See BCP 220.
> 
> I actually had in mind a comment made some way up the thread that
> Android ignores the A bit in RAs. If so then that’s a blatant
> violation, not just of the standard, but also of the wishes/policies
> of network operators who may be fully within both the letter and
> spirit of RFCs/BCPs.
> 
>> Yes, DHCPv6 is not required for hosts to implement, but it is
>> recommended by RFC8504/BCP220
> 
> "Consequently, all hosts SHOULD implement address configuration via
> DHCPv6” This, and the text leading up to it is very clear

Thanks for pointing to that text in BCP220 RFC 8504 "IPv6 Node Reas", 
because I missed it somehow.

Alex


  - if you
> value interoperability at all then implement DHCPv6 client on your
> devices.
> 
>> But then again, networks providing general propose hosts with more
>> than one IPv6 address is not required and is also only recommended
>> by RFC7934/BCP204.
>> 
>> So I think we have a standoff or deadlock, can we find a way to
>> break it? How about we all agree to implement the IETF's
>> recommendations in both cases?
>> 
>> Personally, I think they are both very good recommendations.
> 
> Agreed. It does seem quite simple really. So why is it so hard ?
> 
> Simon
> 
> _______________________________________________ v6ops mailing list 
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>