[Sis-dtn] Level of granularity in PICS

[Dr. Keith L Scott]

So I’m trying to clean up and have gotten to the PICS section.  Felix had a question about the level of granularity we need.  I’m leaning towards something like:

An entry per CLA (Optional to implement but if you DO implement that CLA, do it this way).

One entry per service (register, deregister, change, send, cancel, …).  Must implement this service.

Something about bundle format (referencing 9171)

Then there’s section 5 of RFC9171.  We COULD try to get away with a blanket statement saying that CCSDS implementation should implement all of the procedures in section 5, OR we could have entries for essentially each subsection of section 5 in RFC9171 (Bundle Transmission, Bundle Dispatching, Bundle Forwarding, …).  I suppose the “advantage” of the latter would be if an implementation wanted to deviate, it would be more ‘contained’ in the PICS.

Something about admin record processing (RFC9171 section 6)

========

Thoughts on the above, especially what to do about section 5 in RFC9171?

                                --keith

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sis-dtn/attachments/20220712/0bef86e6/attachment.htm>