LGTM - but do we need to document the behaviour when the client sends an x-correlator of zero length?

LGTM - but do we need to document the behaviour when the client sends an x-correlator of zero length?

In this case, I think that as we return the value provided by the client, we will send an empty string.

In this case, I think that as we return the value provided by the client, we will send an empty string.

Yeah...just seems wasteful. I could understand if sending an empty string meant 'please can the network generate a correlator for me and send it back', but I can't see the rationale for sending an empty string if the network is just going to echo it back.

In this case, I think that as we return the value provided by the client, we will send an empty string.

Yeah...just seems wasteful. I could understand if sending an empty string meant 'please can the network generate a correlator for me and send it back', but I can't see the rationale for sending an empty string if the network is just going to echo it back.

This point is already covered Kevin, Patrice:
When the API Consumer includes non-empty "x-correlator" header in the request, the API Provider must include it in the response with the same value that was used in the request. Otherwise, it is optional to include the "x-correlator" header in the response with any valid value.

It can be an empty string or a valid value, up to the Telco Operator

Thanks, LGTM