Link-layer Triggers Protocol
draft-yegin-l2-triggers-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Alper E. Yegin | ||
Last updated | 2003-06-10 | ||
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
Wireless and mobile hosts are subject to changing their point of attachment from one access network to another. These changes result in link-layer events such as link up and link down. Information on these events can be conveyed to interested parties in the form of link-layer triggers. Primary consumers of this information are the modules implementing mobility related network-layer protocols. When provider and consumer of this information are co-located on the same IP node, required communication can take place via internal mechanisms. But when they are separate, as in the case of networks using wired-to-wireless bridges, a transport mechanism is needed to convey link-layer triggers. This draft defines a UDP based client- server protocol for transporting link-layer triggers between two IP nodes.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)