Re: RE: AD request / L2 Triggers Chapter Statement

L2 Triggers BOF (l2tr)

July 2002
================================

CHAIRS:	 
		

o DESCRIPTION OF THE BOF:
  =======================


The purpose of L2 Triggers work is to develop layer 2 service specifications for wireless links.  Service interactions between the IP layer and the link layer will be identified and defined precisely. The work may involve the definition of a protocol to carry the interaction occurring at layer 2 entities to where L3 interface exists. The work will concentrate on the definition of service interactions from layer 2 towards layer 3, aka triggers.


The ability to quickly and efficiently determine the existence (or non-existence) of a link is needed most commonly as a consequence of 
movement-induced changes in network topology.  Mobile handoff, 
whether in cellular or WLAN contexts, generally requires that the 
entire process complete within 10's of milliseconds is seamless 
voice service is to be maintained.  This requires very fast 
detection of changes in link status.  Since a link layer best 
knows its current link status it is natural to use L2 triggers for this purpose.

While the link status for L3 handover protocols is expected to be the most popular use of L2 triggers, there are other areas or protocols that may benefit from L2 events to be triggered to layer 3, e.g. IP Paging protocol. 

The work will concentrate on identifying the triggers needed by IP layer such as the link status. For each trigger it is necessary to identify the parameters to be passed. It is also important to identify the best formalism to define these parameters. The use of API languages such as C, Java will be considered. Another aspect of formalism is whether or not callbacks should be used or is it preferable to define the triggers in the form of operating system primitives.

The technical problems to be solved include:


 -  generic triggers and triggers specific to different layer 3 protocols such as handover, paging, MANET routing, etc.
-  L2 trigger transport protocol.
-  Triggers specific to each link such as cellular, 802.11, HIPERLAN1, HYPERLAN2, Bluetooth, future technologies such as Flash OFDM.


 -  The work may optionally extend to the coordination for the definition of Layer 2 trigger transport protocol for the links that do not support it with IEEE, Bluetooth, PPs and other organizations. L2 trigger transport protocol must use IP transport and may be version dependent.

The work on L2 triggers needs some amount of collaboration and synchronization with MobileIP WG and MANET WG and IP Paging BOF.
 


o The BOF's goals are:
  ===================


- Show why L2 triggers need to be defined.


- Assess interest in forming a Working Group on L2 triggers.


- Get feedback on the problem statement, which could be used as the
  basis for a Working Group Charter. The discussion of the problem
  statement on the mailing list is recommended prior to the BOF. The BOF
  will be used to form a working group.


- Reach consensus on the terminology to be used for L2 triggers.
  A discussion on terminology on the mailing list is recommended to  
  speed up the process of reaching consensus.


- Outline a number of requirements that must or should be met by the
  solutions for supporting a L2 trigger transport protocol. 

- Come up with an architecture document for L2 trigger transport protocol.  



- Outline any security issues.  



o L2TR BOF AGENDA (54th IETF Yokohama)
  ========================================


- Introduction and agenda bashing 5 min


- TBD
  
- General discussion and opinions on moving forward - All 20 min



o DELIVERABLES
  ============


- Terminology, Problem Scope: July 02

- L2 Trigger APIs : during 03
- Requirements and Framework: December 02


- L2 Trigger Transport Protocols : during 03




o MAILING LIST:
  =============


  [email protected]


  Subscription instructions can be found at ietf.org.