IETF Logo Mail Archive

Re: [mif] WGLC for draft-ietf-mif-mpvd-id

Markus Stenberg <markus.stenberg@iki.fi> Fri, 06 November 2015 01:08 UTC

Return-Path: <markus.stenberg@iki.fi>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB4C91A8A78 for <mif@ietfa.amsl.com>; Thu, 5 Nov 2015 17:08:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level:
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=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 1hicMNrf91nS for <mif@ietfa.amsl.com>; Thu, 5 Nov 2015 17:08:37 -0800 (PST)
Received: from julia1.inet.fi (mta-out1.inet.fi [62.71.2.232]) by ietfa.amsl.com (Postfix) with ESMTP id 5717C1A8A23 for <mif@ietf.org>; Thu, 5 Nov 2015 17:08:37 -0800 (PST)
Received: from [192.168.43.129] (80.220.86.47) by julia1.inet.fi (9.0.002.03-2-gbe5d057) (authenticated as stenma-47) id 5613C7B100BA599F; Fri, 6 Nov 2015 03:07:24 +0200
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <28FFBD43-EEBC-4C65-8BA3-CE2E93A9DB2C@apple.com>
Date: Fri, 06 Nov 2015 10:08:26 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <924CA6D7-04C3-4CE3-BD88-C075BD42CA45@iki.fi>
References: <COL125-W4170BE78E2C2F41BC3A6B4B19B0@phx.gbl> <79C18793-758C-421A-A0C6-2F5625F1E17E@gmx.com> <55AD3922.8090009@gmail.com> <69E5A45D-C11A-4383-A4EE-AEF05675E718@gmx.com> <55AE2288.5070509@gmail.com> <74F2D07D-4FB2-4FB6-B482-EF202B4D533F@gmx.com> <55AF625B.5040506@gmail.com> <352EAA2D-0D69-40F6-8C6B-8980DD780AEA@gmx.com> <F3183EA8-8933-4592-A2DE-4602B6668696@apple.com> <6178F689-9321-41AD-B9AA-550C8A12FF05@gmail.com> <28FFBD43-EEBC-4C65-8BA3-CE2E93A9DB2C@apple.com>
To: Tommy Pauly <tpauly@apple.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mif/bnnOtYHfdQTcG0dGb1aHwPb_My4>
Cc: "mif@ietf.org" <mif@ietf.org>, Hui Deng <denghui02@hotmail.com>
Subject: Re: [mif] WGLC for draft-ietf-mif-mpvd-id
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mif/>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2015 01:08:39 -0000

From my point of view, main thing about the id should be to distinguish between PVDs _already stored_ on the host. Therefore, it is mostly a question of likeliness of conflict. I would phrase it somehow (sorry, no wordsmith) as highly unlikely to collide 64 bit octet blob. ULAs assume that 40 bits is enough for low collision chance on network scale, so 64 should be plenty.

That id could then map to bunch of actual PVD data. I would _personally_ recommend id to be hash of that PVD data (actual algorithm local choice as it should not be visble to the hosts nor their users).  Some subsections of PVD data might have to be defined to be not part of hash, e.g. lifetimes if they change frequently.

Cheers,

-Markus

v2.23.0 | Report a Bug | By Email