Subject: [PWE3] OAM capability indication issue

From: Jixiong Dong <[email-masked]>
Date: Thu, 29 Sep 2005 17:19:44 +0800

Hi, all,

During establishing a PW, source U-PE(U-PE1) will use the VCCV interface parameter field in the PW setup message to indicate its OAM capabilities. When the setup message arrives the peer PE(U-PE2), it will choose certain capability or capabilities according to local policy. When U-PE2 establishs the reverse PW, it has two ways to indicate the OAM capability in the setup message:

1. indicates all OAM capabilities U-PE2 supports.

2. indicates the capabilities choose by U-PE2 during the former PW setup procedure(from U-PE1 to U-PE2).

If we adopt the former, it may cause the different OAM mechanism existed in the different direction of the PW, because the local policy of U-PE1 and U-PE2 is maybe different.

If we adopt the latter, then the OAM mechanism of both PW directions is same.

I suggest we should adopt the latter. Welcome for comments.

Dong
_______________________________________________
pwe3 mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/pwe3