DTNRG
Summary Minutes from IETF69

Intro & agenda; no changes
Document status:
	RFC 4838 issued
	BP spec done moving to IESG (real soon now)
	LTP in IRSG review
	Security docs:
		overview needs rev;
		bsp in work

	DTRNG has authored 50% of all IRTF I-Ds
	Encapsulation & prev hop drafts just refreshed
	TCP CL: Mike/Joerg posted supplemented earlier doc; should progress soonish editorial work to do
	Others:   sdnv doc - no objection to adopting that
	          key mgmt - in a mo
		  uni-CL - not ready ; update later
		  prophet - might need resubmission (not sure) - might be ready
		  multicast & re-tx docs -   others discussed today  cbhe - to be revived
	we need to organise a review of all these nearly done docs

News;  LTP/Saratoga to be presented at TSV area (see TSV area minutes for more)
Stephen Farrell - Key management draft already reported in Dublin
	km - sets out requirements; call for volunteers
	km - details

	related item: change to counter mode for crypto to ensure size(cleartext) == size(corresponding cyphertext)


Mike Demmer - DTN2 status; 2.4 release last week
Routing - DTLSR overiew, paper at SIGCOMM/NSDR;
prophet; flood router

Applications - send/rcv/ping; traceroute app; tunnel app (TCP/UDP over bundles);
dtnperf  Misc features - multi endpoint; dtnsim; neighbourhood discovery (bonjour in Apple)
Coming - security; swig for scripting (with Dirk); pub-sub API

Broken/not-done things: proactive fragmentation; flow control

Ref implementation
	Timeframe - 2.4 out; 2.4.1 patch soon; 2.5 in autumn incl. security

Wes Eddy - Checksum draft (on cisco site now, missed cutoff) [since posted to dtn-interest and as ID]
     Rationale for checksums
	Why not use BSP framework? (discussion)
	Long term proposal - add optional fields
	Q&A:   Why not use BSP security?
		You can. Use new ciphersuite/fixed-key/new-doc
		Application vs. BP-layer integrity provision
		Canonicalisation needed? Re-use mutable stuff where possible
		Mandatory/optional; integrity as part of security or not
		Do it as a ciphersuite? Agreed.

Tom Henderson - Describing ns-3 simulation (Univ. Wash. work/Boeing)
	Q&A:   Dirk - similar emulation extensions as for ns-2 planned?  Sort-of
	Kevin - persistent storage; link status robustness; high delay & directional antennas? could be done?
	A: Maybe in future, not yet.
	Mike D - DTN2 vs. ns-3 feature location? A: YMMV
	Stephen - release dates? real soon now; alpha by year-end-ish

Joerg Ott  Small simulation tool
	"ONE" for opportunistic networks
	Based on synthetic & trace-based mobility models
	Demo (incl viz) based on 100 nodes in Helsinki
	Used to evaluate different routing protocols to figure how motion affects them  Alpha version available

Lloyd Wood  - Saratoga changes
	Saratoga basics as in Dublin Planning to fly bundles/saratoga on UK DMC later this year
	Q&A:  Kevin - not sure who'll get 1st bundle in space (vs Colorado group)
	Kevin - interesting layering questions (answers would need thought)
	Kevin - beacons - would that be replaced by neighbour discovery?
	(next pres) not sure
	Kevin - pull (pub-sub etc) file ops might be useful outside this layer as well
	discussion about where bit-level reliablity is and if its fundamental

Jim Wylie - Neighbour/node discovery
	Problem statement (tends to be done in various ways at various layers) Generic/secure/EID-independent/re-usable/flexible/   scheme needed
	Proposal: like HELO from OSPF (CL independent?)
	
	Not a way to route packets; just one step in that process
	Terms: neighbour = same CL pitcher/catcher - both and you're a neighbour
	The proposal
	Q&A Stephen - what's a domain?
	A: a general system, e.g. "space"
	Kevin - what about other protocols, e.g. nhdp from manet? worth a look & saying how this differs
	Mike D - this replaces CL-specific discovery, but some CLs have/need that so why replace it?

Wrap  - Next meeting: probably Phili/IETF-71  Otherwise: maybe end-07/early-08  Upcoming publication venues/workshops (various)