From an IETF standard point of view, both IPsec and TLS are designed to provide secure network communications, but they have different histories and design philosophies.
IPsec was developed in the 1990s as part of the IPv6 protocol suite and was standardized by the IETF in RFC 2401 in 1998. Since then, there have been several updates to the protocol, including RFC 4301 in 2005 and RFC 7321 in 2014. These updates have addressed various issues such as key management, traffic protection, and interoperability with other protocols.
However, compared to TLS, IPsec has seen relatively few updates to its core protocol over the years. One reason for this is that IPsec is a more complex protocol than TLS, with a wider range of use cases and requirements. Updating the protocol can be difficult without disrupting existing deployments or introducing new interoperability issues. Additionally, the development of new IPsec standards can be slower than other protocols due to the need for consensus among vendors and stakeholders.
On the other hand, TLS was designed specifically for securing web-based communications, and was originally developed as SSL by Netscape in the 1990s. The IETF took over development of SSL and renamed it TLS in 1999, with the first version of TLS standardized in RFC 2246 in 1999. Since then, there have been several updates to the protocol, including TLS 1.1, TLS 1.2, and the latest version, TLS 1.3. These updates have focused on improving security, performance, and usability of the protocol.
Overall, while both IPsec and TLS are designed to provide secure network communications, the development and evolution of the protocols have followed different paths. IPsec has seen fewer updates to its core protocol over the years, likely due to the complexity of the protocol and the need to maintain interoperability with existing deployments. TLS, on the other hand, was designed specifically for web-based communications and has seen more frequent updates and improvements to its core protocol over the years.