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

Keyur Patel <keyur@arrcus.com> Thu, 03 October 2019 17:18 UTC

Return-Path: <keyur@arrcus.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 12F9D120164 for <lsvr@ietfa.amsl.com>; Thu, 3 Oct 2019 10:18:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netorgft1331857.onmicrosoft.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 q1i6zBW1sZH2 for <lsvr@ietfa.amsl.com>; Thu, 3 Oct 2019 10:18:51 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on061e.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe41::61e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CD661201B7 for <lsvr@ietf.org>; Thu, 3 Oct 2019 10:18:51 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=A2RkfkAIAJxN8NT4s5V03sWFsiSIkh0bnNop3EMiL0Dgy9CC1w8F6fPDzyKAJho9XEenD9ZptwAxkkMTxuyejdKjvik/Bi6UAvidudml61pquERbV0k87b0HQkA1sngp1Qy2dPsWrYSlGRJIE7GQMiy9HT1aKBOJUxePz9mKVht3ksTZcgOZ1CjPbG/78oxeyA97tDb4y92KK4hkNqewnjdkd2mJ1Z8lcM4PF5paHhQH5hzU3taGrhClVqbPCXozRa212f5NeFtpUwHUtGC7NpYOf5OhZUkp+luzqHJTMAw5nDs6rCeVyrtu5hIYmSg0nH5UcI55x+8wTKeaQO0Oqw==
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=t07O8b5+RF9TRnyPwGZJfEPhRN3lRHeAbHGZ0hBw7tc=; b=KVY6iT2oU3mtmIDoMcYhYu8fi3YsAALj4ZBDf/SiLatmrj1Ex79OMaMRjBxYUgfTCtjMKk+9IEZz20BM0RFf+URQ1RKQIf4E0SCSitO+9uthJsD+tv0zfvlTnvaXzTeKMpO4f73WmDlKBqqhykngM7FZ5R7m31XM/w7mH4CgIAY5cNsmmscpjRQL7H9YGz0FTNzDda7IWBkGOnchPm5R1btJbEW2SSCfxgCQQMjp9qndlJgEwsb+V5gU0G7Dr1hGh5PY96Ilc3y/gl2AzY7n0/cLWiM5S4ed3m6eQDJprq9VRznUPKOP6nwPq1Aw+jxsAY4kH6g2agAbzUnf6TmicA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arrcus.com; dmarc=pass action=none header.from=arrcus.com; dkim=pass header.d=arrcus.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT1331857.onmicrosoft.com; s=selector2-NETORGFT1331857-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=t07O8b5+RF9TRnyPwGZJfEPhRN3lRHeAbHGZ0hBw7tc=; b=iSnMcVoYNPIwGtyDK+ei+Ns3olOt4ymVR/PAbcejOAV/F/ATRxkILWR4fXRjE2sLjiA5HhU0WuMCt8YKJLDu7T40YZUaxA0aTCKdSHGgdu9ZdJwjWR4YKFV3I+RgGleQxrZR6Yy4ufY9MuGncFfI5Ll/rMTT+QeuK4CryU33V6s=
Received: from BYAPR18MB2856.namprd18.prod.outlook.com (20.179.59.30) by BYAPR18MB2853.namprd18.prod.outlook.com (20.179.58.79) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.20; Thu, 3 Oct 2019 17:18:48 +0000
Received: from BYAPR18MB2856.namprd18.prod.outlook.com ([fe80::6182:28f2:3566:d173]) by BYAPR18MB2856.namprd18.prod.outlook.com ([fe80::6182:28f2:3566:d173%3]) with mapi id 15.20.2305.023; Thu, 3 Oct 2019 17:18:48 +0000
From: Keyur Patel <keyur@arrcus.com>
To: Santosh P K <santosh.pallagatti@gmail.com>, "Acee Lindem (acee)" <acee@cisco.com>
CC: Pushpasis Sarkar <pushpasis.ietf@gmail.com>, "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//++2wCAAt4nAIAAOHMAgAQ5fQCABD5igIAAEqkAgALBcoD//7V8gA==
Date: Thu, 3 Oct 2019 17:18:48 +0000
Message-ID: <5E9B33AF-9310-4E91-BB4B-D6AFF1FABD99@arrcus.com>
References: <D2BB4EDE-97FD-4A82-A93D-45203A34A339@cisco.com> <CA0B675FC61D874D8A9EB2C7B5CEA7872B6A7E11@MISOUT7MSGUSRDG.ITServices.sbc.com> <1DBF92B2-D384-4071-9156-B20795F099AB@cisco.com> <CAEFuwki8QBRL=ZXFy46RCgTyUX4ffYvVAeRe-rFwbcqL=zLRLw@mail.gmail.com> <0A1F41E2-AC1E-4724-A8B6-DE855088FDF4@cisco.com> <1B89E943-C2D0-41C9-B8FE-17CA7F0240EA@cisco.com> <CAEFuwkg_dg2ASfjqzo1_MAfOHh+HB6jLecftFgRh0wTaYRJgYA@mail.gmail.com> <0ED4311E-0D67-401F-BB18-B34865174DB4@cisco.com> <CACi9rdswLh2j4f_VdMKowYk9dD1fqGW_SBxLsBYTPTsr2SP7Gg@mail.gmail.com>
In-Reply-To: <CACi9rdswLh2j4f_VdMKowYk9dD1fqGW_SBxLsBYTPTsr2SP7Gg@mail.gmail.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=keyur@arrcus.com;
x-originating-ip: [70.234.233.187]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 690d7589-355e-41cc-6f89-08d74825c0ef
x-ms-traffictypediagnostic: BYAPR18MB2853:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BYAPR18MB28535923296EB4779F09E0F1C19F0@BYAPR18MB2853.namprd18.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 01792087B6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39830400003)(136003)(376002)(346002)(366004)(396003)(199004)(189003)(6512007)(6436002)(256004)(54896002)(14444005)(6306002)(5660300002)(3846002)(66574012)(26005)(33656002)(6486002)(6116002)(110136005)(606006)(54906003)(76176011)(8676002)(81166006)(81156014)(186003)(8936002)(966005)(36756003)(99286004)(508600001)(316002)(6246003)(102836004)(6506007)(14454004)(11346002)(446003)(9326002)(4326008)(486006)(229853002)(476003)(2616005)(236005)(2906002)(7736002)(76116006)(66066001)(66476007)(66446008)(66946007)(66556008)(71190400001)(64756008)(71200400001)(86362001)(25786009)(53546011); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR18MB2853; H:BYAPR18MB2856.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: arrcus.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: dcoFu6Y84Qx+eD00iAlq4CnyRSwlU9BwNMSPg175IyWXCC8CGNmC3T+nCaMKV3RB+wMqqfGQ0+SUYTtBTDGsA6SnsvnziBbKMvFbtoEabMVnjKaKsYo/Qvbnmxm1EpU9ICv+WhkrT93aZb2yY93TQBX+d1dj3TsaRayJMs9qmI3QU9NsPYl2xtlDnYbo8l6pqqlbZXfrO3rE9ohLmGvAWQlwHlsxIp6/2D7v/xuZFduTf/06OTo4Gc6MHuZH3PYz5Nf/XE9SrUw5o1ON7UKrSUY8x7IHSvZ8ky3c1yBkD9UmGBcvqHebnKAsEzU7bfO/8CSwTCl7ocpA+SAIW6iCb4VyT2zEDJpuUBiclB8WNAp2afHMz/3Lv8zurE50aLaLFmz7X+keGjKUIg9+C2tlwWh9Hof0eHiJfoSuUfbiAqe9dU8UXhRDmsf+ViJP0GW/blHRZeWNBduhOpdTJHqWbg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_5E9B33AF93104E91BB4BD6AFF1FABD99arrcuscom_"
MIME-Version: 1.0
X-OriginatorOrg: arrcus.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 690d7589-355e-41cc-6f89-08d74825c0ef
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Oct 2019 17:18:48.2492 (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: 2puW7Cbfnm462xnVvzRGgNLagtuFgqVH9nsLqSIuOSWZApX7oiMH93mA3f+OlWJX/aj+1qmStTf/43RG7PTpWw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR18MB2853
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/PmFR64VswNUEuATmRdtzyPs2qys>
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: Thu, 03 Oct 2019 17:18:56 -0000

Hi Santosh,

We can add the use case in the applicability draft. This bit could be used when you have a RR/Controller based peering model in CLOS (where RR/Controllers are not in the forwarding path). You may want RR/Controller to announce its reachability using H-bit so that they are not being used as a transit.

Regards,
Keyur

From: Lsvr <lsvr-bounces@ietf.org>; on behalf of Santosh P K <santosh.pallagatti@gmail.com>;
Date: Thursday, October 3, 2019 at 7:46 AM
To: "Acee Lindem (acee)" <acee@cisco.com>;
Cc: Pushpasis Sarkar <pushpasis.ietf@gmail.com>;, "YADLAPALLI, CHAITANYA" <cy098d@att.com>;, "lsvr@ietf.org"; <lsvr@ietf.org>;
Subject: Re: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf
Resent-From: <keyur@arrcus.com>;

All,
    If R-bit or H-bit functionality is being introduced then wanted to know should you not callout for use case here? Use-cases in applicability document does not cover this and would like to also understand how this can be used CLOS and non-CLOS/FAT-tree topology..


Thanks
Santosh P K

On Wed, Oct 2, 2019 at 6:10 AM Acee Lindem (acee) <acee@cisco.com<mailto:acee@cisco.com>> wrote:
Hi Pushpasis,

From: Pushpasis Sarkar <pushpasis.ietf@gmail.com<mailto:pushpasis.ietf@gmail.com>>
Date: Tuesday, October 1, 2019 at 3:34 PM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>
Cc: "YADLAPALLI, CHAITANYA" <cy098d@att.com<mailto:cy098d@att.com>>, "lsvr@ietf.org<mailto:lsvr@ietf.org>" <lsvr@ietf.org<mailto:lsvr@ietf.org>>
Subject: Re: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf

Hi Acee,

Just saw the latest version of the draft. I wanted to understand what is the exact difference between the values 1 and 2. Just to clarify my doubt let's consider a prefix P that is only originated by node N. Now what will be the reachability of prefix P in the two scenarios (first with SPF Status TLV value set to 1 vs with SPF Status TLV value set to 2). Will P be unreachable in both cases? My understanding is it should still be reachable when the value is set to 2.

If my understanding is correct, then perhaps we need more clarifications on the following text.. especially for the case there is no next link from this node.

"If the current Node NLRI attributes includes the SPF status

          TLV (Section 4.1.2) and the status indicates that the Node

          doesn't support transit, the next link for the current node is
          processed."

If the P is unreachable in the later case too (value set to 2), then I don't see what is the difference between using the values 1 and 2.

In this case, the current node is not unreachable as we’ve already taken it off the candidate list and processed the local prefixes. Optionally, the interface addresses on the current node have also been installed. At this point, we are simply not using any of the links in the SPF graph which will have the effect of preventing transit traffic.

Thanks,
Acee

Thanks
-Pushpasis






On Sun, Sep 29, 2019 at 12:15 PM Acee Lindem (acee) <acee@cisco.com<mailto:acee@cisco.com>> wrote:
After discussion with my co-authors and Pushpasis, we are planning on defining an SPF Status TLV for the Node Attribute NLRI analogous to the one defined for Links and Prefixes. However, for the Node Attribute TLV, the status would have an additional value indicating the node should not be used for transit traffic.

                          0 – Reserved
                          1 – Node unreachable with respect to BGP SPF
                          2 – Node does not support transit with respect to BGP SPF
                  3-254 – Undefined
                      255 – Reserved

Comments?

Thanks,
Acee


From: Lsvr <lsvr-bounces@ietf.org<mailto:lsvr-bounces@ietf.org>> on behalf of Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>
Date: Thursday, September 26, 2019 at 10:15 AM
To: Pushpasis Sarkar <pushpasis.ietf@gmail.com<mailto:pushpasis.ietf@gmail.com>>
Cc: "YADLAPALLI, CHAITANYA" <cy098d@att.com<mailto:cy098d@att.com>>, "lsvr@ietf.org<mailto:lsvr@ietf.org>" <lsvr@ietf.org<mailto:lsvr@ietf.org>>
Subject: Re: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf

Hi Pushpasis,
This OSPFv3 R Bit and IS-IS O bit are basically the same functionality. The node is not used for transit but is used for local prefixes.
Thanks,
Acee

From: Pushpasis Sarkar <pushpasis.ietf@gmail.com<mailto:pushpasis.ietf@gmail.com>>
Date: Thursday, September 26, 2019 at 2:53 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>
Cc: "YADLAPALLI, CHAITANYA" <cy098d@att.com<mailto:cy098d@att.com>>, "lsvr@ietf.org<mailto:lsvr@ietf.org>" <lsvr@ietf.org<mailto:lsvr@ietf.org>>
Subject: Re: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf

Hi Chaitanya and Acee,

How about the 'O' bit in Node-Flag-Bits TLV defined in RFC 7752 section 3.3.1.1? I suppose the node can set the 'O' bit when it wants to take itself out from all transit paths. I know the 'O' bit is more related to the scenario when ISIS topology is being exported in BGP-LS. But I suppose we can use that for BGP-LS-SPF as well.

Thanks
-Pushpasis

On Tue, Sep 24, 2019 at 8:35 PM Acee Lindem (acee) <acee@cisco.com<mailto:acee@cisco.com>> wrote:
Hi Chaitanya,
I think this is a good idea and will discuss with my co-authors.
Thanks,
Acee

From: "YADLAPALLI, CHAITANYA" <cy098d@att.com<mailto:cy098d@att.com>>
Date: Tuesday, September 24, 2019 at 11:02 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, "lsvr@ietf.org<mailto:lsvr@ietf.org>" <lsvr@ietf.org<mailto: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<mailto:acee@cisco.com>>
Sent: Tuesday, September 24, 2019 10:42 AM
To: YADLAPALLI, CHAITANYA <cy098d@att.com<mailto:cy098d@att.com>>; lsvr@ietf.org<mailto: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.


_______________________________________________
Lsvr mailing list
Lsvr@ietf.org<mailto:Lsvr@ietf.org>
https://www.ietf.org/mailman/listinfo/lsvr
_______________________________________________
Lsvr mailing list
Lsvr@ietf.org<mailto:Lsvr@ietf.org>
https://www.ietf.org/mailman/listinfo/lsvr