Reported Issues with the Security Mechanism Agreement for the Session Initiation Protocol (SIP)
draft-niemi-rfc3329-issues-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Aki Niemi | ||
| Last updated | 2006-03-01 | ||
| 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 records some of the issues reported by implementors of the Security Mechanism Agreement for the Session Initiation Protocol (SIP), or RFC 3329. It is intended to serve as an aid in discussions and a checklist for a possible revision of the RFC.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)