Re: [OSPF] WG Adoption Poll for "OSPF LLS Extensions for Local Interface ID Advertisement"

"Acee Lindem (acee)" <acee@cisco.com> Mon, 08 May 2017 00:13 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 DCC76126DED for <ospf@ietfa.amsl.com>; Sun, 7 May 2017 17:13:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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, 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 5p2UhZALEBxF for <ospf@ietfa.amsl.com>; Sun, 7 May 2017 17:13:24 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83413126C83 for <ospf@ietf.org>; Sun, 7 May 2017 17:13:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25123; q=dns/txt; s=iport; t=1494202404; x=1495412004; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=sKdTv5ivkwZk808jk8q+VgX917yhQ3ZHUHs6H39wpM0=; b=FUXGIw/d51l44h0EuyouEO9JTA6duCHlmX3y+hrJksiEUPYLzJRbJdEl cId6fUSj/DNqmPbH8/iXFfxJs1E65ZPsZFTUJKZV7bbhYQBQjjKc7JVuf eQPrESxjuAs2FfRgblxHdRTQ9GclfDlN/fq8PdMi68Id6PBFI5+iQYhkE k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AdAQCotw9Z/4QNJK1SChkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJuZ4FuB4NhihiRVZVygg+GJAIahC8/GAECAQEBAQEBAWsohRU?= =?us-ascii?q?BAQEBAyMKTBACAQgRAwEBASgDAgICMBQJCAIEAQ0FiiCwSYImil4BAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEdi1iEOwQ7CYJqgl8FnXkBkxeCBIU8g2aGRpQ9AR84gQp?= =?us-ascii?q?wFUaFKYFKdoZmgTCBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.38,306,1491264000"; d="scan'208,217";a="231971288"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 May 2017 00:13:22 +0000
Received: from XCH-RTP-003.cisco.com (xch-rtp-003.cisco.com [64.101.220.143]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v480DMkK023436 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 8 May 2017 00:13:23 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-003.cisco.com (64.101.220.143) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 7 May 2017 20:13:22 -0400
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.1210.000; Sun, 7 May 2017 20:13:22 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: prz <prz@zeta2.ch>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
CC: OSPF WG List <ospf@ietf.org>
Thread-Topic: [OSPF] WG Adoption Poll for "OSPF LLS Extensions for Local Interface ID Advertisement"
Thread-Index: AQHSxQanGGW4vWTLFUe0gcAxuCky/6Hkn50AgAF8kID//75WAIAB8mYA//++hoCAAcBGrIAASgaA
Date: Mon, 8 May 2017 00:13:21 +0000
Message-ID: <D5352E8F.ADC9D%acee@cisco.com>
References: <D530EF1D.ACB7C%acee@cisco.com> <D53106AD.ACBA9%acee@cisco.com> <c74bd39c55533350e96a1884b7ed9af1@zeta2.ch> <D5320E98.ACF48%acee@cisco.com> <cd38c9344603d9733413bda06ccc6003@zeta2.ch> <D5337994.AD4ED%acee@cisco.com> <c5fb4ee5708a4caab2029943dd2e8eae@XCH-ALN-001.cisco.com> <7eea417112171448d368d007ae0a5da4@zeta2.ch>
In-Reply-To: <7eea417112171448d368d007ae0a5da4@zeta2.ch>
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.197]
Content-Type: multipart/alternative; boundary="_000_D5352E8FADC9Daceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/RimasOYMjbJ1C9xQjTHiMn5Z4sA>
Subject: Re: [OSPF] WG Adoption Poll for "OSPF LLS Extensions for Local Interface ID Advertisement"
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: Mon, 08 May 2017 00:13:27 -0000


From: prz <prz@zeta2.ch<mailto:prz@zeta2.ch>>
Date: Sunday, May 7, 2017 at 3:47 PM
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.com>>
Cc: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>
Subject: Re: [OSPF] WG Adoption Poll for "OSPF LLS Extensions for Local Interface ID Advertisement"


I try to parse that and am still not clear what you both are saying



1. It seems you both saying that RFC3630 is expected now to be used on unnumbered only (for which I find no indication) or are you claiming it's only used that way? Based on which implementation or document? What is "repurposing"? RFC3630 is a published Standards track RFC and I don't know what "re-purposing" standards RFCs means?

RFC 3630 is specific to OSPF TE Opaque LSAs and what I’m saying is that for this specific usage for interface ID discovery, the repurposing the TE LSAs is limited to unnumbered interfaces. For the second time, can you confirm???




2. Or are you saying that the new draft will be restricted to unnumbered only? In which case I expect a new version of draft to discuss further and agree taht the backwards compat section colllapses to "unnumbered link" considerations only  ...

Absolutely not – the draft that is under WG consideration is for general purpose discovery of interface IDs. I believe this point is clear if you read the draft.

Thanks,
Acee


?

--- tony



On Sat, 6 May 2017 18:15:21 +0000, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.com>> wrote:
Tony –

It is known that link identifiers are useful even in cases of numbered links e.g. some telemetry applications prefer to use link identifiers to identify all links (numbered and unnumbered).
So I share Acee’s expectations.

   Les


From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Saturday, May 06, 2017 10:04 AM
To: prz
Cc: OSPF WG List
Subject: Re: [OSPF] WG Adoption Poll for "OSPF LLS Extensions for Local Interface ID Advertisement"

Hi Tony,

I’ll have to discuss with the authors - but my impression is that this would not be limited to unnumbered links.  My understanding is that the repurposing of link–local OSPF TE LSAs is only done on unnumbered links so that would be the main focus of the backward compatibility discussion.

Thanks,
Acee

From: prz <prz@zeta2.ch<mailto:prz@zeta2.ch>>
Date: Saturday, May 6, 2017 at 12:58 PM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>
Cc: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>
Subject: Re: [OSPF] WG Adoption Poll for "OSPF LLS Extensions for Local Interface ID Advertisement"


Hey Acee,

1. looking fwd to read the revision with backwards compatibility section and definition which Hello FSM states the extension applies to

2. I try to read what you say carefully but please clarify: there's nothing in rfc5613 that prevents LLC on any link so do you mean, you suggest  to use this TLV on unnumbered links _only_?  Or do you suggest that RFC3630 implies somehow that LS TE LSAs are used on unnumbered links _only_? If so, I don't see anything in the RFC to this effect ...

--- tony



On Fri, 5 May 2017 15:14:30 +0000, "Acee Lindem (acee)" <acee@cisco.com<mailto:acee@cisco.com>> wrote:
Hi Tony,
The authors will cover this in the next revision. Based on discussions, the usage of link-scoped TE LSAs is limited to unnumbered point-to-point links. If this is the case, the backward compatibility is much simpler than the other discussions we’ve been having.
Thanks,
Acee
From: prz <prz@zeta2.ch<mailto:prz@zeta2.ch>>
Date: Friday, May 5, 2017 at 11:09 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>
Cc: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>
Subject: Re: [OSPF] WG Adoption Poll for "OSPF LLS Extensions for Local Interface ID Advertisement"

Not sure it made it from my other address so rtx to the list ...

A conditional against here ...
I am fine with adoption if I see a version that spells the detailed behavior and especially interactions between RFC4302 and this draft in a detailed section, i.e. both on, RFC4302 gets configured/unconfigured, are the LLS extensions advertised on every hello or just until a specific state (like ISIS padding thingies) and so on ...
I'd rather have this now than a LC discussion ...
The idea is deceptively simple but it is a redundant mechanism and those always end causing inter-op problems unless cleanly spelled out ...
--- tony