added new sub_id related language. Modified existing language to refl…

[tulshi]

…ect the use of the sub_id claim

[independentid]

The format value is an IANA registered format to avoid conflicts. The term "complex" is probably too generic.

You may want to prefix it with the spec name (e.g. caep, risc, ssf) For example "caep_complex".

Registration info is in section 8.1 of the subject identifier draft.

Other than that looks good.

[FragLegs]

The format value is an IANA registered format to avoid conflicts. The term "complex" is probably too generic.

You may want to prefix it with the spec name (e.g. caep, risc, ssf) For example "caep_complex".

Registration info is in section 8.1 of the subject identifier draft.

@independentid Can we separate that into another issue/pull request to avoid polluting the discussion of this one?

[independentid]

Sure. Could be handled as a separate issue.

[appsdesh]

Could you please add following in the section Distinguishing SETs from other Kinds of JWTs

The "sub_id" claim MUST be present, as described in {{{subject-members}}

[appsdesh]

This works! Thanks