Loop Avoidance Using Audits on Registration
draft-srivastava-sipping-loop-avoidance-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Samir Srivastava | ||
| Last updated | 2006-05-25 | ||
| 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
This document proposes change in registration process of SIP for avoiding installation of looped bindings spread across more than one proxy. This version of the document broadly outlines the solution. Exact details will be provided in the subsequent versions, as the solution progresses.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)