I'm referring to support for dynamic/ephemeral configuration. Thanks, Kent
From: "Alexander Clemm (alex)" <[email protected]<mailto:[email protected]>> Date: Monday, November 17, 2014 at 2:55 PM To: Kent Watsen <[email protected]<mailto:[email protected]>>, Dean Bogdanovic <[email protected]<mailto:[email protected]>>, Jason Sterne <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> 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:[email protected]] Sent: Monday, November 17, 2014 11:44 AM To: Dean Bogdanovic; Jason Sterne; Alexander Clemm (alex) Cc: [email protected]<mailto:[email protected]> 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 [email protected] https://www.ietf.org/mailman/listinfo/i2rs
