Re: [dtn-interest] BP-Tables

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

Alan, I certainly agree about the need for standardization of service identifiers.  FWIW, I believe CCSDS is already working on standardizing ipn-scheme service numbers through IANA.

I'm less clear on your illustration, though.  What you're describing sounds to me more like QoS than the sort of thing I usually think of a firewall supporting.  What's the argument for performing this function in bptables rather than in, say, routing?

Scott

From: Hylton, Alan G. (GRC-RHN0) [mailto:[e-mail]]
Sent: Monday, April 23, 2012 8:58 AM
To: Burleigh, Scott C (313B); Ivancic, William D. (GRC-RHN0); [e-mail]
Subject: RE: BP-Tables

Howdy,

I think that this gets at a need for standardization of services.

Also, as an illustration, 3.3 might listen to 4.whatever, and 3.4 might listen to 5.whatever. Say you want to assure 4 that 1GB is set aside and 5 gets 2GB when receiving data. Part of the need for BP Tables is to have resource management in a general network setting. This guarantees that several science missions attached to a non-earth hub (a future TDRSS might be an axle between several hub-n-spokes) do not fight each other.

Alan

From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]]<mailto:[mailto:[e-mail]]> On Behalf Of Burleigh, Scott C (313B)
Sent: Monday, April 23, 2012 11:47 AM
To: Ivancic, William D. (GRC-RHN0); [e-mail]<mailto:[e-mail]>
Subject: Re: [dtn-interest] BP-Tables

Will, is it really important to manage service/application separate from endpoint ID (which is what I think you are saying when you say URI)?  I can see why you need to be able to identify the service/application that characterizes a bundle, but I think you're okay so long as you can always trivially infer service/application from the EID.  Certainly that's already easy to do if you're using "ipn"-scheme EIDs, according to the formal definition of the scheme, but it ought to be easy to tweak the "dtn" scheme definition for this purpose as well if necessary.

Scott

From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]]<mailto:[mailto:[e-mail]]> On Behalf Of Ivancic, William D. (GRC-RHN0)
Sent: Monday, April 23, 2012 8:02 AM
To: [e-mail]<mailto:[e-mail]>
Subject: [dtn-interest] BP-Tables

A small team at NASA Glenn Research Center is looking at implementing the equivalent of IP-Tables for Store-Carry-and-Forward  (Disconnected) Networking

The following are some rough notes from our kickoff brainstorming session.  Anyone who has some ideas on what they might like to see, we would love to hear from you.

We plan to put together an internet draft document some of our thoughts.

A couple of things that sort of stood out:

*  We probably need something like ICMP (BCMP) to return status (with every node listening for this service
* It really would be nice to have services/applications separate from URI
* A more consistant/uniform naming scheme would be very useful
* It would be useful to be able to filer on something like organization (gets into a lot of mixing of Security/keys with identity verification)



Filtering on:
Size
Source URI
Destination URI
Lifetime (TTL) (limit acceptance of bundle based on time).
Hop Count (???)
Service (application == IP port) (how to determine???)

Should service be separate from URI?  (not currently possible in RFC 5050)
Key to deployment is Identity-based, not address-based - So do we need PIB to implement?
In RFC5050 - there is no addressing.  IP-tables are address-based.
Allocate resources (size, etc.) by URI.
Bundling needs the equivalent of IP-ICMP. (Bundle Control Message Protocol?)
IP-Tables can filter on all fields, BP-Tables (should it also do equivalent?)
BP-Tables may help manage resource allocation for quality of service (50% "bulk" bundles, 50% "scheduled service" for example).


ID BP-Tables
1.   Intro
o  Why BP-Tables
2.   IP-Tables
o  What does IP-tables do
3.   BP-Tables
o  What is different
o  What is similar
o  What it should do
o  What it can do
4.   Items of interest
o  URI vs. identity
o  URI vs. application/service
o  How do we identify application/service
5.   ICMP -> BCMP
o  Status replies
6.   Network management and BP-Tables
7.   Security Section
o  BAB, PIB, and PCB key distribution

- Will