Attribute Based Addressing for SIP 1/12/2019 Attribute Based Addressing for SIP Vlasios Tsiatsis †, Jyh-Cheng Chen ‡, Prathima Agrawal ‡ and Mani Srivastava† † UCLA Electrical Engineering Department, Los Angeles, CA, USA ‡ Applied Research, Telcordia Technologies, Inc. Morristown, NJ, USA April 2, 2001 Good afternoon. Today I am going to talk to you about how adaptive frame length control can be used to improve the quality of a wireless link. In particular, when I speak of the link’s “quality,” I am talking about increasing throughput, extending range, and improving energy efficiency of the wireless devices. I will first attempt to motivate the need for such adaptive control, giving an intuitive feel for the benefits we might achieve. I’ll then explain where in the existing hierarchy such adaptation should be placed, that is, where we are doing are work. I will then present analysis which shows in a quantitative fashion that along each of the chosen metrics, there is something to be gained with this technique. Following that I will describe an experiment we did to confirm the analysis. Finally, I will present our ideas of how such a system should be implemented, and I will show you a picture of the architecture we are currently developing along these lines. I will conclude with an indication of where we are going from here. Motivate analyze experiment locate implement

1/12/2019 Introduction Network entities are named either by IP address or a fully qualified domain name Users like descriptive and contextual names e.g. “call my friend Bob”, “call the nearest policeman” Call based and Packet based services in a natural way e.g. “call my friends”, “send my friends this picture”

INVITE helen@ee.ucla.edu 1/12/2019 Contribution Implement an additional user location service for SIP ... .. as a distributed system of attribute based name resolvers SIP Server john@hol.gr INVITE helen@ucla.edu Query Location Server Reply helen@ee.ucla.edu INVITE helen@ee.ucla.edu ACK helen@ee.ucla.edu

Distributed Name Resolution System Database Records User Description as a list of attribute value pairs Database maintenance information Record No Maintenance Information Attribute value pair list a=1 name = vlasios occupation = student city = Seattle

Requests/Responses Each message is preceded by the requesting user identification Registration (soft state) Signoff Description Modification Query Application Level Forwarding Responses in XML form

Information/Request Processing All requests are scoped Currently update requests are replicated to all location servers Queries like DNS Find all Friends A B D Query Reply Query C Friend

Application Level Forwarding Send(Hello) to all Friends A B D Friends are at C Registration Forwarding Friends are at B Friends are at A C What is we only wanted to push send messages to other users ? What is other users have variable attributes or they move ?

Integration with SIP Used Columbia SIP client/server implementation Added the necessary GUI for SIP client and the necessary code for SIP server Used the extension mechanism of SIP (“Require” header) Registration and Updates in REGISTER requests Queries and Application Forwarding in INVITE requests

Future Work Indexing Scheme for Information Processing and Distribution (currently replication) What happens if a user wants to be found: by specific users ? by specific machines ? at some specific time of the day ? Push based messaging system

Conclusions Provide a unified naming system for individuals or groups Descriptive and natural naming system for IP telephony Users concentrate on what they want Suitable for packet oriented communication