IETF Logo Mail Archive

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

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Thu, 22 August 2019 12:35 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 D964112001B for <ipv6@ietfa.amsl.com>; Thu, 22 Aug 2019 05:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable 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 J6wqJqifZpIi for <ipv6@ietfa.amsl.com>; Thu, 22 Aug 2019 05:35:37 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id E72611200C4 for <6man@ietf.org>; Thu, 22 Aug 2019 05:35:36 -0700 (PDT)
Received: (qmail 76690 invoked from network); 22 Aug 2019 12:23:27 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 22 Aug 2019 12:23:27 -0000
Subject: Re: Why do we need to go with 128 bits address space ?
To: Robert Raszuk <robert@raszuk.net>
Cc: Fred Baker <fredbaker.ietf@gmail.com>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "6man@ietf.org" <6man@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
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> <CAF46EB5-03AE-495C-A85D-73B3A9B7EB02@gmail.com> <ded4f1d5-924b-77f1-90f4-11dc4869a8a7@necom830.hpcl.titech.ac.jp> <C7ABF067-3376-46EF-BB57-7275D6350133@gmail.com> <7b3301a9-3816-092c-97cb-55c0a8e89e1e@necom830.hpcl.titech.ac.jp> <CAOj+MMEEQPGCSc4GJ4Bcgieojfuo-_WwcZNa7RXjxutPenxveA@mail.gmail.com>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-ID: <183071ed-667d-7565-5be6-fec287881212@necom830.hpcl.titech.ac.jp>
Date: Thu, 22 Aug 2019 21:35:32 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CAOj+MMEEQPGCSc4GJ4Bcgieojfuo-_WwcZNa7RXjxutPenxveA@mail.gmail.com>
Content-Type: text/plain; charset="iso-2022-jp"; format="flowed"; delsp="yes"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/p3QpXj0QWIdEMNnGDWB7FdllFTE>
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: Thu, 22 Aug 2019 12:35:40 -0000

Robert Raszuk wrote:

> Do you think that if something is written in the paper or on the class
> slides it makes it immediately valid and sound ?

So, you are arguing against *THE* paper. Good luck.

> And IP anycast is used far much broader and wider then just for DNS root
> servers.

As I wrote;

    PIM with a single rendez-vous point has no redundancy and
    anycast is, as is exemplified by multiple addresses of
    anycast DNS root servers, for load distribution, not for
    redundancy.

anycast used by DNS root servers is just an example. What is
your point?

							Masataka Ohta

v2.23.0 | Report a Bug | By Email