Re: [bmwg] IESG Interaction

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 29 July 2010 13:54 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: bmwg@core3.amsl.com
Delivered-To: bmwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 458F23A679F for <bmwg@core3.amsl.com>; Thu, 29 Jul 2010 06:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level:
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09lRvNzEZFNq for <bmwg@core3.amsl.com>; Thu, 29 Jul 2010 06:54:04 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id B224A3A67EF for <bmwg@ietf.org>; Thu, 29 Jul 2010 06:54:03 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.55,280,1278302400"; d="scan'208,217"; a="200273804"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 29 Jul 2010 09:54:26 -0400
X-IronPort-AV: E=Sophos; i="4.55,280,1278302400"; d="scan'208,217"; a="495615631"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 29 Jul 2010 09:54:25 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB2F25.844637A0"
Date: Thu, 29 Jul 2010 15:54:08 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04023D1C01@307622ANEX5.global.avaya.com>
In-Reply-To: <02C94FA7F698FC4093BA0EED57834E250759CFF9@ASHEVS008.mcilink.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [bmwg] IESG Interaction
Thread-Index: AcsvHGH2VuZYnh4hSo6sB1/jNJ4oCgAAEXiwAAIsITA=
References: <02C94FA7F698FC4093BA0EED57834E250759CF65@ASHEVS008.mcilink.com><201007291248.o6TCmVN1012751@klpd017.kcdc.att.com> <02C94FA7F698FC4093BA0EED57834E250759CFF9@ASHEVS008.mcilink.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Snyder, Guy" <guy.snyder@icsalabs.com>, Al Morton <acmorton@att.com>, bmwg@ietf.org
Subject: Re: [bmwg] IESG Interaction
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bmwg>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2010 13:54:10 -0000

Documents do not expire at 6 months after they are submitted to IESG
review (even if they are such marked in the tracker - this actually
seems a bug). 
 
Dan
 


________________________________

	From: bmwg-bounces@ietf.org [mailto:bmwg-bounces@ietf.org] On
Behalf Of Snyder, Guy
	Sent: Thursday, July 29, 2010 3:59 PM
	To: Al Morton; bmwg@ietf.org
	Subject: Re: [bmwg] IESG Interaction
	
	

	Forgive me (you and the authors) if this sounded like I was
saying the authors were not doing something. I was just using these two
documents as examples of the many that have expired. I just wanted to
understand the problem and the process that was trying to be solved. I
think you answered my questions. I totally understand your comment about
volunteer time.

	 

	-- Guy

	-- ICSA Labs

	
________________________________


	From: Al Morton [mailto:acmorton@att.com] 
	Sent: Thursday, July 29, 2010 8:48 AM
	To: Snyder, Guy; bmwg@ietf.org
	Subject: Re: [bmwg] IESG Interaction

	 

	At 06:27 AM 7/29/2010, Snyder, Guy wrote:
	
	

	Content-class: urn:content-classes:message
	Content-type: multipart/alternative;
	 boundary="----_=_NextPart_001_01CB2F08.987022E1"
	
	As part of the discussion for the re-charter, it was presented
that there was an issue getting drafts through the IESG.  Some examples
were the IPsec terminology and methodology. Al indicated that normally
this was because the IESG did not agree with our terminology. 

	
	Well, the audio record rules, but I didn't say much in my
	WG status presentation about these drafts, except that
	they had expired while we were waiting for the authors to
	resolve the IESG comments. (Later, I think Ron may have 
	mentioned the IPsec drafts in his motivation to revise
	the charter. He cited a general difficulty with the benchmarks
	themselves that has caused some problems.)
	
	To see what the IESG really said, which is what matters most,
	https://datatracker.ietf.org/doc/draft-ietf-bmwg-ipsec-term/
	https://datatracker.ietf.org/doc/draft-ietf-bmwg-ipsec-meth/
	
	
	
	

	 So my question is, did the documents stall because authors did
not work with the IESG? 

	
	Officially, we are still waiting to see revised drafts that
	address all the IESG comments.
	
	
	

	 Forgive me, but I don't understand totally how this process
works and how changes/fixes could have happened that would have
satisfied the IESG so the documents did not expire. 

	
	We simply needed the revisions to be made sooner, but we are a
	volunteer organization and the volunteers can only help us 
	when they have the time and energy...
	
	Al