IETF Logo Mail Archive

Re: [Lsr] Open issues with Dynamic Flooding

John E Drake <jdrake@juniper.net> Thu, 07 March 2019 20:12 UTC

Return-Path: <jdrake@juniper.net>
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 4936B126C87 for <lsr@ietfa.amsl.com>; Thu, 7 Mar 2019 12:12:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.233
X-Spam-Level:
X-Spam-Status: No, score=-1.233 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KHOP_DYNAMIC=1.468, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 W0mfge4K2mN0 for <lsr@ietfa.amsl.com>; Thu, 7 Mar 2019 12:12:46 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 73260129B88 for <lsr@ietf.org>; Thu, 7 Mar 2019 12:12:46 -0800 (PST)
Received: from pps.filterd (m0108158.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x27K5B9W030021; Thu, 7 Mar 2019 12:12:43 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=5uhBRT4+ll5ikhGfLJs8fVy22+S1Z5AYCMFEBHob6Lg=; b=MZMCVGPewJ5UYXt4mfAmomUzVYqcJP5GCYzR5giadd0JXeGwpfA0hWr4TA0uX4RYrHv0 0yoITiVeUDoHPNk5gY2K1lsIV4ifYo5oN5AI387NKPL7Dh8sq4nPQ9iCt7i3Lu9xBOkq R2XWyDs29agHLdLB4zqOkY9hjAZQ9SbcoSfVAt8bGeO82hMirOk73FKn1qLkzm+QwYBZ Tva7ERF8PkGCTinqxdmPctgkq879YjkzUcDTbO6IoFXgwzQXbiIR7uKZcvjTGsgC2ybx 1QL9Y0Jj48l1dX0Jc1+6IPQQRRQhHKS1raqWeJwz1XL/1CmqOIy/H0v8Wn+I4ZAWTkvY Eg==
Received: from nam02-cy1-obe.outbound.protection.outlook.com (mail-cys01nam02lp2055.outbound.protection.outlook.com [104.47.37.55]) by mx0a-00273201.pphosted.com with ESMTP id 2r36nc0f8v-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 07 Mar 2019 12:12:43 -0800
Received: from BYAPR05MB5029.namprd05.prod.outlook.com (20.177.230.211) by BYAPR05MB5943.namprd05.prod.outlook.com (20.178.51.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.8; Thu, 7 Mar 2019 20:12:41 +0000
Received: from BYAPR05MB5029.namprd05.prod.outlook.com ([fe80::b58f:10f1:a40b:abf7]) by BYAPR05MB5029.namprd05.prod.outlook.com ([fe80::b58f:10f1:a40b:abf7%4]) with mapi id 15.20.1686.016; Thu, 7 Mar 2019 20:12:41 +0000
From: John E Drake <jdrake@juniper.net>
To: Peter Psenak <ppsenak@cisco.com>, "tony.li@tony.li" <tony.li@tony.li>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] Open issues with Dynamic Flooding
Thread-Index: AQHU0rNaVvQ0QBVMlk2Xrz5VBQhbhaX8p2YAgACQ6ICAAALpAIAABY6AgAA9MgCAAAYKgIAABbWAgAAGcQCAAt1tAIAAIqmAgAAOY8A=
Date: Thu, 07 Mar 2019 20:12:41 +0000
Message-ID: <BYAPR05MB5029B48974AE30912431CE23C74C0@BYAPR05MB5029.namprd05.prod.outlook.com>
References: <AAD29CF0-F0CA-4C3C-B73A-78CD2573C446@tony.li> <c1adac3a-cd4b-130e-d225-a5f40bf0ef55@cisco.com> <F3C4B9B2-F101-4E28-8928-9208D5EBAF99@tony.li> <be28dbcf-8382-329a-229f-5b146538fabe@cisco.com> <966E5756-8CEF-47F4-8564-E23D38F0743E@tony.li> <c8f40acb-94fe-f42a-aa0a-3a42e0067be8@cisco.com> <7F522B6C-9D28-4533-8ABD-9F492D9AF26C@tony.li> <a33ff3ba-975b-2ef2-93e9-1bc9664fdd5a@cisco.com> <2932F33A-1F9E-4C20-A233-E569D8935AE4@tony.li> <C723C078-72FD-426C-99F2-F0A494E0E971@tony.li> <884f0f45-813f-93f0-a63e-f510e5f01ab1@cisco.com>
In-Reply-To: <884f0f45-813f-93f0-a63e-f510e5f01ab1@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.1.100.23
dlp-reaction: no-action
x-originating-ip: [66.129.241.12]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: efb75636-36ed-4c1c-d514-08d6a339409f
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(4618075)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB5943;
x-ms-traffictypediagnostic: BYAPR05MB5943:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BYAPR05MB5943ED4860315F7DB4CC4008C74C0@BYAPR05MB5943.namprd05.prod.outlook.com>
x-forefront-prvs: 096943F07A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(136003)(376002)(346002)(396003)(39860400002)(199004)(189003)(13464003)(106356001)(256004)(186003)(81166006)(53936002)(26005)(71190400001)(71200400001)(76176011)(9686003)(68736007)(102836004)(316002)(3846002)(7736002)(305945005)(7696005)(6506007)(53546011)(93886005)(55016002)(81156014)(97736004)(105586002)(86362001)(2501003)(66066001)(14444005)(486006)(19627235002)(4326008)(229853002)(99286004)(476003)(14454004)(33656002)(6306002)(6436002)(11346002)(8936002)(74316002)(2906002)(6246003)(8676002)(52536013)(6116002)(5660300002)(446003)(966005)(25786009)(110136005)(478600001); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB5943; H:BYAPR05MB5029.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: pQWTWbX4fdaP3yn3nYerROu6+OyMSVoS9Zmx5fHdyT7V6ORj5eJwSNZshsQX5U/E/B3kBhCbuuElvrc+Ks/GXBWLjoJBvJXGuSZs4b+fXTvflxzoCO3mhkkDFsegFB4+Gn4K4xWaKGWwEBk92toM8Px60uxZPSBGL5MfnEGdzF2hDHq3r1SuYFokWrZbyNcoyA5c4MrKn7g02SZWejGmDct8xKthdU1Rm8Ie9slriNhMPJtOyXvkUHMYQ9j36ctBKyX08mwIi3lTCHA212fpy5X12Em9yXE5yeup6G9q/UB1az7EB43ogSxtf3/CzFRfco13uhX80mYXh372h3x0xYwi/wIePy2/X9rR3xnbaS6C6mzvMbGjb8csX42rj3e/kYPH7z6RpdygP5e5kjP8gP/VNDLQNjkflbOfTZ9yD5o=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: efb75636-36ed-4c1c-d514-08d6a339409f
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Mar 2019 20:12:41.1183 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB5943
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-07_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903070135
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/fWjHvJ3C10t_R7Phn7ctp5KGbFY>
Subject: Re: [Lsr] Open issues with Dynamic Flooding
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, 07 Mar 2019 20:12:48 -0000

Hi,

What does 'rate limit' mean in this context?

Yours Irrespectively,

John

> -----Original Message-----
> From: Lsr <lsr-bounces@ietf.org> On Behalf Of Peter Psenak
> Sent: Thursday, March 7, 2019 2:20 PM
> To: tony.li@tony.li
> Cc: lsr@ietf.org
> Subject: Re: [Lsr] Open issues with Dynamic Flooding
> 
> On 07/03/2019 18:16 , tony.li@tony.li wrote:
> >
> >
> >> On Mar 5, 2019, at 1:31 PM, tony.li@tony.li <mailto:tony.li@tony.li>
> >> wrote:
> >>
> >> Let me propose that we add something to sections 6.7.5, 6.7.9, and
> >> 6.7.11 like:
> >>
> >> Addition of temporary flooding should be done with caution, as the
> >> addition of excessive connectivity to the flooding topology may
> >> trigger unwanted behavior. Routers SHOULD add temporary flooding in a
> >> rate limited manner, if not configured otherwise.
> >
> >
> > Hi,
> >
> > I haven’t heard any feedback on this.  Can we please adopt this?
> >
> > The draft cutoff is Monday, March 11.  Could we please incorporate
> > this change and the addition of the pseudonode identifier by then?
> 
> I don't think there is an agreement on the LAN side.
> 
> Rate limiting we can add, but we can do that after March 11, I don't see a need
> to do it before.
> 
> thanks,
> Peter
> 
> 
> >
> > Tony
> >
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_lsr&d=DwIGaQ&c=HAkYuh63rsuhr6Scbfh0
> UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-
> s_xXXup3HzvBSMRj5VE&m=8bZHYmmMERie3AZxsYrvUH_fhv9JyTIkivlY1wizKms
> &s=ZRx3I9aH56q-UmcY_tUkOuIAxjGDEMgE_qeMPmekSgk&e=

v2.23.0 | Report a Bug | By Email