anagement covers Internet management, protocols related to AAA (such as NETCONF, SNMP, RADIUS, and Diameter), and data modeling languages such as YANG. Operations is largely responsible for incorporating operator feedback and input regarding the IETF work. Routing Area (rtg): Is responsible for ensuring continuous operation of the Internet routing system and developing new protocols, extensions, and bug fixes in a timely manner. Security Area (sec): Focuses on security protocols that provide security services like integrity, authentication, non-repudiation, confidentiality, and access control. Transport Area (tsv): Covers a range of technical topics related to data transport on the Inter- net. It supports mechanisms that detect, react to, and manage congestion on the Internet, for protocols such as Transmission Control Protocol (TCP), Forward Error Correction (FEC), qual- ity of service, congestion control and management, and SO forth. The IETF collaborates and coordinates closely with the IEEE, most especially the 802 part of the organization. With this arrangement, the IETF gains improved access to IEEE 802 expertise in the very widely deployed LAN technologies, while IEEE 802 gains better access to IETF expertise on IP encapsulation, routing, and transport. See RFC 7241 for details on the relationship between the two organizations. Well before the IEEE defined PTP/1588, the IETF developed NTP through its RFC process. The IETF started specifying NTP starting in the mid-1980s (RFC 958), and its current version, version 4 (RFC 5905), is a very mature technology. Study on NTPv5 has been initiated with the goal of better accuracy, and the work is currently in RFC draft stage. RFC 5905 and RFC 4330 also define a subset of NTP called the Simple Network Time Protocol (SNTP) used to support networks and applications that do not require the complete range of NTP features and performance. Another notable contribution of the IETF to the area of timing is RFC 3339, which defines a date and time format for use in IP based o