Subject: [TICTOC] Questions regaridng 1588 over MPLS

From: "Shahram Davari" <[email-masked]>
Date: Tue, 31 Jul 2012 21:03:54 +0000

Hi,

During today's TICTOC meeting I raised the following questions. We need your feedback on these questions in order to progress this draft.

  1.  Should CW be mandatory?
     *   If not, then a PTP-LSP needs to carry only one type of PW (either with CW or without CW) but not mix so that LSRs can correctly parse the packet
     *
     *   Without PW the job of LSRs becomes more complex to identify the OAM packets
  2.  Should ECMP/Entropy be disallowed?
     *   The current consensus is yes, no ECMP or Entropy shall be used.
  3.  Should PHP (Penultimate Hop Popping) be allowed?
  4.  How to transport 1588 messages that don't need TS or CF update?
     *   Send them over non-PTP LSP?
     *   Let the LSRs do the parsing and perform TS or CF updated based on message type?
  5.  Should P2MP LSP & P2MP PW be supported?
  6.  Should protection be supported for PTP-LSP?
     *   FRR, 1:1 and 1+1
  7.  How does LSP/PW connectivity failure interact with 1588?
     *   Does the Slave select another master when a failure happens?
     *   Can the protection make the failure invisible to Salve clock?
  8.  Should only VCCV1 and VCCV4 be allowed?
     *   If not then the VCCV type needs to be the same for all PW in the PTP-LSP so that LSRs can correctly parse the packet

Thank you,

[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: cid:[email-masked]]

Shahram Davari | Technical Director, Network Switching Group
Broadcom Corporation | (O) 408-922-7436 | (M) 408-660-5695

[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image005]<http://www.linkedin.com/company/broadcom>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image002]<http://twitter.com/#!/broadcom>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image003]<https://www.facebook.com/Broadcom>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image004]<https://plus.google.com/109188783526874806673/posts#109188783526874806673/posts>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image006]<https://www.youtube.com/user/BroadcomCorporation>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image008]<http://blog.broadcom.com/>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image007]<http://broadcom.com/>