Hi, Jari the points you have made are supported by the work done in GROW on this draft. Specifically, #1 there is consensus behind the draft, time was spent making sure it covered the right points which had consensus. On #2 it does seem that the confusion comes from the use of the first person in the draft. By changing the grammar to definitive statements makes the document stronger, and continues to accurately represent the consensus reached during the work on the text. An example of the changes would be: Change: "The authors note that due to the distributed nature and restricted visibility of the steering of BGP policies, this second step is deemed to not identify the origin of the problem with guaranteed accuracy.” To: "Due to the distributed nature and restricted visibility of the steering of BGP policies, this second step does not identify the origin of the problem with guaranteed accuracy." Peter On 8/20/15, 3:34 PM, "GROW on behalf of Jari Arkko" <grow-bounces@xxxxxxxx on behalf of jari.arkko@xxxxxxxxx> wrote: >After some more staring of the data tracker settings, you are of course completely correct, >Robert :-) The document is marked as having IETF consensus setting, so the text that you >quoted will get inserted into the RFC. > >Pardon my mistake in assuming it wasn’t. > >On the IESG call we had a discussion about this issue. We saw two separate questions: > >1) Substance: Is there a consensus behind the document’s recommendations? The sponsoring AD >and the IESG believes so. > >2) Editorial: Is it appropriate to use the “the authors recommend…” form for IETF-level >consensus statements? The sponsoring AD took your comment about the formulation >(also recommended by other ADs) and will work with the author to revise the document. >However, this matter is indeed editorial, i.e., a Comment rather than a Discuss level >requirement from the IESG. > >So the document will be approved, after some editorial modifications, and will become >an RFC. > >Jari > >_______________________________________________ >GROW mailing list >GROW@xxxxxxxx >https://www.ietf.org/mailman/listinfo/grow