[Stackevo-discuss] When provider networks don't t trust the stack set by the end points ....

Linda Dunbar <linda.dunbar@huawei.com> Mon, 07 December 2015 22:30 UTC

Return-Path: <linda.dunbar@huawei.com>
X-Original-To: stackevo-discuss@ietfa.amsl.com
Delivered-To: stackevo-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 732521B29FF for <stackevo-discuss@ietfa.amsl.com>; Mon, 7 Dec 2015 14:30:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id KnOHUECVNwSD for <stackevo-discuss@ietfa.amsl.com>; Mon, 7 Dec 2015 14:30:46 -0800 (PST)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76FC71B29F5 for <stackevo-discuss@iab.org>; Mon, 7 Dec 2015 14:30:46 -0800 (PST)
Received: from (EHLO dfweml706-chm.china.huawei.com) ([]) by dfwrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CTQ77120; Mon, 07 Dec 2015 16:30:44 -0600 (CST)
Received: from DFWEML701-CHM.china.huawei.com ([]) by dfweml706-chm ([]) with mapi id 14.03.0235.001; Mon, 7 Dec 2015 14:30:40 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "stackevo-discuss@iab.org" <stackevo-discuss@iab.org>
Thread-Topic: When provider networks don't t trust the stack set by the end points ....
Thread-Index: AdExPua6p20KTYEoSD+piZoHokKNhA==
Date: Mon, 7 Dec 2015 22:30:40 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F657DADD4A@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F657DADD4Adfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0201.56660895.006E, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c8c975176b8e039eb145729279cbe8c5
Archived-At: <http://mailarchive.ietf.org/arch/msg/stackevo-discuss/NYtsT77k7X39eDgZZElNjrixuKQ>
Subject: [Stackevo-discuss] When provider networks don't t trust the stack set by the end points ....
X-BeenThere: stackevo-discuss@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IP Stack Evolution Discussion List <stackevo-discuss.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/stackevo-discuss>, <mailto:stackevo-discuss-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stackevo-discuss/>
List-Post: <mailto:stackevo-discuss@iab.org>
List-Help: <mailto:stackevo-discuss-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/stackevo-discuss>, <mailto:stackevo-discuss-request@iab.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2015 22:30:49 -0000

I find the use cases for SPUD are very real and definitely need a good approach to make it happen.

However, a lot of discussions have been centered around the SPUD layer being encoded by End Points, and expect the network to apply certain rules for those traffic. Having an In-band standard signaling among end points and network has its advantages: allowing network to treat packets without getting into the encrypted payload, and not requiring any  extra components across the networks between the end points.

However,  Virtually all traffic today go through provider networks (most likely multiple). Provider network usually don't (can't) trust the signaling or requests from end points because any end points can set their own traffic as "requiring the least latency" or "passing through the network".  Provider network set traffic based on the SLA clients pay.  For example all the DiffServ set by the endpoints are ignored by the provider network, instead Provider Network set its own DiffServ based on the SLA from the customers.

The Network Service Header (NSH) introduced by SFC (http://datatracker.ietf.org/doc/draft-ietf-sfc-nsh/ ) is effectively another layer of stack added to the packets (added by the ingress node).

My question is:
Should SPUD allow multiple types of layer added to data packets? Or only focusing on the layer end points can add?

My two cents.

Linda Dunbar