[trill] Fwd: TRILL over UDP/IP

Donald Eastlake <d3e3e3@gmail.com> Sun, 02 August 2015 01:54 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 8286E1A88DB for <trill@ietfa.amsl.com>; Sat, 1 Aug 2015 18:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id JkGCY2Dk9xC1 for <trill@ietfa.amsl.com>; Sat, 1 Aug 2015 18:54:02 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::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 5CB6B1A874C for <trill@ietf.org>; Sat, 1 Aug 2015 18:54:02 -0700 (PDT)
Received: by obnw1 with SMTP id w1so77653962obn.3 for <trill@ietf.org>; Sat, 01 Aug 2015 18:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=IY7wxrG3Nfv2RzvfV//Fuv95QeDm9UjaBAuu5QSiQJA=; b=hkzTpoFRW5hJRJEbc7QLfuQdQKkrLQ5ni+LIm1Eykw5COhqTxC1Be2I1o0efuB3IjC rdN+hFTAgx5qm/TTtX3PdgMVmCBmSdSQ3busMS4ia8m/YmkXOjs/BL6bVz/ZPSQxuHTD fb7eNbGVLfu/c5b+L+X9ZDW+GUrShBQ4SRQUaGHu4iavBF3wPmKjAaXJyETHBeFaYU3S blmKhVrjLG51w94DINtOpcuzoewJJf2lvcABZ7dZOyYOt9SjMb3VB4BoR9KAJcx6fPU9 dkK9HO0s64EOn+0G4172fVY2mZOeda7gkA9FqiZ5NDihCFXCZNPCNtD4shfBVIEgH8CH sWOw==
X-Received: by with SMTP id r2mr10795533obk.20.1438480441778; Sat, 01 Aug 2015 18:54:01 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Sat, 1 Aug 2015 18:53:47 -0700 (PDT)
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D571CCE21@dfweml701-chm>
References: <2691CE0099834E4A9C5044EEC662BB9D571CCE21@dfweml701-chm>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sat, 1 Aug 2015 21:53:47 -0400
Message-ID: <CAF4+nEEnJ4BFo_uPoMBSYSci3O=8c7LhkxPEvXQiyVGv3_UVHg@mail.gmail.com>
To: "trill@ietf.org" <trill@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c1d8d6bfcbb0051c4a536f
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/v8awUNJpAVqLU35H06GDG61CPUU>
Subject: [trill] Fwd: TRILL over UDP/IP
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: <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: Sun, 02 Aug 2015 01:54:03 -0000

Forwarded to the TRILL WG mailing list by request.


---------- Forwarded message ----------
From: Lucy yong <lucy.yong@huawei.com>
Date: Thu, Jul 30, 2015 at 2:14 PM
Subject: TRILL over UDP/IP


I gave some comments about TRILL over UDP/IP in TRILL meeting and promised
to post them on TRILL mailing list. Please help to post it on TRILL list.

1)      TRILL over UPD makes TRILL running as an UDP application in IP
network. Therefore, it needs meet UDP tunnel/application requirement
specified in RFC5405bis. As a UDP application, three points need to be
considered: 1) checksum, 2) middle-box, 3) congestion control. Please refer
to RFC7510 (MPLS/UDP) where these have been addressed.  If TRILL over UDP
is intended over Internet as well which RFC7510 does not, then RFC7510 does
not apply.

2)      Use IPsec for secure transport over IP network, it will lose UDP
flow entropy benefit.  Alternative is to consider use of DTLS that is a
security transport mechanism at application layer. IPsec is a security
mechanim at network layer.