IETF Logo Mail Archive

Re: a draft about on-link and submit prefixes

sthaug@nethelp.no Tue, 14 March 2017 12:26 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 EA97512956F for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 05:26:43 -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 PDotFr5maah9 for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 05:26:42 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with ESMTP id 1A8D212955C for <ipv6@ietf.org>; Tue, 14 Mar 2017 05:26:42 -0700 (PDT)
Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id 701D9E6065; Tue, 14 Mar 2017 13:26:40 +0100 (CET)
Date: Tue, 14 Mar 2017 13:26:40 +0100
Message-Id: <20170314.132640.74662612.sthaug@nethelp.no>
To: otroan@employees.org
Subject: Re: a draft about on-link and submit prefixes
From: sthaug@nethelp.no
In-Reply-To: <026FE8B0-6FFA-4835-8D72-D4CBC6187A2D@employees.org>
References: <BD1C6A8D-F9D6-44D4-9911-20E1DE3F1658@employees.org> <49C05C3D-9594-4A46-BBA4-5767A9FDD34A@jisc.ac.uk> <026FE8B0-6FFA-4835-8D72-D4CBC6187A2D@employees.org>
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/Ql8Q3kg4hsTMJEPcqiJCSBj3PZ8>
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 12:26:44 -0000

> Right, that was what I feared.
> Including esoteric examples and examples bordering on configuration errors, just isn't going to add clarity in my opinion.

Could an IPv6 subnet be defined *without esoteric examples*?

If not - maybe the IPv6 subnet concept is too complex to be useful?

Just asking...

Steinar Haug, AS2116

v2.23.0 | Report a Bug | By Email