Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
pyDTN
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
7
Issues
7
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
space-public
pyDTN
Commits
50125996
Commit
50125996
authored
Mar 24, 2019
by
Boris Pilka
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update README.md
Former-commit-id:
40d29b11
parent
04653ddf
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
11 deletions
+11
-11
README.md
README.md
+11
-11
No files found.
README.md
View file @
50125996
...
...
@@ -3,8 +3,8 @@
This is the PoC (Proof of Concept) implementation of:
*
[
Bundle Protocol Version 7
](
https://tools.ietf.org/html/draft-ietf-dtn-bpbis-12
)
*
Send/receive a bundle
*
Send bundle functionality is available via
REST
API, useful for testing
*
Schedule contact functionality is available via
REST
API, useful for integration with
[
µPCN
](
https://upcn.eu/
)
*
Send bundle functionality is available via
`REST`
API, useful for testing
*
Schedule contact functionality is available via
`REST`
API, useful for integration with
[
µPCN
](
https://upcn.eu/
)
*
[
Delay-Tolerant Networking TCP Convergence-Layer Protocol
](
https://tools.ietf.org/html/rfc7242
)
...
...
@@ -19,16 +19,16 @@ This is the PoC (Proof of Concept) implementation of:

1.
pyDTN-2 receives REST request to schedule contact: pyDTN-2.dtn available on 172.25.1.11:2002
1.
pyDTN-2 schedules contact with uPCN
, note following issues:
*
Proprietary (not part of any draft)
uPCN
config bundle is used
*
pyDTN-2 receives uPCN
IP address/port on a
[
command line
](
https://git.ifne.eu/space-public/pyDTN/blob/master/docker/docker-compose.yml#L39
)
1.
pyDTN-1 receives REST request to send a bundle to pyDTN-2
1.
pyDTN-1 sends bundle to uPCN
, note following issues:
*
pyDTN-1 receives uPCN
IP address/port on a
[
command line
](
https://git.ifne.eu/space-public/pyDTN/blob/master/docker/docker-compose.yml#L20
)
1.
`pyDTN-2`
receives
`REST`
request to schedule contact:
`pyDTN-2.dtn`
is available on
`172.25.1.11:2002`
1.
`pyDTN-2`
schedules contact with
`uPCN`
, note following issues:
*
Proprietary (not part of any draft)
`uPCN`
config bundle is used
*
`pyDTN-2`
receives
`uPCN`
's
IP address/port on a
[
command line
](
https://git.ifne.eu/space-public/pyDTN/blob/master/docker/docker-compose.yml#L39
)
1.
`pyDTN-1`
receives
`REST`
request to send a bundle to
`pyDTN-2`
1.
`pyDTN-1`
sends bundle to
`uPCN`
, note following issues:
*
`pyDTN-1`
receives
`uPCN`
's
IP address/port on a
[
command line
](
https://git.ifne.eu/space-public/pyDTN/blob/master/docker/docker-compose.yml#L20
)
*
IP address/port is then set (kind of hard-coded) in
[
ipnd/httpd.py
](
https://git.ifne.eu/space-public/pyDTN/blob/master/ipnd/httpd.py#L42
)
1.
uPCN receives a bundle from pyDTN-1 and immediately forwards it to pyDTN-2
, note following issues:
*
uPCN
currently does not store any bundles, if destination is not available, bundle is simply dropped
1.
`uPCN`
receives a bundle from
`pyDTN-1`
and immediately forwards it to
`pyDTN-2`
, note following issues:
*
`uPCN`
currently does not store any bundles, if destination is not available, bundle is simply dropped
Issues listed above will be solved as a part of %2 milestone.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment