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

Sri Gundavelli <sgundave@cisco.com> Wed, 16 March 2011 00:15 UTC

Return-Path: <sgundave@cisco.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 2674F3A6EAA for <netext@core3.amsl.com>; Tue, 15 Mar 2011 17:15:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.447
X-Spam-Level:
X-Spam-Status: No, score=-9.447 tagged_above=-999 required=5 tests=[AWL=-0.244, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
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 weBEIyNrT-lI for <netext@core3.amsl.com>; Tue, 15 Mar 2011 17:15:54 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 2AD773A6A4E for <netext@ietf.org>; Tue, 15 Mar 2011 17:15:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=4802; q=dns/txt; s=iport; t=1300234640; x=1301444240; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=WJlTqaJuYQG59ZMIqV2NibSdMVFjGWnKsYzJizmDRzk=; b=aTaYZG6ZvwJX+SAJc4FeQBkCAB4c2n0E2BKyikuA2uhRjNSAg3lwVkPo ywfuNNgeoa152vtLnrozZYLAGSSueoJOJT6/+Ii9QUk54M7Qzu51RepyL orkXk1h8mGQ7+9ZMqL00xBZgPgolYdd75HyIqUp+g5WZW1VvhNNwC1mYP E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAFqef02tJXG8/2dsb2JhbAClOFV3pG6cYYViBIUwhy2DVYMf
X-IronPort-AV: E=Sophos;i="4.63,191,1299456000"; d="scan'208";a="320712097"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by sj-iport-2.cisco.com with ESMTP; 16 Mar 2011 00:17:19 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2G0HGEi019476; Wed, 16 Mar 2011 00:17:19 GMT
Received: from xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 15 Mar 2011 17:17:18 -0700
Received: from 10.32.243.120 ([10.32.243.120]) by xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) with Microsoft Exchange Server HTTP-DAV ; Wed, 16 Mar 2011 00:17:17 +0000
User-Agent: Microsoft-Entourage/12.28.0.101117
Date: Tue, 15 Mar 2011 17:17:15 -0800
From: Sri Gundavelli <sgundave@cisco.com>
To: Julien Laganier <julien.ietf@gmail.com>
Message-ID: <C9A54F9B.138B8%sgundave@cisco.com>
Thread-Topic: [netext] #5: Logical interface support: Multicast traffic
Thread-Index: Acvjb4Cuze2UQTqf2UO9miCVkCpsWQ==
In-Reply-To: <AANLkTikxyJvbgV3AfzD0WsTx6GbWaLvtpAYMTrKsq2+2@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-2"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 16 Mar 2011 00:17:18.0180 (UTC) FILETIME=[8293F240:01CBE36F]
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: Wed, 16 Mar 2011 00:15:55 -0000

We have captured this under ND. Its a valid point, that ND is just one
sub-case of multicast usage. We should have sub section specific to
multicast and we can present this in a generic way. That's fine, we will
write up some text for this and resolve it.


Sri



On 3/15/11 8:15 AM, "Julien Laganier" <julien.ietf@gmail.com> wrote:

> We have to deal with the general problem. If there are subcases, let's
> deal with all of the subcases, sure. As to link-local, as I said in my
> other note multicast traffic isn' t limited to ND thus I don't believe
> you have covered them.
> 
> --julien
> 
> 2011/3/14 Sri Gundavelli <sgundave@cisco.com>:
>> If you can define the destination scope, link-specific non-link-specific ?
>> We have covered link-specific cases in the ND context (which can be
>> generalized), non-link specific ? May be if you can reflect the issue that
>> you are thinking, that will help resolve the issue.
>> 
>> 
>> 
>> Sri
>> 
>> 
>> 
>> 
>> 
>> 
>> On 3/14/11 5:52 PM, "Julien Laganier" <julien.ietf@gmail.com> wrote:
>> 
>>> 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
>>>>>> 
>>>> 
>>>> 
>> 
>>