Bug 325 - NASA/JSC 1 Only one set of access rights per data object
Summary: NASA/JSC 1 Only one set of access rights per data object
Status: RESOLVED CHANGE AGREED
Alias: None
Product: OAIS June 2012
Classification: Unclassified
Component: Section:Annexes (show other bugs)
Version: June 2012
Hardware: Not certain Windows
: --- Recommended change for other considerations
Assignee: David Giaretta (david@giaretta.org)
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2021-01-13 10:47 UTC by David Giaretta (david@giaretta.org)
Modified: 2024-01-30 21:55 UTC (History)
4 users (show)

See Also:
Organisation of the submitter: NASA
Disposition of the suggested change:
Category of the suggested change: Other considerations
Due date:
Explanation of the reason for the suggested change:
Access control enforcement will be greatly simplified.


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Giaretta (david@giaretta.org) 2021-01-13 10:47:21 UTC
REVIEW ITEM DISPOSITION (RID):
                    RED BOOK RID INITIATION FORM

AGENCY RID NUMBER:  NASA/JSC 1
SUBMITTING ORGANIZATION (Agency, Center): 
------------------------------------------------------------------
REVIEWER'S NAME:   Craig Biggerstaff
CODE:              
E-MAIL ADDRESS:    craig.biggerstaff@nasa.gov
TELEPHONE:         
------------------------------------------------------------------
DOCUMENT NUMBER:   CCSDS 650.0-P-2.1          Pink Book, Issue 2.1
DOCUMENT NAME:     OAIS Reference Model
DATE ISSUED:       October 2020
PAGE NUMBER:       F-1          PARAGRAPH NUMBER:  Annex F
RID SHORT TITLE:  Only one set of access rights per data object 
------------------------------------------------------------------
DESCRIPTION OF REQUESTED CHANGE:  (Use From: "..." To "..." format)

After:  "...Any restrictions which the original rights holder places 
on what the archive preserves should also be respected over time and 
adequate security measures should be put in place to ensure that."

add the following sentence:

"Note that the definition of an Information Package implies that the 
Access Rights Information for that package applies to the entire 
Content Data Object.  The delineation of data into Content Data 
Objects for archiving should take that into account."

------------------------------------------------------------------
CATEGORY OF REQUESTED CHANGE:
     Technical Fact ___    Recommended _X_    Editorial ___
NOTES:
TECHNICAL FACT:  Major technical change of sufficient magnitude as to
 render the Recommendation inaccurate and unacceptable if not
 corrected.  (Supporting analysis/rationale is essential.)
RECOMMENDED:  Change of a nature that would, if incorporated, produce
 a marked improvement in document quality and acceptance.
EDITORIAL:  Typographical or other factual error needing correction.
 (This type of change will be made without feedback to submitter.)
------------------------------------------------------------------
SUPPORTING ANALYSIS:

Access control enforcement will be greatly simplified.



------------------------------------------------------------------
DISPOSITION:
Comment 1 David Giaretta (david@giaretta.org) 2021-01-13 11:17:27 UTC
To give the full context this is the Security Annex where we look at each of the Mandatory Responsibilities:

–	Obtain sufficient control of the information provided to the level needed to ensure Long Term Preservation.
•	Sufficient control includes control of the bits, and would imply adequate security processes for personnel and systems. Security considerations for any agreements with rights holders which may be necessary should be covered by normal business processes. Any restrictions which the original rights holder places on what the archive preserves should also be respected over time and adequate security measures should be put in place to ensure that.

The change would be to append
"Note that the definition of an Information Package implies that the 
Access Rights Information for that package applies to the entire 
Content Data Object.  The delineation of data into Content Data 
Objects for archiving should take that into account."

to this.
Comment 2 David Giaretta (david@giaretta.org) 2021-01-13 11:24:43 UTC
Not all Information Packages are derived from Content Information e.g. an SIP.

It might be clear to make the following change:

From:
"Any restrictions which the original rights holder places on what the archive preserves should also be respected over time and adequate security measures should be put in place to ensure that."

To:
"Any restrictions which the original rights holder places on what the archive preserves should also be respected over time and adequate security measures should be put in place to ensure that. Note that this implies that Information Packages derived from Content Information should respect the access rights associated with that Content Information."
Comment 3 Mark Conrad (mark.conrad.iso@gmail.com) 2021-01-13 16:17:35 UTC
I agree with David's suggested change to respond to the RID.
Comment 4 Craig Biggerstaff (craig.biggerstaff@nasa.gov) 2021-01-13 19:52:54 UTC
My concern was that Information Packages could be assembled from multiple content items having a variety of access rights, and in that case one of those access rights would prevail (in effect overwriting the others' original access rights information).  In my limited understanding of OAIS terminology, I think this (assembling Information Packages from multiple Content Information) would be described as a Transformation.

Feel free to amend the text however you think best.  If the Working Group agrees that David Giaretta's proposed text covers the above scenario, I am content.
Comment 5 David Giaretta (david@giaretta.org) 2021-01-14 12:00:53 UTC
(In reply to craig.biggerstaff from comment #4)
> My concern was that Information Packages could be assembled from multiple
> content items having a variety of access rights, and in that case one of
> those access rights would prevail (in effect overwriting the others'
> original access rights information).  In my limited understanding of OAIS
> terminology, I think this (assembling Information Packages from multiple
> Content Information) would be described as a Transformation.
> 
> Feel free to amend the text however you think best.  If the Working Group
> agrees that David Giaretta's proposed text covers the above scenario, I am
> content.

A Transformation is defined by OAIS as: A Digital Migration in which there is an alteration to the Content Information or PDI of an Archival Information Package. Therefore it applies to AIPs rather than Information Packages in general.

However you make some good points. So how about:

"Any restrictions which the original rights holder places on what the archive preserves should also be respected over time and adequate security measures should be put in place no matter what preservation activities have been adopted, including Transformations. Note that this implies that Information Packages derived from Content Information should respect the access rights associated with that Content Information; where Information from multiple Content Information Objects have been combined then the archive should be able to justify the access rights to be applied, for example taking a union of the restrictions in order to respect the restrictions placed on all the components."
Comment 6 Craig Biggerstaff (craig.biggerstaff@nasa.gov) 2021-01-14 15:31:49 UTC
I like that.  It captures the concern exactly.  Thank you.
Comment 7 John Garrett (garrett@his.com) 2021-01-16 19:25:49 UTC
Just a couple tweaks, I would eliminate "Note that this implies" since it doesn't necessarily imply that for me. So I just said what to do with derived IPs.

Also eliminated the "for example ... a union of ...".  I think it gives a wrong impression that a union of access rights is the most appropriate thing to do when in many cases it isn't.  Info from individual may be restricted, but when combined into statistics may not be.  Intel may be restricted at a certain level, but when combined may result in even more classified info.

So overall I would suggest:

"•	Sufficient control includes control of the bits, and would imply adequate security processes for personnel and systems. Security considerations for any agreements with rights holders which may be necessary should be covered by normal business processes. Any restrictions which the original rights holder places on what the archive preserves should also be respected over time and adequate security measures should be put in place no matter what preservation activities have been adopted, including Transformations. Any Information Packages derived from Content Information should respect the access rights associated with that Content Information; where Information from multiple Content Information Objects have been combined then the archive should be able to justify the access rights to be applied."
Comment 8 David Giaretta (david@giaretta.org) 2021-01-17 13:08:11 UTC
(In reply to John Garrett from comment #7)
> Just a couple tweaks, I would eliminate "Note that this implies" since it
> doesn't necessarily imply that for me. So I just said what to do with
> derived IPs.
> 
> Also eliminated the "for example ... a union of ...".  I think it gives a
> wrong impression that a union of access rights is the most appropriate thing
> to do when in many cases it isn't.  Info from individual may be restricted,
> but when combined into statistics may not be.  Intel may be restricted at a
> certain level, but when combined may result in even more classified info.
> 
> So overall I would suggest:
> 
> "•    Sufficient control includes control of the bits, and would imply
> adequate
> security processes for personnel and systems. Security considerations for
> any agreements with rights holders which may be necessary should be covered
> by normal business processes. Any restrictions which the original rights
> holder places on what the archive preserves should also be respected over
> time and adequate security measures should be put in place no matter what
> preservation activities have been adopted, including Transformations. Any
> Information Packages derived from Content Information should respect the
> access rights associated with that Content Information; where Information
> from multiple Content Information Objects have been combined then the
> archive should be able to justify the access rights to be applied."

OK for me
Comment 9 Mark Conrad (mark.conrad.iso@gmail.com) 2021-03-08 16:24:36 UTC
Ok for me
Comment 10 David Giaretta (david@giaretta.org) 2021-03-30 10:28:07 UTC
MOIMS-DAI20210323 agreed http://review.oais.info/show_bug.cgi?id=325#c7
Comment 11 David Giaretta (david@giaretta.org) 2023-09-28 12:05:33 UTC
REOPENED for ISO review - had been accepted after CESG changes made so not in ISO submission.
Comment 12 David Giaretta (david@giaretta.org) 2024-01-30 21:55:40 UTC
CCSDS MOIMS-DAI 20240130: Agreed to make the change.