IETF Logo Mail Archive

Re: [netext] #5: Logical interface support: Multicast traffic

Julien Laganier <julien.ietf@gmail.com> Tue, 15 March 2011 01:51 UTC

Return-Path: <julien.ietf@gmail.com>
X-Original-To: netext@core3.amsl.com
Delivered-To: netext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 814B03A6E04 for <netext@core3.amsl.com>; Mon, 14 Mar 2011 18:51:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.278
X-Spam-Level:
X-Spam-Status: No, score=-3.278 tagged_above=-999 required=5 tests=[AWL=0.321, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UzGuAiAojtny for <netext@core3.amsl.com>; Mon, 14 Mar 2011 18:51:23 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 023B63A6BD5 for <netext@ietf.org>; Mon, 14 Mar 2011 18:51:22 -0700 (PDT)
Received: by fxm15 with SMTP id 15so124195fxm.31 for <netext@ietf.org>; Mon, 14 Mar 2011 18:52:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=r4vVdc5rI3HYDagI9vCYxeO4FocMm+LNRUKXkhCt6XE=; b=YcqHlULZZR+Tu0c1aVbZzf3U2iwXcXxAt7qbK+TUHNI1SFk9oTcdqnOyTjvdv75hyY elAFdoBCMmia/V5wz4Ljfgmmza+/dhIN6CRQoYsBsItZbYb06evsPRcfvTLfv30/Eo+b gTykhOhsSjiZKePEtnIlYv8J8gbaEdE4oa5+s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=h8fR2c8+52SY2Mjbmnbt2Mn78OCDcMnrSvHTnqakXcCO8pU2GAlW5nJojnRmHHgZtD sznqa0SXgxBeB5U5nAD+dQ1sfKhnDd2QU1xJ5p0bo3J7ywwkGWcuBoqQv6WGh8ypN930 LUwlMS2W2aSyKbrP+2OjOc3JLVyUl/KLYGuJQ=
MIME-Version: 1.0
Received: by 10.223.151.14 with SMTP id a14mr1433158faw.134.1300153966549; Mon, 14 Mar 2011 18:52:46 -0700 (PDT)
Received: by 10.223.78.135 with HTTP; Mon, 14 Mar 2011 18:52:46 -0700 (PDT)
In-Reply-To: <C9A4124D.1361E%sgundave@cisco.com>
References: <AANLkTi=0rTWWrc-MX0anmKpKvfU67QGXsJf9Ww+ifpwq@mail.gmail.com> <C9A4124D.1361E%sgundave@cisco.com>
Date: Mon, 14 Mar 2011 18:52:46 -0700
Message-ID: <AANLkTim4aeCmtWgdXvMFTu=mJC9HmEoZTnYhJBE8Tj7L@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
To: Sri Gundavelli <sgundave@cisco.com>
Content-Type: text/plain; charset="ISO-8859-2"
Content-Transfer-Encoding: quoted-printable
Cc: netext@ietf.org
Subject: Re: [netext] #5: Logical interface support: Multicast traffic
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 01:51:24 -0000

The case I have in mind is: IP stack wants to send a packet to
multicast address M;  How is it transmitted?

--julien

2011/3/14 Sri Gundavelli <sgundave@cisco.com>:
> Julien:
>
> Agree. I did put that note below that we should add any additional cases.
> The text around handling link-specific multicast traffic with different
> destination scopes covers most of the common multicast cases, ALL-NODES,
> SOLICTED-NODE... We can add any missing cases and resolve it. Any specific
> case you are thinking about ? We can generalize the case and make it apply
> for ND and non-ND cases.
>
>
>
> Regards
> Sri
>
>
>
>
> On 3/14/11 5:25 PM, "Julien Laganier" <julien.ietf@gmail.com> wrote:
>
>> Sri -
>>
>> Multicast traffic isn' t limited to ND, thus I don' t think it is
>> appropriate to consider this issue as closed because you crafter some
>> text on ND considerations elsewhere in this document. Please clarify
>> how tranmission on multicast traffic is handled over a logical
>> interface.
>>
>> --julien
>>
>> On Mon, Mar 14, 2011 at 4:27 PM, Sri Gundavelli <sgundave@cisco.com> wrote:
>>>> #5: Logical interface support: Multicast traffic
>>>
>>>  Clarify how the logical
>>>> interface deals with multicast traffic.
>>>
>>>
>>> We believe we have resolve this issue, this is captured in the ND
>>> interactions section. The general considerations around dealing with
>>> link-specific multicast traffic, all-nodes, solicited node multicast
>>> traffic, or others have common considerations. It is possible we might be
>>> missing few cases, we can add that in, but the base handling of things at
>>> the logical interface level, or sub-interface level is captured. Comments
>>> welcome.
>>>
>>>
>>> Sri
>>>
>>>
>>>
>>>
>>>
>>> On 3/3/11 9:19 AM, "netext issue tracker" <trac+netext@trac.tools.ietf.org>
>>> wrote:
>>>
>>>> #5: Logical interface support: Multicast traffic
>>>
>>>  Clarify how the logical
>>>> interface deals with multicast traffic.
>>>
>>> --
>>>>
>>> ---------------------------------------+------------------------------------
>>>
>>>> Reporter:  basavaraj.patil@Š          |       Owner:  telemaco.melia@Š
>>>>
>>>     Type:  defect                     |      Status:  new
>>>>
>>>  Priority:  critical                   |   Milestone:
>>>>
>>> Component:  logical-interface-support  |     Version:
>>>>
>>>  Severity:  -                          |    Keywords:
>>>>
>>> ---------------------------------------+------------------------------------
>>>
>>>>
>>> Ticket URL: <http://trac.tools.ietf.org/wg/netext/trac/ticket/5>
>>> netext
>>>> <http://tools.ietf.org/netext/>
>>>
>>> _____________________________________________
>>>> __
>>> netext mailing
>>>> list
>>> netext@ietf.org
>>> https://www.ietf.org/mailman/listinfo/netext
>>>
>>>
>>> _______________________________________________
>>> netext mailing list
>>> netext@ietf.org
>>> https://www.ietf.org/mailman/listinfo/netext
>>>
>
>

v2.23.0 | Report a Bug | By Email