Hi Ketan,
Please see in line with [Yubao].
Thanks,
Yubao
原始邮件
发件人：KetanTalaulikar
收件人：王玉保10045807;
抄送人：draft-ietf-bess-srv6-servi...@ietf.org;BESS;
日 期 ：2022年06月17日 13:33
主 题 ：Re: Whether the TC/S field of the ESI label field can be used to carry a
portion of Arg.FE2
Hi Yubao,
The label fields per RFC7432 are 24-bit. When carrying actual MPLS labels
in them, the high-order 20 bits are to be used per RFC7432. The rest of the
4 bits are not meant for TC/S though. Moreover, for SRv6 we are following
the convention of VXLAN where 24-bit VNI is encoded in the EVPN
Hi Ketan,
Thanks for your clarifications.
But I still don't notice that RFC7432 has said that the label value is 24 bits,
I just found these paragraphs in RFC7432 or rfc7432bis:
The MPLS Label1 field is encoded as 3 octets, where the high-order
20 bits contain the label val
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the BGP Enabled ServiceS WG of the IETF.
Title : EVPN VPWS Flexible Cross-Connect Service
Authors : Ali Sajassi
Patrice Brisset
Hi Yubao,
Sorry for the delay in response and thanks for catching this issue. We'll
try to correct this during the AUTH48 process.
Please check inline below.
On Thu, May 26, 2022 at 8:20 AM wrote:
>
> Hi authors,
>
>
> There may be conflicting description in
> draft-ietf-bess-srv6-services-15#
Reviewer: Joel Halpern
Review result: Ready
This is a routing directorate review of draft-ietf-bess-evpn-lsp-ping-07
provided by Joel Halpern at the request of the routing directorate review team
leaders as input to the routing area directors. Please treat as any other
review comments.
(Apologie
Hi Jeffrey,
Please see Dfh3> below.
Thanks.
Fanghong
From: Jeffrey (Zhaohui) Zhang [mailto:zzhang=40juniper@dmarc.ietf.org]
Sent: Thursday, June 16, 2022 10:17 AM
To: duanfanghong ; bess@ietf.org
Cc: Xiejingrong (Jingrong) ; Gengxuesong (Geng Xuesong)
; Wangheng (MCAST, P&S)
Subject: RE: [
