1 / 11

DTN Arch Doc Updates IETF63 – 02-Aug-05

DTN Arch Doc Updates IETF63 – 02-Aug-05. Delay Tolerant Networking Research Group Kevin Fall ( kfall@intel.com ) http://www.dtnrg.org. Concept of Region. ‘Regions’ – groupings of related nodes originated from gateway/nodes concept related fairly closely to topology

eddy
Download Presentation

DTN Arch Doc Updates IETF63 – 02-Aug-05

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DTN Arch Doc UpdatesIETF63 – 02-Aug-05 Delay Tolerant Networking Research Group Kevin Fall (kfall@intel.com) http://www.dtnrg.org

  2. Concept of Region • ‘Regions’ – groupings of related nodes • originated from gateway/nodes concept • related fairly closely to topology • identified endpoints by {region, admin} • generalized to be non-topologically related • Eventually realized it is a namespace… • so just adopt that more formally • IETF had worked this already ~ URIs

  3. Nodes, EIDs, Names • Nodes are engines running the DTN protocols • a node may be a ‘member’ of an EID • all nodes have one (or more) <unicast> EIDs • (MEI dropped, at least for now) • EIDs as URIs more formalized • q: what scheme names to use? • a1: use IANA specified ones? • a2: use ‘dtn-prefix’ ones?

  4. Nodes/EIDs 3 Node: C 4 Bundle Protocol Agent Admin Element 2 B Bundle Protocol Agent CLA X CLA Y CLA Z E A

  5. Custody Transfer • Are source and sink nodes custodians • if source isn’t then need ‘none’ concept • Can you take custody even if not asked for • Required vs requested • Is CX really a reliable service? • What happens across diodes? • ‘I tried really hard, but I don’t know message’?

  6. Multicast / Anycast / Broadcast • There is desire to do multicast in DTNs • generalized arch doc to not prohibit this • same with bundle protocol doc • (custody transfer still limited to unicast) • Anycast service also being discussed • arch doc does not appear to prohibit this anyhow • Will discuss this a bit more later…

  7. Priorities • Class of service indicators was vague as to whether priorities were source-specific or more global • also, arch doc discussed specific scheduling priority relationship between high and normal priority bundles • Priority indicators now relative to source • Handling of expedited less normative • leaves scheduling open in arch doc

  8. API • Provision for chunks of message units, rather than word ‘atomic’ • understanding that multiple API calls may be required to convey a bundle data to application • at-most-once delivery semantics supported at destination • Terminology: (app) bindings -> registrations • confusion wrt ‘late binding’ in delivery

  9. Reports and Signals • Bundle status reports (BSRs) • sent to ‘report-to’ EID • these deliver information such as: • bundle arrived/discarded/forwarded • custody transfer completed • arrived at destination (return-receipt) • Signals • at present, for custody transfer, sent to current custodian • no real multicast custody transfer concept yet

  10. Security • Most security issues moved to new doc • Suggested ‘should’ v optional ‘may’ • Security policy routers • topology elements that might check e2e credential/auth information • Concept of DTN-SEC overlay atop the DTN overlay • maybe only some dtn nodes in a topology implement/enforce the security policies

  11. Moving forward… • Arch document is “complete” • we think/hope (multicast is new, though) • Would like to move this forward as info-RFC • multicast area is still a bit weak • Looking for your suggestions –now- • dtn-interest@mailman.dtnrg.org • http://www.dtnrg.org

More Related