A Triggered Interface

Document Type Expired Internet-Draft (individual)
Author Scott Corson 
Last updated 2002-05-09
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized 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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Layer 2 interfaces fundamentally operate as either broadcast or point-to-point. From these primitives, additional layer 3 interface constructs such as non-broadcast multiple access and point-to- multipoint are created as necessary. This approach has served the wired Internet well. However this memo argues that a third type of layer 2 interface is necessary to seamlessly extend IP over dynamic networks, principally wireless. This interface, here termed a 'triggered' interface, combines traditional broadcast interface addressing semantics (i.e. support for unicast, multicast and broadcast link layer addresses) with layer 2 trigger support for the dynamic creation of peer-to-peer interface associations within an otherwise broadcast interface. Its intended domain of applicability covers cellular, WLAN, MANET, etc; in short all currently envisioned forms of dynamic wireless networking.


Scott Corson (corson@flarion.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)