Skip to main content

Last Call Review of draft-ietf-rtgwg-policy-model-27
review-ietf-rtgwg-policy-model-27-secdir-lc-harkins-2021-02-09-00

Request Review of draft-ietf-rtgwg-policy-model-03
Requested revision 03 (document currently at 31)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2020-06-20
Requested 2020-05-29
Requested by Jeff Tantsura
Authors Yingzhen Qu , Jeff Tantsura , Acee Lindem , Xufeng Liu
I-D last updated 2021-02-09
Completed reviews Yangdoctors Early review of -12 by Mahesh Jethanandani (diff)
Secdir Last Call review of -27 by Dan Harkins (diff)
Genart Last Call review of -15 by Francesca Palombini (diff)
Rtgdir Last Call review of -16 by John Scudder (diff)
Tsvart Last Call review of -15 by Tommy Pauly (diff)
Yangdoctors Last Call review of -29 by Mahesh Jethanandani (diff)
Rtgdir Last Call review of -29 by Jonathan Hardwick (diff)
Comments
Dear colleagues,

Hope everyone is safe and well!
As RTGWG is preparing for the WGLC for draft-ietf-rtgwg-policy-model we'd like to ask you to review the draft.

Many thanks!
Jeff & Chris
Assignment Reviewer Dan Harkins
State Completed
Request Last Call review on draft-ietf-rtgwg-policy-model by Security Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/secdir/hblYexZymMRS3JO7e8nXmfmIt6U
Reviewed revision 27 (document currently at 31)
Result Ready
Completed 2021-01-15
review-ietf-rtgwg-policy-model-27-secdir-lc-harkins-2021-02-09-00
   Hello!

   I have reviewed draft-ietf-rtgwg-policy-model-027 as part of the security
directorate's ongoing effort to review all IETF documents being processed
by the IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

   This draft defines a YANG model for routing policy configuration. It
does not attempt to define every possible configuration but, instead,
some common policy configurations that are used presently. I am not a
YANG guy and will defer to the relevant doctors on that matter but the
draft looks like it adequately describes the subset it set out to.

   The security considerations note that data defined in the document are
to be accessed using either SSH or TLS (1.3!). Kudos to authors for
pointing out data nodes that are sensitive and need special attention.
The language should be adequate for an implementer to take heed.

   The summary of the review is READY.

   regards,

   Dan.

-- 
"The object of life is not to be on the side of the majority, but to
escape finding oneself in the ranks of the insane." -- Marcus Aurelius