Re: [Idr] I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-05.txt
"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Thu, 12 May 2016 09:06 UTC
Return-Path: <sprevidi@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 82F9F12D139 for <idr@ietfa.amsl.com>; Thu, 12 May 2016 02:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level:
X-Spam-Status: No, score=-15.517 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.996, 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 lRnkCbVyMcLP for <idr@ietfa.amsl.com>; Thu, 12 May 2016 02:06:47 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87C7812D096 for <idr@ietf.org>; Thu, 12 May 2016 02:06:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3992; q=dns/txt; s=iport; t=1463044007; x=1464253607; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=srOzRXFVhK8bn8TOzNDFZtzva+nSto3kNJrRWf+bOjw=; b=AxBLERIWmQXu6BWRIh8uzxQgDCoiMfTwuEzAmpGOGaWhcnYDU2EcjR3A lQ+wFlfbAkDXZbuCch91ZkFEcqDxqhcE60Lk7ta1Yk+oOAVw2GZpQAIrg s/bHmhoCfYifVxWUyA+PRwcmS6DiSqDwyHe/O2Tcw6uyJN+weO2WiTt5/ Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D+AQC3RjRX/5BdJa1egzhVfQa5VAENgXYXDYVwAhyBGDgUAQEBAQEBAWUnhEIBAQEDAQEBASAROhALAgEIEgYCAiYCAgIlCxUCDgIEEwmIHggOqkqRBgEBAQEBAQEBAQEBAQEBAQEBAQEBARV8hSSBdoJWhz8rgi4FkzCEdwGFfYJ4hSiBaU6EAYhhhi2BQ4dQAR4BAUKDa24BhzF/AQEB
X-IronPort-AV: E=Sophos;i="5.24,609,1454976000"; d="scan'208";a="103499229"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 May 2016 09:06:46 +0000
Received: from XCH-RTP-008.cisco.com (xch-rtp-008.cisco.com [64.101.220.148]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u4C96k6w014943 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <idr@ietf.org>; Thu, 12 May 2016 09:06:46 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-008.cisco.com (64.101.220.148) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 12 May 2016 05:06:45 -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.1104.009; Thu, 12 May 2016 05:06:45 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: idr wg <idr@ietf.org>
Thread-Topic: I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-05.txt
Thread-Index: AQHRrC2bMO+F/4EN8kqWhWMRpQjvcA==
Date: Thu, 12 May 2016 09:06:45 +0000
Message-ID: <A3827AA2-7F15-40B3-B915-35C569FAF7A5@cisco.com>
References: <20160512090542.14194.35537.idtracker@ietfa.amsl.com>
In-Reply-To: <20160512090542.14194.35537.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.198.108]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5014CCCA53EEC6439A13C23BD7D48FB5@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/mytgvbHLl1EZ6PV9-CMucFLWhWc>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-05.txt
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, 12 May 2016 09:06:49 -0000
Hi, the only update in the -05 version is the revert back to “Egress Peer Terminology (EPE)" terminology. The previous version had the “Peer Engineering (PE)” term which apparently created confusion. Obviously the EPE mechanisms are still applicable to both iBGP and eBGP. Thanks and sorry for the churn. s. > On May 12, 2016, at 11:05 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 Inter-Domain Routing of the IETF. > > Title : Segment Routing BGP Egress Peer Engineering BGP-LS Extensions > Authors : Stefano Previdi > Clarence Filsfils > Saikat Ray > Keyur Patel > Jie Dong > Mach (Guoyi) Chen > Filename : draft-ietf-idr-bgpls-segment-routing-epe-05.txt > Pages : 19 > Date : 2016-05-12 > > 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 outline a BGP-LS extension for exporting BGP peering > node topology information (including its peers, interfaces and > peering ASs) in a way that is exploitable in order to compute > efficient BGP Peering Engineering policies and strategies. > > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/ > > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-idr-bgpls-segment-routing-epe-05 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgpls-segment-routing-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
- [Idr] I-D Action: draft-ietf-idr-bgpls-segment-ro… internet-drafts
- Re: [Idr] I-D Action: draft-ietf-idr-bgpls-segmen… Stefano Previdi (sprevidi)