[CCAMP] FW: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms) to Informational RFC

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 11 January 2013 21:10 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D61DB21F8ACE; Fri, 11 Jan 2013 13:10:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.554
X-Spam-Level:
X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hL-iEZ67fLul; Fri, 11 Jan 2013 13:10:53 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 5948A21F8AC8; Fri, 11 Jan 2013 13:10:50 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0BLAmOk032164; Fri, 11 Jan 2013 21:10:48 GMT
Received: from 950129200 (089144192150.atnat0001.highway.a1.net [89.144.192.150]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0BLAj8v032133 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 11 Jan 2013 21:10:47 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: routing-discussion@ietf.org, mpls@ietf.org, pwe3@ietf.org, ccamp@ietf.org, rtg-bfd@ietf.org
Date: Fri, 11 Jan 2013 21:10:47 -0000
Message-ID: <01cb01cdf040$2219c5e0$664d51a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3wPqAVHt9RLqNORBmXnogF2kx3kQ==
Content-Language: en-gb
Subject: [CCAMP] FW: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms) to Informational RFC
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 21:10:55 -0000

Heads up.
A lot of you will be interested in this.
Comments as usual for IETF last calls (see the instructions embedded). Do not
send your comments in reply to *this* message.

Thanks,
Adrian

> Sent: 11 January 2013 19:36
> To: IETF-Announce
> Cc: opsawg@ietf.org
> Subject: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An
> Overview of Operations, Administration, and Maintenance (OAM) Mechanisms)
> to Informational RFC
> 
> 
> The IESG has received a request from the Operations and Management Area
> Working Group WG (opsawg) to consider the following document:
> - 'An Overview of Operations, Administration, and Maintenance (OAM)
>    Mechanisms'
>   <draft-ietf-opsawg-oam-overview-08.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-01-25. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    Operations, Administration, and Maintenance (OAM) is a general term
>    that refers to a toolset that can be used for fault detection and
>    isolation, and for performance measurement. OAM mechanisms have been
>    defined for various layers in the protocol stack, and are used with a
>    variety of protocols.
> 
>    This document presents an overview of the OAM mechanisms that have
>    been defined and are currently being defined by the IETF.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg