[Gen-art] Genart last call review of draft-ietf-rmcat-nada-11

[Joel Halpern via Datatracker]

Reviewer: Joel Halpern
Review result: Almost 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-rmcat-nada-11
Reviewer: Joel Halpern
Review Date: 2019-08-05
IETF LC End Date: 2019-08-12
IESG Telechat date: Not scheduled for a telechat

Summary: This document is almost ready for publication as an Experimental RFC

Major issues:
   It is unclear reading this RFC how the observation information is to be
   communicated from the receiver to the sender.  At first I thought it was to
   use the RTP Receiver report.  But there is no description of how to map the
   fields to that report.   Then section 5.3 describes requirements for a
   reporting mechanism, but does not seem to actually define one.   Thus, I am
   left unclear how independent interoperable implementations of this draft can
   be created.

Minor issues:
The document has 7 front page authors.   The shepherd writeup does not
comment on this. The shepherd writeup seems quite sparse.  II would have
expected some reference to the experimental behavior described in the draft.

This comment is just to confirm that I am reading the draft correctly.  It
looks like when the observed delay cross the delay boundary, the reporting
system reports using a smaller delay than actually approved (slightly more
than 1/9th of observed delay when delay is 3*QTH).  I presume this is
intentional, and that the various analysis pointed to evaluate the risks of
such false reporting?

Is it intentional in section 4.3 in the pseudo-code that the rate clipping
(to keep the rate between RMIN and RMAX) is only applied to the gradual
rate change, not to the accelerated rate change?  The later code says that
the clipping is always applied, which is what I would expect.

Nits/editorial comments:


___
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-ospf-xaf-te-06

[Alissa Cooper]

Roni, thanks for your review. I entered a No Objection ballot.

Alissa


> On Jun 30, 2019, at 7:27 AM, Roni Even via Datatracker  
> wrote:
> 
> Reviewer: Roni Even
> 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-ospf-xaf-te-??
> Reviewer: Roni Even
> Review Date: 2019-06-30
> IETF LC End Date: 2019-07-11
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary: The document is ready for publication as a standard track RFC
> 
> Major issues:
> 
> Minor issues:
> 
> Nits/editorial comments:
> 
> 
> ___
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

___
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-lamps-cms-shakes-11

[Alissa Cooper]

Vijay, thanks for your review. I entered a No Objection ballot.

Alissa


> On Jun 21, 2019, at 11:30 AM, Vijay Gurbani via Datatracker 
>  wrote:
> 
> Reviewer: Vijay Gurbani
> 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-lamps-cms-shakes-??
> Reviewer: Vijay K. Gurbani
> Review Date: 2019-06-21
> IETF LC End Date: 2019-07-03
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary: This draft is ready for publication as a standards track document.
> 
> Major issues: 0
> 
> Minor issues: 0
> 
> Nits/editorial comments: 0
> 
> 
> ___
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

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

Re: [Gen-art] [babel] Genart last call review of draft-ietf-babel-applicability-06

[Alissa Cooper]

Joel, thanks for your review. Juliusz, thanks for your responses. I think the 
phrasing in 2.2 is clear enough as-is. I entered a No Objection ballot.

Alissa


> On Jul 7, 2019, at 11:06 AM, Joel Halpern Direct  
> wrote:
> 
> I do not consider this a show-stopper (I listed it as a nit / editorial), but 
> at least the -07 text does not look better in this regard.
> 
> In my experience, if this were indeed mathematics, one would talk about a 
> metric (how one measures) and a distance (the result of applying the measure. 
>  E.g. Given two points in a metric space, with a distance between them of d, 
> ...  Or more verbosely, given a space with a metric M, the distance between 
> two points a and b is M(A, b).
> 
> Yours,
> Joel
> 
> On 7/7/19 10:26 AM, Juliusz Chroboczek wrote:
>> Dear Joel,
>> Thank you very much for your kind review.
>>> Nits/editorial comments:
>>>In section 2.2, in talking about "metric M", if I have understood 
>>> properly,
>>>I think it would be clearer if you referred to "metric value M".
>> This section has been expanded with human-readable text and a reference to
>> a research paper, and should therefore now be easier to understand.
>> I have, however, decided to follow the usual style of mathematical
>> writing, and have therefore chosen not to follow your advice.  I hope that
>> is okay.
>> Thanks again,
>> -- Juliusz
>> ___
>> babel mailing list
>> ba...@ietf.org
>> https://www.ietf.org/mailman/listinfo/babel
> 
> ___
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

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