References from draft-matuszewski-p2psip-security-requirements
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| draft-bryan-p2psip-app-scenarios |
Application Scenarios for Peer-to-Peer Session Initiation Protocol (P2PSIP)
References Referenced by |
normatively references | ||
| draft-bryan-p2psip-requirements |
P2PSIP Protocol Framework and Requirements
References Referenced by |
normatively references | ||
| draft-ietf-p2psip-base |
REsource LOcation And Discovery (RELOAD) Base Protocol
References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-p2psip-concepts |
Concepts and Terminology for Peer-to-Peer SIP (P2PSIP)
References Referenced by |
Informational | normatively references | |
| draft-ietf-p2psip-diagnostics |
Peer-to-Peer (P2P) Overlay Diagnostics
References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-p2psip-sip |
A SIP Usage for REsource LOcation And Discovery (RELOAD)
References Referenced by |
Proposed Standard | normatively references | |
| draft-matuszewski-p2psip-security-overview |
P2PSIP Security Overview and Risk Analysis
References Referenced by |
Possible Reference | ||
| draft-song-p2psip-security-eval |
P2PSIP Security Analysis and Evaluation
References Referenced by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 3261 |
SIP: Session Initiation Protocol
References Referenced by |
Proposed Standard | normatively references |