Subject: [v6ops] shepherd write-up for draft-ietf-v6ops-nd-cache-init

From: JORDI PALET MARTINEZ <[email-masked]>
Date: Tue, 14 Jul 2020 13:48:18 +0200

=== Submitted as per RFC4858 (3.1)

(1) The document aims for Information status, as indicated in the title page header. This seems appropriate as it is not describing a new protocol but instead discussing details of an existing one, problems and possible mitigations. A "companion" protocol update document exists in 6man (draft-ietf-6man-grand).

(2) IESG approval announcement

Technical Summary:

This document discusses how the neighbor discovery (RFC4861) state machine on a first-hop router is causing user-visible connectivity issues when a new (not being seen on the network before) IPv6 address is being used.

Working Group Summary:

There were no issues during the WG process, on the other way around, consensus was clear.

Document Quality:

The document reports existing and know issues and several vendors have workarounds. It has been approved by v6ops, having successfully passed the last-call.

Personnel:

The document shepherd is Jordi Palet Martinez
The responsible area director is Warren Kumari

(3) Shepherd's review

Before being assigned as shepherd for this document , I was already following the discussion of the document and supported adopting it as WG item. Anyway, as shepherd, I've re-read all the discussion in the mailing list, which started with the typical discussion about separating the problem statement from solution approach and if it belongs to v6ops or 6man and if it requires an errata or update to RFC4861. All has been cleared by the author, which has quickly reacted to all the inputs. I did one more complete review, sent some final typos/editorial inputs to the author, and I believe the document is ready for publication.

(4) Shepherd's concerns

I don't have any concerns about the depth or breadth of the reviews that have been performed. There was sufficient discussion, WG review and no objections.

(5) Other Reviews

I don't think any additional review is required for this document.

(6) Shepherd's Concerns or issues

I don't have any concerns or issues with this document.

(7) IPR disclosures

The author has publicly acknowledged in the WG that there are no known IPRs about this document.

(8) IPRs referencing this document

There are no known IPRs referencing this document, neither was any relevant discussion in the WG.
There is a statement related to the companion document:
https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-6man-grand

(9) WG consensus strength

The document discussion in v6ops had sufficient participation and discussion, received broad support and no objections.

(10) Document conflicts

There was no indication of discontent during the document progress in the WG.

(11) ID nits

No nits found.

(12) No formal review required. 

(13) Document references

All the document references have been correctly identified as normative and informative.

(14) Normative references to other documents

There is a normative reference to a companion document in 6man, ietf-6man-grand. This document has been already adopted as WG item by 6man, and at the time being, is progressing with no objections. Furthermore, it has been reported as something already implemented and tested by at least a vendor.

I understand that both documents will need to be processed/published together by the RFC Editor, as it will not make too much sense to publish only this document and not ietf-6man-grand.

(15) There are no conflicting downward normative references. 

(16) No further documents updated/obsoleted by this one. 

(17) No IANA reservations. 

(18) No IANA registries that require Expert Review. 

(19) No formal language.

(20) No YANG modules.

Regards,
Jordi
@jordipalet

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.