Re: [DLNEX] [Detnet] FW: New Non-WG Mailing List: DLNEX -- Discussion of reliable and deterministic latency attributes

Lou Berger <lberger@labn.net> Thu, 20 October 2016 19:44 UTC

Return-Path: <lberger@labn.net>
X-Original-To: dlnex@ietfa.amsl.com
Delivered-To: dlnex@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C96171296DF for <dlnex@ietfa.amsl.com>; Thu, 20 Oct 2016 12:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.502
X-Spam-Level:
X-Spam-Status: No, score=-1.502 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=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no 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 KLrucy8bQeyy for <dlnex@ietfa.amsl.com>; Thu, 20 Oct 2016 12:44:48 -0700 (PDT)
Received: from gproxy9-pub.mail.unifiedlayer.com (gproxy9-pub.mail.unifiedlayer.com [69.89.20.122]) by ietfa.amsl.com (Postfix) with SMTP id 22EB91296BC for <dlnex@ietf.org>; Thu, 20 Oct 2016 12:35:45 -0700 (PDT)
Received: (qmail 12966 invoked by uid 0); 20 Oct 2016 19:35:44 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy9.mail.unifiedlayer.com with SMTP; 20 Oct 2016 19:35:44 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with id xvbg1t0112SSUrH01vbjlS; Thu, 20 Oct 2016 13:35:44 -0600
X-Authority-Analysis: v=2.1 cv=KLfJUj1o 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=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=CH0kA5CcgfcA:10 a=Q-fNiiVtAAAA:8 a=wU2YTnxGAAAA:8 a=pGLkceISAAAA:8 a=AUd_NHdVAAAA:8 a=9qxNCY_qAAAA:8 a=48vgC7mUAAAA:8 a=i0EeH86SAAAA:8 a=fdgzkQ7Ff76vt9hW5PwA:9 a=VC2IY7vq5sI5JajD:21 a=t7iCXiolvrOacOC7:21 a=QEXdDO2ut3YA:10 a=Fp8MccfUoT0GBdDC_Lng:22 a=Yz9wTY_ffGCQnEDHKrcv:22 a=6kGIvZw6iX1k4Y-7sg4_:22 a=TSZmLRzkpGLBZRr3r8m8:22 a=A2X48xt2e1hG9NJDz63Y:22 a=w1C3t2QeGrPiZgrLijVG:22 a=02toJ7V-nxh73JlV0Smw: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:In-Reply-To:MIME-Version :Date:Message-ID:From:Cc:References:To:Subject; bh=l3BSWCE0vV1DKhCOlXb/z4oC3U/+CP0gWJ1zQy6w3Z0=; b=08sTkzOXq6bdOyptDWAo9zbMya Dm+dbMN1f0zP8kg0xt03T2Fzphb07VQDmlOA5cPeEgKo+771e7hQynvpOSZV1rHtKx0nUo1jfCieo h0C19bPNeLJrcULVzAYOlM1k9;
Received: from pool-100-15-85-191.washdc.fios.verizon.net ([100.15.85.191]:41139 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86_1) (envelope-from <lberger@labn.net>) id 1bxJ7s-0006Fk-M0; Thu, 20 Oct 2016 13:35:40 -0600
To: Linda Dunbar <linda.dunbar@huawei.com>, Pat Thaler <pat.thaler@broadcom.com>
References: <E4FAC118-EC7C-4BD8-8A3C-8A7824F6BDD9@cisco.com> <CAG4d1rc-DNeNB8E7Y9m+=yraYTfpvWV1YJ8Q6TfvkWiGZdts1A@mail.gmail.com> <d2c12e06-3149-56e6-4ca8-806a1eeddc63@labn.net> <CAJt_5Ej=6RdSG-r0PpeAb8Xf9EjV-ssyyXK58N3eJ=jeve0BVw@mail.gmail.com> <4A95BA014132FF49AE685FAB4B9F17F657F5D2FD@dfweml501-mbb>
From: Lou Berger <lberger@labn.net>
Message-ID: <108fba9d-2879-78b2-4152-95d9c16692dc@labn.net>
Date: Thu, 20 Oct 2016 15:35:36 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F657F5D2FD@dfweml501-mbb>
Content-Type: text/plain; charset=UTF-8
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: 1bxJ7s-0006Fk-M0
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-85-191.washdc.fios.verizon.net ([IPv6:::1]) [100.15.85.191]:41139
X-Source-Auth: lberger@labn.net
X-Email-Count: 7
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/dlnex/GR-DM3F3z6fIbkmmYAir9jPjf0o>
Cc: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, "dlnex@ietf.org" <dlnex@ietf.org>, "Patrick Wetterwald \(pwetterw\)" <pwetterw@cisco.com>, Alia Atlas <akatlas@gmail.com>, "matthew.bocci@nokia.com" <matthew.bocci@nokia.com>, "detnet@ietf.org" <detnet@ietf.org>
Subject: Re: [DLNEX] [Detnet] FW: New Non-WG Mailing List: DLNEX -- Discussion of reliable and deterministic latency attributes
X-BeenThere: dlnex@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Discussion of reliable and deterministic latency attributes <dlnex@ietf.org>
List-Id: Discussion of reliable and deterministic latency attributes <dlnex.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dlnex>, <mailto:dlnex-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dlnex/>
List-Post: <mailto:dlnex@ietf.org>
List-Help: <mailto:dlnex-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dlnex>, <mailto:dlnex-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2016 19:44:51 -0000

Hi Linda,

    Could you (or anyone on DLNEX) elaborate on the type of documents
you're thinking of delivering?

In detnet, we've so far been more focused on applications/use cases and
data plane options.  But we're really looking forward to
contributions/drafts on the information that is needed to support the
control of deterministic flows.  The charter states this as:

    Data flow information model: This work will identify the
    information needed for flow establishment and control and be
    used by reservation protocols and YANG data models. The work
    will be independent from the protocol(s) used to control the
    flows (e.g. YANG+NETCONF/RESTCONF, PCEP or GMPLS).

Any drafts/contributions on this topic or willingness to help define
these would be great. 

If there are sufficiently developed ideas, we could probably even find
time to discuss in our Seoul session.  (Or perhaps just informally, if
there aren't.)

Thanks,
Lou

On 10/19/2016 7:09 PM, Linda Dunbar wrote:
>
> Pat,
>
>  
>
> What you said is so true: “The network can't provide a bounded or
> deterministic latency to an unbounded flow”.
>
>  
>
> DETNET charter starts with
>
> The Deterministic Networking (DetNet) Working Group focuses on
> deterministic data paths that operate over Layer 2 bridged and Layer 3
> routed segments, where such paths can provide bounds on latency, loss,
> and packet delay variation (jitter), and high reliability
>
>  
>
> If I understand it correctly, DETNET focuses on the enabling
> technologies to ensure deterministic latency path across a set of nodes.
>
>  
>
> E2E low latency services has many issues, such as:
>
> ·        There could be “bounded flows” that need low latency services
> mixed with other traffic in the network.
>
> ·        E2E services may have to go through many hops, links with
> some links not supporting DETNET.
>
> ·        there could be various protection/re-route mechanisms which
> all increase latency.
>
> ·        etc
>
>  
>
> Some problems specific to WAN include how to isolate the various
> service traffic, and provide maximum manageability to upper layers.
>
>  
>
> One company in NANOG asked why not use ICMP to mark the delay along
> the path to give upper link, ..
>
>  
>
> Linda
>
>  
>
>  
>
> Linda
>
>  
>
> *From:*Pat Thaler [mailto:pat.thaler@broadcom.com]
> *Sent:* Wednesday, October 19, 2016 5:25 PM
> *To:* Lou Berger <lberger@labn.net>
> *Cc:* Alia Atlas <akatlas@gmail.com>om>; Patrick Wetterwald (pwetterw)
> <pwetterw@cisco.com>om>; matthew.bocci@nokia.com; Pascal Thubert
> (pthubert) <pthubert@cisco.com>om>; detnet@ietf.org; dlnex@ietf.org;
> Linda Dunbar <linda.dunbar@huawei.com>
> *Subject:* Re: [Detnet] FW: New Non-WG Mailing List: DLNEX --
> Discussion of reliable and deterministic latency attributes
>
>  
>
> We have been having recent discussions about latency such as what type
> of latency is important.
>
>  
>
> As far as the "feasibility exercise for achieving reliable and
> deterministic latency through a network element or a segment" that
> overlaps very much what DetNet and IEEE 802.1 TSN have been doing. I
> believe we have already shown that it is feasible and are not on
> specifying how to do that. I'm concerned about the overlap between
> what that paragraph describes and our work.
>
>  
>
> There could be useful work on communication from the upper layer of
> the flow characteristics, behavior and requirements. There probably is
> some gap to fill that would help our work. I'm concerned that the list
> description focuses only on exposing lower layer characteristics to
> the upper layer. The network can't provide a bounded or deterministic
> latency to an unbounded flow - to determine what latency can be
> provided, one has to know something about the bandwidth utilization of
> the flow.
>
>  
>
> Regards,
>
> Pat
>
>  
>
> On Wed, Oct 19, 2016 at 1:59 PM, Lou Berger <lberger@labn.net
> <mailto:lberger@labn.net>> wrote:
>
>     Hi Alia,
>
>         Overlap looks likely.  I hope that when it does occur, you send
>     folks over here to contribute -- additional input / WG participation
>     would be great!  (For folks not familiar with DetNet, check out our
>     charter at https://datatracker.ietf.org/wg/detnet/charter/
>     <https://datatracker.ietf.org/wg/detnet/charter/>)
>
>     I expect we'll have some good data plane centric discussions at this
>     meeting, for those who may be interested (there's even still time to
>     submit related drafts!)
>
>     Cheers,
>
>     Lou
>
>     DetNet Co-chair
>
>     On 10/19/2016 11:46 AM, Alia Atlas wrote:
>     > Hi Patrick,
>     >
>     > The discussion intended on dlnex, a non-WG mailing list, is, I
>     think,
>     > broader - spanning the range of communications between upper layer
>     > applications and the network.  It is not clear yet what work might
>     > develop.  Be sure that I will be watching for any specific overlap
>     > with DetNet.
>     >
>     > I feel that it is useful to make it easy for groups to have a
>     list to
>     > brainstorm about their ideas before work is mature enough to
>     consider
>     > for standardization.
>     >
>     > Regards,
>     > Alia
>     >
>     > On Wed, Oct 19, 2016 at 8:17 AM, Patrick Wetterwald (pwetterw)
>     > <pwetterw@cisco.com <mailto:pwetterw@cisco.com>
>     <mailto:pwetterw@cisco.com <mailto:pwetterw@cisco.com>>> wrote:
>     >
>     >     Can someone explain me why this mailing list is created
>     outside of
>     >     DetNet?
>     >
>     >     This sounds like a subset of Detnet no?
>     >
>     >     Thanks,
>     >
>     >     Patrick
>     >
>     >
>     >     On 19/10/2016, 07:56, "detnet on behalf of Pascal Thubert
>     >     (pthubert)" <detnet-bounces@ietf.org
>     <mailto:detnet-bounces@ietf.org>
>     >     <mailto:detnet-bounces@ietf.org
>     <mailto:detnet-bounces@ietf.org>> on behalf of pthubert@cisco.com
>     <mailto:pthubert@cisco.com>
>     >     <mailto:pthubert@cisco.com <mailto:pthubert@cisco.com>>> wrote:
>     >
>     >         From: IETF-Announce
>     [mailto:ietf-announce-bounces@ietf.org
>     <mailto:ietf-announce-bounces@ietf.org>
>     >     <mailto:ietf-announce-bounces@ietf.org
>     <mailto:ietf-announce-bounces@ietf.org>>] On Behalf Of IETF
>     Secretariat
>     >         Sent: mardi 18 octobre 2016 22:36
>     >         To: IETF Announcement List <ietf-announce@ietf.org
>     <mailto:ietf-announce@ietf.org>
>     >     <mailto:ietf-announce@ietf.org <mailto:ietf-announce@ietf.org>>>
>     >         Cc: matthew.bocci@nokia.com
>     <mailto:matthew.bocci@nokia.com> <mailto:matthew.bocci@nokia.com
>     <mailto:matthew.bocci@nokia.com>>;
>     >     dlnex@ietf.org <mailto:dlnex@ietf.org>
>     <mailto:dlnex@ietf.org <mailto:dlnex@ietf.org>>;
>     linda.dunbar@huawei.com <mailto:linda.dunbar@huawei.com>
>     >     <mailto:linda.dunbar@huawei.com
>     <mailto:linda.dunbar@huawei.com>>
>     >         Subject: New Non-WG Mailing List: DLNEX -- Discussion of
>     >     reliable and deterministic latency attributes
>     >
>     >
>     >         A new IETF non-working group email list has been created.
>     >
>     >         List address:dlnex@ietf.org
>     <mailto:address%3Adlnex@ietf.org> <mailto:address%3Adlnex@ietf.org
>     <mailto:address%253Adlnex@ietf.org>>
>     >         Archive:
>     >     https://mailarchive.ietf.org/arch/search/?email_list=dlnex
>
>     >     <https://mailarchive.ietf.org/arch/search/?email_list=dlnex>
>     >         To subscribe:
>     https://www.ietf.org/mailman/listinfo/dlnex
>     <https://www.ietf.org/mailman/listinfo/dlnex>
>     >     <https://www.ietf.org/mailman/listinfo/dlnex>
>     >
>     >         Purpose:
>     >         DLNEX is to discuss various latency characteristics that can
>     >     be exposed by network elements or segments and to explore if
>     there
>     >     are any latency related attributes that can be utilized by upper
>     >     layer. For example, could there be latency exposure that upper
>     >     layer can utilize to plan how to distribute their content to the
>     >     right edges to achieve optimal user experience? Or something
>     used
>     >     by Interactive AR controller to optimize their services? Is
>     there
>     >     any value gained by upper layer expressing that they would
>     rather
>     >     have fixed latency than losing packets?
>     >
>     >         The discussion is to answer questions like: are there any
>     >     effective interaction/coordination between upper layer and lower
>     >     layer to achieve more efficient optimization for latency
>     sensitive
>     >     services?
>     >
>     >         This discussion group is also a place to showcase the
>     state of
>     >     the arts in latency optimized switching architecture and
>     interface
>     >     designs, as the feasibility exercise for achieving reliable and
>     >     deterministic latency through a network element or a segment.
>     >     Those latency exposures are the foundation for (future) latency
>     >     optimized control plane.
>     >
>     >
>     >         For additional information, please contact the list
>     >     administrators.
>     >
>     >         _______________________________________________
>     >         detnet mailing list
>
>     >         detnet@ietf.org <mailto:detnet@ietf.org>
>     <mailto:detnet@ietf.org <mailto:detnet@ietf.org>>
>     >         https://www.ietf.org/mailman/listinfo/detnet
>     >     <https://www.ietf.org/mailman/listinfo/detnet>
>     >
>     >
>     >     _______________________________________________
>     >     detnet mailing list
>     >     detnet@ietf.org <mailto:detnet@ietf.org>
>     <mailto:detnet@ietf.org <mailto:detnet@ietf.org>>
>     >     https://www.ietf.org/mailman/listinfo/detnet
>
>     >     <https://www.ietf.org/mailman/listinfo/detnet>
>     >
>     >
>     >
>     >
>     > _______________________________________________
>     > detnet mailing list
>     > detnet@ietf.org <mailto:detnet@ietf.org>
>     > https://www.ietf.org/mailman/listinfo/detnet
>
>     _______________________________________________
>     detnet mailing list
>     detnet@ietf.org <mailto:detnet@ietf.org>
>     https://www.ietf.org/mailman/listinfo/detnet
>
>  
>
>
>
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet