IETF Logo Mail Archive

Re: <draft-ietf-6man-rfc4291bis-09.txt>

Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com> Thu, 06 July 2017 21:55 UTC

Return-Path: <pch-b7900FA3D@u-1.phicoh.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 37AC9124217 for <ipv6@ietfa.amsl.com>; Thu, 6 Jul 2017 14:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 108ooBG_Rhry for <ipv6@ietfa.amsl.com>; Thu, 6 Jul 2017 14:55:53 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id D1C951200E5 for <ipv6@ietf.org>; Thu, 6 Jul 2017 14:55:52 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1dTEka-0000FlC; Thu, 6 Jul 2017 23:55:52 +0200
Message-Id: <m1dTEka-0000FlC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: <draft-ietf-6man-rfc4291bis-09.txt>
From: Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>
Sender: pch-b7900FA3D@u-1.phicoh.com
References: <20150804195752.5065.13523.idtracker@ietfa.amsl.com> <5AB14F48-2799-4A86-830D-E8A89CCADAAC@gmail.com> <CAN-Dau0O6hrxmWiWa7yPNDkq7Dz_m1y8wA7bYx_1wYuTpM0ruw@mail.gmail.com> <D691C19D-F3D8-4487-8641-DBA7A8DF8A3E@gmail.com> <CAN-Dau39LbQ4Lpx-ULxUuSmeL+zgQsRU5861SUvr6vesB5-uUw@mail.gmail.com> <m1dTCC8-0000DqC@stereo.hq.phicoh.net> <a47855f5-1922-0485-ae56-60e550e7d9b6@gmail.com> <CAN-Dau3_9wg7Q=HwUj81+V_hbjfo+LkPz0yN1YAW0RTr4yBQmw@mail.gmail.com>
In-reply-to: Your message of "Thu, 6 Jul 2017 16:22:14 -0500 ." <CAN-Dau3_9wg7Q=HwUj81+V_hbjfo+LkPz0yN1YAW0RTr4yBQmw@mail.gmail.com>
Date: Thu, 06 Jul 2017 23:55:48 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jo3rEJLBMX1TanW_zFr7IssA9Uc>
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: Thu, 06 Jul 2017 21:55:54 -0000

>But the unfortunate answer is; that is not the purpose of this document.
>This document is a specification, not a document meant to teach anyone
>about IPv6. In fact in the Introduction the document says this is a
>specification, but maybe it would help if it also said what it isn't, that
>is an Introduction to IPv6 and maybe even include a reference to the ISOC
>IPv6 tutorial.

It used to be that RFCs were quite readable.

It makes me sad if we now produce RFCs that essentially require you
to read all the previous versions of the same RFC and the mailing list
discussions surrounding it, to understand what the RFC really tries to
say.

If somebody needs auxiliary materials just to understand an RFC as basic
as addressing architecture, then we are only a small step removed from the
mostly unreadable telco specs.

v2.23.0 | Report a Bug | By Email