Re: [spring] Is srv6 PSP a good idea

Ron Bonica <rbonica@juniper.net> Tue, 17 December 2019 14:54 UTC

Return-Path: <rbonica@juniper.net>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35048120858 for <spring@ietfa.amsl.com>; Tue, 17 Dec 2019 06:54:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net header.b=vxChRBJX; dkim=pass (1024-bit key) header.d=juniper.net header.b=Jhyt5Nrt
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 3CWjO9BKASfF for <spring@ietfa.amsl.com>; Tue, 17 Dec 2019 06:54:34 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 9A45F120856 for <spring@ietf.org>; Tue, 17 Dec 2019 06:54:34 -0800 (PST)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xBHEqkes013962; Tue, 17 Dec 2019 06:53:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=lzN5iN1XZMlkDXPu/QsEzRU9sOPdWS2sa7E55RzJ/Lo=; b=vxChRBJXULyyLh/ss3YW8hV9niLaquX5FPUlK0ecvJ1K+OnXma0IXDyv5xCqt7S+E3+f NVZQ6pJRpTsWRIu5v1iW5FQrqGT5nurJGv+LMp7KsIYp3tWMRiUw16djLlgOtlgqrNlq YkeAU2UCV61lAVrGpGMbWQzcaHLvFk0Ps/umPxgIkr9H3Kq3jrFQj6oNJMgT0pBUtDBf Qkv7oBFfNO9Hjjru8nnKVL0nIkEonx2uXKn4+Xqrsp60wNPb5+WuzqoBTcPs0WfhDtI7 8sCJsH2dJOCCfzFTXlAYSRQcRihSYqnB8Z05jCV5bBBB0SmOmbh8YC00/UqoLHfF+hlc jA==
Received: from nam04-sn1-obe.outbound.protection.outlook.com (mail-sn1nam04lp2053.outbound.protection.outlook.com [104.47.44.53]) by mx0a-00273201.pphosted.com with ESMTP id 2wxa89aht0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 17 Dec 2019 06:53:25 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=S2zAKTZSWzAavDcLkn/j/v17+Mpg0owbNr7OT7W1a5dSFQEkfqWL3bxULX8qkQzKVoz/dSCjccgbVdfzr/LfWDXGcWP0l+EXTivtLZGET+THOyjaTPZgROMQwSgiGGm3AhRvMW6MVyQcGZBDARh71rhjTLDaQMbWFHfC3xwNpsHJD3yXI/cwnbjnPKE84Bgeqs4Fb3J4aJ8g/PjDr/zK217n2SWuLvQCzXuVaSWsIpveMZC1HcjhdTH4jNbOy9JJHCt12Bn+VgrMuIIV2SVDU0dhsyu/Hu8m6h2yUrP7xaPN6w2pZreN2qC4/dJq9qYthRjmINxE7Ph04NsAAyh6vQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lzN5iN1XZMlkDXPu/QsEzRU9sOPdWS2sa7E55RzJ/Lo=; b=P7kcaRoqtxvDe2Y6RD02SypcZil1YbvSByvzTtt1esaRwpob3hK9BvUfrMBSBfklU+xtrYrca5pm5sLeIMSno2cIa1vCLmMBjNqnJOMiaUG3/8dIb8zllg7V8A/17i4nLIXN06LYkDNRoKh3913WYfo6asgD5iwKTqQ/mWrjt1hf/xlXmPFCrUg1zFmDjIhlr4Ou1WioipO9TC7pWg+4QXxctJDtwn/04qzU+KxqOxwxxc+EV8qshqB+36T0qe7zJyTEOqmvl1TKKfV0+da/hxzFlnnYrorvN6Qg2x9/DJN6+JzfjHqCjVSDLavTofQSnaOlxSp1bqwMaFbg1Itnqw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lzN5iN1XZMlkDXPu/QsEzRU9sOPdWS2sa7E55RzJ/Lo=; b=Jhyt5NrtMw96T7HeU6Tbf8tUanjNeg6x1a3ltMk48ZYV2DWTcZEXpYPXXx7KazXP/U8rlHj2rfu+cQCrw/2zhfBSAB+ZgT7XOUQwlw5UP1pvhPmQvrVI+f/WAaTULeTDcpEdIckwy3zYEm1AEBcxFvDxb2Ny1ehyF5tm1JTKixM=
Received: from BN7PR05MB5699.namprd05.prod.outlook.com (20.176.28.88) by BN7PR05MB4339.namprd05.prod.outlook.com (52.133.222.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2538.10; Tue, 17 Dec 2019 14:53:21 +0000
Received: from BN7PR05MB5699.namprd05.prod.outlook.com ([fe80::9461:cfa8:fab9:736c]) by BN7PR05MB5699.namprd05.prod.outlook.com ([fe80::9461:cfa8:fab9:736c%7]) with mapi id 15.20.2559.012; Tue, 17 Dec 2019 14:53:21 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "Voyer, Daniel" <daniel.voyer@bell.ca>, "Xiejingrong (Jingrong)" <xiejingrong@huawei.com>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] Is srv6 PSP a good idea
Thread-Index: AQHVsgKjYcjkTdPeG0y33ySTkvbV/ae+baGw
Content-Class:
Date: Tue, 17 Dec 2019 14:53:21 +0000
Message-ID: <BN7PR05MB56999927EF7F56AA2E0AEA8DAE500@BN7PR05MB5699.namprd05.prod.outlook.com>
References: <EC02B3AB-9E11-4F85-B618-1092B1B8E085@bell.ca>
In-Reply-To: <EC02B3AB-9E11-4F85-B618-1092B1B8E085@bell.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Owner=rbonica@juniper.net; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2019-12-17T14:53:19.1917368Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=Juniper Business Use Only; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Application=Microsoft Azure Information Protection; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=02ec020c-456f-4296-80a0-09f26617fa11; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Extended_MSFT_Method=Automatic
dlp-product: dlpe-windows
dlp-version: 11.3.2.8
dlp-reaction: no-action
x-originating-ip: [108.28.233.91]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: bc19ca08-561f-4594-edf1-08d78300dc85
x-ms-traffictypediagnostic: BN7PR05MB4339:
x-microsoft-antispam-prvs: <BN7PR05MB43398102B6BD27E5901349BCAE500@BN7PR05MB4339.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 02543CD7CD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(136003)(39860400002)(366004)(346002)(376002)(189003)(199004)(13464003)(8936002)(66476007)(64756008)(53546011)(52536014)(66446008)(71200400001)(6506007)(66946007)(478600001)(33656002)(86362001)(186003)(316002)(966005)(4001150100001)(55016002)(76116006)(7696005)(5660300002)(2906002)(9686003)(66574012)(8676002)(81166006)(110136005)(81156014)(26005)(66556008); DIR:OUT; SFP:1102; SCL:1; SRVR:BN7PR05MB4339; H:BN7PR05MB5699.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 4esQSnR4WBZut+uJGKU34DxUX7bn2WlJfgkcqp1YW83UmL3sVEUojDaF+yMht82E/RKZaKi5SnCgwHZ5FMKu1+evpGbCzSPHQlTRsw0gsAnHWJQKmH06lg2J0VUj6l5f2IwPbYSSgNxHKOEkZBc5lUOo+vx4KNzOiBLs/jGlWcgTe7dBaVJ1V1W6gwgFYHphPGhBcKRjUPi17ySGBsz5x59SBRehs6tQekTr6koTxhZpIOnTtpAtjZdTzpbXF4wdrV/2NeYxHpezNeap7VvLScOqFS2HZsBYSJFDKMDpLnwzR14Yie7CpGPf9v5X31a2qlfPHGSmt1LsdzgfAalFwFeLXLpX9orgxrE9R+W84wVGi1Dtb9l/gBrI9CzlzJqI1vOHwUfJE7Ue5zYrWm2xBtJFAOU0OsWMpGwUhpU1foPVgF5PebXzrRnQNt5f/EdqXvWSf/SmwKY8NJoprkzfiyscqG5KbYrAWl/REH1epm3U9OunDixhq5WNxJEMvsLf6KT2xRHNbw4f44SOhERJLdsCYGCvxk/Zj+AsIsfLh0w=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: bc19ca08-561f-4594-edf1-08d78300dc85
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Dec 2019 14:53:21.8068 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Vq25s/sgX2K7km6rf+6Rwra67nDK2t7w3tYCl1LaG50wON4CE4IjqQeNPikoTuyRTMKotcf1Edm3uQYkccT4xg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR05MB4339
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-17_02:2019-12-17,2019-12-17 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 lowpriorityscore=0 clxscore=1011 spamscore=0 bulkscore=0 priorityscore=1501 impostorscore=0 malwarescore=0 adultscore=0 suspectscore=0 mlxlogscore=999 mlxscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912170125
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/MPkHjIL-XckMtlPGEXSaJpaR4k0>
Subject: Re: [spring] Is srv6 PSP a good idea
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Dec 2019 14:54:38 -0000

Daniel,

This use-case is interesting and may justify PHP. Allow me to ask a few questions about it:

1) When the payload arrives at the final segment endpoint, it is encapsulated in IPv6. There are no extension headers between the IPv6 header and the payload, as the SRH has been removed. Do I have that much right?

2) Does the IPv6 Destination Address represent an interface on the final segment endpoint? Or does it represent an instruction instantiated on the final segment endpoint? If the later, what kind of instructions can it represent?

3) Is the final segment always an adjacency segment? Or can it be an node segment?

                                                                                                                                  Happy holidays,
                                                                                                                                        Ron



Juniper Business Use Only

-----Original Message-----
From: spring <spring-bounces@ietf.org> On Behalf Of Voyer, Daniel
Sent: Friday, December 13, 2019 5:14 PM
To: Xiejingrong (Jingrong) <xiejingrong@huawei.com>; spring@ietf.org
Subject: Re: [spring] Is srv6 PSP a good idea

I agree 100% with Jingrong,

PSP allows us to bring SRv6 to legacy PE devices that are not capable of processing the SRH in the dataplane, but are capable of supporting SRv6 in the control plane.
 
See this example:
I am streaming traffic from a server to a customer; The ingress PE (near the server) encapsulates the packet and adds an SRH with a low-latency list of segments; The penultimate node in the SRH executes PSP; The egress PE (near the customer) decapsulates the IPv6 header and forwards the inner packet to the customer.
 
We can include SLA unidirectionally from the server to the customer even though that the egress PE has a legacy ASIC. Legacy equipment are a reality and are not easy to replace, hence interoperability with brownfield is key for any innovative approach.

dan 

On 2019-12-10, 11:15 PM, "spring on behalf of Xiejingrong (Jingrong)" <spring-bounces@ietf.org on behalf of xiejingrong@huawei.com> wrote:

    I think it's a good idea.
    Nothing new, but benefits that people have already said seems notable to me.
    
    (1) reduce the load of final destination. This benefit can be notable for the following sub reasons.
    (1.1) final destination tends to have heavy load. It need to handle all the EHs and do the delivery/demultiplex the packet to the right overlay service.
    (1.2) example 1, the final destination may need to handle the DOH after the RH.
    (1.3) example 2, the final destination may need to do the assembly of fragmented packets.
    (1.4) example 3, the final destination may need to do AH/ESP after the Fragmentation Header.
    (1.5) example 4, the final destination may need to deliver the packet to the right overlay service.
    
    (2) support the incremental deployment when final destination(s) do not process/recognize SRH. This benefit can be notable for the following sub reasons.
    (2.1) A core router may (fan-out) connected with a big number of low-end routers that do not support SRH but support tunnel-end/service-demultiplex function of SRv6.
    
    Thanks
    Jingrong
    
    -----Original Message-----
    From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Joel M. Halpern
    Sent: Wednesday, December 11, 2019 10:55 AM
    To: spring@ietf.org
    Subject: [spring] Is srv6 PSP a good idea
    
    For purposes of this thread, even if you think PSP violates RFC 8200, let us assume that it is legal.
    
    As I understand it, the PSP situation is:
    o the packet arrives at the place (let's not argue about whether SIDs are locators) identified by the SID in the destination address field o that SID is the next to last SID in the SID list o that sid is marked as / known to be PSP o at the intended place in the processing pseudocode, the last (first) entry in the SRH is copied into the destination IPv6 address field of the packet
    -> The SRH being used is then removed from the packet.
    
    In order to evaluate whether this is a good idea, we have to have some idea of the benefit.  It may be that I am missing some of the benefit, and I would appreciate clarification.
    As far as I can tell, the benefit of this removal is that in exchange for this node doing the work of removing the SRH, the final node in the SRH does not have to process the SRH at all, as it has been removed.
    
    I have trouble seeing how that work tradeoff can be beneficial. 
    Removing bytes from the middle of a packet is a complex operation. 
    Doing so in Silicon (we expect this to be done in the fast path of significant forwarders as I understand it) requires very special provision.  Even in software, removing bytes from the middle of a packet requires somewhere between some and a lot of extra work.  It is distinctly NOT free.
    
    In contrast, we have assumed that the work of processing SRH itself is tractable, since otherwise all of SRv6 would be problematic.  So why is this necessary.
    
    Yours,
    Joel
    
    PS: Note that both the MPLS case and the encapsulation case are very different in that the material being removed is at the front of the IP packet.  Pop or prepend are MUCH easier than middle-removal (or middle-insertion).
    
    _______________________________________________
    spring mailing list
    spring@ietf.org
    https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/spring__;!!NEt6yMaO-gk!XgiVQSDxI6sGR3TIAfdOZqcIaUfnd08IJjdwQTSxfNVI3DFpiBWIb4eGReqszq9W$ 
    
    _______________________________________________
    spring mailing list
    spring@ietf.org
    https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/spring__;!!NEt6yMaO-gk!XgiVQSDxI6sGR3TIAfdOZqcIaUfnd08IJjdwQTSxfNVI3DFpiBWIb4eGReqszq9W$ 
    ------------------------------------------------------------------------------
    External Email: Please use caution when opening links and attachments / Courriel externe: Soyez prudent avec les liens et documents joints
    
    

_______________________________________________
spring mailing list
spring@ietf.org
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/spring__;!!NEt6yMaO-gk!XgiVQSDxI6sGR3TIAfdOZqcIaUfnd08IJjdwQTSxfNVI3DFpiBWIb4eGReqszq9W$