Multiple group membership
draft-park-mls-multiple-groups-requirement-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Minho Park | ||
| Last updated | 2019-05-24 (Latest revision 2018-11-20) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| 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 document proposes a functional requirement of Message Level Security (MLS) which provide an efficient management for multiple groups. Although MLS defines an architecture and an abstract protocol for a secure group communication, it overlooks the need of multiple groups. This document describes a usecase of the multiple groups, and the need for an efficient multiple group membership management.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)