IETF Logo Mail Archive

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

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 05 August 2020 19:54 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 5D5163A0EE9 for <lsr@ietfa.amsl.com>; Wed, 5 Aug 2020 12:54:19 -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_H3=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=OxJ8NxIf; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=jCCH0yZP
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 Ix-LFbbCSbJT for <lsr@ietfa.amsl.com>; Wed, 5 Aug 2020 12:54:17 -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 5E7303A0EE6 for <lsr@ietf.org>; Wed, 5 Aug 2020 12:54:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13996; q=dns/txt; s=iport; t=1596657257; x=1597866857; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=rTZHNqXj1FtjmhhoiOquppHPkgVpWEKrS7R4TF+wE5w=; b=OxJ8NxIfJxqA2yZksb2KIWEqaGg3Q7JJP0hnypuI2jIpXPN9FnSUOIgv JZkQbNzPqQSinvkYWTGCDt6VdoFNcDq5GQ2r/+geYync5Za3ZH6lQS7BX E2w8CZGu697qFpEjQHTGorcFJO4agpd5wY0qWuVtbaPSZ9xaY7g8s41CP E=;
IronPort-PHdr: 9a23:EY1ZcRE7xWow6VtDY7WfdZ1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e401QObVoTA4PUCgO3T4OjsWm0FtJCGtn1KMJlBTAQMhshemQs8SNWEBkv2IL+PDWQ6Ec1OWUUj8yS9Nk5YS83/fFbV5Ha16G1aFhD2LwEgIOPzF8bbhNi20Obn/ZrVbk1IiTOxbKk0Ig+xqFDat9Idhs1pLaNixw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BwAAD1DStf/49dJa1gGwEBAQEBAQEBBQEBARIBAQEDAwEBAYF5AwEBAQsBgSIvUQdvWC8shDWDRgONUooEiXKEbIJTA1ULAQEBDAEBLQIEAQGETAIXghECJDcGDgIDAQELAQEFAQEBAgEGBG2FXAyFcQEBAQQSEQoTAQE3AQ8CAQgRAwEBASgDAgICHxEUCQgBAQQBDQUIGoMFgX5NAy4BqSQCgTmIYXaBMoMBAQEFhTANC4IOCYE4AYJvg1+BAYE5hAUagUE/gVSCTT6CGoIlFQkWgmEzgi2QEIJqhl+bdE8KgmKVEoUan36SKY0ZkhECBAIEBQIOAQEFgWkkgVdwFYMkUBcCDY4fDBeDTopWdDcCBgEHAQEDCXyPKgEB
X-IronPort-AV: E=Sophos;i="5.75,438,1589241600"; d="scan'208,217";a="790212567"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Aug 2020 19:54:15 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id 075JsF6g020970 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 5 Aug 2020 19:54:15 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 5 Aug 2020 14:54:15 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 5 Aug 2020 14:54:14 -0500
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 5 Aug 2020 14:54:14 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cDMXzgs50kp64ELtTPVE5JnXiKQyuZexrDQOkt+yj+1+ctmldrWoLPn5l9uFiU8mU2/4kutYp8tPsxBWjlHKAWWji3dGLDfx5Q8n8mp0ZaaovWzqzpZC7eAf3M097FHduacT/w7kF1jT2n7bqE8ngAY10GWZAbtFjIdFmQIjUbgC8tHEJ/I3ONvnAFmUhGFnYokwQalH2sR4nYktEhh7k4Ku+YC/1KP56IpFO5Mb/DOz/8+5mgQjQyS7h1GLtWE5LIhrc0Dgt+VjsRJPlaIDJohUZJGn2VWa7zPVPSSpXMkPODivN10myOPcadtvkYYJyve/MHRy1HrQXVQkD0TOgg==
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=rTZHNqXj1FtjmhhoiOquppHPkgVpWEKrS7R4TF+wE5w=; b=eRV+4O+cHPbIyU8bNgW8pkgE6RlfDn/kQMwVxVGBbW9K6xmFwLw6pPeDr6y7TRQSNZ0JvNn/hanDIUGONi0UKX3xPugBjAxIfIPyMMxvo0BB/fWycxA3wn8DCW2881l1VW3dHa1x81d887p1L0q65YvhW61Vj17ShFNp4dbQ0c3++CCUivrBOmen7RBUj2Dl54w2sDTXjJnAv8ZdvlH/eyJA5shLdDCn7J3ppGoZRoygLXeeGUDEPJhhtdTAaw8RXhhncLGe5LUYfkbT2VzEfPpF4AQm+DPDMdpWN+NC2bllZd9VANwO42AoQIaOQhblU+MvaiXAEZMXjG3LNCYPCw==
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=rTZHNqXj1FtjmhhoiOquppHPkgVpWEKrS7R4TF+wE5w=; b=jCCH0yZPyookwQldZd6rPfxDgCwtUl4YfNbqllWxi2xx3f8Y9h3I0dckcXgJ8FKhbmmdr3WYYk+bzTgs33M8VILydSrjPhBw+U8uhwq2f3h+NiFArBTATxVg06b3BsoVTI5Oy2AFvMS8ReQ/7ZYEVtKEPTbqK5BeAYbBK2GY5yY=
Received: from BY5PR11MB4337.namprd11.prod.outlook.com (2603:10b6:a03:1c1::14) by BYAPR11MB3702.namprd11.prod.outlook.com (2603:10b6:a03:f7::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.19; Wed, 5 Aug 2020 19:54:13 +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 19:54:13 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, Tony Li <tony1athome@gmail.com>, Bruno Decraene <bruno.decraene@orange.com>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] draft-ietf-lsr-isis-area-proxy-02
Thread-Index: AdZqV1bpaX43pBLFSuS5ho/MIT6lUQAE/tVQAADz6SAAARjxgAAyekmAAAjF4kA=
Date: Wed, 05 Aug 2020 19:54:12 +0000
Message-ID: <BY5PR11MB4337DB5B017781522AAF9E66C14B0@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>
In-Reply-To: <89F6F8E5-E11D-4A6E-A783-8C9384FE3A1A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.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: bb1af3c1-e37f-40a5-4c28-08d8397953bb
x-ms-traffictypediagnostic: BYAPR11MB3702:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <BYAPR11MB3702F7FC1EF0CBF5D44CA705C14B0@BYAPR11MB3702.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: PNlrffdu9H/gsWoSXGbYx8rdue6IrOwMhJ7yoQ0tYzSrdWn6L1JN735xN7go35CbBccrY15EAlifFuB0A3hzFHNCWOg8VB1Wc1VPyjrdEqdprg7Icm1yUolGCbSr62hBK4P38SqkMgdsylp3IYGY1fMvMpOf2FUbo5F6I37BlbYmGEg+31xIu8VepKTdMWnp/IehDas6yLofxdnIds2avIWZi4zDiPd5ECrk7J9OrvoLOAUJHvAG0y5GvyoFbSs1u3tnHuHFDZis/iwE//u3+wbwpol334MKRs+UozH6cvkrWbmoVAr1BZHe4Si7ApgxmBMkQLEtx/OoiZc9J70hzQ==
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)(376002)(39860400002)(346002)(136003)(366004)(396003)(64756008)(66446008)(66946007)(66556008)(76116006)(86362001)(2906002)(71200400001)(478600001)(110136005)(66476007)(33656002)(9686003)(8936002)(4326008)(52536014)(66574015)(7696005)(5660300002)(186003)(316002)(55016002)(8676002)(83380400001)(53546011)(6506007); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: yVaXocC+rQSpINqCSzxsmvPbra4DIPh/L6PWdY71I0LgFf25bmMdfO+KTL6JdKbxiWWEQs/c8CGy/w8D30oJ2AOjzX6rn+gjocPhhRk6uU8mOh+70MJnZR34nYAm2rx0OLcPqw7bqtvMfQMVmnx6PzSDTet2wWv9uzLhENo0A5sv1Agzojh1iWQDfbB96/bodfTVrM53HHn596d7CkZ3ltGelC+o5FI/2LhbM2onyDB5Pa38fOdFKwfbBKm1l750GuyWugeRYrQ2hlzCIgcPH0LlHNeBjOVrhI9JbAxVywSwg1JVGCx6BYjH5tHd4bdPyo9SFJVld5bqI1IDh0XPL0BjRe+Z5fcrpiXvnmSP+ltpsazMGiCnz2jEb11sePIhNxMDrDPZkm57hFsIxXQ5i9eU0bvWGt5oFAVqx2HIWw84D8bI3hNbJvZ4hGhUmQX7Vm6+B48MiLhRLJHEj0RYVISBIDckfD6BqCABynIyT2gMNfwNNgJ38CUEi3yA7fYtFTAeSOLrwW2/DrUwfBLsTh5eyHy4wVsZu7s7y9HqkZXYxLg4ZWf/AyeLk4N+Nz378BKu3M27Zf4kiQHP8W6fBhUA300U+Uvb3IFQl4gZwFiXyJxZYFtFCD/JzzB3+DW2R8A4aWIxaB09toNMgyy+IuFPT2dGB877roKpiM2RkWiWzAETzVxcNvjJsc1rbZ9CpKTnXJZJ2+Mi7bNiYX5YyQ==
Content-Type: multipart/alternative; boundary="_000_BY5PR11MB4337DB5B017781522AAF9E66C14B0BY5PR11MB4337namp_"
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: bb1af3c1-e37f-40a5-4c28-08d8397953bb
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Aug 2020 19:54:13.0275 (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: l65z3p3Dboq0iGyb7N4zdbUb+UjtbwWmLc9Pr0kfNy8O7RkUyC0Gk5G/KzQOt+t8vAAP8P0kfrC6nZ76evjf5A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3702
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/aDMSaoblV-l2eKa7XoXWI9A2FVI>
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 19:54:19 -0000

Acee -

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

Hi Tony, Bruno, Les,

From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> on behalf of Tony Li <tony1athome@gmail.com<mailto:tony1athome@gmail.com>>
Date: Tuesday, August 4, 2020 at 11:26 AM
To: Bruno Decraene <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Cc: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.com>>, "lsr@ietf.org<mailto:lsr@ietf.org>" <lsr@ietf.org<mailto:lsr@ietf.org>>
Subject: Re: [Lsr] draft-ietf-lsr-isis-area-proxy-02


Hi Bruno,



[Bruno] Agreed so far.
Do we agree that draft-ietf-lsr-isis-area-proxy uses the SID/Label sub-TLV? We both agree that this sub-TLV has no mention of the global flag nor the routing algoto be used.


So far, we do NOT have agreement on that.  Your argument yesterday (backed by Robert) is pretty compelling: go ahead and assign a prefix and now the Area SID may be advertised as a Node SID in the Proxy LSP. If we take that direction, this discussion is moot.

Why wouldn’t we take this approach? Since the border routers are abstracting the area as a node, why wouldn’t we do the same for the Node-SID?

[Les:] The original idea proposed by the draft authors was to have a SID which could be used to forward traffic to the inside area. Conceptually this does not require a prefix – and the encodings currently defined in the draft reflect this.

Bruno has since commented that he prefers a prefix to be associated with the Area SID.
I agree this is a viable approach, but if we go that way then I think what is needed is:

a)Advertise the “Area Prefix” in the Area Proxy TLV – much as we do a router-id today in the Router-ID TLV.
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.

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?

   Les

Thanks,
Acee

Tony

v2.23.0 | Report a Bug | By Email