Re: Alternatives to the flag (Was:Confirmation to advance: draft-ietf-6man-ipv6only-flag-05)

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 15 May 2019 22:03 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 F2D871200DE for <ipv6@ietfa.amsl.com>; Wed, 15 May 2019 15:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 tvMAc3CgnrBs for <ipv6@ietfa.amsl.com>; Wed, 15 May 2019 15:03:46 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01BB81200D8 for <ipv6@ietf.org>; Wed, 15 May 2019 15:03:45 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id A40E538271; Wed, 15 May 2019 18:02:58 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id A334AE3B; Wed, 15 May 2019 18:03:42 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A0BE9A5; Wed, 15 May 2019 18:03:42 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Gyan Mishra <hayabusagsm@gmail.com>
cc: Nick Hilliard <nick@foobar.org>, 6man WG <ipv6@ietf.org>
Subject: Re: Alternatives to the flag (Was:Confirmation to advance: draft-ietf-6man-ipv6only-flag-05)
In-Reply-To: <0FDCBB0C-B5A6-48C0-AABE-91FDE49D8D63@gmail.com>
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <a2465e81-a17f-ab48-efda-20fe12a70077@foobar.org> <30239E0C-C444-4A7E-8342-AEE47BF8A2BB@employees.org> <20190505200449.GB7546@vurt.meerval.net> <80073906-c3c0-1f22-9e7f-c2b349063936@gmail.com> <CAO42Z2xzVW3m0mN7jEn8SYyYCYhrufVnkfp3rBjJcijBkvucNQ@mail.gmail.com> <CACWOCC-35yVYXSRR0sRL-MBMHyOFZtJx9E9h14G8qqVh5T7qGA@mail.gmail.com> <232c1a43-0fd9-4eae-737b-260a3906f72a@gmail.com> <663F6C0B-7B8A-4088-B9C0-B2867B0C3EB8@gmail.com> <CAN-Dau3VJN7qNHAW-yStMrDRCa4vsDs2ObkAxswnYbcHde2t_w@mail.gmail.com> <m1hPqHO-0000J8C@stereo.hq.phicoh.net> <CAN-Dau3R=4JbcbK7tWkJKYzVjq7DvAAEjVsbCLbZdYYO8OJ0YA@mail.gmail.com> <m1hQ7Dm-0000M3C@stereo.hq.phicoh.net> <CAN-Dau040j6U+1CCn0QJiVMy2nVShHqqSFdCkM-FbMAH-2wjRA@mail.gmail.com> <m1hQCYr-0000KBC@stereo.hq.phicoh.net> <CAN-Dau3Lcv3qTBVtig36RfbQKuGpoqdTLfrM=eWfYxCCQRy5Sw@mail.gmail.com> <m1hQfSy-0000LTC@stereo.hq.phicoh.net> <CAN-Dau3akjaZ-j16ucOY=-d0nabG4ZdFs6wrSD4EGr3NEh9Wsw@mail.gmail.com> <a6 46a186-be05-cdff-c8e4-61cf09930494@foobar.org> <0FDCBB0C-B5A6-48C0-AABE-91FDE49D8D63@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.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: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 15 May 2019 18:03:42 -0400
Message-ID: <14197.1557957822@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/YaGz0Mo7HahWw5UQhHSDGFSKsyE>
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: Wed, 15 May 2019 22:03:48 -0000

Gyan Mishra <hayabusagsm@gmail.com> wrote:
    > I have not tried but can printers use IPv6 link local to print
    > similar to IPv4 when a dhcp server is not present?

I think mine can.

In fact, the dhcp server on my "corporate" network (the one trusted for
stuff, vs the one the TVs, media, and experiments, and family is on) has been
broken for a few months for hysterical raisons.  {Fixing it involves being
offline for a few hours, while I reconfigure the replacement router... so I
haven't done it yet}.

So my printing is all over IPv6, but it's not always over LL.
I notice the LLv6 comes and goes, and I don't quite know why, so I'll hard
code the DNS/IPv6-GUA name, and then I'll go back to dnssd discovered LL.

The real question is however: how many clients support those DHCPv4 options?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-