Re: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf

Keyur Patel <> Thu, 26 September 2019 21:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DD1F2120154 for <>; Thu, 26 Sep 2019 14:44:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ol53aD5_0y8v for <>; Thu, 26 Sep 2019 14:44:28 -0700 (PDT)
Received: from ( [IPv6:2a01:111:f400:fe49::60f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A3871120114 for <>; Thu, 26 Sep 2019 14:44:27 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=DuxYR1r0k5LqsjeA7ZQPr8ij8VXt5en4S4efC5JsFebn5SxVqRRFAQW3g6EDeyvky40w0QrdJUaTOFpLTii5H54zuzvu2+syTySVhrjdb20ihSbaGB9B/WN0HpiLw+yw+TQcg9OtD1Owq4XAZo3NzKOiwEadAu8clCOunnILhLaZBJIqF5ujCJ/7gyfgNdU5sMT433FimZ7+N42bdY7v6b0Hv6C+D7rQRZIOA4R38TymjsAxJPpm6O/lA4Svy2Br3gBfi8D5VtokZv5ozgLNrM0+V/jLYG6Ttvzi9TPjHS0E7QwoSs6zSA8VqIzv/Mrqjow20O3HSykk71Y9meqJ2Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5D/qLSJm2NGQ8gkapgEwiloL3DyEV8E5rj4k1VDLJiI=; b=e3hajvkhd9az12w8IoOoW4SuVlQuXTgzHTCBjDTjGvHwRektaViXWBXsxoUADl7b/SKERmrVk8j/zxPgMhPgSlQsGVP7DzzQC0TfnIJXj3Kl9ug6AvxJsl60m6Occ9akhYn8sI2IwZHbwJWeSIdxGRE8kdO9elVWyKpg6nisZLBJ3RYoCAZs7VyH8QAVBxzUV7Bu4RfdIelahGZs4SSZKiYSVf+HS8rBjlQMHKHg3NxD0O9zHYtoYbt+zqVUN3lsTaFCWewnmNB1HMupUzhbgHrAiSyG8x9CD2o7pc8GDojY/+C/ssJnqAo4rnsTzdeE1iDbxst/UoaSZEGo3YsVpA==
ARC-Authentication-Results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector2-NETORGFT1331857-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5D/qLSJm2NGQ8gkapgEwiloL3DyEV8E5rj4k1VDLJiI=; b=Jt9oM2O8WkBi2QX5VjauxiXBoVzPX7HPLw4aFFbwiRu6Pw2yLD0a4lk+BhftPo9H4Sgob77adkplzlxpdtSgZFctzfwSib01lDIpetrTH/1AWEX4ILqZ4fV+SuCnRVi6Mw8vTnitJ7w3BLORJhALcleIVvMVJ+dvVDkyD9Frk9k=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.17; Thu, 26 Sep 2019 21:44:25 +0000
Received: from ([fe80::b521:31ad:de0d:f5a7]) by ([fe80::b521:31ad:de0d:f5a7%6]) with mapi id 15.20.2284.028; Thu, 26 Sep 2019 21:44:25 +0000
From: Keyur Patel <>
To: "Acee Lindem (acee)" <>, "YADLAPALLI, CHAITANYA" <>, "" <>
Thread-Topic: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf
Thread-Index: AQHVcuYo8M/r5JDftkuPWSUyelTbyKc66yvg//++2wCAA5RAgA==
Date: Thu, 26 Sep 2019 21:44:25 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 70371388-13e8-4f19-7946-08d742cab38f
x-ms-traffictypediagnostic: BYAPR18MB3030:
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0172F0EF77
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39830400003)(396003)(136003)(366004)(346002)(376002)(189003)(199004)(36756003)(86362001)(14454004)(508600001)(66574012)(486006)(6436002)(5660300002)(476003)(6512007)(6486002)(2616005)(54896002)(6306002)(236005)(25786009)(71200400001)(316002)(110136005)(2906002)(71190400001)(66556008)(64756008)(6116002)(3846002)(256004)(14444005)(66066001)(8676002)(81166006)(8936002)(81156014)(76116006)(6246003)(66946007)(2501003)(66476007)(66446008)(446003)(76176011)(102836004)(53546011)(6506007)(26005)(99286004)(186003)(229853002)(11346002)(7736002)(33656002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR18MB3030;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: pCRP0s3xSp8L0LsDtUvYkSYaDTSkqpprTCIH75hN7iHDBvr9r0w98oGX69sTnR1OL6PlKYUJwcLiJlguXk/k9iaJyXsoLnHaTKcAet59DJ7DpvNUrKXy1EZgawgzHxJwXTiABOFIpsJGunFpZuo+E/P2VnSehsexI4TuhwoRMeTeC6eEULdY2muWbYotOzwXRfpNPVfOGIuyZhoMLjka9IiDmQTo53hMzIX1bJNGcVkdSFEe0QajVi8vNhat5bimLGR/VFFK7tB21jCvVW1IJwzSMBpAFZp//p3fncbD+v6FzhluZ/QAFQ2Y21g1iZRp/pf+9kyIovper49y7WdZMVF2OoAXXE4cOO3Q7PbWiTSwpKKsQgX5iwl4fapusLQJGex714L/xj3FphtgurPdkCd05eg1O5w6sHbu6gUOb/Q=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_E3F532F0D12E4319822DBED552B343F7arrcuscom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 70371388-13e8-4f19-7946-08d742cab38f
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Sep 2019 21:44:25.7826 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 697b3529-5c2b-40cf-a019-193eb78f6820
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: OjdYjGrOoiLqm0qWxO8rlDf0X4nkG+nTmaIgHaTvYv58pnzlZozk/tLlLWQS7dSspSE/bGLVbHXrIeHCk+YKDA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR18MB3030
Archived-At: <>
Subject: Re: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Vector Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 26 Sep 2019 21:44:31 -0000

Hi Chaitanya, Acee,

I agree it’s a good idea. I was checking base LS and it seems that the functionality is missing. Maybe we add this feature as a separate LS draft and cover it in SPF as an extension?


From: Lsvr <> on behalf of "Acee Lindem (acee)" <>
Date: Tuesday, September 24, 2019 at 8:05 AM
To: "YADLAPALLI, CHAITANYA" <>om>, "" <>
Subject: Re: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf
Resent-From: <>

Hi Chaitanya,
I think this is a good idea and will discuss with my co-authors.

Date: Tuesday, September 24, 2019 at 11:02 AM
To: Acee Lindem <>om>, "" <>
Subject: RE: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf

Correct like a R-Bit.

I have read this draft and I support it.


This communication may contain information that is privileged, or confidential. If you are not the intended recipient, please note that any dissemination, distribution or copying of this communication is strictly prohibited.  Anyone who receives this message in error should notify the sender immediately by telephone or by return e-mail and delete it from his or her computer.

From: Acee Lindem (acee) <>
Sent: Tuesday, September 24, 2019 10:42 AM
Subject: Re: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf

Hi Chaitanya,

Exactly what do you mean by node cost out and what use case are you trying to satisfy. If a node wants to remove itself from the topology, it can simply withdraw its link NLRI. However, are you looking for a mechanism similar to the OSPFv3 R-Bit as a Node NLRI SPF Attribute?

      This bit (the `Router' bit) indicates whether the originator is an
      active router.  If the router bit is clear, then routes that
      transit the advertising node cannot be computed.  Clearing the
      router bit would be appropriate for a multi-homed host that wants
      to participate in routing, but does not want to forward non-
      locally addressed packets.


From: Lsvr <<>> on behalf of "YADLAPALLI, CHAITANYA" <<>>
Date: Tuesday, September 24, 2019 at 10:31 AM
To: "<>" <<>>
Subject: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf

Hi Authors,
The draft does not explicitly call out mechanisms for node cost out. It would be good to call out mechanisms to cost out a node explicitly.


Chaitanya Yadlapalli
Network Infrastructure And Services

AT&T Services, Inc.
200 S Laurel Ave, Middletown, NJ 07722
o  732.420.7977  |<>

This communication may contain information that is privileged, or confidential. If you are not the intended recipient, please note that any dissemination, distribution or copying of this communication is strictly prohibited.  Anyone who receives this message in error should notify the sender immediately by telephone or by return e-mail and delete it from his or her computer.