A YANG Data Model for the Virtual Router Redundancy Protocol (VRRP)
draft-ietf-rtgwg-yang-vrrp-11

[Ballot comment]
I have to refer to an appendix to find the full tree diagram. https://tools.ietf.org/html/draft-ietf-rtgwg-yang-vrrp-08#appendix-A, with no forward reference.
Why don't you have the full tree in a new section, as you did in https://tools.ietf.org/html/draft-ietf-rtgwg-yang-rip-08#section-3

[Ballot comment]
Please consider updating the example in appendix B to conform to the IAB guidance found at . This would involve changing the example to use IPv6 instead of IPv4, or adding an IPv6 example in addition to the IPv4 example.

[Ballot comment]
- I support Kathleen's DISCUSS.

- I like the way sections 2.2 and 2.3 are constructed. Thanks.
In section 2.4 that's a pity that we don't see which per instance oper states and stats are available.

        +--ro
            +--ro statistics
              +--ro


I have to refer to an appendix to find the answer https://tools.ietf.org/html/draft-ietf-rtgwg-yang-vrrp-08#appendix-A
Why don't you have the full tree as from the appendix in 2.X?

- No need to include the WG chairs in the YANG module, as per 6087bis

        WG Chair: Jeff Tantsura
                 

        WG Chair: Chris Bowers
                 


- The following two references must point to the working group documents

  [I-D.bjorklund-netmod-rfc7223bis]
              Bjorklund, M., "A YANG Data Model for Interface
              Management", draft-bjorklund-netmod-rfc7223bis-00 (work in
              progress), August 2017.

  [I-D.bjorklund-netmod-rfc7277bis]
              Bjorklund, M., "A YANG Data Model for IP Management",
              draft-bjorklund-netmod-rfc7277bis-00 (work in progress),
              August 2017.

- Thanks for the appendix B. It's always useful.
Note: I have not validated the instance.

[Ballot discuss]
Hello, Thanks for your work on this draft.  Could you please update the Security Considerations to use the current template?  I believe this is the current, but that should be confirmed:
https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-10#page-52

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

The IANA Services Operator has completed its review of draft-ietf-rtgwg-yang-vrrp-07. If any part of this review is inaccurate, please let us know.

The IANA Services Operator has a question about one of the actions requested in the IANA Considerations section of this document.

The IANA Services Operator understands that, upon approval of this document, there are two actions which we must complete.

First, in the ns registry of the IETF XML Registry located at

https://www.iana.org/assignments/xml-registry/

a single new registration is to be made:

ID: yang:ietf-vrrp
URI: urn:ietf:params:xml:ns:yang:ietf-vrrp
Filename: [ TBD-at-registration ]
Reference: [ RFC-to-be ]

Because this registry requires Expert Review [RFC8126] for registration, we've contacted the IESG-designated expert in a separate ticket to request approval. Expert review should be completed before your document can be approved for publication as an RFC.

Second, in the YANG Module Names registry on the YANG Parameters registry page located at

https://www.iana.org/assignments/yang-parameters/

a single new YANG Module is to be registered:

Name: ietf-vrrp
File: [ TBD-at-registration ]
Maintained by IANA?:
Namespace: urn:ietf:params:xml:ns:yang:ietf-vrrp
Prefix: vrrp
Module:
Reference: [ RFC-to-be ]
Notes:

IANA Question --> What should be the value for "Maintained by IANA?" for this new YANG module?

The IANA Services Operator understands that these are the only two actions required upon approval of this document.

Thank you,

Amanda Baber
Lead IANA Services Specialist

The following Last Call announcement was sent out (ends 2017-12-12):

From: The IESG
To: IETF-Announce
CC: Yingzhen Qu , rtgwg-chairs@ietf.org, akatlas@gmail.com, yingzhen.qu@huawei.com, draft-ietf-rtgwg-yang-vrrp@ietf.org, rtgwg@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (A YANG Data Model for Virtual Router Redundancy Protocol (VRRP)) to Proposed Standard


The IESG has received a request from the Routing Area Working Group WG
(rtgwg) to consider the following document: - 'A YANG Data Model for Virtual
Router Redundancy Protocol (VRRP)'
  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
ietf@ietf.org mailing lists by 2017-12-12. 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 describes a data model for Virtual Router Redundancy
  Protocol (VRRP).  Both version 2 and version 3 of VRRP are covered.




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

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-vrrp/ballot/


No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information:
    draft-bjorklund-netmod-rfc7277bis: A YANG Data Model for IP Management (None - IETF stream)
    draft-bjorklund-netmod-rfc7223bis: A YANG Data Model for Interface Management (None - IETF stream)
    draft-ietf-netmod-revised-datastores: Network Management Datastore Architecture (None - IETF stream)

(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 Standard'. 
The type of RFC is properly indicated in the title page header.
This document describes the VRRP YANG data model.

(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 describes a YANG data model for Virtual Router Redundancy (VRRP), and both version 2 and 3 are covered.
VRRP provides higher resiliency by specifying an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The protocol has been implemented and deployed by most of network equipment vendors.  Providing a standard YANG model will facilitate the protocol configuration and status in a vendor independent way.

Working Group Summary
This draft has been thoroughly discussed in the WG.
The draft adoption and progress has received full support from the WG.
All comments have been addressed.  The draft is ready for publication.

Document Quality
The draft went to many rounds of reviews by YANG-Doctors as well as implementers, which resulted in a very high quality document.
It has been reported that Huawei has implemented the model, and multiple vendors have shown significant interest in the topic. 

Personnel
Yingzhen Qu is the Document Shepherd.
Alia Atlas 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.
The draft has been thoroughly reviewed by the Shepherd. Nits and review comments have been addressed in revision 04.

(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.
The draft has been reviewed by Routing Directorate QA and YANG Doctors.

(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.
  N/A

(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.  Every author has confirmed. 

(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR disclosures.
Yes.  The authors have been asked (and they answered) on the WG list about IPR at every step of the process.  There haven't been any concerns raised on the list.

(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 draft adoption and progress had received full support from the WG.
 
(10) 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.

(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 nits in review comments have been addressed in revision 04.

(12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, media type, and URI type reviews.
The draft has been reviewed by YANG-Doctors, all the comments received have been properly addressed. 

(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 (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.
The state of other documents remains unchanged.

(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).
This draft registers a URI in the IETF XML registry and a YANG module in the YANG Module Names registry.

(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, etc.
The draft has been reviewed by YANG-Doctors, all the comments received have been properly addressed.