IETF Logo Mail Archive

Re: [Lsr] Flooding Path Direction

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Thu, 04 April 2019 06:26 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 34B0C1203DB for <lsr@ietfa.amsl.com>; Wed, 3 Apr 2019 23:26:09 -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=TKGdsyug; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=KxPgZ5VZ
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 8wWckJZ7YQqt for <lsr@ietfa.amsl.com>; Wed, 3 Apr 2019 23:26:07 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DAEF1203B0 for <lsr@ietf.org>; Wed, 3 Apr 2019 23:26:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6836; q=dns/txt; s=iport; t=1554359165; x=1555568765; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=omMia3RSuUwaOjB7deWXqLQ8HKKgMogNk9SvfRwJ2FY=; b=TKGdsyugO2mRpVGlBsV0bQ68TTGh/aJ6v/oJdO2jcJOmEOV1G5GQ3wnb gVU1DlYXte6jTBUOa9/C/f9EL47B6n/mXwBeWi/5LbkzbYPLbX0JJwbkk EkBOUZcUxsOhEd7lYQiOVLf4TRQrC/npIP1LLV7Ni4sF95fk4YeJkNMFL Y=;
IronPort-PHdr: 9a23:2jty4BUQUA3t857DZDReZitv6yvV8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSANSJ8OpK3uzRta2oGXcN55qMqjgjSNRNTFdE7KdehAk8GIiAAEz/IuTtank4HMlDSE1N9HCgOk8TE8H7NBXf
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ASAAB7oqVc/4UNJK1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ4vUANoVCAECycKhASDRwOEUopSgleJOIkThEqBLoEkA1QOAQEshEACF4UtIjQJDQEBAwEBCQEDAm0cAQuFSgEBAQEDIwoTAQE3AQ8CAQgRBAEBKwICAh8RHQgBAQQOBQiDG4ERTAMVAQKgfAKKFHGBL4J5AQEFhRINC4IMCIEwAYsyF4FAP4FXgkw+ghqCLIMIMYImjQ2EKYdajCU2CQKQNINelE6LTodfjBECBAIEBQIOAQEFgU84gVZwFYMnggqDb4NGhw1ygSiOIwGBHgEB
X-IronPort-AV: E=Sophos;i="5.60,306,1549929600"; d="scan'208,217";a="458063330"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Apr 2019 06:26:03 +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 x346Q4ga006971 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Apr 2019 06:26:04 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.1473.3; Thu, 4 Apr 2019 01:26:03 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 4 Apr 2019 02:26:02 -0400
Received: from NAM04-SN1-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.1473.3 via Frontend Transport; Thu, 4 Apr 2019 01:26:02 -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=omMia3RSuUwaOjB7deWXqLQ8HKKgMogNk9SvfRwJ2FY=; b=KxPgZ5VZ1RyHPAQv2BYUAHlM9EFxA9V/2H/mooI5DbC6ubJMh1SZ/LYGVkcH31ayzBnfY6tdiaAb2ievAlRJRQUtMPCiShZrCl4P/KcT7r+BtVgC3OREP+flvutDhqkwN6we/0lIjprmkifhwNQb0o+sTb38cCq+d8gb37oTQfM=
Received: from BYAPR11MB3751.namprd11.prod.outlook.com (20.178.238.144) by BYAPR11MB3271.namprd11.prod.outlook.com (20.177.185.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.15; Thu, 4 Apr 2019 06:26:01 +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 06:26:01 +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+cx5O9DydfsgAEveUAAAFawJAAAQ+AgAAANmRw
Date: Thu, 04 Apr 2019 06:26:01 +0000
Message-ID: <BYAPR11MB3751127FEA49D06038EBE623C0500@BYAPR11MB3751.namprd11.prod.outlook.com>
References: <BYAPR11MB375152970011BD7563A8E271C0500@BYAPR11MB3751.namprd11.prod.outlook.com> <DE048608-1403-431D-BD88-27D95E49E089@tony.li> <BYAPR11MB375129E24A8D1C0BB5E4D598C0500@BYAPR11MB3751.namprd11.prod.outlook.com> <89E37338-8E33-43F9-B8AB-76DD1884914C@tony.li>
In-Reply-To: <89E37338-8E33-43F9-B8AB-76DD1884914C@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: 2fb70729-0a9e-4338-5d84-08d6b8c66868
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BYAPR11MB3271;
x-ms-traffictypediagnostic: BYAPR11MB3271:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BYAPR11MB3271B3B2500A87F34E803DFAC0500@BYAPR11MB3271.namprd11.prod.outlook.com>
x-forefront-prvs: 0997523C40
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(366004)(396003)(346002)(39860400002)(376002)(136003)(199004)(189003)(790700001)(446003)(256004)(105586002)(8936002)(102836004)(68736007)(5640700003)(11346002)(6436002)(4744005)(2906002)(86362001)(486006)(9686003)(25786009)(53546011)(66066001)(53936002)(5660300002)(93886005)(2501003)(6246003)(476003)(52536014)(99286004)(229853002)(6306002)(97736004)(14454004)(26005)(6506007)(54896002)(76176011)(7696005)(74316002)(2351001)(55016002)(81156014)(71190400001)(478600001)(6916009)(4326008)(3846002)(106356001)(186003)(7736002)(33656002)(316002)(71200400001)(6116002)(8676002)(81166006)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3271; H:BYAPR11MB3751.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: h/6S7vBpcC/nbepN7w8AE0HCxu0ioJ99MJQY3HWIss4EKW9kizQCcFmW3oFox58/sHavvMEwmhZxLhhw4PvnnnbSA+uqkivJGpHKnwxV/+IUDjukopvMYkEzRdjBVFhdEUW11heHKGvs/Tzyv7YMqwEtzp/rhqwQ0D50bZ5wkDpu5TELtsrVzvyymlPKVvCdwc0fvhu+o3ahmobE0PGS5sLo1aDpcIK8h7ut5BQM/ve4QNvzi97MNn6wzjAka6cMwunxqjEL9lGVun4ONneBr4xnLGMlqkQc6OKN1qr9oaVDDBMneCA6fQ0/9OtUpIbT/0GukkO5W0DeMZamP5mCT7ZnaxdeRMQOcLXJUwofZlzOWDDVCwtLe6wJ1XxXCvQIGZQ01dbR8v4IaqsrpduTEVAkEDfqpbiOEihGDJdIbvU=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB3751127FEA49D06038EBE623C0500BYAPR11MB3751namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2fb70729-0a9e-4338-5d84-08d6b8c66868
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2019 06:26:01.3558 (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: BYAPR11MB3271
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/DcDLBNhmHJakMcpoDvzUt5ef6ZQ>
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 06:26:09 -0000

I mean flooding in one direction only, not unidirectional forwarding.

Regards,
Jakob.

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


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


Well, right now, the protocol doesn’t really support unidirectional links. At all.

Tony

v2.23.0 | Report a Bug | By Email