Re: [Idr] I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-15.txt
"Ketan Talaulikar (ketant)" <ketant@cisco.com> Mon, 05 March 2018 15:22 UTC
Return-Path: <ketant@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 DE95712711D for <idr@ietfa.amsl.com>; Mon, 5 Mar 2018 07:22:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 2vsST-OPfRwN for <idr@ietfa.amsl.com>; Mon, 5 Mar 2018 07:22:32 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22A951200C1 for <idr@ietf.org>; Mon, 5 Mar 2018 07:22:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3504; q=dns/txt; s=iport; t=1520263352; x=1521472952; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=B/z0EISrumwPODNGJ+z+YTDFBZd8Uw8xPwJGH6rR4Y8=; b=fdiNGiwYUGTfMLB6p2GJZ37j8Ar39pNvDAsrnKz48U+2zbvPztUmMBLq AFxzoUhad1aXUFKfzSH0PQKMK0Cfmf/sAy4sLvaEWhTo3b+UQz7AcNEG4 OhWmS3Qr4VH2zK/qe82q63keMc8xcxpd/X56R9qoRrs0tloN3r267K94n E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DlAABWX51a/4sNJK1cGQEBAQEBAQEBAQEBAQcBAQEBAYNQZnAoCo1ujXmCAoEWlDQUggEKGA2FCwKCcyE0GAECAQEBAQEBAmscC4UjAQEBBAEBODQXBAIBCBEBAwEBHwkHJwsUAwYIAgQTCIUTEKptiGOCK4Utgi6BV4Fmgy2DLgEBAgEBF4E+hgUEiCeSOwkChlKDEocPgXFOcIJ3iFyJfYcrAhEZAYEtAR44gVJwFRkhgkMJgigcgXt3AYthgRgBAQE
X-IronPort-AV: E=Sophos;i="5.47,427,1515456000"; d="scan'208";a="79545746"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Mar 2018 15:22:31 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id w25FMVlY003538 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <idr@ietf.org>; Mon, 5 Mar 2018 15:22:31 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 5 Mar 2018 09:22:27 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1320.000; Mon, 5 Mar 2018 09:22:27 -0600
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-15.txt
Thread-Index: AQHTtImQ/8ehOE5K4UqwV0wsGcsykqPBwbKQ
Date: Mon, 05 Mar 2018 15:22:27 +0000
Message-ID: <6a4a1df67c644035a57e5be2a7080bd9@XCH-ALN-008.cisco.com>
References: <152025805997.14555.17901279590182913258@ietfa.amsl.com>
In-Reply-To: <152025805997.14555.17901279590182913258@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.47.227]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Gu-2zAjM-CuFIvDaYvX7bjAzzcU>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-15.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: Mon, 05 Mar 2018 15:22:35 -0000
Hello, Following are the updates in this version : 1) Removal of the MUST clause for BGP-LS Identifier since it is not mandatory for many EPE use-cases. BGP-LS Identifier can still be used as the draft allows for use of Node Descriptors from RFC7752. 2) References to IPv6 SID in the document were removed and the specification is now covered in https://datatracker.ietf.org/doc/draft-dawra-idr-bgpls-srv6-ext/ where it is now consistent with https://datatracker.ietf.org/doc/draft-filsfils-spring-srv6-network-programming/ 3) The SID Flags section is updated to include the B & P flags. The B flag was described in companion use-case draft https://tools.ietf.org/html/draft-ietf-spring-segment-routing-central-epe-10#section-3.6 but was missed from this draft. Apart from this there are minor nits updated based on review comments. Thanks, Ketan -----Original Message----- From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: 05 March 2018 19:24 To: i-d-announce@ietf.org Cc: idr@ietf.org Subject: [Idr] I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-15.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing WG 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-15.txt Pages : 21 Date : 2018-03-05 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-15 https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgpls-segment-routing-epe-15 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgpls-segment-routing-epe-15 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/ _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr
- [Idr] I-D Action: draft-ietf-idr-bgpls-segment-ro… internet-drafts
- Re: [Idr] I-D Action: draft-ietf-idr-bgpls-segmen… Ketan Talaulikar (ketant)