IETF Logo Mail Archive

[Detnet-dp-dt] one question on S-DetNet-PEs

Loa Andersson <loa@pi.nu> Wed, 08 March 2017 13:03 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 34BE312966F for <detnet-dp-dt@ietfa.amsl.com>; Wed, 8 Mar 2017 05:03:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 kfGwecIwy1Ex for <detnet-dp-dt@ietfa.amsl.com>; Wed, 8 Mar 2017 05:03:31 -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 D488F12966A for <detnet-dp-dt@ietf.org>; Wed, 8 Mar 2017 05:03:30 -0800 (PST)
Received: from [192.168.1.11] (unknown [119.95.38.221]) (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 EAAC218013D1 for <detnet-dp-dt@ietf.org>; Wed, 8 Mar 2017 14:03:28 +0100 (CET)
To: "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
From: Loa Andersson <loa@pi.nu>
Message-ID: <74ee1719-053f-e12f-304c-f3fa9cf286f5@pi.nu>
Date: Wed, 8 Mar 2017 21:03:25 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/rG-pWgP_vFlxsK4XZKe2YOtWpN0>
Subject: [Detnet-dp-dt] one question on S-DetNet-PEs
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, 08 Mar 2017 13:03:32 -0000

Folks,

There might be a simple answer, but I don't see it just now.

Suppose we have a network, where we designate a certain number of
nodes as S-DetNet-PEs, to build a nice overlay DetNet.

Assume that we also designate another set of nodes as S-DetNet-PEs
for another overlay DetNet.

Also assume that some nodes that are S-DetNet-PE in one network
are P's in the other.

If we signal that we have have a detnet-ms-pw going through a P node
that is capable of doing elimination/replication, how do we stop the
P-node from doing that?

This was something that the T-Lables did for us.

/Loa
-- 


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