Re: [manet] DLEP and broadcast/multicast
"A. Riley Eller" <reller@cococorp.com> Mon, 15 August 2011 17:01 UTC
Return-Path: <reller@cococorp.com>
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 534B921F8C79 for <manet@ietfa.amsl.com>; Mon, 15 Aug 2011 10:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.101
X-Spam-Level: *
X-Spam-Status: No, score=1.101 tagged_above=-999 required=5 tests=[AWL=-1.200, BAYES_50=0.001, MANGLED_TOOL=2.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2J88U+P9ZcYE for <manet@ietfa.amsl.com>; Mon, 15 Aug 2011 10:01:03 -0700 (PDT)
Received: from exchange.liveoffice.com (exchla3.liveoffice.com [64.70.67.188]) by ietfa.amsl.com (Postfix) with ESMTP id CDFB921F8C7B for <manet@ietf.org>; Mon, 15 Aug 2011 10:01:03 -0700 (PDT)
Received: from exhub13.exchhosting.com (192.168.11.122) by exhub05.exchhosting.com (192.168.11.101) with Microsoft SMTP Server (TLS) id 8.2.213.0; Mon, 15 Aug 2011 10:01:47 -0700
Received: from EXMBX13.exchhosting.com ([fe80::34:7540:6989:7b8d]) by exhub13.exchhosting.com ([::1]) with mapi; Mon, 15 Aug 2011 10:01:47 -0700
From: "A. Riley Eller" <reller@cococorp.com>
To: Vikram KAUL <vkaul@research.telcordia.com>, "manet@ietf.org" <manet@ietf.org>
Date: Mon, 15 Aug 2011 10:01:47 -0700
Thread-Topic: [manet] DLEP and broadcast/multicast
Thread-Index: AcxbXkci4/+BiQpISFOKZvWse5W0swADHRhA
Message-ID: <3D05610F3AC2E047AACAA68F63DF908D345B1AA01A@EXMBX13.exchhosting.com>
References: <alpine.WNT.2.01.1108151053430.5496@vkaul7-t61>
In-Reply-To: <alpine.WNT.2.01.1108151053430.5496@vkaul7-t61>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [manet] DLEP and broadcast/multicast
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 15 Aug 2011 17:01:04 -0000
Perhaps the DLEP specification would benefit from accepting a pseudo-link identifier for multicast messages? My team's research shows that EFT implementations achieve higher overall accuracy by measuring multicast messages as a universal estimator for queuing-plus-congestion. Giving DLEP the ability to describe that value, and also gaining the ability to control the radio's performance for multicast traffic, would be a valuable addition. -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Vikram KAUL Sent: Monday, August 15, 2011 8:15 AM To: manet@ietf.org Subject: [manet] DLEP and broadcast/multicast Folks I have some questions about how DLEP handles multicast/broadcast traffic and the intents that the router might have to send to the modem device. Some of this might have been answered; but I couldn't find it in the archives The inherent nature of DLEP seems focused on neighbor relationships and link characteristics (MDR, CDR, Latency, etc) are focused on individual neighbors as identifed by the 'MAC Address Sub-TLV' which is mandatory in most of the messages My question is related to broadcast and/or multicast traffic that would emanate from a router. Let us presume that the underlying multicast protocol is SMF for ease of discussion... but it could be anything that forwards native multicast packets, either via flooding or after creating trees. How can one use DLEP to specify the MDR/CDR or latency requirements for those flows ? Is it even possible to do so ? I understand how one could do it for individual links to neighbors. But if I presume that multicast and broadcast is the predominant traffic (say 70%-80%, and I don't believe I am wrong about that), how can one use DLEP "Link Characteristics Request Message" to specify that traffic to a particular MAC address should be able to get at least what is specified by the CDR Sub-TLV Typically (but not always) MAC addresses for multicast IP packets are set to 01:00:xx:yy:zz:aa for a destination multicast address of xx.yy.zz.aa. Could one not have that 01:00:xx:yy:zz:aa MAC Address Sub-TLV so that the modem could identify that traffic to that MAC Address (and hence traffic to that destination multicast IP address) needs to get at least that data rate. How the modems would achieve that is a separate question, but DLEP does not delve into those answers anyway Again, it might be that the charter for DLEP is to focus specifically on one-to-one relationships (and hence one-to-one specifications and conditions). Could the specs not be augmented to support something on one-to-many specifications ? Just thinking aloud. regards.. Vikram _______________________________________________ manet mailing list manet@ietf.org https://www.ietf.org/mailman/listinfo/manet
- [manet] DLEP and broadcast/multicast Vikram KAUL
- Re: [manet] DLEP and broadcast/multicast A. Riley Eller
- Re: [manet] DLEP and broadcast/multicast Vikram KAUL
- Re: [manet] DLEP and broadcast/multicast Stan Ratliff
- Re: [manet] DLEP and broadcast/multicast Joe Macker
- Re: [manet] DLEP and broadcast/multicast A. Riley Eller
- Re: [manet] DLEP and broadcast/multicast Stan Ratliff
- Re: [manet] DLEP and broadcast/multicast A. Riley Eller
- Re: [manet] DLEP and broadcast/multicast Vikram KAUL