RFC 5486: Session Peering for Multimedia Interconnect (SPEERMINT) Terminology

This document defines the terminology that is to be used in describing Session PEERing for Multimedia INTerconnect (SPEERMINT). This memo provides information…

Read RFC 5486 on the RFC Editor

Outgoing relationships (7 related RFCs)

Informative reference — RFC 3261: SIP: Session Initiation Protocol
Informative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Informative reference — RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Informative reference — RFC 2782: A DNS RR for specifying the location of services (DNS SRV)
Informative reference — RFC 3761: The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
Informative reference — RFC 3404: Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)
Informative reference — RFC 761: DoD standard Transmission Control Protocol

Incoming relationships (6 related RFCs)

Normatively referenced by — RFC 6406: Session PEERing for Multimedia INTerconnect (SPEERMINT) Architecture
Normatively referenced by — RFC 6461: Data for Reachability of Inter-/Intra-NetworK SIP (DRINKS) Use Cases and Protocol Requirements
Informatively referenced by — RFC 8969: A Framework for Automating Service and Network Management with YANG
Informatively referenced by — RFC 6271: Requirements for SIP-Based Session Peering
Informatively referenced by — RFC 6404: Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested Countermeasures
Informatively referenced by — RFC 6076: Basic Telephony SIP End-to-End Performance Metrics