References

Assumptions


IssueNotesSign-off
1


Issues & Decisions


Issue

Notes

Decision
1Request the list of all the operation aside from CRUD

CC Csaba Kocsis To revert


2output as uri-FDN/alternate id may be reported back as a cm handle id. 

Kolawole Adeolokun to revert. Discuss extra cost with Peter T. (Current error sci wording are ambiguous)  - This is a legacy, and moving away from it soon


Requirements

Full Requirement from Study


Requirement

Additional Information

Sign-Off

1Update existing single sync cm handle APIs (CPS-E-05) to support alternate id (containing uri-FDNs).
  • NCMP existing single sync cm handle APIs shall be able to receive a request with md5-hash as a cm handle id (“As is”).
  • NCMP existing single sync cm handle APIs shall be able to receive a request with uri-FDN/alternate id as a cm handle id.


Functional


Interface

Requirement

Additional Information

Sign-off
1CPS-E-05

Update existing single sync cm handle APIs to support alternate id 


Update all the CRUD operations.

 Csaba Kocsis, All CPS 

2CPS-E-05

NCMP is to be able to find the correct CM Handles based on the 'exact match'

Registration of managed element should have 'the same' match. 

 Csaba Kocsis, All CPS 

Error Handling


Error Scenario

Expected behavior

Sign-off

1

output as uri-FDN/alternate id may be reported back as a cm handle id. 



Characteristics


Parameter

Expectation

Notes

Sign-off

1



Out-of-scope

  • Positive output should not be affected by the response we receive as uri-FDN/alternate id as a cm handle id response. 

Solution Proposal

Example of Resource Rules Expand source
Interface Proposal Expand source
Sample call Expand source


  • No labels