[ovs-dev] Open Vswitch Feature Enhancement- Provider Bridging Feature

Hiteshi Madan hiteshi.madan at tcs.com
Mon Oct 13 08:52:00 UTC 2014


Hi Team,

We are thinking to contibute in following feature ;

       -IEEE 802.1ah (Provider Backbone Bridging).

If anybody is already working on it please let us know.

Thanks & Regards,
Hiteshi Madan
-----Hiteshi Madan/DEL/TCS wrote: -----
To: Ben Pfaff <blp at nicira.com>
From: Hiteshi Madan/DEL/TCS
Date: 09/24/2014 01:04PM
Cc: dev at openvswitch.org
Subject: Re: Open Vswitch Feature Enhancement- Provider Bridging Feature

Hi Thomas,

While working on 802.1ad feature(provider bridging),will you also incorporate IEEE 802.1ah (Provider Backbone Bridging)?
Can we Plan to implement IEEE 802.1ah (Provider Backbone Bridging) feature separtely?

Thanks & Regards,
Hiteshi Madan

-----Ben Pfaff <blp at nicira.com> wrote: -----
To: Hiteshi Madan <hiteshi.madan at tcs.com>, Thomas F Herbert <thomasfherbert at gmail.com>
From: Ben Pfaff <blp at nicira.com>
Date: 09/02/2014 08:48PM
Cc: dev at openvswitch.org
Subject: Re: Open Vswitch Feature Enhancement- Provider Bridging Feature

On Mon, Sep 01, 2014 at 05:16:49PM +0530, Hiteshi Madan wrote:
> Hi Ben and Team,
> 
> I have checked the features list supported in open Vswitch.I found that following feature is not yet supported:
> 
> ?-??? 802.1ad (provider bridging)
> 
> We are thinking to contribute in above feature.
> 
> Can you please provide your inputs/opinions and suggestion for it?
> Also can you please provide any documents link which can help us to understand the code flow in faster way?

Please coordinate with Tom Herbert (CCed), who is also working on an
implementation.
  
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you





More information about the dev mailing list