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

"Acee Lindem (acee)" <acee@cisco.com> Tue, 24 September 2019 15:05 UTC

Return-Path: <acee@cisco.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23DEF1201B7 for <lsvr@ietfa.amsl.com>; Tue, 24 Sep 2019 08:05:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 header.b=gPfuo3BB; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ZHKZw/Xt
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 KzkHm5Z13lkS for <lsvr@ietfa.amsl.com>; Tue, 24 Sep 2019 08:05:07 -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 0BCF3120103 for <lsvr@ietf.org>; Tue, 24 Sep 2019 08:05:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18467; q=dns/txt; s=iport; t=1569337507; x=1570547107; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=/pTU9brNUzdpzqxAA90VJri4qOGUSk+BNjC+gsHHBgc=; b=gPfuo3BB3lJOnBEhw/WatvuQToP8IDBYeuOX0VFREVLD7jygZfucsaji dICNwZqtzPbqnv6i72FGutnfxzKF1o/xeQ9zOB2XzsXZ/lqjntKXtYWSa Yn63K9yEUsXKDWFP3nPDFtDGlNcyK33/k19zEFA5h7nGK6bY7KHAvHGFN c=;
IronPort-PHdr: =?us-ascii?q?9a23=3AskDPkBIaY3F7T6hsY9mcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeCuKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZuMAkD2BPXrdCc9Ws9FUQwt8g=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ArAABOMIpd/5pdJa1iAxoBAQEBAQI?= =?us-ascii?q?BAQEBDAIBAQEBgVMFAQEBAQsBgRsvKScDbVYgBAsqhCKDRwOEUoYlTYFqJZM?= =?us-ascii?q?XhF2BLhSBEANUCQEBAQwBAS0CAQGEPwIXgwojNAkOAgMJAQEEAQEBAgEFBG2?= =?us-ascii?q?FLQyFSgEBAQQSER0BATgPAgEIEQMBAQEoAwICAjAUCQgCBAESIoMAAYEdTQM?= =?us-ascii?q?dAQKiZwKBOIhhc4Eygn0BAQWCSIJFGIIXCYE0AYV4hHKBHhiBfyZrJwwTgkw?= =?us-ascii?q?+hAgcAQE1CQEVEYJEMoImjFmDAYUpiSSOaQqCIpUKG4I2h0uEJYp/jhqZFQI?= =?us-ascii?q?EAgQFAg4BAQWBUjiBWHAVZQGCQVAQFIFOgScBAoJIilNzMneJN4JFAQE?=
X-IronPort-AV: E=Sophos;i="5.64,544,1559520000"; d="scan'208,217";a="636315241"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 24 Sep 2019 15:05:05 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x8OF550c004014 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 24 Sep 2019 15:05:05 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 24 Sep 2019 10:05:05 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 24 Sep 2019 10:05:04 -0500
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 24 Sep 2019 10:05:04 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HJ/y30EqZQwNEYNg3POR0GOpMERO2Qk7p3nKQWJrBuCBjka6K8so1AliTkkKUXfKrHjik348BlD/KepFfCce7TBFG3e+GwJkskjYg8nFqRyRpf+RjQgt+2+kQqY8vuK1BbPi9dauJ9xW1C4ywYjLuS1ZHJgHESylkwr3FaoUp+DHmcTYUux7AQHsEboIngGHT+p3argEGZbwlFN2oYxnbQo9hW+cv31Xqyk0ZZboHdm5O1ESgR/Ri3xJb3RnwV4hi6OWEl4eGJm3/JK/3OPQZjGKWTKDmhi1u9qki3zxbiLGtZXvnGR6keuNGEbePiIeAkpeN6MB/nX4Vop0KudWZQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/pTU9brNUzdpzqxAA90VJri4qOGUSk+BNjC+gsHHBgc=; b=HazJPl/jOKo8x1nt45nkxhYa4WrdPtYTPkBFLXfizSuNcCmgN4/hwOb3fZg+nShR4b69BjTmRjgszjWtJw83IbUNTKvZ4sk17/thrZlpSYFZymJ1ai666WWO0cq+41wIiYX6sMG6TUtj4mjYuikPhs7j7FMpJeM3v/kMWQNvDqS1PCO0PSW0CUfvoBMTcyXGIpdepaNjDibFwxG5ID6xUaLZSqVmxu/70ce6JxYE829X3RjXX+Vm0iNsWlwytmpm8/tqRdtZLqtfatSL4gff42yMQ0BzjFJ18wxUN+1Cf2EsvdglUgipyZEHASbk2Uu4U4q4vtxJcL0a5CiCu939ew==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/pTU9brNUzdpzqxAA90VJri4qOGUSk+BNjC+gsHHBgc=; b=ZHKZw/XtSE+BiqSPs/6nA6QWDmHzD+o/6Uk/IbXPjGYLMsoj3QSRkpIUccHuFZWzgFapskW9Z7VXoeacjimTnsCBbi26w+FMuZDdk2vyr738Lded3rVcT6p8ufiNe52sUCs68JHM+W7k4+uHwqCgpnZY8oq1e32qK+JCp3oj9YA=
Received: from MN2PR11MB4221.namprd11.prod.outlook.com (52.135.38.14) by MN2PR11MB3902.namprd11.prod.outlook.com (10.255.180.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.25; Tue, 24 Sep 2019 15:05:03 +0000
Received: from MN2PR11MB4221.namprd11.prod.outlook.com ([fe80::cdc1:a2cf:eb3:a420]) by MN2PR11MB4221.namprd11.prod.outlook.com ([fe80::cdc1:a2cf:eb3:a420%6]) with mapi id 15.20.2284.023; Tue, 24 Sep 2019 15:05:03 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "YADLAPALLI, CHAITANYA" <cy098d@att.com>, "lsvr@ietf.org" <lsvr@ietf.org>
Thread-Topic: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf
Thread-Index: AQHVcuYo8M/r5JDftkuPWSUyelTbyKc66yvg//++2wA=
Date: Tue, 24 Sep 2019 15:05:02 +0000
Message-ID: <1DBF92B2-D384-4071-9156-B20795F099AB@cisco.com>
References: <D2BB4EDE-97FD-4A82-A93D-45203A34A339@cisco.com> <CA0B675FC61D874D8A9EB2C7B5CEA7872B6A7E11@MISOUT7MSGUSRDG.ITServices.sbc.com>
In-Reply-To: <CA0B675FC61D874D8A9EB2C7B5CEA7872B6A7E11@MISOUT7MSGUSRDG.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [2001:420:c0c4:1002::7c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e6c45375-1cb4-4168-30cb-08d7410093ba
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600167)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3902;
x-ms-traffictypediagnostic: MN2PR11MB3902:
x-microsoft-antispam-prvs: <MN2PR11MB3902CAA4F122F4EB95282E69C2840@MN2PR11MB3902.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0170DAF08C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(396003)(376002)(39860400002)(366004)(199004)(189003)(8936002)(6306002)(54896002)(236005)(6512007)(102836004)(14454004)(478600001)(256004)(33656002)(76116006)(316002)(6486002)(53546011)(6506007)(66946007)(66476007)(229853002)(14444005)(66556008)(6116002)(64756008)(66446008)(110136005)(2501003)(25786009)(71200400001)(7736002)(8676002)(2906002)(2616005)(36756003)(446003)(99286004)(186003)(76176011)(86362001)(9326002)(5660300002)(11346002)(6436002)(46003)(81156014)(476003)(81166006)(66574012)(71190400001)(6246003)(486006); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3902; H:MN2PR11MB4221.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: MqcAGlvqMrILzggGKu6Cce7Nzj5wwWDARFp51nXd7GvyFztc1Pl+gEMa/Ti3ium/s/eJLfMbpfNFbQqpLaSb81EuubIIrMhgK2hUCK+dsdYrW9F52tcpscH9d+h0+4Ncdc7qk7ThHACgwXnT6AcujWIPKpJDhqSwaqXQYWa4qkYq/S5NaYQYKkFdgiBrKegR02TFyFn+WjMTW2z9hwE/s/mLI7Y9iMzR/LD65ol0VYC4Beam+kQnU7KaCNQwbxc+veXL1MLBqqXFiBn06aYfWMhFiHWaGyY3Posfpm9mQoiGexBPGYyVKvAi+dVASrHwEIdG932XHwqvVpldpHegnREt72yHh5HvGOhIg99j6C8OFQqz711Jwl49scbeUESwFSVqlIOt8SCZXPbvit/FOuYeAeN32oU4c7HelEcmuvg=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_1DBF92B2D38440719156B20795F099ABciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e6c45375-1cb4-4168-30cb-08d7410093ba
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Sep 2019 15:05:02.8963 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 9KLCJf2XCEfMOyLADzPMR9NJeX4T937D+YScEK4UVxGHuF1w2/pv5jRgTizba+xt
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3902
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.25, xch-rcd-015.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/Ex7vr9VF1xNjeyJkmCSVjcGP9_8>
Subject: Re: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2019 15:05:10 -0000

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

From: "YADLAPALLI, CHAITANYA" <cy098d@att.com>
Date: Tuesday, September 24, 2019 at 11:02 AM
To: Acee Lindem <acee@cisco.com>om>, "lsvr@ietf.org" <lsvr@ietf.org>
Subject: RE: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf

Correct like a R-Bit.

I have read this draft and I support it.

Thanks,
Chaitanya


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) <acee@cisco.com>
Sent: Tuesday, September 24, 2019 10:42 AM
To: YADLAPALLI, CHAITANYA <cy098d@att.com>om>; lsvr@ietf.org
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?

   R-bit
      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.

Thanks,
Acee




From: Lsvr <lsvr-bounces@ietf.org<mailto:lsvr-bounces@ietf.org>> on behalf of "YADLAPALLI, CHAITANYA" <cy098d@att.com<mailto:cy098d@att.com>>
Date: Tuesday, September 24, 2019 at 10:31 AM
To: "lsvr@ietf.org<mailto:lsvr@ietf.org>" <lsvr@ietf.org<mailto:lsvr@ietf.org>>
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.

Thanks,
Chaitanya


Chaitanya Yadlapalli
Network Infrastructure And Services

AT&T Services, Inc.
200 S Laurel Ave, Middletown, NJ 07722
o  732.420.7977  |  cy098d@att.com<mailto:cy098d@att.com>

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.