Subject: Re: [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps

From: "Ali Sajassi (sajassi)" <[email-masked]>
Date: Mon, 6 Jun 2016 17:11:57 +0000

Hi Thomas,

I updated and checked-in a new rev of this draft couple of weeks ago to address the comments that came up on this email thread - the main changes were outlined in my previous email. Can you please progress this draft for its LC. If there is any issue preventing the progress of this draft, would you let us know.

Regards,
Ali

From: Cisco Employee <[email-masked]<mailto:[email-masked]>>
Date: Tuesday, May 24, 2016 at 12:04 AM
To: John E Drake <[email-masked]<mailto:[email-masked]>>, Thomas Morin <[email-masked]<mailto:[email-masked]>>, IDR <[email-masked]<mailto:[email-masked]>>, BESS <[email-masked]<mailto:[email-masked]>>, "[email-masked]<mailto:[email-masked]>" <[email-masked]<mailto:[email-masked]>>, "Rabadan, Jorge (Nokia - US)" <[email-masked]<mailto:[email-masked]>>, "[email-masked]<mailto:[email-masked]>" <[email-masked]<mailto:[email-masked]>>
Subject: Re: [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps
Resent-From: <[email-masked]<mailto:[email-masked]>>, Cisco Employee <[email-masked]<mailto:[email-masked]>>
Resent-To: Cisco Employee <[email-masked]<mailto:[email-masked]>>, <[email-masked]<mailto:[email-masked]>>, <[email-masked]<mailto:[email-masked]>>, <[email-masked]<mailto:[email-masked]>>, <[email-masked]<mailto:[email-masked]>>, <[email-masked]<mailto:[email-masked]>>, <[email-masked]<mailto:[email-masked]>>
Resent-Date: Tuesday, May 24, 2016 at 12:05 AM

Folks,

I have updated and published rev03 of even-overlay draft.
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay/

The main changes are:

  1.  section 10.2 - DCI using ASBR
  2.  The setting of Ethernet tag and VNI fields - there were some inconsistencies in different sections. Section 5.1.3 captures the setting of these fields for different type of services in pretty good details. All other sections were cleaned up and now refer to section 5.1.3.

Thomas,
The draft is ready for its long-overdue WG LC considering how long its has been around and its multi-vendor implementation status.

Regards,
Ali