Working Group
Click on the red underlined text to get to the source
... the SIP protocol [3], as long as the working group exists. All
changes or extensions to SIP must first exist as SIP ...
... changes or extensions to SIP must first exist as SIP Working Group
documents. The SIP Working group ...
... Working Group
documents. The SIP Working group is charged with being the guardian
of the SIP protocol for the Internet ...
... SIPPING Working Group.
IETF working groups do not live forever; typically, mailing lists
continue after the working group ...
... IETF working groups do not live forever; typically, mailing lists
continue after the working group is concluded. If the SIP Working
Group has closed and no suitable replacement or follow-on working
group ...
... continue after the working group is concluded. If the SIP Working
Group has closed and no suitable replacement or follow-on working
group is active, the Transport ...
... working group is concluded. If the SIP Working
Group has closed and no suitable replacement or follow-on working
group is active, the Transport Area directors ...
... Transport Area directors will the use the non-
working group standards track document process (described in section
6.1.2 of RFC 2026--IETF Standards ...
... IETF is hoped to be low.
It is appropriate for any working group to develop SIP event packages
...
... event packages
[4], but the working group must have charter approval to do so. The
IETF will also require (Individual) RFC publication for the
...
... registration of event packages developed outside the scope of an IETF
working group. Requirements for publishing event packages are
...
... The IETF SIPPING Working Group ...
... IETF Session Initiation Protocol Proposal Investigation (sipping)
Working Group is chartered to be a filter in front of the SIP Working
Group ...
... Working Group is chartered to be a filter in front of the SIP Working
Group. This working group will investigate requirements for
...
... filter in front of the SIP Working
Group. This working group will investigate requirements for
applications of SIP ...
... large, or from individuals who are reporting the requirements as
determined by another standards body. The SIPPING Working Group will
also not live forever, with similar consideration to the sections
above.
...
... above.
The SIPPING Working Group may determine: that these requirements can
be satisfied by SIP ...
... such as realtime presence.
When the SIPPING working group decides on a set of requirements, it
forwards them to the SIP ...
... set of requirements, it
forwards them to the SIP working group. The SIPPING Working Group
may also document usage or applications of SIP ...
... forwards them to the SIP working group. The SIPPING Working Group
may also document usage or applications of SIP which do not require
...
... protocol extensions.
The SIPPING working group also acts as a filter for proposed event
packages as described in Section 4.3.
...
... requirements. After the Internet-Draft is published, the authors
should send a note to the SIPPING Working Group mailing list to start
...
... charter based on the mailing list discussion. The SIPPING working
group should consider whether the requirements can be merged with
other requirements ...
... If the chairs and the ADs both feel that the particular new problems
should be added to the SIPPING Working Group charter, then the ADs
will present the proposed SIPPING charter modifications to the IESG ...
... IESG (with IAB advice) approves of the charter changes, the
SIPPING working group can then work on the problems described in the
Internet-Draft.
...
... Internet-Draft
would then be passed to the SIP working group for consideration (if
warranted). The SIP working group ...
... working group for consideration (if
warranted). The SIP working group is not required to adopt the
proposed solution from this additional Internet-Draft.
...
... Internet-Draft.
The SIPPING working group may also evaluate such proposals for
extensions if the requirements are judged to be appropriate to SIP ...
... SIP,
but are not sufficiently general for standards track activity. The
SIPPING working group will attempt to determine if the new proposal
meets the requirements for publication as a "P-" header ...
... which the requirements analysis is implicit and the SIP working group
requests the addition of a charter item for an extension without a
full SIPPING ...
... Transport Area calls for architectural guardianship and application
of Occam's Razor by the SIP Working Group.
In keeping with the IETF ...
... 6. The proposed header MUST be clearly documented in an (Individual
or Working Group) Informational RFC, and registered with IANA.
...
... standards-track RFC issued through the SIP Working Group") MUST
include a "P-" prefix on the header ...
... can only be created and registered by the publication of a Standards
Track RFC (from an IETF Working Group). Normal event packages can be
created ...
... event packages can be
created and registered by the publication of any Working Group RFC
(Informational, Standards Track, Experimental), provided that the RFC
...
... (Informational, Standards Track, Experimental), provided that the RFC
is a chartered working group item.
Individuals may also wish to publish SIP ...
... SIP event package MUST first be
published as Internet-drafts for review by the SIPPING Working Group,
or the working group, mailing list ...
... Internet-drafts for review by the SIPPING Working Group,
or the working group, mailing list, or expert designated by the
Transport ...
... Transport Area Directors if the SIPPING Working Group has closed.
Proposals should include a strong motivational section, a thorough
description of the proposed syntax and semantics ...
... author should submit his or her proposal as an individual Internet-
Draft, and post an announcement to the working group mailing list to
begin discussion ...
... mailing list to
begin discussion. The SIPPING Working Group will determine if the
proposed package is a) an inappropriate usage of SIP, b) applicable
...
... to SIP but not sufficiently interesting, general, or in-scope to
adopt as a working group effort, c) contrary to similar work planned
in the Working Group, or d) should be adopted as or merged with
...
... adopt as a working group effort, c) contrary to similar work planned
in the Working Group, or d) should be adopted as or merged with
chartered work.
...
... registration of
event packages developed outside the scope of an IETF working group,
according to the following guidelines:
...