Phil Shafer

Experience

1. Software Architect

   Juniper Networks

   Nov 1997 — Present

   For the last 16 years, I\'ve worked on the JUNOS User Interface beginning with ideas sketched our during my job interview with Paul Traina and incorporating concepts and ideas from the team, our customers, SEs and many other sources. These include the XML API (on which the NETCONF standard is based), the DDL data definition language (on which the YANG standard is based), configuration groups, on-box scripting (aka JUNOS Automation), the SLAX scripting language (an alternative syntax for XSLT), and the off-box JUISE scripting environment. Distilling widely varying customer needs into simple, reusable technologies has been a central theme, as has reducing the volume of \'noise\' in the configuration data that users need to view. In contrast with the traditional view of configuration as a set of commands, JUNOS views configuration data as real data, allowing it to be the target of commands like \"rename\",\"deactivate\", etc, and the centralization and abstraction of data has allowed us to add features into the common UI infrastructure that are instantly universally available. Data the user sees in the CLI is trafficked internally in XML, with CLI doing the XML to text converson. This means our data is easily available in the XML API, with no lag between \"shipping\" and \"supported in the API\".

Skills

• Routing
• C
• Programming
• Yang
• Networking
• Juise
• Bgp
• Perl
• Data Center
• Junos
• Open Source
• Ietf
• Netconf
• User Interface
• Juniper
• Ethernet
• Xml
• Juniper Technologies
• Unix
• Slax
• Tcp/Ip
• Network Management
• Network Architecture
• Tcp/Ip Protocols
• Ip
• Software Development