[Teas] Genart telechat review of draft-ietf-teas-rsvp-egress-protection-14

Stewart Bryant <stewart.bryant@gmail.com> Mon, 05 March 2018 19:32 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: teas@ietf.org
Delivered-To: teas@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EFFB12DA6B; Mon, 5 Mar 2018 11:32:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: gen-art@ietf.org
Cc: draft-ietf-teas-rsvp-egress-protection.all@ietf.org, ietf@ietf.org, teas@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.74.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152027834027.31747.14180175871085676142@ietfa.amsl.com>
Date: Mon, 05 Mar 2018 11:32:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/PRosk-yQ9vLZKIqZpY7EKFiUNJ4>
Subject: [Teas] Genart telechat review of draft-ietf-teas-rsvp-egress-protection-14
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 19:32:27 -0000

Reviewer: Stewart Bryant
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 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

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-teas-rsvp-egress-protection-??
Reviewer: Stewart Bryant
Review Date: 2018-03-05
IETF LC End Date: 2018-02-27
IESG Telechat date: 2018-03-08

Summary: This is much improved since the earlier version I reviewed.

I do have a concern about the use of the term "egress" when I think that it
should be "egress node" or some such other network object.

Major issues: None

Minor issues: None

Nits/editorial comments:

The authors often use the term egress on its own when I think they mean egress
PE or egress node or egress LSR. If my English concern is correct, this should
be addressed before this goes to the RFC Editor else  Auth48 will be a painful
process for all concerned.