[Lsr] Questions on Prefix Unreachable Announcement
Huaimo Chen <huaimo.chen@futurewei.com> Fri, 20 December 2019 14:50 UTC
Return-Path: <huaimo.chen@futurewei.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 6811C120074 for <lsr@ietfa.amsl.com>; Fri, 20 Dec 2019 06:50:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 E4mqQNrknn3t for <lsr@ietfa.amsl.com>; Fri, 20 Dec 2019 06:50:13 -0800 (PST)
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (mail-dm6nam10on2094.outbound.protection.outlook.com [40.107.93.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08D9612006E for <lsr@ietf.org>; Fri, 20 Dec 2019 06:50:13 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RAzGBL455tYiHgzrfsW2glR+iOn4te5sCfMmceylN1EKjcZRWNqNfaKug+mfKHZK1KwpUhW/sX5i0BBrGEAdievf0G8OqasllDP/I6L2yXB5CUPou3s9Hmm3L7RLSkITh6+W3ZRaApNQstqTtvh/pRNX/wOLANdlNpcgAA/iQ5kFaaNp/KYA+S8GlQeu0zvy8ELuwc5uDcEaJmgwAuLwNrqsIc2G2IZ/Y3ud/vam6fhiM7jRRk9sgKZRh+q/rQnaujrISq6YWU66FubJIbWId0DXch+5b+9pGPvrKTAQRk5QejEMt4UB/vMNK6P4SYCkPi0Px484b1AwWbiDD3lSmQ==
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=RaHsHWLS/kFgMNVuc5pZGawoVl5aQe876HgHNzQDB+c=; b=RDopeifKBooV+rxi7hzYx1d3Y9WqFATZApZZbp9PR966zN9SbnyT6SWeT30fltf3wKcTn+6u07Lg+z4Qmen2elnspkGEr+aEl3OkJV/EonXxiRHnTU5uPizFJpI0Z4itxk1HtgP9y22NzJB32SBAbc16HwF6kqy2RNlDDbSTZuDnN82pt+NbARjMXW00vTpq9W8276i7FzJ8hCTx5CEXhSLxJtx/+5LiiKswGHovY0jNEAQnoEH1J5ofwQJ5j2xmR8PnpMSde398RJlZY9xtZECVwbEQJOeS9cNOWMt3GIEZVVC7N2A243zcXu3YvYimNDSJvZpK/qKyv1m2wxJmvQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RaHsHWLS/kFgMNVuc5pZGawoVl5aQe876HgHNzQDB+c=; b=AkI8EqPTiInSfLDIE71fSrK/N7AbXSagO/AZQ2cGAhE3z1yqHTX3vmmkhp828L1OsdBdMSJM0XnCpEWdRqvaZoro2jHbILlTm95/H239WVyOHvPfPWpz5Fd5MtKkI1BuhcOoG0t2NCTLNGk/zW96ES8SY//mCjYfIUeww/6R+28=
Received: from SN6PR13MB2271.namprd13.prod.outlook.com (52.135.93.160) by SN6PR13MB2304.namprd13.prod.outlook.com (52.135.90.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.10; Fri, 20 Dec 2019 14:50:10 +0000
Received: from SN6PR13MB2271.namprd13.prod.outlook.com ([fe80::70b0:78f1:a9bf:4b64]) by SN6PR13MB2271.namprd13.prod.outlook.com ([fe80::70b0:78f1:a9bf:4b64%7]) with mapi id 15.20.2559.012; Fri, 20 Dec 2019 14:50:10 +0000
From: Huaimo Chen <huaimo.chen@futurewei.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: Questions on Prefix Unreachable Announcement
Thread-Index: AQHVtqFhLWhLRe9QyUWU/cOhgzYB7qfDGwTH
Date: Fri, 20 Dec 2019 14:50:09 +0000
Message-ID: <SN6PR13MB227139E1A9EDCDE266A89848F22D0@SN6PR13MB2271.namprd13.prod.outlook.com>
References: <SN6PR13MB22719959075908AEF48AB991F2520@SN6PR13MB2271.namprd13.prod.outlook.com>
In-Reply-To: <SN6PR13MB22719959075908AEF48AB991F2520@SN6PR13MB2271.namprd13.prod.outlook.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=huaimo.chen@futurewei.com;
x-originating-ip: [2601:199:4300:8e5a:302f:6aab:d62a:13bb]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3de9730e-3bc9-4f0c-2ff4-08d7855be96e
x-ms-traffictypediagnostic: SN6PR13MB2304:
x-microsoft-antispam-prvs: <SN6PR13MB2304AEB2136C54827712CD35F22D0@SN6PR13MB2304.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 025796F161
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39850400004)(346002)(136003)(376002)(396003)(366004)(199004)(189003)(33656002)(19627405001)(8936002)(9686003)(86362001)(8676002)(66574012)(81156014)(81166006)(5660300002)(2906002)(52536014)(44832011)(55016002)(110136005)(186003)(316002)(76116006)(478600001)(7696005)(66556008)(71200400001)(66946007)(64756008)(966005)(6506007)(66446008)(66476007); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR13MB2304; H:SN6PR13MB2271.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: MWZ4fIV7pdOATTYHVlUlVYG0UkKr5tVdYIRzP+OFZxX+0VSarZZWT+mL32CyeptfZjHz+z0Kbja6qf7OXOjdOCYQlDmZpcfXv0aL1aWQKMLs6CYfm6BrO2YDtQzHsvnnkvlvqKUK0Od/mGxAW1SW32Udc0iQJOugPFHTtL6UlvHRWZER/uKyxotoLhDOztkt+MIdoL4J1lg6jx6lwGp/C4HQwD5ic9TGerMqhpDZo+3Y9+kkzP8XPS6Owyl6G69fUDvg/w7XzDL61cnQS0iUn++vSezBAyGhHafXx4CAAx9B+lmccPbrM+SVBQpQepgBCZl3J5Rflm+nnWId8kqFDpOyap1XKrnBfCZdVS3jyDJuKfZ510ahv36psFf0Ns+FKPufQa7y8trfW3LpzQX+DVEfqlSBts084DsCYA5qasB8ILbWxKEB/l7XIZvF8h3hOD9V2jApphqPOArYKD6TtZ5bGmqjEgldTPRd/vDHJII=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_SN6PR13MB227139E1A9EDCDE266A89848F22D0SN6PR13MB2271namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3de9730e-3bc9-4f0c-2ff4-08d7855be96e
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Dec 2019 14:50:09.9626 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 3pEcaxQRKjc2zEU0vyBXvZEi9vRVj50CePmWB470ZpmwMVCYcHToqJNOU7amzPrMMjI9Dm7H7EDDkl9B1cQxiA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR13MB2304
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/IveNu2uC5LtypcfAoh1u204XF-E>
Subject: [Lsr] Questions on Prefix Unreachable Announcement
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: Fri, 20 Dec 2019 14:50:15 -0000
Hi Aijun,
My understanding of your draft https://datatracker.ietf.org/doc/draft-wang-lsr-prefix-unreachable-annoucement/ as follows:
After the ABR originates the Extended Prefix Opaque LSA, which contains a prefix and its originator (i.e., the router originating the prefix), it will announce that the prefix is unreachable when it can not reach the prefix (i.e., the prefix becomes unreachable from reachable from the ABR's perspective).
Is my understanding right?
Should the ABR remove the prefix from the Extended Prefix Opaque LSA after it announces the prefix unreachable for a give period of time? After a router in another area receives the unreachable announcement of the prefix, it installs a black hole route to the prefix, and then removes the black hole route after a configurable time. After the black hole route derived from the unreachable announcement of the prefix is removed, it seems better to remove the unreachable prefix from the LSA.
Can the ABR just remove the prefix (i.e., the TLV for the prefix) from the Extended Prefix Opaque LSA when it can not reach the prefix?
Best Regards,
Huaimo