• IETF67Interop

DTNRG Interop at IETF-67 (San Diego)

All dates and times and all other details are still liable to change.

Logistics

Who: See table below

When: Wednesday morning to Friday evening

What: Bundle Protocol (BP) and Licklider Transmission Protocol (LTP) interop.

Where: IETF terminal room (=> participants will have to register and pay for the IETF meeting)

Detailed scheduling will try to account for people who have to attend other IETF WG meetings during this time period. Such constraints should be determined early on in the process as soon as we have a complete list of participants.

General Rules

This is internal interop event between implementers and closely related people. Only people bringing implementations are allowed in. A joint statement may be issued in the end by all implementers. Otherwise, the results are confidential and no marketing efforts whatsoever may be drawn from these.

Participants

Equipment

The IETF terminal room suplies wired and wireless connectivity on the IETF LAN.

Everyone has to bring their own development and test kit.

Keith Scott may be able to bring a link delay emulator of some sort...

Kevin Fall may be able to bring a hub so we can watch traffic...

Hans Kruse and/or Leigh Torgerson may be able to generate delays if we get the basics working first

Can we get someone to bring a laptop with ethereal? (Is there any DTN stuff for ethereal?)...

Jöerg Ott will bring an access point for separate WLAN connectivity

We should setup a jabber room to chat and also act as our log...

Bundle Protocol Details

The baseline for the Bundle Protocol testing will be the trivial UDP convergence layer, in which each Bundle is transmitted according to the BP spec in a single datagram.

Specific goals:

• Simple bundle transmission.
• Bundle transmission with custody transfer
• Usage of different status report request flags and their proper processing.
• Each implementation should act as a sender and as a receiver.

JO: I guess we'll need to check which features the present implementations support; we don't need to get ahead ourselves for this first event.

TCP Convergence Layer Details

The TCP convergence layer will be tested as part of the bundle protocol implementation which may make exploring different failure modes and configurations more complex and difficult.

Specific goals:

• Connection setup
• Minimal parameter negotiation (need to define which ones)
• Keep-alive messaging
• Unidirectional messaging
• Bidirectional messaging
• Interim convergence layer acknowledgements
• Orderly connection teardown
• Connection abort (e.g., unplugging cable or disabling wireless interface)
• Each implementation shall operate as a connection initiator and acceptor
• Zero-length payload bundles
• Multiple segment sizes

The above will be revised and finished according to the TCP CL Internet Draft.

Basic bundle interop matrix

The idea is to fill in as much of this as we can during Wed/Thu.

There are 5 organisations involved (DTN2, ION, GATECH, JOERG and BBN) and two convergence layers (TCP & UDP). Each might interop with each in principle but proba bly not all organisations support all CLs.

As each pairwise interop succeeds (optimism:-), we can write in what's worked in the relevant cell, e.g. "TCP-ok" or whatever.

LTP Details

Goals:

• Basic1: Running a session successfully involving transfer of O(10) data segments
• Basic2: Basic1 plus delays
• Advanced1: Run a session even with the ltplib compiled to generate all errors
• Advanced2: Test LTP auth extension? (Reqiures new java code?)
• Advanced3: Test cookie extension? (Requires new java code?)