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

"Acee Lindem (acee)" <acee@cisco.com> Sat, 06 May 2017 17:04 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 2361E1274D0 for <ospf@ietfa.amsl.com>; Sat, 6 May 2017 10:04:03 -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 MP3K7I_VecWX for <ospf@ietfa.amsl.com>; Sat, 6 May 2017 10:04:01 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F02D127698 for <ospf@ietf.org>; Sat, 6 May 2017 10:04:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10581; q=dns/txt; s=iport; t=1494090241; x=1495299841; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=iOGsbXaYCEXMaEPdr/YzjvL5ryb6tnt4tNQPHTyvok0=; b=ZNnoR8V73mXD9JLF7u9PhyaWTehu7sNeUzzVxetzzeuxjqo4rlTwfHQE Vzq84eBEKmHXJI+VAB9iq8A85pQHJ8FAPCtHKzFcfVjbt/wWqxtqfr1Yu C/ucFb9dfE2tAOrAhCQgIRBEMHkueL2WQp4LidugG/dg4N2aU7hEMnTqj E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AsAQC/AA5Z/49dJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm5ngW4Hg2GKGJFWkDqFOIIPhiQCGoQvPxgBAgEBAQEBAQFrKIU?= =?us-ascii?q?VAQEBAQMjCkwQAgEIEQMBAigDAgICMBQJCAIEDgWKIK9jgiaKYAEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAR2LWIQ/OwmCaoJfBZ15AZMXggSFPINmhkaUPQEfOIEKcBV?= =?us-ascii?q?GhSmBSnaGQ4EwgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.38,299,1491264000"; d="scan'208,217";a="420584519"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 May 2017 17:04:00 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v46H40J9011898 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 6 May 2017 17:04:00 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 6 May 2017 13:03:59 -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; Sat, 6 May 2017 13:03:59 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: prz <prz@zeta2.ch>
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//++hoA=
Date: Sat, 6 May 2017 17:03:59 +0000
Message-ID: <D5337994.AD4ED%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>
In-Reply-To: <cd38c9344603d9733413bda06ccc6003@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_D5337994AD4EDaceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/YJYYGFo1jxINW8mVUlGRXwkKq8U>
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: Sat, 06 May 2017 17:04:03 -0000

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