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

IETF Secretariat <ietf-secretariat@ietf.org> Tue, 18 October 2016 20:35 UTC

Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: dlnex@ietf.org
Delivered-To: dlnex@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED2C129472; Tue, 18 Oct 2016 13:35:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.35.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147682294801.30835.15229676723560958189.idtracker@ietfa.amsl.com>
Date: Tue, 18 Oct 2016 13:35:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dlnex/au0qDzpYng9Jcw9ejHlOTZZCmeQ>
Cc: matthew.bocci@nokia.com, dlnex@ietf.org, linda.dunbar@huawei.com
Subject: [DLNEX] New Non-WG Mailing List: DLNEX -- Discussion of reliable and deterministic latency attributes
X-BeenThere: dlnex@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org, 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: Tue, 18 Oct 2016 20:35:48 -0000

A new IETF non-working group email list has been created.

List address:dlnex@ietf.org
Archive: https://mailarchive.ietf.org/arch/search/?email_list=dlnex
To subscribe: 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.