Re: [Lsr] draft-ietf-lsr-isis-area-proxy-02

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 05 August 2020 23:02 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD7353A089D for <lsr@ietfa.amsl.com>; Wed, 5 Aug 2020 16:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=iwRmjJ6D; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=egHJNQVJ
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 HMECXOv6U_IA for <lsr@ietfa.amsl.com>; Wed, 5 Aug 2020 16:02:49 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E075A3A0898 for <lsr@ietf.org>; Wed, 5 Aug 2020 16:02:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13898; q=dns/txt; s=iport; t=1596668568; x=1597878168; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=0TK6GMDRmSctQVMc+c3B6K+PxEcUUYCG1Tlal0xccuk=; b=iwRmjJ6DEDSDoPD7yz/v1fjfT46Aen/mLb4ompqNRqBBht1u2rmS0TJ+ BK+gL3FbeZVaiTKymOtRahllfQ6vNpKwPYwgpOrcJla0o7wDAHGkLsU9T wjEdhUp1+kVX6Smrm47AJsP1F5hCWGzHnhMkrGOK/eKunEtZCNa1HV0w8 8=;
IronPort-PHdr: 9a23:cJ8maRInd1Phn8s73tmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeGvKk/g1rAXIGd4PVB2KLasKHlDGoH55vJ8HUPa4dFWBJNj8IK1xchD8iIBQyeTrbqYiU2Ed4EWApj+He2YkdQEcf6IVbVpy764TsbAB6qMw1zK6z8EZLTiMLi0ee09tXTbgxEiSD7b6l1KUC9rB7asY8dho4xJw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CoBQALOitf/5ldJa1WChwBAQEBAQEHAQESAQEEBAEBggqBIy9RB29YLyyENoNGA41RigSJcoRsglMDVQMIAQEBDAEBLQIEAQGETAIXghECJDgTAgMBAQsBAQUBAQECAQYEbYVcDIVxAQEBBBIRChMBATcBDwIBBgIRBAEBKwICAh8RHQgCBA4FCBqDBYF+TQMuAZhIkGgCgTmIYXaBMoMBAQEFhSYNC4IOCYE4gnCDX4Y/GoFBP4ERQ4JNPoIagXYvgxUzgi2QEIJqhl+bdE8KgmKVEoUan36fQpIRAgQCBAUCDgEBBYFqI4FXcBWDJFAXAg2OHwwXg06KVnQ3AgMDAQcBAQMJfI8nAQE
X-IronPort-AV: E=Sophos;i="5.75,439,1589241600"; d="scan'208,217";a="798979341"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Aug 2020 23:02:47 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 075N2lCw029235 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 5 Aug 2020 23:02:47 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 5 Aug 2020 18:02:47 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 5 Aug 2020 19:02:46 -0400
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 5 Aug 2020 18:02:46 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=k4mv+HQS8fezYjvH3P08WfDFJFeIJp8Vo74GDuOQKrT8zFdGBBWf/DmHf1EQNGOOi+FWjteJEt9gIVNl3ZJH5Gxdg+ZuGA4W9Ld7BA8VW0jTSmY6gKXr5KlyJ9D5jXEVtNMlfsJIUTyz8S8pWQGswzG30JUEt+psrH6u6FdCe9XC/gmt9U1Ut5ui2W88kK81mw5ozc6L82pMYAViBqOzL0enDlhCw/fmgM+WKfSkgpmOjyYkliFGgq4833DXN0hH4MInzyzzFJzLdvDFuHYUMgazQi9FaujdrJ2PNfkVVvfM9g+5EfjMHVyeKFALuZVwN8a7qR2+C/4dA2zptlHaMw==
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=0TK6GMDRmSctQVMc+c3B6K+PxEcUUYCG1Tlal0xccuk=; b=Pgme5UgdlcmCSA24AGV0WxhsffoaA1RoQTrxa/qkGkn5tO8uOlGi5nllgjvRmNxcoDJujLoWx1Kgng6EkeZ9xUssuVuIH4mzhfq11h9GfGidjsA03wXtpX/l4XewYA4FKO8sYniFfFQjmvnGI0fZd/6uOMmKbIXFSi8rZeUuinximPJcLdCENVUVAW6GVSZXwqxHnawnz0Q3Gl++pgzHZMsnsXNZbmJEGWpeOu34ln2mz6lcbwD709LrlOmeUf1CDEeW8drilk3UFVMYMi4B27alOwyA3oG4w3F3Cu1678AA/8jJ78O+oGJOVJXOXNXAj1LqccTKwp159PXrZAJjUQ==
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=0TK6GMDRmSctQVMc+c3B6K+PxEcUUYCG1Tlal0xccuk=; b=egHJNQVJTqO26UZHMugiO/mcNDk33oI2vskzsMhbBed299al/G2ArtQW+RN2NOcFFFZQWgcEpDKeoBj1dAwjkZZPpOPmGmDKEqF9RxTj6tkXhMbQgk3LSBuTpk97bJE8YkPqJWP6UbTtGNuCqll7W6H2614EzPWEauvfMtPzb7w=
Received: from BY5PR11MB4337.namprd11.prod.outlook.com (2603:10b6:a03:1c1::14) by BYAPR11MB2856.namprd11.prod.outlook.com (2603:10b6:a02:bd::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3261.16; Wed, 5 Aug 2020 23:02:44 +0000
Received: from BY5PR11MB4337.namprd11.prod.outlook.com ([fe80::208e:de88:5049:c6e9]) by BY5PR11MB4337.namprd11.prod.outlook.com ([fe80::208e:de88:5049:c6e9%6]) with mapi id 15.20.3239.022; Wed, 5 Aug 2020 23:02:44 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Tony Li <tony1athome@gmail.com>
CC: "Acee Lindem (acee)" <acee@cisco.com>, Bruno Decraene <bruno.decraene@orange.com>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] draft-ietf-lsr-isis-area-proxy-02
Thread-Index: AdZqV1bpaX43pBLFSuS5ho/MIT6lUQAE/tVQAADz6SAAARjxgAAyekmAAAjF4kAAAOmGAAAFjJIw
Date: Wed, 05 Aug 2020 23:02:44 +0000
Message-ID: <BY5PR11MB4337E1A347464FAD04591D97C14B0@BY5PR11MB4337.namprd11.prod.outlook.com>
References: <32323_1596545126_5F295866_32323_118_1_53C29892C857584299CBF5D05346208A48F0BB30@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <BY5PR11MB43375CB413060250B336BE64C14A0@BY5PR11MB4337.namprd11.prod.outlook.com> <4558_1596554251_5F297C0B_4558_298_1_53C29892C857584299CBF5D05346208A48F0C59B@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <95A83DB0-A58C-4BD5-AF0B-8EF49D20EB3A@gmail.com> <89F6F8E5-E11D-4A6E-A783-8C9384FE3A1A@cisco.com> <BY5PR11MB4337DB5B017781522AAF9E66C14B0@BY5PR11MB4337.namprd11.prod.outlook.com> <824DFF9C-56E4-4E4F-A249-2E9413D85CC4@gmail.com>
In-Reply-To: <824DFF9C-56E4-4E4F-A249-2E9413D85CC4@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2602:306:36ca:6640:6426:c4f8:c68b:628e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 51c6d745-a8ee-4734-9580-08d83993a9b7
x-ms-traffictypediagnostic: BYAPR11MB2856:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <BYAPR11MB28566DFAE9B57DBD9C383D3EC14B0@BYAPR11MB2856.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: eqQ01xyisvaiNBD147lVCo2rAdMWlUh4D2Y7pNiKV4/hGJ6vow+wjsN5GrPHxbc19L5DmHp+76mHz+VvuD/Uz/1ly+vqwFWLYtv84nzd40x36z7qBDXmUfYOqTzguQHPmWsnL0LjQ6sTiKTemy8hcrefuI6g42pnofENq9LXkR/J6Cnr8udJDYa8a9rzrJH5NMTLNrB8/scfWMX4b4mhtLsqG4bSAXV9C5/z2/i0xAqObgWDTfKTr7BM5ePK4/+/h3YwbbwtGKl6+2AgQlGrfDIdmbywzXDL6lSd908L05HIyiFVLjKIgVzfFTOindSRaUduzbZ577XGD2INaX9OcA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY5PR11MB4337.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(39860400002)(366004)(136003)(376002)(346002)(396003)(8676002)(8936002)(33656002)(4326008)(66946007)(71200400001)(76116006)(6916009)(66446008)(64756008)(66556008)(66476007)(186003)(66574015)(7696005)(55016002)(53546011)(2906002)(5660300002)(86362001)(316002)(9686003)(54906003)(6506007)(478600001)(52536014); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: 6XRBsXxA3xofVYAYLVWpe8jwBxVn4SXXWYwZFigo8poCjQ9LCS2z2hqtVohxRFQ0V5VZvO0ulRdYKeBVbBfZpS2iQZ8yp2jcq/rEc39vMIbxUq8bPirGlxVz7bUrmefhOJnA5NcTmpKGoEvVCBkuFGRopPKBl6nYZInf7fe0WirF+FDQO2hoxdO5CO4fY1LUHZazlxpjuNLZcsM5Qez6E/zzSO2REH73QWWBgyNMfufe463UYB27ggWiTCWbTM/xkUroBt5rFfxLFy48EnoxkVr4qrgzQy9JNaWJY6rMJgFoXO/eEabEiHHotlYUk8c6uiZTmXqREwtEYvuleZEPKtOZ1mJyiJ3LfUTvTJetz5Wj/Kjq7AkMUqda/SX/BVQl7kQvHXVXxM2oA9XG/EOGi2Xpv2o6DNWKNEmhy7E2W+t/VfzKKFksKqg0PKAD+NLlROB2pt9L39MN9P5rdjnj0YHs5WUjC9T5AOubtVBKjS3i+M4XESEgNJiERTkvkGJW7DY3c5ujBmTQKaR3cW/dZQQH3aV/LVP9KQsUQGZ3YvWbiBGLSrrLVjNc/KhJLcZ2dl0rPOzuwxXXWNMfb1iUPGRV93uvErHuEggZgpqrKS3xLm2bR3NwsVx/EhaZuQIVZ7l76lHlfNM08b1xNIPCBgEa18H0NvqlpFGvbN08gNGCkxCfff3HsPtMBTyJOW4fSDqnYgotsf65sFdkvh2UJw==
Content-Type: multipart/alternative; boundary="_000_BY5PR11MB4337E1A347464FAD04591D97C14B0BY5PR11MB4337namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BY5PR11MB4337.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 51c6d745-a8ee-4734-9580-08d83993a9b7
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Aug 2020 23:02:44.2182 (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: XxM9uotycHk8aj1JbfGPKXFOlhMxlV8BaI0tEmL/3SGIOzDoRG7cujEnSg0OEHMMnglzJmYTZ8/ENUmastnsQg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2856
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/4VIdClbE_qufbN6ySuaXr5yDFVs>
Subject: Re: [Lsr] draft-ietf-lsr-isis-area-proxy-02
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2020 23:02:51 -0000

Tony -

From: Tony Li <tony1athome@gmail.com>
Sent: Wednesday, August 05, 2020 1:08 PM
To: Les Ginsberg (ginsberg) <ginsberg@cisco.com>
Cc: Acee Lindem (acee) <acee@cisco.com>; Bruno Decraene <bruno.decraene@orange.com>; lsr@ietf.org
Subject: Re: [Lsr] draft-ietf-lsr-isis-area-proxy-02


Les,



a)Advertise the “Area Prefix” in the Area Proxy TLV – much as we do a router-id today in the Router-ID TLV.


This would make the Area Prefix mandatory for Area Proxy, which is not desired.  We would prefer it to remain optional and thus part of the Area SID sub-TLV.

[Les2:] You can advertise the Area Prefix in an optional sub-TLV – just as you did with the Area SID. That is what I expected you would do.


b)The remaining info (reachability and SID) can then be provided using existing Prefix Reachability advertisements – no need for new sub-TLV for “Area SID”. This eliminates any potential issues if the SID advertised by “Area SID sub-TLV” were to differ from the SID advertised in Prefix Reachability for the same prefix.


As we discussed privately, we view this as a non-issue.  The Area Leader is the one advertising both the Area SID sub-TLV and the Proxy LSP. If there’s a coding error, there’s a coding error. There is a single source of truth (the Area Leader’s config) and we cannot protect against every possible coding error.  Reconciling the prefix with a separate advertisement has a non-trivial chance of being broken too, and IMHO, much larger.

[Les2:] You can define the advertisements in a way which reduces the possibility of ambiguity – which seems like a good thing to me.
And rest assured that you will be asked by someone to define the expected behavior when there is an inconsistency. 😊
Since prefix SID and Prefix reachability are directly related in forwarding, it makes far more sense to me to have those two together.
If you find correlating information in two different TLVs too challenging, you could opt for a new bit in the prefix attributes sub-TLV to identify a prefix as an “Area Prefix”. Then you would not need any additional info advertised in the Area Proxy TLV at all.


 There then remains the question as to whether the “Area Prefix” is anycast or unicast i.e., is it common to all IERs or is it unique to whomever gets elected Area Leader?


Does it matter? We have no clear semantics for this prefix. A difference that makes no difference is no difference.

[Les:] This question needs to be directed at those who prefer the Area Prefix approach. It matters as it impacts configuration and advertisement semantics. An anycast prefix is NOT a Node Prefix.
And it impacts how traffic is forwarded into the area.

   Les

Tony