FW: New Version Notification for draft-psarkar-rtgwg-rlfa-node-protection-05.txt

Pushpasis Sarkar <psarkar@juniper.net> Tue, 24 June 2014 08:37 UTC

Return-Path: <psarkar@juniper.net>
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 1F9311A01B8 for <rtgwg@ietfa.amsl.com>; Tue, 24 Jun 2014 01:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 mcInVzhC9XAy for <rtgwg@ietfa.amsl.com>; Tue, 24 Jun 2014 01:37:07 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0188.outbound.protection.outlook.com [207.46.163.188]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDFC61A0165 for <rtgwg@ietf.org>; Tue, 24 Jun 2014 01:37:06 -0700 (PDT)
Received: from BN1PR05MB520.namprd05.prod.outlook.com (10.141.65.151) by BN1PR05MB517.namprd05.prod.outlook.com (10.141.65.142) with Microsoft SMTP Server (TLS) id 15.0.954.9; Tue, 24 Jun 2014 08:37:04 +0000
Received: from BN1PR05MB520.namprd05.prod.outlook.com ([169.254.14.130]) by BN1PR05MB520.namprd05.prod.outlook.com ([169.254.14.130]) with mapi id 15.00.0954.000; Tue, 24 Jun 2014 08:37:04 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-psarkar-rtgwg-rlfa-node-protection-05.txt
Thread-Topic: New Version Notification for draft-psarkar-rtgwg-rlfa-node-protection-05.txt
Thread-Index: AQHPj4ZRGrvLb3srckattm85Q624TJt/7rWQ
Date: Tue, 24 Jun 2014 08:37:03 +0000
Message-ID: <8c744efff6c148149db4cd76dcfe115b@BN1PR05MB520.namprd05.prod.outlook.com>
References: <20140624082840.3753.40879.idtracker@ietfa.amsl.com>
In-Reply-To: <20140624082840.3753.40879.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [116.197.184.16]
x-microsoft-antispam: BL:0; ACTION:Default; RISK:Low; SCL:0; SPMLVL:NotSpam; PCL:0; RULEID:
x-forefront-prvs: 02524402D6
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(377454003)(53754006)(377424004)(13464003)(199002)(189002)(79102001)(15975445006)(81542001)(76576001)(2656002)(85306003)(105586002)(80022001)(106116001)(87936001)(50986999)(64706001)(20776003)(54356999)(21056001)(86362001)(74502001)(31966008)(76482001)(77982001)(85852003)(74316001)(81342001)(106356001)(15202345003)(101416001)(76176999)(19580395003)(19580405001)(33646001)(99286002)(99396002)(83322001)(74662001)(77096002)(95666004)(66066001)(46102001)(83072002)(92566001)(24736002)(106276001); DIR:OUT; SFP:; SCL:1; SRVR:BN1PR05MB517; H:BN1PR05MB520.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/U4XtmDB4PaPwK2iYm83_Zaoq1Xc
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: Tue, 24 Jun 2014 08:37:09 -0000

Hi All,

We have addressed all of the pending comments in the latest version of this draft. Request you all to review and provide feedback. 

Also we would like to re-call for WG adoption for this draft and take it forward as a WG document (as was decided in last IETF meeting).

Thanks and Regards,
-Pushpasis

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Tuesday, June 24, 2014 1:59 PM
To: Shraddha Hegde; Harish Raghuveer; Shraddha Hegde; Hannes Gredler; Harish Raghuveer; Stephane Litkowski; Chris Bowers; Pushpasis Sarkar; Chris Bowers; Pushpasis Sarkar; Hannes Gredler; Stephane Litkowski
Subject: New Version Notification for draft-psarkar-rtgwg-rlfa-node-protection-05.txt


A new version of I-D, draft-psarkar-rtgwg-rlfa-node-protection-05.txt
has been successfully submitted by Pushpasis Sarkar and posted to the IETF repository.

Name:		draft-psarkar-rtgwg-rlfa-node-protection
Revision:	05
Title:		Remote-LFA Node Protection and Manageability
Document date:	2014-06-24
Group:		rtgwg
Pages:		16
URL:            http://www.ietf.org/internet-drafts/draft-psarkar-rtgwg-rlfa-node-protection-05.txt
Status:         https://datatracker.ietf.org/doc/draft-psarkar-rtgwg-rlfa-node-protection/
Htmlized:       http://tools.ietf.org/html/draft-psarkar-rtgwg-rlfa-node-protection-05
Diff:           http://www.ietf.org/rfcdiff?url2=draft-psarkar-rtgwg-rlfa-node-protection-05

Abstract:
   The loop-free alternates computed following the current Remote-LFA
   [I-D.ietf-rtgwg-remote-lfa] specification gaurantees only link-
   protection.  The resulting Remote-LFA nexthops (also called PQ-
   nodes), may not gaurantee node-protection for all destinations being
   protected by it.

   This document describes procedures for determining if a given PQ-node
   provides node-protection for a specific destination or not.  The
   document also shows how the same procedure can be utilised for
   collection of complete characteristics for alternate paths.
   Knowledge about the characteristics of all alternate path is
   precursory to apply operator defined policy for eliminating paths not
   fitting constraints.


                                                                                  


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