A Generic Referral Object for Internet Entities
draft-carpenter-behave-referral-object-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2009-10-19 | ||
| 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-behave-referral-object-01.txt
Abstract
The purpose of a referral is to enable a given entity in a multiparty application to pass information to another party. This memo specifies a Generic Referral Object (GRO) to be used in the context of referrals. The proposed object is compact and is application- independent. Both IPv4 and IPv6 schemes are supported, as well as upper layer identifiers. Additional information to characterise an enclosed reference is also described. To allow proper interpretation of referrals, a new notion of scope identifiers is introduced.
Authors
Mohamed Boucadair
(mohamed.boucadair@orange-ftgroup.com)
Brian Carpenter
(brian.e.carpenter@gmail.com)
Joel Halpern
(jhalpern@redback.com)
Sheng Jiang
(shengjiang@huawei.com)
Keith Moore
(moore@network-heretics.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)