[Gen-art] Review Assignments

2020-10-02 Thread Jean Mahoney via Datatracker
Hi all,

The following reviewers have assignments:

Last calls:

Reviewer   Type  LC end Draft
Brian CarpenterLast Call 2020-10-15 
draft-ietf-tls-external-psk-importer-05
Francis Dupont Last Call 2020-08-26 draft-ietf-mpls-spl-terminology-04
Wassim Haddad  Last Call 2020-09-30 draft-ietf-ccamp-wson-yang-26
Gyan MishraLast Call 2020-10-01 draft-ietf-idr-tunnel-encaps-19
Suhas Nandakumar   Last Call 2020-08-26 
draft-ietf-spring-srv6-network-programming-23
Ines RoblesLast Call 2020-10-08 
draft-ietf-opsawg-model-automation-framework-06
Robert Sparks  Last Call 2020-10-02 
draft-ietf-lpwan-schc-over-lorawan-10
Peter Yee  Last Call 2020-10-12 draft-ietf-dots-server-discovery-11

Next in the reviewer rotation:

  Tim Evens
  David Schinazi
  Francis Dupont
  Suhas Nandakumar
  Francesca Palombini
  Christer Holmberg
  Dale Worley
  Pete Resnick
  Roni Even
  Dan Romascanu

The LC and Telechat review templates are included below:
---

-- Begin LC Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End LC Template --

-- Begin Telechat Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



___
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art


Re: [Gen-art] Genart last call review of draft-ietf-detnet-flow-information-model-10

2020-10-02 Thread Balázs Varga A
Hi Jouni,
Many thanks for your review.
I will correct the editorial comments.
Thanks and cheers
Bala'zs

-Original Message-
From: Jouni Korhonen via Datatracker  
Sent: Friday, September 11, 2020 9:40 PM
To: gen-art@ietf.org
Cc: draft-ietf-detnet-flow-information-model@ietf.org; last-c...@ietf.org; 
det...@ietf.org
Subject: Genart last call review of draft-ietf-detnet-flow-information-model-10

Reviewer: Jouni Korhonen
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area Review Team 
(Gen-ART) reviews all IETF documents being processed by the IESG for the IETF 
Chair.  Please treat these comments just like any other last call comments.

For more information, please see the FAQ at

.

Document: draft-ietf-detnet-flow-information-model-??
Reviewer: Jouni Korhonen
Review Date: 2020-09-11
IETF LC End Date: 2020-09-11
IESG Telechat date: Not scheduled for a telechat

Summary:
This informational document is ready for publication with some editorial nits.

Major issues:
None.

Minor issues:
None.

Nits/editorial comments:

1) Line 210:   remove the excess full stop after "Section 6"
2) Section 1.1 lines 221 to 226. I do not see a reason to the intro text here..
It will read odd after a while when things move on. I recommend leaving only 
the following text with some rewording:
  "Therefore, the DetNet flow and service
information models described in this document are based on
[IEEE8021Qcc], which is an amendment to [IEEE8021Q].
This document specifies flow and service information models only."
3) Line 853: YANG is referred without a reference. In general, the YANG model 
gets mentioned for the first time in the summary as "These models are used as 
input for the YANG model". That came a bit out of sudden here and a some more 
context would be nice to have.


___
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art


[Gen-art] Genart last call review of draft-ietf-lpwan-schc-over-lorawan-10

2020-10-02 Thread Robert Sparks via Datatracker
Reviewer: Robert Sparks
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

.

Document: draft-ietf-lpwan-schc-over-lorawan-10
Reviewer: Robert Sparks
Review Date: 2020-10-02
IETF LC End Date: 2020-10-02
IESG Telechat date: Not scheduled for a telechat

Summary: Ready for publication as a proposed standard but with nits to consider
before publication

Nits/editorial comments:

The abstract says "This is called a profile." It would be better to say
something like "This document specifies a profile of RFC8724."

What does "other Internet networks" mean? Please replace the phrase with
something more descriptive.

The word "efficient" in the last sentence of the introduction is puzzling.
Could it simply be removed?

As the shepherd report notes, there are figures that need to be reworked to
satisfy column constraints.



___
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art


[Gen-art] Genart last call review of draft-ietf-idr-tunnel-encaps-19

2020-10-02 Thread Gyan Mishra via Datatracker
Reviewer: Gyan Mishra
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

.

Document: draft-ietf-idr-tunnel-encaps-??
Reviewer: Gyan Mishra
Review Date: 2020-10-02
IETF LC End Date: 2020-10-01
IESG Telechat date: Not scheduled for a telechat

Summary:
   This draft updates RFC 5512 is which was never used in production.
This document deprecates the original RFC 5512
   Encapsulation SAFI used for GRE encapsulation type only and defined extended
   community attributes  (which has never been used in production) , and
   specifies semantics for the attribute when it is carried in UPDATEs of
   certain other SAFIs.  This document adds support for additional Tunnel
   Types, and allows a remote tunnel endpoint address to be specified for each
   tunnel.  This document also provides support for specifying fields of any
   inner or outer encapsulations that may be used by a particular tunnel.

This document is well written and clearly defines all the tunnel encapsulation
attributes that exist today. This draft modification of the usage of the tunnel
encapsulation attribute is backwards compatible so does not impact the existing
deployments of the tunnel encapsulation types such as vxlan,vxlan GPE, NVGRE,
MPLS over GRE, L2TPV3.

Major issues:
None

Minor issues:
Is tunnel type RFC 7510 MPLS over UDP supported.  Also RFC 8663 SR-MPLS over IP
for SRv6 and SR-MPLS interoperability where MPLS over GRE RFC 4023 is used or
RFC 7510 MPLS over UDP and outer encapsulation is IPv6 for SRv6 forwarding
plane to tunnel SR-MPLS.

Nits/editorial comments:
As this update is backwards compatible to tunnel encapsulation attributes
deployed today is there any code upgrade for vendor implementation required now
for router vendors to support the new encapsulation attributes TLV and Sub TLVs
and extended community attributes defined with this draft.



___
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art


[Gen-art] Genart last call review of draft-ietf-idr-tunnel-encaps-19

2020-10-02 Thread Gyan Mishra via Datatracker
Reviewer: Gyan Mishra
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

.

Document: draft-ietf-idr-tunnel-encaps-??
Reviewer: Gyan Mishra
Review Date: 2020-10-02
IETF LC End Date: 2020-10-01
IESG Telechat date: Not scheduled for a telechat

Summary:
   This draft updates RFC 5512 is which was never used in production.
This document deprecates the original RFC 5512
   Encapsulation SAFI used for GRE encapsulation type only and defined extended
   community attributes  (which has never been used in production) , and
   specifies semantics for the attribute when it is carried in UPDATEs of
   certain other SAFIs.  This document adds support for additional Tunnel
   Types, and allows a remote tunnel endpoint address to be specified for each
   tunnel.  This document also provides support for specifying fields of any
   inner or outer encapsulations that may be used by a particular tunnel.

This document is well written and clearly defines all the tunnel encapsulation
attributes that exist today. This draft modification of the usage of the tunnel
encapsulation attribute is backwards compatible so does not impact the existing
deployments of the tunnel encapsulation types such as vxlan,vxlan GPE, NVGRE,
MPLS over GRE, L2TPV3.

Major issues:
None

Minor issues:
Is tunnel type RFC 7510 MPLS over UDP supported.  Also RFC 8663 SR-MPLS over IP
for SRv6 and SR-MPLS interoperability where MPLS over GRE RFC 4023 is used or
RFC 7510 MPLS over UDP and outer encapsulation is IPv6 for SRv6 forwarding
plane to tunnel SR-MPLS.

Nits/editorial comments:
As this update is backwards compatible to tunnel encapsulation attributes
deployed today is there any code upgrade for vendor implementation required now
for router vendors to support the new encapsulation attributes TLV and Sub TLVs
and extended community attributes defined with this draft.



___
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art