Re: [netext] #5: Logical interface support: Multicast traffic
"MELIA, TELEMACO (TELEMACO)" <telemaco.melia@alcatel-lucent.com> Tue, 15 March 2011 10:03 UTC
Return-Path: <telemaco.melia@alcatel-lucent.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 3FF523A6C42 for <netext@core3.amsl.com>; Tue, 15 Mar 2011 03:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.784
X-Spam-Level:
X-Spam-Status: No, score=-5.784 tagged_above=-999 required=5 tests=[AWL=0.465, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 jEjrnPxk4uYC for <netext@core3.amsl.com>; Tue, 15 Mar 2011 03:03:27 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id 229AC3A69E3 for <netext@ietf.org>; Tue, 15 Mar 2011 03:03:26 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p2FA2qO4002560 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 15 Mar 2011 11:04:46 +0100
Received: from FRMRSSXCHMBSE1.dc-m.alcatel-lucent.com ([135.120.45.54]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Tue, 15 Mar 2011 11:04:43 +0100
From: "MELIA, TELEMACO (TELEMACO)" <telemaco.melia@alcatel-lucent.com>
To: Sri Gundavelli <sgundave@cisco.com>, Julien Laganier <julien.ietf@gmail.com>
Date: Tue, 15 Mar 2011 11:04:41 +0100
Thread-Topic: [netext] #5: Logical interface support: Multicast traffic
Thread-Index: AcvitL1pk/SlWp5N1kqZTFBp+1zpPQAQ3dzg
Message-ID: <3D6C64F2D792B540BAAEBCEF6509363B0EE6E5A424@FRMRSSXCHMBSE1.dc-m.alcatel-lucent.com>
References: <AANLkTim4aeCmtWgdXvMFTu=mJC9HmEoZTnYhJBE8Tj7L@mail.gmail.com> <C9A41645.13626%sgundave@cisco.com>
In-Reply-To: <C9A41645.13626%sgundave@cisco.com>
Accept-Language: en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "netext@ietf.org" <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 10:03:28 -0000
Julien, is the question about global multicast traffic? telemaco -----Message d'origine----- De : netext-bounces@ietf.org [mailto:netext-bounces@ietf.org] De la part de Sri Gundavelli Envoyé : mardi 15 mars 2011 04:00 À : Julien Laganier Cc : netext@ietf.org Objet : Re: [netext] #5: Logical interface support: Multicast traffic 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 >>>> >> >> _______________________________________________ netext mailing list netext@ietf.org https://www.ietf.org/mailman/listinfo/netext
- [netext] #5: Logical interface support: Multicast… netext issue tracker
- Re: [netext] #5: Logical interface support: Multi… Sri Gundavelli
- Re: [netext] #5: Logical interface support: Multi… Julien Laganier
- Re: [netext] #5: Logical interface support: Multi… Sri Gundavelli
- Re: [netext] #5: Logical interface support: Multi… Julien Laganier
- Re: [netext] #5: Logical interface support: Multi… Sri Gundavelli
- Re: [netext] #5: Logical interface support: Multi… MELIA, TELEMACO (TELEMACO)
- Re: [netext] #5: Logical interface support: Multi… Julien Laganier
- Re: [netext] #5: Logical interface support: Multi… Sri Gundavelli