IETF Logo Mail Archive

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

Gyan Mishra <hayabusagsm@gmail.com> Wed, 15 May 2019 20:33 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 59AFB12010F for <ipv6@ietfa.amsl.com>; Wed, 15 May 2019 13:33:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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 YJ-9m9Y4ntVG for <ipv6@ietfa.amsl.com>; Wed, 15 May 2019 13:33:30 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 5CD2E1200FE for <ipv6@ietf.org>; Wed, 15 May 2019 13:33:30 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id d13so1327082qth.5 for <ipv6@ietf.org>; Wed, 15 May 2019 13:33:30 -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=pinWyZAQ2zAINcnS2WhNITx3ntHP7U/cBbppKjlF7ps=; b=up/xfTVFNEo5h0V/EW0REVUwmrSnJw1LcH8yE0cJbhC3f/vDY2etqiCLsTd1aQjb1+ 6OZa6STpButHObytq7a6+ICp4GhhGNZr/hdUeYhWaYY8lKjvyjWSbV6JCwVK0rqui/I7 fF60FaMsZEUa9Pb9iFm9iiChILcSWTTjbXCatLmQitKsD5/Lua9m+kj/CWcNHSKc2T49 8YidS5aN1DK0gQVGytA+PiWoeMqZyBiEtrDPMF3wIdo2tUQjwNeRtqzqX3HNLfhED5ti 5SY/T9kS7ZmwI5In6o8YWnbXGXtJhhn8XWJ42a1GttiC3Ngdbeu6huhKGnsipWRfcutv MjHw==
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=pinWyZAQ2zAINcnS2WhNITx3ntHP7U/cBbppKjlF7ps=; b=oRT9ccdJQbrkxUYyCT1Pd6C6C4Cm5JDKHeCuzB8n0xh+DHfzH43dkK201f79G57H0Q 6g6YHAhPB0EQw67EJJPGV4uzVbUNkK0HFGLNxXqEtvRrEKymXph1KSxy7RcQHW3KNalS /gngyN3z3qFelGGrRdEIz/mimsmgMgqtEHWo8HzV7+KCsbukKoYbefb/MpK0JT8pqWLX YEANePMQI9EKyze5D/VZ4z9Aa3rRk+zB5ljhGLQ70OmWHAY9sexueN2YA4E8M3ejUR+1 udhuw/OaH61ow9qEIDVgd6IBaMIfyfJu2h1FAKHfqetAFvORUYjv8yjU4pDYWutpicSn p4tw==
X-Gm-Message-State: APjAAAWi4sWf/BrU6vpxXJeriEaxdK92LQyFmuhqIcl3+y+vVNAY40YL RjLUuep9BIV9jF3cD6cPHGsOxL1Y
X-Google-Smtp-Source: APXvYqzm/sB1bD4TvyCf4tpybEjvhZltScOk7fqhlNhwJJ05rJhlwi8VqDE3tSQR13rnrsNetdTrww==
X-Received: by 2002:a0c:88f0:: with SMTP id 45mr1616904qvo.19.1557952409117; Wed, 15 May 2019 13:33:29 -0700 (PDT)
Received: from [192.168.1.213] (pool-72-83-194-140.washdc.fios.verizon.net. [72.83.194.140]) by smtp.gmail.com with ESMTPSA id n66sm1649940qke.6.2019.05.15.13.33.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 May 2019 13:33:28 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-3F24029F-4997-4191-8BFC-E3099DF4176F"
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: <a646a186-be05-cdff-c8e4-61cf09930494@foobar.org>
Date: Wed, 15 May 2019 16:33:27 -0400
Cc: David Farmer <farmer@umn.edu>, 6man WG <ipv6@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <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> <a646a186-be05-cdff-c8e4-61cf09930494@foobar.org>
To: Nick Hilliard <nick@foobar.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/PORaRQRLq2RUi9_9VE01CJxZu3I>
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 20:33:32 -0000

Per RFC 2563 as Dave mentioned the option exists to 
disable IPv4 link local on dual stacked hosts.

I have not tried but can printers use IPv6 link local to print 
similar to IPv4 when a dhcp server is not present?


2. The Auto-Configure Option This option code is used to ask whether, and be notified if, auto- configuration should be disabled on the local subnet. The auto- configure option is an 8-bit number. Code Len Value +-----+-----+-----+ | 116 | 1 | a | +-----+-----+-----+ The code for this option is 116, and its length is 1. This code, along with the IP address assignment, will allow a DHCP client to determine whether or not it should generate a link-local IP address. 


2.1. Auto-Configure Values The auto-configure option uses the following values: DoNotAutoConfigure 0 AutoConfigure 1 When a server responds with the value "AutoConfigure", the client MAY generate a link-local IP address if appropriate. However, if the server responds with "DoNotAutoConfigure", the client MUST NOT generate a link-local IP address, possibly leaving it with no IP address.

Gyan
Sent from my iPhone

> On May 15, 2019, at 9:34 AM, Nick Hilliard <nick@foobar.org> 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.
> 
> Nick
> 
> --------------------------------------------------------------------
> 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