Re: [spring] I-D Action: draft-ietf-spring-segment-routing-central-epe-04.txt
"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Thu, 16 February 2017 22:35 UTC
Return-Path: <sprevidi@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0956B129706 for <spring@ietfa.amsl.com>; Thu, 16 Feb 2017 14:35:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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, 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 mbpAjgrYI1uf for <spring@ietfa.amsl.com>; Thu, 16 Feb 2017 14:35:15 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95902124281 for <spring@ietf.org>; Thu, 16 Feb 2017 14:35:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2719; q=dns/txt; s=iport; t=1487284515; x=1488494115; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=N8K0HktC6Y4VOLkts6gL86zgU74bn+3KhiI1dmp14hA=; b=KXtwvEk5MdZdV4kLLxBwL7a2vENCFk5HI79aN071FoP7LYSLsfV/B1dN 2PQLkbC5JWvH/UAE7Rpo65ga4y5H8o7CDw9R3B0EZ38Q3vOUX6xAO6fyy +V+ht6dLahShgz9rc2sSgEpY/mxvGmvXWlHxx7UvLTzpIKf8CpIisDMGx E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CJAQA1KKZY/4kNJK1eGQEBAQEBAQEBAQEBBwEBAQEBg1FhgQkHjVqRcB+VM4IMHw2FdgKCED8YAQIBAQEBAQEBYiiEcAEBAQMBAQE4NBALAgEIEgYeECcLFw4CBBMJEolJCA6ydYtVAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZMggUIgmKDF4E9MoMCgjEFm38Bhm+LJ4F7U4REiXSKWog9AR84PERRFRglEQGGMnUBiSmBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.35,169,1484006400"; d="scan'208";a="207394171"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 Feb 2017 22:35:14 +0000
Received: from XCH-RTP-010.cisco.com (xch-rtp-010.cisco.com [64.101.220.150]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v1GMZEcl015743 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <spring@ietf.org>; Thu, 16 Feb 2017 22:35:14 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-010.cisco.com (64.101.220.150) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 17:35:13 -0500
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Thu, 16 Feb 2017 17:35:13 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: SPRING WG <spring@ietf.org>
Thread-Topic: I-D Action: draft-ietf-spring-segment-routing-central-epe-04.txt
Thread-Index: AQHSiKTanc0vu5pFvUab7SRQCb9bPaFsjGiA
Date: Thu, 16 Feb 2017 22:35:13 +0000
Message-ID: <C48DDB55-32BD-4CCA-8219-441A8E4BADEF@cisco.com>
References: <148728445743.1027.18128759602323016329.idtracker@ietfa.amsl.com>
In-Reply-To: <148728445743.1027.18128759602323016329.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.209.26]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4535A74021C8FB4E8D25FE1D56A4BEAF@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/YY0gmsssFrJ-Xu3z4rXmO_SLJsc>
Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-central-epe-04.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 22:35:17 -0000
Hi, this version integrates comments received during shepherd review. Thanks. s. > On Feb 16, 2017, at 11:34 PM, internet-drafts@ietf.org wrote: > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Source Packet Routing in Networking of the IETF. > > Title : Segment Routing Centralized BGP Egress Peer Engineering > Authors : Clarence Filsfils > Stefano Previdi > Ebben Aries > Dmitry Afanasiev > Filename : draft-ietf-spring-segment-routing-central-epe-04.txt > Pages : 19 > Date : 2017-02-16 > > Abstract: > Segment Routing (SR) leverages source routing. A node steers a > packet through a controlled set of instructions, called segments, by > prepending the packet with an SR header. A segment can represent any > instruction topological or service-based. SR allows to enforce a > flow through any topological path and service chain while maintaining > per-flow state only at the ingress node of the SR domain. > > The Segment Routing architecture can be directly applied to the MPLS > dataplane with no change on the forwarding plane. It requires minor > extension to the existing link-state routing protocols. > > This document illustrates the application of Segment Routing to solve > the BGP Egress Peer Engineering (BGP-EPE) requirement. The SR-based > BGP-EPE solution allows a centralized (SDN) controller to program any > egress peer policy at ingress border routers or at hosts within the > domain. > > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-central-epe/ > > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-spring-segment-routing-central-epe-04 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-central-epe-04 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
- [spring] I-D Action: draft-ietf-spring-segment-ro… internet-drafts
- Re: [spring] I-D Action: draft-ietf-spring-segmen… Stefano Previdi (sprevidi)