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

Loa Andersson <loa@pi.nu> Thu, 09 March 2017 10:11 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 D77B312711D for <detnet-dp-dt@ietfa.amsl.com>; Thu, 9 Mar 2017 02:11:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 qFA1e3qDoLIS for <detnet-dp-dt@ietfa.amsl.com>; Thu, 9 Mar 2017 02:11:05 -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 6A184129428 for <detnet-dp-dt@ietf.org>; Thu, 9 Mar 2017 02:11:05 -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 BD05A18013DA; Thu, 9 Mar 2017 11:11:02 +0100 (CET)
To: =?UTF-8?Q?Bal=c3=a1zs_Varga_A?= <balazs.a.varga@ericsson.com>, "jouni.korhonen@broadcom.com" <jouni.korhonen@broadcom.com>, "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
References: <74ee1719-053f-e12f-304c-f3fa9cf286f5@pi.nu> <46fb38a7-8e24-325f-4c0d-9aad197e1dc6@broadcom.com> <76843020-3674-1912-8954-a78323c850de@pi.nu> <DBXPR07MB1288B3116C877858558A1A3AC210@DBXPR07MB128.eurprd07.prod.outlook.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <4e250455-31f1-4ab0-f253-26291ec34e8d@pi.nu>
Date: Thu, 9 Mar 2017 18:10:57 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <DBXPR07MB1288B3116C877858558A1A3AC210@DBXPR07MB128.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/xBm6dAt1Kwihl--U0c-IjH-y0oo>
Subject: Re: [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: Thu, 09 Mar 2017 10:11:08 -0000

Balázs,

inline please.

On 2017-03-09 17:02, Balázs Varga A wrote:
> Hi,
>
> Generally agree, just two additional notes/comments:
> - Mandatory tunnels:
> They are needed anyway for regular P nodes. The DetNet role of intermediate
> "P" nodes is limited to ensure congestion protection.  However P nodes can
> usually recognize only LSP labels and cannot consider the whole label stack for
> flow recognition.  Therefore if DetNet flows would not use tunnels P nodes may
> not distinguish them from regular (non-DetNet) flows and cannot achieve congestion
> protection.

While I agree to this, and it is another nail in the coffin of thw "we 
don't need", you are changing the scenario I draw. The point I tried to
make was that DA-S-PE capable nodes in some scenarios might serve in a P
role in some scenarios - the operators choice.

/Loa


>
> - DA-S-PE needs also PW and FRER specific configuration:
> As clarification to the step when "DetNet-PW-label is allocated by the DA-S-PE for
> the DA-T-PE". You wrote:
>    > the DetNet-PW-label is allocated by the DA-S-PE for the DA-T-PE, and
>    >  as the LSP is set up an instruction is entered into the LFIB whether
>    >  the DA-S-PE should do FRER or not.
> I think we need more than a simple instruction "to do FRER or not". The egress
> replication on the DA-S-PE (towards the next DA-S-PE(s) or the terminating
> DA-T-PE) may be DetNet-flow specific (how many member flows should be created,
> which tunnel should be used by the egress member flows, etc.).
>
> I think we do not have signaling for that DetNet-flow and FRER specific configuration.
> Do we intend to configure them in advance via management?
>
> Cheers
> Bala'zs
>
> -----Original Message-----
> From: Detnet-dp-dt [mailto:detnet-dp-dt-bounces@ietf.org] On Behalf Of Loa Andersson
> Sent: Thursday, March 09, 2017 2:31 AM
> To: jouni.korhonen@broadcom.com; detnet-dp-dt@ietf.org
> Subject: Re: [Detnet-dp-dt] one question on S-DetNet-PEs
>
> Jouni, et.al.,
>
> On 2017-03-09 04:18, Jouni Korhonen wrote:
>> Good guestion.
>>
>> I guess, if you want a specific node to be a S-DetNet-PE for some
>> overlay and P for other, you could "tunnel" through it in P case.
>
> Yes - I think that is necessary. There is a bit more too it though.
>> The
>> currect draft still has text for "overlay labels" (i.e., L-labels) and
>> I think those would work nicely for this case as you say below.
>
> OK - leave that in! There is a terminology issue here, the way we are doing things now, the L-label is the PSN tunnel in the PW architecture.
>
> The caveat is that PSN tunnel needsto be mandatory, unless you want to have a very complicated configuration for when a node is P for one overlay but DA-S-PE for another.
>
> Let me see if I got right
>
> - the PSN-tunnel (PHP'ed at the P node adjacent to the DA-S-PE) takes
>    the DetNet PW to the DA-S-PE.
>
> - the DetNet-PW-label is allocated by the DA-S-PE for the DA-T-PE, and
>    as the LSP is set up an instruction is entered into the LFIB whether
>    the DA-S-PE should do FRER or not.
>
> - DA-T-PE establish a PSN-tunnel through which the DetNet PW is
>    tunneled.
>
> - in the case of using a signaling protocol (since this is PWs I guess
>    it by default is LDP) to establish the PW, no other node than the
>    DA-S-PE, and the egress (DA-T-PE) sees the request for FRER.
>
> - for signaling the L-Label/PSN tunnel, RSVP-TE could be used, which
>    means that the L-Label/PSN-tunnel also serves at BW container.
>
> Did I get that right?
>
> Yes I think it will work.
>
> /Loa
>
>>
>> - Jouni
>>
>> 3/8/2017, 5:03 AM, Loa Andersson kirjoitti:
>>>
>>> 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