Re: [bess] draft-ietf-bess-security-00.txt

"Susan Hares" <shares@ndzh.com> Mon, 05 November 2018 08:27 UTC

Return-Path: <shares@ndzh.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 89FA91274D0 for <bess@ietfa.amsl.com>; Mon, 5 Nov 2018 00:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no
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 VwDGQIHiEtmH for <bess@ietfa.amsl.com>; Mon, 5 Nov 2018 00:27:13 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD36812EB11 for <bess@ietf.org>; Mon, 5 Nov 2018 00:27:12 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=166.170.26.143;
From: Susan Hares <shares@ndzh.com>
To: "'Henderickx, Wim (Nokia - BE/Antwerp)'" <wim.henderickx@nokia.com>, bess@ietf.org
References: <010a01d474de$63837bb0$2a8a7310$@ndzh.com> <FC3F05E8-45F2-424A-A005-5BE336C2FB5B@nokia.com>
In-Reply-To: <FC3F05E8-45F2-424A-A005-5BE336C2FB5B@nokia.com>
Date: Mon, 05 Nov 2018 03:10:45 -0500
Message-ID: <012601d474df$0e22d5c0$2a688140$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0127_01D474B5.254D9110"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGUeW1iWaqbgtcQG0umhLekKnbLegJkVb60pa2odXA=
Content-Language: en-us
X-Antivirus: AVG (VPS 181105-2, 11/05/2018), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/9qXW7CvOWFticASekKspAp3f814>
Subject: Re: [bess] draft-ietf-bess-security-00.txt
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: Mon, 05 Nov 2018 08:27:15 -0000

+1 on this question.   I hope Ali will discuss. 

 

Sue 

 

From: Henderickx, Wim (Nokia - BE/Antwerp) [mailto:wim.henderickx@nokia.com] 
Sent: Monday, November 5, 2018 3:10 AM
To: Susan Hares; bess@ietf.org
Subject: Re: [bess] draft-ietf-bess-security-00.txt

 

Also how does the solution behave if the edge device is no longer connected to the RR and does not get keys in time to refresh. Common issue in SD-WAN context which is in scope from what I understood on the discussion with Linda.

 

From: BESS <bess-bounces@ietf.org> on behalf of Susan Hares <shares@ndzh.com>
Date: Monday, 5 November 2018 at 15:06
To: "bess@ietf.org" <bess@ietf.org>
Subject: [bess] draft-ietf-bess-security-00.txt

 

Ali:

 

It would be useful to indicate how you keep the IPSEC information from going outside the AS.   For reference, this is Keyur Patel’s question. 

 

Cheerily, Susan Hares