[13:00:39] danny joins the room [13:21:22] lm joins the room [13:24:35] vladim joins the room [13:25:35] Karen O'Donoghue joins the room [13:26:01] Brian Haberman joins the room [13:26:09] NTP Status [13:26:13] 4 RFCs published [13:26:54] One document under discussion: draft-chen-ntps-ra-opt [13:27:27] Not sure if this work should be pursued [13:27:41] Call for additional NTP work items on the mailing list. [13:28:59] Holding off on discussing the advancement of the NTP specs beyond Proposed Standard. [13:30:02] no kidding [13:31:25] ITU Status is the next topic [13:32:30] Slide 2: Focus of Q13 [13:33:35] Three recommendations released focused on synchronization [13:34:01] Slide 3: IEEE 1588 Profiles [13:34:45] rdroms joins the room [13:34:46] Focus on PTP, but also interest in NTP for legacy interaction [13:35:28] Preference moving towards using packetized protocols [13:35:40] Slide 4: Document structure in Q13/15 [13:37:00] Slide 5: 1588 Telecom Profile [13:37:42] First profile focused on frequency transport [13:38:15] why is there no document on UDP over IPV6 like IEEE-2008 annexD? [13:38:17] Slide 6: G.8265,1 - Frequency distribution [13:38:42] Trasnport is unicast with future work to look at unicast/multicast mix [13:38:52] No security aspects considered [13:39:26] Management aspects will be specified in future versions of the profile [13:39:51] Danny - you mean 1588-2008 right? If so, I'll ask at the end of Stefano's presentation... [13:40:04] I will ask [13:40:11] oh... even better... [13:41:57] Slide 7: Time-Phase Requirements [13:44:01] Peter wants to know which UTC will be used to reach the 3 micro-second synchronization accuracy. [13:44:03] this is exact test than 3GPP2 text [13:44:07] text [13:44:35] Slide 8: ITU-T Recc. G.8271 [13:44:36] but this would be the "national" UTC - operator would have to use same UTC [13:45:01] Slide 9: 1588 Time Profile [13:45:50] Slide 10: Main Study Points [13:46:19] Slide 11: ITU-T Definitions and PDV Metrics [13:46:36] Slide 12: OTN Timing Aspects [13:47:04] End of presentation [13:47:25] Does anyone in the jabber room need me to provide additional information? [13:47:43] Next topic: 1588 MPLS encapsulation [13:48:33] Design team failed to produce a recommendation. [13:48:47] Slide on MPLS encapsulation options [13:51:38] Slide on "What we would need to do" [13:54:20] Question on why the special treatment is needed. [13:54:34] why do you need special treatment? [13:55:56] who is talking? [13:56:15] I don't know. He does not have a name tag on. [13:57:08] Point: we need to spell out what is needed and MPLS may have those tools already. [13:57:46] Point: work needed for signaling beyond a BCP [13:58:25] Point (Sasha): Doesn't understand the point on signaling a re-route. [13:59:50] Curtis V. : Routers have been running NTP for years. [14:00:25] Putting the timestamp in as close to the hardware has already been solved. [14:01:11] Point: TC and pseudo-wire are orthogonal points [14:01:48] Point: Need to work on the requirements first. What clocks are we working on? [14:02:38] Need to step back and work on requirements for all the environments. [14:03:20] Luca Martini: Define this as a network service. [14:03:41] Timing is an LSP label. [14:04:26] Impact on algorithms needs to be considered. [14:04:57] Next presentation: 1588 over MPLS [14:05:12] Slide 1: Requirements [14:05:48] Slide 2: Proposed Solution [14:06:58] Slide 3: UDP/IP Encapsulation [14:07:08] Slide 4: PW Encapsulation [14:07:26] Slide 5: Advantages [14:09:01] Slide 6: Future work [14:09:56] Martini Luca: Fine wrt encapsulation. Still needs signaling work. [14:11:11] Question: Is IP multicast supported? [14:11:28] Yes, it is supported. [14:11:55] Why do we need to flag the LSP with timing information? [14:12:37] Need to know that it is a timing packet [14:13:18] Point: Don't like it since it is a control packet. [14:14:08] Point: Not convinced that TC is needed. [14:14:23] Need it to reach microsecond synchronization [14:14:45] Peter Lothberg: Make sure that packet is not hard-coded. [14:15:27] Stefano: Existing 1588 profiles allows synchronization over MPLS. [14:15:45] rdroms leaves the room [14:15:55] Marc: Should re-order options to reflect what is viable. [14:16:19] But does like the proposal. Thinks it is the easiest way. [14:16:38] Next presentation: PTP over MPLS(?) [14:16:51] Slide 1: Transports [14:17:27] Slide 2: PTP Sync/Delay Packet Format [14:17:52] Ron Cohen? [14:17:52] Slide 3: Scenarios [14:18:03] Yes - Cohen is presenting [14:18:52] Slide 4: PTP Transport Service [14:20:02] Slide 5: Desired SLA [14:21:14] Slide 6: Main Requirement [14:23:06] Slide 7: More to handle... [14:23:38] Slide 8: Alternative: Distributed TC Approach [14:25:07] Slide 9: Direct PTP over MPLS [14:26:39] Peter Lothberg: How big is the network? [14:26:54] 20 hops is not unreasonable. [14:27:09] How large (in kilometers)? [14:28:16] Laws of physics will impact the synchronization. [14:28:35] Craig Schultz: Assume you can time synch the boundaries. [14:28:53] Need to use 1588 to get the clock to the edge devices. [14:29:37] Cohen: two scenarios, depends on who is being synchronized. [14:30:27] Craig: Have the affects of the transport on the clock been investigated? [14:30:40] Some studies done in 1588 [14:31:25] different timescale? [14:31:46] Slide: Internal Synchronization [14:32:22] Slide: Why Not PTP over Layer 2 [14:32:53] are the two internal source unsynchronized with each other and does that matter? [14:33:38] Slide: Using MPLS Protection [14:34:23] Danny, depends on the application; it may be 2+ distinct timing domains, e.g., MB SFN domains [14:34:50] Slide: And p2mp Sync Distribution [14:35:11] Slide: Why Not IP over MPLS? [14:35:41] Slide: Summary [14:35:43] that's scary (to me) [14:36:32] @danny: I think it is due to the desire to not route the traffic off the MPLS network [14:36:55] so that needs to be clarified [14:36:56] Next presentation: 1588v2 Clock Synch (Jin) [14:37:10] Slide 1: Requirement Analysis [14:37:38] Actuall, it is labeled as Slide 2 [14:37:47] Slide 3: Current Problem [14:38:21] Slide 4: Deployment with P2MP... [14:38:40] Lots of animation [14:39:34] Slide 5: Solution Description [14:40:31] Slide 6: Solution Description (cnt) [14:40:40] s/(cnt)/(cont) [14:41:39] Slide 7: PROS & CONS [14:42:16] Slide 8: Next steps [14:43:00] Yaakov: How do you know the delays for the slaves? [14:43:12] Delay times based on the slave ID [14:43:33] Next presentation: Security [14:43:50] Slide 2: Introduction [14:44:06] Slide 3: Security and Timing [14:44:50] Slide 4: Mobile Backhaul [14:46:15] Slide 5: Handling of timing packets and IPsec [14:47:13] why are the packets being encrypted in the first place? It's not confidential data [14:47:45] Slide 6: Identifying PTP packets in IPSEC [14:48:12] @danny: requirements slide mentioned a possible need for confidentiality [14:48:28] Slide 7: NTP and PTP Security Schemes [14:48:48] Slide 8: Conclusions [14:49:18] of a timing packet? [14:49:30] @danny: *shrug* [14:49:48] Next presentation: Security requirements of 1588 [14:49:53] Slide 2: Background [14:50:16] Slide 3: Background [14:51:14] Slide 4: Issue cases in entire protection [14:52:40] Slide 5: Discussion [14:53:20] Next presentation: Management requirements [14:53:42] I really need to understand why the timestamp packet needs to be encrypted as it makes no sense to me. [14:53:47] slide 2: Purpose of draft [14:54:06] @danny: Guess that is a good topic for the tictoc mailing list [14:54:15] Slide 3: Elements of sync management [14:54:23] Slide 4: Issues to be resolved [14:57:21] Second presentation on a PTP MIB [14:57:33] Slide 2: Purpose of Draft [14:58:09] Slide 3: Contents of MIB [14:58:23] should it also be aligned with the NTP MIB or are they too different? [14:59:32] Slide 4: Issues to be resolved [15:00:21] Presentation concluded [15:01:11] Sorry folks, but I have to drop out to go chair another session. [15:01:19] :) [15:01:30] Brian Haberman leaves the room [15:02:10] thanks bryan [15:03:53] we cannot discuss work-in-process that is not publically available [15:04:42] it's an IETF requirement [15:05:09] Karen O'Donoghue leaves the room [15:05:44] vladim leaves the room [15:06:50] lm leaves the room [15:33:42] Karen O'Donoghue joins the room [15:41:21] danny leaves the room [18:25:37] Karen O'Donoghue leaves the room [22:02:06] Karen O'Donoghue joins the room [22:03:36] Karen O'Donoghue leaves the room: Replaced by new connection [22:03:36] Karen O'Donoghue joins the room [23:17:40] Karen O'Donoghue leaves the room