Re: [Idr] I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-12.txt

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Fri, 28 April 2017 11:16 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 48FB61201F2 for <idr@ietfa.amsl.com>; Fri, 28 Apr 2017 04:16:58 -0700 (PDT)
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 o-vD7d6BZOZN for <idr@ietfa.amsl.com>; Fri, 28 Apr 2017 04:16:56 -0700 (PDT)
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 698A812751F for <idr@ietf.org>; Fri, 28 Apr 2017 04:13:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2745; q=dns/txt; s=iport; t=1493378025; x=1494587625; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=MMZyWceM8RX6u2D0pOb7TRxNgpogYdcqKxWX/K2OyrM=; b=XiBObE7ViJQsdBrAl2t6nhGAM0fzYE9qcxR8sMZCypOYnXZy1o6NGklk QGmKGjqt2Qz+ErFFcDRk77YySVxzyyuVWoKxu22ujGe6ff2FnKPj8+dID 1VN3Ew3NJvXlMBfh2hGRJz59e5IKF1gyGKf3/PX+/cvAOcLsol9Cb+hYC Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DNAACGIgNZ/5JdJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1VhgQwHjXmRTpVsgg8hDYV2AoQvPxgBAgEBAQEBAQFrKIUVAQE?= =?us-ascii?q?BAQIBAQE4NBALAgEIEgYeECcLFw4CBBMJig4IDrAyiwUBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEdhl+BXiuCb4MggT8ygwKCMQWdUAGHGIMxiEKCAlWEYooli0CIZgE?= =?us-ascii?q?fOIEKbxUaKhIBhl11AYZegQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,387,1488844800"; d="scan'208";a="416167345"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Apr 2017 11:13:44 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v3SBDhrZ005388 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <idr@ietf.org>; Fri, 28 Apr 2017 11:13:44 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, 28 Apr 2017 07:13:43 -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; Fri, 28 Apr 2017 07:13:43 -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-12.txt
Thread-Index: AQHSwBB+fPCad9InFEKiP898hVvPQA==
Date: Fri, 28 Apr 2017 11:13:42 +0000
Message-ID: <D4C457E0-C567-493B-B9F7-66E62DFC78B2@cisco.com>
References: <149337795343.2975.11840522747921489092@ietfa.amsl.com>
In-Reply-To: <149337795343.2975.11840522747921489092@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.162.46]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <26F0CBFA69F8414AB525D488C19BA4AE@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/z-Rkl2yqmwDSPsew0_4TEIm_K1I>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-12.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 28 Apr 2017 11:16:58 -0000

updated version after various comments and reviews.

Thanks.
s.


> On Apr 28, 2017, at 1:12 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 Inter-Domain Routing of the IETF.
> 
>        Title           : BGP-LS extensions for Segment Routing BGP Egress Peer Engineering
>        Authors         : Stefano Previdi
>                          Clarence Filsfils
>                          Keyur Patel
>                          Saikat Ray
>                          Jie Dong
> 	Filename        : draft-ietf-idr-bgpls-segment-routing-epe-12.txt
> 	Pages           : 21
> 	Date            : 2017-04-28
> 
> 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 are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-idr-bgpls-segment-routing-epe-12
> https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgpls-segment-routing-epe-12
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgpls-segment-routing-epe-12
> 
> 
> 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