% Datatracker information for RFCs on the Legacy Stream is unfortunately often
% incorrect. Please correct the bibtex below based on the information in the
% actual RFC at https://rfc-editor.org/rfc/rfc3427.txt

@misc{rfc3427,
    series =    {Request for Comments},
    number =    3427,
    howpublished =  {RFC 3427},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC3427},
    url =       {https://www.rfc-editor.org/info/rfc3427},
    author =    {Rohan Mahy and Joerg Ott and Dean Willis and Allison J. Mankin and Brian Rosen and Scott O. Bradner},
    title =     {{Change Process for the Session Initiation Protocol (SIP)}},
    pagetotal = 12,
    year =      2002,
    month =     dec,
    abstract =  {This memo documents a process intended to apply architectural discipline to the future development of the Session Initiation Protocol (SIP). There have been concerns with regards to new SIP proposals. Specifically, that the addition of new SIP features can be damaging towards security and/or greatly increase the complexity of the protocol. The Transport Area directors, along with the SIP and Session Initiation Proposal Investigation (SIPPING) working group chairs, have provided suggestions for SIP modifications and extensions. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.},
}