Re: [Detnet-dp-dt] about identity labels.. was Re: new versions of my slides

Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es> Sat, 04 March 2017 10:01 UTC

Return-Path: <cjbc@it.uc3m.es>
X-Original-To: detnet-dp-dt@ietfa.amsl.com
Delivered-To: detnet-dp-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F97D129469 for <detnet-dp-dt@ietfa.amsl.com>; Sat, 4 Mar 2017 02:01:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=it-uc3m-es.20150623.gappssmtp.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 TQpW197kQWhm for <detnet-dp-dt@ietfa.amsl.com>; Sat, 4 Mar 2017 02:01:34 -0800 (PST)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (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 7F0C11294B2 for <detnet-dp-dt@ietf.org>; Sat, 4 Mar 2017 02:01:34 -0800 (PST)
Received: by mail-wm0-x22a.google.com with SMTP id n11so31576542wma.1 for <detnet-dp-dt@ietf.org>; Sat, 04 Mar 2017 02:01:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it-uc3m-es.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:reply-to:to:date:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=Fo215ws/XAGi694RPkWDHTjFzHSVYWv0lGs0DqMETUg=; b=ai0mE1LEYLqNciDRpEZt+QcsBpKjodinIVevVg8zWCBciXmp2L01P9ma3IHjzE4LH2 V5ulmqrbdAbLBTuNPH3tDVnrM97KvemTZgrDCEtDEdElKUCpw1e2is1r5e17+IaqpHWX OJB6QzZkdqM/W0iUGJqfE4Z5c5bbYl//X8uv0huBsUnhqH/xqRocwAcS4szMWywH/f0O RuYCKG5rBCQjWK8YxcJV0gYPuobgxuRvbvlnHa/vowTpRZMO8tLP1va+zxUrxeVJ6pw0 nbAFVvHZoRfqzgk8fVW+D356k46S5r4y1wRnTpGN6Mvx/k8iwkK9+KIeS38wwHL4E1Nq aS+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:reply-to:to:date :in-reply-to:references:organization:mime-version :content-transfer-encoding; bh=Fo215ws/XAGi694RPkWDHTjFzHSVYWv0lGs0DqMETUg=; b=typk1XpKNTQXC2gFjNBpd41+UqD8+GxrlntXpgEiNDvcZWFv7IZATJCM5rMiZF2xrw auKKLgcc7M5D4i5/w2QGnhlOsaHzFfuoG6PwqLWUDJuPt1MCcgUNm+oWa8R+D/XAhhYd tSuKp0i767enwJM9zLYLcHaaIJVC3wimIcoZOIccg/kYRCknNKUDq2zB+RPFKt9XX0rn Qze3vnJZWWcQQVA1HmeGxrcGgEXgb3ZRW7PLWY+0xm1zr+cQYixN8Oho71gH0G5XmRXw HCOitQkGU05dHMkFA5qkHFEExG6e2J9KLoGaN9f1tAthtS/MhX00fscpxzqr10AzyeJM dR3Q==
X-Gm-Message-State: AMke39mTCjPVl8TIvpEit4cCa8qR3PZlE3430IY4uGDXU8cLquSU5gnKUmDivkxJ4RxJblD3
X-Received: by 10.28.44.66 with SMTP id s63mr5794286wms.77.1488621692831; Sat, 04 Mar 2017 02:01:32 -0800 (PST)
Received: from cjbc_dell.lan (85.251.161.16.dyn.user.ono.com. [85.251.161.16]) by smtp.gmail.com with ESMTPSA id 11sm18602507wrb.10.2017.03.04.02.01.31 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 04 Mar 2017 02:01:32 -0800 (PST)
Message-ID: <1488621691.3705.1.camel@it.uc3m.es>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: Jouni Korhonen <jouni.korhonen@broadcom.com>, "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
Date: Sat, 04 Mar 2017 11:01:31 +0100
In-Reply-To: <75B5D515-73E0-44C0-8CE2-824731505589@broadcom.com>
References: <bc92627a-e1c2-ca97-9af9-8aedd37a772c@pi.nu> <3DF0466E9510274382F5B74499ACD6F8C3CB2F@dfwpml702-chm.exmail.huawei.com> <3DF0466E9510274382F5B74499ACD6F8C3CB40@dfwpml702-chm.exmail.huawei.com> <cde5c41f-2a48-7007-279a-ffa44ef43bec@pi.nu> <DBXPR07MB128512162D9FA45A2A10624AC570@DBXPR07MB128.eurprd07.prod.outlook.com> <75B5D515-73E0-44C0-8CE2-824731505589@broadcom.com>
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.22.4-1
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/BZ04Ogw6iUfDarr4jFxW-1qE36M>
Subject: Re: [Detnet-dp-dt] about identity labels.. was Re: new versions of my slides
X-BeenThere: detnet-dp-dt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: cjbc@it.uc3m.es
List-Id: DetNet WG Data Plane Design Team <detnet-dp-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet-dp-dt>, <mailto:detnet-dp-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet-dp-dt/>
List-Post: <mailto:detnet-dp-dt@ietf.org>
List-Help: <mailto:detnet-dp-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet-dp-dt>, <mailto:detnet-dp-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Mar 2017 10:01:37 -0000

Hi Jouni,

On Wed, 2017-03-01 at 18:51 -0800, Jouni Korhonen wrote:
> Folks,
> 
> Back to d-id.. I understand the intent and need for the d-id label.
> What I cannot immediately see it is going to help the FRER
> implementation. Using Loa’s slides as a reference: assume G and D
> both assign the same d-pw1 label values to F and A. Fortunately the
> combination of d-id+d-pw is unique. However, when packets arrive at
> B, the seqnum+history lookup would need to use both d-id+d-pw as a
> combined key. This is getting cumbersome. One would need to map d-
> id+d-pw to something that is locally unique in LFIB or use d-id as an
> indirect index to separate LFIB tables holding d-pw associated
> information. Since d-id and d-pw are separate labels this ends up
> two-three lookups and carrying along the history metadata. Depending
> on the flexibility of the memory sub-system one might face
> interesting restrictions, for example on the size of the LFIB tables
> first indexed by d-id.
> 
> I know this was very implementation dependent rant, but how I
> currently see d-id, it has made life easier for a control plane and a
> provisioning. At the same time it seems to make the life of the hw
> and data structure design hard.
> 
> So far the “cleanest” solution for me has been the one with d-pw
> ranges configured into T-DetNet-PE devices - to prevent collisions.
> That one had the downside of fixed allocations put into nodes by the
> network administrator.
> 

I share your view. I like more the approach in which we avoid having
the additional d-id (and we use globally unique d-pw labels). I
acknowledge see all the advantages it brings, but I also share the
concerns about the extra label layer and the potentially cumbersome
processing. There have been also some discussions about the size of the
label pool if they need to be globally unique. I think we need to have
some discussion documented in the draft about this if we go in this
direction.

Carlos

> - Jouni
>