Re: about violation of standards - fe80::1/128

神明達哉 <jinmei@wide.ad.jp> Wed, 24 April 2019 14:49 UTC

Return-Path: <jinmei.tatuya@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 2CC8C120401 for <ipv6@ietfa.amsl.com>; Wed, 24 Apr 2019 07:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.669
X-Spam-Level:
X-Spam-Status: No, score=-0.669 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 FB3Gt84b2GOU for <ipv6@ietfa.amsl.com>; Wed, 24 Apr 2019 07:49:46 -0700 (PDT)
Received: from mail-wr1-f50.google.com (mail-wr1-f50.google.com [209.85.221.50]) (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 5F8DC1203DB for <ipv6@ietf.org>; Wed, 24 Apr 2019 07:49:46 -0700 (PDT)
Received: by mail-wr1-f50.google.com with SMTP id b1so14235878wru.3 for <ipv6@ietf.org>; Wed, 24 Apr 2019 07:49:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=e+7xWEfUztHWFk0clceRPL4Zq/b02KlHcuDD147QzKc=; b=gulyTMOAdSO5cLJRp7xbrILi/LqqBkHWKfP3Dk6MA2oKQUHnH+c83PLemhkFakPpUV 12UjL16b+1Bs51gfbfybHMIzumFp4GHCA8/m8BW1GfiOwArRmQYt+4+Gp+3txWQ5fZ9S uCYNpX0rMYP3W0/zZ/cmSSU8Agk9VvnqzpjXNOVf6XLPbpkYDvTB8PazX1hCgaZTcLNd HRZ9iKdpZLz5GvUZwQeHVjsN7oivuJdGFeATVpVVG23iAovOOLwNOZd23y4Yd4YXLRv/ IfOCB+uVm/LCZfMjwzG9PiyBTYvO1AJOqkUaDQYOXq3XF5PLNneLhaMv20IzOia0PPTb aQHQ==
X-Gm-Message-State: APjAAAU6Jtjfq/zz1Ul6RuccptenKn9fl/B8wwe/J2ty2Gnlvm8GGfjl ExX3pDqRWczvb3OUNDuPQ3j45kzzkTsZmwBEN5s=
X-Google-Smtp-Source: APXvYqxijnC3dk+XzO0/rXfhH1tmKzdU0NnAjSePHQZxppnoRT6n2Eo4qlJjQwkS2oUweLPOeePfQFIftFOF7eTZLO4=
X-Received: by 2002:adf:c986:: with SMTP id f6mr21652826wrh.93.1556117384522; Wed, 24 Apr 2019 07:49:44 -0700 (PDT)
MIME-Version: 1.0
References: <bb7f7606-2adf-e669-8bcd-e41f17800782@gmail.com> <CAJE_bqd9frqX5-yeVPj8MYXpZ4737HqK1gmfD9cQV3A-Ea5HrQ@mail.gmail.com> <CAKQ4NaWLGh3f_dN6WVNnYs9fKL8=vfpnShAK8AczPo8LE8LjFA@mail.gmail.com> <CAJE_bqdsJ74ajnCgvm+bWZk=m_Emdy46TKc=73sHG-sf9Czsdg@mail.gmail.com> <a0973403-960b-1136-514d-fd675e318824@gmail.com>
In-Reply-To: <a0973403-960b-1136-514d-fd675e318824@gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Wed, 24 Apr 2019 07:49:32 -0700
Message-ID: <CAJE_bqf170RceGvJvrmGkkq2tVzLx7nBi+cqQ9fU3xxmyxAE6A@mail.gmail.com>
Subject: Re: about violation of standards - fe80::1/128
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: Yucel Guven <yucel.guven@gmail.com>, IPv6 <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000eeee42058747cf1c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vHgwGRYR-vGHMrlTomxKL-_6HxU>
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, 24 Apr 2019 14:49:55 -0000

At Wed, 24 Apr 2019 16:29:59 +0200,
Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:

> As a response, I would like to ask whether fe80::1/128 on lo is a
> violation of standards.

First off, assuming you refer to the behavior of BSD variants
(including MacOS X), it's not 'lo' but 'loN' (normally just lo0 but
can also be lo1, lo2, etc, if these are also configured).  The world
doesn't only consist of Linux.

Secondly, again assuming it's BSD variants, it's not /128 but /64.

Third, I don't see which standard it might violate.  Could you be
more specific?

If you simply mean whether an implementation could choose to use ::1
as the mandatory link-local address on a loopback interface and skip
assigning an fe80 address on it, then I'd say it should be allowed as
we discussed off-list.  But IMO that would also require some update to
RFC4291, which is hopefully much less controversial than using a non-0
value in the intermediate 54-bit field.  And in any case, that doesn't
mean assigning an fe80 address on such an interface is a violation.

--
JINMEI, Tatuya