Protocol Action: 'TRILL Distributed Layer 3 Gateway' to Proposed Standard (draft-ietf-trill-irb-14.txt)

The IESG <> Thu, 07 July 2016 00:29 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 0463512B022; Wed, 6 Jul 2016 17:29:50 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Protocol Action: 'TRILL Distributed Layer 3 Gateway' to Proposed Standard (draft-ietf-trill-irb-14.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Wed, 06 Jul 2016 17:29:50 -0700
Archived-At: <>
Cc:,,, The IESG <>,,
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 Jul 2016 00:29:50 -0000

The IESG has approved the following document:
- 'TRILL Distributed Layer 3 Gateway'
  (draft-ietf-trill-irb-14.txt) as Proposed Standard

This document is the product of the Transparent Interconnection of Lots
of Links Working Group.

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah

A URL of this Internet Draft is:

Technical Summary

TRILL provides optimum routing for layer 2 traffic. A centralized
gateway solution is typically used for layer 3 inter-subnet traffic
forwarding in a TRILL campus but has the following issues:
   1. Sub-optimum forwarding paths for inter-subnet traffic.
   2. A centralized gateway may need to support a very large number of
      gateway interfaces in a data center, one per tenant per data
      label used by that tenant, to provide interconnect functionality
      for all the layer 2 virtual networks in a TRILL campus.
   3. A traffic bottleneck at the gateway.

This document specifies an optional TRILL distributed gateway solution
that resolves these centralized gateway issues.

Working Group Summary

   There has been good support from the working group to advance this
   work. There have been no changes in the concept or basic
   architecture since it was adopted as a WG draft.

   This document isn't strictly in the charter, but there was support and
   it is a useful idea.  I asked the IESG about a year ago, when I was consulted
   and read it, whether it was better to progress as an AD-sponsored draft or
   as a WG draft and there was agreement for it to go as a WG draft with the
   associated review.

Document Quality

   This document is of high quality. It has received numerous reviews
   including the RTG DIR QA review here:
   Implementations are planned by IPinfusion and Huawei.


   Document Shepherd:  Donald Eastlake
   Responsible Area Director:  Alia Atlas
  WG Chairs: Jon Hudson, Sue Hares