[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [PWE3] RE: [802.1] 802.1ad Customer FCS Retention
- To: <stbryant@cisco.com>
- Subject: RE: [PWE3] RE: [802.1] 802.1ad Customer FCS Retention
- From: neil.2.harrison@bt.com
- Date: Mon, 24 Nov 2003 09:02:03 -0000
- Cc: <kgk@igs.net>, <jmessenger@advaoptical.com>, <nfinn@cisco.com>, <mark@interflect.com>, <stds-802-1@ieee.org>, <pwe3@ietf.org>, <Maarten.Vissers@alcatel.de>, <alan.mcguire@bt.com>
- List-help: <mailto:pwe3-request@ietf.org?subject=help>
- List-id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
- List-post: <mailto:pwe3@ietf.org>
- List-subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,<mailto:pwe3-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,<mailto:pwe3-request@ietf.org?subject=unsubscribe>
- Sender: pwe3-admin@ietf.org
- Thread-index: AcOyIXxHJTttl7nPQweG3XVURu+34gACKBHA
- Thread-topic: [PWE3] RE: [802.1] 802.1ad Customer FCS Retention
> >>If you assume a PW to be a sort of bridge,
> >
> > NH=> A PW is for sure not a bridge! A PW is an adaptation funtion
> > that lies between a client layer network and a server layer network
> > of MPLS or IP.
>
> Neil
>
> Surely that is just one way to model the PW? Can't a PW also be
> modelled as a repeater with certain internal delay and error
> characteristics.
>
> Stewart
Stewart,
If this is a valid analogy then every networking technology that relays some traffic unit between points A and B can be regarded as modelling a bridge.....and that does not seem a good analogy to me.
regards, Neil
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3