
From nobody Fri Sep  1 13:12:16 2017
Return-Path: <d3e3e3@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 928BE132FD9 for <trill@ietfa.amsl.com>; Fri,  1 Sep 2017 13:12:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.549
X-Spam-Level: 
X-Spam-Status: No, score=-0.549 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 uSDdmsP16Dvc for <trill@ietfa.amsl.com>; Fri,  1 Sep 2017 13:12:13 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77E9E13350F for <trill@ietf.org>; Fri,  1 Sep 2017 13:12:13 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id w10so10299922oie.1 for <trill@ietf.org>; Fri, 01 Sep 2017 13:12:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=f3Qi06KFrx3Ki0kwxLYB2WQW4LVoPchDQTMQV0iyzFc=; b=VwnilB89UrQH6WFCONQt+1yPQyrwIwFtpLYvmdBqTppaAlhHUhib3UMikCqgCdsCP2 vSEaR6W07HfeX4xz11D+eKlFV97YNbvD6QUy2KBie2QiACA5GbYvQZicqJy4REArgGi+ n4xYBC3z2GnE8BXClF7D1qgL1pEJuNEInY3dKg7BcUR+ywYyjqrolIQcrD86FD+m4BpJ 8rvtfhZL2uMeoKu2Gjg8G4P8EXxeiUd17rCOAT3X0WTkas8drPpHosZixApCrYFhQx9x 76NXHDaIsYatpupjbqE5wQiCbKFVZb3EyF9y3OuNOdTRTdLYAQwcQxONmxP+AN//T4zI mQhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=f3Qi06KFrx3Ki0kwxLYB2WQW4LVoPchDQTMQV0iyzFc=; b=EUsh6Rf74Q57K1gpNthr3AdGm0IqX9l0bTU8SQV8ojKYv01JxgygADn/eQtM1HNnY3 96qcbUXZO3HKKLNU8C0AnfHq0Sh652fj1yQRmWCtTSZeYxGaXyXXPu/p1KcMBfOL6P6U 9X5QN9LEN1BNuCJlIjeqBycCrZgxhWx3EZpAxidShHJF7AUJuxSqcnhiAHV/9qSojwAz iGKiyG8u1KdjzSGPzG9KKekyA0BteXnMxh9MO/VLKamMjBAJZQxzJBuwxVElYxGLcXJE R501szAR7DpdJuYzym723HLDDT57uuXuf2hGBoPYsfpszcRuDDFfKmTODtkKkWNLnxZF GuJA==
X-Gm-Message-State: AHPjjUhQgIu/DGKJ+eiLj2hzbVtJIpBkpSQBsHHKVSThfpqaUKY5Pyln mb/du6aACuFleEdOUUb4oc3IyEqp0rqkYio=
X-Google-Smtp-Source: ADKCNb54uCODBcOjs6+ybRRARbqYqxwmJMXXPFledgWhuo1gEvKjbOf/H817AYJ/zIVdoXOisjCe31uWlyMOsXUjTo8=
X-Received: by 10.202.81.200 with SMTP id f191mr2785710oib.172.1504296732446;  Fri, 01 Sep 2017 13:12:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.168.183.10 with HTTP; Fri, 1 Sep 2017 13:11:56 -0700 (PDT)
In-Reply-To: <150429576986.6399.10283142135323676448.idtracker@ietfa.amsl.com>
References: <150429576986.6399.10283142135323676448.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 1 Sep 2017 16:11:56 -0400
Message-ID: <CAF4+nEGFiQpDB-P0ftzAtJ0SNLW6N8RuEWyN5Jx8BKddPUWF=g@mail.gmail.com>
To: "trill@ietf.org" <trill@ietf.org>
Content-Type: multipart/alternative; boundary="001a113b065a5fd4230558266081"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/835kLkoEGZhT3awDGQ5W0Q5KyqY>
Subject: [trill] Fwd: New Version Notification for draft-eastlake-trill-vendor-channel-02.txt
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 20:12:15 -0000

--001a113b065a5fd4230558266081
Content-Type: text/plain; charset="UTF-8"

As per the presentation at the Berlin IETF meeting here
https://datatracker.ietf.org/meeting/99/materials/slides-99-trill-vendor-channel-protocol/
the vendor channel draft has been revived.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Fri, Sep 1, 2017 at 3:56 PM
Subject: New Version Notification for
draft-eastlake-trill-vendor-channel-02.txt
To: Hao Weiguo <haoweiguo@huawei.com>, Yizhou Li <liyizhou@huawei.com>,
Ayan Banerjee <ayabaner@cisco.com>, "Donald E. Eastlake" <d3e3e3@gmail.com>

A new version of I-D, draft-eastlake-trill-vendor-channel-02.txt
has been successfully submitted by Donald E. Eastlake and posted to the
IETF repository.

Name:           draft-eastlake-trill-vendor-channel
Revision:       02
Title:          TRILL: Vendor Specific TRILL Channel Protocol
Document date:  2017-09-01
Group:          Individual Submission
Pages:          14
URL:            https://www.ietf.org/internet-drafts/draft-eastlake-trill-
vendor-channel-02.txt
Status:         https://datatracker.ietf.org/doc/draft-eastlake-trill-
vendor-channel/
Htmlized:       https://tools.ietf.org/html/draft-eastlake-trill-vendor-
channel-02
Htmlized:       https://datatracker.ietf.org/doc/html/draft-eastlake-trill-
vendor-channel-02
Diff:           https://www.ietf.org/rfcdiff?url2=draft-eastlake-trill-
vendor-channel-02

Abstract:
   The IETF TRILL (TRansparent Interconnection of Lots of Links)
   protocol is implemented by devices called TRILL switches or RBridges
   (Routing Bridges). TRILL includes a general mechanism, called RBridge
   Channel, for the transmission of typed messages between RBridges in
   the same campus and between RBridges and end stations on the same
   link. This document specifies a method to send vendor specific
   messages over the RBridge Channel facility.






Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--001a113b065a5fd4230558266081
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">As per the presentation at the Berlin IETF meeting here<di=
v><a href=3D"https://datatracker.ietf.org/meeting/99/materials/slides-99-tr=
ill-vendor-channel-protocol/">https://datatracker.ietf.org/meeting/99/mater=
ials/slides-99-trill-vendor-channel-protocol/</a></div><div>the vendor chan=
nel draft has been revived.</div><div><br clear=3D"all"><div><div class=3D"=
gmail_signature">Thanks,<br>Donald<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=C2=A0Donald E=
. Eastlake 3rd =C2=A0 +1-508-333-2270 (cell)<br>=C2=A0155 Beaver Street, Mi=
lford, MA 01757 USA<br>=C2=A0<a href=3D"mailto:d3e3e3@gmail.com" target=3D"=
_blank">d3e3e3@gmail.com</a></div></div>
<br><div class=3D"gmail_quote">---------- Forwarded message ----------<br>F=
rom: <b class=3D"gmail_sendername"></b> <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>&gt;</span><br>D=
ate: Fri, Sep 1, 2017 at 3:56 PM<br>Subject: New Version Notification for d=
raft-eastlake-trill-vendor-channel-02.txt<br>To: Hao Weiguo &lt;<a href=3D"=
mailto:haoweiguo@huawei.com">haoweiguo@huawei.com</a>&gt;, Yizhou Li &lt;<a=
 href=3D"mailto:liyizhou@huawei.com">liyizhou@huawei.com</a>&gt;, Ayan Bane=
rjee &lt;<a href=3D"mailto:ayabaner@cisco.com">ayabaner@cisco.com</a>&gt;, =
&quot;Donald E. Eastlake&quot; &lt;<a href=3D"mailto:d3e3e3@gmail.com">d3e3=
e3@gmail.com</a>&gt;<br><br>
A new version of I-D, draft-eastlake-trill-vendor-<wbr>channel-02.txt<br>
has been successfully submitted by Donald E. Eastlake and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-eastlake-trill-vendor-<=
wbr>channel<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A002<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 TRILL: Vendor Specific TRILL Chann=
el Protocol<br>
Document date:=C2=A0 2017-09-01<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 14<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-eastlake-trill-vendor-channel-02.txt" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/internet-<wbr>drafts/draft-ea=
stlake-trill-<wbr>vendor-channel-02.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-eastlake-trill-vendor-channel/" rel=3D"noreferrer" target=
=3D"_blank">https://datatracker.ietf.org/<wbr>doc/draft-eastlake-trill-<wbr=
>vendor-channel/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-eastlake-trill-vendor-channel-02" rel=3D"noreferrer" target=3D"_blank=
">https://tools.ietf.org/html/<wbr>draft-eastlake-trill-vendor-<wbr>channel=
-02</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org=
/doc/html/draft-eastlake-trill-vendor-channel-02" rel=3D"noreferrer" target=
=3D"_blank">https://datatracker.ietf.org/<wbr>doc/html/draft-eastlake-trill=
-<wbr>vendor-channel-02</a><br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.o=
rg/rfcdiff?url2=3Ddraft-eastlake-trill-vendor-channel-02" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/rfcdiff?<wbr>url2=3Ddraft-eastlake=
-trill-<wbr>vendor-channel-02</a><br>
<br>
Abstract:<br>
=C2=A0 =C2=A0The IETF TRILL (TRansparent Interconnection of Lots of Links)<=
br>
=C2=A0 =C2=A0protocol is implemented by devices called TRILL switches or RB=
ridges<br>
=C2=A0 =C2=A0(Routing Bridges). TRILL includes a general mechanism, called =
RBridge<br>
=C2=A0 =C2=A0Channel, for the transmission of typed messages between RBridg=
es in<br>
=C2=A0 =C2=A0the same campus and between RBridges and end stations on the s=
ame<br>
=C2=A0 =C2=A0link. This document specifies a method to send vendor specific=
<br>
=C2=A0 =C2=A0messages over the RBridge Channel facility.<br>
<br>
<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div><br></div></div>

--001a113b065a5fd4230558266081--


From nobody Sun Sep 10 20:03:04 2017
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 165A2132CE9; Sun, 10 Sep 2017 20:02:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 tPH3GSQYA2kO; Sun, 10 Sep 2017 20:02:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AE00128D0F; Sun, 10 Sep 2017 20:02:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 91C10B80118; Sun, 10 Sep 2017 20:02:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, trill@ietf.org
Message-Id: <20170911030236.91C10B80118@rfc-editor.org>
Date: Sun, 10 Sep 2017 20:02:36 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/4f3WRV-IIwrUJr2iIZWKuqNMuFU>
Subject: [trill] RFC 8243 on Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 03:02:58 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8243

        Title:      Alternatives for Multilevel Transparent Interconnection 
                    of Lots of Links (TRILL) 
        Author:     R. Perlman, 
                    D. Eastlake 3rd,
                    M. Zhang,
                    A. Ghanwani,
                    H. Zhai
        Status:     Informational
        Stream:     IETF
        Date:       September 2017
        Mailbox:    radia@alum.mit.edu, 
                    d3e3e3@gmail.com, 
                    zhangmingui@huawei.com,
                    anoop@alumni.duke.edu, 
                    honjun.zhai@tom.com
        Pages:      29
        Characters: 66920
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-trill-rbridge-multilevel-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8243

        DOI:        10.17487/RFC8243

Although TRILL is based on IS-IS, which supports multilevel unicast
routing, extending TRILL to multiple levels has challenges that are
not addressed by the already-existing capabilities of IS-IS.  One
issue is with the handling of multi-destination packet distribution
trees.  Other issues are with TRILL switch nicknames.  How are such
nicknames allocated across a multilevel TRILL network?  Do nicknames
need to be unique across an entire multilevel TRILL network?  Or can
they merely be unique within each multilevel area?

This informational document enumerates and examines alternatives
based on a number of factors including backward compatibility,
simplicity, and scalability; it makes recommendations in some cases.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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



From nobody Fri Sep 22 06:19:03 2017
Return-Path: <ekr@rtfm.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C83134330 for <trill@ietfa.amsl.com>; Fri, 22 Sep 2017 06:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 twPg8Oua2EDR for <trill@ietfa.amsl.com>; Fri, 22 Sep 2017 06:18:58 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABD0F1329F9 for <trill@ietf.org>; Fri, 22 Sep 2017 06:18:57 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id u11so712864ywh.7 for <trill@ietf.org>; Fri, 22 Sep 2017 06:18:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=a4jGxy4HBOpTU1Qfg+Svcmyb5qDq1WXsOxCm9bJbP8Q=; b=cTYHLKW9duQ/g/pCxJ8S3yZ+rpMN2A4u5rTDYE319crKtRIveGr1SQk+Uwi78q/byy GWndjwkoJNPnvwCSiBcmbxfu/q4cAxErM5RJxZSU8JmdRemxgCU9jlo8wTPG9e9ZHS3J V9clyWRCRbmtWNR0mNcrUKC6X/yFrbvVGoyx1Hnoekg8Nz9CCr9AyOILasjszgYZimtU w0ye/LW2n1GHo/JEtWzRlx0WUropex5EhgR0gdC3CkMg9gaKEHJ3Lqjwjp2VM0INGl3/ LzpGAL6Bsem+gIO7TyFUjEdYqiHkGaWN56vKIEJU59bTQcIuSxj57hRS5tK86qK/GMRg RBHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=a4jGxy4HBOpTU1Qfg+Svcmyb5qDq1WXsOxCm9bJbP8Q=; b=Ew71j+aLqIoRuWqXEzFusnIMjSeuz5VqlZ7OZ+PmpzbH3U7B+b5L71KUSqWaTT4zgg fu/Oj8ol/frQ++fAcgdhPFSEQE+3HSbEXXBLHZSs5joBf186ELIOEV24yXVWoWpEmz4D wNcST3tufkHXlMPQv6cmIgTi65bRPlFyF6PFDw72Awon6iQFXolrQm1k1J5o3Nzv8Yog kAeiyJcGT1N2JnfbDm46lD1CGZN3oXTmT+y9mnH9gWKrdcJ6k3T4z+x38l62Op+SDhI0 sv5sOc7dNfQqFlCGyCV4zp+jmqYu/9hXJ0jIKVxNQkqzlq3zmNxQyBEY+dTdjWNAJWrM Izog==
X-Gm-Message-State: AHPjjUiV2xsoIUAH0hIJCEoB5zqwxp2qmjpyQFI1XYzwqfRU5VdJ1RW+ Xk09ittXSt5Hu4eDEaYiIfaaP/TyDoQOgdc5/rzBsXtc
X-Google-Smtp-Source: AOwi7QCMHEcKqCl6HlJsXrtR20JbZdgZZssH4wE0aw9kfett3nf/WUeI8FgiPzwWjkYdSDdDSX9kE0m/Lejr8uScPoo=
X-Received: by 10.37.170.203 with SMTP id t69mr3627618ybi.99.1506086336831; Fri, 22 Sep 2017 06:18:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.75.17 with HTTP; Fri, 22 Sep 2017 06:18:16 -0700 (PDT)
In-Reply-To: <CAF4+nEFVzrv0OvV13qqON9SRQZQj63ZaegtHbs9fp21Zo5Lusw@mail.gmail.com>
References: <149925473455.19397.5891341140635090367.idtracker@ietfa.amsl.com> <CAF4+nEFVzrv0OvV13qqON9SRQZQj63ZaegtHbs9fp21Zo5Lusw@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 22 Sep 2017 06:18:16 -0700
Message-ID: <CABcZeBMay2x7mEB8gNv_w3bRM3mHuqWv-FR110A7-HGBHtrH=g@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-trill-arp-optimization@ietf.org,  "trill-chairs@ietf.org" <trill-chairs@ietf.org>, Susan Hares <skh@ndzh.com>, "trill@ietf.org" <trill@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c056e901bbc290559c70dd1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/oTj_2i_K51CTi7nwT77XTPfQJgs>
Subject: Re: [trill] Eric Rescorla's Discuss on draft-ietf-trill-arp-optimization-08: (with DISCUSS and COMMENT)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 13:19:01 -0000

--94eb2c056e901bbc290559c70dd1
Content-Type: text/plain; charset="UTF-8"

On Wed, Aug 23, 2017 at 12:38 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> Hi Eric,
>
> On Wed, Jul 5, 2017 at 7:38 AM, Eric Rescorla <ekr@rtfm.com> wrote:
> > Eric Rescorla has entered the following ballot position for
> > draft-ietf-trill-arp-optimization-08: Discuss
> >
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
>
> As a general comment, the Security Consideration section could use
> clarification and some expansion.
>
> Although one can imagine various mixed modes, to the first approximation
> there are two ways of doing the optimization of various multi-destination
> messages discussed in this document:
>
>    - Using data plane learning by observing ARP/ND and similar messages
>    (in addition to the learning of MAC addresses from the data plane which is
>    enabled by default in TRILL). As described in this document, such data
>    plane learning by TRILL switches can be used to sometimes optimize
>    ARP/ND/RARP/unknown-destination messages. But the result isn't
>    particularly more or less secure than it is when this data plane learning
>    is done by end stations rather than by TRILL switches (or bridges or other
>    kinds of switches) in the middle doing some optimization of the relevant
>    multi-destination messages. Interface address information learned through
>    data plane learning by edge TRILL switches can also be propagated via the
>    control plane but this is not significantly different from propagating that
>    information via the multi-destination messages that are being optimized to
>    unicast or optimized away.
>    - Using a complete, trusted directory as might be based on an
>    orchestration system in a data center. Since the messages between TRILL
>    switches doing ARP/ND/RARP/unknown-destination optimization can be
>    secured and the TRILL switches can be configured to ignore data plane
>    learning, this enables TRILL switches to provide answers that are "correct"
>    in that they correspond to the data in this complete, trusted directory.
>    However, there can still be various forged messages/addresses on a local
>    link between end station(s) and edge TRILL switches. Such a local link can,
>    with TRILL, be a bridged LAN, so such forgeries emitted by an end station
>    may be seen by other end stations and cause incorrect learning from the
>    data plane.
>
> The existing Security Considerations section is a bit sketchy and
> concentrates more on the data plane case, as that is the one with the
> greatest security challenges.
>

Yes, this seems like a reasonable assessment. Alia, does someone have the
action item to make it less sketchy?


> It's not clear to me how the security properties of this mechanism
> > compare to existing TRILL. The text says:
> >
> >    Unless Secure ND (SEND [RFC3971]) is used, ARP and ND messages can be
> >    easily forged. Therefore the learning of MAC/IP addresses by RBridges
> >    from ARP/ND should not be considered as reliable. See Section 4.1 for
> >    SEND Considerations.
> >
> > "not considered as reliable" seems suboptimal. You need to cover how
> > this mechanism compares to the non-use of this mechanism.
>
> As above, the optimization mechanisms do not make any significant
> difference to the inherent insecurities of data plane learning but when
> used with a complete, trusted directory, it improves considerably over data
> plane learning..
>

That had kind of been my impression, but then I don't understand what "not
considered as reliable" is doing here. I'm supposed to be doing something
with it, so while it may be non-secure, I'm still relying on it, no?



> This document seems very sketchy on what you do when you get duplicate
> > IPs.
>
> Why should what you do when you notice a duplicate IP address be
> significantly different just because some multi-destination messages are
> being optimized? Why shouldn't you just do whatever you do now and why is
> that any of TRILL's business?
>

Because you're getting the information via different vector, TRILL needs to
specify what you do,
if only to say "do what you would do otherwise".

>
>
> >    In the case where the former owner replies, a Duplicate Address has
> >    been detected. In this case the querying RBridge SHOULD log the
> >    duplicate so that the network administrator can take appropriate
> >    action.
> >
> > How does logging solve the problem?
>
> It doesn't but it seems better than not logging.
>
> > What do you reply to ARPs with and/or propagate to other nodes?
>
> If you are asking how you reply to ARPs if the IP address being ARPed for
> has been found to be duplicated, there are the two cases outlined above. If
> you are using a complete, trusted directory, you give the presumed correct
> answer provided by that directory. If you are using data plane learning,
> you use whatever you last learned from the data plane (which could have
> been a forgery over writing good information or good information over
> writing a forgery or a forgery overwriting a different forgery or ...).
>
> > Do you tell the originator of the advertisement you have a duplicate?
>
> As far as I know there is no standardized way to tell a station that you
> think it has an IP address that is duplicated locally and I don't think it
> is the job of TRILL to provide such a mechanism. Certainly this document
> does not propose anything of that sort.
>

OK.



>    When a newly connected end-station exchanges messages with a DHCP
> >    [RFC2131] server an edge RBridge should snoop them (mainly the
> >    DHCPAck message) and store IP/MAC mapping information in its ARP/ND
> >    cache and should also send the information out through the TRILL
> >    control plane using ESADI.
> >
> > What happens if the attacker sets up a fake DHCP server and pretends
> > to assign addresses to himself? It seems like maybe that's the same
> > as fake ARPs but maybe not.
>
> This snooping on DHCP messages only applies to the data plane learning
> case. In the case of a complete, trusted directory, edge RBridges already
> know the right answer, so to speak. With data plane learning, if there are
> forged DHCP messages, things are likely to get all screwed up. Of course,
> you could run DHCP over IPsec but, partly due to the localized nature of
> DHCP, I don't think very many people do that. There is also RFC 3118 which
> can be used to authenticate DHCP messages, but that assumes the
> distribution of keying information.
>
> There isn't much difference between the various multi-destination messages
> (ARP / DHCP) advertising the addresses and point of attachment of
> interfaces. But, overall, I'm not sure why a document that is just
> describing ways to optimize the distribution of various multi-destination
> messages needs to analyze the security of the protocols implemented by
> those multi-destination when, as in the data plane learning case, it is not
> significantly changing that security.
>

Well, in this case, you have a new threat vector: DHCP. Even if it is the
same kind of threats, it's still a new threat vector.
More generally documents need to contain complete security considerations
sections. If the security considerations
are the same as with some other document, then they need to say that.



> > In general, the security considerations need a complete threat
> > analysis per 3552.
>
> I don't think there is that much new in this document. While the Security
> Considerations section needs clarification and some expansion, I don't
> think it is, for example, the job of this document to do a threat analysis
> of the ARP protocol as long as it can make a reasonable case that the
> security of ARP is not significantly changed by the optimizations specified.
>

Sure, but it also doesn't make that case.


> ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
>
> For completeness, I've cut and pasted below the COMMENT responses I sent
> to you a while ago.
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 <(508)%20333-2270> (cell)
>  155 Beaver Street, Milford, MA 01757 USA
> <https://maps.google.com/?q=155+Beaver+Street,+Milford,+MA+01757+USA&entry=gmail&source=g>
>  d3e3e3@gmail.com
>
> > S 2.
> >
> >    plane on the edge RBridges, it should be possible to completely
> >    suppress flooding of ARP/ND messages in a TRILL Campus, When all end-
> >    station MAC addresses are similarly known, it should be possible to
> >    suppress unknown unicast flooding by dropping any unknown unicast
> >    received at an edge RBridge.
> >
> > Are these "should be possibles" normative? Descriptive?
>
> Section 2 of this document is a general discussion of the optimization
> problem which, while it does mention a couple of possible facets of
> potential solutions, is not intended to be normative.
>
>
> > S 4.
> > This is a sequence of steps, so it would be nice to preface them with
> > a list of the steps. It's also odd to have SEND considerations right
> > in the middle here.
>
> Sorry, I don't understand exactly what you are pointing at as a
> sequence of steps. All of Section 4? Just the text between the Section
> 4 heading and the Section 4.1 heading? Something else?
>

Sorry, my point is that if I read this correctly, I do 4.3, then 4.4, etc.
It would be nice if they were listed ahead of this as "this is what you do,
now read the sections"


> > 4.3 Get Sender's IP/MAC Mapping Information for Non-zero IP
> >
> > Please explain what a non-zero IP is and why it's relevant.
> > This graf also needs an introductory sentence or something before
> > the bullets.
>
> Here is a copy of the response that was sent to a similar comment in
> Dale Worley's GENART review:
>
> This section is talking about getting and handling the IP/MAC
> mapping information for a local end station by an edge RBridge. An
> ARP/ND from such a local end station might show a zero source IP
> address if the end station does not have one or is probing for
> duplicates.
>
> Perhaps the title for the Section should be something like
>
>    4.3 Extracting Local End Station IP/MAC Mapping Information
>
> and a new first paragraph could be added something like
>
>    Edge RBridges extract and use information about the correspondence
> between local end station IP and MAC addresses from the ARP/ND
> messages those end stations send as described below. An apparent zero
> source IP address means that the end station is probing for duplicate
> IP addresses and messages with such a zero source IP address are not
> used for the extraction of IP/MAC address mapping information
>

LGTM


>
> > S 4.4.
> >    It is not essential that all RBridges use the same strategy for which
> >    option to select for a particular ARP/ND query. It is up to the
> >    implementation.
> >
> > This seems inconsistent with the MUST in arm (b) below, because I
> > can just take some other arm. It's also kind of surprising to be this
> > non-prescriptive.
>
> The wording needs to be clarified. Which lettered item listed below
> applies is determined by the circumstances; however, which of the
> numbered strategies associated with these items is followed is an
> implementation choice in handeling any particular ARP/ND.
>

OK.

>
> > S 8.
> >    some other location (MAC/VM Mobility) and gets connected to egde-
> >
> > Nit: edge is mispelled.
>
> OK.
>

--94eb2c056e901bbc290559c70dd1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Aug 23, 2017 at 12:38 PM, Donald Eastlake <span dir=3D"ltr">&lt=
;<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.com</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hi Er=
ic,<span class=3D""><br><br>On Wed, Jul 5, 2017 at 7:38 AM, Eric Rescorla &=
lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; w=
rote:<br></span><span class=3D"">&gt; Eric Rescorla has entered the followi=
ng ballot position for<br>&gt; draft-ietf-trill-arp-<wbr>optimization-08: D=
iscuss<br>&gt;<br></span>&gt; ------------------------------<wbr>----------=
--------------------<wbr>----------<br>&gt; DISCUSS:<br>&gt; --------------=
----------------<wbr>------------------------------<wbr>----------<br><br>A=
s a general comment, the Security Consideration section could use clarifica=
tion and some expansion.<div><br></div><div>Although one can imagine variou=
s mixed modes, to the first approximation there are two ways of doing the o=
ptimization of various multi-destination messages discussed in this documen=
t:<br><ul><li>Using data plane learning by observing ARP/ND and similar mes=
sages (in addition to the learning of MAC addresses from the data plane whi=
ch is enabled by default in TRILL). As described in this document, such dat=
a plane learning by TRILL switches can be used to sometimes optimize ARP/ND=
/RARP/unknown-<wbr>destination messages. But the result isn&#39;t particula=
rly more or less secure than it is when this data plane learning is done by=
 end stations rather than by TRILL switches (or bridges or other kinds of s=
witches) in the middle doing some optimization of the relevant multi-destin=
ation messages. Interface address information learned through data plane le=
arning by edge TRILL switches can also be propagated via the control plane =
but this is not significantly different from propagating that information v=
ia the multi-destination messages that are being optimized to unicast or op=
timized away.<br></li><li>Using a complete, trusted directory as might be b=
ased on an orchestration system in a data center. Since the messages betwee=
n TRILL switches doing ARP/ND/RARP/unknown-<wbr>destination optimization ca=
n be secured and the TRILL switches can be configured to ignore data plane =
learning, this enables TRILL switches to provide answers that are &quot;cor=
rect&quot; in that they correspond to the data in this complete, trusted di=
rectory. However, there can still be various forged messages/addresses on a=
 local link between end station(s) and edge TRILL switches. Such a local li=
nk can, with TRILL, be a bridged LAN, so such forgeries emitted by an end s=
tation may be seen by other end stations and cause incorrect learning from =
the data plane.<br></li></ul>The existing Security Considerations section i=
s a bit sketchy and concentrates more on the data plane case, as that is th=
e one with the greatest security challenges.</div></div></blockquote><div><=
br></div><div>Yes, this seems like a reasonable assessment. Alia, does some=
one have the action item to make it less sketchy?</div><div><br></div><div>=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><span c=
lass=3D"">&gt; It&#39;s not clear to me how the security properties of this=
 mechanism<br>&gt; compare to existing TRILL. The text says:<br>&gt;<br>&gt=
; =C2=A0 =C2=A0Unless Secure ND (SEND [RFC3971]) is used, ARP and ND messag=
es can be<br>&gt; =C2=A0 =C2=A0easily forged. Therefore the learning of MAC=
/IP addresses by RBridges<br>&gt; =C2=A0 =C2=A0from ARP/ND should not be co=
nsidered as reliable. See Section 4.1 for<br>&gt; =C2=A0 =C2=A0SEND Conside=
rations.<br>&gt;<br>&gt; &quot;not considered as reliable&quot; seems subop=
timal. You need to cover how<br>&gt; this mechanism compares to the non-use=
 of this mechanism.<br><br></span>As above, the optimization mechanisms do =
not make any significant difference to the inherent insecurities of data pl=
ane learning but when used with a complete, trusted directory, it improves =
considerably over data plane learning..</div></div></div></blockquote><div>=
<br></div><div>That had kind of been my impression, but then I don&#39;t un=
derstand what &quot;not considered as reliable&quot; is doing here. I&#39;m=
 supposed to be doing something with it, so while it may be non-secure, I&#=
39;m still relying on it, no?</div><div><br></div><div><br></div><div><br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><span class=
=3D"">&gt; This document seems very sketchy on what you do when you get dup=
licate<br>&gt; IPs.<br><br></span>Why should what you do when you notice a =
duplicate IP address be significantly different just because some multi-des=
tination messages are being optimized? Why shouldn&#39;t you just do whatev=
er you do now and why is that any of TRILL&#39;s business?</div></div></div=
></blockquote><div><br></div><div>Because you&#39;re getting the informatio=
n via different vector, TRILL needs to specify what you do,</div><div>if on=
ly to say &quot;do what you would do otherwise&quot;.=C2=A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><div dir=3D"ltr"><div><div><span class=3D""><br><br>&g=
t; =C2=A0 =C2=A0In the case where the former owner replies, a Duplicate Add=
ress has<br>&gt; =C2=A0 =C2=A0been detected. In this case the querying RBri=
dge SHOULD log the<br>&gt; =C2=A0 =C2=A0duplicate so that the network admin=
istrator can take appropriate<br>&gt; =C2=A0 =C2=A0action.<br>&gt;<br>&gt; =
How does logging solve the problem?</span></div><div><br></div><div>It does=
n&#39;t but it seems better than not logging.</div><span class=3D""><div><b=
r></div><div>&gt; What do you reply to ARPs with=C2=A0and/or propagate to o=
ther nodes?</div><div><br></div></span><div>If you are asking how you reply=
 to ARPs if the IP address being ARPed for has been found to be duplicated,=
 there are the two cases outlined above. If you are using a complete, trust=
ed directory, you give the presumed correct answer provided by that directo=
ry. If you are using data plane learning, you use whatever you last learned=
 from the data plane (which could have been a forgery over writing good inf=
ormation or good information over writing a forgery or a forgery overwritin=
g a different forgery or ...).</div><div><br></div><div><span class=3D"">&g=
t; Do you tell the originator of the=C2=A0advertisement you have a duplicat=
e?<br><br></span>As far as I know there is no standardized way to tell a st=
ation that you think it has an IP address that is duplicated locally and I =
don&#39;t think it is the job of TRILL to provide such a mechanism. Certain=
ly this document does not propose anything of that sort.</div></div></div><=
/blockquote><div><br></div><div>OK.</div><div><br></div><div><br></div><div=
><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><span =
class=3D"">&gt; =C2=A0 =C2=A0When a newly connected end-station exchanges m=
essages with a DHCP<br>&gt; =C2=A0 =C2=A0[RFC2131] server an edge RBridge s=
hould snoop them (mainly the<br>&gt; =C2=A0 =C2=A0DHCPAck message) and stor=
e IP/MAC mapping information in its ARP/ND<br>&gt; =C2=A0 =C2=A0cache and s=
hould also send the information out through the TRILL<br>&gt; =C2=A0 =C2=A0=
control plane using ESADI.<br>&gt;<br>&gt; What happens if the attacker set=
s up a fake DHCP server and pretends<br>&gt; to assign addresses to himself=
? It seems like maybe that&#39;s the same<br>&gt; as fake ARPs but maybe no=
t.<br><br></span>This snooping on DHCP messages only applies to the data pl=
ane learning case. In the case of a complete, trusted directory, edge RBrid=
ges already know the right answer, so to speak. With data plane learning, i=
f there are forged DHCP messages, things are likely to get all screwed up. =
Of course, you could run DHCP over IPsec but, partly due to the localized n=
ature of DHCP, I don&#39;t think very many people do that. There is also RF=
C 3118 which can be used to authenticate DHCP messages, but that assumes th=
e distribution of keying information.</div><div><br></div><div>There isn&#3=
9;t much difference between the various multi-destination messages (ARP / D=
HCP) advertising the addresses and point of attachment of interfaces. But, =
overall, I&#39;m not sure why a document that is just describing ways to op=
timize the distribution of various multi-destination messages needs to anal=
yze the security of the protocols implemented by those multi-destination wh=
en, as in the data plane learning case, it is not significantly changing th=
at security.</div></div></div></blockquote><div><br></div><div>Well, in thi=
s case, you have a new threat vector: DHCP. Even if it is the same kind of =
threats, it&#39;s still a new threat vector.</div><div>More generally docum=
ents need to contain complete security considerations sections. If the secu=
rity considerations</div><div>are the same as with some other document, the=
n they need to say that.</div><div><br></div><div><br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><div dir=3D"ltr"><div><div><span class=3D""><br>&gt; In gen=
eral, the security considerations need a complete threat<br>&gt; analysis p=
er 3552.<br><br></span>I don&#39;t think there is that much new in this doc=
ument. While the Security Considerations section needs clarification and so=
me expansion, I don&#39;t think it is, for example, the job of this documen=
t to do a threat analysis of the ARP protocol as long as it can make a reas=
onable case that the security of ARP is not significantly changed by the op=
timizations specified.<br></div></div></div></blockquote><div><br></div><di=
v>Sure, but it also doesn&#39;t make that case.</div><div><br></div><div><b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div>&gt; ----=
--------------------------<wbr>------------------------------<wbr>---------=
-<br>&gt; COMMENT:<br>&gt; ------------------------------<wbr>-------------=
-----------------<wbr>----------<br><br>For completeness, I&#39;ve cut and =
pasted below the COMMENT responses I sent to you a while ago.<span class=3D=
""><br><br>Thanks,<br>Donald<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D<br>=C2=A0Donald E.=
 Eastlake 3rd =C2=A0 <a href=3D"tel:(508)%20333-2270" value=3D"+15083332270=
" target=3D"_blank">+1-508-333-2270</a> (cell)<br>=C2=A0<a href=3D"https://=
maps.google.com/?q=3D155+Beaver+Street,+Milford,+MA+01757+USA&amp;entry=3Dg=
mail&amp;source=3Dg">155 Beaver Street, Milford, MA 01757 USA</a><br>=C2=A0=
<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.com</a><=
br><br></span><span class=3D"">&gt; S 2.<br>&gt;<br>&gt; =C2=A0 =C2=A0plane=
 on the edge RBridges, it should be possible to completely<br>&gt; =C2=A0 =
=C2=A0suppress flooding of ARP/ND messages in a TRILL Campus, When all end-=
<br>&gt; =C2=A0 =C2=A0station MAC addresses are similarly known, it should =
be possible to<br>&gt; =C2=A0 =C2=A0suppress unknown unicast flooding by dr=
opping any unknown unicast<br>&gt; =C2=A0 =C2=A0received at an edge RBridge=
.<br>&gt;<br>&gt; Are these &quot;should be possibles&quot; normative? Desc=
riptive?<br><br></span><span class=3D"">Section 2 of this document is a gen=
eral discussion of the optimization<br></span>problem which, while it does =
mention a couple of possible facets of<span class=3D""><br>potential soluti=
ons, is not intended to be normative.<br><br><br></span><span class=3D"">&g=
t; S 4.<br>&gt; This is a sequence of steps, so it would be nice to preface=
 them with<br>&gt; a list of the steps. It&#39;s also odd to have SEND cons=
iderations right<br>&gt; in the middle here.<br><br></span><span class=3D""=
>Sorry, I don&#39;t understand exactly what you are pointing at as a<br>seq=
uence of steps. All of Section 4? Just the text between the Section<br>4 he=
ading and the Section 4.1 heading? Something else?<br></span></div></div></=
div></blockquote><div><br></div><div>Sorry, my point is that if I read this=
 correctly, I do 4.3, then 4.4, etc.</div><div>It would be nice if they wer=
e listed ahead of this as &quot;this is what you do,</div><div>now read the=
 sections&quot;</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div d=
ir=3D"ltr"><div><div><span class=3D""></span><span class=3D"">&gt; 4.3 Get =
Sender&#39;s IP/MAC Mapping Information for Non-zero IP<br>&gt;<br>&gt; Ple=
ase explain what a non-zero IP is and why it&#39;s relevant.<br>&gt; This g=
raf also needs an introductory sentence or something before<br>&gt; the bul=
lets.<br><br></span><span class=3D"">Here is a copy of the response that wa=
s sent to a similar comment in<br>Dale Worley&#39;s GENART review:<br><br>T=
his section is talking about getting and handling the IP/MAC<br>mapping inf=
ormation for a local end station by an edge RBridge. An<br>ARP/ND from such=
 a local end station might show a zero source IP<br>address if the end stat=
ion does not have one or is probing for<br>duplicates.<br><br>Perhaps the t=
itle for the Section should be something like<br><br>=C2=A0 =C2=A04.3 Extra=
cting Local End Station IP/MAC Mapping Information<br><br>and a new first p=
aragraph could be added something like<br><br>=C2=A0 =C2=A0Edge RBridges ex=
tract and use information about the correspondence<br>between local end sta=
tion IP and MAC addresses from the ARP/ND<br>messages those end stations se=
nd as described below. An apparent zero<br>source IP address means that the=
 end station is probing for duplicate<br>IP addresses and messages with suc=
h a zero source IP address are not<br>used for the extraction of IP/MAC add=
ress mapping information<br></span></div></div></div></blockquote><div><br>=
</div><div>LGTM</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div d=
ir=3D"ltr"><div><div><span class=3D""><br></span><span class=3D"">&gt; S 4.=
4.<br>&gt; =C2=A0 =C2=A0It is not essential that all RBridges use the same =
strategy for which<br>&gt; =C2=A0 =C2=A0option to select for a particular A=
RP/ND query. It is up to the<br>&gt; =C2=A0 =C2=A0implementation.<br>&gt;<b=
r>&gt; This seems inconsistent with the MUST in arm (b) below, because I<br=
>&gt; can just take some other arm. It&#39;s also kind of surprising to be =
this<br>&gt; non-prescriptive.<br><br></span><span class=3D"">The wording n=
eeds to be clarified. Which lettered item listed below<br>applies is determ=
ined by the circumstances; however, which of the<br>numbered strategies ass=
ociated with these items is followed is an<br>implementation choice in hand=
eling any particular ARP/ND.<br></span></div></div></div></blockquote><div>=
<br></div><div>OK.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"lt=
r"><div><div><span class=3D""><br></span><span class=3D"">&gt; S 8.<br>&gt;=
 =C2=A0 =C2=A0some other location (MAC/VM Mobility) and gets connected to e=
gde-<br>&gt;<br>&gt; Nit: edge is mispelled.<br><br></span>OK.</div></div><=
/div>
</blockquote></div><br></div></div>

--94eb2c056e901bbc290559c70dd1--


From nobody Wed Sep 27 06:47:06 2017
Return-Path: <shares@ndzh.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37FD21330B0 for <trill@ietfa.amsl.com>; Wed, 27 Sep 2017 06:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.646
X-Spam-Level: ***
X-Spam-Status: No, score=3.646 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no autolearn_force=no
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 AveLyqbhppx6 for <trill@ietfa.amsl.com>; Wed, 27 Sep 2017 06:46:58 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8E4C1331DD for <trill@ietf.org>; Wed, 27 Sep 2017 06:46:58 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=184.157.84.200; 
From: "Susan Hares" <shares@ndzh.com>
To: <trill@ietf.org>
Cc: "'Jon Hudson'" <jon.hudson@gmail.com>, "'Donald Eastlake'" <d3e3e3@gmail.com>
Date: Wed, 27 Sep 2017 09:46:46 -0400
Message-ID: <029201d33797$100ec870$302c5950$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0293_01D33775.88FD9DA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdM3ltsKZn0e2l/KSRmP/uHcV/n8gg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/Bng-QAqdNQ3XbBjCqZQyt7lhgtI>
Subject: [trill] draft-eastlake-trill-group-keying - has been adopted
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 13:47:04 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0293_01D33775.88FD9DA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The draft draft-eastlake-trill-group-keying has been adopted.  The authors
should submit this draft as:

Draft-ietf-trill-group-keying-00.txt. 

 

The authors should remember that we quickly need to move to WG last call on
this draft.  I will ping you again in 2 weeks to see if you are ready for WG
LC. 

 

Sue Hares 


------=_NextPart_000_0293_01D33775.88FD9DA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>The draft =
draft-eastlake-trill-group-keying has been adopted.&nbsp; The authors =
should submit this draft as:<o:p></o:p></p><p =
class=3DMsoNormal>Draft-ietf-trill-group-keying-00.txt. =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The authors should remember that we quickly need to =
move to WG last call on this draft. &nbsp;I will ping you again in 2 =
weeks to see if you are ready for WG LC. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Sue Hares =
<o:p></o:p></p></div></body></html>
------=_NextPart_000_0293_01D33775.88FD9DA0--


From nobody Wed Sep 27 06:53:10 2017
Return-Path: <shares@ndzh.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C36A8134B96 for <trill@ietfa.amsl.com>; Wed, 27 Sep 2017 06:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.646
X-Spam-Level: ***
X-Spam-Status: No, score=3.646 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no autolearn_force=no
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 hz8DfK6hZ7s6 for <trill@ietfa.amsl.com>; Wed, 27 Sep 2017 06:53:07 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C97F134B5E for <trill@ietf.org>; Wed, 27 Sep 2017 06:53:07 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=184.157.84.200; 
From: "Susan Hares" <shares@ndzh.com>
To: <trill@ietf.org>
Cc: "'Jon Hudson'" <jon.hudson@gmail.com>, "'Donald Eastlake'" <d3e3e3@gmail.com>
Date: Wed, 27 Sep 2017 09:53:04 -0400
Message-ID: <02ac01d33797$f12bdf50$d3839df0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02AD_01D33776.6A1BC5F0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdM3l88keHkqu15RTx2XlnJpSHF+fw==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/b2rKKx3ebeePJ5-gNVaIsm5zcBU>
Subject: [trill] draft-rp-trill-parent-selection-03 - WG has adopted this draft
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 13:53:09 -0000

This is a multipart message in MIME format.

------=_NextPart_000_02AD_01D33776.6A1BC5F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Greetings TRILL WG:

 

The WG has adopted draft-rp-trill-parent-selection-03.txt.   Will the
authors please submit this draft as; 

 

Draft-ietf-trill-parent-selection-00.txt. 

 

Thank you, 

 

Susan Hares 


------=_NextPart_000_02AD_01D33776.6A1BC5F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Greetings =
TRILL WG:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The WG has adopted =
draft-rp-trill-parent-selection-03.txt.&nbsp;&nbsp; Will the authors =
please submit this draft as; <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Draft-ietf-trill-parent-selection-00.txt. =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Thank you, <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Susan Hares =
<o:p></o:p></p></div></body></html>
------=_NextPart_000_02AD_01D33776.6A1BC5F0--


From nobody Wed Sep 27 06:57:29 2017
Return-Path: <shares@ndzh.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8A54134BAA for <trill@ietfa.amsl.com>; Wed, 27 Sep 2017 06:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.845
X-Spam-Level: **
X-Spam-Status: No, score=2.845 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no autolearn_force=no
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 zRoqPSyu_HAr for <trill@ietfa.amsl.com>; Wed, 27 Sep 2017 06:57:27 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90E9E134BCD for <trill@ietf.org>; Wed, 27 Sep 2017 06:57:23 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=184.157.84.200; 
From: "Susan Hares" <shares@ndzh.com>
To: <trill@ietf.org>
Cc: "'Jon Hudson'" <jon.hudson@gmail.com>, "'Donald Eastlake'" <d3e3e3@gmail.com>
Date: Wed, 27 Sep 2017 09:57:20 -0400
Message-ID: <02be01d33798$89e884f0$9db98ed0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02BF_01D33777.02D84480"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdM3mGpyZem/e7TrQ1Kh2Nit9HT8zg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/ZaViUU_7Cy6jxKvd5JCj0vs2pbo>
Subject: [trill] draft-ietf-trill-ecn-support-03 has passed WG LC
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 13:57:28 -0000

This is a multipart message in MIME format.

------=_NextPart_000_02BF_01D33777.02D84480
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The WG has reached consensus on draft-trill-ecn-support-03.txt.  This draft
will be forward to the IESG for publication. 

 

Susan Hares and Jon Hudson 


------=_NextPart_000_02BF_01D33777.02D84480
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>The WG has =
reached consensus on draft-trill-ecn-support-03.txt.&nbsp; This draft =
will be forward to the IESG for publication. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Susan Hares =
and Jon Hudson <o:p></o:p></p></div></body></html>
------=_NextPart_000_02BF_01D33777.02D84480--


From nobody Wed Sep 27 07:00:44 2017
Return-Path: <shares@ndzh.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD1A41321A2 for <trill@ietfa.amsl.com>; Wed, 27 Sep 2017 07:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.845
X-Spam-Level: **
X-Spam-Status: No, score=2.845 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no autolearn_force=no
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 2Cx5zRVYl2UU for <trill@ietfa.amsl.com>; Wed, 27 Sep 2017 07:00:41 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C89BE133200 for <trill@ietf.org>; Wed, 27 Sep 2017 07:00:37 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=184.157.84.200; 
From: "Susan Hares" <shares@ndzh.com>
To: <trill@ietf.org>
Cc: "'Jon Hudson'" <jon.hudson@gmail.com>, "'Donald Eastlake'" <d3e3e3@gmail.com>
Date: Wed, 27 Sep 2017 10:00:34 -0400
Message-ID: <02cb01d33798$fdaee2d0$f90ca870$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02CC_01D33777.769DB800"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdM3mKqBGHyR/tfFTnm1Tp/q1BQuRg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/cOu20Ps3JwXnIqObV0fKS0Edqbk>
Subject: [trill] draft-ietf-trill-over-ip - The WG has not reached consensus
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 14:00:42 -0000

This is a multipart message in MIME format.

------=_NextPart_000_02CC_01D33777.769DB800
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The TRILL WG has not reached consensus on draft-ietf-trill-over-ip-10.txt.
Thank you for all your comments and thoughts. 

 

The authors should consider the comments received in WG LC and spin another
draft.  We will do another WG LC in October. 

 

Sue Hares 

 


------=_NextPart_000_02CC_01D33777.769DB800
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>The TRILL =
WG has not reached consensus on =
draft-ietf-trill-over-ip-10.txt.&nbsp;&nbsp; &nbsp;Thank you for all =
your comments and thoughts. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The authors =
should consider the comments received in WG LC and spin another draft. =
&nbsp;We will do another WG LC in October. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Sue Hares =
<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_02CC_01D33777.769DB800--


From nobody Wed Sep 27 13:44:15 2017
Return-Path: <shares@ndzh.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6623313508C; Wed, 27 Sep 2017 13:44:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.346
X-Spam-Level: **
X-Spam-Status: No, score=2.346 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no autolearn_force=no
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 nif0bL5r_i6M; Wed, 27 Sep 2017 13:44:13 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F0AC13508F; Wed, 27 Sep 2017 13:44:12 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=184.157.84.200; 
From: "Susan Hares" <shares@ndzh.com>
To: <trill@ietf.org>
Cc: <trill-chairs@ietf.org>, "'Donald Eastlake'" <d3e3e3@gmail.com>
Date: Wed, 27 Sep 2017 16:44:08 -0400
Message-ID: <003a01d337d1$5e08e490$1a1aadb0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_003B_01D337AF.D6F7B9C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdM30CPZJSW/WSnFSaeBI64cJFkEKg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/9uFhwrD6oxFV7aa3E4PAzkntlnc>
Subject: [trill] Working group LC on draft-ietf-trill-multi-topology-04 (9/27
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 20:44:14 -0000

This is a multipart message in MIME format.

------=_NextPart_000_003B_01D337AF.D6F7B9C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

This begins a 2 week WG LC on draft-ietf-trill-multi-topology-04.txt.
During this WG last call please include comment on the following three
things in addition to your normal comments:

1)      Does this draft support the things you desire to support multiple
topology routing of unicast and multi-destination traffic in TRILL?

2)      Do you think this draft is read for publication? 

3)      Do you think that multi-topology trill has a place in the data
center deployments of TRILL?

 

Sue Hares and Jon Hudson 

Co-chairs TRILL 


------=_NextPart_000_003B_01D337AF.D6F7B9C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1923827797;
	mso-list-type:hybrid;
	mso-list-template-ids:1390460602 67698705 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>This =
begins a 2 week WG LC on draft-ietf-trill-multi-topology-04.txt.&nbsp; =
During this WG last call please include comment on the following three =
things in addition to your normal comments:<o:p></o:p></p><p =
class=3DMsoNormal> <o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>1)<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Does this draft support the things you desire to =
support multiple topology routing of unicast and multi-destination =
traffic in TRILL?<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>2)<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Do you think this draft is read for publication? =
<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>3)<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Do you think that multi-topology trill has a =
place in the data center deployments of TRILL?<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Sue Hares =
and Jon Hudson <o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:"Courier =
New";color:black'>Co-chairs TRILL =
</span><o:p></o:p></p></div></body></html>
------=_NextPart_000_003B_01D337AF.D6F7B9C0--


From nobody Thu Sep 28 10:14:10 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: trill@ietf.org
Delivered-To: trill@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 67A6E1345FD; Thu, 28 Sep 2017 10:14:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: trill@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150661884633.27671.11051898112082529561@ietfa.amsl.com>
Date: Thu, 28 Sep 2017 10:14:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/hH3W1ZXZxm4kIDhnk6f3gmT-TDw>
Subject: [trill] I-D Action: draft-ietf-trill-group-keying-00.txt
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2017 17:14:06 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transparent Interconnection of Lots of Links WG of the IETF.

        Title           : A Group Keying Protocol
        Authors         : Donald E. Eastlake
                          Dacheng Zhang
	Filename        : draft-ietf-trill-group-keying-00.txt
	Pages           : 27
	Date            : 2017-09-28

Abstract:
   This document specifies a general group keying protocol. It also
   provides use profiles for the application of this group keying
   protocol to multi-destination TRILL Extended RBridge Channel message
   security and TRILL over IP packet security.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-trill-group-keying/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-trill-group-keying-00
https://datatracker.ietf.org/doc/html/draft-ietf-trill-group-keying-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Sep 30 15:47:30 2017
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C78AA1342DF; Sat, 30 Sep 2017 15:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 9f1HsM13F5T3; Sat, 30 Sep 2017 15:47:20 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 742201342DD; Sat, 30 Sep 2017 15:47:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E5291B80DEB; Sat, 30 Sep 2017 15:47:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, trill@ietf.org
Message-Id: <20170930224719.E5291B80DEB@rfc-editor.org>
Date: Sat, 30 Sep 2017 15:47:19 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/5ywIXK91qqVJGrqqzLgDx9AzYFM>
Subject: [trill] RFC 8249 on Transparent Interconnection of Lots of Links (TRILL): MTU Negotiation
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Sep 2017 22:47:22 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8249

        Title:      Transparent Interconnection of Lots of 
                    Links (TRILL): MTU Negotiation 
        Author:     M. Zhang, 
                    X. Zhang,
                    D. Eastlake 3rd, 
                    R. Perlman,
                    S. Chatterjee
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2017
        Mailbox:    zhangmingui@huawei.com, 
                    zhangxudong@huawei.com, 
                    d3e3e3@gmail.com,
                    radia@alum.mit.edu, 
                    somnath.chatterjee01@gmail.com
        Pages:      15
        Characters: 32423
        Updates:    RFC 6325, RFC 7177, RFC 7780

        I-D Tag:    draft-ietf-trill-mtu-negotiation-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8249

        DOI:        10.17487/RFC8249

The base IETF TRILL (Transparent Interconnection of Lots of Links)
protocol has a TRILL campus-wide MTU feature, specified in RFCs 6325
and 7177, that assures that link-state changes can be successfully
flooded throughout the campus while being able to take advantage of a
campus-wide capability to support jumbo packets.  This document
specifies recommended updates to that MTU feature to take advantage,
for appropriate link-local packets, of link-local MTUs that exceed
the TRILL campus MTU.  In addition, it specifies an efficient
algorithm for local MTU testing.  This document updates RFCs 6325,
7177, and 7780.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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


