Re: [Lsr] New Version Notification for draft-wang-lsr-prefix-unreachable-annoucement-03.txt

"Acee Lindem (acee)" <acee@cisco.com> Tue, 28 July 2020 13:24 UTC

Return-Path: <acee@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 140293A0BA8 for <lsr@ietfa.amsl.com>; Tue, 28 Jul 2020 06:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.62
X-Spam-Level:
X-Spam-Status: No, score=-9.62 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=gmad4YAL; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=vSn7TKb/
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 fwyOwF05Sdpq for <lsr@ietfa.amsl.com>; Tue, 28 Jul 2020 06:23:59 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47DA53A0C15 for <lsr@ietf.org>; Tue, 28 Jul 2020 06:23:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6630; q=dns/txt; s=iport; t=1595942639; x=1597152239; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=XiL1Q6gn4kZjgqUm5Ay30pLVGMDkmKM+jQwzZoT0SOY=; b=gmad4YALzxkPyfslY+dQPmAbMyDwu/6K0KIWStSQPXuYyo0skZapSFUq PKcjLQZbk7vMqjHrIbE9hDmmfQ3LKqyHgU4C4AT7Y6b+9sck7K5XKTEpb J4Tr2WU5EpDvokxJNdaLEzBtXUhUogoaPzces/XVdkmiLNdl52qTkTaLL k=;
IronPort-PHdr: 9a23:VhfSwBX2+Z0A/1ArXPoFHvOFDd3V8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSBNyFufJZgvXbsubrXmlTqZqCsXVXdptKWldFjMgNhAUvDYaDDlGzN//laSE2XaEgHF9o9n22Kw5ZTcD5YVCBomC78jMTXB74MFk9KuH8AIWHicOx2qi78IHSZAMdgj27bPtyIRy6oB+XuNMRhN5pK706zV3CpX4bdg==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CfBQCjJSBf/4UNJK1gHAEBAQEBAQcBARIBAQQEAQFAgUqBUlEHb1gvLAqEKoNGA41WmGGCUwNVCwEBAQwBARgNCAIEAQGETAIXggkCJDgTAgMBAQsBAQUBAQECAQYEbYVcDIVxAQEBBAEBEBERDAEBKQMJAgELBAIBCBEEAQEDAiMDAgICJQsUAQgIAgQBDQUbB4MEAYJLAy4BDqNVAoE5iGF2gTKDAQEBBYE3Ag5BgxIYgg4JgQ4qgm2DWYIzhAQaggCBEAEnHIFPfj6CXAEBAgEBFYEeToJwM4ItjysEJYMShwCbDIEFCoJfiFiON4JhAx6Ce4EiiCeTJYEpjCyEQooulGwCBAIEBQIOAQEFgWojgVdwFRohKgGCPglHFwINjh43gzqFFIVCdAI1AgYBBwEBAwl8jTeBNAGBEAEB
X-IronPort-AV: E=Sophos;i="5.75,406,1589241600"; d="scan'208";a="530659179"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 Jul 2020 13:23:58 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id 06SDNwhG019895 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 28 Jul 2020 13:23:58 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 28 Jul 2020 08:23:58 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 28 Jul 2020 09:23:57 -0400
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 28 Jul 2020 09:23:56 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=BcUdD5+iAOksrIGktn8XhvJTDe4Tre1lHy+NfbEuT6YocGAb3YP/kU7ooap/jCQAkifNHYrc4pB4WprMwPGvuvEMeBzI68P4SH4KJ+BBl2O855Ryh2agAUOTmSaWbMkh+Zkd8/mQIT4fH/HVppzz7bIC8fiQjK8uAKd9+wKwRCFBaGfMa4HEUX4NGO+Hmwdq10PBZYRgeahRf7pWlFa7bgIwgGZ7vquAVGo44cUZz1cnL6GdQXQvRGE9pCbXLaGwzpxtLprzIRdAmdGXVWqyQS41MUi8UFK5YsAzoIF36d0l9XO/1s0iclUQaFq0wR9R0ZfLwCycuiGLpiOBxliHKg==
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=XiL1Q6gn4kZjgqUm5Ay30pLVGMDkmKM+jQwzZoT0SOY=; b=HRpb8PNHjv6xdq2MY0pXfFKXkmkvLtwR3TyXltxJnaWcsGD7a3AGlh4RASVQ/gPaPYYr2+ZqI3ALjUsrcYPP63+4x21H4Y+vlhevWQ2ATp3nOFvEwytSlRAzTYCqQgQmWzBpmBPyR40yKm438tr4QWF53MBQut3bsD1vavx0lFwPVzy/qfrRgHdY8+UpKr6xzhrm8+uvvZdhPIlYHYuLKWg65AoCKIRHsLJ+7XHO2RsUpv4Qq90VMyEj5oFxRnFc5wIrDUNOCDQi/FmlG8s3+iFLY7/z1Ieyp3FBek1Z7HOHx/i85+3woApIf6OZvRlmrWtOdh7mJT5nLyXTlmEMag==
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=XiL1Q6gn4kZjgqUm5Ay30pLVGMDkmKM+jQwzZoT0SOY=; b=vSn7TKb/t9h+sDBP1opqIwfIo8qFGH8aJD8IqhJ+zu6D0C6VbKgJmOp/EbGoRpGjEoNx6v3AujaC6wIq5m9hDQmnHjBvcbVu0EipZuXXS0hK/oc8j2dQexzstq9hW8HFHFU+f9V4K23bma06EYgL2WUEGlSAmvSFwomVjlGMgK0=
Received: from BYAPR11MB2887.namprd11.prod.outlook.com (2603:10b6:a03:89::27) by BY5PR11MB3957.namprd11.prod.outlook.com (2603:10b6:a03:183::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.22; Tue, 28 Jul 2020 13:23:56 +0000
Received: from BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::70a6:bb5b:16b:4f9b]) by BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::70a6:bb5b:16b:4f9b%7]) with mapi id 15.20.3216.033; Tue, 28 Jul 2020 13:23:56 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Huzhibo <huzhibo@huawei.com>, Aijun Wang <wangaj3@chinatelecom.cn>, "lsr@ietf.org" <lsr@ietf.org>
CC: Xiaoyaqun <xiaoyaqun@huawei.com>
Thread-Topic: [Lsr] New Version Notification for draft-wang-lsr-prefix-unreachable-annoucement-03.txt
Thread-Index: AQIFxVYWa52TS3+lleUCjv1WJLVErai73FhQgADS6ICAAMyIAIAAeysA
Date: Tue, 28 Jul 2020 13:23:55 +0000
Message-ID: <827F1C55-2A0E-47E9-87EF-BFBDE556F13F@cisco.com>
References: <159581253012.15882.18408845608624077923@ietfa.amsl.com> <014a01d663b5$d8228660$88679320$@chinatelecom.cn> <DE46CF44-A583-4754-8CAC-E2B2EFEF3E51@cisco.com> <06CF729DA0D6854E8C1E5121AC3330DFAF70E4FC@dggemm509-mbx.china.huawei.com>
In-Reply-To: <06CF729DA0D6854E8C1E5121AC3330DFAF70E4FC@dggemm509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.39.20071300
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [136.56.133.70]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 47fc9fad-74e4-4490-a37d-08d832f97ac5
x-ms-traffictypediagnostic: BY5PR11MB3957:
x-microsoft-antispam-prvs: <BY5PR11MB39573300025EE939C211E38AC2730@BY5PR11MB3957.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: 5ovQo8DgPdqAJKPevucRwizqrEeiv4J9IsOX26ASzUE8L1Rrg5SvLxtNRQx0th2flDQBpreqLoUyWC+Samh9o0JiRmio1YABMLH6SaWj7TastiGpugKuVPaekyI8RGAt1spE5VQKaAGZj5qRmhpCAh6SDUbS5g/skUAI/Yx4Ut7Ix3KBMsNAg0vp+gGj3FXaOiaiqOsC55qzHRNHZAmNdHEOaogsnaqazuxbLqauDqSl3asoXU1Czvnt/qivXhOzKYpJO0+TApT1BnO1le0p7/IrAOT4d9hR01hOfp2N/sv0Euf91oQJJfnk2m45WeluRrSGcKIv1Ehnk3oAw8oEA8TO4jzlevyqV6QPeh7/99ik5a9lOjbuCDtbXv66tiDzFcQu17UT/OMCV1JQu/GhxA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR11MB2887.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(376002)(136003)(346002)(39860400002)(396003)(366004)(5660300002)(86362001)(66476007)(66556008)(71200400001)(8676002)(15650500001)(76116006)(186003)(26005)(8936002)(66946007)(66446008)(4326008)(91956017)(36756003)(64756008)(66574015)(6506007)(53546011)(316002)(2906002)(83380400001)(478600001)(966005)(6486002)(33656002)(6512007)(2616005)(110136005); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: 9QgB3CAnJVki6VR40ikLafdrg6113PkWEOYhq7wV3hKsEpxFe0ldMrkXuQCRjCvAItkT825oi2XwPXbfaRK3Bp9Rcpti+hd2ANJMd3wlp25028ljdkpSqj4nD8eKWHJZmnwHijsv9HsMEskDh5OR0V0nmLdH/qQnASDtbjnBVogb2XMU9Mv3pwyNYZrSDNXWHl+QhKZjFayPzS3rcdY30il+MGxz6+EpCodWSl92026hIDG0lkdc5/iXHB3UuTDOKLl68l0rROmTeGgoizOsKh2Cma5RpvKJunMK92mSANO+m+JrFaV4ZHuIKBVPpYcmCBQPgqoyB/X4WIWY0adSQSRC54cKZYuOc5/h7S5VnVrvFt5y9tyYEEwlzBVfq4YaLczbgwPmCYb/S4og6k4fSFGaTNqSYU422rbE7/9eCYhE0HGX64dA/BFka+M3X63YGLozoZLaFym48yDIfD9GHzmf8L2ILvQMnPJ63H06pxCGzln/e3PRqv33rNvh/1sM
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <1BDE8ED85D73344581E7C5564252A067@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR11MB2887.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 47fc9fad-74e4-4490-a37d-08d832f97ac5
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jul 2020 13:23:55.8734 (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: UJV1dFQ6iruG6O+lZ4408/t8ZBcqEJ9lSYvbrnm6NqFVnL8zNWtl2WZJJOmlzCsd
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB3957
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/a0dbKkvbxfGigglmZv4DQjtlPME>
Subject: Re: [Lsr] New Version Notification for draft-wang-lsr-prefix-unreachable-annoucement-03.txt
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: Tue, 28 Jul 2020 13:24:05 -0000

See my response to Aijun... Please provide topologies where the section 6.1 solution doesn't work. 
Acee

On 7/27/20, 10:03 PM, "Huzhibo" <huzhibo@huawei.com> wrote:

    Hi Acee:

    In fact, we have meet some scenarios where redundant paths cannot be deployed within a area. Especially when the access area uses the nearby access principle, ABRs form disordered combinations, which makes it difficult to deploy physical or tunnel connections. In addition, advertising unreachable prefixes can prevent traffic detours. Of course, This draft also has some other attempts to use Segment Routing to automatically establish connections between ABRs.

    Thanks

    Zhibo Hu

    -----Original Message-----
    From: Acee Lindem (acee) [mailto:acee@cisco.com] 
    Sent: Tuesday, July 28, 2020 1:51 AM
    To: Aijun Wang <wangaj3@chinatelecom.cn>; lsr@ietf.org
    Cc: Huzhibo <huzhibo@huawei.com>; Xiaoyaqun <xiaoyaqun@huawei.com>
    Subject: Re: [Lsr] New Version Notification for draft-wang-lsr-prefix-unreachable-annoucement-03.txt

    Speaking as an LSR Working Group member:

    Asking the WG precisely how to advertise prefix unreachability is the wrong question - it is analogous to asking whether to use a car or truck to drive off the edge of a cliff. Rather than messing up OSPF and IS-IS with these complex and unnecessary mechanisms, it would be better to address the requirement in your network design. Note that the unreachability of a given summarized prefix is only relevant if it is reachable through another ABR. In this case, the network design should provide adequate intra-area redundancy to provide communications between the ABRs. If this cannot be accomplished, an intra-area adjacency should be established over a tunnel between the ABRs in the backbone. Contrary to section 6.1, Looping is normally not a problem as ABRs should add back hole routes for their advertised summaries. 

    Acee

    On 7/26/20, 9:34 PM, "Lsr on behalf of Aijun Wang" <lsr-bounces@ietf.org on behalf of wangaj3@chinatelecom.cn> wrote:

        Hi, LSR experts:

        We have uploaded the new version of this PUA(Prefix Unreachable Announcement) draft. The main updates are the followings:
        1) Describes the solution that using tunnel to redirect traffic among ABRs, when all ABRs reaches the PUA limit.
        2) Describe fast rerouting to avoid routing black hole.
        3) Defining PUA capabilities announcements for OSPFv2/OSPFv3 and ISIS.

        There are also some arguments about the current solution for PUA, for example:
        1) Is it suitable to set the "Prefix Originator" sub-TLV to NULL to indicate the prefix is unreachable?
        2) if not, what's the consideration? What's the other convincible solution?

        Wish to hear comments and suggestions on the above issues. We will also have the presentation on the coming IETF LSR meeting.

        Best Regards

        Aijun Wang
        China Telecom 

        -----Original Message-----
        From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
        Sent: Monday, July 27, 2020 9:16 AM
        To: Zhibo Hu <huzhibo@huawei.com>; Aijun Wang <wangaj3@chinatelecom.cn>; Yaqun Xiao <xiaoyaqun@huawei.com>
        Subject: New Version Notification for draft-wang-lsr-prefix-unreachable-annoucement-03.txt


        A new version of I-D, draft-wang-lsr-prefix-unreachable-annoucement-03.txt
        has been successfully submitted by Aijun Wang and posted to the IETF repository.

        Name:		draft-wang-lsr-prefix-unreachable-annoucement
        Revision:	03
        Title:		Prefix Unreachable Announcement
        Document date:	2020-07-27
        Group:		Individual Submission
        Pages:		11
        URL:            https://www.ietf.org/internet-drafts/draft-wang-lsr-prefix-unreachable-annoucement-03.txt
        Status:         https://datatracker.ietf.org/doc/draft-wang-lsr-prefix-unreachable-annoucement/
        Htmlized:       https://tools.ietf.org/html/draft-wang-lsr-prefix-unreachable-annoucement-03
        Htmlized:       https://datatracker.ietf.org/doc/html/draft-wang-lsr-prefix-unreachable-annoucement
        Diff:           https://www.ietf.org/rfcdiff?url2=draft-wang-lsr-prefix-unreachable-annoucement-03

        Abstract:
           This document describes the mechanism that can be used to announce
           the unreachable prefixes for service fast convergence.




        Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

        The IETF Secretariat



        _______________________________________________
        Lsr mailing list
        Lsr@ietf.org
        https://www.ietf.org/mailman/listinfo/lsr