[trill] 答复: review of Trill over UDP/IP

Zongning <zongning@huawei.com> Tue, 15 July 2014 09:00 UTC

Return-Path: <zongning@huawei.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 9B6BC1A059F for <trill@ietfa.amsl.com>; Tue, 15 Jul 2014 02:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.552
X-Spam-Level:
X-Spam-Status: No, score=-104.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 oHunpNyUKHJR for <trill@ietfa.amsl.com>; Tue, 15 Jul 2014 02:00:50 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AEE91A0535 for <trill@ietf.org>; Tue, 15 Jul 2014 02:00:49 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BHF02263; Tue, 15 Jul 2014 09:00:48 +0000 (GMT)
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 15 Jul 2014 10:00:11 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.155]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Tue, 15 Jul 2014 17:00:07 +0800
From: Zongning <zongning@huawei.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Thread-Topic: [trill] review of Trill over UDP/IP
Thread-Index: Ac+fxW4CtnOjHs+WR2eN+H4TioPy5///8msA//9sRwA=
Date: Tue, 15 Jul 2014 09:00:06 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC6667796617112B@nkgeml501-mbs.china.huawei.com>
References: <B0D29E0424F2DE47A0B36779EC6667796616FF53@nkgeml501-mbs.china.huawei.com> <CAF4+nEGPMgN7t5g=2pBxdt5C3S5YAwe6uuWtSxuM0ew9NYqQ7A@mail.gmail.com>
In-Reply-To: <CAF4+nEGPMgN7t5g=2pBxdt5C3S5YAwe6uuWtSxuM0ew9NYqQ7A@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.54]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/trill/AD6ROC3h3-ANKGtMGA7k5x4f-yc
Cc: "trill@ietf.org" <trill@ietf.org>
Subject: [trill] 答复: review of 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: <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: Tue, 15 Jul 2014 09:00:52 -0000

Hi, Donald,

Thank you for the prompt reply. Please see inline.

-----邮件原件-----
发件人: Donald Eastlake [mailto:d3e3e3@gmail.com] 
发送时间: 2014年7月15日 15:52
收件人: Zongning
抄送: trill@ietf.org
主题: Re: [trill] review of Trill over UDP/IP

Hi,

On Mon, Jul 14, 2014 at 8:40 PM, Zongning <zongning@huawei.com> wrote:
> Hi, folks,
>
> (Re-send after subscription, sorry for potentially duplicated 
> message…)
>
> I’ve briefly reviewed the draft mainly from transport consideration’s 
> perspective, and have a question on congestion control.
>
> It says “When a TRILL over IP flow carries primarily IP-based traffic, 
> the aggregate traffic is assumed to be TCP friendly… and no additional 
> congestion avoidance action is necessary”. I’d like to see more 
> discussion about whether the adoption of UDP encapsulation by RBridges 
> between the end-hosts will negate such conclusion? Another word, even 
> if the end-hosts use TCP for congestion control, should there be some 
> congestion consideration between the RBridges that talk UDP?

Congestion control has been a very active area of discussion for other drafts. The congestion control text in the current version of draft-ietf-trill-over-ip was just copied with minor edits from an earlier version of draft-ietf-mpls-in-udp. That mpls draft has since been updated with substantial changes to its congestion section so I'm sure some work will be needed here.

[Ning] Then I'd suggest to add reference to [RFC5405] "Unicast UDP Usage Guidelines for Application Designers", which provides several cases in 3.1.3 about whether the UDP tunnel user should consider additional congestion control mechanism or not. Moreover, similar to draft-ietf-mpls-in-udp, I think it would be beneficial to add some brief text to clarify which case(s) in [RFC5405] that the draft-ietf-trill-over-ip belongs to, based on the specific features (if any) of Trill traffic.

> Plus, I’d know the reason why choosing UDP? I cannot find any in the 
> draft – but I am sure there are reasons discussed in the group. :-)

This was discussed at IETF 89 and the consensus there was confirmed on the mailing list. See http://www.ietf.org/mail-archive/web/trill/current/msg06206.html
You could look at the minutes at
http://www.ietf.org/proceedings/89/minutes/minutes-89-trill or listen to the audio recording.

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

> Sorry if I misunderstood any point, and thanks for your clarification 
> in advance!
>
> -Ning
>
>
>
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill
>