rfc3427
rfc2418
rfc2026
rfc1796
rfc2223
rfc2119
rfc2360
rfc2804
draft-bradner-submission-rights
draft-iprwg-technology
draft-bradner-ipr-technology
rfc3427
rfc2418
rfc2026
rfc1796
rfc2223
rfc2119
rfc2360
rfc2804
draft-bradner-submission-rights
draft-iprwg-technology
draft-bradner-ipr-technology
rfc3427.txt  | Change Process for the Session Initiation Protocol (SIP) |
| Author(s) | A. Mankin, S. Bradner, R. Mahy, D. Willis, J. Ott, B. Rosen |
| Organization | ietf |
| State | best current practice |
| Size | 26234 bytes |
| also | bcp67.txt |
| 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. |
| rfc2418.txt | IETF Working Group Guidelines and Procedures |
| Author(s) | S. Bradner |
| Organization | ietf |
| State | best current practice |
| Size | 62857 bytes |
| obsoletes | rfc1603.txt |
| updated by | rfc3934.txt |
| also | bcp25.txt |
| Abstract | The Internet Engineering Task Force (IETF) has responsibility for developing and reviewing specifications intended as Internet Standards. IETF activities are organized into working groups (WGs). This document describes the guidelines and procedures for formation and operation of IETF working groups. It also describes the formal relationship between IETF participants WG and the Internet Engineering Steering Group (IESG) and the basic duties of IETF participants, including WG Chairs, WG participants, and IETF Area Directors. |
| rfc2026.txt | The Internet Standards Process -- Revision 3 |
| Author(s) | S. Bradner |
| Organization | ietf |
| State | best current practice |
| Size | 86731 bytes |
| obsoletes | rfc1602.txt |
| updated by | rfc3667.txt rfc3668.txt rfc3932.txt |
| also | bcp9.txt |
| Abstract | This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. It also addresses the intellectual property rights and copyright issues associated with the standards process. |
| rfc1796.txt | Not All RFCs are Standards |
| Author(s) | C. Huitema, J. Postel, S. Crocker |
| Organization | ietf |
| State | informational |
| Size | 7049 bytes |
| Abstract | This document discusses the relationship of the Request for Comments (RFCs) notes to Internet Standards. |
| rfc2223.txt | Instructions to RFC Authors |
| Author(s) | J. Postel, J. Reynolds |
| Organization | ietf |
| State | informational |
| Size | 38064 bytes |
| obsoletes | rfc1543.txt rfc1111.txt rfc825.txt |
| rfc2119.txt | Key words for use in RFCs to Indicate Requirement Levels |
| Author(s) | S. Bradner |
| Organization | ietf |
| State | best current practice |
| Size | 4723 bytes |
| also | bcp14.txt |
| Abstract | In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. Authors who follow these guidelines should incorporate this phrase near the beginning of their document: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Note that the force of these words is modified by the requirement level of the document in which they are used. |
| rfc2360.txt | Guide for Internet Standards Writers |
| Author(s) | G. Scott |
| Organization | ietf |
| State | best current practice |
| Size | 47280 bytes |
| also | bcp22.txt |
| Abstract | This document is a guide for Internet standard writers. It defines those characteristics that make standards coherent, unambiguous, and easy to interpret. In addition, it singles out usage believed to have led to unclear specifications, resulting in non-interoperable interpretations in the past. These guidelines are to be used with RFC 2223, "Instructions to RFC Authors". |
| rfc2804.txt | IETF Policy on Wiretapping |
| Author(s) | IAB, IESG |
| Organization | ietf |
| State | informational |
| Size | 18934 bytes |
| Abstract | The Internet Engineering Task Force (IETF) has been asked to take a position on the inclusion into IETF standards-track documents of functionality designed to facilitate wiretapping. This memo explains what the IETF thinks the question means, why its answer is "no", and what that answer means. |
| draft-bradner-submission-rights-02.txt
|
| draft-bradner-ipr-technology-02.txt
|