Hello All, As discussed in meeting today. We will meet again at 8:00AM PST on Friday 13th Dec 2019. The link for the meeting is as below. https://bluejeans.com/9192742159<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Furl%3Fq%3Dhttps%253A%252F%252Fbluejeans.com%252F9192742159%26sa%3DD%26usd%3D2%26usg%3DAFQjCNFJQliS8DvrNzwGqf6hFTZ7DCV_HQ&data=02%7C01%7Csapk%40vmware.com%7C2a7110da751b435f870a08d77d9b2c2a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637115977724498667&sdata=GckpZvcOXXTlJO4rIyFFXWKeFDSto%2BPeGl9m%2FWTOTac%3D&reserved=0> Agenda and topics to be discussed in upcoming meeting. 1. Review and conclude Static yang. 2. VRF usage conclusion. * We may not be able to use IETF network instance as currently libyang does not support mount option. * Making changes to existing IETF yang to allow VRF at top of the tree. 3. Port of all existing IETF Yang which could be used as is or with extensions in to FRR. * Interface yang. * Routing yang. * And so on. 4. Issues we encountered with libyang while using standard yang. * Currently if we are using ipv6-unicast-routing from IETF routing yang then libyang goes in a loop. * Remove few augment statements from rib-ext, as it is pointing to path which is not available in ietf-routing.yang Thanks Santosh P K