IETF Logo Mail Archive

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

Sri Gundavelli <sgundave@cisco.com> Tue, 15 March 2011 01:57 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 A39033A6BBA for <netext@core3.amsl.com>; Mon, 14 Mar 2011 18:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.471
X-Spam-Level:
X-Spam-Status: No, score=-9.471 tagged_above=-999 required=5 tests=[AWL=-0.268, 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 aau2fH9SBZ50 for <netext@core3.amsl.com>; Mon, 14 Mar 2011 18:57:13 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id EE20C3A68AB for <netext@ietf.org>; Mon, 14 Mar 2011 18:57:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=3804; q=dns/txt; s=iport; t=1300154317; x=1301363917; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=dxLW9WcvpPul82BDncNSxWnzYICgg9h9pKPKcrqCvSI=; b=i+SUvR/5hTJjiXgVLZ8qKnQKognIbsJBP1YcF0VEbmiANVbpnCeM8TIW J+nT5Ig/Shf+I8LpDStrBFfj8Pj2YPPlnSRTRJoZRhEXgtZ+xlbGM8aEY 2m2sewjVkpV1Cz18XAi6QDi7MqZUM5CDuMm9TX2YoZn5nQRcZwQkjZFuB M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIdkfk2tJXHB/2dsb2JhbAClO1N3pXqcUYViBIUrhyeDVIMc
X-IronPort-AV: E=Sophos;i="4.62,319,1297036800"; d="scan'208";a="346552118"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by sj-iport-5.cisco.com with ESMTP; 15 Mar 2011 01:58:37 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id p2F1waiF025127; Tue, 15 Mar 2011 01:58:36 GMT
Received: from xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Mar 2011 18:58:36 -0700
Received: from 10.32.246.213 ([10.32.246.213]) by xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) with Microsoft Exchange Server HTTP-DAV ; Tue, 15 Mar 2011 01:58:35 +0000
User-Agent: Microsoft-Entourage/12.28.0.101117
Date: Mon, 14 Mar 2011 19:00:21 -0800
From: Sri Gundavelli <sgundave@cisco.com>
To: Julien Laganier <julien.ietf@gmail.com>
Message-ID: <C9A41645.13626%sgundave@cisco.com>
Thread-Topic: [netext] #5: Logical interface support: Multicast traffic
Thread-Index: AcvitL1pk/SlWp5N1kqZTFBp+1zpPQ==
In-Reply-To: <AANLkTim4aeCmtWgdXvMFTu=mJC9HmEoZTnYhJBE8Tj7L@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-2"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 15 Mar 2011 01:58:36.0427 (UTC) FILETIME=[7F1515B0:01CBE2B4]
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:57:15 -0000

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
>>>> 
>> 
>>

v2.23.0 | Report a Bug | By Email