[bess] Kathleen Moriarty's Discuss on draft-ietf-bess-mvpn-extranet-04: (with DISCUSS)

"Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com> Fri, 18 December 2015 01:47 UTC

Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
X-Original-To: bess@ietf.org
Delivered-To: bess@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B461B31ED; Thu, 17 Dec 2015 17:47:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151218014710.16763.71345.idtracker@ietfa.amsl.com>
Date: Thu, 17 Dec 2015 17:47:10 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/bess/DBdwMh2Z3WE80NJxhA5qDsmlQwI>
Cc: aretana@cisco.com, bess-chairs@ietf.org, draft-ietf-bess-mvpn-extranet@ietf.org, martin.vigoureux@alcatel-lucent.com, bess@ietf.org
Subject: [bess] Kathleen Moriarty's Discuss on draft-ietf-bess-mvpn-extranet-04: (with DISCUSS)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 18 Dec 2015 01:47:10 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-bess-mvpn-extranet-04: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-extranet/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I just have one question/request to improve the security consideration
section.  The only security mentioned in this draft is what's called a
"security violation", where traffic may go to the incorrect "VPN"
endpoint.  If you are worried about traffic winding up in the wrong
place, why is there no consideration for observing this traffic on the
wire?  Since there is no encryption, wouldn't this also be a security
consideration to call out specifically? 

Mention of the possibility of active attacks that could alter or tamper
with the traffic or passive attacks that could observe the traffic as a
risk due to lack of encryption (confidentiality protection) would help or
a reason why this doesn't matter.

Thanks!