[Trigtran] TRIGTRAN BoF at IETF 56

"Spencer Dawkins" <sdawkins@cynetanetworks.com> Wed, 05 March 2003 22:50 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03962 for <trigtran-archive@odin.ietf.org>; Wed, 5 Mar 2003 17:50:28 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h25N1Ch31311 for trigtran-archive@odin.ietf.org; Wed, 5 Mar 2003 18:01:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25N1CO31308 for <trigtran-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 18:01:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03926 for <trigtran-web-archive@ietf.org>; Wed, 5 Mar 2003 17:49:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25N15O31300; Wed, 5 Mar 2003 18:01:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25N0hO31222 for <trigtran@optimus.ietf.org>; Wed, 5 Mar 2003 18:00:43 -0500
Received: from MAIL.cynetanetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03915 for <trigtran@ietf.org>; Wed, 5 Mar 2003 17:49:28 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Wed, 05 Mar 2003 16:51:31 -0600
Message-ID: <9255B6CD76A88943A3062F7D4E6432F55C3771@mail.cynetanetworks.com>
Thread-Topic: TRIGTRAN BoF at IETF 56
Thread-Index: AcLjacPSNLtTkmLIRYePel8xDFdIlA==
From: Spencer Dawkins <sdawkins@cynetanetworks.com>
To: "Trigtran Mailing List (E-mail)" <trigtran@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h25N0iO31223
Subject: [Trigtran] TRIGTRAN BoF at IETF 56
Sender: trigtran-admin@ietf.org
Errors-To: trigtran-admin@ietf.org
X-BeenThere: trigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>, <mailto:trigtran-request@ietf.org?subject=unsubscribe>
List-Id: Triggers for Transport <trigtran.ietf.org>
List-Post: <mailto:trigtran@ietf.org>
List-Help: <mailto:trigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>, <mailto:trigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Carl and I will be hosting a second TRIGTRAN BoF at IETF 56.

The working copy of the BoF Agenda is available below (and is 
being sent to agenda@ietf.org).

We will present issues discussed in the Framework draft, available at 
http://www.ietf.org/internet-drafts/draft-dawkins-trigtran-framework-00.txt.

This BoF is intended to lead to the formation of a TRIGTRAN working group,
so most of our time together will be dedicated to answering a series of
questions to figure out if we're doing the right thing.

Please plan to attend and be opinionated.

Spencer, for Spencer and Carl

p.s. The Problem Statement draft will be available at 
http://www.ietf.org/internet-drafts/draft-dawkins-trigtran-probstmt-01.txt,
as soon as it's announced. The only changes we've made were updates to
reflect constraints in the minimal architecture model that we adopted
at IETF 55.

p.p.s. The meeting minutes from the first BOF are available at
http://www.ietf.org/proceedings/02nov/239.htm

p.p.p.s. My e-mail address is changing to spencer_dawkins@yahoo.com,
effective immediately.

----------- Agenda ------------------------

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
	Preliminary Security Assessment

- Questions leading to a WG charter					50 minutes
	- is an end-to-end solution sufficient, 
		or do we really need help from the network?
	- are explicit messages required?
	- can we agree on the list of canonical triggers?
	- 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
	Volunteers
	Documents
	Timeline
	Land Mines
_______________________________________________
Trigtran mailing list
Trigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/trigtran