IETF Logo Mail Archive

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

Lou Berger <lberger@labn.net> Wed, 22 February 2017 11:09 UTC

Return-Path: <lberger@labn.net>
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 A78EC1296DF for <detnet-dp-dt@ietfa.amsl.com>; Wed, 22 Feb 2017 03:09:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.888
X-Spam-Level:
X-Spam-Status: No, score=-3.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 LFNEXydHWMcN for <detnet-dp-dt@ietfa.amsl.com>; Wed, 22 Feb 2017 03:09:00 -0800 (PST)
Received: from gproxy3-pub.mail.unifiedlayer.com (gproxy3-pub.mail.unifiedlayer.com [69.89.30.42]) by ietfa.amsl.com (Postfix) with SMTP id 7CC3A1296DE for <detnet-dp-dt@ietf.org>; Wed, 22 Feb 2017 03:09:00 -0800 (PST)
Received: (qmail 31286 invoked by uid 0); 22 Feb 2017 11:08:57 -0000
Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy3.mail.unifiedlayer.com with SMTP; 22 Feb 2017 11:08:57 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with id nn8t1u00r2SSUrH01n8wGG; Wed, 22 Feb 2017 04:08:57 -0700
X-Authority-Analysis: v=2.1 cv=GtPRpCFC c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=kj9zAlcOel0A:10 a=n2v9WMKugxEA:10 a=i0EeH86SAAAA:8 a=48vgC7mUAAAA:8 a=-S4XveCqY4Bwomd_HQgA:9 a=CjuIK1q_8ugA:10 a=02toJ7V-nxh73JlV0Smw:22 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject: References:In-Reply-To:Message-ID:Date:To:From:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=hiur6doMo08rPHITA/f+huqesvr2EFRu8Q05CO+CBOY=; b=ZYikiZt3YriMyrA/fPWArjlPvh XQRqH/V60XNAUlRWIXl5dGcZGJw4EFqy72qnAyQHhoee1APrnM/gR71ncy/S3ZrkFgsh2eYUAdj7Y gOVlfAl7Zhx2F6RSdag8WyLHg;
Received: from pool-100-15-85-191.washdc.fios.verizon.net ([100.15.85.191]:45140 helo=[11.4.0.102]) by box313.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1cgUmz-000584-C0; Wed, 22 Feb 2017 04:08:53 -0700
From: Lou Berger <lberger@labn.net>
To: Loa Andersson <loa@pi.nu>, <detnet-dp-dt@ietf.org>, DetNet Chairs <detnet-chairs@ietf.org>
Date: Wed, 22 Feb 2017 06:08:56 -0500
Message-ID: <15a65828140.27fd.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
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>
User-Agent: AquaMail/1.7.2-121 (build: 100700200)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.85.191
X-Exim-ID: 1cgUmz-000584-C0
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-85-191.washdc.fios.verizon.net ([11.4.0.102]) [100.15.85.191]:45140
X-Source-Auth: lberger@labn.net
X-Email-Count: 2
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/Yu79qvhpdn9KXciqggoGJUuKuzE>
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
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:09:01 -0000

Loa,


On February 22, 2017 5:33:20 AM Loa Andersson <loa@pi.nu> 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?
>

This is more a wg question than DT one, and we're not there yet.  I'd say 
the intent *at this point* is that they should be allowed for, and any work 
done by the DT that would impact / limit will need to be documented and 
discussed.

Lou

> - 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?
>
> /Loa
> --
>
>
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>
> _______________________________________________
> Detnet-dp-dt mailing list
> Detnet-dp-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet-dp-dt
>

v2.8.7 | Report a Bug | By Email