
From internet-drafts@ietf.org  Mon Feb  6 01:51:33 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A1C121F8608; Mon,  6 Feb 2012 01:51:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upcZDLfFm0Kz; Mon,  6 Feb 2012 01:51:33 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FDBD21F85C9; Mon,  6 Feb 2012 01:51:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120206095118.17322.58756.idtracker@ietfa.amsl.com>
Date: Mon, 06 Feb 2012 01:51:18 -0800
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-ptp-mib-01.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2012 09:51:33 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Timing over IP Connection and Transfe=
r of Clock Working Group of the IETF.

	Title           : Precision Time Protocol Version 2 (PTPv2) Management Inf=
ormation Base
	Author(s)       : Vinay Shankarkumar
                          Laurent Montini
                          Tim Frost
                          Greg Dowd
	Filename        : draft-ietf-tictoc-ptp-mib-01.txt
	Pages           : 66
	Date            : 2012-02-06

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP-based internets.
   In particular, it defines objects for managing networks using
   Precision Time Protocol.

   This memo specifies a MIB module in a manner that is both compliant
   to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
   definitions.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tictoc-ptp-mib-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-tictoc-ptp-mib-01.txt


From stefano.ruffini@ericsson.com  Mon Feb 13 07:53:04 2012
Return-Path: <stefano.ruffini@ericsson.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF9BD21F862A for <tictoc@ietfa.amsl.com>; Mon, 13 Feb 2012 07:53:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cAHBEs2kM4RZ for <tictoc@ietfa.amsl.com>; Mon, 13 Feb 2012 07:53:02 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id CECFF21F8508 for <tictoc@ietf.org>; Mon, 13 Feb 2012 07:53:01 -0800 (PST)
X-AuditID: c1b4fb3d-b7bb7ae0000007b2-41-4f3931dca888
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 10.5D.01970.CD1393F4; Mon, 13 Feb 2012 16:53:00 +0100 (CET)
Received: from ESESSCMS0360.eemea.ericsson.se ([169.254.1.48]) by esessmw0256.eemea.ericsson.se ([153.88.115.96]) with mapi; Mon, 13 Feb 2012 16:53:00 +0100
From: Stefano Ruffini <stefano.ruffini@ericsson.com>
To: "davari@broadcom.com" <davari@broadcom.com>, "manav.bhatia@alcatel-lucent.com" <manav.bhatia@alcatel-lucent.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Mon, 13 Feb 2012 16:52:59 +0100
Thread-Topic: [TICTOC] FW:  I-D Action: draft-ietf-tictoc-1588overmpls-02.txt
Thread-Index: AcyEsdD7iw8R1PGDSO67KTR0LIlKkgAAnsgQGRBCKVA=
Message-ID: <28C9B1CD4D27844E9CD8F02BFEB705642678F2D417@ESESSCMS0360.eemea.ericsson.se>
References: <7C362EEF9C7896468B36C9B79200D8350D005EA98E@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350D005EA98E@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: it-IT, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [TICTOC] FW: I-D Action: draft-ietf-tictoc-1588overmpls-02.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2012 15:53:04 -0000

Dear Manav, Sharham, 1588 over mpls draft Authors=20

 I have collected some notes on version 02 of the 1588 over MPLS draft that=
 may be considered for future versions of the document.=20

1) In general the draft needs some clean-up. In particular as also highligh=
ted in previous discussions (e.g. in Taipei) some of the aspects to be addr=
essed are outside the scope of TICTOC, and a review with the MPLS WG will c=
ertainly be required. For instance the description of the protocol - partic=
ularly with respect to how layering is modeled in the behavior of an LSR.=20
Section 16 (e.g. the description of LER behavior in section 16.1) should be=
 among the main parts to be checked by the MPLS WG.=20
The CCAMP WG should also be involved in the review .=20

2) There is a serious mismatch between what is currently in the introductio=
n and what the rest of the draft includes. Most notably, the introduction s=
eems to imply that only 1588 PTP messages are transported while it is clear=
 from the abstract and in subsequent sections (10 and 16, particularly) tha=
t other message types may also be transported on the same LSP.=20
In addition more information should be added with respect to the required r=
outing and signaling extensions. In particular the introduction should list=
 at least well-known and commonly used routing and signaling protocols, inc=
luding those for which the draft currently defines extensions and why other=
s are considered out of scope.=20

3) Section 3 and 4 could be expanded to better explain the various 1588 net=
work scenarios and applicability of the draft to these scenarios .
In fact , although as explained in section 4, the main scenario of interest=
 for this draft is with LSRs implementing (E2E?) TC, and BC implemented in =
the LERs, it seems that other scenarios could be of interest or at least th=
e applicability of the draft could be better clarified (e.g. indicating the=
 benefits, if any, in using the features described in the draft).
 For instance some of the scenarios that should be considered are:=20
- BC in the LERs, and 1588 unaware LSRs
- BC in the LERs, and LSRs with P2P TC=20
- Boundary clocks in every node, which is currently the main scenario being=
 studied in ITU-T.=20

Finally, assuming the TC layer violation is addressed by terminating the PT=
P at every hop (i.e. also in the LSR-TC), how would this case be addressed =
by the draft ?

4) The Introduction reads:=20
"This document provides two methods for transporting PTP messages over MPLS=
. One is principally focused on an IP/MPLS environment and the second is fo=
cused on the MPLS-TP environment."
Section 6.1. explains that the mapping described in this section is suitabl=
e for IP/MPLS networks.
A similar consideration should be added in 6.2 as relevant for MPLS-TP. For=
 instance the MPLS-TP related assumptions should be made clear in this sect=
ion. Perhaps title of these sections might be revised.=20

5) Section 5=20
The discussion on using P2P or P2MP LSP ("The PTP LSP between Master Clocks=
 and Slave Clocks MAY be P2MP or P2P LSP while the PTP LSP between
   each Slave Clock and Master Clock SHOULD be P2P LSP.") could be describe=
d more in detail (e.g. adding the rationales) or perhaps removed. It may al=
so be related to the specific profile used. =20

6) Section 14.1 and 14.2:=20
only 1 bit is currently defined (C) for the 1588aware link capability infor=
mation
If relevant (see also comment 3), the authors could consider to distinguish=
 already at this stage several cases (E2E TC, P2P TC, BC, etc.), allocating=
 more bits, rather than leaving everything for future use.

7) Section 16.3
The definition of "non-1588-aware LSR" may need to be revised: the current =
definition seems to mix the capability of handling PTP packets with the cap=
ability of handling the RSVP-TE extensions. I think it would be better to u=
se different terms for these cases.

Best Regards
Stefano=
