Re: I-D Action: draft-foglar-ipv6-ull-routing-00.txt

Mark Smith <markzzzsmith@gmail.com> Sat, 16 September 2017 01:07 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 54A811320CF; Fri, 15 Sep 2017 18:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 TC_accrk5XXt; Fri, 15 Sep 2017 18:07:07 -0700 (PDT)
Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::229]) (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 EA92A126B71; Fri, 15 Sep 2017 18:07:06 -0700 (PDT)
Received: by mail-ua0-x229.google.com with SMTP id t36so2007012uah.10; Fri, 15 Sep 2017 18:07:06 -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:content-transfer-encoding; bh=pPGTTSGwgao1V8SORI8toyZTyLzIphtIjG2wFuTsKDM=; b=Z3GKbUHDgAMDaFIzlOVmCxbGds/+vPDeBHTgeaIl1QNyB9CKmUGVLavENFJMzYsrXr e9HtRC6zEv2UcknBfF4F1/WWZZ0t3UsloisnybK0Rn4SFlHyU8yje90dwYOlBqFff1im eheZtvXeZvjzexCgVVJ9NxG59Q//Loq4zKVhVin49JFpnu6ZDQbcCW0NHzXgow+ZffSF 0cr0WPh1UiNa8e965xxMjPNEyagjFRlGGlMb4DG5OJSsSqqSCFqXWRsleJwa9bwqoeok kJ+RE6X3Dbus+eBJnCxnGchXPZLMkFPQO/GbPDsofrxK+Ovz9GvL9DywjFSAoBcdTkJn yrGw==
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:content-transfer-encoding; bh=pPGTTSGwgao1V8SORI8toyZTyLzIphtIjG2wFuTsKDM=; b=M8ZiJ2+95NPXaoYVe69M8aUlPC/zM9M5N79hQjGH004ccX0kSz4k2E5ME88rpYS0Bb o8DI1uPmsPt1JNnPiqf8hIV1+r9Gyv0BX9wr4Dr5uruxNOnpPhFd11EjRVM4W0aY2eS2 iGdoChWBh219A8inqgRxNJ+jWAIgBTmxj1mr0ljgaoNDXuNCuy/s9TT7R2pj1w0rRImJ af1Zq1rgYCtvJILd8/dE0A+TrFoFV4h5QZ8qli3XY+bPzr44c/hK39wfsibZcZJ3d5pv LQaR5nNoBfmWyzjsAC+ICiHggEUcSD3wUSO+WmZkuC/szwO814GLgVJAW52G3w0SxYb8 T7XQ==
X-Gm-Message-State: AHPjjUjKZ6tLW5CQYbWfLld1BGdkTSEqI7wR1zBu7l8UwwaGQA2mxzAp yRauo+wEOLj3f2vxv8jyIq/zfmzApyqajREWKX0=
X-Google-Smtp-Source: ADKCNb7LGFe9G7EGqeSjCdSSD0alZ2UbElAtedEuf18jiB5fB4qeBoS7tQftKkrkKof/albgG96tFd3UM9buawkV3xg=
X-Received: by 10.159.52.66 with SMTP id s2mr22808314uab.120.1505524025943; Fri, 15 Sep 2017 18:07:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.27.17 with HTTP; Fri, 15 Sep 2017 18:06:35 -0700 (PDT)
In-Reply-To: <bf117e83-ec1c-03fa-1eff-38679277829e@gmail.com>
References: <150523432567.17956.11322312258310497482@ietfa.amsl.com> <7e8fd49f-a777-fd9e-d410-be7e8d5958cc@gmail.com> <3F17FC48-D8CB-46A4-A8B3-0BC7F65E6D26@employees.org> <bf117e83-ec1c-03fa-1eff-38679277829e@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sat, 16 Sep 2017 11:06:35 +1000
Message-ID: <CAO42Z2xF48Ne+DZjc=rYP7cwq3fRHqjYvMLcgOwJJYUBSOa0ow@mail.gmail.com>
Subject: Re: I-D Action: draft-foglar-ipv6-ull-routing-00.txt
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Ole Troan <otroan@employees.org>, draft-foglar-ipv6-ull-routing@ietf.org, 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vfT3HF_FPNzPaQUF52VjY01YTYc>
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: Sat, 16 Sep 2017 01:07:08 -0000

On 16 September 2017 at 09:31, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> On 15/09/2017 20:10, Ole Troan wrote:
>>> Re https://tools.ietf.org/html/draft-foglar-ipv6-ull-routing-00
>>>
>>> "One of the goals of IPv6 was to have a sufficiently long address
>>> to allow grouping in fields to simplify routing decisions."
>>>
>>> What makes you believe that? I don't recall such a goal in the IPng
>>> process, and I can't see any trace of it in RFC1752 or RFC1726.
>>
>>
>> “Addressing can follow topology or topology can follow addressing; choose one” - Y Rekhter
>>
>> Goal or no goal, we know of no other way to make the routing system scale.
>
> Sure. I agree with that and with the RIPE policy that Mikael cited. Believe
> me, everybody in the IPng discussion was acutely aware of the tension between
> PA and PI addressing and the benefits of aggregation when possible. But that
> is very different from the quoted "goal", which simply wasn't there. Allowing
> topological aggregation was a goal, of course, but that's always been a
> matter of prefix assignment policy, not of the protocol design.
>
> Please note that I did not say that their idea will not work. It's the
> "alternative fact" that I'm concerned about.

>From what I've read in Christian Huitema's IPv6 book, at one stage
there was a thought of swapping the source and destination address
fields so that the DA field was first, to facilitate this sort of
cut-through forwarding. From memory, the explanation was that it was
decided against was because fields other than the just the DA address
have to be processed during layer 3 forwarding.

Regards,
Mark.



>
>     Brian
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------