Re: [Idr] new thread regarding capabilities handling

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Sun, 30 April 2017 22:31 UTC

Return-Path: <jheitz@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB3D12947B for <idr@ietfa.amsl.com>; Sun, 30 Apr 2017 15:31:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.823
X-Spam-Level:
X-Spam-Status: No, score=-11.823 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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
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 1QSyajScB1Zj for <idr@ietfa.amsl.com>; Sun, 30 Apr 2017 15:31:03 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D7681204DA for <idr@ietf.org>; Sun, 30 Apr 2017 15:29:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=839; q=dns/txt; s=iport; t=1493591351; x=1494800951; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Il+TQhA/u3SdfbErHEATXI5O3tMuN3XyEd6L72S6C2c=; b=WoLCDOF/4aGSKtlGPTTNMv3JTSXo0eHxhGaYEiYsMXTZqzduwYGyhDLM fTzYF/19N6jb+S7fOBr2ClCgt8R1AhtY13s9fMSnwg8h6LHCo+4gxXcGX fpM/80huLUc1A3RPsBngh/cV/b21b+bltBpGnKskGM090q3mo8Tcyf0Tf 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DNAAD9YwZZ/4kNJK1cGQEBAQEBAQEBAQEBBwEBAQEBgywpYoEMB415kU2VbYIPIQuFeAKENz8YAQIBAQEBAQEBayiFFQEBAQEDAQE4NAsMBAIBCA4DBAEBAR4JBycLFAkIAgQBDQUIiAkBgg0OsHSLDQEBAQEBAQEBAQEBAQEBAQEBAQEBARgFhl+EeYQ0EgGGAQWdUwGTB5FnlCwBHzh/C28VRIZwdYZzgSGBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.37,397,1488844800"; d="scan'208";a="419899673"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 30 Apr 2017 22:29:10 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v3UMTAdi018662 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 30 Apr 2017 22:29:10 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 30 Apr 2017 17:29:09 -0500
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1210.000; Sun, 30 Apr 2017 17:29:09 -0500
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, Robert Raszuk <robert@raszuk.net>
CC: idr wg <idr@ietf.org>
Thread-Topic: [Idr] new thread regarding capabilities handling
Thread-Index: AQHSvxW8g4JW974FxUC7sLdZ6BzDD6HZBUUAgAALVYCAAOuqAIAACjgAgACKNICAABaTgIAAEg2AgAPJcFA=
Date: Sun, 30 Apr 2017 22:29:09 +0000
Message-ID: <3f8ec5766b5348c5a27bbe5ad1fecb11@XCH-ALN-014.cisco.com>
References: <alpine.DEB.2.02.1704270713380.5591@uplift.swm.pp.se> <a7a10b72-2215-9968-e4c8-0592e29ce893@cisco.com> <alpine.DEB.2.02.1704270812470.5591@uplift.swm.pp.se> <20170427201736.GF22975@pfrc.org> <e4ad3bd2-73cd-c1f7-6ef4-8bbd974974ae@cisco.com> <alpine.DEB.2.02.1704280706040.5591@uplift.swm.pp.se> <CA+b+ERn6fdTTkWWSXN4nHgs+QJevrH3Hzh54f5Sgijt-0Aei7A@mail.gmail.com> <alpine.DEB.2.02.1704280919340.5591@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1704280919340.5591@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.8.22]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/IZeQGUetUOGkY8sroV8cO4u8q7c>
Subject: Re: [Idr] new thread regarding capabilities handling
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 22:31:05 -0000

If it goes down with a notification message, you don't get GR.
I haven't tried it, but I bet you get a CEASE.

Thanks,
Jakob.


> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Mikael Abrahamsson
> Sent: Friday, April 28, 2017 12:34 AM
> To: Robert Raszuk <robert@raszuk.net>
> Cc: idr wg <idr@ietf.org>
> Subject: Re: [Idr] new thread regarding capabilities handling
> 
> On Fri, 28 Apr 2017, Robert Raszuk wrote:
> 
> > Just try it out ;)
> 
> I have tried it out. From what I remember we had to turn it off because it
> gave us 3 minute outages that we didn't much desire.
> 
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr