IETF Logo Mail Archive

Re: [bess] [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Mon, 06 June 2016 17:12 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 E849412D0C8; Mon, 6 Jun 2016 10:12:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.946
X-Spam-Level:
X-Spam-Status: No, score=-15.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, 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 RSH3fLy0vvue; Mon, 6 Jun 2016 10:11:59 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A73412D135; Mon, 6 Jun 2016 10:11:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9447; q=dns/txt; s=iport; t=1465233119; x=1466442719; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=zxfYYzn/WD/b2qcUFgRbecwR7991SXfCQS/B29BRZLE=; b=KAET/bROzBPOZavsyjpAuwMtDii8+O4tpfsJIP3IcBIg5jDKh96G3Upw 9dt+gVXelClh+1P8aET6uCzbXqqG76919QqEZjBv7TFGbbGbAASmIhG6c WSi8k6HmN7q2aU6c3KCckAZTuiIj1P0iakMYuin72onjMLkP0WAEaM9Ty 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AqAgAqrlVX/4MNJK1bgm5NVm8OBrVXhH2BeiKFcAKBMzgUAQEBAQEBAWUnhEUBAQEEgQkCAQgRAwECKAcyFAkIAgQBEogVAxcOuw4BAQEBAQEBAQEBAQEBAQEBAQEaBYp0gkOBTxEBPIU6BY4eiioBhgKII4FphFCIZY9ZAR42g25uAYhjNn8BAQE
X-IronPort-AV: E=Sophos;i="5.26,428,1459814400"; d="scan'208,217";a="281660352"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Jun 2016 17:11:58 +0000
Received: from XCH-RTP-002.cisco.com (xch-rtp-002.cisco.com [64.101.220.142]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u56HBw0w003955 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 6 Jun 2016 17:11:58 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-002.cisco.com (64.101.220.142) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 6 Jun 2016 13:11:57 -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.1104.009; Mon, 6 Jun 2016 13:11:57 -0400
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>, John E Drake <jdrake@juniper.net>, Thomas Morin <thomas.morin@orange.com>, IDR <idr@ietf.org>, BESS <bess@ietf.org>, "draft-ietf-bess-evpn-overlay@tools.ietf.org" <draft-ietf-bess-evpn-overlay@tools.ietf.org>, "Rabadan, Jorge (Nokia - US)" <jorge.rabadan@nokia.com>, "draft-ietf-idr-tunnel-encap@tools.ietf.org" <draft-ietf-idr-tunnel-encap@tools.ietf.org>
Thread-Topic: [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps
Thread-Index: AQHRpi++kmVRnOfCCEaLlUJwLCbjV5+pXciAgAAV74CAABx8AIAAAd6AgAD40oCAAAcLgIAAlB8AgAAObQCAE5+SgIAAQjEAgAiAQYCAFRg5AA==
Date: Mon, 06 Jun 2016 17:11:57 +0000
Message-ID: <D37AFB0E.1A944C%sajassi@cisco.com>
References: <5729F1C3.1030605@orange.com> <5729F7C5.6040604@orange.com> <52D35106-ED5E-4C95-9131-6EA4527370D5@alcatel-lucent.com> <BY2PR0501MB1702CD2423A817F3725CB5DFC77B0@BY2PR0501MB1702.namprd05.prod.outlook.com> <012C176C-A8D6-45AA-BA69-616C0ED7E41E@alcatel-lucent.com> <SN1PR0501MB1709E1AF8C398791421E2123C77B0@SN1PR0501MB1709.namprd05.prod.outlook.com> <420BA2D8D80A6727.2B2C290F-2299-40BB-B53B-CC36D2B5D826@mail.outlook.com> <1881_1462451514_572B3D3A_1881_7198_1_0vn90oitr7e881gh2sn8qm5f.1462451509961@email.android.com> <SN1PR0501MB17099CA0122BA8B4C3F99E7EC77C0@SN1PR0501MB1709.namprd05.prod.outlook.com> <17029_1462484835_572BBF63_17029_2323_1_opi9hqsl9b9tani0t0skkcuq.1462484831251@email.android.com> <SN1PR0501MB170976E947BEABC8FD591ED8C77C0@SN1PR0501MB1709.namprd05.prod.outlook.com> <28175_1463566739_573C4192_28175_2444_1_613f729b-d12e-5c48-29a1-ff000c1184a1@orange.com> <SN1PR0501MB17090A6F0AC5D3D447E21C28C7490@SN1PR0501MB1709.namprd05.prod.outlook.com> <D369475E.1A2CD7%sajassi@cisco.com>
In-Reply-To: <D369475E.1A2CD7%sajassi@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.76.53]
Content-Type: multipart/alternative; boundary="_000_D37AFB0E1A944Csajassiciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/IzlIbsGNPdiWrYaHwSps9b6gREg>
Subject: Re: [bess] [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.17
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, 06 Jun 2016 17:12:02 -0000

Hi Thomas,

I updated and checked-in a new rev of this draft couple of weeks ago to address the comments that came up on this email thread - the main changes were outlined in my previous email. Can you please progress this draft for its LC. If there is any issue preventing the progress of this draft, would you let us know.

Regards,
Ali

From: Cisco Employee <sajassi@cisco.com<mailto:sajassi@cisco.com>>
Date: Tuesday, May 24, 2016 at 12:04 AM
To: John E Drake <jdrake@juniper.net<mailto:jdrake@juniper.net>>, Thomas Morin <thomas.morin@orange.com<mailto:thomas.morin@orange.com>>, IDR <idr@ietf.org<mailto:idr@ietf.org>>, BESS <bess@ietf.org<mailto:bess@ietf.org>>, "draft-ietf-bess-evpn-overlay@tools.ietf.org<mailto:draft-ietf-bess-evpn-overlay@tools.ietf.org>" <draft-ietf-bess-evpn-overlay@tools.ietf.org<mailto:draft-ietf-bess-evpn-overlay@tools.ietf.org>>, "Rabadan, Jorge (Nokia - US)" <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>, "draft-ietf-idr-tunnel-encap@tools.ietf.org<mailto:draft-ietf-idr-tunnel-encap@tools.ietf.org>" <draft-ietf-idr-tunnel-encap@tools.ietf.org<mailto:draft-ietf-idr-tunnel-encap@tools.ietf.org>>
Subject: Re: [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps
Resent-From: <alias-bounces@ietf.org<mailto:alias-bounces@ietf.org>>, Cisco Employee <sajassi@cisco.com<mailto:sajassi@cisco.com>>
Resent-To: Cisco Employee <sajassi@cisco.com<mailto:sajassi@cisco.com>>, <jdrake@juniper.net<mailto:jdrake@juniper.net>>, <nabil.n.bitar@verizon.com<mailto:nabil.n.bitar@verizon.com>>, <uttaro@att.com<mailto:uttaro@att.com>>, <wim.henderickx@alcatel-lucent.com<mailto:wim.henderickx@alcatel-lucent.com>>, <aisaac@juniper.net<mailto:aisaac@juniper.net>>, <draft-ietf-bess-evpn-overlay@ietf.org<mailto:draft-ietf-bess-evpn-overlay@ietf.org>>
Resent-Date: Tuesday, May 24, 2016 at 12:05 AM


Folks,

I have updated and published rev03 of even-overlay draft.
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay/

The main changes are:

  1.  section 10.2 - DCI using ASBR
  2.  The setting of Ethernet tag and VNI fields - there were some inconsistencies in different sections. Section 5.1.3 captures the setting of these fields for different type of services in pretty good details. All other sections were cleaned up and now refer to section 5.1.3.

Thomas,
The draft is ready for its long-overdue WG LC considering how long its has been around and its multi-vendor implementation status.

Regards,
Ali

v2.23.0 | Report a Bug | By Email