RIFT: Routing in Fat Trees
draft-ietf-rift-rift-21

Document History
1. Does the working group (WG) consensus represent the strong concurrence of a
few individuals, with others being silent, or did it reach broad agreement?
  The WG consensus is solid.

2. Was there controversy about particular points, or were there decisions where
the consensus was particularly rough?
  No.

3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
so, please summarize 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.

4. For protocol documents, are there existing implementations of the contents of
the document? Have a significant number of potential implementers indicated
plans to implement? Are any existing implementations reported somewhere,
either in the document itself (as RFC 7942 recommends) or elsewhere
(where)?
  Yes. At least two implementations existed.

Additional Reviews
5. Do the contents of this document closely interact with technologies in other
IETF working groups or external organizations, and would it therefore benefit
from their review? Have those reviews occurred? If yes, describe which
reviews took place.
  No. The contents of this document have no closely interact with technologies
in other IETF WG or external organizations.

6. Describe how the document meets any required formal expert review criteria,
such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.
  No formal review required.

7. If the document contains a YANG module, has the final version of the module
been checked with any of the recommended validation tools for syntax and
formatting validation? If there are any resulting errors or warnings, what is
the justification for not fixing them at this time? Does the YANG module
comply with the Network Management Datastore Architecture (NMDA) as specified
in RFC 8342?
  No.

8. Describe reviews and automated checks performed to validate sections of the
final version of the document written in a formal language, such as XML code,
BNF rules, MIB definitions, CBOR's CDDL, etc.
  Thrift compilers have successfully generated automatic code from the
Information Elements Schema defined in Appendix B, which are used in two
interoperable implementations.

Document Shepherd Checks
9. Based on the shepherd's review of the document, is it their opinion that this
document is needed, clearly written, complete, correctly designed, and ready
to be handed off to the responsible Area Director?
  This document is ready for publication.  The document shepherd has done a
complete and general review of the Document. All issues that were raised in the
working group have been addressed. A new version (-17) with nits modification
is going to be published. This document is ready to be submitted to IESG.

10. Several IETF Areas have assembled lists of common issues that their
reviewers encounter. For which areas have such issues been identified
and addressed? For which does this still need to happen in subsequent
reviews?
  The IETF Areas’ comments have been addressed.

11. What type of RFC publication is being requested on the IETF stream (Best
Current Practice, Proposed Standard, Internet Standard,
Informational, Experimental or Historic)? Why is this the proper type
of RFC? Do all Datatracker state attributes correctly reflect this intent?
  The intended status is Proposed Standards. It is indicated in the header.
It matches with the content of the Document which defines protocol procedures.
All Datatracker state attributes correctly reflect this intent.

12. Have reasonable efforts been made to remind all authors of the intellectual
property rights (IPR) disclosure obligations described in BCP 79? To
the best of your knowledge, have all required disclosures been filed? If
not, explain why. If yes, summarize any relevant discussion, including links
to publicly-available messages when applicable.
  Yes. All Authors and Contributors have made a statement regarding their
knowledge of IPR which would relate to this Document. Six IPR disclosures
have been made against this Document. The WG did not raise any issue with
the existence of these IPR.

13. Has each author, editor, and contributor shown their willingness to be
listed as such? If the total number of authors and editors on the front page
is greater than five, please provide a justification.
  The number of authors exceeds five. The sixth co-author Jordan Head is the
main editor of version 16. He did great job to improve the draft.

14. Document any remaining I-D nits in this document. Simply running the idnits
tool is not enough; please review the "Content Guidelines" on
authors.ietf.org. (Also note that the current idnits tool generates
some incorrect warnings; a rewrite is underway.)
  Some idnits noise exist, but only editorial changes needed.

15. Should any informative references be normative or vice-versa? See the IESG
Statement on Normative and Informative References.
  No.

16. List any normative references that are not freely available to anyone. Did
the community have sufficient access to review any such normative
references?
  The community has sufficient access to review such normative references.

17. Are there any normative downward references (see RFC 3967 and BCP
97) that are not already listed in the DOWNREF registry? If so,
list them.
  No.

18. Are there normative references to documents that are not ready to be
submitted to the IESG for publication or are otherwise in an unclear state?
If so, what is the plan for their completion?
  No.

19. Will publication of this document change the status of any existing RFCs? If
so, does the Datatracker metadata correctly reflect this and are those RFCs
listed on the title page, in the abstract, and discussed in the
introduction? If not, explain why and point to the part of the document
where the relationship of this document to these other RFCs is discussed.
  No.

20. 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 aspects of the document requiring IANA assignments are
associated with the appropriate reservations in IANA registries. Confirm
that any referenced IANA registries have been clearly identified. Confirm
that each newly created IANA registry specifies its initial contents,
allocations procedures, and a reasonable name (see RFC 8126).
  There was a long thread with the AD about registry naming/structure.
Aligned with his suggestions, the document lists IANA registries to be created,
with reasonable names, detailed specification of initial contents and procedures
for future allocations (expert review).

21. List any new IANA registries that require Designated Expert Review for
future allocations. Are the instructions to the Designated Expert clear?
Please include suggestions of designated experts, if appropriate.
  Tony Przygienda, Bruno Rijsman and Pascal Thubert are suggested as the
IANA Experts for the new registries.

22. RIFT is uniquely justified to have more than 5 authors given its wide
scope and long time in development of specification. The authors listed all
contributed significant ideas or parts of the spec or participated heavily
in formatting/editing of the draft over long periods of times. I recommend
to add each of the authors for the reasons given below:
Jordan did huge amount of lifting as editor incl. svg etc.
Pascal contributed tons, whole theoretical framework/language of fabric,
mobility, negative disaggregation fib especially, reworked whole flood
reduction.
Bruno wrote open source and was on all early calls, found FSM problems.
Dmitry was on all early calls, contributed lots practical considerations
from operation's side.
'Alankar (which will be added again) the same, on all early things,
contributed lots original ideas.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

IANA has completed its review of draft-ietf-rift-rift-20. If any part of this review is inaccurate, please let us know.

IANA has a question about the first and fourth actions requested in the IANA Considerations section of this document.

First, in the Service Name and Transport Protocol Port Number Registry located at:

https://www.iana.org/assignments/service-names-port-numbers/

the temporary registrations for:

Service Name: rift-lies
Port Number: 914
Transport Protocol: udp
Description: Routing in Fat Trees Link Information Elements
Assignee: IESG
Contact: IETF Chair
Reference: [ RFC-to-be ]

Service Name: rift-ties
Port Number: 915
Transport Protocol: udp
Description: Routing in Fat Trees Topology Information Elements
Assignee: IESG
Contact: IETF Chair
Reference: [ RFC-to-be ]

will be made permanent, their assignees and contacts updated, and their references changed to [ RFC-to-be ].

IANA Comment -> Would the authors be able to add the the templates from RFC 6335, Section 8.1 to Section 10.1 of this I-D?

Second, in the IPv4 Multicast Address Space registry group located at:

https://www.iana.org/assignments/multicast-addresses/

the temporary registration for:

Address: 224.0.0.121
Description: ALL_V4_RIFT_ROUTERS

will be made permanent and its reference changed to [ RFC-to-be ].

Third, in the IPv6 Multicast Address Space Registry group located at:

https://www.iana.org/assignments/ipv6-multicast-addresses/

the temporary registration for:

Address: FF02::A1F7
Description: ALL_V6_RIFT_ROUTERS

will be made permanent and its reference changed to [ RFC-to-be ].

Fourth, while the new top-level Routing in Fat Trees registry makes sense to IANA, the instructions in section 10.2 of the IANA Considerations Section appear to be contradictory. Section 10.2 says that "Allocation of new values is always performed via `Expert Review` action." However, nearly every registry in the subsequent section provides conflicting registration procedure instructions (see RFC8126). Which are the correct instructions for these registries?

In addition, it would be helpful to have explicit titles for the registries in each subsection of Section 10.2.

NOTE: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.

For definitions of IANA review states, please see:

https://datatracker.ietf.org/help/state/draft/iana-review

Thank you,

David Dong
IANA Services Sr. Specialist

The following Last Call announcement was sent out (ends 2024-03-05):

From: The IESG
To: IETF-Announce
CC: Zheng Zhang , aretana.ietf@gmail.com, draft-ietf-rift-rift@ietf.org, james.n.guichard@futurewei.com, rift-chairs@ietf.org, rift@ietf.org, zhang.zheng@zte.com.cn
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call:  (RIFT: Routing in Fat Trees) to Proposed Standard


The IESG has received a request from the Routing In Fat Trees WG (rift) to
consider the following document: - 'RIFT: Routing in Fat Trees'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2024-03-05. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  This document defines a specialized, dynamic routing protocol for
  Clos and fat tree network topologies optimized towards minimization
  of control plane state as well as minimization of configuration and
  operational complexity.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-rift-rift/


The following IPR Declarations may be related to this I-D:

  https://datatracker.ietf.org/ipr/2944/
  https://datatracker.ietf.org/ipr/3168/
  https://datatracker.ietf.org/ipr/3343/
  https://datatracker.ietf.org/ipr/3091/
  https://datatracker.ietf.org/ipr/3226/
  https://datatracker.ietf.org/ipr/3167/

Document History
1. Does the working group (WG) consensus represent the strong concurrence of a
few individuals, with others being silent, or did it reach broad agreement?
  The WG consensus is solid.

2. Was there controversy about particular points, or were there decisions where
the consensus was particularly rough?
  No.

3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
so, please summarize 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.

4. For protocol documents, are there existing implementations of the contents of
the document? Have a significant number of potential implementers indicated
plans to implement? Are any existing implementations reported somewhere,
either in the document itself (as RFC 7942 recommends) or elsewhere
(where)?
  Yes. At least two implementations existed.

Additional Reviews
5. Do the contents of this document closely interact with technologies in other
IETF working groups or external organizations, and would it therefore benefit
from their review? Have those reviews occurred? If yes, describe which
reviews took place.
  No. The contents of this document have no closely interact with technologies
in other IETF WG or external organizations.

6. Describe how the document meets any required formal expert review criteria,
such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.
  No formal review required.

7. If the document contains a YANG module, has the final version of the module
been checked with any of the recommended validation tools for syntax and
formatting validation? If there are any resulting errors or warnings, what is
the justification for not fixing them at this time? Does the YANG module
comply with the Network Management Datastore Architecture (NMDA) as specified
in RFC 8342?
  No.

8. Describe reviews and automated checks performed to validate sections of the
final version of the document written in a formal language, such as XML code,
BNF rules, MIB definitions, CBOR's CDDL, etc.
  Thrift compilers have successfully generated automatic code from the
Information Elements Schema defined in Appendix B, which are used in two
interoperable implementations.

Document Shepherd Checks
9. Based on the shepherd's review of the document, is it their opinion that this
document is needed, clearly written, complete, correctly designed, and ready
to be handed off to the responsible Area Director?
  This document is ready for publication.  The document shepherd has done a
complete and general review of the Document. All issues that were raised in the
working group have been addressed. A new version (-17) with nits modification
is going to be published. This document is ready to be submitted to IESG.

10. Several IETF Areas have assembled lists of common issues that their
reviewers encounter. For which areas have such issues been identified
and addressed? For which does this still need to happen in subsequent
reviews?
  The IETF Areas’ comments have been addressed.

11. What type of RFC publication is being requested on the IETF stream (Best
Current Practice, Proposed Standard, Internet Standard,
Informational, Experimental or Historic)? Why is this the proper type
of RFC? Do all Datatracker state attributes correctly reflect this intent?
  The intended status is Proposed Standards. It is indicated in the header.
It matches with the content of the Document which defines protocol procedures.
All Datatracker state attributes correctly reflect this intent.

12. Have reasonable efforts been made to remind all authors of the intellectual
property rights (IPR) disclosure obligations described in BCP 79? To
the best of your knowledge, have all required disclosures been filed? If
not, explain why. If yes, summarize any relevant discussion, including links
to publicly-available messages when applicable.
  Yes. All Authors and Contributors have made a statement regarding their
knowledge of IPR which would relate to this Document. Six IPR disclosures
have been made against this Document. The WG did not raise any issue with
the existence of these IPR.

13. Has each author, editor, and contributor shown their willingness to be
listed as such? If the total number of authors and editors on the front page
is greater than five, please provide a justification.
  The number of authors exceeds five. The sixth co-author Jordan Head is the
main editor of version 16. He did great job to improve the draft.

14. Document any remaining I-D nits in this document. Simply running the idnits
tool is not enough; please review the "Content Guidelines" on
authors.ietf.org. (Also note that the current idnits tool generates
some incorrect warnings; a rewrite is underway.)
  Some idnits noise exist, but only editorial changes needed.

15. Should any informative references be normative or vice-versa? See the IESG
Statement on Normative and Informative References.
  No.

16. List any normative references that are not freely available to anyone. Did
the community have sufficient access to review any such normative
references?
  The community has sufficient access to review such normative references.

17. Are there any normative downward references (see RFC 3967 and BCP
97) that are not already listed in the DOWNREF registry? If so,
list them.
  No.

18. Are there normative references to documents that are not ready to be
submitted to the IESG for publication or are otherwise in an unclear state?
If so, what is the plan for their completion?
  No.

19. Will publication of this document change the status of any existing RFCs? If
so, does the Datatracker metadata correctly reflect this and are those RFCs
listed on the title page, in the abstract, and discussed in the
introduction? If not, explain why and point to the part of the document
where the relationship of this document to these other RFCs is discussed.
  No.

20. 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 aspects of the document requiring IANA assignments are
associated with the appropriate reservations in IANA registries. Confirm
that any referenced IANA registries have been clearly identified. Confirm
that each newly created IANA registry specifies its initial contents,
allocations procedures, and a reasonable name (see RFC 8126).
  There was a long thread with the AD about registry naming/structure.
Aligned with his suggestions, the document lists IANA registries to be created,
with reasonable names, detailed specification of initial contents and procedures
for future allocations (expert review).

21. List any new IANA registries that require Designated Expert Review for
future allocations. Are the instructions to the Designated Expert clear?
Please include suggestions of designated experts, if appropriate.
  Tony Przygienda, Bruno Rijsman and Pascal Thubert are suggested as the
IANA Experts for the new registries.

Closed request for Early review by INTDIR with state 'Withdrawn': For now, as this document is at -12 and had "not ready/has issues" reviews from other directorates and has not been update since 5/25/2020, assume this document is dead for now.

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 1 November 2019.

(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?

  The intended status is Proposed Standards. It is indicated in the header.
  It matches with the content of the Document which defines protocol procedures.

(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:

    This document defines a specialized, dynamic routing protocol for Clos and fat-tree network topologies optimized towards minimization of configuration and operational complexity.

Working Group Summary:

    The RIFT WG supports the publication of this Document as a Proposed Standard RFC.

Document Quality:

    Several implementations of this technology exist.
    Many reviewers provide comments and suggestions.
    This document is clear and well-written.

Personnel:

    Zheng Zhang is the Document Shepherd.
    Alvaro Retana is the Responsible Area Director.

(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.

  This document is ready for publication.  The document shepherd has done a complete and general review of the Document.
  All issues that were raised in the working group have been addressed.
  A new version (-12) with nits modification is going to be published.
  This document is ready to be submitted to IESG.

(4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed?

  No concerns.

(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 such reviews needed.

(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 such concerns, all the outstanding issues have been resolved.

(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?

  All Authors and Contributors have made a statement regarding their knowledge of IPR which would relate to this Document.

(8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures.

  Six IPR disclosures have been made against this Document.
  The WG did not raise any issue with the existence of these IPR.

(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 WG consensus is solid.

(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.

  No errors were found on the ID nits check, only idnits noise.

(12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, YANG 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. With one update in version 12 of this document.

(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 8126).

  There was a long thread with the AD about registry naming/structure. Aligned with his suggestions, the document lists IANA registries to be created, with reasonable names, detailed specification of initial contents and procedures for future allocations (expert review).

(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.

  Tony Przygienda, Bruno Rijsman and Pascal Thubert are suggested as the IANA Experts for the new registries.

(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, YANG modules, etc.

  Thrift compilers have successfully generated automatic code from the Information Elements Schema defined in Appendix B, which are used in two interoperable implementations.

(20) If the document contains a YANG module, has the module been checked with any of the recommended validation tools (https://trac.ietf.org/trac/ops/wiki/yang-review-tools) for syntax and formatting validation? If there are any resulting errors or warnings, what is the justification for not fixing them at this time? Does the YANG module comply with the Network Management Datastore Architecture (NMDA) as specified in RFC8342?

  No.

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 1 November 2019.

(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?

  The intended status is Proposed Standards. It is indicated in the header.
  It matches with the content of the Document which defines protocol procedures.

(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:

    This document defines a specialized, dynamic routing protocol for Clos and fat-tree network topologies optimized towards minimization of configuration and operational complexity.

Working Group Summary:

    The RIFT WG supports the publication of this Document as a Proposed Standard RFC.

Document Quality:

    Several implementations of this technology exist.
    Many reviewers provide comments and suggestions.
    This document is clear and well-written.

Personnel:

    Zheng Zhang is the Document Shepherd.
    Alvaro Retana is the Responsible Area Director.

(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.

  This document is ready for publication.  The document shepherd has done a complete and general review of the Document.
  All issues that were raised in the working group have been addressed.
  A new version (-12) with nits modification is going to be published.
  This document is ready to be submitted to IESG.

(4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed?

  No concerns.

(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 such reviews needed.

(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 such concerns, all the outstanding issues have been resolved.

(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?

  All Authors and Contributors have made a statement regarding their knowledge of IPR which would relate to this Document.

(8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures.

  Six IPR disclosures have been made against this Document.
  The WG did not raise any issue with the existence of these IPR.

(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 WG consensus is solid.

(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.

  No errors were found on the ID nits check, only idnits noise.

(12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, YANG 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. With one update in version 12 of this document.

(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 8126).

  There was a long thread with the AD about registry naming/structure. Aligned with his suggestions, the document lists IANA registries to be created, with reasonable names, detailed specification of initial contents and procedures for future allocations (expert review).

(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.

  Tony Przygienda, Bruno Rijsman and Pascal Thubert are suggested as the IANA Experts for the new registries.

(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, YANG modules, etc.

  Thrift compilers have successfully generated automatic code from the Information Elements Schema defined in Appendix B, which are used in two interoperable implementations.

(20) If the document contains a YANG module, has the module been checked with any of the recommended validation tools (https://trac.ietf.org/trac/ops/wiki/yang-review-tools) for syntax and formatting validation? If there are any resulting errors or warnings, what is the justification for not fixing them at this time? Does the YANG module comply with the Network Management Datastore Architecture (NMDA) as specified in RFC8342?

  No.

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 1 November 2019.

(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?

  The intended status is Proposed Standards. It is indicated in the header.
  It matches with the content of the Document which defines protocol procedures.

(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:

    This document defines a specialized, dynamic routing protocol for Clos and fat-tree network topologies optimized towards minimization of configuration and operational complexity.

Working Group Summary:

    The RIFT WG supports the publication of this Document as a Proposed Standard RFC.

Document Quality:

    Several implementations of this technology exist.
    Many reviewers provide comments and suggestions.
    This document is clear and well-written.

Personnel:

    Zheng Zhang is the Document Shepherd.
    Alvaro Retana is the Responsible Area Director.

(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.

  This document is ready for publication.  The document shepherd has done a complete and general review of the Document.
  All issues that were raised in the working group have been addressed.
  A new version (-12) with nits modification is going to be published.
  This document is ready to be submitted to IESG.

(4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed?

  No concerns.

(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 such reviews needed.

(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 such concerns, all the outstanding issues have been resolved.

(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?

  All Authors and Contributors have made a statement regarding their knowledge of IPR which would relate to this Document.

(8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures.

  Six IPR disclosures have been made against this Document.
  The WG did not raise any issue with the existence of these IPR.

(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 WG consensus is solid.

(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.

  No errors were found on the ID nits check, only idnits noise.

(12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, YANG 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. With one update in version 12 of this document.

(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 8126).

  The document requests IANA actions.

(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.

(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, YANG modules, etc.

  Not applicable.

(20) If the document contains a YANG module, has the module been checked with any of the recommended validation tools (https://trac.ietf.org/trac/ops/wiki/yang-review-tools) for syntax and formatting validation? If there are any resulting errors or warnings, what is the justification for not fixing them at this time? Does the YANG module comply with the Network Management Datastore Architecture (NMDA) as specified in RFC8342?

  No.

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 1 November 2019.

(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?

  The intended status is Proposed Standards. It is indicated in the header.
  It matches with the content of the Document which defines protocol procedures.

(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:

    This document defines a specialized, dynamic routing protocol for Clos and fat-tree network topologies optimized towards minimization of configuration and operational complexity.

Working Group Summary:

    The RIFT WG supports the publication of this Document as a Proposed Standard RFC.

Document Quality:

    Several implementations of this technology exist.
    Many reviewers provide comments and suggestions.
    This document is clear and well-written.

Personnel:

    Zheng Zhang is the Document Shepherd.
    Alvaro Retana is the Responsible Area Director.

(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.

  This document is ready for publication.  The document shepherd has done a complete and general review of the Document.
  All issues that were raised in the working group have been addressed.
  A new version (-12) with nits modification is going to be published.
  This document is ready to be submitted to IESG.

(4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed?

  No concerns.

(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 such reviews needed.

(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 such concerns, all the outstanding issues have been resolved.

(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?

  All Authors and Contributors have made a statement regarding their knowledge of IPR which would relate to this Document.

(8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures.

  Six IPR disclosures have been made against this Document.
  The WG did not raise any issue with the existence of these IPR.

(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 WG consensus is solid.

(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.

  No errors were found on the ID nits check, only idnits noise.

(12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, YANG 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. With one update in version 12 of this document.

(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 8126).

  The document requests IANA actions.

(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.

  N/A.

(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, YANG modules, etc.

  Not applicable.

(20) If the document contains a YANG module, has the module been checked with any of the recommended validation tools (https://trac.ietf.org/trac/ops/wiki/yang-review-tools) for syntax and formatting validation? If there are any resulting errors or warnings, what is the justification for not fixing them at this time? Does the YANG module comply with the Network Management Datastore Architecture (NMDA) as specified in RFC8342?

  No.