[no subject]

-----Original Message-----
From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On Behalf Of
neil.2.harrison@bt.com
Sent: Thursday, November 13, 2003 3:02 AM
To: Shahram_Davari@pmc-sierra.com; tnadeau@cisco.com; pwe3@ietf.org
Subject: RE: [PWE3] Adopt draft-nadeau-pwe3-oam-msg-map-03.txt as PWE3
WG draft?


As Dave Allan pointed out earlier, there is a document on ATM and MPLS
peer OAM I/W....it is Y.1712.  Its simple and complete.  This should not
be ignored.

regards, Neil

> -----Original Message-----
> From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> Sent: 13 November 2003 06:03
> To: 'tnadeau@cisco.com'; pwe3@ietf.org
> Subject: RE: [PWE3] Adopt draft-nadeau-pwe3-oam-msg-map-03.txt as PWE3

> WG draft?
>=20
>=20
> I think A document on OAM Interworking between PW and ATM/FR
> is needed.
> Does that mean any draft with this title should be accepted?
>=20
> -Shahram
>=20
> >-----Original Message-----
> >From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
> >Sent: Wednesday, November 12, 2003 6:28 PM
> >To: pwe3@ietf.org
> >Subject: RE: [PWE3] Adopt
> draft-nadeau-pwe3-oam-msg-map-03.txt as PWE3
> >WG draft?
> >
> >
> >
> >	Although a valid point for discussion, the real question
> >should be whether a document in question is useful to the WG=20
> >or not.  If it is, we can discuss the details on the list,
> >as is normal IETF policy. =20
> >
> >	--Tom
> >
> >
> >>-----Original Message-----
> >>From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On
> >>Behalf Of Shahram Davari
> >>Sent: Wednesday, November 12, 2003 12:04 PM
> >>To: 'neil.2.harrison@bt.com'; tnadeau@cisco.com; pwe3@ietf.org
> >>Subject: RE: [PWE3] Adopt draft-nadeau-pwe3-oam-msg-map-03.txt=20
> >>as PWE3 WG draft?
> >>
> >>
> >>Right. So only AIS/FDI and Down state are mappable. The down
> >>state of MPLS layer (using CV or periodic ping) is used to=20
> >>generate AIS on the client layer (i.e., ATM, or FR). Also an=20
> >>FDI in MPLS layer could be used to generate AIS on client=20
> >>layer (ATM/FR).
> >>
> >>If the PEs don't support transport of ATM/FR AIS/RDI, then in
> >>theory it is possible (although not architecturally clean) to=20
> >>use some sort of signaling/message in MPLS network to inform=20
> >>the egress PE to generate the AIS/RDI on the ATM/FR connections.
> >>
> >>-Shahram
> >>
> >>
> >>
> >>>-----Original Message-----
> >>>From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
> >>>Sent: Wednesday, November 12, 2003 12:45 PM
> >>>To: Shahram Davari; tnadeau@cisco.com; pwe3@ietf.org
> >>>Subject: RE: [PWE3] Adopt
> >draft-nadeau-pwe3-oam-msg-map-03.txt as PWE3
> >>>WG draft?
> >>>
> >>>
> >>>Hi Shahram.....to be strictly accurate here, in a
> >>>client/server networking I/W case the only server->client OAM=20
> >>>function mapping that is relevent is FDI (or AIS in old=20
> >>>currency).  RDI stays within the layer/trail it is relevant=20
> >>>to.....it has no upwards mapping from server->client in a=20
> >>>'backwards direction' (if you see what I mean) but terminates=20
> >>>at the trail sink of the return direction (if one exists).
> >>>
> >>>Otherwise I agree with your remarks.
> >>>
> >>>regards, Neil
> >>>> -----Original Message-----
> >>>> From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> >>>> Sent: 12 November 2003 16:49
> >>>> To: 'tnadeau@cisco.com'; pwe3@ietf.org
> >>>> Subject: RE: [PWE3] Adopt
> >>>draft-nadeau-pwe3-oam-msg-map-03.txt as PWE3
> >>>> WG draft?
> >>>>=20
> >>>>=20
> >>>> Hi,
> >>>>=20
> >>>> The only OAM function that is mappable in a network
> >>>> interworking case (e.g., PW)
> >>>> is AIS/RDI and up/down state. Any other type of mapping is=20
> >>>> not only architecturally wrong, but not required.
> >>>>=20
> >>>> So I suggest that first we have a debate on the higher level
> >>>> architectural issues
> >>>> and requirements before accepting this draft.
> >>>>=20
> >>>> Yours,
> >>>> -Shahram
> >>>>=20
> >>>>=20
> >>>> >-----Original Message-----
> >>>> >From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
> >>>> >Sent: Monday, November 10, 2003 10:47 PM
> >>>> >To: pwe3@ietf.org
> >>>> >Subject: [PWE3] Adopt draft-nadeau-pwe3-oam-msg-map-03.txt
> >>>as PWE3 WG
> >>>> >draft?
> >>>> >
> >>>> >
> >>>> >
> >>>> >	The chairs requested that we take the
> >>>> >matter of adoption of this draft to the
> >>>> >list. Please comment.
> >>>> >
> >>>> >	--Tom
> >>>> >
> >>>> >http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-m
> >>>> ap-03.txt
> >>>>=20
> >>>>=20
> >>>>=20
> >>>> _______________________________________________
> >>>> pwe3 mailing list
> >>>> pwe3@ietf.org https://www1.ietf.org/mailman/listinfo/pwe3
> >>>>=20
> >>>> _______________________________________________
> >>>> pwe3 mailing list
> >>>> pwe3@ietf.org https://www1.ietf.org/mailman/listinfo/pwe3
> >>>>=20
> >>>
> >>
> >>_______________________________________________
> >>pwe3 mailing list
> >>pwe3@ietf.org
> >>https://www1.ietf.org/mailman/listinfo/pwe3
> >>
> >
> >
> >
> >_______________________________________________
> >pwe3 mailing list
> >pwe3@ietf.org
> >https://www1.ietf.org/mailman/listinfo/pwe3
> >
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3