Update to the Extensible Authentication Protocol (EAP) Applicability Statement for Application Bridging for Federated Access Beyond Web (ABFAB)

Abstract

This document updates the Extensible Authentication Protocol (EAP) applicability statement from RFC 3748 to reflect recent usage of the EAP protocol in the Application Bridging for Federated Access Beyond web (ABFAB) architecture. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7057.

A GSS-API Mechanism for the Extensible Authentication Protocol

“…Together this combination will provide federated authentication and authorization for GSS-API applications. This specification meets the applicability requirements for EAP to application authentication [RFC7057].…”

An Improved Secure SIP Registration Mechanism to Avoid VoIP Threats

“…SIP uses HTTP messages in Uniform Resource Identifiers (URIs) requests that are initiated between SIP peers, while SMTP is used in the SIP headers. SIP security mechanisms were described in the following RFCs: RFC 3261 (Rosenberg, et al, 2003), RFC 3329 (Camarillo, 2004), RFC 4474 (Peterson et al, 2006), and RFC 7057 (Winter et al, 2013). These mechanisms are related to HTTP Digest authentication, S/MIME, TLS, and IPSec models.…”