IETF Logo Mail Archive

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

Gyan Mishra <hayabusagsm@gmail.com> Thu, 16 May 2019 23:19 UTC

Return-Path: <hayabusagsm@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 6CE7812036E for <ipv6@ietfa.amsl.com>; Thu, 16 May 2019 16:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 z-1xr5AmICYx for <ipv6@ietfa.amsl.com>; Thu, 16 May 2019 16:19:43 -0700 (PDT)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 D0793120353 for <ipv6@ietf.org>; Thu, 16 May 2019 16:19:42 -0700 (PDT)
Received: by mail-qt1-x829.google.com with SMTP id o7so6034394qtp.4 for <ipv6@ietf.org>; Thu, 16 May 2019 16:19:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CCODSpnn8a4+6HSTJcSkl4HfEuUfc4Vp/f4uXyMTG28=; b=kEbcD2XafFnO7PM8duNBrUqmrZ04hFFy5jPmlvkUZJycKWOR4XTlNOx+7bFkyyvuYT Qul17oHuBGL7neHlf89cBy2XlR8mryR89a48tthhJBqy6xUu/AcGy5r2M2NdgomgCedc 6ONd3KS/WAFwMAEcebBz8sSXjXW+4KUuSllGGcS17Asq/XFIfqNUifvnP+R1uTmu+XHj vPndBWdqtv4QdZncuFRF4gf7hzt9wPmU3N+WKUYjgQa2D3LbqPsYp12OL6ffdrDvllX2 G9PrgF27HT1LN/ZhVhSDFTkcTcW5euQAo5aiw47wLDfwhb8XLeYoztwzZ4Crw4WwEn98 /DZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CCODSpnn8a4+6HSTJcSkl4HfEuUfc4Vp/f4uXyMTG28=; b=TpuJngYFnDCW59Qdvo4xRoxEa9SsFXiZtk/5PHWXVkZ+Tnk59YZsKjc9YE2TsVbp0S Go/iSzvyTTF06aA12FLMh2Z7AvbrSjWmqNj+wtx0DqpuWlCpm/Lc+HES9Fx9mj7VqXkI sfGsiuSeMoj5tgdk3zfFJwZKhDiZXSuwiLxNJVPJVSNCc9/LZ6CPVUKlgo+jBfemoqt+ IpvMO/cwwC9Om9RYW1SzpVtJWy4jKuu9JC+67sTeboHM91EJpJJE9Ip8EdAPfgIETYxs qO3UJZa6TWZ3Cd4sxag7blN477rWhpgxtBW8LNvjHaYKQMOw+dAfCVbNibGYiIw5f8n6 Z0cg==
X-Gm-Message-State: APjAAAXCxlUsm0VnxsjI3Q9U0YvZQGdI7+rjSb2UJ0JPb50mL37j2USc LbdHT3MKXvhiuRUdcJHql77BKSMj
X-Google-Smtp-Source: APXvYqzSQhPcYQ6RUndF7N9VWpE815L3wZiEGVsBWU4XMow+o7cL8I3b7Ep1oYIgwz5w3/RjM47XGw==
X-Received: by 2002:ac8:332a:: with SMTP id t39mr46161692qta.245.1558048781643; Thu, 16 May 2019 16:19:41 -0700 (PDT)
Received: from ?IPv6:2600:1003:b021:e374:8c55:b721:4b18:dca0? ([2600:1003:b021:e374:8c55:b721:4b18:dca0]) by smtp.gmail.com with ESMTPSA id m6sm3176103qkc.56.2019.05.16.16.19.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 May 2019 16:19:40 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
Subject: Re: Alternatives to the flag (Was:Confirmation to advance: draft-ietf-6man-ipv6only-flag-05)
From: Gyan Mishra <hayabusagsm@gmail.com>
X-Mailer: iPhone Mail (16E227)
In-Reply-To: <CAO42Z2xjkFQjYX_fjbTEekXrGce1z0PA8h7KUvpFQgY3EP7Wkg@mail.gmail.com>
Date: Thu, 16 May 2019 19:19:38 -0400
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man WG <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E0256E13-8487-436A-A8F7-D38C9546405C@gmail.com>
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.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> <a646a186-be05-cdff-c8e4-61cf09930494@foobar.org> <725e05a6-726d-850a-0196-e7585b5449bd@gmail.com> <CAO42Z2xjkFQjYX_fjbTEekXrGce1z0PA8h7KUvpFQgY3EP7Wkg@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/eNxmrHXVrI6KXYUgMP0X92Esf9I>
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: Thu, 16 May 2019 23:19:50 -0000

That’s pretty cool.

I’ll have to try both the LL and global uni printing at home.  Also try the IPv4 LL printing.

So I guess if dhcp option was set to disable IPv4 link local and on your home network your broadband router supported setting the IPv6 only flag so you could turn off IPv4 and your router went down you could still print via IPv6 LL just as you did in your scenario. 

I guess I could convert my home network to IPv6 only and build V4 and V6 port forwarding rules back to my IPv6 only severs at home.  

Gyan

Sent from my iPhone

> On May 15, 2019, at 9:01 PM, Mark Smith <markzzzsmith@gmail.com> wrote:
> 
> On Thu, 16 May 2019 at 06:45, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>> 
>>> On 16-May-19 01:34, Nick Hilliard wrote:
>>> David Farmer wrote on 15/05/2019 14:27:
>>>> So, I'm not willing to drop what I think is a viable solution to the
>>>> problem unless other stakeholders are willing to buy into this kind of
>>>> change. In particular, I'm thinking the people maintaining mDNS in dnssd
>>>> wg. I can't see making the change proposed above without their buy-in.
>>> [...]
>>>> So I think we either need the flag or disable RFC 3927 by default on
>>>> dual-stack hosts.
>>> 
>>> RFC 2563 already specifies a protocol to turn off ipv4 LLs.
>> 
>> Yes, an IPv4-based mechanism. The proposal stipulates that we want a mechanism for IPv6-only networks to signal to dual-stack hosts, as did draft-ietf-sunset4-noipv4. That is of course looking to the future, not to most current networks.
>> 
> 
> IPv6 Only means only IPv6.
> 
> 
>>    Brian
>> 
>> 
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email