[OSPF] draft-atlas-ospf-mrt-02

"Russ White" <russw@riw.us> Sun, 06 July 2014 12:41 UTC

Return-Path: <russw@riw.us>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 051CB1A0120 for <ospf@ietfa.amsl.com>; Sun, 6 Jul 2014 05:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level:
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 Pvj1hOwFvFIp for <ospf@ietfa.amsl.com>; Sun, 6 Jul 2014 05:41:35 -0700 (PDT)
Received: from server.riw.us (server.riw.us [162.144.32.236]) (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 F31C81A011C for <ospf@ietf.org>; Sun, 6 Jul 2014 05:41:34 -0700 (PDT)
Received: from 108-78-210-25.lightspeed.chrlnc.sbcglobal.net ([108.78.210.25]:52186 helo=RussPC) by server.riw.us with esmtpsa (UNKNOWN:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from <russw@riw.us>) id 1X3ll6-0003le-Oo; Sun, 06 Jul 2014 12:41:33 +0000
From: Russ White <russw@riw.us>
To: 'OSPF List' <ospf@ietf.org>
Date: Sun, 06 Jul 2014 08:41:26 -0400
Message-ID: <02df01cf9917$9b05a650$d110f2f0$@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: Ac+ZFv4nWa+hKUOQQ8u/arcrmksngA==
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.riw.us
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
X-Get-Message-Sender-Via: server.riw.us: authenticated_id: russw@riw.us
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/2mXVkvWjfpXcc0dnUefzVYCdIf8
Cc: 'Alia Atlas' <akatlas@juniper.net>
Subject: [OSPF] draft-atlas-ospf-mrt-02
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 06 Jul 2014 12:41:37 -0000

Just one question/comment on this draft -- In section 6.1, MRT-Ineligible
Links TLV for OSPFv2, the draft says there should be a new TLV in the router
capabilities LSA that advertises links not to be included in the MRT
calculation (excluded links). I'm not certain why an option isn't used in
the LSA header for this, instead. Two things that seem strange to me:

- The exclusion of a link is a link property, not a router property, so I'm
not certain why this would be advertised as a property of the OSPF router.
This seems to muddy the line between router and properties and link
properties in a way that sets the stage for make the router capabilities
just another area into which to stuff various bits of information we can't
find a home for elsewhere.

- If you modify a specific link state, then you must advertise two TLVs, or
rather two LSAs, rather than one. Thus these two pieces of information must
be connected in a local database, but advertised separately, with all the
coordination/etc. that implies.

It seems like it might be better to move this bit of information into the
TLV where the actual link state is advertised in some way.

:-)

Russ