Triggers for Transport BOF (trigtran)

Thursday, March 20 at 0900-1130
================================

CHAIRS:	Carl Williams <carlw@mcsr-labs.org>
	Spencer Dawkins <spencer_dawkins@yahoo.com>

AGENDA:

- Agenda Bashing                                    10 minutes


- Issues identified in TRIGTRAN Framework draft     20 minutes
        Constraints of Minimal Architecture
        Form of Registrations
        Form of Notifications
        Allowable Responses to Notifications
        Deployment Issues
        Security


- Questions leading to a WG charter            50 minutes
        - can we agree on the list of canonical triggers?
        - is an end-to-end solution sufficient, 
                or do we really need help from the network?
        - are explicit messages required?
        - can these triggers be generated by subnetwork technologies?
        - can we agree on a list of reasonable responses?
        - who would use TRIGTRAN notifications? (OMA, SIP, etc.)?
        - who would implement a reasonable TRIGTRAN specification?


- Next Steps leading to a TRIGTRAN working group   40 minutes
        IETF? or IRTF? (some of both)?
        Volunteers?
        Documents?
        Timeline
        Land Mines



References:


Strawman TRIGTRAN framework (version 00)
http://www.ietf.org/internet-drafts/draft-dawkins-trigtran-framework-00.txt


Strawman TRIGTRAN problem Statement updated (version 01)
http://www.ietf.org/internet-drafts/draft-dawkins-trigtran-probstmt-01.txt



How to subsribe to TRIGTRAN mailing list:


The mailing list information is at 
https://www1.ietf.org/mailman/listinfo/trigtran


The mailing list archives are at 
http://www.ietf.org/mailarchive/workinggroups/trigtran
/current/maillist.html


Please followup on the TRIGTRAN mailing list, at trigtran@ietf.org.