SILC Message Flag Payloads
draft-riikonen-flags-payloads-04
Document | Type |
Expired Internet-Draft
(individual in gen area)
Expired & archived
|
|
---|---|---|---|
Author | Pekka Riikonen | ||
Last updated | 2004-06-11 (Latest revision 2003-12-03) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats | |||
Stream | WG state | (None) | |
Document shepherd | (None) | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Scott Hollenbeck | ||
IESG note | |||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo describes the data payloads associated with the SILC Message Flags, as defined in the SILC Packet Protocol specification [SILC2]. The purpose of the Message Flags is to augment the function of the Message Payload used to send both private and channel messages, by allowing the sender to tell the receiver what type of data the payload includes, and how the data should be processed. Some of the Message Flags may define additional payloads to be associated with the flag, and this memo describes these payloads.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)