Re: [Detnet-dp-dt] high level questions on detnet dataplane

Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es> Wed, 22 February 2017 11:17 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 987E61296E1 for <detnet-dp-dt@ietfa.amsl.com>; Wed, 22 Feb 2017 03:17:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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 pa1tGiuHwH-Y for <detnet-dp-dt@ietfa.amsl.com>; Wed, 22 Feb 2017 03:17:26 -0800 (PST)
Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (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 08DCF12968C for <detnet-dp-dt@ietf.org>; Wed, 22 Feb 2017 03:17:26 -0800 (PST)
Received: by mail-wr0-x242.google.com with SMTP id 89so1073071wrr.1 for <detnet-dp-dt@ietf.org>; Wed, 22 Feb 2017 03:17:25 -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=h2O1GgKKxyT+wkz+ouxK3lQpYMrPIqv/iUZzUcjYtfc=; b=bfcX9ZhNNIn6szSaDHU2VtI8Q5K5AkVkzuUqNKY++R2yB9898Z7o1KhW2Qsn9kgX4N NvOcz+Oy1u5/zfY+vyfZL6AQqp064xnGWX4IKtXOpIm+71sMIyKF3TYe0uopQvRZkH1s c3U50/ZU18H98qa5XoqO8E3O6wFWZ1NVoUI/QSjAqkFecy5MWrobbHUzNFv3E9Aupl9H jGiaY3TLLimy1WWBGer8BSNo0sKsjzo9ikc4QVNamBVzVDAW6PSBMrCCdvY/JiZUEXlx CrObYt/kl5XMKGo6m6nMJmkA6lN3nb6sjza6tXU4OOv3/aesetMNTmkr9Jag1ZyuuDLm V0gA==
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=h2O1GgKKxyT+wkz+ouxK3lQpYMrPIqv/iUZzUcjYtfc=; b=otvSwUjHIlAOarSUCeb7zK1adxltAERe0VY2qlWkxzUuSG7PcREk5YLGeVJWmhhh+b g5c6xp3iO/mryc/0E+Vw7qDFb2rTtuLqrr4FvEgmx9fAaFujHfbfJhBC/HZAw2BJW4jg A7bFm//zey/vM6JHv0O3hzeDLFREo8VtwUzOp7Qhp/5pZGEbiNiF72dhbk+qTLk6mbAI QYICzn5AGcJFGJdcefQLoanCK8nx2ceMJ1RtXiJc8Zlb+95iLFMVRGpR/bCSen6h1PMe b2ep3fB1HXsBsZA8HJsIIdDPBrHaEQ9fi/Ad9nYjru2lFGtWBqh3iHjbAwKmm9Eipqqx wUMQ==
X-Gm-Message-State: AMke39nSiNu4so/cjc1JB8vkL56jvVCgtaIjRpWl23TuYoTb9piXTVbRfmgbui5gpx5X0yNf
X-Received: by 10.223.164.1 with SMTP id d1mr9591626wra.90.1487762244477; Wed, 22 Feb 2017 03:17:24 -0800 (PST)
Received: from [10.117.28.103] ([212.201.111.75]) by smtp.gmail.com with ESMTPSA id 136sm1642657wms.32.2017.02.22.03.17.23 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 22 Feb 2017 03:17:24 -0800 (PST)
Message-ID: <1487762243.2981.16.camel@it.uc3m.es>
From: Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es>
To: Loa Andersson <loa@pi.nu>, detnet-dp-dt@ietf.org, DetNet Chairs <detnet-chairs@ietf.org>
Date: Wed, 22 Feb 2017 12:17:23 +0100
In-Reply-To: <1645a73b-0260-327f-c45b-8bb084235689@pi.nu>
References: <DBXPR07MB12832861ED58D86FD3D0A09AC510@DBXPR07MB128.eurprd07.prod.outlook.com> <F278A381-1E43-4607-8015-5CFDE871D382@broadcom.com> <DBXPR07MB1287715CE1D6AA6B6CC932DAC500@DBXPR07MB128.eurprd07.prod.outlook.com> <1645a73b-0260-327f-c45b-8bb084235689@pi.nu>
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/2GeEIkUllRSjmqmh56V_PnncTWQ>
Subject: Re: [Detnet-dp-dt] high level questions on detnet dataplane
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: Wed, 22 Feb 2017 11:17:28 -0000

Hi Loa,

On Wed, 2017-02-22 at 18:32 +0800, Loa Andersson wrote:
> Folks,
> 
> two questions, the first because I've be taling it for granted, the 
> second brought up bu two indenpendent people I talked about DetNet
> with.
> 
> - is a design criteria that the existing MPLS control plane protocols
>    shall be able to use with the DetNet dataplane?
> 
> - I've heard the opinion (from two different directions) that doing
>    replication/elimination other than at the egress/ingress will make
> the
>    solution to complicated. Do we have a good motiation why we need
> it?

I also have this question in mind. I've checked draft-ietf-detnet-dp-
alt-00 and found this:

"
4.5.  #5 Flow duplication and merging

[...]

   The solution alternative has to provide means for end systems, relay
   and edge nodes to be able to duplicate packets into duplicate flows,
   and later merge the flows into one for duplicate elimination.  The
   duplication and merging may take place at multiple points in the
   network in order to ensure that one (or more) equipment failure
   event(s) still leave at least one path intact for a deterministic
   networking flow.  The goal is again to enable hitless 1+1 protection
   in a way that no packet gets lost or there is no ramp up time when
   either one of the paths fails for one reason or another.
"

Not completely clear to me why we need to allow duplication and merging
at multiple points. 

I have also another question: are we considering somehow the
requirements that some detnet applications (e.g., crosshauling) might
require bidirectional flows to be symmetric?

Thanks,

Carlos

> 
> /Loa