IETF Logo Mail Archive

Re: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 19 October 2018 14:00 UTC

Return-Path: <swmike@swm.pp.se>
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 AF3C5130F53 for <ipv6@ietfa.amsl.com>; Fri, 19 Oct 2018 07:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 TQJG48xhxHvR for <ipv6@ietfa.amsl.com>; Fri, 19 Oct 2018 07:00:56 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 A8AE0130F6C for <ipv6@ietf.org>; Fri, 19 Oct 2018 07:00:48 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 56607B0; Fri, 19 Oct 2018 16:00:46 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1539957646; bh=0bwXYuEqUla8yjXTI7oEv7tWGQHFi0EKcypp1utnYeM=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=K/3W9udTv8Q2zj62GXtk5uKdU5A/c0rWcj1amPN/ynHdmZZI486+CnnTcjfZ/JhRG cXSZI/RubklSjxunrORkJAznGaHZ6ekeGZd/VGUwr8RtkbDs9d8UILwnl2CTpHjXIP L0Y3y5NO6/7psSkMASBIwJ8r3EyML2WcEWxlIioc=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 5059DAF; Fri, 19 Oct 2018 16:00:46 +0200 (CEST)
Date: Fri, 19 Oct 2018 16:00:46 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
cc: 6man WG <ipv6@ietf.org>
Subject: Re: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt
In-Reply-To: <422E06B9-8A68-4905-9901-7F4E201ADAB2@employees.org>
Message-ID: <alpine.DEB.2.20.1810191557270.26856@uplift.swm.pp.se>
References: <153973137181.9473.10666616544238076833@ietfa.amsl.com> <092346e1-6350-e54e-e711-9c5ee6dc4e6b@gmail.com> <CAFU7BASO_ByzbanhLKnWV280O_fASd-8W+ujpj3sN6d2-whw2w@mail.gmail.com> <CACWOCC-u7aAPwAOcixYvt2On=-o_8X25GhqdXTfA+tWRC1o2XA@mail.gmail.com> <alpine.DEB.2.20.1810191534430.26856@uplift.swm.pp.se> <422E06B9-8A68-4905-9901-7F4E201ADAB2@employees.org>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/B1ITmtBBHOEfqgUcxAiGHjrLo3Q>
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: Fri, 19 Oct 2018 14:01:06 -0000

On Fri, 19 Oct 2018, Ole Troan wrote:

> There should be a SHOULD disable IPv4 processing on the interface in there somewhere.
> If it is not then I think the SHOULD MUST be added.

"A host that receives only RAs with the flag set to 1 SHOULD NOT
    attempt any IPv4 operations, unless it subsequently receives at least
    one RA with the flag set to zero.  As soon as such an RA is received,
    IPv4 operations SHOULD be started."

The word "MUST" is never used in the document as a requirement to turn off 
IPv4. The only must is here (why isn't it upper case BTW?):

"If a default router expires (i.e.,
    no RA is received that refreshes its lifetime), the host must remove
    this router's flag value from consideration."

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email