Discuss on draft-lin-sbfd-path-consistency-over-srv6-00

linchangwang <linchangwang.04414@h3c.com> Tue, 22 March 2022 02:31 UTC

Return-Path: <linchangwang.04414@h3c.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 354353A1CC9; Mon, 21 Mar 2022 19:31:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 eQg7zap6I0NS; Mon, 21 Mar 2022 19:31:18 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (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 8A14F3A1CC8; Mon, 21 Mar 2022 19:31:16 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 22M2SikU061533; Tue, 22 Mar 2022 10:28:44 +0800 (GMT-8) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG2EX09-IDC.srv.huawei-3com.com (unknown [10.8.0.72]) by mail.maildlp.com (Postfix) with ESMTP id 61D56246D472; Tue, 22 Mar 2022 10:29:55 +0800 (CST)
Received: from DAG2EX07-IDC.srv.huawei-3com.com (10.8.0.70) by DAG2EX09-IDC.srv.huawei-3com.com (10.8.0.72) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.17; Tue, 22 Mar 2022 10:28:44 +0800
Received: from DAG2EX07-IDC.srv.huawei-3com.com ([fe80::2dff:54b3:cdc:daad]) by DAG2EX07-IDC.srv.huawei-3com.com ([fe80::2dff:54b3:cdc:daad%9]) with mapi id 15.01.2375.017; Tue, 22 Mar 2022 10:28:44 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "jhaas@pfrc.org" <jhaas@pfrc.org>, "reshad@yahoo.com" <reshad@yahoo.com>
CC: Lihao <lihao@h3c.com>, "jiangwenying@chinamobile.com" <jiangwenying@chinamobile.com>, "chengweiqiang (chengweiqiang@chinamobile.com)" <chengweiqiang@chinamobile.com>, "spring@ietf.org" <spring@ietf.org>
Subject: Discuss on draft-lin-sbfd-path-consistency-over-srv6-00
Thread-Topic: Discuss on draft-lin-sbfd-path-consistency-over-srv6-00
Thread-Index: Adg9lItZSTV7l6NCQVmogVCNMcV8Ig==
Date: Tue, 22 Mar 2022 02:28:44 +0000
Message-ID: <84d962b16db840d7a11caeb64dbc7b9c@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.76.67]
x-sender-location: DAG2
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-DNSRBL:
X-MAIL: h3cspam02-ex.h3c.com 22M2SikU061533
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/Mo2kNzHhcdzKr9deeEEh6urNncs>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Mar 2022 02:31:24 -0000

Hi WG ,Chairs:

https://datatracker.ietf.org/doc/html/draft-lin-sbfd-path-consistency-over-srv6-00

This document describes a method to keep the forward path and
reverse path of S-BFD consistent when detecting SRv6 Policy.

There is no meeting for bfd in IETF-113,  we will present this draft in spring WG:
  March 25, 2022  12:30-14:30 Friday Afternoon session I (UTC+1)
  o S-BFD Path Consistency over SRv6[ 5 minutes ]

S-BFD could be used to monitor SRv6 Policy,  a session associated with a segment list.
Path inconsistency may cause false positive issue.
To the issue, The consistency of forward and reverse path of the same session should be guaranteed.
This draft describes how to realize the bidirectional path consistency of packet when monitoring SRv6 policy by S-BFD.

How to correlate bidirectional path?
1.  Correlating bidirectional path using Path Segment
    2.  Path Segment is defined to identify an SR path in [draft-ietf-spring-srv6-path-segment]
    3.  [draft-ietf-idr-sr-policy-path-segment] extends BGP SR Policy
    4.  Using path segment and reverse path segment to establish a mapping table
       Using the mapping table to get segment list by reverse Path segment

S-BFD Initiator procedure:
    1. Encapsulating the segment list associated with SBFD-session session to SRH
    2. Encapsulating the path segment of segment list in SRH, and set SRH.P-Flag

S-BFD reflector procedure:
    1. If SRH.P-flag is set, extracts the path segment (i.e. SID-Path-A1)of the forward path from SRH
    2.Get segment list of reverse path by the path segment as a reverse path segment from mapping table
    3. Encapsulating response packet with the reverse segment list

Any comments and suggestions are greatly welcome.

Best regards,
Changwang Lin



发件人: linchangwang (RD)
发送时间: 2022年3月2日 23:17
收件人: jiangwenying@chinamobile.com; chengweiqiang (chengweiqiang@chinamobile.com); lihao (02566, RD); 'rtg-bfd@ietf.org'
主题: Re: I-D Action: draft-lin-sbfd-path-consistency-over-srv6-00.txt

Hi WG,

We have just posted a new draft about sbfd path consistency over SRv6 in BFDWG.
https://datatracker.ietf.org/doc/html/draft-lin-sbfd-path-consistency-over-srv6-00

This document describes a method to keep the forward path and
reverse path of S-BFD consistent when detecting SRv6 Policy.

Any comments and suggestions are greatly welcome.

Best regards,
Changwang Lin





发件人: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] 代表 internet-drafts@ietf.org
发送时间: 2022年3月2日 19:33
收件人: i-d-announce@ietf.org
主题: I-D Action: draft-lin-sbfd-path-consistency-over-srv6-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : S-BFD Path Consistency over SRv6
        Authors         : Changwang Lin
                          Weiqiang Cheng
                          Wenying Jiang
Filename        : draft-lin-sbfd-path-consistency-over-srv6-00.txt
Pages           : 12
Date            : 2022-03-02

Abstract:
   Bidirectional Forwarding Detection (BFD) can be used to monitor
   paths between nodes. Seamless BFD (S-BFD) provides a simplified
   mechanism which is suitable for monitoring of paths that are setup
   dynamically and on a large scale network. In SRv6, when a headend
   use S-BFD to monitor the segment list/CPath of SRv6 Policy, the
   forward path of S-BFD packet is indicated by segment list, the
   reverse path of BFD packet is via the shortest path from the
   reflector back to the initiator (headend) as determined by routing.
   The forward path and reverse path of S-BFD packet are likely
   inconsistent going through different intermediate nodes or links.
   This document describes a method to keep the forward path and
   reverse path of S-BFD consistent when detecting SRv6 Policy.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-lin-sbfd-path-consistency-over-srv6/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-lin-sbfd-path-consistency-over-srv6-00


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
This e-mail and its attachments contain confidential information from New H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!