IETF Logo Mail Archive

Re: [Detnet-dp-dt] Data Plane Approach - Synchronization Traffic

Loa Andersson <loa@pi.nu> Thu, 26 January 2017 07:01 UTC

Return-Path: <loa@pi.nu>
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 E9987129495 for <detnet-dp-dt@ietfa.amsl.com>; Wed, 25 Jan 2017 23:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level:
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 lvFxnYrTSXEg for <detnet-dp-dt@ietfa.amsl.com>; Wed, 25 Jan 2017 23:01:09 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B257512940A for <detnet-dp-dt@ietf.org>; Wed, 25 Jan 2017 23:01:09 -0800 (PST)
Received: from [192.168.1.11] (unknown [122.52.28.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 0825718013BE; Thu, 26 Jan 2017 08:01:06 +0100 (CET)
To: Tal Mizrahi <talmi@marvell.com>, "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
References: <2d23229047a4428684fa1194fd95261c@IL-EXCH01.marvell.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <d3d8326e-b22a-df42-a7ed-6d3f1fca1e1c@pi.nu>
Date: Thu, 26 Jan 2017 15:01:01 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <2d23229047a4428684fa1194fd95261c@IL-EXCH01.marvell.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/QvXSIDCXOe1Ob6Bjc-p3D_FhH_Y>
Subject: Re: [Detnet-dp-dt] Data Plane Approach - Synchronization Traffic
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: Thu, 26 Jan 2017 07:01:12 -0000

Tal,

On 2017-01-26 14:44, Tal Mizrahi wrote:
> Hi,
>
> I realize this is a bit off-topic, but one of the things I am wondering about is how synchronization traffic (PTP) is forwarded in the context of the data plane approaches we have been considering.
> Is PTP transported as a DETNET flow?
> - If the answer is no: does that mean we are assuming that synchronization is achieved at a different layer, possibly requiring dedicated communication between the customer and provider?
> - If the answer is yes: not sure replication and elimination makes sense for PTP.

Why is that?

/Loa
>
> Will be happy to hear your thoughts, and apologies if this has already been discussed elsewhere and I am not aware.
>
> Cheers,
> Tal.
> _______________________________________________
> Detnet-dp-dt mailing list
> Detnet-dp-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet-dp-dt
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

v2.8.7 | Report a Bug | By Email