Identifier Management for I2RS Protocol
draft-chen-i2rs-identifier-management-00
| Document | Type |
Expired Internet-Draft
(i2rs WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ran Chen , Frank Feng | ||
| Last updated | 2015-10-14 (Latest revision 2015-03-22) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Candidate for WG Adoption | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
An I2RS Agent may communicate with multiple clients. Two (or more) client may attempt to manipulate the same piece of data on the I2RS Agent. In order to solve this collision, the proposal is to have a simple priority associated with each I2RS Client. In addition, if the hold timer for an I2RS session expires, the I2RS Agent should delete the I2RS data associated with the I2RS Client. In order to delete the related I2RS data correctly, it is important to identify the client on the I2RS Agent. This document describes how to deploy identifier and priority associated with each I2RS Client based on [I-D.ietf-i2rs-architecture].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)