Re: [bess] Kathleen Moriarty's No Objection on draft-ietf-bess-evpn-etree-13: (with COMMENT)

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Fri, 27 October 2017 18:21 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 0E25513F42F; Fri, 27 Oct 2017 11:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 YiAEGGcGKaVh; Fri, 27 Oct 2017 11:21:29 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 567B413F3AC; Fri, 27 Oct 2017 11:21:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1415; q=dns/txt; s=iport; t=1509128489; x=1510338089; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=2pSDn6OJetnHDMhymAhgHue48JEhFJwRwgN6ItDfXAc=; b=Yue1ZChw8cVHvsDtZsgUpjNNdlQoB+yEMQqdYK2iNuCQ1unmz+cISuaI XE9rDwLuBTdMWpDPXylHCsDF5cAJpAAGeZ8olKjy6KzJwISZ0dhcy759x EgBmWqz86UV4ikpBOTKiGUlcuW9R5NmkaLN8k5ATxrWl8bmmmqeAJpmeI g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CiAABvePNZ/5JdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg19kbicHjhKPFIpJjXMQggEKI4UYAoRLPxgBAgEBAQEBAQFrKIU?= =?us-ascii?q?eBjo/EAIBCDYQIRElAgQBDQWKCwMVEKs0hzoNgyMBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEYBYMuggeDOYMqgl6BawkBEgFRBoU+BYollyI8AodkiB2EeYIVhgCLGIx?= =?us-ascii?q?fOYhLAhEZAYE4AR84gQNMGXoVgy2DEYFOdwGJL4EkgREBAQE?=
X-IronPort-AV: E=Sophos;i="5.44,304,1505779200"; d="scan'208";a="22577042"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Oct 2017 18:21:28 +0000
Received: from XCH-RTP-004.cisco.com (xch-rtp-004.cisco.com [64.101.220.144]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v9RILSO0020403 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 27 Oct 2017 18:21:28 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-004.cisco.com (64.101.220.144) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 27 Oct 2017 14:21:27 -0400
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.1320.000; Fri, 27 Oct 2017 14:21:27 -0400
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-bess-evpn-etree@ietf.org" <draft-ietf-bess-evpn-etree@ietf.org>, Thomas Morin <thomas.morin@orange.com>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>, "bess@ietf.org" <bess@ietf.org>, Alvaro Retana <aretana.ietf@gmail.com>
Thread-Topic: Kathleen Moriarty's No Objection on draft-ietf-bess-evpn-etree-13: (with COMMENT)
Thread-Index: AQHTLQEYbD0ZY767gkyCBOG3WriclKL4FHqA
Date: Fri, 27 Oct 2017 18:21:27 +0000
Message-ID: <D618C58D.2270A9%sajassi@cisco.com>
References: <150535608269.12663.6685913567714963265.idtracker@ietfa.amsl.com>
In-Reply-To: <150535608269.12663.6685913567714963265.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.7.7.170905
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.76.53]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25AE8E2F9F61894AA2827CDBC190C7A3@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/aExVR2TUgXMDeHg_od4NdaKxBBg>
Subject: Re: [bess] Kathleen Moriarty's No Objection on draft-ietf-bess-evpn-etree-13: (with COMMENT)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 27 Oct 2017 18:21:31 -0000

Hi Kathleen,

Leaf to leaf communication prohibition is one of the main function of
E-TREE service per MEF definition and RFC 7387. The document describes how
to implement this E-TREE service for EVPN and how it can be done more
efficiently. 

Regards,
Ali


On 9/13/17, 7:28 PM, "Kathleen Moriarty"
<Kathleen.Moriarty.ietf@gmail.com> wrote:

>Kathleen Moriarty has entered the following ballot position for
>draft-ietf-bess-evpn-etree-13: No Objection
>
>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-evpn-etree/
>
>
>
>----------------------------------------------------------------------
>COMMENT:
>----------------------------------------------------------------------
>
>I'm reading the leaf to leaf prohibition as a routing optimization that
>isn't
>intended for security purposes, but could help prevent routing loops and
>leakage.  There is a little text early on in the document to describe the
>purpose, but I agree the text should be made a bit more clear.
>
>