Re: [bess] Proposed updates to address comments to draft-ietf-bess-mvpn-fast-failover

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Wed, 07 November 2018 04:43 UTC

Return-Path: <sajassi@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8A12130F20; Tue, 6 Nov 2018 20:43:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.97
X-Spam-Level:
X-Spam-Status: No, score=-14.97 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 iKsxx6eCPhy4; Tue, 6 Nov 2018 20:43:45 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF04130EE5; Tue, 6 Nov 2018 20:43:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10380; q=dns/txt; s=iport; t=1541565825; x=1542775425; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=DE79dwfurXcAAiKbdh7qPJ51ueKruUYQtN6u1am0J2U=; b=TxnG9kb+7GO53XKUSzNwb/cnjYIjPSa+jkn9J9ccNH5OOlhujcq8pFNO 1e0BN6qfs3P0X0LhB+wAtzcMrqTYtqH1ubyxrwlB9g1u3yzx3F+OeJ4Oa Uu0lDkgmOpGvoCaeDRXdjbG97B2tYnoGRTjtw+OBu+9BWQjd6a7PYCgtg o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AEAADxbOJb/5JdJa1kGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUQUBAQEBCwGBDXZmgQInCoNsiBiMF4INiQOIWYVUFIFmCwE?= =?us-ascii?q?BhGwCF4NBIjQNDQEDAQECAQECbSiFOgEBAQEDI1AWAgEIEQMBAisCAgIfER0?= =?us-ascii?q?IAgQBEoMhAYEdTAMVqSaBLogGDYIZi3gXggCBEScfgh4uglaBZAxYgmQxgiY?= =?us-ascii?q?CjmKGLIl9LgkCjWaDKhiBVoUAig6JRoRLiRUCERSBJh04gVVwFWUBgkGQWkE?= =?us-ascii?q?xjDaBHwEB?=
X-IronPort-AV: E=Sophos;i="5.54,474,1534809600"; d="scan'208,217";a="196798872"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Nov 2018 04:43:44 +0000
Received: from XCH-RTP-001.cisco.com (xch-rtp-001.cisco.com [64.101.220.141]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id wA74hh7f016735 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 7 Nov 2018 04:43:44 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-001.cisco.com (64.101.220.141) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 6 Nov 2018 23:43:43 -0500
Received: from xch-rtp-005.cisco.com ([64.101.220.145]) by XCH-RTP-005.cisco.com ([64.101.220.145]) with mapi id 15.00.1395.000; Tue, 6 Nov 2018 23:43:43 -0500
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Greg Mirsky <gregimirsky@gmail.com>, BESS <bess@ietf.org>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>
Thread-Topic: Proposed updates to address comments to draft-ietf-bess-mvpn-fast-failover
Thread-Index: AQHUcF/xCyeg/Qs6RE2iCtinHHm5GKVDld0A
Date: Wed, 7 Nov 2018 04:43:43 +0000
Message-ID: <57F3B998-46CD-4E95-BCC5-0AA741B1C68E@cisco.com>
References: <CA+RyBmW2qK3qVEGEL6fbjPUrEggGbrMbk3A=u4f3jbvB_XAuPQ@mail.gmail.com>
In-Reply-To: <CA+RyBmW2qK3qVEGEL6fbjPUrEggGbrMbk3A=u4f3jbvB_XAuPQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.3.181015
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.125.127]
Content-Type: multipart/alternative; boundary="_000_57F3B99846CD4E95BCC50AA741B1C68Eciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.141, xch-rtp-001.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/A7hhuMLzOU0X4dyyNqC7Wq7bl5o>
Subject: Re: [bess] Proposed updates to address comments to draft-ietf-bess-mvpn-fast-failover
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2018 04:43:52 -0000

Hi Greg,

The changes look good. Thanks for taking care of my comments.

Cheers,
Ali

From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tuesday, October 30, 2018 at 7:50 AM
To: Cisco Employee <sajassi@cisco.com>om>, BESS <bess@ietf.org>rg>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>
Subject: Proposed updates to address comments to draft-ietf-bess-mvpn-fast-failover

Dear Ali,
my sincere apologies for being so terribly late to address your comments at the BESS WG meeting in Montreal. Below are the updates I propose:
OLD TEXT:
  Then The Downstream PE MAY
   initiate a switchover of the traffic from the Primary Upstream PE to
   the Standby Upstream PE.
NEW TEXT:
  Then The Downstream PE MAY
   initiate a switchover of the traffic from the Primary Upstream PE to
   the Standby Upstream PE only if the Standby Upstream PE deemed
   available.  The dedicated p2mp BFD session MAY monitor the state of
   the Standby Upstream PE.

OLD TEXT:
   Whenever the state of the BFD session changes to Down the Provider
   Tunnel will be considered down, and the downstream PE will switch to
   the backup Provider Tunnel.
NEW TEXT:
   Whenever the state of the BFD session changes to Down the Provider
   Tunnel will be considered down, and the downstream PE MAY switch to
   the backup Provider Tunnel only if the backup Provider Tunnel deemed
   available.  The dedicated p2mp BFD session MAY monitor the state of
   the backup Provider Tunnel.

Attached please find diff to highlight the update and the new version of the draft.

Kind regards,
Greg