Kent,

Thank you for brining this topic. I would suggest to start with each vendor 
writing their own draft and then we can get together, analyze and merge the 
documents. We, Juniper, already have implementation, but before publishing 
draft, we are checking with legal, as there is some IPR.

As soon I hear back from legal, will respond to this thread.

Dean

On Nov 17, 2014, at 3:51 PM, Kent Watsen 
<kwat...@juniper.net<mailto:kwat...@juniper.net>> wrote:


I'm referring to support for dynamic/ephemeral configuration.

Thanks,
Kent


From: "Alexander Clemm (alex)" <a...@cisco.com<mailto:a...@cisco.com>>
Date: Monday, November 17, 2014 at 2:55 PM
To: Kent Watsen <kwat...@juniper.net<mailto:kwat...@juniper.net>>, Dean 
Bogdanovic <de...@juniper.net<mailto:de...@juniper.net>>, Jason Sterne 
<jason.ste...@alcatel-lucent.com<mailto:jason.ste...@alcatel-lucent.com>>
Cc: "i2rs@ietf.org<mailto:i2rs@ietf.org>" <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Subject: RE: documenting existing implementations

Hi Kent,
which specific items are you referring to? I assume the YANG models for 
topology?
For what has been implemented as part of Open Daylight, please see 
https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Model_Reference
Can you please be a bit more specific as to what would be the goal of producing 
a report, and which informed decision regarding what steps this is intending to 
support?
Thanks
--- Alex


From: Kent Watsen [mailto:kwat...@juniper.net]
Sent: Monday, November 17, 2014 11:44 AM
To: Dean Bogdanovic; Jason Sterne; Alexander Clemm (alex)
Cc: i2rs@ietf.org<mailto:i2rs@ietf.org>
Subject: documenting existing implementations

Dean, Alex, Jason,

My primary takeaway from the I2RS WG meeting is that existing implementations 
exist from ALU, Cisco, and Juniper.  It seems a practical engineering activity 
to document each of these implementations and discover where they 
converge/diverge, both with each other as well as the I2RS arch/req drafts.  
After said activity, the WG can make an informed decision regarding next steps.

Would you and/or others from your companies be interest in producing such a 
report?

Thanks,
Kent


_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to