← Prev in month ← Prev in thread
Next in thread → Next in month →

Noggin Feedback for public review of cap-v1.2-au-profile-v1.0-csprd01 [SEC=UNCLASSIFIED]

From
Trott, Gregory <>
Date
2012-01-20T07:32:54+00:00
ID
Thread
Noggin Feedback for public review of cap-v1.2-au-profile-v1.0-csprd01 [SEC=UNCLASSIFIED]
UNCLASSIFIED

OASIS,

 

The feedback below is submitted on behalf of an Australian reviewer as the issues raised could potentially impact the content of the OASIS cap-v1.2-au-profile-v1.0-csprd01 document.  

 

The Reviewers details are:

 

Reviewer’s Name:   Owen Prime (Chief Technology Officer)  +61-2-9219-8803 /  

 

Reviewer‘s Organisation:  Noggin Pty Ltd  (http://www.noggin.com.au)

 

 

1) Page 12: <restriction> element: Whilst we are unsure of the timeline, the Protective Security Policy Framework (PSPF) will progressively replace the PSM and there are some changes to the classification markings used by agencies.  The use of the RFC2119 term "SHALL" in CAP-AU-STD may cause problems for some agencies in future should these changes affect them. We recommend that the new classifications be included and CAP-AU Stakeholder Group keep an eye on the progress of adoption of the PSPF.

 

Initial consideration from CAP-AU Project Manager: Agree that PSPF should replace PSM. Disposition of this issue can be cross referenced to the action agreed previously as per earlier comments passed to OASIS.

 

 

 

2) Page 23: <urgency>, <severity>, and <certainty> elements: The document states that "jurisdictions / organisations MAY need to tailor" the implementation of these elements. As these elements are enumerations in CAP v1.2, any tailoring is limited to a subset of the respective list.

 

Initial consideration from CAP-AU Project Manager: Recommend that wording of each note for <urgency>, <severity>, and <certainty> be revised to remove ambiguities.  CAP-AU Project Manager will consult with Reviewer to obtain his recommendation for consideration by OASIS.

 

 

 

3) Page 24: <effective> element, point (2): There is a typo, "<msgTyp>" should read "<msgType>".

 

Initial consideration from CAP-AU Project Manager: Agree that this edit should be corrected in the next revision of the document.

 

 

 

4) Page 31: <resource><mimeType> element, point (2): There is a typo, "<mineType>" should read "<mimeType>" 

 

Initial consideration from CAP-AU Project Manager: Agree that this edit should be corrected in the next revision of the document.

 

 

 

 

 

Greg Trott

CAP-AU Project Manager 

Australian Government Attorney-General's Department

 

 

If you have received this 
transmission in error please
notify us immediately by return e-mail and 
delete all
copies. If this e-mail or any attachments have been sent
to you 
in error, that error does not constitute waiver
of any confidentiality, 
privilege or copyright in respect
of information in the e-mail or 
attachments.
← Prev in month ← Prev in thread
Next in thread → Next in month →