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

Manav Bhatia <manavbhatia@gmail.com> Mon, 28 April 2014 16:53 UTC

Return-Path: <manavbhatia@gmail.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 40BA11A0A38 for <tictoc@ietfa.amsl.com>; Mon, 28 Apr 2014 09:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 lJVIzQe2Egko for <tictoc@ietfa.amsl.com>; Mon, 28 Apr 2014 09:53:04 -0700 (PDT)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 43F241A0A1D for <tictoc@ietf.org>; Mon, 28 Apr 2014 09:53:04 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id i11so7494459oag.23 for <tictoc@ietf.org>; Mon, 28 Apr 2014 09:53:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Dfq6XaUIfasDDxKiPsdRai9kxsUi2+CVNb8mKB8qxBg=; b=DiRTVPQtGqFpQf7B2NtQWGEA1UYt2cx72LDvFrKDQyIbeQAHTyg1Ud8v4Sp5puKMzg tY9OY+9cQBY3BYhskYnqvOLiW5QHrycWrgrOF4l4hnkLrZG0auJ4CghRBnBF+ZsCWTmQ ADd8zeVXYHyNYxADhb4P/PtNqmvEz/t3qwneUuJCK6ThaiRJ+6TpXYcOGghA4Sqt1J3H wF8w+UU5UMoDxF0csufZ6MX2mDMgri8KH/WtA5XxH6V0e094SHl7NuQSfV9pDkc0De5F PLmIXmQtEuQHcPuJ77uLNlJIL5iwd1QqMx07joHJI/1aF3Ph+b9u+juv5DdVFdM6fJ2R cmWw==
MIME-Version: 1.0
X-Received: by 10.60.135.106 with SMTP id pr10mr23349394oeb.15.1398703983408; Mon, 28 Apr 2014 09:53:03 -0700 (PDT)
Received: by 10.76.77.97 with HTTP; Mon, 28 Apr 2014 09:53:03 -0700 (PDT)
In-Reply-To: <287eb6668e0c48ccb1488c92f5ac168f@SG70YWXCHHUB03.zap.alcatel-lucent.com>
References: <20140428160410.4246.17468.idtracker@ietfa.amsl.com> <20211F91F544D247976D84C5D778A4C32E5FAB39@SG70YWXCHMBA05.zap.alcatel-lucent.com> <287eb6668e0c48ccb1488c92f5ac168f@SG70YWXCHHUB03.zap.alcatel-lucent.com>
Date: Mon, 28 Apr 2014 22:23:03 +0530
Message-ID: <CAG1kdogTSBgNW==GACU--1syEvyur70MoJ681PoEMshcM5jQPw@mail.gmail.com>
From: Manav Bhatia <manavbhatia@gmail.com>
To: "Meyer, Peter" <Peter.Meyer@microsemi.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/tictoc/OG_eZvt0HMG0IeQCkSXZfUK_kyQ
X-Mailman-Approved-At: Mon, 28 Apr 2014 10:04:35 -0700
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
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:53:06 -0000

Hi Peter,

This wasnt intentional. Let me take a look at why certain sections got
removed -- i think its an editorial issue.

Cheers, Manav



On Mon, Apr 28, 2014 at 10:10 PM, Meyer, Peter
<Peter.Meyer@microsemi.com> wrote:
>
> 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