Re: [OSPF] Immediate Replying Hello
"Acee Lindem (acee)" <acee@cisco.com> Wed, 31 January 2018 15:16 UTC
Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62DC412EC04 for <ospf@ietfa.amsl.com>; Wed, 31 Jan 2018 07:16:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.529
X-Spam-Level:
X-Spam-Status: No, score=-14.529 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 mCw20A7aRarF for <ospf@ietfa.amsl.com>; Wed, 31 Jan 2018 07:16:05 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B68AF12EB5E for <ospf@ietf.org>; Wed, 31 Jan 2018 07:15:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13936; q=dns/txt; s=iport; t=1517411734; x=1518621334; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=iXwtL54TYnZqEaGyAfGbKhygdTxO8bHQOir1Wk/VIGE=; b=dU5MXDAUFLLK+YAYGeoGzPQbdAaTDUhqszEpgwqtPwLEb7DiBP9s5j9L b8/VqP+rcRi9kQE5HukOYDhWpXyVU7R5kuUGHTB8R2imZY9xEnYQqvdK+ bY80tl4+37r+hLWjUdi1P5YQarCinqyNW6VL+hu3yVQNMnPs91+EaLJTg s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DCAQDM3HFa/49dJa1aGQEBAQEBAQEBAQEBAQcBAQEBAYJKSy1mdSgKg1aYUIICkXKHawolhRYCGoI1VxUBAQEBAQEBAQJrKIUjAQEBBCNmAgEIEQMBAQEoAwICAjAUCQgBAQQBEolRZBCmZYInimMBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYRbghWDaIMFgy8CAgEBggQJFoJhMYI0BYpdgRCIS4VhigUCiBaNVIIdkhCLBoJhiVUCERkBgTsBNSMlgStwFT0qAYF/CYNyAQEBeXgBixyBFwEBAQ
X-IronPort-AV: E=Sophos; i="5.46,440,1511827200"; d="scan'208,217"; a="64476620"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Jan 2018 15:15:33 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id w0VFFWKw017288 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 31 Jan 2018 15:15:33 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 31 Jan 2018 10:15:32 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Wed, 31 Jan 2018 10:15:31 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "rui.valadas@tecnico.ulisboa.pt" <rui.valadas@tecnico.ulisboa.pt>, "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: [OSPF] Immediate Replying Hello
Thread-Index: AdOabOwv6GrDPNKQQD+raPWu8jRIMgAJLucAAAxdKID//8ZxgA==
Date: Wed, 31 Jan 2018 15:15:31 +0000
Message-ID: <258A916F-195A-4AE3-9A3C-73B45C81DF51@cisco.com>
References: <000c01d39a6d$602ea9e0$208bfda0$@tecnico.ulisboa.pt> <DAAB9EC6-D53A-4639-BC7E-9435D8B97B3C@cisco.com> <00b601d39a99$3421cae0$9c6560a0$@tecnico.ulisboa.pt>
In-Reply-To: <00b601d39a99$3421cae0$9c6560a0$@tecnico.ulisboa.pt>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: multipart/alternative; boundary="_000_258A916F195A4AE39A3C73B45C81DF51ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/G7NmKk6LEg9CjUQrpGiYeiT6-ho>
Subject: Re: [OSPF] Immediate Replying Hello
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jan 2018 15:16:12 -0000
From: OSPF <ospf-bounces@ietf.org> on behalf of "rui.valadas@tecnico.ulisboa.pt" <rui.valadas@tecnico.ulisboa.pt> Date: Wednesday, January 31, 2018 at 8:44 AM To: OSPF WG List <ospf@ietf.org> Subject: Re: [OSPF] Immediate Replying Hello Hi, It helps, thanks. But the Kou draft (https://datatracker.ietf.org/doc/draft-kou-ospf-immediately-replying-hello/ ) also mentions two other situations where immediate hellos must be sent: after state changes from “2-Way” or greater down to “Init” (case 2), and after DR election (case 3). Do you know if these cases are also implemented? While there are other cases where hellos are sent other than on a timer, I don’t know of these cases being implemented. Thanks, Acee Thanks. Rui From: Acee Lindem (acee) [mailto:acee@cisco.com] Sent: Wednesday, January 31, 2018 12:47 PM To: rui.valadas@tecnico.ulisboa.pt; ospf@ietf.org Subject: Re: [OSPF] Immediate Replying Hello Hi Rui, It is not a standard. However, it is a technique used by many implementations to speed adjacency formation when a hello packet is received and the neighbor state is less than two-way. At least one of the implementations with witch with I have been associated would unicast the hello. Hope this helps, Acee From: OSPF <ospf-bounces@ietf.org<mailto:ospf-bounces@ietf.org>> on behalf of "rui.valadas@tecnico.ulisboa.pt<mailto:rui.valadas@tecnico.ulisboa.pt>" <rui.valadas@tecnico.ulisboa.pt<mailto:rui.valadas@tecnico.ulisboa.pt>> Date: Wednesday, January 31, 2018 at 3:28 AM To: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>> Subject: [OSPF] Immediate Replying Hello Hi, Many OSPF implementations include the Immediate Replying Hello feature, which I believe is not standard. The only reference I found is the draft “Update to OSPF Hello procedure, draft-kou-ospf-immediately-replying-hello-02.txt” which has expired. Are vendors following what is written in this draft? Is there a document from any vendor that details this feature? Thanks. Rui Valadas
- [OSPF] Immediate Replying Hello rui.valadas
- Re: [OSPF] Immediate Replying Hello Acee Lindem (acee)
- Re: [OSPF] Immediate Replying Hello rui.valadas
- Re: [OSPF] Immediate Replying Hello Acee Lindem (acee)