[Teas] Identifiers in draft-zhang-teas-transport-service-model

["Scharf, Michael (Nokia - DE)" <[e-mail]>]

Hi all,

I have had some off-list discussions with the authors of draft-zhang-teas-transport-service-model. Regarding one specific point I look for further feedback on the list:

To me it seems a quite surprising design choice to model in a service model endpoints (tp-id) and service IDs (service-id) by an integer value (uint32). A more obvious choice to me would be e.g. a string.

This seems to be common practice in another service model of the IETF. See draft-ietf-l3sm-l3vpn-service-model-11:

    typedef svc-id {
        type string;
        description
         "Defining a type of service component
         identificators.";
    }

I think the IETF should try to align at least basic constructs in "service models" even if they apply to different technologies. Some communality at least regarding identifiers would be a good starting point, IMHO.

Is there any particular reason why IDs would have to be uint32 in a transport service model context?

Thanks

Michael