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

Lou Berger <lberger@labn.net> Thu, 09 March 2017 14:00 UTC

Return-Path: <lberger@labn.net>
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 484BA129630 for <detnet-dp-dt@ietfa.amsl.com>; Thu, 9 Mar 2017 06:00:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 ZQTfkkiGIj-E for <detnet-dp-dt@ietfa.amsl.com>; Thu, 9 Mar 2017 06:00:47 -0800 (PST)
Received: from gproxy7-pub.mail.unifiedlayer.com (gproxy7-pub.mail.unifiedlayer.com [70.40.196.235]) by ietfa.amsl.com (Postfix) with SMTP id C7408129606 for <detnet-dp-dt@ietf.org>; Thu, 9 Mar 2017 06:00:47 -0800 (PST)
Received: (qmail 23557 invoked by uid 0); 9 Mar 2017 14:00:43 -0000
Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy7.mail.unifiedlayer.com with SMTP; 9 Mar 2017 14:00:43 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with id tq0S1u00Q2SSUrH01q0VkH; Thu, 09 Mar 2017 07:00:29 -0700
X-Authority-Analysis: v=2.1 cv=R4+QR7hX 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=N659UExz7-8A:10 a=xqWC_Br6kY4A:10 a=6Iz7jQTuP9IA:10 a=48vgC7mUAAAA:8 a=Q-fNiiVtAAAA:8 a=WSNK2VrypjiWNuwTxLYA:9 a=ttDtYZe1KtCluIOX:21 a=eL0kRsI00UC3n7UI:21 a=pILNOxqGKmIA:10 a=w1C3t2QeGrPiZgrLijVG:22 a=Fp8MccfUoT0GBdDC_Lng: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:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=g1raSfQ6oSbOmJufMMc6aqCMys8VEONzZVd6b6jkiRc=; b=xAkmOF4RKGEmxlCYav33TE21/c ake453LACtmrxvb1XmmQoAeMh79NsODHqFr7dKZ6m9EkdKmz36XNS8D3GK8tdZ0rZQ+1CeKJkO+lM eZx2kiouBK+ZjcXedCN9O3E0Y;
Received: from pool-100-15-85-191.washdc.fios.verizon.net ([100.15.85.191]:35212 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1clycD-0008Fp-Rk; Thu, 09 Mar 2017 07:00:25 -0700
To: =?UTF-8?Q?Bal=c3=a1zs_Varga_A?= <balazs.a.varga@ericsson.com>, Loa Andersson <loa@pi.nu>, "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: Lou Berger <lberger@labn.net>
Message-ID: <1e1453ea-a55f-1a4a-908b-992b9073717b@labn.net>
Date: Thu, 9 Mar 2017 09:00:24 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <DBXPR07MB1288B3116C877858558A1A3AC210@DBXPR07MB128.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252
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: 1clycD-0008Fp-Rk
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]:35212
X-Source-Auth: lberger@labn.net
X-Email-Count: 4
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/73rLHhMLsd6iHjbZoBVOcGy54wo>
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 14:00:54 -0000

Balázs,
A couple of comments below.

On 3/9/2017 4:02 AM, 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. 
The also can provide TE style resource control (allocation, enforcement,
even shaping and policing).  It may even provide LSP level
protection/restorations functions.

>  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.
This is up to the "client" layer, i.e., DetNet aware S&T PEs.  Note that
a P router is an LSR and  only operates on labels (either classic MPLS
or SR).  S-PEs and T-PEs are always on PEs, by definition, even when the
function doesn't reside connected to CEs.

Lou


>
> - 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