Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1 LL on loopback

神明達哉 <jinmei@wide.ad.jp> Tue, 16 April 2019 15:51 UTC

Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A17E6120A77; Tue, 16 Apr 2019 08:51:27 -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 rYhcJVmd3pn1; Tue, 16 Apr 2019 08:51:25 -0700 (PDT)
Received: from mail-wm1-f46.google.com (mail-wm1-f46.google.com [209.85.128.46]) (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 78AD112063C; Tue, 16 Apr 2019 07:30:44 -0700 (PDT)
Received: by mail-wm1-f46.google.com with SMTP id n25so25759444wmk.4; Tue, 16 Apr 2019 07:30:44 -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=KUn9Gs6Rlvq/R/FVylGuhjuInTlUsG7MJPIo2wg+qSQ=; b=Aw50QqK+1xkvu1uazMxDbFG+KiruaFcDVIry2QKMVR414PPuwye61FK86VXTCGVtMy dIkjy3j4kF7sKFwRwUpLbNVTDnCwIJUTpfr23B0nShcnHCR7mSidGvIpA2UsaYhy657a PASzEYVZu+CuPcVcq92Tg9DCYX44IHYLGzOfg8+3NiT5BM3hOtp0N/EO5k4PLwak38A2 QOVLe08ZR5eKkDf4RNqKsgtkIdBjSYJ2Jh1cPUtJdSQvuI5BmdaHxOpvd9312O08H0Z+ 5fLOElas62U+RsfI6IAubGmONbp29lRryWQMRk6+YpcDxfitDWah83XiEpWuyuaLMafT iNrA==
X-Gm-Message-State: APjAAAUL5RoAto4JSkXyeevT+f5cs6bAYmEYRTzQBXlXFNAE1+Fd+FKn JavEX575tz0ywFgcB3X6S3eeQIeIxsc5Iv4NziY=
X-Google-Smtp-Source: APXvYqzsTwDktpeAQ/6XkxMPQ8LsEccR9Cu5lLPhk2oP6DQur2Kudt7vVERNYskZ3BmAEaBDCO4vbvELiTXHXXKfa+Q=
X-Received: by 2002:a7b:c446:: with SMTP id l6mr28119504wmi.80.1555425040453; Tue, 16 Apr 2019 07:30:40 -0700 (PDT)
MIME-Version: 1.0
References: <155169869045.5118.3508360720339540639@ietfa.amsl.com> <bcb6d12d-5b21-1f10-1afe-221321f8e7a6@gmail.com> <CAJE_bqd5t77B5ij3ot-F-ucx5+3A7LATC-VTBx3w2_kCDD8fNA@mail.gmail.com> <35193c42-44ec-7337-56e6-84df6053843e@gmail.com> <CAJE_bqdkhNFLg9ZT3uSFmjd-+5J78nQTQ8wKDHE8fe2v9Zn8Rg@mail.gmail.com> <35eeeddc-e861-d357-1468-dd853c53ea4d@gmail.com>
In-Reply-To: <35eeeddc-e861-d357-1468-dd853c53ea4d@gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Tue, 16 Apr 2019 07:30:28 -0700
Message-ID: <CAJE_bqfDPom7+LunUD7XtmcE4kxFFBOcFVe+BgFNejdQNqDn=Q@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: Pascal Thubert <pthubert@cisco.com>, "<int-dir@ietf.org>" <int-dir@ietf.org>, draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org, its@ietf.org, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000002d3db0586a69dc3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/OvSiEq62WXnAgVDmdwfNICfK-tg>
Subject: Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1 LL on loopback
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2019 15:51:29 -0000

At Tue, 16 Apr 2019 12:52:37 +0200,
Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:

> >  > That RFC4291 section 2.1 says:
> >  > >    All interfaces are required to have at least one Link-Local
unicast
> >  > >    address (see Section 2.8 for additional required addresses).
> >  >
> >  > Sidenote: I think the loopback interface does not have a link-local
> >  > address.  Probably it is not all interfaces that must have at least
> > one ll(
> >
> > Indeed, there's some subtle point here.  RFC4007 somewhat tries to
> > clarifies it:

> Well,  RFC4007 predates RFC4291, so it is little meaningful to say it
> clarifies it.

Could we be stop nitpicking?  I didn't say RFC4007 clarified RFC4291;
I meant it clarified the requirement of having a link-local address on
all interfaces, which I thought was clear from the context.  For that
matter, the above exact same text has existed since RFC2373.  Even
RFC1884 (the very first address architecture RFC) essentially says the
same thing in Section 2.7.

> Maybe we can say that RFC4291 must be updated given all these issues.

> > BTW, whether a loopback interface has an fe80 address is actually
> > implementation dependent.  BSDs usually assign ::1 on a loopback
> > interface while also generating an fe80 address on it:
> >
> > % ifconfig lo0
> > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
> >      options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
> >      inet6 ::1 prefixlen 128
> >      inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
>
> Ah?  It self-forms that fe80 address without a sysadmin requesting it?

Yes.

> In other OSs like linux, windows, there is no fe80::1 unless the
> sysadmin adds it.
>
> In that sense, this is an additional reason (together with the
> RFC4291-violating fe80:1::1 potentially breaking in BSD) to think that
> RFC4291 and co. are mostly for BSDs.

You're free to think so.  But that doesn't change the fact that
fe80:1::1 violates the RFC, so you'll need to update it if you want it
to be allowed.

Note also that MacOS is derived from BSD in case you don't
remember/know it.  And, in fact it also generates both "fe80::1" and
"::1" on the "lo0" interface.

Anyway, I don't think this discussion affects your draft?  If you want
to continue it, 6man would be a better place, if only to reduce the
noise in the original thread.

--
JINMEI, Tatuya