CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 21:55:51 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=U4FbBZLglhOd.XzIllUJCn_3XbixwlqY8d5bl396kEo-1760219751-1.0.1.1-HkPmjTcw41Pwh0x0ZWZkrNn13qqy7UVLgCutPgVyvQUVEB3iVz4hUz1d4qm_U4jDBbrnXtjniWBaAJuzFVhmcuPWa2meOx0PMdg1iVnfTVo; path=/; expires=Sat, 11-Oct-25 22:25:51 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98d19a9e9abe8e4d-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 6737 » RFC Editor
Search RFCs
RFC 6737
The Diameter Capabilities Update Application, October 2012
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6737
Discuss this RFC: Send questions or comments to the mailing list dime@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6737
Abstract
This document defines a new Diameter application and associated Command Codes. The Capabilities Update application is intended to allow the dynamic update of certain Diameter peer capabilities while the peer-to-peer connection is in the open state. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us