[Idr] FW: New Version Notification for draft-ketant-idr-bgp-ls-bgp-only-fabric-00.txt

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Sat, 03 March 2018 15:58 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 7FE671242F7 for <idr@ietfa.amsl.com>; Sat, 3 Mar 2018 07:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 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, 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 hmaNAIDXLIAX for <idr@ietfa.amsl.com>; Sat, 3 Mar 2018 07:58:08 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99BF3124F57 for <idr@ietf.org>; Sat, 3 Mar 2018 07:58:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3438; q=dns/txt; s=iport; t=1520092688; x=1521302288; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=5y5gtCfVrW2PnJLScrfE/8R/jupBBsUAjmQFBp2Gytc=; b=PX7uNEAHlDoTmhNPxWWGBz/wxlWA+jq7jTUZ8q/fRd1KRqrHPKgtdOS9 rUD1Nfoqd88V287K1FzH/Ig2hyHELoY6ESeSkesS/RgEBzf6BAgGX6jBQ 1CUcyXXNBowc9vG6vuyZhx9h3fnf5HVk8FmiH27w74PUDMjLnJKhskAI7 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D2AAB/xZpa/4kNJK1bGQEBAQEBAQEBAQEBAQcBAQEBAYMfMWZwKAqDSookjXmCAoEWlDSCFQolhQsCGoJHITQYAQIBAQEBAQECaxwLhSMBAQEEIxFDDgQCAQgRBAEBAwIjAwICAjAUAQYBAQUDAgQTCIUTEKh2gieIYoIrgQ+EHoIugVeBZoMtgy4BAQIBAYR4gmIEjXmMaQkChlKKIYFxToNniFyJfYcrAhEZAYEtAR44gVJwFRmCZAmEP3cBin+BGAEBAQ
X-IronPort-AV: E=Sophos;i="5.47,418,1515456000"; d="scan'208";a="363207348"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Mar 2018 15:58:07 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w23Fw7sT005772 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <idr@ietf.org>; Sat, 3 Mar 2018 15:58:07 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sat, 3 Mar 2018 09:58:06 -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; Sat, 3 Mar 2018 09:58:06 -0600
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: New Version Notification for draft-ketant-idr-bgp-ls-bgp-only-fabric-00.txt
Thread-Index: AQHTswcPHXLDep/YiEG9wZKQHAE6SaO+qfCw
Date: Sat, 03 Mar 2018 15:58:06 +0000
Message-ID: <06146ed9ab24497da1411caaf5d687ef@XCH-ALN-008.cisco.com>
References: <152009210169.8298.1979166695647932486.idtracker@ietfa.amsl.com>
In-Reply-To: <152009210169.8298.1979166695647932486.idtracker@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.72]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3SQWuUYAgpEsuj525sFsG5ErDfE>
Subject: [Idr] FW: New Version Notification for draft-ketant-idr-bgp-ls-bgp-only-fabric-00.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: Sat, 03 Mar 2018 15:58:10 -0000

Hello All,

This new draft describes the procedures for advertisement of the network topology in a BGP-only network (e.g. a MSDC) using BGP-LS and describes a TE use-case that leverages the same.

Look forward to discuss and review this with the WG.

Thanks,
Ketan

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: 03 March 2018 21:18
To: Krishna Muddenahally Ananthamurthy (kriswamy) <kriswamy@cisco.com>; Gaurav Dawra <szandi@linkedin.com>; Krishna Muddenahally Ananthamurthy (kriswamy) <kriswamy@cisco.com>; Ketan Talaulikar (ketant) <ketant@cisco.com>; Shawn Zandi <szandi@linkedin.com>; Clarence Filsfils (cfilsfil) <cfilsfil@cisco.com>
Subject: New Version Notification for draft-ketant-idr-bgp-ls-bgp-only-fabric-00.txt


A new version of I-D, draft-ketant-idr-bgp-ls-bgp-only-fabric-00.txt
has been successfully submitted by Ketan Talaulikar and posted to the IETF repository.

Name:		draft-ketant-idr-bgp-ls-bgp-only-fabric
Revision:	00
Title:		BGP Link-State Extensions for BGP-only Fabric
Document date:	2018-03-03
Group:		Individual Submission
Pages:		21
URL:            https://www.ietf.org/internet-drafts/draft-ketant-idr-bgp-ls-bgp-only-fabric-00.txt
Status:         https://datatracker.ietf.org/doc/draft-ketant-idr-bgp-ls-bgp-only-fabric/
Htmlized:       https://tools.ietf.org/html/draft-ketant-idr-bgp-ls-bgp-only-fabric-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ketant-idr-bgp-ls-bgp-only-fabric-00


Abstract:
   BGP is used as the only routing protocol in some networks today.  In
   such networks, it is useful to get a detailed view of the nodes and
   underlying links in the topology along with their attributes similar
   to one available when using link state routing protocols.  Such a
   view of a BGP-only fabric enables use cases like traffic engineering
   and forwarding of services along paths other than the BGP best path
   selection.

   This document defines extensions to the BGP Link-state address-family
   (BGP-LS) and the procedures for advertisement of the topology in a
   BGP-only network.  It also describes a specific use-case for traffic
   engineering based on Segment Routing.


                                                                                  


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.

The IETF Secretariat