Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: [RPRWG] A question on IP over RPR




I think, providing appropriate registers where things can be read, is a good
idea. Even special service interfaces signals may be fine. However, in the
interest of speed, it would be advisable to limit .17 to Layer 2 only.
Ofcourse the signals and/or register bits will be defined keeping the
requirements of IP/ RTP in mind.

Regards,
Devendra Tripathi
VidyaWeb (India) Pvt Ltd.
(Subsidiary of CoVisible Solutions Inc.)
Pune, India
Tel: +91-20-433-1362

> -----Original Message-----
> From: Mike Takefman [mailto:tak@xxxxxxxxx]
> Sent: Tuesday, February 05, 2002 10:28 PM
> To: Devendra Tripathi
> Cc: Jim Forster; lcwang@xxxxxxx; stds-802-17@xxxxxxxx
> Subject: Re: [RPRWG] A question on IP over RPR
>
>
> Speaking with my Cisco Hat on,
>
> we have received so much customer feedback that RPR should have
> the hooks in to allow layer 3 to control / select various things
> like ring selection. I believe the standard should allow either
> layer 2 or layer 3 to control it. When layer 3 knows some things
> about what is going on below, it can make better decisions.
>
> mike
>
>
> > I am wondering, if the ring management should be left to RPR
> layer only. It is very similar to Link aggregation (802.3ad) which
> > also provides fault tolerance.
> >
> > Regards,
> > Devendra Tripathi
> > VidyaWeb (India) Pvt Ltd.
> > (Subsidiary of CoVisible Solutions Inc.)
> > Pune, India
> > Tel: +91-20-433-1362
> >
> >        -----Original Message-----
> >        From: owner-stds-802-17@xxxxxxxxxxxxxxxxxx
> [mailto:owner-stds-802-17@xxxxxxxxxxxxxxxxxx]On Behalf Of
> >        Jim Forster
> >        Sent: Thursday, January 31, 2002 10:57 PM
> >        To: lcwang@xxxxxxx; stds-802-17@xxxxxxxx
> >        Subject: RE: [RPRWG] A question on IP over RPR
> >
> >        Briefly, the L3 (IP) to L2 (RPR) binding is very similar
> to  that on Ethernet, with an extension.  IP on Ethernet uses
> >        ARP to determine the MAC address corresponding to the
> next-hop IP address.  On RPR we need this but we also
> >        need a direction bit, or Ring ID -- which Ring, Inner or
> Outer to use.  So ARP proceeds pretty much like on
> >        Ethernet to determine the next-hop MAC address.  Then
> RPR topology information is consulted to determine
> >        which ring to use, and the result stored along with the
> IP-MAC address binding information.
> >
> >          -- Jim
> >
> >              -----Original Message-----
> >              From: owner-stds-802-17@xxxxxxxxxxxxxxxxxx
> >              [mailto:owner-stds-802-17@xxxxxxxxxxxxxxxxxx]On
> Behalf Of lcwang@xxxxxxx
> >              Sent: Thursday, January 31, 2002 1:12 AM
> >              To: stds-802-17@xxxxxxxx
> >              Subject: [RPRWG] A question on IP over RPR
> >              Importance: High
> >
> >              A question of IP over RPR.
> >
> >              According to IP address, using routing protocol, a
> data forwarding route can be selected. On
> >              the other hand, RPR may transfer data through
> >              its ring on both direction. How can consistency of
> L3 and L2 data transfer be guaranteed?
> >
> >              Can someone explian this? Thanks.
> >
> >              Leo Wang
> >
> >
> >
> >
> >              __________________________________________
> >
> >              È«³¡ÌؼۣºÊýÂëÃ?Ã
> »ú¡¢ÕÆÉ�µçÄÔ¡¢MP3
> >              http://shopping.263.net/category21.htm
> >              ÌìÓ®³´¹É,ÌìÉúÎÒÓ®!
> >              http://stock19.263.net/download/borntowin.htm
>
>
>
> --
> Michael Takefman              tak@xxxxxxxxx
> Manager of Engineering,       Cisco Systems
> Chair IEEE 802.17 Stds WG
> 2000 Innovation Dr, Ottawa, Canada, K2K 3E8
> voice: 613-254-3399       fax: 613-254-4867
>