Re: [dtn] summary of work items

["Burleigh, Scott C (312B)" <[e-mail]>]

Hi, Marc and Brian.  I agree this is a very good summary.  I will offer a couple of proposed tweaks, marked in <> brackets in-line below.

Scott

From: dtn [mailto:[e-mail]] On Behalf Of Marc Blanchet
Sent: Thursday, December 11, 2014 6:33 AM
To: [e-mail]
Subject: [dtn] summary of work items

Hello,
 Brian and I have worked on a summary of the work items that were discussed during our interim meeting last week. We hope this reflects our discussion. We would like to make sure this summary is appropriate before sending it to our AD. So please review and confirm.  The intent of this email is _not_ to discuss each work items, but to review if the list is ok.

Regards, Marc&Brian

=====================
DTN Work Items

Phase 1

  1.  Header Integrity and Immutability  <if "payload integrity" is included in this item then maybe the item title should be just "End-to-end Integrity" and item ii should be omitted?>

     *   Status: DTN WG work item

     *   Considerations:

        *   payload integrity

        *   e2e integrity

        *   immutability of primary block

        *   remove dictionary
<I suggest that we add "bundle size" here, removing it from Phase 2.  I don't think bundle size is in fact an issue, but if it is an issue then it is fundamental and we need to address it at the beginning.  Will has linked it to the design of the integrity mechanisms, so I think this work item is the right place for it.>

  1.  Improved Security

     *   Status: DTN WG work item

     *   Considerations:

        *   Determine if SBSP is starting point

        *   Identify dependency on header changes driven by other work items  <maybe just "Identify dependency on header changes"?  Because the security improvements may themselves be the drivers for some of those changes.>

  1.  Addressing

     *   Status: DTN WG work item

     *   Considerations:

        *   develop requirements on addressing from use cases
<I suggest that we consider "constrained environments" here rather than in item 8.  So far in our conversations, I think constrained environments have had more impact on addressing than on any other topics.>

        *   narrow scope of work

        *   Possible interim meeting

  1.  Node/Neighbor Discovery

     *   Status: DTN WG work item

     *   Considerations:

        *   Investigate MANET discovery protocol model

        *   Assess applicability of draft-irtf-dtnrg-ipnd

  1.  Static Routing

     *   Status: DTN WG work item

     *   Considerations:

        *   Assess relationship to node/neighbor discovery

  1.  Avoid Routing Loops

     *   Status: DTN WG work item
<suggested Considerations: assess applicability of draft-fall-dtnrg-schl-00>

  1.  Time and bundle expiration

     *   Status: DTN WG work item
<suggested Considerations: assess applicability of draft-irtf-dtnrg-bundle-age-block-01>

  1.  Improve Specifications such as RFC 5050

     *   Status: DTN WG work item

     *   Considerations:

        *   fix known specification bugs

        *   constrained environments  <as noted above, I suggest we relocate this topic>

        *   default operations

        *   simplify options

        *   identify issues for incompatibilities with 5050

  1.  Registry of Service Identifier

     *   Status: DTN WG work item.

Phase 2
(after phase 1 completed, potential work items below. list to be reviewed at that time)

  1.  Network Management

     *   Network monitoring only, not configuration

     *   Considerations:

        *   Potentially interface with LIME WG

        *   Move configuration to DTNRG?

  1.  Key management

  1.  Extended Class of Service

  1.  Multicast

  1.  Streaming Support

  1.  Bundle size  <as noted above, I suggest we relocate this topic>

Non Work Items

  1.  Dynamic Routing

     *   Status: suggesting DTNRG