RFC 5361: A Document Format for Requesting Consent
In plain English — editorial summary, not part of the RFC
This document defines an Extensible Markup Language (XML) format for a permission document used to request consent. A permission document written in this format is used by a relay to request a specific recipient permission to perform a particular routing translation. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5361
- Published
- October 2008
- Authors
- G. Camarillo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5025Presence Authorization RulesCurrent
December 2007
- RFC 3994Indication of Message Composition for Instant MessagingCurrent
February 2005
- RFC 3858An Extensible Markup Language (XML) Based Format for Watcher InformationCurrent
August 2004
- RFC 5277NETCONF Event NotificationsCurrent
July 2008
- RFC 4744Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)Updated
December 2006
- RFC 4743Using NETCONF over the Simple Object Access Protocol (SOAP)Updated
December 2006
- RFC 4741NETCONF Configuration ProtocolObsoleted
December 2006
- RFC 6120Extensible Messaging and Presence Protocol (XMPP): CoreUpdated
March 2011
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?