Re: [Gen-art] Gen-ART review of draft-betts-itu-oam-ach-code-point-04

"Adrian Farrel" <> Mon, 07 May 2012 13:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1A8F921F8637; Mon, 7 May 2012 06:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lMYM1HLaSzVW; Mon, 7 May 2012 06:49:15 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 4094B21F8630; Mon, 7 May 2012 06:49:14 -0700 (PDT)
Received: from (localhost.localdomain []) by (8.13.8/8.13.8) with ESMTP id q47DnCcp012234; Mon, 7 May 2012 14:49:12 +0100
Received: from 950129200 ( []) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id q47DnAow012225 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 May 2012 14:49:11 +0100
From: Adrian Farrel <>
To: 'Christer Holmberg' <>,
References: <>
In-Reply-To: <>
Date: Mon, 07 May 2012 14:49:10 +0100
Message-ID: <006601cd2c58$2f326b30$8d974190$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIMbPmvAujJQq4KsAzDKDfxoFlAaJY/0X7Q
Content-Language: en-gb
Subject: Re: [Gen-art] Gen-ART review of draft-betts-itu-oam-ach-code-point-04
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 07 May 2012 13:49:16 -0000

All (copying the IESG),

I do sincerely welcome all reviews of all I-Ds that I sponsor or where I am the
responsible AD. I even mainly welcome them when I am an author.

However, when Directorate or Review Team reviews come in so long after the end
of IETF Last Call, and especially when they arrive after the I-D has been
updated to address last call comments, I do grind my teeth a bit.

Additionally, when Directorate or Review Team reviews are repeated and bring up
new issues (even minor ones) that were in the document at the time of the first
review but didn't warrant a comment at that time, I feel like I am being asked
for a rock.

Anyway, thanks Chris for caring enough to read the document for a second time,
and see in line for answers.

> Summary: The draft is ready for publication, with a couple of editorial nits.
> Major issues: -
> Minor issues: -
> Nits/editorial comments:
> (The comments also applied to the -03 version, and I apologize for
> not bringing them up when I reviewed that version.)
> - General: G-ACh is mentioned throughout the document, but only in 
> section 4 is there a reference to RFC 5586. I suggest to add a reference
> on first occurrence at least to section 1. It would probably be good also
> in section 3.

Added RFC Editor note

Section1 para 2

s/Generic Associated Channel (G-ACh) Type/Generic Associated Channel (G-ACh)
Type [RFC5586]

> - Section 1: What is the purpose of the last paragraph, talking about IETF
>  Experts not agreeing? For someone who has not followed the work, it
>  seems as little strange.

I am not sure how to answer you without giving a long and detailed history of
this work covering the last four years. Such a history is without doubt

You might read the referenced I-D for an alternate viewpoint. Or you might speak
privately with any number of people involved with this work.

In summary, this text is necessary to obtain consensus on the publication of
this document, and is agreed by the document author.

> - Section 3: The text says "The G-ACh Type assigned by this document". I guess
> it would be better to say e.g. "based on this document".

Well, of course, "based on" is also not right :-)

One might say, "...assigned by the IANA as a result of the request contained in
this document."
To me that is over-baked. What is more, during late-stage IANA processing, the
"request" text in I-Ds is replaced with "action" text that describes what action
IANA has taken.

Common usage is that a document that is approved for publication and that makes
an IANA request is the document that made the assignment or created the

So we won't make any change for that.