Re: [Lsr] Flooding Path Direction

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Thu, 04 April 2019 05:52 UTC

Return-Path: <jheitz@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 2A12B1202DD for <lsr@ietfa.amsl.com>; Wed, 3 Apr 2019 22:52:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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_HI=-5, 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=hchIdF9v; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=WOKUtmU3
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 xErMhqUUTPx2 for <lsr@ietfa.amsl.com>; Wed, 3 Apr 2019 22:52:25 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97DB51201D1 for <lsr@ietf.org>; Wed, 3 Apr 2019 22:52:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7011; q=dns/txt; s=iport; t=1554357145; x=1555566745; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=s3AkpaBko8IzGfwfdmaE30z7hj9z/cyH5XkljkANUE0=; b=hchIdF9v/8djY0vMBzkHrmObATXyQxZOgcsld7yc3f7PpjZkUMC8Z3WX MJ0InhhPs60EvXPKSIoN4kMDk3CAtgSQOrH583ds/VBl1uF+VgtQX5AMq CAfFSTOITp7LajDFGehW6YsZpBCmVPQVQ3lEA4fsiuWNFjDo20gMZF2mv c=;
IronPort-PHdr: 9a23:NtmeuB1FxmdYTliBsmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxGOt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQC032LeL4Ryc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ASAABImqVc/4gNJK1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ4vUANoVCAECycKh0sDhFKKUoJXiTiJE4RKgS6BJANUDgEBLIRAAoVEIjQJDQEBAwEBCQEDAm0cAQuFSgEBAQEDLRMBATcBDwIBCBEEAQEvIREdCAEBBA4FCIMbgRFMAxUBAqB+AooUgiCCeQEBBYUSDQuCDAiBMAGLMheBQD+BV4JMPoIagiyDOYImkTaHWowlNgkCkDSDXpROi06HX4wRAgQCBAUCDgEBBYFPOIFWcBWDJ4IKg2+DRocNcoEojiMBgR4BAQ
X-IronPort-AV: E=Sophos;i="5.60,306,1549929600"; d="scan'208,217";a="324841317"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Apr 2019 05:52:24 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x345qOQr018297 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Apr 2019 05:52:24 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 4 Apr 2019 00:52:23 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 4 Apr 2019 00:52:22 -0500
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 4 Apr 2019 00:52:22 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DnUd8EryErXL6rFG6fJeyCKiF6gMfnN7k3Y9piMm0JQ=; b=WOKUtmU3lY23bHinSkgvA7JhJ+M5CxOoGxjqioXVSAF7hfha69hF+ClcqGkJ5B0QoSWSka7cPgyTlc++UhNMC6e3caTYy73lhbT76iWpbqatigTLdXoIL7xkF5GEP/Kjjtf3id9fOajbC2HggNb8J0UAFADh1KQsepZ97/XBbzY=
Received: from BYAPR11MB3751.namprd11.prod.outlook.com (20.178.238.144) by BYAPR11MB3077.namprd11.prod.outlook.com (20.177.226.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.17; Thu, 4 Apr 2019 05:52:21 +0000
Received: from BYAPR11MB3751.namprd11.prod.outlook.com ([fe80::a417:158f:9c54:b98a]) by BYAPR11MB3751.namprd11.prod.outlook.com ([fe80::a417:158f:9c54:b98a%5]) with mapi id 15.20.1771.011; Thu, 4 Apr 2019 05:52:21 +0000
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: "tony.li@tony.li" <tony.li@tony.li>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] Flooding Path Direction
Thread-Index: AdTqkbHsqMouS91uR3+cx5O9DydfsgAEveUAAAFawJA=
Date: Thu, 04 Apr 2019 05:52:21 +0000
Message-ID: <BYAPR11MB375129E24A8D1C0BB5E4D598C0500@BYAPR11MB3751.namprd11.prod.outlook.com>
References: <BYAPR11MB375152970011BD7563A8E271C0500@BYAPR11MB3751.namprd11.prod.outlook.com> <DE048608-1403-431D-BD88-27D95E49E089@tony.li>
In-Reply-To: <DE048608-1403-431D-BD88-27D95E49E089@tony.li>
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=jheitz@cisco.com;
x-originating-ip: [73.158.53.252]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f471c54f-ecf9-4b39-fd2b-08d6b8c1b49b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BYAPR11MB3077;
x-ms-traffictypediagnostic: BYAPR11MB3077:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BYAPR11MB3077FFE4D02D8DB5C55EEE36C0500@BYAPR11MB3077.namprd11.prod.outlook.com>
x-forefront-prvs: 0997523C40
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(366004)(39860400002)(346002)(136003)(376002)(189003)(199004)(97736004)(476003)(3846002)(53936002)(54896002)(186003)(478600001)(2501003)(25786009)(2906002)(68736007)(2351001)(5640700003)(81166006)(486006)(7696005)(8936002)(81156014)(8676002)(55016002)(74316002)(76176011)(11346002)(790700001)(6916009)(446003)(6436002)(52536014)(229853002)(5660300002)(316002)(66066001)(6306002)(256004)(14454004)(86362001)(4326008)(6506007)(4744005)(106356001)(99286004)(71190400001)(7736002)(105586002)(33656002)(71200400001)(26005)(6246003)(9686003)(102836004)(53546011)(6116002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3077; H:BYAPR11MB3751.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: JqqIWAR6YO4pZjp2twUWhV3jgGnKJcvvvyqIm3hAK/OMQpqY8eNNfzbYAnNwREW1o42L7xllvxPdil3bUGU5vH/85Ws6DTbwK91c8OY44L3leNt973Mz16+pF4nhx1lMvU/r7jFY301T9sMoUnZlEjnKcRHuB0ZWCNdUwc942zjDwzPsLsI24USijUF/yBBlfMPULXLiYRqQp45SgYiyJActSfkQNjC3g0cksATBgNrY8URr6usYPOlBUynzFQfsYq9MLht8JCWoi5plQv1KBxP5I4uHbA9RlWRmbV2QsTS+4Cr51Lt/jhMabHvV2eeEfGkGah+NyQFP2zWLCWzDdyfql6sugLwQwUxzdAT0CwqBGBBwH6ole9p7wUjXmuV9hiJcbLyu6wM0+sOsbWdGIvFSO6Qw7AuWF2V1LhSYkQc=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB375129E24A8D1C0BB5E4D598C0500BYAPR11MB3751namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f471c54f-ecf9-4b39-fd2b-08d6b8c1b49b
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2019 05:52:21.6963 (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-Transport-CrossTenantHeadersStamped: BYAPR11MB3077
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/8l4l8mxsHnqwbxK50afyUGNMVDQ>
Subject: Re: [Lsr] Flooding Path Direction
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: Thu, 04 Apr 2019 05:52:28 -0000

I think this is too restrictive.
We should not exclude algorithms that can build a flooding topology with unidirectional links.

Regards,
Jakob.

From: Tony Li <tony1athome@gmail.com> On Behalf Of tony.li@tony.li
Sent: Wednesday, April 3, 2019 10:10 PM
To: Jakob Heitz (jheitz) <jheitz@cisco.com>
Cc: lsr@ietf.org
Subject: Re: [Lsr] Flooding Path Direction


The direction of the Flooding Path in draft-ietf-lsr-dynamic-flooding-00
is not clear.

I think it should be uni-directional, such that path (1,2) is different to
path (2,1). If the path (1,2) should be bi-directional, then it can be encoded
as (1,2,1).


Hi Jakob,

The intent was that flooding be bi-directional on all links and thus (1,2) is sufficient to describe that link.

The reason for encoding things as paths is for the encoding efficiency.  (1,2,3) is more efficient than (1,2) and (2,3).

Regards,
Tony