[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PWE3] Re: Questions concerning draft-dong-pwe3-mspw-oam-00.txt



Simon,
 
I am very glad to see that you are interesting in the internet-draft about MS-PW OAM. Thank you very much for giving me very profound information.
 
Please see below.
 
Best regards,
Dong
----- Original Message -----
Sent: Thursday, October 20, 2005 8:56 AM
Subject: Questions concerning draft-dong-pwe3-mspw-oam-00.txt

Dear Jixiong,
My name's Simon Delord and I am part of the OAM work for both PWE3 and L2VPN WGs. Philippe Niger (Cc) from France Telecom is also interested in this work.
I've read with great interest your draft and I have a couple of questions regarding MSPW-OAM.
 
Here are the questions:
 
   - figure 4 shows the FDI packet format: is this the packet that is encapsulated over the CW on the PW? or is it an LDP extension?
[DONG] The FDI packet is encapsulated as the OAM payload of the VCCV packet format. So it's suitable for the PW with CW or without CW. In case of PW with CW, VCCV packet = CW + OAM payload, where CW uses the format in figure 5 and OAM payload is FDI packet format in figure 4. In case of PW without CW, VCCV packet = OAM packet in figure 6, where OAM payload is FDI packet. It is not an LDP extension.
 
   - it is stated that : "When the U-PE of a MS-PW received a FDI packet, it will send PW
   status TLV to the peer side U-PE of the MS-PW to notify the current
   MS-PW status. " => would it be possible to use an RDI mechanism instead of an LDP message to notify the remote U-PE? I believe that a SP worry would be to rely on the control plane to carry alarm indication instead of the data plane.
[DONG] Thank you for giving a key problem. I have the following considerations: a. There is only FDI requirement, NO RDI requirement, in MS-PW requirement document(draft-martini-pwe3-MH-PW-requirements). b. I miss one point, that is, we can use BFD notify e2e PW status if VCCV-BFD is used. This point has been indicated in oam-map document. c.If VCCV-BFD is not used, how to do it? Maybe RDI requirement should be introduced into MS-PW requirement document. Welcome for the comments from Luca and NB.
 
  - in the inter-AS case, what happens if one SP does not want to send any IP information about its S-PEs to a distant U-PE located in a remote AS? how do we proceed with that, do we imagine some sort of Proxy mode at one AS-BR?
[DONG] You are very right. However Maybe this depend on the progress of the MS-PW control protocol. If S-PE have the AGI/TAII/SAII information, I think we should use these information.
 
 - I think there are some "typo" mistakes in page 9: CV type of 0x08 should be 0x10, 0x10 should be 0x20, etc...
[DONG] It's not an error. You may refer to page 9 of VCCV document.
 
 - I am not too sure to understand how the FDI message and the LDP status relate to each other. Would you by the way, have some sort of powerpoint presentation that would help us understand how you want to implement this solution?
[DONG] I have no ppt presentation now. If the above answer 1 can't eliminate your doubt, I can make one presentation for you.
 
thanks in advance for your help,
                             Simon


 
2005/10/13, Jixiong Dong <dongjixiong at huawei.com>:
Dear all,

we have submitted the following draft for consideration by the PWE3 WG.
http://www.ietf.org/internet-drafts/draft-dong-pwe3-mspw-oam-00.txt
 
We look forward to feedback from pwe3 members. All comments and suggestions
are welcome.
 
Best Regards,
Dong
 
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title : Operation and Maintenance for Multi-segment Pseudo Wire
Author(s) : J. Dong
Filename : draft-dong-pwe3-mspw-oam-00.txt
Pages : 13
Date : 2005-10-10

   This draft proposes a method for operation and maintenance on the
   multi-segment pseudo wires (MS-PWs). It extends and is compatible
   with the existing single-segment pseudo wire OAM mechanism [VCCV].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-dong-pwe3-mspw-oam-00.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request at ietf.org with the word unsubscribe in the body of the message. 
You can also visit
https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
"get draft-dong-pwe3-mspw-oam-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or
ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
mailserv at ietf.org.
In the body type:
"FILE /internet-drafts/draft-dong-pwe3-mspw-oam-00.txt".

NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility.  To use this
feature, insert the command "ENCODING mime" before the "FILE"
command.  To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader.  Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


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



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