Re: [spring] I-D Action: draft-ietf-spring-segment-routing-central-epe-05.txt
"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Fri, 10 March 2017 08:18 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 0F7B4129715 for <spring@ietfa.amsl.com>; Fri, 10 Mar 2017 00:18:38 -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 SsK0S73bWcOE for <spring@ietfa.amsl.com>; Fri, 10 Mar 2017 00:18:36 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00C0E1293D9 for <spring@ietf.org>; Fri, 10 Mar 2017 00:18:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2725; q=dns/txt; s=iport; t=1489133916; x=1490343516; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=pGo7IVcuIgy71Zq+D2VqqeX7ocrwF5z7muSZMZxdAAs=; b=KfWTy/b5shr0Jbm14R/HxKvw0aAGwAGeI9BVRZPVZV5kfFUpaONfvVHc 6fDsL4uaTgWCc7bGMzQCiAU+Rb0Ji5gkuij/C+NAgves5QGF2rZz9aurH cIkjbkTQy9WmseDeM6j37Z+1qyVf8rNR6cVZsEzSUMlAArJhba7cqkWYH 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AyAQAXYMJY/5RdJa1dGQEBAQEBAQEBAQEBBwEBAQEBg1FhgQoHjWaRMR+VOIIOHw2CQIM2AoI0PxgBAgEBAQEBAQFrKIUVAQEBAQIBAQE4NBALAgEIEgYeECcLFw4CBBMJEoldCA6zJYpqAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZOggUIgmKDF4E9MoMCgjEFnDkBhnWLQoF7U4RQigKKd4hHAR84gQNWFRgnEQGGQnUBiR2BDQEBAQ
X-IronPort-AV: E=Sophos;i="5.36,139,1486425600"; d="scan'208";a="393326935"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Mar 2017 08:18:16 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v2A8HvNe029882 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <spring@ietf.org>; Fri, 10 Mar 2017 08:17:57 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 10 Mar 2017 03:17:57 -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; Fri, 10 Mar 2017 03:17:57 -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-05.txt
Thread-Index: AQHSmXaGXJQgSiJiSEawHHvbrXUcaqGODo+A
Date: Fri, 10 Mar 2017 08:17:56 +0000
Message-ID: <CAACF78B-9987-44BB-953E-01DD470B80D2@cisco.com>
References: <148913372542.7410.16912254004883253396@ietfa.amsl.com>
In-Reply-To: <148913372542.7410.16912254004883253396@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.227.200]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AA7E5D9DC25092448F213CA58E95774A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/LIPaSRibMcd6zOAn-fFkqnQ2M1s>
Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-central-epe-05.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: Fri, 10 Mar 2017 08:18:38 -0000
this is the updated version after the various reviews. Thanks. s. > On Mar 10, 2017, at 9:15 AM, 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-05.txt > Pages : 19 > Date : 2017-03-10 > > 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 a > 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 (Software Defined Network, 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-05 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-central-epe-05 > > > 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)