[cssm] Notes from FRM, FRIN, SACP, etc. splinter session on 240716

[Barkley, Erik J (US 3970)]

All,

Thank you for the productive meeting. Here are the notes I captured from our splinter session tomorrow.  Corrections appreciated.  I have a sent out a proposal for a follow-up session in September.

Best regards,
-Erik

--notes from splinter session--

  1.  Looked at the xml schema for the aperture FR and noted that FRIN was optional and frNickname required

     *   Participants in splinter session wondered if this should in fact be the opposite way around

  1.  Also noted that the FRIN is defined as a string but we believe the FRM book defines this as an integer
  2.  Clarified that the FRIN resides at the level of the FR, and not the  individual parameters of the FR
  3.  Discussed  the approach whereby a nickname is associated with a FRIN that is assigned to allow FRs (across the various strata) that belong to particular carrier profile to be logically associated

     *   For example, a nickname of something like "BEPI-X-Fwd-HR" (for x-band high-rate forward carrier) has a FRIN=1, which is assigned to the Ccsds401SpaceLinkCarrierXmit, RntXMit, etc. FRs belonging to this forward carrier profile

        *   Data Transfer Services, in the return direction, would need some "additive" FRINs or other such consideration
        *   Aperture stratum will also need some special consideration

     *   E. Barkley to take an action to sketch this more fully, especially in terms of information exchanged between user and provider

        *   Noted that this is in an overall context of identifying what the service user provides (in terms of naming, instance numbers), what the service user needs to do (with the naming, FRINs) , and how this relates to initializing and use MD-CSTS instances

     *   Noted that it needs to be made clear that the FRIN is not bound to equipment instances, but rather service/configuration profile instances

  1.  C. Haddow updated the UML diagram to properly indicate the cardinalities in the proto configuration profile UML diagram
  2.  ModResParm definition still pending further discussion
  3.  Agreed to have another splinter session in September


-----Original Appointment-----
From: Barkley, Erik J (US 3970)
Sent: Tuesday, July 2, 2024 9:24
To: Barkley, Erik J (US 3970); Colin Haddow; Marcin. Gnat at dlr. de
Cc: CCSDS Service Mgmt; Holger Dreihahn; Eddy, Wesley M. (GSFC-580.0)[MTI SYSTEMS, INC.]; Martin Unal; hugh.kelliher at spaceconnexions.com; Shames, Peter M (US 312B)
Subject: FRM, FRIN, SACP, etc. splinter session
When: Tuesday, July 16, 2024 7:00-8:30 (UTC-08:00) Pacific Time (US & Canada).
Where: Microsoft Teams Meeting

Double check updated UML model re ModResParm and FRINs vs FrNickName, etc.  finalize approach to enable CDE publication.
________________________________________________________________________________
Microsoft Teams Need help?<https://aka.ms/JoinTeamsMeeting?omkt=en-US>
Join the meeting now<https://teams.microsoft.com/l/meetup-join/19%3ameeting_ZjY0ODBjYjgtYzg5ZC00OWM1LWI1Y2EtYWJkNjNjNzY1Y2E1%40thread.v2/0?context=%7b%22Tid%22%3a%22545921e0-10ef-4398-8713-9832ac563dad%22%2c%22Oid%22%3a%2267d795cb-b5e4-4807-ab2d-6277bdc0b96f%22%7d>
Meeting ID: 259 556 640 71
Passcode: cBntg9
________________________________
Dial in by phone
+1 323-813-7400,,870968956#<tel:+13238137400,,870968956> United States, Los Angeles
Find a local number<https://dialin.teams.microsoft.com/050d5f53-1121-4c8a-8fed-036dd963e1d4?id=870968956>
Phone conference ID: 870 968 956#
For organizers: Meeting options<https://teams.microsoft.com/meetingOptions/?organizerId=67d795cb-b5e4-4807-ab2d-6277bdc0b96f&tenantId=545921e0-10ef-4398-8713-9832ac563dad&threadId=19_meeting_ZjY0ODBjYjgtYzg5ZC00OWM1LWI1Y2EtYWJkNjNjNzY1Y2E1@thread.v2&messageId=0&language=en-US> | Reset dial-in PIN<https://dialin.teams.microsoft.com/usp/pstnconferencing>
________________________________________________________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20240716/d66a0ba5/attachment-0001.htm>