[OSPF] FW: RFC 8099 on OSPF Topology-Transparent Zone

"Acee Lindem (acee)" <acee@cisco.com> Wed, 01 March 2017 12:40 UTC

Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 63F5F12946F for <ospf@ietfa.amsl.com>; Wed, 1 Mar 2017 04:40:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
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, 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, URIBL_BLOCKED=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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 0rOhZQ5Kq6wn for <ospf@ietfa.amsl.com>; Wed, 1 Mar 2017 04:40:24 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7102012952F for <ospf@ietf.org>; Wed, 1 Mar 2017 04:40:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2837; q=dns/txt; s=iport; t=1488372024; x=1489581624; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=PaEXNziCho1vIxfpUNnlGMlvVcYhqx51pRGkQF4lGWk=; b=kFqfgE+0xweRfx2smbB3vhbkmF5kXzYzzjbDrbt6vQTVZGtPl38SZpcJ Nzt/cvSpQnRiXcqXa7Wy3IOtucF7CHSB2aMT0J0AMYqR6e+++jB9Ofc4+ qZ4fp5NDa8UHKZCzzoX8DOJY4o0Cln38J529N7iPf2q4i2gK5zGRE4u/6 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.35,225,1484006400"; d="scan'208";a="212733045"
Received: from alln-core-11.cisco.com ([]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Mar 2017 12:40:23 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com []) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v21CeNqI016265 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ospf@ietf.org>; Wed, 1 Mar 2017 12:40:23 GMT
Received: from xch-rtp-015.cisco.com ( by XCH-RTP-014.cisco.com ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 1 Mar 2017 07:40:22 -0500
Received: from xch-rtp-015.cisco.com ([]) by XCH-RTP-015.cisco.com ([]) with mapi id 15.00.1210.000; Wed, 1 Mar 2017 07:40:22 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: OSPF WG List <ospf@ietf.org>
Thread-Topic: [OSPF] RFC 8099 on OSPF Topology-Transparent Zone
Thread-Index: AQHSkiqH33TjpKPLokWbPFxUL/y1HqF/7Z6A
Date: Wed, 01 Mar 2017 12:40:22 +0000
Message-ID: <D4DC2AA6.9FDB4%acee@cisco.com>
References: <20170301011841.6EC63B8210A@rfc-editor.org>
In-Reply-To: <20170301011841.6EC63B8210A@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-ID: <824A8770D95BD24BAE8B354C1C01F4D1@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/pHmDM33IiYKh4JoGHYFl0TRVcK8>
Subject: [OSPF] FW: RFC 8099 on OSPF Topology-Transparent Zone
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 01 Mar 2017 12:40:26 -0000

Congrats to Huaimo, Renwei, Alvaro, Yi, and Zhiheng on publication of this
innovative document.

On 2/28/17, 8:18 PM, "OSPF on behalf of rfc-editor@rfc-editor.org"
<ospf-bounces@ietf.org on behalf of rfc-editor@rfc-editor.org> wrote:

>A new Request for Comments is now available in online RFC libraries.
>        RFC 8099
>        Title:      OSPF Topology-Transparent Zone
>        Author:     H. Chen,
>                    R. Li,
>                    A. Retana,
>                    Y. Yang,
>                    Z. Liu
>        Status:     Experimental
>        Stream:     IETF
>        Date:       February 2017
>        Mailbox:    huaimo.chen@huawei.com,
>                    renwei.li@huawei.com,
>                    aretana@cisco.com,
>                    yyang1998@gmail.com,
>                    liu.cmri@gmail.com
>        Pages:      27
>        Characters: 60149
>        Updates/Obsoletes/SeeAlso:   None
>        I-D Tag:    draft-ietf-ospf-ttz-06.txt
>        URL:        https://www.rfc-editor.org/info/rfc8099
>        DOI:        10.17487/RFC8099
>This document presents a Topology-Transparent Zone (TTZ) in an OSPF
>area.  A TTZ comprises a group of routers and a number of links
>connecting these routers.  Any router outside of the zone is not
>aware of the zone.  A TTZ hides the internal topology of the TTZ from
>the outside.  It does not directly advertise any internal information
>about the TTZ to a router outside of the TTZ.  The information about
>the links and routers such as a link down inside the TTZ is not
>advertised to any router outside of the TTZ.
>This document is a product of the Open Shortest Path First IGP Working
>Group of the IETF.
>EXPERIMENTAL: This memo defines an Experimental Protocol for the
>Internet community.  It does not specify an Internet standard of any
>kind. Discussion and suggestions for improvement are requested.
>Distribution of this memo is unlimited.
>This announcement is sent to the IETF-Announce and rfc-dist lists.
>To subscribe or unsubscribe, see
>  https://www.ietf.org/mailman/listinfo/ietf-announce
>  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>For searching the RFC series, see https://www.rfc-editor.org/search
>For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>The RFC Editor Team
>Association Management Solutions, LLC
>OSPF mailing list