Re: [apps-discuss] [appsdir] Responding to Applications Area Directorate reviews

["Murray S. Kucherawy" <[e-mail]>]

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of Dave Crocker
> Sent: Wednesday, April 11, 2012 8:40 AM
> To: S Moonesamy
> Cc: [e-mail]; [e-mail]
> Subject: Re: [apps-discuss] [appsdir] Responding to Applications Area Directorate reviews
> 
> > In plain English, this means that the comments in the review does not
> > bear more weight than a comment submitted by an individual during a
> > Last Call.
> 
> It might be worth adding simple language like this to our material,
> including the apps area review team web page AND the template.
> 
> The essence of directorate-based reviews is perspective, not authority.
> 
> In our case, it supplies a review from someone with an applications-
> oriented perspective.  What should matter, therefore, are the merits of
> the review and not the body "authorizing" it.

I think that's a laudable goal, but there are constant reminders that directorate reviews at least appear to carry more weight since their association with authority (the ADs in particular) is difficult to obscure.  Often I see DISCUSSes posted based solely on the fact that a review team or directorate did a review but it was not addressed.  Further, those reviews are referenced in the DISCUSS as (for example) "the review done by Murray Kucherawy of the Applications Directorate", rather than just by name.

It's true that we're volunteers, but being appointed to the directorate does mean someone thinks you're an expert at something.

This paragraph of SM's message captures it better, I think, though I would change the word "veto" to something else:

The Applications Area Directors may or may not agree with the comments of the AppsDir reviewer.  The  Applications Area Directorate does not have any veto power on a draft.  It is suggested that the
author(s) asks the document shepherd (RFC 4858) or the Area Director who sponsored the draft for guidance about IETF process, changes that should be made, whether to post a new revision, etc.

-MSK