Avoiding declarative service IDs

J. Rosenberg in “Identification of Communications Services in the Session Initiation Protocol (SIP)” RFC 5897 argues that services should not be identified by a service identifier (such as a new Service-ID header).

Slide Notes

J. Rosenberg, Identification of Communications Services in the Session Initiation Protocol (SIP), RFC Editor, RFC 5897 (Informational), ISSN 2070-1721, June 2010 http://www.rfc-editor.org/rfc/rfc5897.txt Links to an external site.

Transcript

[slide496] And Rosenberg talks about avoiding declarative service IDs. That you don't want services to be identified by service identifiers. i.e., simply a label. You want it to be identified by a description of the service it provides. Because now I can have a service that takes those descriptions and synthesizes them into another service. That if I simply know its service 87 it doesn't tell me anything about what it does. And I think at this point we will take a 10-minute break. Is that OK? And we will come back and talk about this is much more than voice.