rfc.dk

Cited by: RFC 3238

21 RFCs whose text mentions RFC 3238 (IAB Architectural and Policy Considerations for Open Pluggable Edge Services), newest first

RFCTitleStatusDate
7452Architectural Considerations in Smart Object NetworkingH. Tschofenig, J. Arkko, D. Thaler, D. McPhersonInformationalMarch 2015
5369Framework for Transcoding with the Session Initiation Protocol (SIP)G. CamarilloInformationalOctober 2008
4902Integrity, Privacy, and Security in Open Pluggable Edge Services (OPES) for SMTPM. StecherInformationalMay 2007
4313Requirements for Distributed Control of Automatic Speech Recognition (ASR), Speaker Identification/Speaker Verification (SI/SV), and Text-to-Speech (TTS) ResourcesD. OranInformationalDecember 2005
4236HTTP Adaptation with Open Pluggable Edge Services (OPES)A. Rousskov, M. StecherProposed StandardNovember 2005
4142Full-mode Fax Profile for Internet Mail (FFPIM)D. Crocker, G. KlyneProposed StandardNovember 2005
4141SMTP and MIME Extensions for Content ConversionK. Toyoda, D. CrockerProposed StandardNovember 2005
4037Open Pluggable Edge Services (OPES) Callout Protocol (OCP) CoreA. RousskovProposed StandardMarch 2005
3914Open Pluggable Edge Services (OPES) Treatment of IAB ConsiderationsA. Barbir, A. RousskovInformationalOctober 2004
3897Open Pluggable Edge Services (OPES) Entities and End Points CommunicationA. BarbirInformationalSeptember 2004
3838Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES)A. Barbir, O. Batuner, A. Beck, T. Chan, H. OrmanInformationalAugust 2004
3837Security Threats and Risks for Open Pluggable Edge Services (OPES)A. Barbir, O. Batuner, B. Srinivas, M. Hofmann, H. OrmanInformationalAugust 2004
3836Requirements for Open Pluggable Edge Services (OPES) Callout ProtocolsA. Beck, M. Hofmann, H. Orman, R. Penno, A. TerzisInformationalAugust 2004
3835An Architecture for Open Pluggable Edge Services (OPES)A. Barbir, R. Penno, R. Chen, M. Hofmann, H. OrmanInformationalAugust 2004
3752Open Pluggable Edge Services (OPES) Use Cases and Deployment ScenariosA. Barbir, E. Burger, R. Chen, S. McHenry, H. Orman, R. PennoInformationalApril 2004
3724The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet ArchitectureJ. Kempf, Ed., R. Austein, Ed., IABInformationalMarch 2004
3568Known Content Network (CN) Request-Routing MechanismsA. Barbir, B. Cain, R. Nair, O. SpatscheckInformationalJuly 2003
3507Internet Content Adaptation Protocol (ICAP)J. Elson, A. CerpaInformationalApril 2003
3459Critical Content Multi-purpose Internet Mail Extensions (MIME) ParameterE. BurgerProposed StandardJanuary 2003
3426General Architectural and Policy ConsiderationsS. FloydInformationalNovember 2002
3387Considerations from the Service Management Research Group (SMRG) on Quality of Service (QoS) in the IP NetworkM. Eder, H. Chaskar, S. NagInformationalOctober 2002