Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

"Tapraj Singh (tapsingh)" <tapsingh@cisco.com> Tue, 16 October 2018 13:25 UTC

Return-Path: <tapsingh@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6117C130DE1 for <bess@ietfa.amsl.com>; Tue, 16 Oct 2018 06:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.575
X-Spam-Level:
X-Spam-Status: No, score=-12.575 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.064, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 RmFeSrB3b_2P for <bess@ietfa.amsl.com>; Tue, 16 Oct 2018 06:25:26 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52B3112D4EE for <bess@ietf.org>; Tue, 16 Oct 2018 06:25:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=83886; q=dns/txt; s=iport; t=1539696326; x=1540905926; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=x/ryqaXJhaxPETngxBy/Mgkzh6CmgT6iCFtmyU3MznU=; b=hx6ylji4IhkGwC9Xh74wimqcCqsB82hqIW2eR/3a/xCLkeX1rWc5WmMT pOA4A55lGKTvT9shvBZ62v4nWrZRwXyglcqWlYjFpx94B0rgLCyI0Guv1 r8ASKjB6idu+QwZ5jsJy90izM4iyydoBSkoaip+Zyn/nyyQiArTZrr3j0 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAABr5sVb/4UNJK1jGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQxIBSpmfygKg2uIF447iHSOE4F6CwE?= =?us-ascii?q?BGAEJhEoCF4RPITQNDQEDAQECAQECbRwMhTkBAQEBAwEBGAkKQQsQAgEIEQM?= =?us-ascii?q?BAQEhAQYDAgICHwYLFAkIAgQBDQUUgwwBgR1MAxUPpgmBLod7DYIYi0wXgUE?= =?us-ascii?q?/gREBJx+CHi6CVkUBAQIYgQMkAQE1CQYQCIJFMYImAohEIYVDhWgliUcuCQK?= =?us-ascii?q?GU4ZjgyMXgU9MhCSJX4c8hQd2iE0CERSBJh04J4EucBU7KgGCQQmBbTAXfAE?= =?us-ascii?q?CBoJChRSFPQFvAQGJOYEfgR8BAQ?=
X-IronPort-AV: E=Sophos;i="5.54,388,1534809600"; d="scan'208,217";a="249037662"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Oct 2018 13:25:12 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id w9GDPCZo000954 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 16 Oct 2018 13:25:12 GMT
Received: from xch-rcd-009.cisco.com (173.37.102.19) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 16 Oct 2018 08:25:11 -0500
Received: from xch-rcd-009.cisco.com ([173.37.102.19]) by XCH-RCD-009.cisco.com ([173.37.102.19]) with mapi id 15.00.1395.000; Tue, 16 Oct 2018 08:25:11 -0500
From: "Tapraj Singh (tapsingh)" <tapsingh@cisco.com>
To: John E Drake <jdrake@juniper.net>, "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>, Zhuangshunwan <zhuangshunwan@huawei.com>, Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
CC: "jiang.he@ericsson.com" <jiang.he@ericsson.com>, "p.muthu.arul.mozhi@ericsson.com" <p.muthu.arul.mozhi@ericsson.com>, "bess@ietf.org" <bess@ietf.org>, "jaikumar.somasundaram@ericsson.com" <jaikumar.somasundaram@ericsson.com>
Thread-Topic: [bess] EVPN MH: Backup node behavior in Primary Path Failure
Thread-Index: AQHUW7tPwY67GDKFZkSdu6BevJADsqUO0DWQgAAs0YD//2wngIAAOYeAgAAP8QCAABE+gIAAur4AgAAlfICAEcCXwIAAk7iAgAA/goD//5ZQgA==
Date: Tue, 16 Oct 2018 13:25:11 +0000
Message-ID: <5C803F71-DC25-4BB3-BC13-EC35BB9DA783@cisco.com>
References: <067ED9A1-F8D0-4C53-97A0-3E6FA7E063EC@nokia.com> <VI1PR07MB4302D68B2828F10E49C834A486EA0@VI1PR07MB4302.eurprd07.prod.outlook.com> <D4979895-D9D9-434D-A247-62682E678853@nokia.com> <CAKz0y8zP+h+=tvEiiM=5MZxzdtk43_jOJ8BxtgENs5D-Orx98Q@mail.gmail.com> <19D6CCFE-183E-4BF7-A7D2-7D5F9DA96D7A@nokia.com> <CAKz0y8xzxNv2EBuCmUC2r5=tDozc1th41Ao0dbdVXcAbEQLJRw@mail.gmail.com> <9B51E983-4E46-4E7B-9F28-F161A6CB362F@nokia.com> <CAKz0y8yjjCpxf76iZFUkgkDk24=PR_=2nqt26JWJCQROx4xcmg@mail.gmail.com> <7300ABF3-3BEC-452D-8609-258BFF563B34@nokia.com> <19AB2A007F56DB4E8257F949A2FB9858DC48C158@NKGEML515-MBX.china.huawei.com> <AM0PR07MB384409BA9BB5DD71AECE4B8EF7FE0@AM0PR07MB3844.eurprd07.prod.outlook.com> <BN7PR05MB4354814E7D525E350098B967C7FE0@BN7PR05MB4354.namprd05.prod.outlook.com>
In-Reply-To: <BN7PR05MB4354814E7D525E350098B967C7FE0@BN7PR05MB4354.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.107.108]
Content-Type: multipart/alternative; boundary="_000_5C803F71DC254BB3BC13EC35BB9DA783ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.17, xch-aln-007.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/QBYlIYusgh8CMyY3JQF06mY6B4o>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Oct 2018 13:25:30 -0000

  Agree with John suggestion.

Thanks
Tapraj

From: BESS <bess-bounces@ietf.org> on behalf of John E Drake <jdrake@juniper.net>
Date: Tuesday, October 16, 2018 at 5:43 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>, Zhuangshunwan <zhuangshunwan@huawei.com>, Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Cc: "jiang.he@ericsson.com" <jiang.he@ericsson.com>, "p.muthu.arul.mozhi@ericsson.com" <p.muthu.arul.mozhi@ericsson.com>, "bess@ietf.org" <bess@ietf.org>, "jaikumar.somasundaram@ericsson.com" <jaikumar.somasundaram@ericsson.com>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Jorge,

The other possibility for this case is for each PE to advertise a Per EVI Ethernet A-D route for only those EVIs for which it would become DF if the current DF were to fail..

Yours Irrespectively,

John

From: BESS <bess-bounces@ietf.org> On Behalf Of Rabadan, Jorge (Nokia - US/Mountain View)
Sent: Tuesday, October 16, 2018 4:56 AM
To: Zhuangshunwan <zhuangshunwan@huawei.com>; Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Cc: jiang.he@ericsson.com; p.muthu.arul.mozhi@ericsson.com; jaikumar..somasundaram@ericsson.com; bess@ietf.org
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Hi,

RFC7432 explains that if there are more than 2 PEs in the ES, then, upon receiving the AD route withdrawals, the remote PE will flood. That is, it’ll flush the MACs and flood since it does not know who the new DF is, and there is no backup for a given MAC.

So yes, with more than 2 PEs, there is no backup per se. Note that, even if we had the BDF indication, upon an ES failure the remote PE will start receiving MAC/IP route withdrawals. Hence unless the re advertisements of the MACs start coming immediately, the BDF indication may not avoid flooding anyway.. We can add the P and B bits here too, but they may not be as useful as in RFC8214.

Thanks,
Jorge


________________________________
From: Zhuangshunwan <zhuangshunwan@huawei.com<mailto:zhuangshunwan@huawei.com>>
Sent: Tuesday, October 16, 2018 00:19
To: Rabadan, Jorge (Nokia - US/Mountain View); Muthu Arul Mozhi Perumal
Cc: jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>; p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>; bess@ietf.org<mailto:bess@ietf.org>; jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>
Subject: RE: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Hi Jorge,

8.4.  Aliasing and Backup Path of RFC7432 says:

<snip>
.   The backup path is a closely related function, but it is used in
.   Single-Active redundancy mode.  In this case, a PE also advertises
.   that it has reachability to a given EVI/ES using the same combination
.   of Ethernet A-D per EVI route and Ethernet A-D per ES route as
.   discussed above, but with the "Single-Active" bit in the flags of the
.   ESI Label extended community set to 1.  A remote PE that receives a
.   MAC/IP Advertisement route with a non-reserved ESI SHOULD consider
.   the advertised MAC address to be reachable via any PE that has
.   advertised this combination of Ethernet A-D routes, and it SHOULD
.   install a backup path for that MAC address.
<snip>

Actually, do we think that the function described in this section only works when there are only 2 PEs in one ES?
When there are more than 2 PEs in one ES, it cannot work unless RFC7432 also introduce the BDF election function defined in RFC8214.

Regards,
Shunwan

From: BESS [mailto:bess-bounces@ietf.org] On Behalf OfRabadan, Jorge (Nokia - US/Mountain View)
Sent: Friday, October 05, 2018 2:01 PM
To: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com<mailto:muthu.arul@gmail.com>>
Cc: jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>; p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>; bess@ietf.org<mailto:bess@ietf.org>; jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

That should be true only in RFC8214. That’s my point…

From:Muthu Arul Mozhi Perumal <muthu.arul@gmail.com<mailto:muthu.arul@gmail.com>>
Date: Friday, October 5, 2018 at 5:47 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>
Cc: "jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>" <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>, "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>, "jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>" <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>, "p.muthu.arul...mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>" <p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Thanks, Jorge.

In EVPN single-active dual-homing or EVPN VPWS single-active multi-homing, when other PEs realize that the DF is dead, they all need to re-run the DF election for sure. However, traffic recovery need not wait until the DF election gets over electing a new DF..it only requires the other PEs and the backup to realize the primary/DF is dead and start forward. That's my point..

Regards,
Muthu

On Fri, Oct 5, 2018 at 1:30 AM Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>> wrote:
Muthu,


From:Muthu Arul Mozhi Perumal <muthu.arul@gmail.com<mailto:muthu.arul@gmail.com>>
Date: Thursday, October 4, 2018 at 5:37 PM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>
Cc: "jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>" <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>, "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>, "jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>" <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>, "p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>" <p...muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Thanks, Jorge. This is inline with my thinking. So, in single-active multihoming, once the primary is dead we don't need to wait for the DF election to happen for the backup (or some other PE in the ES) to become active and start forwarding traffic over the ES, instead it only requires the remote PEs and backup to realize that the primary is dead (thru' NH tracking / BFD) and start forwarding over the ES, right?
[JORGE] When the other PEs in the ES realize the DF is dead, they need to remove the dead PE from the candidate list and run DF Election. You may optimize things if you only have two PEs in the ES (such as skip the timer) but if you have more than 2 PEs in the ES, there is really no concept of backup PE in RFC7432, but simply the other PEs are non-DF. However, the concept of backup PE in an ES with more than two PEs is specified in RFC8214, where all the PEs in the ES not only elect a DF but also a backup DF, and signal this backup condition in the AD per-EVI routes. Note this is not there in RFC7432.

Regards,
Muthu

On Thu, Oct 4, 2018 at 8:10 PM Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>> wrote:
Muthu,

About this:

Suppose we have a full mesh of iBGP sessions b/w the PEs, then who would withdraw the routes if the primary PE / DF itself fails? Instead, the BGP session would timeout causing the primary PE's neighbors to flush out the A-D routes received from the primary PE, right? This can take several seconds, isn't it?

No, not in the implementations I know of. Next Hop tracking will immediately detect that the PE is not in the network anymore and the routes will be invalidated. You can also bootstrap the BGP sessions to BFD.
But that has nothing to do with EVPN!.. it’s regular BGP.

Thx
Jorge

From:Muthu Arul Mozhi Perumal <muthu.arul@gmail.com<mailto:muthu.arul@gmail.com>>
Date: Thursday, October 4, 2018 at 1:14 PM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>
Cc: "jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>" <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>, "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>, "jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>" <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>, "p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>" <p...muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Please see inline..

On Thu, Oct 4, 2018 at 3:33 PM Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>> wrote:
In-line.

Thx
Jorge

From:Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>
Date: Thursday, October 4, 2018 at 11:28 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>, "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Cc: Jiang He <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>, P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: RE: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Thanks Jorge for the quick reply.
Please find further question below.

From: Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>
Sent: Thursday, October 4, 2018 1:52 PM
To: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>;bess@ietf.org<mailto:bess@ietf.org>
Cc: Jiang He <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>; P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Hi,


Questions:
1.      Will the node in backup mode forward the packet to CE?

[JORGE] as soon as it becomes DF it can forward packets to the CE. The backup node will have to run DF election upon the ES route withdrawal from the primary. If AC-DF is enabled, it can also react to the withdrawal of AD routes from the primary PE.

[Jai] Does that mean if any packet comes to a node that is still in the backup mode will get dropped, before the new DF election is complete? Why cant this be used as FRR? Or what is the use case of having backup node(s)?

[JORGE2] when the primary node fails, ES and AD routes are withdrawn.
Suppose we have a full mesh of iBGP sessions b/w the PEs, then who would withdraw the routes if the primary PE / DF itself fails? Instead, the BGP session would timeout causing the primary PE's neighbors to flush out the A-D routes received from the primary PE, right? This can take several seconds, isn't it?

Regards,
Muthu

The AD route withdrawal is an indication for remote nodes that they have to send traffic to the backup (for a given MAC) or to flush the MACs if there are more than 2 PEs in the ES. Around the same time or maybe earlier, the ES route withdrawal will make the backup PE take over as DF. So the overall convergence time will depend on how/when those two things happen in time. Only the DF PE can forward traffic. A non-DF can never forward traffic or there will be risk of duplicate packets.


2.      Will all the nodes in backup mode forward the packet before DF election?

[JORGE] Only the new DF can forward.



3. If they forward, how is duplicate packets handled, in this case?
[JORGE] see above.

My two cents..

Thanks.
Jorge



From:BESS <bess-bounces@ietf.org<mailto:bess-bounces@ietf.org>> on behalf of Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson..com>>
Date: Thursday, October 4, 2018 at 10:03 AM
To: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Cc: Jiang He <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>, P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: [bess] EVPN MH: Backup node behavior in Primary Path Failure


Hello Everyone,

Sorry if it is a duplicate. I repost this query as I did not receive any response yet.
(I was wondering if this mail already reached the group or not)


I have a question on Primary PE encountering a failure in EVPN multihoming

in single active mode.



RFC7432, section 14.1.1:

<snip>

   If there is more than one backup PE for a given ES, the remote PE

   MUST use the primary PE's withdrawal of its set of Ethernet A-D per

   ES routes as a trigger to start flooding traffic for the associated

   MAC addresses (as long as flooding of unknown unicast packets is

   administratively allowed), as it is not possible to select a single

   backup PE.

</snip>



Questions:

1. Will the node in backup mode forward the packet to CE?

2. Will all the nodes in backup mode forward the packet before DF election?

3. If they forward, how is duplicate packets handled, in this case?



Please help me anwere these questions.



Thanks & Regards

Jaikumar S


_______________________________________________
BESS mailing list
BESS@ietf.org<mailto:BESS@ietf.org>
https://www.ietf.org/mailman/listinfo/bess<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bess&d=DwMF-g&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=llt1h0ORtcdfSlkLb74jt9vVkGyLR7KhsJZdkWdoEgc&s=oDroIh7x63kHwujqh4jOajbDMQbGlP8jcMoIyVNdt6A&e=>