IETF Logo Mail Archive

Re: a draft about on-link and submit prefixes

sthaug@nethelp.no Tue, 14 March 2017 13:20 UTC

Return-Path: <sthaug@nethelp.no>
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 889441294E3 for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 06:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham 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 DEqgO1AnkPcN for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 06:20:25 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with ESMTP id CACE3129498 for <ipv6@ietf.org>; Tue, 14 Mar 2017 06:20:24 -0700 (PDT)
Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id A447DE6065; Tue, 14 Mar 2017 14:20:23 +0100 (CET)
Date: Tue, 14 Mar 2017 14:20:23 +0100
Message-Id: <20170314.142023.41722849.sthaug@nethelp.no>
To: lorenzo@google.com
Subject: Re: a draft about on-link and submit prefixes
From: sthaug@nethelp.no
In-Reply-To: <CAKD1Yr1G-65Vw0OyKP8CDPuUY7+-Q_hBrLY8E6wAoHHYM9jHsg@mail.gmail.com>
References: <026FE8B0-6FFA-4835-8D72-D4CBC6187A2D@employees.org> <20170314.132640.74662612.sthaug@nethelp.no> <CAKD1Yr1G-65Vw0OyKP8CDPuUY7+-Q_hBrLY8E6wAoHHYM9jHsg@mail.gmail.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/nPgB8MTikMKGsTtRu7q5ynL6-LE>
Cc: ipv6@ietf.org, jinmei@wide.ad.jp
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 14 Mar 2017 13:20:26 -0000

> > Could an IPv6 subnet be defined *without esoteric examples*?
> >
> > If not - maybe the IPv6 subnet concept is too complex to be useful?
> 
> Let's go back to IPv4, it's easy to understand.

I hope it's possible to ask for clarifications of the IPv6 subnet model
without returning to IPv4.

I haven't seen a definition of what an IPv6 subnet is. I specifically
haven't seen where it is defined that a given subnet prefix can be
spread across multiple links - especially since RFC 4291 says

"Currently, IPv6 continues the IPv4 model in that a subnet prefix is
associated with one link."

So if this is no longer the case (just like it's not the case that all
IPv6 netmasks are /64 or /127) then it is useful to have this defined
somewhere.

Steinar Haug, AS2116

v2.23.0 | Report a Bug | By Email