A Generic Referral Object for Internet Entities
draft-carpenter-behave-referral-object-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Mohamed Boucadair , Brian E. Carpenter , Joel M. Halpern , Sheng Jiang , Keith Moore | ||
Last updated | 2009-10-19 | ||
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
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
Brian E. Carpenter
Joel M. Halpern
Sheng Jiang
Keith Moore
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)