IETF Logo Mail Archive

Re: [Idr] [spring] IDR WG 2 week WG LC on draft-ietf-idr-bgpls-segment-routing-epe - (2/15/2017 to 3/1/2017)

"Gaurav Dawra (gdawra)" <gdawra@cisco.com> Thu, 16 February 2017 15:39 UTC

Return-Path: <gdawra@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 875AC12009C; Thu, 16 Feb 2017 07:39:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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=-0.001, SPF_HELO_PASS=-0.001, 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 79pQnsDvew1S; Thu, 16 Feb 2017 07:39:41 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4620712965D; Thu, 16 Feb 2017 07:39:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10800; q=dns/txt; s=iport; t=1487259581; x=1488469181; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=5zxV0t5qktU89pl54tQOX4JMgtQgWxXQo3aG0oBg3fg=; b=gKw0Q+ypaShEyuUIL7mBPAS5rS2BKPjCWfgbDXtLvV1XUvMS+Mq8V3n2 Y12w26v5zCa6tKEBMeOsn/3atQc8Mll4z8b2F69CXvkBK/tCMWVZsfefo 5ghPLmvldE1RaGtz3Lrqn6LCXoEZX+YJvmeTJFCM8zg9oAmbe/BaBTCbv 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A2AQA1x6VY/4ENJK1eGQEBAQEBAQEBAQEBBwEBAQEBgm9iYYEJB41akhCQB4UsggwfAQyFLEoCggo/GAECAQEBAQEBAWIohHABAQEEAQFsCxACAQgRAwECJAQHJwsUCQgCBAENBYlsDrJoizsBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYZMhG+EdIVFBZVchiMBhm+LJ5EGkxcBHziBAFEVPYQNb4FIdYkqgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.35,169,1484006400"; d="scan'208,217";a="207545694"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 Feb 2017 15:39:40 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v1GFddLH010540 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 16 Feb 2017 15:39:40 GMT
Received: from xch-rtp-012.cisco.com (64.101.220.152) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 10:39:39 -0500
Received: from xch-rtp-012.cisco.com ([64.101.220.152]) by XCH-RTP-012.cisco.com ([64.101.220.152]) with mapi id 15.00.1210.000; Thu, 16 Feb 2017 10:39:39 -0500
From: "Gaurav Dawra (gdawra)" <gdawra@cisco.com>
To: Robert Raszuk <robert@raszuk.net>, Susan Hares <shares@ndzh.com>
Thread-Topic: [spring] IDR WG 2 week WG LC on draft-ietf-idr-bgpls-segment-routing-epe - (2/15/2017 to 3/1/2017)
Thread-Index: AQHSiGri+NyMNxA4e0i/ZPLgTjfcSg==
Date: Thu, 16 Feb 2017 15:39:39 +0000
Message-ID: <D4CB07AE.1D015D%gdawra@cisco.com>
References: <00f901d287e4$16ecb2f0$44c618d0$@ndzh.com> <CA+b+ERnPhRqrQds4Uu2sk4u-=nD7N81z6uA0oK=owOc59tvouQ@mail.gmail.com>
In-Reply-To: <CA+b+ERnPhRqrQds4Uu2sk4u-=nD7N81z6uA0oK=owOc59tvouQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.0.161029
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.58.145]
Content-Type: multipart/alternative; boundary="_000_D4CB07AE1D015Dgdawraciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/BGaM-w01DiYR8NCdnq8utv908Ww>
Cc: idr wg <idr@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Subject: Re: [Idr] [spring] IDR WG 2 week WG LC on draft-ietf-idr-bgpls-segment-routing-epe - (2/15/2017 to 3/1/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 15:39:43 -0000

Support.

Regards,

-Gaurav

From: spring <spring-bounces@ietf.org<mailto:spring-bounces@ietf.org>> on behalf of Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>>
Date: Thursday, February 16, 2017 at 4:39 AM
To: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Cc: idr wg <idr@ietf.org<mailto:idr@ietf.org>>, "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>, "Alvaro Retana (aretana)" <aretana@cisco.com<mailto:aretana@cisco.com>>
Subject: Re: [spring] IDR WG 2 week WG LC on draft-ietf-idr-bgpls-segment-routing-epe - (2/15/2017 to 3/1/2017)

Support.

Thx
R.

On Feb 15, 2017 6:39 PM, "Susan Hares" <shares@ndzh.com<mailto:shares@ndzh.com>> wrote:
This begins a 2 week IDR WG last call on draft-ietf-idr-bgpls-segment-routing-epe from (2/15 to 3/1/2017)    There are two implementations describe on the wiki at:
https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgpls-segment-routing-epe%20

The two implementation are from  Cisco IOS-XR release 6.0.2 and Cisco Nexus Switch N9000/N3000 platforms running NX-OS 7.0(3)I1(1) or greater.   The authors will indicate on the list and in the wiki the following information :


1)      Were these implementations separate implementations?

2)      What were the results of the interoperability tests?

This work is linked to the draft-ietf-spring-segment-routing-central-epe work in the SPRING WG. Based on the two drafts, the WG should might consider:

1)      Is there need for this work in deployments in networks/

2)      Is this technically ready for publication?

3)      Does it fit with the spring informational draft?

For the ease of reference the web references are below:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/
https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-central-epe/

Sue Hares

_______________________________________________
spring mailing list
spring@ietf.org<mailto:spring@ietf.org>
https://www.ietf.org/mailman/listinfo/spring

v2.23.0 | Report a Bug | By Email