From: "Meyer, Peter" <Peter.Meyer@microsemi.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>,
 "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] draft-ietf-tictoc-1588overmpls-06 comments
Thread-Index: AQHPYwCgrZZS4dYWj0irju9oTrbzeg==
Date: Mon, 28 Apr 2014 16:40:48 +0000
Message-ID: <13F67EA88BD57F4DB6E764F4D6188C771B408CBA@aussrvexchmbx1.microsemi.net>
References: <20140428160410.4246.17468.idtracker@ietfa.amsl.com>
 <20211F91F544D247976D84C5D778A4C32E5FAB39@SG70YWXCHMBA05.zap.alcatel-lucent.com>
In-Reply-To: <20211F91F544D247976D84C5D778A4C32E5FAB39@SG70YWXCHMBA05.zap.alcatel-lucent.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Received-SPF: None (: microsemi.com does not designate permitted sender hosts)
Archived-At: http://mailarchive.ietf.org/arch/msg/tictoc/DgMyyeT4TURvbXyCjkkGSsY5T_0
Subject: Re: [TICTOC] draft-ietf-tictoc-1588overmpls-06 comments
Precedence: list

Hi Manav,

I notice a number of changes to BC support that I did not see discussed on =
the reflector between draft-05 and draft-06.   Moving from draft-04 to draf=
t-05 there was a significant effort to understand how TC (both P2P and E2E)=
 and BC work with LER and LSR and there seemed to be agreement on the draft=
-05 text on that topic (I worked a good deal with Shahram on the text).

Related, I would note that the ITU-T has finished the first network deploym=
ent scenarios, clock chain and performance specs for IEEE1588 with phase/ti=
me support and it uses BC in every network element (see ITU-T G.8275, G.827=
1, G.8273.2, etc.).


Specifically my comments on draft-06 changes

1) Section 15.2 the following text has been deleted
"When a Timing-capable/aware LSR behaves as a Boundary clock and receives a=
 Timing message from a Timing-capable/aware MPLS interface.  The LSR perfor=
ms the functions of a Boundary Clock in terminating the received Timing mes=
sage and re-generating a new timing message over another (or the same) MPLS=
 interface."

2) Section 15.3 the following text has been deleted
"or BC"

3) Section 18, the Applicability statement was removed from draft-04 to dra=
ft-05.  It has now be re-introduced.  Text should include the draft-04 prop=
osal (before the entire section was removed)
"o  An LSR receives MPLS encapsulated Timing messages from a Timing LSP and=
 terminates them, while performing the OC or BC functionality."


Regards,
Peter




-----Original Message-----
From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of Bhatia, Manav (M=
anav)
Sent: April 28, 2014 12:09 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-06.txt

Hi Yaakov,

This version addresses the final set of comments that we received as per th=
e MPLS and TICTOC WG last call.

Can we move it further now?

Cheers, Manav

> -----Original Message-----
> From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: Monday, April 28, 2014 9:34 PM
> To: i-d-announce@ietf.org
> Cc: tictoc@ietf.org
> Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-06.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Timing over IP Connection and
> Transfer of Clock Working Group of the IETF.
>=20
>         Title           : Transporting Timing messages over MPLS
> Networks
>         Authors         : Shahram Davari
>                           Amit Oren
>                           Manav Bhatia
>                           Peter Roberts
>                           Laurent Montini
> 	Filename        : draft-ietf-tictoc-1588overmpls-06.txt
> 	Pages           : 36
> 	Date            : 2014-04-28
>=20
> Abstract:
>    This document defines the method for transporting Timing messages
>    such as PTP and NTP over an MPLS network.  The method allows for the
>    easy identification of these PDUs at the port level to allow for
> port
>    level processing of these PDUs in both LERs and LSRs.
>=20
>    The basic idea is to transport Timing messages inside dedicated MPLS
>    LSPs.  These LSPs only carry Timing messages and possibly Control
> and
>    Management packets, but they do not carry customer traffic.
>=20
>    Two methods for transporting Timing messages over MPLS are defined.
>    The first method is to transport Timing messages directly over the
>    dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
>    MPLS networks.  The second method is to transport Timing messages
>    inside a PW via Ethernet encapsulation.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588overmpls/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-06
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tictoc-1588overmpls-06
>=20
>=20
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc