IETF Logo Mail Archive

Re: [Idr] Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)

"duzongpeng@foxmail.com" <duzongpeng@foxmail.com> Fri, 18 March 2022 01:20 UTC

Return-Path: <duzongpeng@foxmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14C063A1776 for <idr@ietfa.amsl.com>; Thu, 17 Mar 2022 18:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.164
X-Spam-Level:
X-Spam-Status: No, score=-4.164 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, FREEMAIL_FROM=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
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 1eZIP9BEx4hm for <idr@ietfa.amsl.com>; Thu, 17 Mar 2022 18:20:32 -0700 (PDT)
Received: from out162-62-57-87.mail.qq.com (out162-62-57-87.mail.qq.com [162.62.57.87]) (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 8F77B3A176F for <idr@ietf.org>; Thu, 17 Mar 2022 18:20:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1647566426; bh=7OEnpE8J+car84rnSgNj4WVSC3vlMDG4LmBfH6fqYH8=; h=Date:From:To:Subject:References; b=Cj8f0Fdub7aIDGeFeVZhQWdhKnPZae88nzIwfJHaJGvMd2/wdRR29ch5O5lHmRM2M Tn9gHXkUPqLeLp+xlF4el7II/fsNKQ3t26U9LCvbxuMado+tWKNOaWXdKwCN+2vkFH gLwPcesD3ODt4HuQQeagvyHPRnIcEO06SJj0ZC80=
Received: from cmcc-PC ([103.35.105.43]) by newxmesmtplogicsvrsza5.qq.com (NewEsmtp) with SMTP id 51884E6B; Fri, 18 Mar 2022 09:20:24 +0800
X-QQ-mid: xmsmtpt1647566424tgm2hbuiq
Message-ID: <tencent_836AAFFC050ACC079B5D85EFA9AD416D3E05@qq.com>
X-QQ-XMAILINFO: NKv2G1wnhDBnlKw/5d8qSEVEfI5wdxdGiXreFA6CR03KwCjAg1AmUH14Ot2gJd B+nFXJItWi1KEEedgLWRuL4j9Dap4JJ5rFSP7nW001ViAPeEtYleJbo5ydfR4z8aGmsr9nujGtBp 5PIQF/A32nzZ0zIdCyNCiVUiLqLcDnT/p5Z3jO3CZW6wUyZj54x9m3f0wwZFk66/C+cHzoeDIfzY oJAVI6CaJw88VfpgTAoqUZryWei+dU1y+J5RtHDruCI1+hQmnvMfMzQXaVQUVbFoAFIRQWhtRdx+ TRc6OX8zhJz4EY3dxvI3y35lh/HeusGOhcBitt9Peb3H58TPmvoAWDLQ8SR/jZ93y4LlZt/h6UOG yJjAb3Xz+bqO+LKY+r/5kSgDUIvMKvtqPRYXlsUg6hE+uDeK6DJD8JGpTmvR3Vcav2446qCW84Gb AkBo6YLZBEBWfQHJrOWPnwbGrkR+foRthMJM1ouWNapN5t0Ow2dwtLt0L09QtkwNLruXQTg1tSS9 ovjI3O2zRfFMg294MBNPdWKBxw/HCuJLb68ot4rxoQ2hpCSGre1oa2B34F/LXGSiV2MtUmjUf6Ea O3kfCjfHNA3M/ozCvkwuqkuAhLjqA+B9PTXxJYcvnapSygoFxurA3N3Daa3CPujhT9mGYtn0pCcv M4GM1BZpCMogZnnAr9+ZKkncSxmafxc21316n1IC48rNOiNNbPUV8tmynFP2mYcyDZQQ15t8j/GR Rw5kh7kk/e8aTdLOIR3CwElQWw69wkXmwwXe3ILSLdvANQ/hUoJhlhkztscbpHw9KLP/3Ye8Og7I aQDEfszg8NmyECLeIhVcQrAUR/Q92xe9RELE8MEEJdDYrUjdOWkkjDNFHXebfG1yIBPj/d7h1DxA cOk9lhv/3JVY2J5MiN0by4eOyo5IXU2ushQpeQGcH4RXHULWcnj+js/qxwaX8w+A==
Date: Fri, 18 Mar 2022 09:22:58 +0800
From: "duzongpeng@foxmail.com" <duzongpeng@foxmail.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf. org" <idr@ietf.org>
References: <00ca01d8348c$8b05d270$a1117750$@ndzh.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.23.116[cn]
Mime-Version: 1.0
X-OQ-MSGID: <202203180922581656801@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart362806434864_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/EYKrI09jc-FGlH18pMjl6khGUnE>
Subject: Re: [Idr] Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2022 01:20:37 -0000

Hi, all

    I support the adoption. It is necessary for the deployment of IFIT in the network.


Best Regards
Zongpeng Du



duzongpeng@foxmail.com & duzongpeng@chinamobile.com
 
From: Susan Hares
Date: 2022-03-10 22:38
To: idr@ietf.org
Subject: [Idr] Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)
Greeting: 
 
This begins a 2 week WG Adoption call (3/10/2022 to 3/24/2022) 
for draft-wang-idr-bgp-ifit-capabilities-04
https://datatracker.ietf.org/doc/draft-wang-idr-bgp-ifit-capabilities/
 
In your comments please consider if: 
 
1) Do the additions to BGP (2 Communities and 
TLV for next-hop-capability attribute) 
help the distribute information regarding the  IFIT options 
from tail (egress) nodes to head nodes (ingress)?  
 
Are there any cases where these BGP 
Communities should be removed or ignored?  
 
 
2) Are the mechanisms (2 Communities and 
attribute TLV) correctly specified? 
 
3) How do these additions interaction with the 
  With SR technology for IFIT described in 
   draft-ietf-idr-sr-policy-ifit, and its 
   use of RFC9012 (tunnel attributes)? 
 
(Authors an example on how these
technologies work together or 
 operate separately would be helpful). 
 
4)  Will this addition help network operators 
deploying IFIT technology? 
 
 
Cheerily, Sue

v2.23.0 | Report a Bug | By Email