The SIP PING Method
draft-fwmiller-ping-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Frank w. Miller | ||
| Last updated | 2006-05-16 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Session Initiation Protocol (SIP) has the potential for long periods of time to elapse when no signaling traffic is sent between a User Agent Client (UAC) and a User Agent Server (UAS). There are situations when it may be necessary for some signaling traffic to flow periodically between these endpoints or to have a quick, lightweight check for whether a UAS is alive. The PING method is proposed that can be used for these purposes.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)