Re: [manet] Topic for discussion?

"Ratliff, Stanley" <sratliff@idirect.net> Tue, 23 July 2019 01:18 UTC

Return-Path: <sratliff@idirect.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 826C11200CD for <manet@ietfa.amsl.com>; Mon, 22 Jul 2019 18:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 9ATdeM9xaRuU for <manet@ietfa.amsl.com>; Mon, 22 Jul 2019 18:18:25 -0700 (PDT)
Received: from us-smtp-delivery-174.mimecast.com (us-smtp-delivery-174.mimecast.com [63.128.21.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E0DD120045 for <manet@ietf.org>; Mon, 22 Jul 2019 18:18:24 -0700 (PDT)
Received: from webmail.idirect.net (198.180.159.2 [198.180.159.2]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-98-7XC1wP3bNu2kk-DaQiYpfA-1; Mon, 22 Jul 2019 21:18:22 -0400
Received: from vausditchmc3.idirect.net (10.250.251.203) by vausditchmc3.idirect.net (10.250.251.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Mon, 22 Jul 2019 21:18:22 -0400
Received: from vausditchmc3.idirect.net ([fe80::a089:5025:3057:5d51]) by vausditchmc3.idirect.net ([fe80::a089:5025:3057:5d51%13]) with mapi id 15.01.1713.004; Mon, 22 Jul 2019 21:18:21 -0400
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: Lou Berger <lberger@labn.net>, MANET IETF <manet@ietf.org>, Stan Ratliff <ratliffstan@gmail.com>
Thread-Topic: [manet] Topic for discussion?
Thread-Index: AQHVQMuhCnIF0J6No0+5thrTd/hxsabXZm8A
Date: Tue, 23 Jul 2019 01:18:20 +0000
Message-ID: <705d2209c9234e2596d65eeec7f33092@idirect.net>
References: <502f02f6-fbb1-f56c-9369-5b6409944350@labn.net>
In-Reply-To: <502f02f6-fbb1-f56c-9369-5b6409944350@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.250.251.20]
MIME-Version: 1.0
X-MC-Unique: 7XC1wP3bNu2kk-DaQiYpfA-1
X-Mimecast-Spam-Score: 0
Content-Type: multipart/alternative; boundary="MCBoundary=_11907222118230911"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/CRXBsPJk4171GG1pudbWumFYWvM>
Subject: Re: [manet] Topic for discussion?
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2019 01:18:27 -0000

Lou, 

I agree with Rick - this is a good discussion for us to have. I think we can start from my email, but having said that, it you can put together a slide or two, that would be great. If the great karma of airline travel allows, I'll be in Montreal before the MANET meeting. But, since I was due in Montreal last Sunday night, I guess one never knows... ;-)

Either way, a good discussion to have. 

Regards,
Stan

> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Lou Berger
> Sent: Monday, July 22, 2019 4:25 PM
> To: MANET IETF <manet@ietf.org>; Stan Ratliff <ratliffstan@gmail.com>
> Subject: [manet] Topic for discussion?
> 
> Hi,
> If there is time on the agenda I'd like to raise/have a discussion on dlep
> support for IP multicast. These questions come out of looking at the
> opensource dlep implementation posted at https://github.com/mit-ll/LL-
> DLEP <https://protect-
> us.mimecast.com/s/Hm65CQWqVVTowkETMP1sl?domain=github.com>  and
> RFC8175. The questions are:
> 
> (a) How does a multicast receiver identify itself (and remove itself)
> 
> (b) how does a (potential) multicast sender know about a multicast group
> and it's related parameters
> 
> (c) how does a (potential) multicast sender know what endpoints are
> reachable via a multicast group
> 
> I raised this same question with a number of people including the
> RFC8175 authors and we generally agreed that there are answers for (a) and
> (b) that can be traced easily/obviously back to RFC8175, and a fairly straight
> forward answer to (c) that we don't think falls within the intent of the RFC.
> (At least the authors of RFC8175 gave the same answers that we separately
> arrived at.)
> 
> I think it would be great if we could review the questions and ensure that we
> all agree on the answers. I can through some slides together on this, or we
> Stan/Rick could do the same. - Or we can start with Stan's (if he prefers)
> email on the topic.
> 
> Thoughts?
> 
> Thanks,
> Lou
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet <https://protect-
> us.mimecast.com/s/Wg8OCR6rWWi53vksOjum0?domain=ietf.org>

This electronic message and any files transmitted with it contains information from iDirect, which may be privileged, proprietary and/or confidential. It is intended solely for the use of the individual or entity to whom they are addressed. 
If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of 
this email is strictly prohibited. If you received this email in error, please delete it and immediately notify the sender.