M. Handley, H. Schulzrinne, and E. Schooler, RFC 2543: SIP: Session initiation protocol, http://www.rfc-editor.org/rfc/rfc2543.txt, July 1997, Status: Proposed standard. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Policy-Based Networking in a Mobile, Multi-Connected Environment - Myhre (2003) (Correct)
....cache home address care of address pairs, and forward packages addressed to the home address of a mobile host directly to the care of address. This approach demands changes to the network layer of all routers in the Internet. Some focus on mobility on the transport layer[36] or application layer[23]. The advantage of moving mobility support higher up in the network stack is to allow the higher level protocols to adapt to the changes in mobility. When a hand ooe is initiated, the properties of the network may well have changed dramatically. There may be a wholly dioeerent bandwidth, and ....
M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg. Rfc 2543: Sip: Session initiation protocol, 1999.
Enabling Secure IP Telephony in Enterprise Networks - Reynolds (2001) (Correct)
....allow terminals on either network to utilize and access resources and information contained in both. IP telephony services can be deployed using one of two different protocols. The Internet Engineering Task Force (IETF) has developed a plain text protocol called Session Initiation Protocol (SIP) [23] based on the structure of the Hypertext Transfer Protocol (HTTP) 18] The International Telecommunication Union (ITU) developed H.323 [31] which inherited the structure and basic functionality from the Signaling System 7 (SS7) 47] protocol used within the PSTN. The two protocols are not ....
....does not influence the quality of service of a call [53] Given that H.323 is a more complex protocol to decode and examine, this work is based on SIP. However, the solutions outlined are applicable to a H.323 environment. 2.2. 1 Session Initiation Protocol The Session Initiation Protocol [23] is an ASCII based client server protocol (server side binds to port 5060) that uses either the Transmission Control Protocol (TCP) 40] or the User Datagram Protocol (UDP) 39] as a transport. The following quote from the RFC gives a detailed description of SIP s capabilities: The Session ....
[Article contains additional citation context not shown here]
M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg. RFC 2543: SIP: Session Initiation Protocol, March 1999.
A Case for Network Musical Performance - Lazzaro, Wawrzynek (Correct)
....and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and or a fee. NOSSDAV 01, June 25 26, 2001, Port Jefferson, New York, USA. Copyright 2001 ACM 1 58113 370 7 01 0006 . 5.00. and SIP [5] for networking, and MIDI [8] for musical control) with a new RTP packetization for MIDI performance that supports the graceful recovery from lost and late packets. We analyze data from NMP experiments conducted on CalREN2 hosts located on the UC Berkeley, Stanford, and Caltech campuses, and ....
....do not need to know the Internet addresses of the other musicians in a session. Instead, the musicians choose a session name for the performance, and the NMP clients interact with a conference server to handle connection details. Our conference server uses the Session Initiation Protocol (SIP) [5]. Our system also includes an auxiliary server for system testing, called a mirror server. Participants may temporarily launch a mirror server at the start of the session, to help debug the link and measure latencies. Mirror servers implement the RTP and SIP functionality of an NMP client, but ....
M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg. RFC 2543: SIP: Session initiation protocol, 1999.
Real-time Transport Protocol (RTP) security - Hallivuori (Correct)
....key from the password. RTP assumes that more complex key management is either handled by other protocols or by application specific profiles. On conference type applications (video, audio or even only a shared white board) key management is handled by combination of SIP, SAP and SDP protocols [6, 8, 9, 13]. These protocols feature strong authentication and key exchange features, and provide standardized way to establish encrypted conferences using RTP as the transport protocol. 5 Analysis of RTP security 5.1 Confidentiality The default DES CBC algorithm is inadequate, as it can easily be broken ....
M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg. RFC 2543: SIP: Session initiation protocol, March 1999.
Diplomarbeit | Master's Thesis - Enhancing An Isdn (Correct)
No context found.
M. Handley, H. Schulzrinne, and E. Schooler, RFC 2543: SIP: Session initiation protocol, http://www.rfc-editor.org/rfc/rfc2543.txt, July 1997, Status: Proposed standard.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC