You may be trying to access this site from a secured browser on the server. Please enable scripts and reload this page.
Turn on more accessible mode
Turn off more accessible mode
Skip Ribbon Commands
Skip to main content
Turn off Animations
Turn on Animations
To navigate through the Ribbon, use standard browser navigation keys. To skip between groups, use Ctrl+LEFT or Ctrl+RIGHT. To jump to the first Ribbon tab use Ctrl+[. To jump to the last selected command use Ctrl+]. To activate a command, use Enter.
Browse
Tab 1 of 2.
List Tools
List
List Tools group. Tab 2 of 2.
CCSDS.org
CWE
Areas
- SEA
- MOIMS
- CSS
- SOIS
- SLS
- SIS
Management
- CESG
- CMC
- Secretariat
- SANA
Framework
My Profile
Request Login
Password Management
- Change Password
- Forgot or Expired Password
Discussions
SMWG List of Editorial Issues for Red-2
It looks like your browser does not have JavaScript enabled. Please turn on JavaScript and try again.
Site Content
Documents
Action Items
Announcements
Calendar
Links
Discussions
Issues for the Production of the SLE-SM Red-2 book
Items for the SM Concept Book
Possible Red-2 RID items
SMWG Items to be Considered for Future (post-Blue-1) Versions of SLE(CS)- Service Management
SMWG List of Editorial Issues for Red-2
SMWG Schema Issues
SMWG Service Agreement Modifications Needed
UML Models Library
Site contents
Threading
Started: 8/2/2007 10:26 PM by Barkley Erik
View Properties
SMWG: List of Editorial Issues for Red-2
Base message thread for issues that are related to the editing of Red-2 and/or are not really significant from the point of view of major issues to be solved in development of Red-2
Posted: 8/2/2007 10:31 PM by Barkley Erik
View Properties
Minor, subtle but important issue with respect to 'reuse" of parameters and applicable service agreement parameters:
In looking at the remodeled event sequencing information I came across the modulationIndex parameter definition all pointing to the same table. However, there are in fact two distinct modulationIndex parameters with respect to the service agreement (forward carrier versus return carrier). The table that defined the modulationIndex parameter for the return carrier did not call out the applicable service agreement parameters constraint. The "source" table for the data set were modulationIndex is first defined referred to the forward carrier agreement information in the service agreement section. We should double check this in other cases where the same parameter name is used in both the forward and return carrier sensing that the proper service agreement parameter is called out despite the fact that the general definition of the parameter is the same.
Show Quoted Messages