FW: New Version Notification for draft-nitish-vrrp-bfd-00.txt

"Nitish Gupta (nitisgup)" <nitisgup@cisco.com> Mon, 15 June 2015 13:37 UTC

Return-Path: <nitisgup@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 116DC1B3644 for <rtgwg@ietfa.amsl.com>; Mon, 15 Jun 2015 06:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ue1igGEiFM8J for <rtgwg@ietfa.amsl.com>; Mon, 15 Jun 2015 06:37:07 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14B601B363A for <rtgwg@ietf.org>; Mon, 15 Jun 2015 06:37:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2148; q=dns/txt; s=iport; t=1434375427; x=1435585027; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+JurFuV2zogmvrm6Hm6dY+I6+ueHslYrMk2u/7+sNKI=; b=HbqkWw07yasY/gn8Egr1s+S1/xzhVPx9H6L6yf5jX5GSfo06F0HdwA3y gUYuN1Sl5az/PCBwoGxUhrZhw+IWOdXYFb47kyAw6q/ZnNXGA51osyTXS tPudm9ZkbS+x0ZHEH8zabQu2lYB808Rcp+rZgtDvQOQnYgbdRFKhSa1Ii o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BpBAAh1H5V/5JdJa1cgxBUXwa9XgmBYYV4AoEzOBQBAQEBAQEBgQqEIwEBBDozCgIQAgEINhAyGwEGAwIEDgWILw3KDwEBAQEBAQEBAQEBAQEBAQEBAQEBAReLRIUGB4QtBYt7h2ABhE+CVYQdgTNBg0OOfoNbJoN5bwGBRYEBAQEB
X-IronPort-AV: E=Sophos;i="5.13,618,1427760000"; d="scan'208";a="3630570"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-4.cisco.com with ESMTP; 15 Jun 2015 13:37:06 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t5FDb5Jx028723 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Jun 2015 13:37:05 GMT
Received: from xmb-rcd-x15.cisco.com ([169.254.5.62]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0195.001; Mon, 15 Jun 2015 08:37:05 -0500
From: "Nitish Gupta (nitisgup)" <nitisgup@cisco.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-nitish-vrrp-bfd-00.txt
Thread-Topic: New Version Notification for draft-nitish-vrrp-bfd-00.txt
Thread-Index: AQHQpRZUSk2E35hBAESbWfKVYNCATp2uRpSA
Date: Mon, 15 Jun 2015 13:37:04 +0000
Message-ID: <D1A4D1E2.50F6A%nitisgup@cisco.com>
References: <20150612134728.15333.53928.idtracker@ietfa.amsl.com>
In-Reply-To: <20150612134728.15333.53928.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [10.142.111.88]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A82E8C594062BF48BF7223E6C01CD895@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/2I3q6nonDD8E7W7XNDA7L2aT6bs>
X-Mailman-Approved-At: Mon, 15 Jun 2015 07:59:51 -0700
Cc: "colin@doch.org.uk" <colin@doch.org.uk>, "Aditya Dogra (addogra)" <addogra@cisco.com>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2015 13:37:09 -0000

Hi All,

We are proposing a peer learning mode in VRRP which will help in seamless
integration of VRRP with BFD.
We are looking forward to your comments on the draft.

Thanks,
Nitish

On 12/06/15 7:17 pm, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D, draft-nitish-vrrp-bfd-00.txt
>has been successfully submitted by Nitish Gupta and posted to the
>IETF repository.
>
>Name:		draft-nitish-vrrp-bfd
>Revision:	00
>Title:		Fast failure detection using peer learning in VRRP with BFD
>Document date:	2015-06-12
>Group:		Individual Submission
>Pages:		16
>URL:            
>https://www.ietf.org/internet-drafts/draft-nitish-vrrp-bfd-00.txt
>Status:         https://datatracker.ietf.org/doc/draft-nitish-vrrp-bfd/
>Htmlized:       https://tools.ietf.org/html/draft-nitish-vrrp-bfd-00
>
>
>Abstract:
>   This draft presents an enhanced failure detection mechanism to detect
>   the failure of VRRP Master router on the LAN using a peer learning
>   mode.  Typically the VRRP protocol is able to perform the transparent
>   fail-over detection within a time period of 3 seconds with default
>   fail-over timers.  Real-time protocols (voice/video/real-time
>   transactional) require a maximum network disruption in the order of
>   150ms for traffic on the network.  A failure detection and fail-over
>   time of 150ms on conventionally configured VRRP protocol is extremely
>   aggressive and may impact the reliability and performance of the
>   network.
>
>   A more efficient mechanism for real-time failure detection can be
>   enabled in VRRP protocol by building a peer table, using a new VRRP
>   Advert packet type.  This will help in forming a mesh of BFD
>   sessions.  Once the BFD sessions are created, VRRP can receive faster
>   notification of failures, without the overhead of increased VRRP
>   protocol Advert messages.
>
>                  
>        
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>