JET BGP API: JET compliance (Revision 2)

The routing protocol daemon (RPD) and other daemons expose external APIs to other daemons and external applications (including SDK and JET applications) through Juniper Extension Toolkit (JET). JET includes APIs to add, delete, and lookup routes. To keep the APIs consistent between different daemons, API Revision 2 is being defined. API Revision 2 unifies the API best practices, API naming conventions, the maintenance of APIs across different releases, and more. 

API Revision 2 focuses on following aspects: 

• Maintain the old PRPD API without any changes. 
• New package name for the new set API. 
• New JAPI filenames for the new set API. 
• Rename RPCs to follow naming conventions for the new set API. 
• Fix response messages to have code and sub-code in the new set API. 
• Move common definitions out of protocol files into common files in the new set API. 
• Check enum names, and make them unique according to the file scope in the new set API. 

 Specifically, this feature introduces Revision 2 for PRPD BGP APIs.