Modifications of such material outside the IETF Standards Process. Material may not have granted the IETF Trust the right to allow The person(s) controlling the copyright in some of this This document may contain material from IETF Documents or IETFĬontributions published or made publicly available before Novemberġ0, 2008. The Trust Legal Provisions and are provided without warranty as Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal ![]() RFC 6733 Diameter Base Protocol October 2012Ĭopyright (c) 2012 IETF Trust and the persons identified as the Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained at Internet Standards is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. ![]() The Diameter base protocol as defined in thisĭocument obsoletes RFC 3588 and RFC 5719, and it must be supported by ![]() This document specifies the message format, transport,Įrror reporting, accounting, and security services used by allĭiameter applications. The Diameter base protocol is intended to provide an Authentication,Īuthorization, and Accounting (AAA) framework for applications suchĪs network access or IP mobility in both local and roaming Request for Comments: 6733 Telcordia TechnologiesĬategory: Standards Track Ericsson Research Updated by: 7075, 8553 Errata Exist Internet Engineering Task Force (IETF) V.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |