Re: [ietf-privacy] Accurate history

S Moonesamy <sm+ietf@elandsys.com> Mon, 08 November 2021 06:24 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf-privacy@ietfa.amsl.com
Delivered-To: ietf-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B65363A0D36 for <ietf-privacy@ietfa.amsl.com>; Sun, 7 Nov 2021 22:24:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 6Gg5tyxu4ESp for <ietf-privacy@ietfa.amsl.com>; Sun, 7 Nov 2021 22:24:37 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AD043A0D35 for <ietf-privacy@ietf.org>; Sun, 7 Nov 2021 22:24:37 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.109.155]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 1A86Nww8028216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Nov 2021 22:24:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1636352650; x=1636439050; i=@elandsys.com; bh=MFj52lt7ikyqyInZG13hFaUtynzedFb6HRiXXQKtscU=; h=Date:To:From:Subject:In-Reply-To:References; b=g1XERo30mghqHnDrvyRFUROeZkcXbPVf7yH//iIAuYN4JUBOGiTGeM0p0xT1KWkHo xBM+smL7/mZKSkdZBEhsRkHkjYcLzK7oAIY9SwNGEifWsQdaK4cVDGtO5ktqzwhKew JPX9SkoAW8t5yIH/IvcvYPHy49i+NT3gfCT9E1Go=
Message-Id: <6.2.5.6.2.20211107214455.0804f2a0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 07 Nov 2021 22:19:47 -0800
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>, ietf-privacy@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <daefa555bccc4eb4b6e61e51d85bde3d@huawei.com>
References: <8F4B97EA-665F-4A59-B99D-791B4AB9F2F7@yahoo.co.uk> <c3e9fe1b-8e48-a364-9e25-4084dac70889@meetinghouse.net> <3a6bf8ad-5492-0942-a451-6317e8a93705@network-heretics.com> <3e685576-a230-a7c4-f371-d66a55aa820d@necom830.hpcl.titech.ac.jp> <7a087707-499f-e3bf-8701-1a58930a8a22@meetinghouse.net> <4ec32d7a-a17b-635b-91bc-4152313d6800@necom830.hpcl.titech.ac.jp> <885e62bf-7d6a-4501-a48a-e7c2cbf20382@joelhalpern.com> <e59adb61-a55c-7f5f-a60a-40bf186c139d@necom830.hpcl.titech.ac.jp> <CAC8QAceMSrfkqGTYcMNr3JargO3gxJqTaEyf02LGHd-KVeUDHw@mail.gmail.com> <6286da3e-2beb-9556-089a-2e1951573b1e@gmail.com> <59c80b60-438f-b10f-ad61-ba839f6e4f95@necom830.hpcl.titech.ac.jp> <e834916e85ea47ef94fce07c23928d2b@huawei.com> <37b299c8-e821-07e5-6240-68fb9d1ca137@gmail.com> <23b450fb11eb4a51bb4ee837b5c52657@huawei.com> <a805b50d-3ccd-dd2a-4931-6c6dc9a8ede3@necom830.hpcl.titech.ac.jp> <CAC8QAceY1gtK5v3WGMd4OB0z826jDiDDw_g1LbjWef7MKTnrcg@mail.gmail.com> <eae026b8fc7a42eeb2210dcb156d5f56@huawei.com> <8007ec69-628a-448a-28f3-090b6fdab999@network-heretics.com> <ef39c3fdba804c15bcaacdd1616160ea@huawei.com> <6.2.5.6.2.20211105234600.094db288@elandnews.com> <daefa555bccc4eb4b6e61e51d85bde3d@huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-privacy/AnZEbQcsTke5dBvJ7n8HOiGu1sU>
Subject: Re: [ietf-privacy] Accurate history
X-BeenThere: ietf-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internet Privacy Discussion List <ietf-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-privacy/>
List-Post: <mailto:ietf-privacy@ietf.org>
List-Help: <mailto:ietf-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2021 06:24:42 -0000

Hi Vasilenko,
At 02:22 AM 07-11-2021, Vasilenko Eduard wrote:
>The context was about IPv6 addressing only, not the privacy on the 
>general scope.
>The second half of IPv6 address bits (64 from 128) are used only for 
>privacy now. RFC 8981.
>IPv6 is 64-bit addressing architecture because of this, not 128 as 
>many believe.
>The host generates different pseudo-random IIDs (64-bits) and uses 
>them to create many temporary addresses for different sessions.
>Keith Moore mentioned that it is privacy. Hence, the good wastage of 
>(2^64-1)/2^64 of IPv6 address space.
>I was arguing that it is fake privacy. Hence, not a justification to 
>waste so huge address space.

Thanks for the clarification about the privacy comment.

The address size of IPv6 is described as 128 bits in RFC 2460.  I 
suggest looking at "wastage" [1] from an address allocation 
perspective [2] instead of an address space perspective.  That might 
make discussion of other issues, e.g. privacy, less difficult.

Regards,
S. Moonesamy

1. There were probably some assumptions which made sense when the 
protocol was designed.
2. The allocation of addresses has an impact on privacy.