![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hi Ben, Basically I want to understand whether PID is required for OAM or not? Also is OAM a type of MCC traffic? Thanks, Shahram -----Original Message----- From: benjamin.niven-jenkins at bt.com [mailto:benjamin.niven-jenkins at bt.com] Sent: Monday, September 21, 2009 4:32 PM To: Shahram Davari; ietf at ietf.org; ietf-announce at ietf.org Cc: mpls at ietf.org Subject: RE: [mpls] Last Call: draft-ietf-mpls-tp-nm-req (MPLS TP Network Management Requirements) to Proposed Standard Sharam, The draft describes network management requirements and at most states that OAM must be configurable by network management. It presupposes nothing about the OAM mechanism used or now the individual network elements (LSRs) recognise the OAM packets themselves. So I don't understand your question in regards to the draft as the question you ask is not relevant within the scope of the draft. Ben ________________________________________ From: mpls-bounces at ietf.org [mpls-bounces at ietf.org] On Behalf Of Shahram Davari [davari at broadcom.com] Sent: Tuesday, September 22, 2009 12:24 AM To: ietf at ietf.org; IETF-Announce Cc: mpls at ietf.org Subject: Re: [mpls] Last Call: draft-ietf-mpls-tp-nm-req (MPLS TP Network Management Requirements) to Proposed Standard Hi, Just for clarification, does this draft require using a PID for BFD and LSP-ping? If not how are the various OAM types identified? Thanks, Shahram -----Original Message----- From: mpls-bounces at ietf.org [mailto:mpls-bounces at ietf.org] On Behalf Of The IESG Sent: Monday, September 21, 2009 3:54 PM To: IETF-Announce Cc: mpls at ietf.org Subject: [mpls] Last Call: draft-ietf-mpls-tp-nm-req (MPLS TP Network Management Requirements) to Proposed Standard The IESG has received a request from the Multiprotocol Label Switching WG (mpls) to consider the following document: - 'MPLS TP Network Management Requirements ' <draft-ietf-mpls-tp-nm-req-05.txt> as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf at ietf.org mailing lists by 2009-10-05. Exceptionally, comments may be sent to iesg at ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-nm-req-05.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18244&rfc_flag=0 _______________________________________________ mpls mailing list mpls at ietf.org https://www.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls at ietf.org https://www.ietf.org/mailman/listinfo/mpls
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.