IETF Logo Mail Archive

Re: [Softwires] draft-ietf-softwire-mesh-multicast-05.txt

Shu Yang <yangshu1988@gmail.com> Wed, 17 July 2013 14:46 UTC

Return-Path: <yangshu1988@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F233921F9D2C for <softwires@ietfa.amsl.com>; Wed, 17 Jul 2013 07:46:21 -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=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j+uyAsPMwmpw for <softwires@ietfa.amsl.com>; Wed, 17 Jul 2013 07:46:21 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 449A921F9294 for <softwires@ietf.org>; Wed, 17 Jul 2013 07:46:20 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id c11so1852149wgh.25 for <softwires@ietf.org>; Wed, 17 Jul 2013 07:46:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DsB0CfC+fS1UJwUwMqiexkq2Y/801yqWP4PZ9W5wVCg=; b=Uv3QSyCP7EqUViN3mjbDCVhZdn5KpG8p52DakZoD9NNzOIXX9qErJsnVly8Bl6rI7v O0A3m3jR5dA627N2Xbrc8wFTUIP8xf1DKKM/wKoPfj7BDFk+dB8mDPwSSBHzw3wvy81d tJ2/38B4K704E0rGOjDaycRJlsihpNTa0MzQzWlqtZs4FONdRmn0rrqwfEbuB3Qex1NC Hw91YVLmEplM//lAlApsUSQe4I0rJo7cDYuZ4cxINvyVWmnsIzyEEr75ai1EwnTF1Uqn TX9IxddSX8d76LxHPelGrwRRfGTFfaAQfEapnCLykZ7glmrvsDKyeaUcpI/P32M49vbS /O7w==
MIME-Version: 1.0
X-Received: by 10.180.36.107 with SMTP id p11mr4978660wij.31.1374072380314; Wed, 17 Jul 2013 07:46:20 -0700 (PDT)
Received: by 10.194.55.131 with HTTP; Wed, 17 Jul 2013 07:46:20 -0700 (PDT)
In-Reply-To: <CAC8QAceH3qOEn3wscouBA+AQcBLDRLMh6Cf48+TXBrPM993oZg@mail.gmail.com>
References: <CAL6OX+3KDNvdryZZMHyGQ34dggKKEJW37MzeohPpJ6MwyjCbBw@mail.gmail.com> <CAC8QAceH3qOEn3wscouBA+AQcBLDRLMh6Cf48+TXBrPM993oZg@mail.gmail.com>
Date: Wed, 17 Jul 2013 22:46:20 +0800
Message-ID: <CAL6OX+2CR5x+2QHn3FnrcG9qSZ4JQ0BFEaFEe8=SbN1ebBG=RQ@mail.gmail.com>
From: Shu Yang <yangshu1988@gmail.com>
To: sarikaya@ieee.org
Content-Type: text/plain; charset="ISO-8859-1"
Cc: softwires@ietf.org
Subject: Re: [Softwires] draft-ietf-softwire-mesh-multicast-05.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2013 14:46:22 -0000

Hi, Dear Behcet,

> But my question is a very fundamental  one. I think that mesh architecture is
> a very specific architecture. It seems that it will work only for unicast.

In Section 11 of RFC5565,  it's recommended that softwire multicast be supported
within the mesh framework.

Best Regards,
Shu Yang

On Wed, Jul 17, 2013 at 3:07 AM, Behcet Sarikaya <sarikaya2012@gmail.com> wrote:
>
> Dear Shu,
>
> Please see inline.
>
> Regards,
>
> Behcet
>
> On Tue, Jul 16, 2013 at 8:03 AM, Shu Yang <yangshu1988@gmail.com> wrote:
>>
>> Dear Behcet,
>>
>> > If Softwire mesh means packets from the host to
>> > one CE are directly routed to the destination CE, I
>> > am puzzled how multicast can be supported in such a network?
>>
>> In Softwire mesh multicast, packets from source host are first
>> routed to AFBR (address family border router), using multicast.
>> Then packets travel through the core towards another AFBR
>> (as the core runs MPBGP), with either unicast or multicast.
>> At last, packets are routed to the destination, with multicast
>> again.
>>
>
> My question is not about how you propose to support multicast.
>
> But my question is a very fundamental  one. I think that mesh architecture is a very specific architecture. It seems that it will work only for unicast.
>
> As to your approach, of course you can do things like that but that would also work for non mesh architecture, right?
>
>
>> Your further review and comments are more than welcome.
>>
>> Best Regards,
>> Shu Yang
>
>

v2.23.0 | Report a Bug | By Email