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

Balázs Varga A <balazs.a.varga@ericsson.com> Thu, 09 March 2017 13:38 UTC

Return-Path: <balazs.a.varga@ericsson.com>
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 E47EF129604 for <detnet-dp-dt@ietfa.amsl.com>; Thu, 9 Mar 2017 05:38:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
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 BWbbitSfIrv7 for <detnet-dp-dt@ietfa.amsl.com>; Thu, 9 Mar 2017 05:38:49 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 819C11295FE for <detnet-dp-dt@ietf.org>; Thu, 9 Mar 2017 05:38:48 -0800 (PST)
X-AuditID: c1b4fb30-46ffb70000007a5b-a9-58c15ae58c0e
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by (Symantec Mail Security) with SMTP id 40.E9.31323.5EA51C85; Thu, 9 Mar 2017 14:38:46 +0100 (CET)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.21) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 9 Mar 2017 14:38:44 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=qyevFQopa5WQNJ1yeoVPLAlxfV/dGMVeTcJtgiktSBg=; b=HS3SHC/VArpVbfvUKLOjWDRS1uDJlvdnJKYryNLIrsHoxkgM9anFqcbaIIQBEm/1aKsr/wNZN0ZoiFUWHQs723cNOi/eeQHv+hX5lCEDLsxECr/BRQkXWZBr4z+c/ChJW9yfKVg9huv+7/Qw5A1rr248p5sn2onmv+BGhhskQro=
Received: from DBXPR07MB128.eurprd07.prod.outlook.com (10.242.138.156) by DBXPR07MB128.eurprd07.prod.outlook.com (10.242.138.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.2; Thu, 9 Mar 2017 13:38:43 +0000
Received: from DBXPR07MB128.eurprd07.prod.outlook.com ([169.254.3.89]) by DBXPR07MB128.eurprd07.prod.outlook.com ([169.254.3.89]) with mapi id 15.01.0947.022; Thu, 9 Mar 2017 13:38:43 +0000
From: =?iso-8859-1?Q?Bal=E1zs_Varga_A?= <balazs.a.varga@ericsson.com>
To: Loa Andersson <loa@pi.nu>, "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
Thread-Topic: [Detnet-dp-dt] one question on S-DetNet-PEs
Thread-Index: AQHSmAx8WmrmUkK4e0qxY24qEx0v1KGLYiQAgABXYYCAAHO1EIAAHZCAgAAFFdCAABYIAIAAGkXQ
Date: Thu, 9 Mar 2017 13:38:43 +0000
Message-ID: <DBXPR07MB1283ED994AA12C9A34E1C36AC210@DBXPR07MB128.eurprd07.prod.outlook.com>
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> <4e250455-31f1-4ab0-f253-26291ec34e8d@pi.nu> <DBXPR07MB128F8D6D5EE3F7C6FB22A75AC210@DBXPR07MB128.eurprd07.prod.outlook.com> <0708a722-0bee-1670-921f-1d349806b33b@pi.nu>
In-Reply-To: <0708a722-0bee-1670-921f-1d349806b33b@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: pi.nu; dkim=none (message not signed) header.d=none;pi.nu; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [91.82.100.59]
x-microsoft-exchange-diagnostics: 1; DBXPR07MB128; 7:FY9pL2i59lPOKgvhxJbXR9Zsz2ebIMo9FPyzs2eFjyHis6gHBZ7KnFDXHLITEUk+wAXNmObTEsWaMz4R2GHRKEMpZm0y9kWW954sbVsqSHmhQfmlxIpL+Qt95MvbEIFHqOiYxMsr4hzo84Dwjwcmspv0+7Toy7URkSySuNOUbxwSY50i85CfoSDbmsW6yITmNEa6k+R1wvwlHRHLaHbVQnj3/iMrJoJcIRZByuDis2y9Qz4bIfbs/RPrZWrXiaSmBW6eesIU+bpY/MXpyz9Jz2cg4VgGuH3W/+0KKfJR3i2Qrmm2ixFrNQ981ZC/OG3lRXu8UhUPfsvDjOPslaiJcQ==
x-ms-office365-filtering-correlation-id: bc988432-b701-4826-3bbf-08d466f19aed
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:DBXPR07MB128;
x-microsoft-antispam-prvs: <DBXPR07MB1281F69CCD2202C2EB07D5AAC210@DBXPR07MB128.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(50582790962513)(21748063052155)(17755550239193);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123564025)(20161123558025)(20161123555025)(20161123562025)(20161123560025)(6072148); SRVR:DBXPR07MB128; BCL:0; PCL:0; RULEID:; SRVR:DBXPR07MB128;
x-forefront-prvs: 0241D5F98C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39450400003)(24454002)(13464003)(377424004)(252514010)(37854004)(377454003)(38730400002)(189998001)(236005)(229853002)(6506006)(6246003)(106116001)(2501003)(6436002)(9686003)(102836003)(3846002)(6116002)(606005)(53546006)(54896002)(230783001)(54356999)(50986999)(122556002)(76176999)(53936002)(33656002)(6306002)(790700001)(25786008)(66066001)(7736002)(2906002)(8676002)(3280700002)(5660300001)(2900100001)(93886004)(3660700001)(74316002)(81166006)(2950100002)(8936002)(7906003)(7696004)(99286003)(86362001)(55016002)(9326002); DIR:OUT; SFP:1101; SCL:1; SRVR:DBXPR07MB128; H:DBXPR07MB128.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DBXPR07MB1283ED994AA12C9A34E1C36AC210DBXPR07MB128eurprd_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Mar 2017 13:38:43.6756 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBXPR07MB128
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Se0iTURjGOd9l+5RGx3l7XQaxhKLwkooYSJRkSFREUNmSdOWXl7y1maVd 0C5mDsnASKeiwyE008JmU2rpPijzui77o6ZhmpVLSlDRMrXcjoH//d7nOc/Dew6Ho6VNrIxL zczhVZnKdLnInamMM3kHflVY4kKskxGRhrImUeRSTTW9k4rV639Tsdp7RaKDlMI9KolPT83l VcE7Et1T7LqnbHbPLLpgm7JTBaj3HSpBbhzgcHBMjYpLkDsnxc0IKhr7aDJ0IVhoHnANDC6l wVr6ZMUpp6DreuvKYEHQ11dIO8tEOAami0dETvbCB8D8t5ctQRzniSPh9utQIm+HxzM22il7 YQXMfvF3ygwOgIX2WsrJkmW53GZmSH0NDY6Ccle923K2/+cPsZMR9oG5ngeuAI19wT5GwoAx 6J9ZacLe4Pi8xDqLEL6B4Lv9IUOMDdBSN+m6NGANDSOLL0XE2A+Lhmkx4X0wYbWu6Knw6UM7 SzgNNNd0DAlXUDClMa0c8gdjox0Rw8hCjzDi2sMTy+Cj7RYi7A/jQ2aW7J0FOt2MqAxt0q66 hnaVpXW9hwd0V44xRA+C93fLRYS3QoNugiYcCBVLArNar0NiA/JW8+qTGcmhoUG8KvWUWp2V GZTJ57Sg5U9kMf4JaUOOb7sEhDkkXyPJ9u+Mk7LKXHVehoCAo+VekkuHLHFSSZIyL59XZSWo zqXzagGt4xi5ryTi/vBRKU5W5vBneD6bV/13Kc5NVoDShju7hcP148V3Ynp2m98sKfIHJP2x PgmL3TfFUWEltTSnP5toOF49drE+7LRxfVHDVdNlTZTmeeTaK+etg6OPhuYcM7MdVeGVfvO/ BFtWW8eJ6r1wzKMo3vE2uPCISfvKMe+9OdovuurFqKw1DDYOCgFKKl4A1qz32tOuqJcz6hTl ti20Sq38B+Vh74dAAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/ViH5Sov599FXULGTieJePj9adjs>
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 13:38:52 -0000

Hi Loa,

Exactly. A,B and C are PE for their directly connected CEs, but P for pass-through traffic.

Let's see how "dense" DetNet flows will be populated in future networks. In networks

where only a small portion of the traffic require DetNet treatment we may see some

P nodes.

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 12:48 PM
To: detnet-dp-dt@ietf.org
Subject: Re: [Detnet-dp-dt] one question on S-DetNet-PEs



Bala'zs,



Oh, sure understood - it is just that when we invented the P and PE terminology it was not for nodes, but for functions. A PE were the group of functions needed in a node that interfaced customers. A P was the functions that were need by a node that was passing traffic inside a provider network,



The caveat was that PE an P functions, at least in the network that did run at that time, were often found on the same node, consider this.





           +-----+                     +-----+

+--+      |     |                     |     |     +--+

|CE|------|  A  |---------------------|  B  |-----|CE|

+--+      |     |                     |     |     +--+

           +-----+                     +-----+

              |                           |

              |         +------+          |

              |         |      |          |

              +---------|  C   |----------+

                        |      |

                        +------+

                            |

                            |

                          +---+

                          |CE |

                          +---+



If one view A, B and C as node are they P or PE nodes?



/Loa



On 2017-03-09 18:31, Balázs Varga A wrote:

> Hi,

>

> Correct. My comment was an additional argument for the tunnels.

> There are two scenarios mandating tunnels:

> 1, regular P nodes

> 2, DA-S-PE nodes acting as P node for some PWs

>

> Cheers

> Bala'zs

>

> -----Original Message-----

> From: Loa Andersson [mailto:loa@pi.nu]

> Sent: Thursday, March 09, 2017 11:11 AM

> To: Balázs Varga A <balazs.a.varga@ericsson.com<mailto:balazs.a.varga@ericsson.com>>;

> jouni.korhonen@broadcom.com<mailto:jouni.korhonen@broadcom.com>; detnet-dp-dt@ietf.org<mailto:detnet-dp-dt@ietf.org>

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

>

> 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<mailto:jouni.korhonen@broadcom.com>; detnet-dp-dt@ietf.org<mailto: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<mailto:loa@mail01.huawei.com>

Senior MPLS Expert                          loa@pi.nu<mailto:loa@pi.nu>

Huawei Technologies (consultant)     phone: +46 739 81 21 64



_______________________________________________

Detnet-dp-dt mailing list

Detnet-dp-dt@ietf.org<mailto:Detnet-dp-dt@ietf.org>

https://www.ietf.org/mailman/listinfo/detnet-dp-dt