Last Call Review of draft-ietf-pals-redundancy-spe-02

Request Review of draft-ietf-pals-redundancy-spe
Requested rev. no specific revision (document currently at 03)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2015-10-20
Requested 2015-10-08
Authors Jie Dong, Haibo Wang
Draft last updated 2015-12-14
Completed reviews Genart Last Call review of -02 by Robert Sparks (diff)
Secdir Last Call review of -02 by Joseph Salowey (diff)
Opsdir Last Call review of -02 by Linda Dunbar (diff)
Rtgdir Early review of -02 by He Jia (diff)
Assignment Reviewer Robert Sparks
State Completed
Review review-ietf-pals-redundancy-spe-02-genart-lc-sparks-2015-12-14
Reviewed rev. 02 (document currently at 03)
Review result Almost Ready
Review completed: 2015-12-14


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-pals-redundancy-spe-02
Reviewer: Robert Sparks
Review Date: 16 Oct 2015
IETF LC End Date: 19 Oct 2015
IESG Telechat date: 22 Oct 2015

Summary: Almost ready for publication as PS but with issues that need to 
be discussed/addressed

This document is hard to read. It is more acronym-laden than it
needs to be.

There is a process issue that the IESG should pay attention to.
The shepherd writeup says this:

   "There is one IPR declaration (1911) raised in November 2012 against
    an early version of the draft.  There was no discussion in the WG
    related to this."

That happens sometimes, but it's much better to have a real indication
that the group considered the disclosure and explicitly decided not to
change directions.

The last sentence of the 2nd paragraph (declaring multi-homing on both
sides of an S-PE out of scope) should be moved earlier in the document.
The introduction and perhaps even the abstract can be clearer about
what _is_ in scope.

It needs to be clearer where the normative description of behavior is.
I think you're intending it to be the first part of section 3. I have
not worked through the references enough to ensure that it is complete.

The third paragraph starts off "In general, ...". Are there any
specific cases where the requirements that follow do not hold? If so,
there needs to be more description. If not, please delete "In general,".

Are sections 3.1 and 3.2 supposed to be only examples? Would the
specification of the protocol be complete if they were deleted? If not,
something needs to be moved up into the main part of section 3.
For instance, is the SHOULD at the end of 3.1 a requirement placed by
this document, or is it restating a requirement from somewhere else?
Similarly, please inspect the SHOULD in the second paragraph of 3.2.

I also suggest moving 3.1 and 3.2 into their own section, clearly
labeling them as examples.

Is it worth more explanation in the document why you've added the
MUST NOT in the first paragraph of section 3?

The security considerations section only points off to other documents.
Most of those just point to each other. Chasing it back, there's some
meat in the security considerations section of 4447, and some in 5085,
but it's a real chase to find what's relevant.  Please consider calling
out what an implementer needs to consider explicitly here.