Re: [spring] I-D Action: draft-ietf-spring-segment-routing-central-epe-02.txt
"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Tue, 13 September 2016 08:33 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 CFA9012B11B for <spring@ietfa.amsl.com>; Tue, 13 Sep 2016 01:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.029
X-Spam-Level:
X-Spam-Status: No, score=-16.029 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=-1.508, 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 C0LuwHmaasyg for <spring@ietfa.amsl.com>; Tue, 13 Sep 2016 01:33:39 -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 0A01F12B059 for <spring@ietf.org>; Tue, 13 Sep 2016 01:33:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2599; q=dns/txt; s=iport; t=1473755618; x=1474965218; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=+9dnzNo3FHtadnHV7ctOgGtZUly89CGd7SbOO/6hc78=; b=lxE5Gj7bN6gTVeQmb5e9m4SXmdHWqQKRRFMbiD7AYTztxRMIP+THj1jl BaWxhdKU7ucPxIqJZHMvRHk1CZfj7oqK+tz2lJfs045NuV4/tFBHyh8w4 YhnU4HYV+4MlF1ug6WxqY/pDZrE7nflOU34dtaEPFsMsjDLDRGMtA2oqG g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CFAQAyuddX/5pdJa1dGgEBAQECAQEBAQgBAQEBgzoBAQEBAR5XfAeNLKseggMZDYUuSgKBTDgUAQIBAQEBAQEBXieEYQEBAQMBAQEBNzQQCwIBCBIGHhAnCxcOAgQTG4gnCA6+JQEBAQEBAQEBAQEBAQEBAQEBAQEBARyGMIF5glaEQIMtgi8FlBOFUAGGJIkngW5OhBKJFIxYg3oBHjaEXHCGMH8BAQE
X-IronPort-AV: E=Sophos;i="5.30,327,1470700800"; d="scan'208";a="322824545"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Sep 2016 08:33:38 +0000
Received: from XCH-RTP-010.cisco.com (xch-rtp-010.cisco.com [64.101.220.150]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u8D8Xbdm018833 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <spring@ietf.org>; Tue, 13 Sep 2016 08:33:38 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; Tue, 13 Sep 2016 04:33:36 -0400
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; Tue, 13 Sep 2016 04:33:36 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: SPRING WG <spring@ietf.org>
Thread-Topic: [spring] I-D Action: draft-ietf-spring-segment-routing-central-epe-02.txt
Thread-Index: AQHSDZg/1dhIykcBlE2Y2M3WtZe1BaB3WucA
Date: Tue, 13 Sep 2016 08:33:36 +0000
Message-ID: <822880D4-D7A2-4FC0-97D3-0A2EDB4FF5A1@cisco.com>
References: <147375506057.22203.5288196775100193002.idtracker@ietfa.amsl.com>
In-Reply-To: <147375506057.22203.5288196775100193002.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.253.22]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0645F8408CA6BC4FAE60A9599056B163@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/6dscnAhXdhDDsWFXX6paozB7uTA>
Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-central-epe-02.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: Tue, 13 Sep 2016 08:33:41 -0000
FYI, just a refresh. s. > On Sep 13, 2016, at 10:24 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 Peer Engineering > Authors : Clarence Filsfils > Stefano Previdi > Ebben Aries > Daniel Ginsburg > Dmitry Afanasiev > Filename : draft-ietf-spring-segment-routing-central-epe-02.txt > Pages : 18 > Date : 2016-09-13 > > 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 Peer Engineering (BGP-PE) requirement. The SR-based BGP-PE > solution allows a centralized (SDN) controller to program any egress > peer policy at ingress border routers or at hosts within the domain. > This document is on the informational track. > > > > 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-02 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-central-epe-02 > > > 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/ > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring
- Re: [spring] I-D Action: draft-ietf-spring-segmen… Stefano Previdi (sprevidi)
- [spring] I-D Action: draft-ietf-spring-segment-ro… internet-drafts