Currently, IoTDM is responding with following attributes while creating the “content” resource or when AS retrieve (GET) the “content” resource.

1) While doing Container creation request, see following response -
{
"m2m:cnt":

{ "ct": "20170220T144009", "st": 0, "ty": 3, "cbs": 0, "ri": "01i", "lt": "20170220T144009", "pi": "/InCSE1/01h", "et": "29991231T111111", "cni": 0 }

}

2) I do see following in the data-store (MD-SAL)

Expected behavior - NSC shall include “mni”, attributes in the HTTP/201 when container create response ?

As per onem2m TS-004 (see para 1) -

7.4.6.2.1 Create
Originator:
No change from the generic procedures in clause 7.2.2.1.
Receiver:
Primitive specific operation on Recv-6.4 is performed with following exceptions for optional attributes while executing procedures defined in clause 7.3.3.3.
The Hosting CSE may assign default values based on local policy for optional attributes maxNrOfInstances , maxByteSize and maxInstanceAge.
If the maxNrOfInstances , maxByteSize or maxInstanceAge attributes are present in the resource representation, but their value indicates an invalid value, then the request shall be rejected with a Response Status Code indicating "BAD_REQUEST" error.
There are two cases where the Hosting CSE shall configure or overrride a maxNrOfInstances , maxByteSize or maxInstanceAge value specified in the resource representation (if present).
1) The Originator does not specify a value

2) The Hosting CSE determines the maxNrOfInstances , maxByteSize or maxInstanceAge requested by the Originator doesn’t meet its requirements (e.g. based on a local policy)

In these cases, the Hosting CSE shall configure a maxNrOfInstances , maxByteSize or maxInstanceAge into the resource according to local policy. In addition, the Hosting CSE shall communicate the modified value back to the originator in the response if the Result Content parameter permits this.
No other changes from the generic procedures in clause 7.2.2.2