2.1.5 Generic Referral Object (grobj)
NOTE: This charter is a snapshot of the 76th IETF Meeting in Hiroshima, Japan. It may now be out-of-date.
Last Modified: 2009-10-07
Chair(s):
Dan Wing <dwing@cisco.com>
Sheng Jiang <shengjiang@huawei.com>
Applications Area Director(s):
Lisa Dusseault <lisa.dusseault@gmail.com>
Alexey Melnikov <alexey.melnikov@isode.com>
Applications Area Advisor:
Alexey Melnikov <alexey.melnikov@isode.com>
Mailing Lists:
General Discussion:
To Subscribe:
Archive:
Description of Working Group:
The purpose of a referral is to enable a given entity in a multiparty
application to pass information to another party. Existing referrals
are IPv4 address only (with implied port number) or are IPv4 address+port.
But, with IPv6 deployments and the need for compatibility with existing
IPv4 applications, referrals will need to be more generic, providing
a richer language for IPv4 and IPv6 address referrals, and fallbacks for
when neither of these is directly applicable.
This BOF will consider a proposed Generic Referral Object (GRO) to be
used for 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 includeded. To allow proper interpretation
of referrals, a new notion of scope identifiers is introduced. GRO's
richer language helps peers avoid address translators or tunnels and to
choose a reachable path with the desired characteristics.
See draft-carpenter-behave-referral-object
The purpose of the BOF is to expose these ideas to a wider spectrum
of people including Apps Area experts and to discuss whether to
take the ideas forward in the IETF.
Goals and Milestones:
No Current Internet-Drafts
No Request For Comments
Slides
GRO: Problem Statement
Generic Referral Objects
GROJB BoF Agenda
Referrals in Mobile Networks