RFC 7565: The 'acct' URI Scheme
In plain English — editorial summary, not part of the RFC
This document defines the 'acct' Uniform Resource Identifier (URI) scheme as a way to identify a user's account at a service provider, irrespective of the particular protocols that can be used to interact with the account.
Document record
- Document ID
- RFC7565
- Published
- May 2015
- Authors
- P. Saint-Andre
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8141Uniform Resource Names (URNs)Current
April 2017
- RFC 6570URI TemplateCurrent
March 2012
- RFC 5122Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)Current
February 2008
- RFC 5028A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) ServicesUpdated
October 2007
- RFC 4622Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)Obsoleted
August 2006
- RFC 4575A Session Initiation Protocol (SIP) Event Package for Conference StateCurrent
August 2006
- RFC 4415IANA Registration for Enumservice VoiceUpdated
February 2006
- RFC 4095Attaching Meaning to Solicitation Class KeywordsCurrent
May 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?