rfc.dk

Cited in: RFC 8599

20 RFCs mentioned in the text of RFC 8599 (Push Notification with the Session Initiation Protocol (SIP))

RFCTitleStatusDate
2119Key words for use in RFCs to Indicate Requirement LevelsS. BradnerBest Current PracticeMarch 1997
3261SIP: Session Initiation ProtocolJ. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley, E. SchoolerProposed StandardJuly 2002
3264An Offer/Answer Model with Session Description Protocol (SDP)J. Rosenberg, H. SchulzrinneProposed StandardJuly 2002
3680A Session Initiation Protocol (SIP) Event Package for RegistrationsJ. RosenbergProposed StandardMarch 2004
3840Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)J. Rosenberg, H. Schulzrinne, P. KyzivatProposed StandardAugust 2004
3891The Session Initiation Protocol (SIP) "Replaces" HeaderR. Mahy, B. Biggs, R. DeanProposed StandardSeptember 2004
3969The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)G. CamarilloBest Current PracticeDecember 2004
4320Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE TransactionR. SparksProposed StandardJanuary 2006
4321Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE TransactionR. SparksInformationalJanuary 2006
5079Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)J. RosenbergProposed StandardDecember 2007
5234Augmented BNF for Syntax Specifications: ABNFD. Crocker, Ed., P. OverellInternet StandardJanuary 2008
5626Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)C. Jennings, Ed., R. Mahy, Ed., F. Audet, Ed.Proposed StandardOctober 2009
6665SIP-Specific Event NotificationA.B. RoachProposed StandardJuly 2012
6809Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)C. Holmberg, I. Sedlacek, H. KaplanProposed StandardNovember 2012
7841RFC Streams, Headers, and BoilerplatesJ. Halpern, Ed., L. Daigle, Ed., O. Kolkman, Ed.InformationalMay 2016
8030Generic Event Delivery Using HTTP PushM. Thomson, E. Damaggio, B. Raymor, Ed.Proposed StandardDecember 2016
8126Guidelines for Writing an IANA Considerations Section in RFCsM. Cotton, B. Leiba, T. NartenBest Current PracticeJune 2017
8174Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsB. LeibaBest Current PracticeMay 2017
8291Message Encryption for Web PushM. ThomsonProposed StandardNovember 2017
8292Voluntary Application Server Identification (VAPID) for Web PushM. Thomson, P. BeverlooProposed StandardNovember 2017