Re: [OSPF] OSPF Topology Transparent Zone (TTZ) Next Steps

"Russ White" <> Tue, 09 July 2013 16:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 24B3B21F9AAB for <>; Tue, 9 Jul 2013 09:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.334
X-Spam-Status: No, score=-2.334 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id A9Gx2Q9g+ZCR for <>; Tue, 9 Jul 2013 09:50:25 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 4D57921F8EB2 for <>; Tue, 9 Jul 2013 09:50:25 -0700 (PDT)
Received: from ([] helo=USCSWHITER10L1C) by with esmtpa (Exim 4.80.1) (envelope-from <>) id 1Uwb7N-000683-KI; Tue, 09 Jul 2013 09:50:21 -0700
From: "Russ White" <>
To: "'Acee Lindem'" <>, "'OSPF List'" <>
References: <>
Date: Tue, 9 Jul 2013 12:50:34 -0400
Message-ID: <03d201ce7cc4$6e853160$4b8f9420$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJASbXjpHZnDaWjys0nPldLDGuuhZh0eshwgAR5oGA=
Content-Language: en-us
X-Antivirus-Scanner: Seems clean. You should still use an Antivirus Scanner
Subject: Re: [OSPF] OSPF Topology Transparent Zone (TTZ) Next Steps
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 09 Jul 2013 16:50:31 -0000

I want to clarify something on this thread...

> In general, I think this is useful. I can think of specific situations
where it
> would be nice/would have been nice to have. In fact, a few of us went some
> ways towards designing just such a system (using different mechanisms)
> when we were deep into the MANET/OSPF space, but never released,
> implemented, etc., the idea.

This part I think is true --I think we need to think about use cases in this
space, and figure out if there are interesting things to do in the OSPF
space to handle those use cases.

> I would put my vote into making this a WG doc and moving it forward.

OTOH, I've looked through these drafts again, and talked to a couple of
other folks about them, and it seems, to me, that we're starting from the
wrong end of the stick. What we seem to have, right now, is a set of
solution drafts, and everyone is thinking of a different set of problems
when they read those solutions (including me --I read this draft and think,
"this would be useful to solve that problem, if only we could make the
overall modifications simpler, and change this over here, and..."). 

What might be useful would be to step back from the solutions draft for a
moment and build a use cases/requirements draft to start from, rather than
working from these solutions drafts specifically.