[trill] draft-ietf-trill-channel-tunnel-05 - 2 week WG LC (5/29 to 6/12)

"Susan Hares" <shares@ndzh.com> Fri, 29 May 2015 12:38 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5E901A8858 for <trill@ietfa.amsl.com>; Fri, 29 May 2015 05:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Level:
X-Spam-Status: No, score=-99.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=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 fSNZ0u6W_T62 for <trill@ietfa.amsl.com>; Fri, 29 May 2015 05:37:59 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 777541A8857 for <trill@ietf.org>; Fri, 29 May 2015 05:37:58 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=174.124.178.112;
From: "Susan Hares" <shares@ndzh.com>
To: <trill@ietf.org>
Date: Fri, 29 May 2015 08:37:50 -0400
Message-ID: <02e201d09a0c$47249810$d56dc830$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02E3_01D099EA.C0160550"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdCaCmcpq5lgvSoHTv2mkuf69u8KsQ==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
X-IsFriend: <shares@ndzh.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/RpO_MBckO91s4HA2TJpQZynXcq8>
Cc: 'Donald Eastlake' <d3e3e3@gmail.com>, trill-chairs@tools.ietf.org, draft-ietf-trill-channel-tunnel@tools.ietf.org, shares@ndzh.com, 'Jon Hudson' <jon.hudson@gmail.com>
Subject: [trill] draft-ietf-trill-channel-tunnel-05 - 2 week WG LC (5/29 to 6/12)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 29 May 2015 12:38:01 -0000

This is to begin a 2 week WG LC for draft-ietf-trill-channel-tunnel-05 (5/29
to 6/12).  The authors (Donald, Mohammed, Yizhou) should send a note to the
list indicating whether they know if any IPR. 

 

You can access the draft at: 

http://datatracker.ietf.org/doc/draft-ietf-trill-channel-tunnel/

 

A summary of the document is: 

   The IETF TRILL (Transparent Interconnection of Lots of Links)

   protocol includes an optional mechanism, called RBridge Channel, that

   is specified in RFC 7178, for the transmission of typed messages

   between TRILL switches in the same campus and between TRILL switches

   and end stations on the same link. This document specifies two

   optional extensions to the RBridge Channel protocol: (1) A standard

   method to tunnel a variety of payload types by encapsulating them in

   an RBridge Channel message; and (2) A method to support security

   facilities for RBridge Channel messages. This document updates RFC

   7178.

 

Please answer the following questions: 

1)      Does this draft enhance RFC7178 and is it ready for WG LC? 

2)      Do you have any concerns regarding the mechanisms? 

 

Sue