Problem Statement for Referral
draft-carpenter-referral-ps-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2011-02-23 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-carpenter-referral-ps-02.txt
Abstract
The purpose of a referral is to enable a given entity in a multiparty Internet application to pass information to another party. It enables a communication initiator to be aware of relevant information of its destination entity before launching the communication. This memo discusses the problems involved in referral scenarios.
Authors
Sheng Jiang
(jiangsheng@huawei.com)
Brian Carpenter
(brian.e.carpenter@gmail.com)
Zhen Cao
(caozhenpku@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)