[OPS-AREA] FW: Call for Comments: "Uncoordinated Protocol Development Considered Harmful"
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 11 June 2009 10:22 UTC
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0613928C184; Thu, 11 Jun 2009 03:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.433
X-Spam-Level:
X-Spam-Status: No, score=-2.433 tagged_above=-999 required=5 tests=[AWL=0.166, BAYES_00=-2.599]
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 h3EfZBElNysp; Thu, 11 Jun 2009 03:22:44 -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 64FA528C16D; Thu, 11 Jun 2009 03:22:43 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,202,1243828800"; d="scan'208";a="148273382"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 11 Jun 2009 06:22:49 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 11 Jun 2009 06:22:48 -0400
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: Thu, 11 Jun 2009 12:22:14 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040179050A@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Call for Comments: "Uncoordinated Protocol Development Considered Harmful"
Thread-Index: AcnqfIs4nq4lpPvXQL6uVgdEOnxDgwAAaYrw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: ops-dir@ietf.org
Cc: ops-area@ietf.org
Subject: [OPS-AREA] FW: Call for Comments: "Uncoordinated Protocol Development Considered Harmful"
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jun 2009 10:22:45 -0000
This is an IAB document, so it goes through a different type of review cycle. I think the issues raised by this document have operational implications. I would suggest that OPS-DIR assigns a reviewer for this and also invite comments from the OPSAREA community. Thanks and Regards, Dan -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of IAB Chair Sent: Thursday, June 11, 2009 1:08 PM To: IETF Announcement list Cc: mmorrow@cisco.com; iab@iab.org; stbryant@cisco.com Subject: Call for Comments: "Uncoordinated Protocol Development Considered Harmful" The IAB intends to publish the following document and invites any comments you might have: "Uncoordinated Protocol Development Considered Harmful" http://tools.ietf.org/html/draft-iab-mpls-tp-uncoord-harmful-00 Abstract This document identifies various types of damage that may occur without formal coordination and joint development on protocols of mutual interest between standards development organizations. The IAB has selected T-MPLS as recent case study to describe hazard to both the MPLS and Internet architecture as a result of uncoordinated adaptation of a protocol. This experience has resulted in a considerable improvement in the relationship between the two organisations. In particular, this was achieved via the establishment of the "Joint working team on MPLS-TP" which was the first ever joint ITU/IETF group. In addition, the leadership of the two organisations have agreed to improve inter- organizational working practices so as to avoid conflict in future between ITU-T Recommendations and IETF RFCs. Please provide your feedback before June 28, 2009. For the IAB, --Olaf Kolkman IAB Chair _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
- [OPS-AREA] FW: Call for Comments: "Uncoordinated … Romascanu, Dan (Dan)