Re: Loopback interface terminology issue
Mark Smith <markzzzsmith@gmail.com> Mon, 16 October 2017 01:32 UTC
Return-Path: <markzzzsmith@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 C157C1332DA for <ipv6@ietfa.amsl.com>; Sun, 15 Oct 2017 18:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.496
X-Spam-Level:
X-Spam-Status: No, score=-1.496 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 5NNMEkeVeALp for <ipv6@ietfa.amsl.com>; Sun, 15 Oct 2017 18:32:29 -0700 (PDT)
Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::236]) (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 F13331332D4 for <ipv6@ietf.org>; Sun, 15 Oct 2017 18:32:28 -0700 (PDT)
Received: by mail-ua0-x236.google.com with SMTP id s41so8655021uab.10 for <ipv6@ietf.org>; Sun, 15 Oct 2017 18:32:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ks7u2TTOditn6/TghwUcGJbRerwGoV76/wj3HOKIUxc=; b=FVCi6aMClabozvBW0SLnIH7yIK1RCeS0pXdME/lProggdDdksKxddl4Ho1agbRYRTC 0lJh5AC3RMSsEHnMC+aO426/qxfkYyo67cYdbeU/VQHni7MD3/QeeDjwH3WrjD1MdiFy npugEF5Biw75l+/BLRgUCwCrwqJ5wA/xMgSn76nJU8Hf36vBhUQD5J8g2A7CNKxoSXaD mtov54jW2jieDSuoYAuyNJiV/Hm8lLJv8H1uW4VW2A8f0gkH6uYrHD9cGvomZBeLFhTo zNd29ZxIZasj3a/vXIGdmXFm7BzYdZSpZd4yT5nAhxBKJ04VMEGLOIDr0qdDqS0bPR6V pdug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ks7u2TTOditn6/TghwUcGJbRerwGoV76/wj3HOKIUxc=; b=ieuu3q6zmyO6+5VlPxpN4T3ShboI3cFiRUt52NJAO5mYmtQMms629x+YcvTvccRQst xYy+FmlEJmEsqm8eR53Qs49Z+U16OwHrlMDsDvg4LFsEGeG7ihFsXr7NPUXXEfvzQ0MH arW2y2Hkz5pzHAQMk0hDtxg4+R7xSmOcN/jMDdTguknharsFDNc33Z5x/hmmWAXpc9+5 cNjFkfZjVOhqQwkxXaYE0QycXxiSIjlvxkgy2NbZscJSOZjGRApkE0ON0Mp4NxhOMmy3 egTCnSprHVjiLZEruq/Fgyh498kcOI2dfDGOJ2mcNEXkQ9FDGSqG/dDK+Djq7ma2pij9 mIsA==
X-Gm-Message-State: AMCzsaXXwOw135QjgXFqhzptNJLCXLBQMPC5BxWfBkG3CRt7ed3jhOEn lPyKrh0jq7ce/xt7gsSvUEYIyZYSek+ps+r2ms8=
X-Google-Smtp-Source: AOwi7QCBBcfHbiHqN5bPRrSj3jAFgw0oRgfJ4yjLt34p9wj3WGlIqkQ5pw76rHUzT2UnURlqio/l5vCFM/hahCq88aM=
X-Received: by 10.176.80.241 with SMTP id d46mr6345183uaa.53.1508117547962; Sun, 15 Oct 2017 18:32:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.52.221 with HTTP; Sun, 15 Oct 2017 18:32:27 -0700 (PDT)
Received: by 10.159.52.221 with HTTP; Sun, 15 Oct 2017 18:32:27 -0700 (PDT)
In-Reply-To: <20171015024129.GB20159@faui40p.informatik.uni-erlangen.de>
References: <4998af7c-700d-369d-f64f-a8f4ea585084@gmail.com> <20171015013639.GA20159@faui40p.informatik.uni-erlangen.de> <20171015015318.764838AF5D66@rock.dv.isc.org> <20171015024129.GB20159@faui40p.informatik.uni-erlangen.de>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Mon, 16 Oct 2017 12:32:27 +1100
Message-ID: <CAO42Z2ytSNu6c3_kLB4TxhC2JF=K-PmQw=DnxE0N27EvzBzo+g@mail.gmail.com>
Subject: Re: Loopback interface terminology issue
To: Toerless Eckert <tte@cs.fau.de>
Cc: Mark Andrews <marka@isc.org>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c191064b9d548055b9ffa3d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vRDvEKVixGU1GixGSYM7KLU5txw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 16 Oct 2017 01:32:31 -0000
On 15 Oct. 2017 13:41, "Toerless Eckert" <tte@cs.fau.de> wrote: On Sun, Oct 15, 2017 at 12:53:18PM +1100, Mark Andrews wrote: > > IMHO: A loopback interface is an attachment to a node internal > > "loopback link". If other addresses beside "loopback addresses" are > > assigned to such a link, then this implies that the interface > > is configured to forward non-self-destined packets. > > No. Whether such addresses are forwarded by default or not depends on > the weak/strong host model in use. Not really. If the transport stack (a) logically attaches to the loopback interface then the loopback source address is the source address corresponding to the interface. The difference between strong and weak model would only come in if a transport socket (b) binds to a physical interface and tries to send/receive packets for the loopback address. I think the stacks i know logically do (a), althogh i am not sure how cleanly it's implemented. If its 100% clean then the TTL of the sent packet should be decremented by 1 before output on the physcial interface. Not sure which stacks this is done in. > Loopback interfaces are also used for test networks wholely constrained > to the node. Ok. How about: If other addresses beside "loopback addresses" are assigned to such a link, then the interface needs to be configured to forward non-self-destined packets originated from the loopback interface (see rfc8200, section 2). This draft might help. In IPv4, there are different forwarding rules for hosts and routers over the loopback interface for the 127/8 prefix. This draft proposes a larger IPv6 prefix for loopback, and mirrors those differences. https://tools.ietf.org/html/draft-smith-v6ops-larger-ipv6-loopback-prefix-04 Cheers Toerless > > On Sat, Oct 14, 2017 at 02:11:54PM +1300, Brian E Carpenter wrote: > > > Hi, > > > > > > This come rather late in the day, but it results from some wordsmithing > > > difficulties in a draft in another WG: > > > > > > The IPv6 specs are very clear that an address is assigned to an interface, > > > not to a node, but they don't say anywhere that non-loopback addresses may > > > be assigned to the loopback interface. However, sometimes as a practical > > > matter, it's necessary to assign a routeable address (GUA or ULA) that > > > is not created via a specific IPv6 interface. Conventionally, that is > > > done by assigning it to the loopback interface. > > > > > > However, the only place I have found that defines 'loopback interface' for > > > IPv6 is in the addressing architecture: 'a virtual interface (typically > > > called the "loopback interface") to an imaginary link that goes nowhere.' > > > (RFC 4291, section 2.5.3). The text only mentions the loopback address ::1. > > > > > > Do people agree with something like the following? > > > > > > 'Note that other forms of unicast IPv6 address may be assigned to the > > > loopback interface, in cases where an address is assigned to the node > > > without being assigned to the interface to a specific link.' > > > > > > This is after all common practice in various operating systems; we > > > just never documented it, as far as I know. > > > > > > Regards > > > Brian Carpenter > > > > > > > > > -------------------------------------------------------------------- > > > IETF IPv6 working group mailing list > > > ipv6@ietf.org > > > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > > > -------------------------------------------------------------------- > > > > -- > > --- > > tte@cs.fau.de > > > > -------------------------------------------------------------------- > > IETF IPv6 working group mailing list > > ipv6@ietf.org > > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > > -------------------------------------------------------------------- > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: marka@isc.org > > -------------------------------------------------------------------- > 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 --------------------------------------------------------------------
- Loopback interface terminology issue Brian E Carpenter
- Re: Loopback interface terminology issue Karl Auer
- Re: Loopback interface terminology issue David Farmer
- Re: Loopback interface terminology issue Brian E Carpenter
- Re: Loopback interface terminology issue Brian E Carpenter
- Re: Loopback interface terminology issue Toerless Eckert
- Re: Loopback interface terminology issue Mark Andrews
- Re: Loopback interface terminology issue Toerless Eckert
- Re: Loopback interface terminology issue Mark Smith
- Re: Loopback interface terminology issue STARK, BARBARA H
- Re: Loopback interface terminology issue Ole Troan
- RE: Loopback interface terminology issue Templin, Fred L
- Re: Loopback interface terminology issue 神明達哉
- Re: Loopback interface terminology issue Toerless Eckert
- Re: Loopback interface terminology issue 神明達哉
- Re: Loopback interface terminology issue Toerless Eckert
- Re: Loopback interface terminology issue Brian E Carpenter
- RE: Loopback interface terminology issue Templin, Fred L
- Re: Loopback interface terminology issue Toerless Eckert
- Re: Loopback interface terminology issue Brian E Carpenter
- RE: Loopback interface terminology issue Templin, Fred L
- Re: Loopback interface terminology issue joel jaeggli
- Re: Loopback interface terminology issue Brian E Carpenter
- Re: Loopback interface terminology issue Michael Richardson
- Re: Loopback interface terminology issue Michael Richardson
- RE: Loopback interface terminology issue Templin, Fred L
- Re: Loopback interface terminology issue Michael Richardson
- Re: Loopback interface terminology issue tom p.
- RE: Loopback interface terminology issue Templin, Fred L
- Re: Loopback interface terminology issue Toerless Eckert
- RE: Loopback interface terminology issue Templin, Fred L