IETF Logo Mail Archive

Re: [spring] Segment Routing in Two Dimensional IP Routing

Bo Wang <wangbo2019@tsinghua.edu.cn> Fri, 15 July 2022 09:25 UTC

Return-Path: <wangbo2019@tsinghua.edu.cn>
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 20A90C188720 for <spring@ietfa.amsl.com>; Fri, 15 Jul 2022 02:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.993
X-Spam-Level:
X-Spam-Status: No, score=-1.993 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tsinghua.edu.cn
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVfaIB8k8DUG for <spring@ietfa.amsl.com>; Fri, 15 Jul 2022 02:25:03 -0700 (PDT)
Received: from zg8tmja5ljk3lje4ms43mwaa.icoremail.net (zg8tmja5ljk3lje4ms43mwaa.icoremail.net [209.97.181.73]) by ietfa.amsl.com (Postfix) with SMTP id A0D0CC14EB1E for <spring@ietf.org>; Fri, 15 Jul 2022 02:24:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tsinghua.edu.cn; s=dkim; h=Received:Date:From:To:Cc:Message-ID: In-Reply-To:References:Subject:MIME-Version:Content-Type: Content-Transfer-Encoding; bh=Z35t/81iGOZN4nOI8XcEAs6cwOMIroPYiL iQO9EDhGQ=; b=EPqswQ7Ct2APAYCSFnXIwjwcBM5l1E4cmkVkKPhJkggSeBJrSS i0+OsoFwcpbTJXXYJzP5b0DgUQTUgAm8Bt5WZDNCYSfeppnmnYzDfuZDGE/ohDwR KtuOM5G08mva611YPi8bd0jLMTzB3TtGEu51BWsm4v6OCD/xBUoGGSVsQ=
Received: from BoodeMacBook-Pro-2.local (unknown [166.111.132.233]) by web5 (Coremail) with SMTP id zAQGZQCnQzBiMtFiYkdxAw--.4478S2; Fri, 15 Jul 2022 17:24:50 +0800 (CST)
Date: Fri, 15 Jul 2022 17:24:51 +0800
From: Bo Wang <wangbo2019@tsinghua.edu.cn>
To: "li_zhenqiang@hotmail.com" <li_zhenqiang@hotmail.com>
Cc: "spring@ietf.org" <spring@ietf.org>, Mingwei Xu <xmw@cernet.edu.cn>
Message-ID: <6EEE8EB8-C292-4381-A8CF-2788E966503A@tsinghua.edu.cn>
In-Reply-To: <MEYP282MB2942F188562D4B9C66096E03FC8B9@MEYP282MB2942.AUSP282.PROD.OUTLOOK.COM>
References: <AAE72459-2D42-4450-9927-9DFA51B83FF8@tsinghua.edu.cn>
X-Mailer: MailMasterMac/4.15.7.1280 (12.3.1)
X-CUSTOM-MAIL-MASTER-SENT-ID: 17ACC0DF-4B45-4520-A264-3E2741906228
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64
X-CM-TRANSID: zAQGZQCnQzBiMtFiYkdxAw--.4478S2
X-Coremail-Antispam: 1UD129KBjvJXoWxGFWkWrWUuFWfXF1UAF4rGrg_yoW5WF48pF WrK3y5JFWqkFnrGF40qw4SyF1SgFWkta1xGr18CwsFvF45KF18KF1Ikw15Z3WrCr1Fy34F qr43u3yrWa1YvFJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUHG14x267AKxVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0 rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK02 1l84ACjcxK6xIIjxv20xvE14v26F1j6w1UM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26r4U JVWxJr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_Gc CE3s1lnxkEFVAIw20F6cxK64vIFxWle2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG6c80 4VAFz4xC04v7Mc02F40E42I26xC2a48xMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87 Iv67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lF7I21c0E jII2zVCS5cI20VAGYxC7M4xvF2IEb7IF0Fy264kE64k0F24lFcxC0VAYjxAxZF0Ex2Iqxw ACY4xI6c02F40Ez4kGawAKzVCjr7xvwVAFz4v204v26I0v724lc2xSY4AK67AK6r4fMxAI w28IcxkI7VAKI48JMxC20s026xCaFVCjc4AY6r1j6r4UMI8I3I0E5I8CrVAFwI0_JrI_Jr Wlx2IqxVCjr7xvwVAFwI0_Jr0_Jr4lx4CE17CEb7AF67AKxVWUXVWUAwCIc40Y0x0EwIxG rwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AKxVWUJVW8Jw CI42IY6xAIw20EY4v20xvaj40_Jr0_JF4lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcVC2 z280aVCY1x0267AKxVW8JVW8Jr1l6VACY4xI67k04243AbIYCTnIWIevJa73UjIFyTuYvj fUUDGOUUUUU
X-CM-SenderInfo: pzdqwuzrsqimo6wvx0pjkxthxhgxhubq/
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/lGOr82XyS5dRKZK0oBjuvEOFxus>
Subject: Re: [spring] Segment Routing in Two Dimensional IP Routing
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 15 Jul 2022 09:25:08 -0000

Dear Zhenqiang,

Thanks for your professional questions. TwoD-IP routing (i.e., src-dst routing) is different from FlowSpec in the following two aspects:

1. FlowSpec is not a policy-routing protocol in essence, while TwoD-IP routing is a policy-routing protocol.

Although FlowSpec and TwoD-IP routing both use src and dst address to classify traffic, their actions on the target traffic are very different.

FlowSpec' primary goal is to mitigate the effects of DoS and DDoS attacks, and its actions mainly include dropping, rate limiting, redirect-to-VRF, reseting DSCP. Therefore, essentially, FlowSpec is not a policy-routing protocol. Instead of specifying the preference of the forwarding path for any routing node, it can only redirect the filtered traffic to one or several specific paths at most.

In contrast, TwoD-IP routing is a policy-routing protocol. It can specify the preference of the target traffic for any router node, including reachability and cost. The forwarding path is dynamically calculated according to the preference, optimization object, and constraint. TwoD-IP routing protocol has better flexibility than FlowSpec.

2. FlowSpec suffers from bad scalability if it is used to make policy-routing, where TwoD-IP routing protocol has good scalability.

FlowSpec faces the challenges of dimensional explosion if it is used to make policy-routing.

TwoD-IP routing protocol has good scalability. It addresses the explosion problem by proposing a novel forwarding table structure with a separation of TCAM and SRAM, where TCAM provides fast lookup speeds and SRMA provides large memory space.


Best Regards,
Bo Wang
Hello Bo Wang，

A SDN controller can use BGP FlowSpec to indicate the headend node to steer corresponding packets to proper SR policy. Besides source and destination IP address, other information such as source port, destination port, protocol etc, can also be specified in the BGP FlowSpec rules. 

Best Regards,
Zhenqiang Li

 
From: 王博
Date: 2022-07-14 10:39
Subject: [spring] Segment Routing in Two Dimensional IP Routing
Dear SPRING WG,

We have submitted a draft “Segment Routing in Two Dimensional IP Routing” to SPRING WG. We are looking for your feedback and comments.

URL: https://datatracker.ietf.org/doc/draft-xu-spring-segment-twod-ip-routing/

This draft describes an extension of SR to support TwoD-IP routing (i.e., src-dst routing) which makes forwarding decisions based on both source and destination IP addresses.

We have implemented a src-dst routing prototype based on segment routing and deployed it over CERNET (China Education and Research Network).

Bo Wang


v2.23.0 | Report a Bug | By Email