Re: Comments on ULE extension header....

[Gorry Fairhurst <gorry@erg.abdn.ac.uk>]

On Ethernet bridging...

On 8/6/04 12:59 pm, "William StanisLaus" <williams@calsoft.co.in> wrote:

> Please see the comments inlined...
> 
> -William.
> 
>> -----Original Message-----
>> From: owner-ipdvb@erg.abdn.ac.uk
>> [mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Gorry Fairhurst
>> Sent: Tuesday, June 08, 2004 3:20 PM
>> To: ipdvb@erg.abdn.ac.uk
>> Cc: Bernhard Collini-Nocker
>> Subject: Re: Comments on ULE extension header....
>> 
>> 
>> On 7/6/04 7:30 pm, "williams@calsoft.co.in"
>> <williams@calsoft.co.in> wrote:

<snip>

> 
> 
>>> In Optional headers, Wish to add Source mac address... In case of
>>> UDLR(RFC3077), during DTCP announcement, ULE can take the
>> source mac i.e.
>>> FUMAC makes simple in address resolution. -UDLR is jst an example.
>>> otherthings are security filters can be implemented based
>> on source MAC.
>>> 
>> 
>> Yes - this is true.
>> 
>> We had a discussion on this topic at the Vienna BoF, and at
>> that time I
>> don't recall a need for a MAC source without a MAC
>> destination address. If
>> that is still the case, then maybe the bridging format extension would
>> satisfy this requirement?
>> 
>> Thoughts?
> 
> 
> William> In case of UDLR, it is not a packet forwarding, the orginator
> of the packet is the FEED itself i.e. satellite terminal. My understand
> with bridged format packets is sending the ethernet packets along with
> L2 information in satellite network, i.e. L2 tunneling. In that you
> still have outer ULE and MPEG headers.
> Please correct if I'm wrong.
> 

So I'd guess if you wanted a source MAC address, an example is:

<base ULE header, (D=1)> <Bridging header><payload><crc-32>

I.e.:


<Len,Type=bridging, (D=1)> <MAC-dst;MAC-src;Ether-Type><payload><crc-32>

>> 
>>> -William
>>> 
>>> 
>>> --------------------------------------------------------------------
>>> mail2web - Check your email from the web at
>>> http://mail2web.com/ .
>>> 
>> 
>> Gorry Fairhurst
>>> 
>> 
>