Re: [OSPF] OSPF Topology Transparent Zone (TTZ) WG poll for adoption as experimental

"Daniel King" <> Thu, 22 January 2015 22:21 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 7B6431A882C for <>; Thu, 22 Jan 2015 14:21:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AqE3EB-ZDy0g for <>; Thu, 22 Jan 2015 14:21:13 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CC2811A87F2 for <>; Thu, 22 Jan 2015 14:21:12 -0800 (PST)
Received: by with SMTP id r20so45235772wiv.0 for <>; Thu, 22 Jan 2015 14:21:11 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:sender:from:to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=JxdCCP5wO5KFctjaJZtl5rE6CUsKlSHzgU2dIEhtCSE=; b=h+kyrZKgpjUsFJ7bpBCLBVMBbZImdtyAxNfY+eL+YBG3CxeWbabeg0PgodeDYYCN76 c0V4y1KZpFtrnzxgYFAdpUTGWra2FP2Eb/KHaHsKdb6Md7wscwEPRKKXiIXabkIhXC7E cw9o+RyFsms77jZsy3aBwJykE9pbUpxeQNCaYvcU73Q0Rfr4PgyjkxOiqyEyLYLOPSUR INWbmRj7vWAsnWCldGsbsicbQ++SWXDbckKrjWu0+hcs80fY0UerC4HPn/wuiHw/WzHn cRJkdT/90npmNAgomsTaUEK3uKlOMF4++7ZnbAxhp7NRQA4S6541yLboFd1Rn9cZY5cG nHIg==
X-Gm-Message-State: ALoCoQmR3lr6rmJgkdlYilJrKeq992fL8IJbRAh40aWhtOi4FcVFcYVHRg7gmjZDH39Y6xPlJmzh
X-Received: by with SMTP id gn7mr7796902wjc.30.1421965271426; Thu, 22 Jan 2015 14:21:11 -0800 (PST)
Received: from Serenity ( []) by with ESMTPSA id ei5sm4793179wid.2.2015. for <> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 22 Jan 2015 14:21:10 -0800 (PST)
Sender: Daniel King <>
X-Google-Original-Sender: "Daniel King" <>
From: "Daniel King" <>
To: <>
Date: Thu, 22 Jan 2015 22:21:06 -0000
Message-ID: <000b01d03691$b7d064b0$27712e10$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdA2jtlP4ArygwwpTIeSetmAX8OtqA==
Content-Language: en-gb
Archived-At: <>
Subject: Re: [OSPF] OSPF Topology Transparent Zone (TTZ) WG poll for adoption as experimental
X-Mailman-Version: 2.1.15
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: Thu, 22 Jan 2015 22:21:15 -0000

Hi All, 


Authors, really interested in seeing more results from your test networks,
things like:

- Scalability of TTZ (network sizes)
- Start-up time, average time to form relationships, etc.
- Impact from link failures and convergence time
- Operational findings/issues 

Your I-D contains already contains some high-level implementation details
(Good Job!), but I suggest you report your existing/future findings as per
RFC6982 (Improving Awareness of Running Code: The Implementation Status
Section). This would include some or all of the following information: 

- The organization responsible for the implementation, if any
- The implementation's name and/or a link to a web page describing the
- A brief/general description
- The implementation's level of maturity: research, prototype, alpha, beta,
production, widely used, etc.
- Coverage: which parts of the protocol specification are implemented and
which versions of the Internet-Draft were implemented.
- Licensing: the terms under which the implementation can be used. For
example: proprietary, royalty licensing, freely distributable with
acknowledgement (BSD style), freely distributable with requirement to
redistribute source (General Public License (GPL) style), and other
- Implementation experience: any useful information the implementers want to
share with the community
- Contact information: ideally a person's name and email address, but
possibly just a URL or mailing list

Finally, I would like to understand the applicability/impact when using
OSPF-TE. I guess this will be a separate document though.

BR, Dan. 

>We have discussed OSPF TTZ at several IETFs and the authors and their
>colleagues have even developed a working prototype. We believe there is
>consensus that the protocol mechanisms are viable. However, there is
>disagreement as to whether or not these mechanisms will provide
>significant benefit. The answer is definitely topology and deployment
>dependent. After some discussion, we have decided to poll for adoption as
>an experimental draft. Please indicate your support or opposition WG
>adoption as experimental prior to January 24th, 2015. 
>For your convenience, here is a URL for the draft:
>Acee and Abhay