Re: Why do we need to go with 128 bits address space ?

Fred Baker <fredbaker.ietf@gmail.com> Wed, 21 August 2019 23:38 UTC

Return-Path: <fredbaker.ietf@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 E7497120024; Wed, 21 Aug 2019 16:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 tFpMKJeuX5BE; Wed, 21 Aug 2019 16:38:41 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 88CC7120043; Wed, 21 Aug 2019 16:38:41 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id y1so2221791plp.9; Wed, 21 Aug 2019 16:38:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=L5mcMPsx6Jdxk8e/bF6a6AyKVxrXz3DEbluIEKKSBRQ=; b=kkOljjH8VoqADLAr54M+R5qvYfubyMPIaL6+mZnHvADdb0zPOCCGx2XtmFXweYSYbK bzrjKfwvXA+AtrFgY2wbZIsvOiKJIHcT4Fa/xhVkS1AI+0Fw75s582co0AU/GgSYe6Oy 0fKn38CvODUwkp2mfzzz/yybzQsYJWIJQ9sHZ49cGvndu3WEb9NfBQByFMqftgZBQf60 Snu9f6GSi+kLZkGVgEQX1a4MbYOqkgnp3NgI5HBJORW6PXSNwujirUmliJ3Gv7pJAWEd CV+0QCC3bPyoajQ/p4CIxlC1Na14v3BrgReoe5/1z5tGi1fSJcC/oRyYL7isTNDiQnlV 2log==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=L5mcMPsx6Jdxk8e/bF6a6AyKVxrXz3DEbluIEKKSBRQ=; b=ZdkhIvY35RVosnDkTQ4fDfz/J4ibU0ISSprLzDUGSqNLS2iLcuPYhX2KtcLqfrbQ7A a3Bddye1USw1VVOzaK5evUtk8m5k53hyMaeslB5TlUCRAMABgYtPvp0PktvBme++AsPP myXz974lEXP/lhooVG3P0B/nU81ydyXOmWn9DRJcBf1DYntyMMcS+bLiBtR3OuWegB3U 7qvWM2ARBDoC4+p/rquui4rofuDGSqAU8kutzkDyjmFr51wmnEhko9/Qu/+5MNtxXMmX MIOXfwiTBDrE/1AmN24SAo66as2X+6MnilnVtmO8Yd/ndaDgNyabK4rV6OTvx+698Cng lfsA==
X-Gm-Message-State: APjAAAVkQ0SX7OPQqTz6+cPRCmsXxNGN2guKvYI1lctTyhxjGW3zYRtg oEFswG/XfRyrJDU3H0me5jE=
X-Google-Smtp-Source: APXvYqy6UcwScF0vM4qo3mODF1jc8gZng8A3NIBp/VpzpI9wU5ntl5zwWV73CHAnFvSEEz8d5mTN4Q==
X-Received: by 2002:a17:902:76c7:: with SMTP id j7mr35554041plt.247.1566430721063; Wed, 21 Aug 2019 16:38:41 -0700 (PDT)
Received: from ?IPv6:2600:8801:d004:600:b8f1:f1af:4586:1842? ([2600:8801:d004:600:b8f1:f1af:4586:1842]) by smtp.gmail.com with ESMTPSA id e66sm25165575pfe.142.2019.08.21.16.38.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Aug 2019 16:38:40 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3578.1\))
Subject: Re: Why do we need to go with 128 bits address space ?
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <df102b3b-d337-8852-c5dc-f7aa4f479d77@necom830.hpcl.titech.ac.jp>
Date: Wed, 21 Aug 2019 16:38:39 -0700
Cc: Robert Raszuk <robert@raszuk.net>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "6man@ietf.org" <6man@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CAF46EB5-03AE-495C-A85D-73B3A9B7EB02@gmail.com>
References: <CAPTMOt+cGhBqHmT3yZVChv-PCMqxT-WPDcDdM3RuTc1TMfFeVg@mail.gmail.com> <4278D47A901B3041A737953BAA078ADE148C2FE4@DGGEML532-MBX.china.huawei.com> <10708d7b-a4bc-f9d8-a644-7c5617f5ebf3@gont.com.ar> <CAPTMOtLyiUpi4L+7TpLePvm=JtpEnw-Yv1NCKvO63_HK2jFnCA@mail.gmail.com> <447e5dae-2ae9-b9fe-baa2-111c028d3b68@necom830.hpcl.titech.ac.jp> <CAOj+MMH=wb+v137TvQkZ+KxaBobA8qYmvoHkFzEgi9-PP-Lqxg@mail.gmail.com> <df102b3b-d337-8852-c5dc-f7aa4f479d77@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
X-Mailer: Apple Mail (2.3578.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SSMNWoGMoLCky9nScD4a8mEzVZI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 21 Aug 2019 23:38:44 -0000


> On Aug 21, 2019, at 12:56 PM, Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:
> 
>   Once a full routing table is available on all the end systems, it is
>   easy for the end systems try all the destination addresses, from the
>   most and to the least favorable ones, based on the routing metric.

Ohta-san:

I'm familiar with the paper "End to end arguments in system design" as well. I'm also familiar with John Day, although I suspect I have learned more from him than he has learned from me.

That said, we don't operate on the end2end principle in the Internet, in the sense of the application determining the route its packets will take to a destination. Applications know the addresses they might send packets to, but they have no idea by what path said packets might be routed - and probably wouldn't know how to interpret them if they did. That is separately determined by every AS the packet goes through, and can change in a clock tick. The network is intelligent - it uses routing protocols scubas BGP, OSP, and IS-IS to determine the routing of packets without the application being aware or involved.



Yours very humbly, Fred