Re: [TICTOC] draft-ietf-tictoc-1588overmpls-06 comments

"Meyer, Peter" <Peter.Meyer@microsemi.com> Mon, 28 April 2014 16:41 UTC

Return-Path: <Peter.Meyer@microsemi.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3194D1A0943 for <tictoc@ietfa.amsl.com>; Mon, 28 Apr 2014 09:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JoDhKbwFrAfv for <tictoc@ietfa.amsl.com>; Mon, 28 Apr 2014 09:41:02 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0206.outbound.protection.outlook.com [207.46.163.206]) by ietfa.amsl.com (Postfix) with ESMTP id B59CF1A0248 for <tictoc@ietf.org>; Mon, 28 Apr 2014 09:41:01 -0700 (PDT)
Received: from BLUPR02CA013.namprd02.prod.outlook.com (10.141.30.13) by BLUPR02MB485.namprd02.prod.outlook.com (10.141.82.14) with Microsoft SMTP Server (TLS) id 15.0.929.12; Mon, 28 Apr 2014 16:41:00 +0000
Received: from BN1AFFO11FD037.protection.gbl (2a01:111:f400:7c10::113) by BLUPR02CA013.outlook.office365.com (2a01:111:e400:879::13) with Microsoft SMTP Server (TLS) id 15.0.929.12 via Frontend Transport; Mon, 28 Apr 2014 16:41:00 +0000
Received: from avsrvexchhts1.microsemi.net (208.19.100.21) by BN1AFFO11FD037.mail.protection.outlook.com (10.58.52.241) with Microsoft SMTP Server (TLS) id 15.0.929.8 via Frontend Transport; Mon, 28 Apr 2014 16:40:59 +0000
Received: from AUSSRVEXCHHTS1.microsemi.net (10.201.34.105) by avsrvexchhts1.microsemi.net (10.100.34.105) with Microsoft SMTP Server (TLS) id 14.2.347.0; Mon, 28 Apr 2014 09:40:58 -0700
Received: from AUSSRVEXCHMBX1.microsemi.net ([fe80::1d99:3632:64b1:ebf4]) by aussrvexchhts1.microsemi.net ([::1]) with mapi id 14.02.0347.000; Mon, 28 Apr 2014 11:40:56 -0500
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
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [134.199.53.117]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:208.19.100.21; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019001)(6009001)(428001)(199002)(189002)(13464003)(377424004)(377454003)(51704005)(66066001)(16796002)(97736001)(83322001)(2009001)(6806004)(85852003)(83072002)(84676001)(23726002)(46102001)(15202345003)(86362001)(76482001)(97756001)(50466002)(80022001)(31966008)(74662001)(33656001)(2656002)(92726001)(79102001)(76176999)(53416003)(87936001)(561944002)(80976001)(81542001)(4396001)(15975445006)(55846006)(92566001)(77982001)(54356999)(46406003)(19580405001)(81342001)(47776003)(44976005)(20776003)(50986999)(19580395003)(101416001)(99396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR02MB485; H:avsrvexchhts1.microsemi.net; FPR:2CE4F1FD.A4F6AFCD.B5F67F77.CC59550.204BA; MLV:sfv; PTR:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-Forefront-PRVS: 01952C6E96
Received-SPF: None (: microsemi.com does not designate permitted sender hosts)
X-OriginatorOrg: microsemi.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tictoc/DgMyyeT4TURvbXyCjkkGSsY5T_0
Subject: Re: [TICTOC] draft-ietf-tictoc-1588overmpls-06 comments
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 16:41:04 -0000

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 draft-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 deployment scenarios, clock chain and performance specs for IEEE1588 with phase/time support and it uses BC in every network element (see ITU-T G.8275, G.8271, 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 performs the functions of a Boundary Clock in terminating the received Timing message 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 draft-05.  It has now be re-introduced.  Text should include the draft-04 proposal (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 (Manav)
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 the 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
> 
> 
> 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.
> 
>         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
> 
> 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.
> 
>    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.
> 
>    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.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588overmpls/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-06
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-1588overmpls-06
> 
> 
> 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.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> 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