Re: [bess] WG adoption call and IPR poll for draft-rabadan-bess-vendor-evpn-route-07

Hi Jim,

The route type value is an “scarce” resource, with 11 values currently allocated and more described in drafts. With the success of EVPN in the industry and its use for multiple applications, we wanted to reserve a value that can be used for applications that are specific to a vendor, or even for experimental use. Reserving the last value of an IANA registry for this, is not uncommon in IETF, is it?

Besides that, we want to define a generic key and format for this type 255, so that RRs that don’t understand the specific application can still compare routes and reflect them accordingly.

Thank you.
Jorge

From: BESS <bess-bounces@ietf.org> on behalf of "UTTARO, JAMES" <ju1738@att.com>
Date: Tuesday, August 20, 2019 at 8:44 PM
To: Jeff Tantsura <jefftant.ietf@gmail.com>, "bess@ietf.org" <bess@ietf.org>, Stephane Litkowski <slitkows.ietf@gmail.com>
Subject: Re: [bess] WG adoption call and IPR poll for draft-rabadan-bess-vendor-evpn-route-07

Could the authors provide further insight on the following..

“   The intend of this new Type is to allow operators and vendors to
   design rapidly new EVPN applications/prototypes and experiment with
   them in deployed networks before standardizing the specific
   application. Software Defined Networks (SDN) are evolving fast and
   the flexibility allowed by this new Route Type will contribute to the
   SDN control plane evolution.”

Thanks,
              Jim Uttaro

From: BESS <bess-bounces@ietf.org> On Behalf Of Jeff Tantsura
Sent: Tuesday, August 20, 2019 1:24 PM
To: bess@ietf.org; Stephane Litkowski <slitkows.ietf@gmail.com>
Subject: Re: [bess] WG adoption call and IPR poll for draft-rabadan-bess-vendor-evpn-route-07

In general I support the adoption.

Could the authors please clarify how a company that doesn’t have OUI assigned should populate the OUI field and how interdependency between IEEE registration and EVPN implementation would be handled.

Informal references for IEEE OUI handling process would be useful too, perhaps this one - https://standards.ieee.org/products-services/regauth/tut/index.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__standards.ieee.org_products-2Dservices_regauth_tut_index.html&d=DwQFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=MYuiLReJlALiFwDrRezkBWP2u4ggWRWeN0eIP5w7al8&s=XUVcfVx2JQIwaW8F6JwTZo3uoNsUuvw6Eh80onubSKg&e=>

Cheers,
Jeff
On Aug 20, 2019, 5:15 AM -0400, Stephane Litkowski <slitkows.ietf@gmail.com<mailto:slitkows.ietf@gmail.com>>, wrote:

Hi,

This email begins a two-weeks WG adoption poll for draft-rabadan-bess-vendor-evpn-route-07 [1]
Please review the draft and post any comments to the BESS working group list.

We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an author or a contributor of this document, please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR, copying the BESS mailing list. The document won't progress without answers from all the authors and contributors.
Currently, there are no IPR disclosures against this document..

If you are not listed as an author or a contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.

This poll for adoption closes on 2nd September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-rabadan-bess-vendor-evpn-route/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Drabadan-2Dbess-2Dvendor-2Devpn-2Droute_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=MYuiLReJlALiFwDrRezkBWP2u4ggWRWeN0eIP5w7al8&s=3J4-0GVkpzaHtSWBVIB1M27NrF9hWg4vgc00q896Bvo&e=>
_______________________________________________
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=DwQFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=MYuiLReJlALiFwDrRezkBWP2u4ggWRWeN0eIP5w7al8&s=7DyN6_vPh_Mrdl3tDhi4_pFpdiiKFTL8LBLzX38CLDs&e=>