[Moims-sc] HTTP/XML Binding BB Agency review conditions

[Churlaud Olivier]

Dear WG members,

The following conditions have been raised by CESG before launching the agency review (see below).

We said we would do a full interoperability test, so (1) is OK.
For (2), it would be great that ESA, as book captain, takes each condition as a RID and either takes the change into account or justifies why we would like not to comply. The goal would be to discuss those changes during the in-person meetings in Matera.

We'll talk about it next Monday, during the monthly telecon.

Regards,
Olivier

Raised conditions:

  1.  Planning a full interoperability testing activity for the BB
  2.  Doing the following changes in the text:

  *   [Suggestion] General suggestion (perhaps something for CCSDS to consider more in general).  This will be something of an "upgrade" from the previous CCSDS 524.3-B-1 (June 2018).  As such, I think it will be helpful to established implementations to indicate what is needed for moving to the what will be CCSDS 524.3-B-2.  For example, for this recommendation, I think the guidance could be something like;
a.    Header Parsing & Emitting: Update the header generation module to reflect X-MAL-Version-Number: 2 and run string fields through percent-encoding routines.
b.    Schema & Namespace Refresh: Regenerate XML schemas using major version 2 target namespaces (urn:ccsds:schema:mo:malxml:2:...) and update XML serialization models for explicit <Body> wrapping.
c.    Data Type Formatting: Re-align precision formatting for FineTime types to strictly support up to 9 decimal places.
  *   Conditions:
1)    Minor formatting:
a.    The title page (Page 2) states July 2026.
b.    The Authority page (Page 3) lists May 2026 for Issue 1.1 and June 2026 in the bottom running header.
c.    Suggest usingt June 2026 (or other date) consistently through the documen
2)    Change FROM:  "The MAL header field 'Supplements' shall be assigned to zero or more HTTP header fields, each with name 'X-MAL-Supplement' " TO: The MAL header field(s) 'Supplement' shall be assigned to zero or more HTTP header fields, each with name 'X-MAL-Supplement' ";  Rationale: X-MAL-Supplement is stated a single field which can be repeated - the field name is not defined as plural.
3)    Section 3.6.2.3 please check the statement "The version number '2' shall be added to the SANA registry 'MAL HTTP Binding Version Number' and shall refer to the Mission Operations HTTP Transport and XML Encoding document CCSDS 524.3-B-1."  Presumably this will be CCSDS 524.3-B-2, so this should probably not say "CCSDS 524.3-B-1"?
4)    Section B1.3.3 Please supply proper reference number for text that reads "...provide authentication information (reference)...
5)    Minor: WG call as to whether to fix or not: TOC, list of Figure lists Figure 4-1, and Figure 4-2 as being on pp B-3 and B-4 which is correct, but technically these would now be Figure B-1 and B-2 respectively.
6)    Page 2-5: how are items g) and h) different Interaction Patterns/Interaction Stages? They both say "PUBSUB - NOTIFY (broker to consumer)".  Assume this is a duplicate line and delete or was there suppose to be some other semantic indication here?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-sc/attachments/20261001/73d851a8/attachment.htm>