IETF Logo Mail Archive

RE: LC reviews: draft-brenner-dime-peem

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 07 January 2008 06:08 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JBl9p-0004cH-IF; Mon, 07 Jan 2008 01:08:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JBl9l-0004bl-Dl; Mon, 07 Jan 2008 01:08:17 -0500
Received: from de307622-de-outbound.net.avaya.com ([198.152.71.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JBl9k-0007Sh-Uf; Mon, 07 Jan 2008 01:08:17 -0500
X-IronPort-AV: E=Sophos;i="4.24,251,1196658000"; d="scan'208";a="84489367"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 07 Jan 2008 01:08:13 -0500
X-IronPort-AV: E=Sophos;i="4.24,251,1196658000"; d="scan'208";a="139901934"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 07 Jan 2008 01:07:32 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 07 Jan 2008 07:07:33 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0478A6F2@307622ANEX5.global.avaya.com>
In-Reply-To: <478148F3.5060109@joelhalpern.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: LC reviews: draft-brenner-dime-peem
Thread-Index: AchQq68QTZCRfmVRQoWUBb3FlV4MDgAR4MOg
References: <F66D7286825402429571678A16C2F5EE0135EACE@zrc2hxm1.corp.nortel.com> <478148F3.5060109@joelhalpern.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, gen-art@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: mrbrenner@alcatel-lucent.com, Mary Barnes <mary.barnes@nortel.com>, ietf@ietf.org
Subject: RE: LC reviews: draft-brenner-dime-peem
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org


 
 

> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com] 

> 	The first of the two comments below is probably 
> primarily the IESG's concern, although it affects the IETF last call.
> 	The second comment is a more general issue.
> 
> Comments:
> 	This document requests assignment of a Diameter Command Code.
> 	As this requires "IETF Consensus" additional care may 
> be needed to ensure that the Last Call produces clarity on 
> the required consensus. 
> It would seem appropriate for the last call announcement to 
> have indicated this requirement.  It is difficult to claim 
> "IETF Consensus" 
> from the typical non-response to IETF last call for 
> informational documents.
> 

Hi Joel,

Thank you for catching this. I have required the Secretariat to re-issue
the Last Call with the clarification of the issue you are pointing to. 

Dan

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email