PROTO Writeup for draft-ietf-sipbrandy-rtpsec-06
(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)? Why
is this the proper type of RFC? Is this type of RFC indicated in
the title page header?
BCP, as indicated in the title page header.
(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement
Write-Up. Recent examples can be found in the "Action"
announcements for approved documents. The approval announcement
contains the following sections:
Technical Summary:
Although the Session Initiation Protocol (SIP) includes a suite of
security services that has been expanded by numerous
specifications over the years, there is no single place that
explains how to use SIP to establish confidential media sessions.
Additionally, existing mechanisms have some feature gaps that need
to be identified and resolved in order for them to address the
pervasive monitoring threat model. This specification describes
best practices for negotiating confidential media with SIP,
including both comprehensive protection solutions which bind the
media to SIP-layer identities as well as opportunistic security
solutions.
Working Group Summary:
There is consensus in the WG around this document.
Document Quality:
While parts of the specification have been implemented, we are not
aware of any implementation that implements all of it. In fact,
the goal with publishing this RFC is to get more implementations
out there.
Personnel:
Who is the Document Shepherd? Who is the Responsible Area Director?
Gonzalo Camarillo is the Document Shepherd. Ben Campbell is the
responsible AD.
(3) Briefly describe the review of this document that was performed by
the Document Shepherd. If this version of the document is not
ready for publication, please explain why the document is being
forwarded to the IESG.
The document shepherd reviewed revision 06 of this document, which
was ready for publication.
(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?
No.
(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA,
DNS, DHCP, XML, or internationalization? If so, describe the
review that took place.
No.
(6) Describe any specific concerns or issues that the Document
Shepherd has with this document that the Responsible Area Director
and/or the IESG should be aware of? For example, perhaps he or she
is uncomfortable with certain parts of the document, or has
concerns whether there really is a need for it. In any event, if
the WG has discussed those issues and has indicated that it still
wishes to advance the document, detail those concerns here.
No concerns.
(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of
BCP 78 and BCP 79 have already been filed. If not, explain why?
Yes.
(8) Has an IPR disclosure been filed that references this document? If
so, summarize any WG discussion and conclusion regarding the IPR
disclosures.
No.
(9) How solid is the WG consensus behind this document? Does it
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with
it?
The whole WG understands the document and agree with
it. Nevertheless, the number of active participants in the
SIPBRANDY WG is limited at this point.
(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarise the areas of conflict in
separate email messages to the Responsible Area Director. (It
should be in a separate email because this questionnaire is
publicly available.)
No.
(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the
Internet-Drafts Checklist). Boilerplate checks are not enough;
this check needs to be thorough.
The document contains no relevant nits.
(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type
reviews.
No formal reviews are needed.
(13) Have all references within this document been identified as
either normative or informative?
Yes.
(14) Are there normative references to documents that are not ready
for advancement or are otherwise in an unclear state? If such
normative references exist, what is the plan for their
completion?
No.
(15) Are there downward normative references references (see RFC
3967)? If so, list these downward references to support the Area
Director in the Last Call procedure.
No.
(16) Will publication of this document change the status of any
existing RFCs? Are those RFCs listed on the title page header,
listed in the abstract, and discussed in the introduction? If the
RFCs are not listed in the Abstract and Introduction, explain
why, and point to the part of the document where the relationship
of this document to the other RFCs is discussed. If this
information is not in the document, explain why the WG considers
it unnecessary.
No.
(17) Describe the Document Shepherd's review of the IANA
considerations section, especially with regard to its consistency
with the body of the document. Confirm that all protocol
extensions that the document makes are associated with the
appropriate reservations in IANA registries. Confirm that any
referenced IANA registries have been clearly identified. Confirm
that newly created IANA registries include a detailed
specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and
a reasonable name for the new registry has been suggested (see
RFC 5226).
The IANA Considerations Section is complete and consistent.
(18) List any new IANA registries that require Expert Review for
future allocations. Provide any public guidance that the IESG
would find useful in selecting the IANA Experts for these new
registries.
No new registries are defined.
(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.
No such checks were needed.