References to rfc3238

This is an experimental product. 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.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
RFC 3459 Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter
References Referenced by
Proposed Standard normatively references Downref
RFC 3467 Role of the Domain Name System (DNS)
References Referenced by
Informational normatively references
RFC 3568 Known Content Network (CN) Request-Routing Mechanisms
References Referenced by
Informational normatively references
RFC 3835 An Architecture for Open Pluggable Edge Services (OPES)
References Referenced by
Informational normatively references
RFC 3836 Requirements for Open Pluggable Edge Services (OPES) Callout Protocols
References Referenced by
Informational normatively references
RFC 3838 Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES)
References Referenced by
Informational normatively references
RFC 3914 Open Pluggable Edge Services (OPES) Treatment of IAB Considerations
References Referenced by
Informational normatively references
RFC 4313 Requirements for Distributed Control of Automatic Speech Recognition (ASR), Speaker Identification/Speaker Verification (SI/SV), and Text-to-Speech (TTS) Resources
References Referenced by
Informational normatively references
RFC 4902 Integrity, Privacy, and Security in Open Pluggable Edge Services (OPES) for SMTP
References Referenced by
Informational normatively references
RFC 5369 Framework for Transcoding with the Session Initiation Protocol (SIP)
References Referenced by
Informational normatively references
RFC 3426 General Architectural and Policy Considerations
References Referenced by
Informational informatively references
RFC 3724 The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture
References Referenced by
Informational informatively references
RFC 3752 Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios
References Referenced by
Informational informatively references
RFC 3837 Security Threats and Risks for Open Pluggable Edge Services (OPES)
References Referenced by
Informational informatively references
RFC 3897 Open Pluggable Edge Services (OPES) Entities and End Points Communication
References Referenced by
Informational informatively references
RFC 4037 Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core
References Referenced by
Proposed Standard informatively references
RFC 4141 SMTP and MIME Extensions for Content Conversion
References Referenced by
Proposed Standard informatively references
RFC 4142 Full-mode Fax Profile for Internet Mail (FFPIM)
References Referenced by
Proposed Standard informatively references
RFC 4236 HTTP Adaptation with Open Pluggable Edge Services (OPES)
References Referenced by
Proposed Standard informatively references
RFC 3507 Internet Content Adaptation Protocol (ICAP)
References Referenced by
Informational Possible Reference
RFC 3387 Considerations from the Service Management Research Group (SMRG) on Quality of Service (QoS) in the IP Network
References Referenced by
Informational Reference