As required by RFC 4858, this is the current template for the Document
Shepherd Write-Up.
Changes are expected over time. This version is dated 24 February 2012.
(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
Since this document documents the intended actions, systems, etc for deployment
of a bgpsec enabled network, I believe 'BCP' is appropriate as an intended
status. There are no 'BGPSEC Enabled' networks today, but in planning to deploy
operations staff will need plans and maps to use in finding their way through
the forest. This should serve as that map.
(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
"Deployment of the BGPsec architecture and protocols has many
operational considerations. This document attempts to collect and
present the most critical and universal. It is expected to evolve as
BGPsec is formalized and initially deployed."
Relevant content can frequently be found in the abstract
and/or introduction of the document. If not, this may be
an indication that there are deficiencies in the abstract
or introduction.
Working Group Summary
This draft went thorugh several revisions (10), with good discussion from
stake-holders in the communit(ies) affected.
Was there anything in WG process that is worth noting? For
example, was there controversy about particular points or
were there decisions where the consensus was particularly
rough?
nothing of note.
Document Quality
The document is in good shape, there are some ID-NITS to deal with prior to
final publication, notably:
2 references to be fixed up (downref 2 normative references, easily adjusted)
Boilerplate issues (2119 issues), also easily adjusted.
Are there existing implementations of the protocol? Have a
significant number of vendors indicated their plan to
implement the specification? Are there any reviewers that
merit special mention as having done a thorough review,
e.g., one that resulted in important changes or a
conclusion that the document had no substantive issues? If
there was a MIB Doctor, Media Type or other expert review,
what was its course (briefly)? In the case of a Media Type
review, on what date was the request posted?
This is not a protocol, so no implementations.
Personnel
Who is the Document Shepherd? Who is the Responsible Area
Director?
Shepherd: Chris Morrow (morrowc@ops-netman.net)
AD: Alvaro Retana (aretana@cisco.com)
(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.
I read the document (a few times over it's lifecycle) and believe it is in good
shape 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 IPR concerns
(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?
Consensus is as solid as ever in SIDR... there was good review over the
lifetime of the document.
(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 https://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.
** Downref: Normative reference to an Informational draft:
draft-ietf-sidr-bgpsec-overview (ref. 'I-D.ietf-sidr-bgpsec-overview')
** Downref: Normative reference to an Informational RFC: RFC 6480RFC2119 boilerplate issues
and private-ip usage which should be changed to test/documentation networks.
all fixable before final publication, none super relevant to the content.
(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.
no formal review required.
(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?
There are references to drafts, yes, which will have to be sorted out before
publication is finalized.
(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.
yes, two. which will be fixed.
** Downref: Normative reference to an Informational draft:
draft-ietf-sidr-bgpsec-overview (ref. 'I-D.ietf-sidr-bgpsec-overview')
** Downref: Normative reference to an Informational RFC: RFC 6480
6480 will likely eventually point to the -bis I expect, and the overview will
shift ot the final rfc when that is published.
(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).
There are no IANA considerations.
(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.
NONE
(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.
id-nits run, no other structured data to review.