[spring] 答复: I-D Action: draft-yang-spring-ach6-sr-00.txt

"Yangfan (IP Standard)" <shirley.yangfan@huawei.com> Fri, 16 July 2021 09:34 UTC

Return-Path: <shirley.yangfan@huawei.com>
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 1E3333A2FDB for <spring@ietfa.amsl.com>; Fri, 16 Jul 2021 02:34:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 c2xjdkzLlUYX for <spring@ietfa.amsl.com>; Fri, 16 Jul 2021 02:34:24 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2ABE3A2FD8 for <spring@ietf.org>; Fri, 16 Jul 2021 02:34:23 -0700 (PDT)
Received: from fraeml745-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GR5Sl5Xy2z6FD69 for <spring@ietf.org>; Fri, 16 Jul 2021 17:25:43 +0800 (CST)
Received: from kwepeml100005.china.huawei.com (7.221.188.221) by fraeml745-chm.china.huawei.com (10.206.15.226) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Fri, 16 Jul 2021 11:34:19 +0200
Received: from kwepeml500003.china.huawei.com (7.221.188.182) by kwepeml100005.china.huawei.com (7.221.188.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Fri, 16 Jul 2021 17:34:17 +0800
Received: from kwepeml500003.china.huawei.com ([7.221.188.182]) by kwepeml500003.china.huawei.com ([7.221.188.182]) with mapi id 15.01.2176.012; Fri, 16 Jul 2021 17:34:17 +0800
From: "Yangfan (IP Standard)" <shirley.yangfan@huawei.com>
To: Haoyu Song <haoyu.song@futurewei.com>, spring <spring@ietf.org>
Thread-Topic: I-D Action: draft-yang-spring-ach6-sr-00.txt
Thread-Index: AQHXdzj1OjiyQVpUKEe+QNvclLkaMqtAKqpQgAJ/YTCAARpVsIAAe6awgAESnyA=
Date: Fri, 16 Jul 2021 09:34:17 +0000
Message-ID: <531f54eaa85b429cb9d8c74b6fddb39f@huawei.com>
References: <162610642271.17197.10650711865428805159@ietfa.amsl.com> <63b9ef942bdd4457b3e11ce5490caeee@huawei.com> <BY3PR13MB4787FD125E823A4D67DDFA4D9A139@BY3PR13MB4787.namprd13.prod.outlook.com> <ea5677df676840ed8e783d191c7f54bd@huawei.com> <BY3PR13MB4787E7F89B6A24381ABF461A9A129@BY3PR13MB4787.namprd13.prod.outlook.com>
In-Reply-To: <BY3PR13MB4787E7F89B6A24381ABF461A9A129@BY3PR13MB4787.namprd13.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.115]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/UjHdmLktWkZG-9CnAq5mrTWuQ8g>
Subject: [spring] =?utf-8?b?562U5aSNOiBJLUQgQWN0aW9uOiBkcmFmdC15YW5nLXNw?= =?utf-8?q?ring-ach6-sr-00=2Etxt?=
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: Fri, 16 Jul 2021 09:34:29 -0000

Hi Haoyu,

I agree with you. Since ACH6 provides a control channel generally used for different ctrl/mgmt protocols by specifying Channel-Type, actually it avoids the worse situation where each protocol requires different SRH flags for indication. 
In this way, two SRH flags can have two indication functions:
1) indicate whether the payload is ACH6 ctrl packet or user data;
2) indicate whether every SID should check this ACH6 packet

I think it would be very friendly and only require limited modifications to current SRv6 implementations. 

Regards,
Fan 



-----邮件原件-----
发件人: spring [mailto:spring-bounces@ietf.org] 代表 Haoyu Song
发送时间: 2021年7月16日 0:37
收件人: Yangfan (IP Standard) <shirley.yangfan@huawei.com>om>; spring <spring@ietf.org>
主题: Re: [spring] I-D Action: draft-yang-spring-ach6-sr-00.txt

If we have one extensible mechanism to cover many important use cases, I don't think two flags are too luxury.
I think HBH and E2E are indeed two distinct requirements and for the efficiency of packet processing, they should be taken care of separately. 

Haoyu

-----Original Message-----
From: Yangfan (IP Standard) <shirley.yangfan@huawei.com> 
Sent: Thursday, July 15, 2021 6:10 AM
To: Haoyu Song <haoyu.song@futurewei.com>om>; spring <spring@ietf.org>
Subject: 答复: I-D Action: draft-yang-spring-ach6-sr-00.txt

Hi Haoyu,

Thank you for your comments.
In the draft I propose two approaches of ACH6 encapsulation, one is in IPv6 DOH EH, another is in payload as you said. 

To encap ACH6 message in payload and use SRH flag to indicate the processing has its advantages. 1) ACH6 packet encapsulated in payload would never get lost 2) friendly to present implementations. But I doubt that ACH6 may need two different flags to indicate whether intermediate node should process it or not. In draft-~-siam, T flag indicates every SR endpoint to process IOAM data. It is not necessary for every SR endpoint to process ACH6 packet if this packet is only e2e used. It might be too luxurious to be considered as an option. :) 

Best regards,
Fan 





-----邮件原件-----
发件人: spring [mailto:spring-bounces@ietf.org] 代表 Haoyu Song
发送时间: 2021年7月15日 0:47
收件人: Yangfan (IP Standard) <shirley.yangfan@huawei.com>om>; spring <spring@ietf.org>
主题: Re: [spring] I-D Action: draft-yang-spring-ach6-sr-00.txt

Dear authors,

I like the idea of ACH for SRv6, and I think the use cases make sense and expect to see more if such mechanism exists. However, my opinion is that, since ACH packets are dedicated control packets, it might be easier to  encapsulate it in UDP payload while using an SRH flag to indicate the presence of ACH, which is more extensible. In fact, I think this draft can be consolidated with our draft "draft-song-spring-siam-01" for supporting IOAM ins SRv6 https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-song-spring-siam-01&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822819814%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=eDkM9JCqsN%2FgIUaLg00PRy%2F1WOAg%2FrznagwtejcYtn8%3D&amp;reserved=0  because I can see the potential for ACH6 to become a generic mechanism in SRv6 to support OAM and message passing pertaining to specific SR paths. 
Look forward more discussions on this!

Best,
Haoyu 

-----Original Message-----
From: spring <spring-bounces@ietf.org> On Behalf Of Yangfan (IP Standard)
Sent: Monday, July 12, 2021 7:32 PM
To: spring <spring@ietf.org>
Subject: [spring] I-D Action: draft-yang-spring-ach6-sr-00.txt

Hi SPRING,

A new draft was submitted to specify how an ACH6 (associated channel over IPv6) control channel is used in a Segment Routing network. On one hand, SRv6 SIDs list in SRH provides a certain SRv6 path. On the other hand, ACH6 provides the control and management capability to the SRv6 path.

Here is some background info if you are not acquainted with ACH6, 
ACH6 is initially proposed at IETF 110 (https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-yang-rtgwg-ipv6-associated-channel-01&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822819814%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=lw40XWM%2Btq2bsaHTIEBsfSrTZ95TGTwVrn6ahrrFjKE%3D&amp;reserved=0)
ACH6 in SR (https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-yang-spring-ach6-sr&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822819814%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=eYmH1dL0tlgZNeeWktSencVDQ8Y09H6mh6C3wuUxtp0%3D&amp;reserved=0) and ACH6 OAM mechanism in SR (https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-yang-spring-ach6-oam-sr&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822829767%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=tvcmpAIfiQ3eoPzJoa0ZDtGgXHhX42z0ZHWESx610T8%3D&amp;reserved=0) are proposed at IETF 111

As always, comments and suggestions are welcome and appreciated. 

Stay safe.

Best regards,
Fan (on behalf of authors)



-----邮件原件-----
发件人: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] 代表 internet-drafts@ietf.org
发送时间: 2021年7月13日 0:14
收件人: i-d-announce@ietf.org
主题: I-D Action: draft-yang-spring-ach6-sr-00.txt


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


        Title           : ACH6 in Segment Routing
        Authors         : Fan Yang
                          Tianran Zhou
	Filename        : draft-yang-spring-ach6-sr-00.txt
	Pages           : 11
	Date            : 2021-07-12

Abstract:
   Associated Channel over IPv6 (ACH6) provides a control channel to one
   specific IPv6 forwarding path for control and management purpose.
   When ACH6 is used in a Segment Routing network, it provides a control
   channel to an SRv6 path.  This document specifies an SRv6 ACH6
   mechanism and describes how ACH6 is applied in a Segment Routing
   network.



The IETF datatracker status page for this draft is:
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-yang-spring-ach6-sr%2F&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822829767%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=pAQM4pTkFhAyfd9MfSi%2FZgTbLDV8dwMPjfeqhyme578%3D&amp;reserved=0

There is also an htmlized version available at:
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-yang-spring-ach6-sr-00&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822829767%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=hQ4LfPPGwqzLbbGSiwdLh65Hqpx0R3kAdOAXzJ7Cv7w%3D&amp;reserved=0


Internet-Drafts are also available by anonymous FTP at:
https://nam11.safelinks.protection.outlook.com/?url=ftp%3A%2F%2Fftp.ietf.org%2Finternet-drafts%2F&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822829767%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=9Yw1vKXSMjxB0ZmKLjH6Fw7L%2FDGZUVhRabPXIOskVQg%3D&amp;reserved=0


_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fi-d-announce&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822829767%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=Ogd4DSv10WnIEqfnClKg1EAuDytoWEGIUsu7R7Vhfq4%3D&amp;reserved=0
Internet-Draft directories: https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ietf.org%2Fshadow.html&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822829767%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=Y%2B7J9ObF%2BJ4MXv8AEh1q13asc6FMwMh3j37dLhVDvU4%3D&amp;reserved=0 or https://nam11.safelinks.protection.outlook.com/?url=ftp%3A%2F%2Fftp.ietf.org%2Fietf%2F1shadow-sites.txt&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822829767%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=Wzi2HtmPnmcSG0%2BWNk6UvyZZgDqoiTu1q%2BRr3jjBtDU%3D&amp;reserved=0
_______________________________________________
spring mailing list
spring@ietf.org
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fspring&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822829767%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=IX9urrjS6spFRyG15cN6ZZ2XrksEdyb5cxyhNhFyt2U%3D&amp;reserved=0
_______________________________________________
spring mailing list
spring@ietf.org
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fspring&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C58fe8ca575554e33fb4108d94791cdb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637619513822829767%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=IX9urrjS6spFRyG15cN6ZZ2XrksEdyb5cxyhNhFyt2U%3D&amp;reserved=0
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring