[manet] DLEP and broadcast/multicast

Vikram KAUL <vkaul@research.telcordia.com> Mon, 15 August 2011 15:13 UTC

Date: Mon, 15 Aug 2011 11:14:30 -0400
From: Vikram KAUL <vkaul@research.telcordia.com>
To: manet@ietf.org
Message-ID: <alpine.WNT.2.01.1108151053430.5496@vkaul7-t61>
User-Agent: Alpine 2.01 (WNT 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Subject: [manet] DLEP and broadcast/multicast
Precedence: list

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