[VRRP] Publication of RFC 6527 on VRRPv3 MIB

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 09 March 2012 13:06 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B97F621F862F for <vrrp@ietfa.amsl.com>; Fri, 9 Mar 2012 05:06:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[AWL=-0.103, BAYES_00=-2.599, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 5-RYfkdTsnq7 for <vrrp@ietfa.amsl.com>; Fri, 9 Mar 2012 05:06:36 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com []) by ietfa.amsl.com (Postfix) with ESMTP id B681A21F864F for <vrrp@ietf.org>; Fri, 9 Mar 2012 05:06:29 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain []) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q29D6SVb003600 for <vrrp@ietf.org>; Fri, 9 Mar 2012 13:06:28 GMT
Received: from 950129200 ([]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q29D6IoW003566 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <vrrp@ietf.org>; Fri, 9 Mar 2012 13:06:25 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: vrrp@ietf.org
Date: Fri, 09 Mar 2012 13:06:17 -0000
Message-ID: <0c8d01ccfdf5$71115d40$533417c0$@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: Acz99J/itYf13069QnCHwBhQJhP7GQ==
Content-Language: en-gb
Subject: [VRRP] Publication of RFC 6527 on VRRPv3 MIB
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Virtual Router Redundancy Protocol <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 13:06:36 -0000

Thanks to Kalyan for all the effort to reach completion on this document.

It is the last in the series of working group documents and we are now truly

This email list remains open for discussion of VRRP issues. Anyone with new
proposals or modifications for VRRP should bring them forward in individual I-Ds
for AD sponsorship, but this list remains a good place for discussion.


> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of rfc-editor@rfc-editor.org
> Sent: 08 March 2012 01:43
> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> Cc: rfc-editor@rfc-editor.org
> Subject: RFC 6527 on Definitions of Managed Objects for Virtual Router
> Redundancy Protocol Version 3 (VRRPv3)
> A new Request for Comments is now available in online RFC libraries.
>         RFC 6527
>         Title:      Definitions of Managed Objects for
>                     Virtual Router Redundancy Protocol Version 3
>                     (VRRPv3)
>         Author:     K. Tata
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       March 2012
>         Mailbox:    tata_kalyan@yahoo.com
>         Pages:      31
>         Characters: 62639
>         Obsoletes:  RFC2787
>         I-D Tag:    draft-ietf-vrrp-unified-mib-10.txt
>         URL:        http://www.rfc-editor.org/rfc/rfc6527.txt
> This specification defines a portion of the Management Information
> Base (MIB) for use with network management based on the Simple Network
> Management Protocol (SNMP).  In particular, it defines objects for
> configuring, monitoring, and controlling routers that employ the Virtual
> Router Redundancy Protocol Version 3 (VRRPv3) for both IPv4 and IPv6 as
> defined in RFC 5798.  This memo obsoletes RFC 2787.  [STANDARDS-TRACK]
> This is now a Proposed Standard Protocol.
> STANDARDS TRACK: This document specifies an Internet standards track
> protocol for the Internet community,and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the Internet
> Official Protocol Standards (STD 1) for the standardization state and
> status of this protocol.  Distribution of this memo is unlimited.
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   http://www.ietf.org/mailman/listinfo/ietf-announce
>   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> The RFC Editor Team
> Association Management Solutions, LLC
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce