[OPSAWG] FW: New Version Notification for draft-janapath-opsawg-flowoam-req-00.txt

Balaji Venkat Venkataswami <balajivenkat@force10networks.com> Tue, 08 May 2012 14:14 UTC

Return-Path: <balajivenkat@force10networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31D3221F85E3 for <opsawg@ietfa.amsl.com>; Tue, 8 May 2012 07:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AXdjoCCx3ZZG for <opsawg@ietfa.amsl.com>; Tue, 8 May 2012 07:14:14 -0700 (PDT)
Received: from mx.force10networks.com (maa.force10networks.com [59.163.202.254]) by ietfa.amsl.com (Postfix) with ESMTP id 40F1521F8653 for <opsawg@ietf.org>; Tue, 8 May 2012 07:14:14 -0700 (PDT)
Received: from EXCH-CLUSTER-11.force10networks.com ([10.16.127.21]) by exch7-maa-fe.force10networks.com ([10.16.126.10]) with mapi; Tue, 8 May 2012 19:44:09 +0530
From: Balaji Venkat Venkataswami <balajivenkat@force10networks.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Date: Tue, 08 May 2012 19:44:06 +0530
Thread-Topic: New Version Notification for draft-janapath-opsawg-flowoam-req-00.txt
Thread-Index: Ac0s+Ermvdd6tgQzSEGk0njzc6C2+AAK/bRg
Message-ID: <5EC91DDA759C324DB62C5A5F7B4922193CC8390459@EXCH-CLUSTER-11.force10networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "phoose@fb.com" <phoose@fb.com>
Subject: [OPSAWG] FW: New Version Notification for draft-janapath-opsawg-flowoam-req-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 14:14:15 -0000

Dear all,

Earlier in the month of February 2012 a group of authors from Microsoft, Facebook and DELL had published
a draft for a mechanism named Traceflow (which had seen an earlier incarnation in 2008). After subsequent
discussions with Ron Bonica and Melinda Shore and a presentation of Traceflow in IETF83 in Paris, it was
decided to publish a set of requirements rather than a tool specification itself. So we have split the
requirements separately and are publishing the following enclosed draft for your kind perusal and review.

Your collective feedback on the proposal is most welcome. This mail is to initiate that needed discussion
on the subject. 

thanks and regards,
Traceflow team

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Tuesday, May 08, 2012 2:25 PM
To: balaji_venkat_venkat@dell.com
Cc: pathangi_janardhanan@dell.com; phoose@fb.com; rgroves@microsoft.com
Subject: New Version Notification for draft-janapath-opsawg-flowoam-req-00.txt

A new version of I-D, draft-janapath-opsawg-flowoam-req-00.txt has been successfully submitted by Balaji Venkat Venkataswami and posted to the IETF repository.

Filename:	 draft-janapath-opsawg-flowoam-req
Revision:	 00
Title:		 Requirements for OAM tools that enable flow Analysis
Creation date:	 2012-05-08
WG ID:		 Individual Submission
Number of pages: 11

Abstract:
   This document specifies Operations and Management (OAM) requirements
   that improve on the traditional OAM tools like Ping and  Traceroute.
   These requirements have arisen from the fact that more details than
   given by Ping and Traceroute are required while troubleshooting or
   doing performance and network planning. These requirements have been
   gathered from network operators especially from data centers where
   the networks have slightly different characteristics compared to
   regular campus/carrier networks.

                                                                                  


The IETF Secretariat