Re: [Int-area] multicast over wifi and and IEEE-IETF coordination

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Wed, 04 November 2015 10:20 UTC

Return-Path: <evyncke@cisco.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6DED1B2CA9; Wed, 4 Nov 2015 02:20:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TXjETjIsDP1o; Wed, 4 Nov 2015 02:20:56 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D80CA1B2CA7; Wed, 4 Nov 2015 02:20:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6274; q=dns/txt; s=iport; t=1446632456; x=1447842056; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=FfIcxLQhyzl8NcQWXMYD+9LHzJv2as8rYmw/Z9JOR7c=; b=ScMXEcrj2cLro9s6GkoOKJHHELqrGnKqiuTmFan6CdPs5awmqEvjPBxJ AcfCl/acNMaiTKDLmSrvBmvjK9JZiXd7RamCESZuzU+RgjaER9psNz3zq 1WsScRk/bK9GCMar2Dd2ZzEfJF3Xcd/bWXQWLwQhnW4LM8LnwHyUvgcAi U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AnAgDq2jlW/4cNJK1egztTbwa9PgENgV0XCoVyAhyBJDgUAQEBAQEBAYEKhDUBAQEEAQEBIBE6CwwEAgEIEQQBAQECAiMDAgICJQsUAQgIAgQBDQWILg2wMZEEAQEBAQEBAQEBAQEBAQEBAQEBAQEBFASBAoVTAYN3gQaEKhEBAhuDHIFDBYdEjwQBhRyIBoFahD+SNoNxAR8BAUKCER2BVnKDczqBBwEBAQ
X-IronPort-AV: E=Sophos;i="5.20,242,1444694400"; d="scan'208";a="204901498"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-8.cisco.com with ESMTP; 04 Nov 2015 10:20:54 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id tA4AKsBC025201 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 4 Nov 2015 10:20:54 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 4 Nov 2015 05:20:53 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1104.000; Wed, 4 Nov 2015 05:20:53 -0500
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Mikael Abrahamsson <swmike@swm.pp.se>, "Toerless Eckert (eckert)" <eckert@cisco.com>
Thread-Topic: multicast over wifi and and IEEE-IETF coordination
Thread-Index: AQHRFporO3PMCyEQWkSveOriSt2nNp6LXgIAgAAPcoCAABkcgIAAhcSA
Date: Wed, 4 Nov 2015 10:20:53 +0000
Message-ID: <D25F9A53.5D3FA%evyncke@cisco.com>
References: <20151104004558.GJ31730@cisco.com> <alpine.DEB.2.02.1511040151520.15542@uplift.swm.pp.se> <9904FB1B0159DA42B0B887B7FA8119CA6BE807E6@AZ-FFEXMB04.global.avaya.com> <d4a7a943d65c4536a986641491e41cf4@XCH-RCD-001.cisco.com>
In-Reply-To: <d4a7a943d65c4536a986641491e41cf4@XCH-RCD-001.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.7.151005
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.60.138.46]
Content-Type: text/plain; charset="utf-8"
Content-ID: <70203832CA13784EB3C3A4247A08F5CD@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/int-area/2l8EHTimldXgFqNFF4jG8V3D2jg>
X-Mailman-Approved-At: Mon, 09 Nov 2015 08:47:05 -0800
Cc: "mboned@ietf.org" <mboned@ietf.org>, "6man@ietf.org" <6man@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
Subject: Re: [Int-area] multicast over wifi and and IEEE-IETF coordination
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2015 10:20:58 -0000

I also support the idea of a BoF during an IETF meeting. The issues need
to be known to as many people as possible until there is 'a fix' within
IEEE 

-éric

On 4/11/15 04:22, "ipv6 on behalf of Pascal Thubert (pthubert)"
<ipv6-bounces@ietf.org on behalf of pthubert@cisco.com> wrote:

>Hello Dan,
>
>I'd see it useful to give this a lot of visibility and accessibility. A
>BoF-type meeting outside of meeting hours at this or the next IETF would
>probably improve that piece. INTAREA has collisions that people did not
>necessarily get a chance to manage in advance so interested people may
>miss the presentation.
>I would like to be sure that most interested parties have a chance to
>know that this is happening at all.
>
>Some of these discussion will relate to work happening at various WGs.
>Out of my hat and not copied above I see at least 6lo and MANET which
>deal with radios networks and need efficient network and service
>discovery. Cc ing 6lo because this is where RFC 6775 originated, and new
>work is taking place.
>
>There will be serious discussions, and probably documents produced in the
>form of best practices. This work may deserve a short-termed WG on its
>own. A non-Wg forming BoF would help figure all that out.
>
>Cheers,
>
>Pascal
>
>
>> -----Original Message-----
>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Romascanu, Dan
>> (Dan)
>> Sent: mercredi 4 novembre 2015 10:52
>> To: Mikael Abrahamsson <swmike@swm.pp.se>se>; Toerless Eckert (eckert)
>> <eckert@cisco.com>
>> Cc: mboned@ietf.org; 6man@ietf.org; int-area@ietf.org
>> Subject: RE: multicast over wifi and and IEEE-IETF coordination
>> 
>> Does anybody believe there is a better/other place to go with this
>> information?
>> 
>> Thanks and Regards,
>> 
>> Dan
>> 
>> 
>> > -----Original Message-----
>> > From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Mikael
>> > Abrahamsson
>> > Sent: Wednesday, November 04, 2015 2:57 AM
>> > To: Toerless Eckert
>> > Cc: mboned@ietf.org; 6man@ietf.org; int-area@ietf.org
>> > Subject: Re: multicast over wifi and and IEEE-IETF coordination
>> >
>> > On Tue, 3 Nov 2015, Toerless Eckert wrote:
>> >
>> > > [sorry, resending with correct email aliases]
>> > >
>> > > Mikael:
>> > >
>> > > Any reason to choose INTAREA ?
>> >
>> > I didn't choose anything, INTAREA was chosen by the people in the
>> > coordination group that includes several ADs. The multicast over wifi
>> > issue has been raised in multiple working groups.
>> >
>> > > There is already a draft in mboned:
>> > >
>> > > draft-mcbride-mboned-wifi-mcast-problem-statement-00.txt
>> > >
>> > > and... mboned runs in parallel to intarea this time *sigh* and... i
>> > > am sure mboned participants would love to hear your preso about
>>IEEE.
>> >
>> > So thanks for including mboned so that people there are aware that
>> > this is discussed in INTAREA. MBONED is not alone in having conflicts
>> > with INTAREA, there are other low-power wireless technology people who
>> > also have conflicts. Please discuss this issue on the INTAREA mailing
>> > list, and you can watch the presentation (it's not mine) after the
>> > fact on for instance Meetecho. I don't believe there is much time for
>> > discussion in the INTAREA meeting, they have a packed agenda already
>>if I
>> understood correctly.
>> >
>> > --
>> > Mikael Abrahamsson    email: swmike@swm.pp.se
>> >
>> > --------------------------------------------------------------------
>> > IETF IPv6 working group mailing list
>> > ipv6@ietf.org
>> > Administrative Requests:
>> > https://urldefense.proofpoint.com/v2/url?u=https-
>> >
>> 3A__www.ietf.org_mailman_listinfo_ipv6&d=BQICAg&c=BFpWQw8bsuKpl
>> 1
>> >
>> SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=aVouzp
>> b
>> > CzgpDGMb8eabFNhiZ61AnoK06iltaK1NwjdE&s=cleQzxju-
>> > 9RBGYIarDCVTKq1uzL_2XAW0kgXpVNreiw&e=
>> > --------------------------------------------------------------------
>> 
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------