Re: [mpls] [Detnet] Help wanted in detnet

Lou Berger <lberger@labn.net> Sun, 22 January 2017 23:25 UTC

Return-Path: <lberger@labn.net>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E14712947B for <mpls@ietfa.amsl.com>; Sun, 22 Jan 2017 15:25:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.156
X-Spam-Level:
X-Spam-Status: No, score=-3.156 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.156, 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 wk_MLUGuOvHF for <mpls@ietfa.amsl.com>; Sun, 22 Jan 2017 15:25:43 -0800 (PST)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) by ietfa.amsl.com (Postfix) with SMTP id E43A8129477 for <mpls@ietf.org>; Sun, 22 Jan 2017 15:25:42 -0800 (PST)
Received: (qmail 21616 invoked by uid 0); 22 Jan 2017 23:25:39 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy6.mail.unifiedlayer.com with SMTP; 22 Jan 2017 23:25:39 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with id bbRb1u00M2SSUrH01bReEB; Sun, 22 Jan 2017 16:25:39 -0700
X-Authority-Analysis: v=2.1 cv=YuCcGeoX 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=IgFoBzBjUZAA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=48vgC7mUAAAA:8 a=AEDFM0qtAAAA:8 a=oDAgVuGWUbNHv24R1X8A:9 a=7U8PblL76EH-Qy0r:21 a=TA6A2QWcWSgaaYax:21 a=CjuIK1q_8ugA:10 a=bAYZg8X5nFwA:10 a=UXQz2jJI57UA:10 a=un45IlilgiACyq7YEsAA:9 a=8-Zwe7KDYJyXcBPL:21 a=rWFxRt0EX17nccGa:21 a=BjBjrUqITmSQrCJq:21 a=UiCQ7L4-1S4A:10 a=6UIaq3Bcl8oA:10 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 a=w1C3t2QeGrPiZgrLijVG:22 a=NCq4FBG6EvGFEERSFaZp:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Type:MIME-Version:Subject:References:In-Reply-To: Message-ID:Date:CC:To:From:Sender:Reply-To:Content-Transfer-Encoding: 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=trrLIj64nHBp9NS33aTjzwIy6/f4FX07jjJf/Ixi218=; b=az9trBTCNyhR0YF4t6LSSDnNQ1 NO6UNsyeG58wasYzhON0X3nYcJ9lteKDhRmr967x2jKO0AU8qaAE1rawrt0/gEIIZvAtaeprXs37p GOYPnlXrV4KH4FITMRJqSAcX3;
Received: from pool-100-15-85-191.washdc.fios.verizon.net ([100.15.85.191]:41743 helo=[11.4.0.102]) by box313.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1cVRVv-0006UO-3N; Sun, 22 Jan 2017 16:25:35 -0700
From: Lou Berger <lberger@labn.net>
To: <adrian@olddog.co.uk>, "'John Dowdell'" <john.dowdell.ietf@gmail.com>
Date: Sun, 22 Jan 2017 18:25:34 -0500
Message-ID: <159c87f92e8.27fd.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <0a6d01d274fe$2a87e530$7f97af90$@olddog.co.uk>
References: <86C8BF8E-7475-484F-89DD-62D428C96983@gmail.com> <0a6d01d274fe$2a87e530$7f97af90$@olddog.co.uk>
User-Agent: AquaMail/1.7.2-121 (build: 100700200)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------159c87fc6d01ac727fd439be388"
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: 1cVRVv-0006UO-3N
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]:41743
X-Source-Auth: lberger@labn.net
X-Email-Count: 3
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/hepV8S_3dsus2vOmoECu77N2_nw>
Cc: mpls@ietf.org, detnet@ietf.org, teas@ietf.org
Subject: Re: [mpls] [Detnet] Help wanted in detnet
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jan 2017 23:25:44 -0000

Hi  adrian.

I think we have good synergy now happening on the participant and chair 
levels.  Check out [1] as one example...

Lou
[1] https://www.ietf.org/mail-archive/web/detnet/current/msg00887.html


On January 22, 2017 5:24:17 PM "Adrian Farrel" <adrian@olddog.co.uk> wrote:

> Hey John,
>
> I realise that your email was two months ago, but I don't see any responses in
> the archive and so I thought I would try to understand why by re-reading your
> email.
>
> I think it is very probably completely unclear to everyone who is not following
> Detnet exactly what you're asking for.
>
> Reading your email (and none of the Detnet documents) I am not clear 
> whether you
> plan to transport deterministic Ethernet over some as yet unspecified data 
> plane
> (which you might choose or enhance based on its capabilities), whether you
> propose to map the features of the transported deterministic Ethernet to
> features of the transport, whether you hope to map the features of the
> deterministic Ethernet to features of the transport so that only the data is
> actually transported, or what. You could, for example, use a transport that has
> no scheduling and queueing support, but that is also non-blocking.
>
> Indeed, the word "transport" probably immediately made half of your audience
> think one thing (transport network) and the other half another thing (transport
> layer protocol).
>
> Of course, I went the extra mile ;-) and looked at your slide. Sadly no light
> was shed.
>
> I suspect the answer you're looking for is not "why not use deterministic
> Ethernet as your transport?" and similarly "have you thought of using a 
> photonic
> network?"
>
> Can you better phrase your question for the audience?
>
> Thanks,
> Adrian
>
> From: detnet [mailto:detnet-bounces@ietf.org] On Behalf Of John Dowdell
> Sent: 15 November 2016 05:32
> To: teas@ietf.org; mpls@ietf.org; detnet@ietf.org
> Subject: [Detnet] Help wanted in detnet
>
> Hi all in mpls and teas groups (consolidating earlier posting only on mpls)
>
> Over in detnet wg we are working on transporting deterministic Ethernet (e.g.
> from 802.1TSN LANs) across the wide area for applications such as industrial
> control and audio/video broadcast. One of the key assumptions is that the
> underlying transport already has sufficient scheduling and queueing support to
> allow proper extension of time-sensitive (or even time-critical) traffic over,
> for example, MPLS.
>
> To help us validate that assumption, please can someone volunteer to help us?
> Feel free to come over to the detnet list. Recommendations on exactly which
> flavour(s) of MPLS and/or configurations and/or gotchas would be most welcome.
>
> The slides in question are here
> https://www.ietf.org/proceedings/97/slides/slides-97-detnet-detnet-data-plane-02
> .pptx, slide 4.
>
> Many thanks in anticipation.
>
> John
>
>
>
>
>
>
>
> ----------
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet
>