Re: [nsp] Hi

From: Bert Kellerman (bertke@charter.net)
Date: Sun Nov 26 2000 - 06:06:28 EST


Sorry I don't have word so I can't view the doc. A jpg, pdf, or ascii
drawing is generally better to send to a public list. :)

Based on the RFC you have 2 methods to do this:

1. Multiplex on the VC(use a different VC for each protocol)
2. Stick an LLC header(with possiblly a SNAP header also) in the AAL5
Payload, before the PDU

With each method there are also different frame formats for routed and
bridged protocols, respectively.

Here is a link to the RFC. It explains it better than I could so check
it out, it's actually not a bad read.

http://www.cis.ohio-state.edu/htbin/rfc/rfc1483.html

Also, here are some cisco configuration links.

http://www.cisco.com/warp/public/121/routed_rfc1483.html
http://www.cisco.com/warp/public/121/18.html#bridged

Bert

TellapatiNaidu wrote:
>
> Hi,
> This is T.R.Naidu from India.I have a question regarding ATM/Ethernet
> Bridging.
>
> ( Please verify the small attched diagram)
>
> Suppose an application is running on the bridge ,between
> ATM interface and Ethernet Interface.I have a PVC between two bridges and all
> the nodes have the same subnet address.Suppose my application running on
> bridge H1 wishes to transport packets only to node H20 directly from IP
> ,should I use a separate PVC using encapsulation of routed IP protocol ? I
> have only one PVC for bridged protocols. To be frank I am not at all clear
> with the Bridge Concept with this regard.And also if I want to transport
> bridged PDUs from H20 to H1 and H11 how will be the flow.What should be the
> functionality of the Bridge with this regard ? Especially I am not clear with
> flow of Multicast and Broadcast frames from H20 to any other node.All the
> nodes are in the same LAN.
> Any help will be greately appreciated.
> With regards,
> T.R.Naidu.
> INDIA.
>
>
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
>
> ------------------------------------------------------------------------
> Name: doc.doc
> doc.doc Type: Microsoft Word Document (application/msword)
> Encoding: base64



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:22 EDT