Re: [TICTOC] minutes for joint meeting of ntp/tictoc at IETF 88

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Wed, 11 December 2013 08:21 UTC

Return-Path: <Alexander.Vainshtein@ecitele.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 6D2B31AE1AD for <tictoc@ietfa.amsl.com>; Wed, 11 Dec 2013 00:21:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 Y6pTh6LBTOVr for <tictoc@ietfa.amsl.com>; Wed, 11 Dec 2013 00:21:40 -0800 (PST)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0083.outbound.protection.outlook.com [213.199.154.83]) by ietfa.amsl.com (Postfix) with ESMTP id 4643A1AE14C for <tictoc@ietf.org>; Wed, 11 Dec 2013 00:21:38 -0800 (PST)
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB531.eurprd03.prod.outlook.com (10.242.109.155) with Microsoft SMTP Server (TLS) id 15.0.837.10; Wed, 11 Dec 2013 08:21:31 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0837.004; Wed, 11 Dec 2013 08:21:31 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Tal Mizrahi <talmi@marvell.com>
Thread-Topic: [TICTOC] minutes for joint meeting of ntp/tictoc at IETF 88
Thread-Index: AQHO8saLUa3tLJ1V70GVIQriLGIuy5pL/EiAgAAiTYCAAo0r0A==
Date: Wed, 11 Dec 2013 08:21:30 +0000
Message-ID: <5de970d486a0435aa6d31f2232673aad@AM3PR03MB532.eurprd03.prod.outlook.com>
References: <52A23B71.1000305@isoc.org> <74470498B659FA4687F0B0018C19A89C01CAF450D842@IL-MB01.marvell.com> <7347100B5761DC41A166AC17F22DF1121B72F166@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B72F166@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.56.21]
x-forefront-prvs: 0057EE387C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(13464003)(25584003)(199002)(189002)(164054003)(377454003)(52044002)(51704005)(66066001)(56816005)(90146001)(79102001)(65816001)(2656002)(80022001)(51856001)(87266001)(63696002)(46102001)(83322001)(74366001)(19580395003)(69226001)(76482001)(50986001)(56776001)(85306002)(4396001)(47976001)(47736001)(49866001)(53806001)(80976001)(19580405001)(81686001)(77982001)(87936001)(54356001)(54316002)(81816001)(59766001)(74316001)(561944002)(81342001)(81542001)(31966008)(33646001)(74662001)(74502001)(76576001)(85852003)(83072002)(74876001)(76786001)(47446002)(74706001)(76796001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB531; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:147.234.56.21; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
Cc: "odonoghue@isoc.org" <odonoghue@isoc.org>, NTP Working Group <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] minutes for joint meeting of ntp/tictoc at IETF 88
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: Wed, 11 Dec 2013 08:21:43 -0000

Tal,
I fully agree with you that having two different drafts addressing the same problem is most unfortunate (even if this is neither the first nor, most probably the last time IETF encounters this issue :-).

At the same time I do not see any easy way to merge the two approaches:
- From my point of view the approach taken in the TICTOC WG draft breaks the MPLS data plane architecture which allows only a limited set of "alert mechanisms" for intercepting a labeled packet and manipulating its payload instead of regular forwarding
- The alternative proposal is an attempt to find a solution that, while delivering the same functionality, would stay within the boundaries of this architecture.

Regards,
     Sasha


> -----Original Message-----
> From: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
> Sent: Monday, December 09, 2013 7:14 PM
> To: Tal Mizrahi; odonoghue@isoc.org; tictoc@ietf.org; NTP Working Group;
> Shahram Davari (davari@broadcom.com); Alexander Vainshtein; Stewart Bryant
> <stbryant@cisco.com> (stbryant@cisco.com); John E Drake
> (jdrake@juniper.net)
> Subject: RE: [TICTOC] minutes for joint meeting of ntp/tictoc at IETF 88
> 
> Adding John.
> 
> -----Original Message-----
> From: Tal Mizrahi [mailto:talmi@marvell.com]
> Sent: Monday, December 09, 2013 7:11 AM
> To: odonoghue@isoc.org; tictoc@ietf.org; NTP Working Group; Shahram Davari
> (davari@broadcom.com); Gregory Mirsky; Alexander Vainshtein; Stewart Bryant
> <stbryant@cisco.com> (stbryant@cisco.com)
> Subject: RE: [TICTOC] minutes for joint meeting of ntp/tictoc at IETF 88
> 
> Hi,
> 
> I apologize for this late comment, as I could not attend the IETF meeting.
> 
> >Greg Mirsky presented his new draft from the MPLS working group on
> >Residence Time Measurement. There were a number of questions related to
> >the technical content of the draft.
> >Discussion should continue on the tictoc and mpls mailing lists.
> >(draft-mirsky-mpls-residence-time-00.txt)
> >
> >The subject of the current draft on Timing over MPLS that is being
> >working in the tictoc working group was addressed.
> >There are still concerns regarding a way forward for this draft. After
> >much discussion, it was decided that the draft would proceed in the
> >tictoc working group as an Experimental RFC.
> 
> It looks like we are heading towards having two drafts that solve the same
> problem, which is most unfortunate.
> Isn't there a way to update Shahram's draft in a way that will satisfy Greg and
> Sasha's concerns and eliminate the need for draft-mirsky-mpls-residence-time?
> For example using GAL instead of a dedicated LSP in Shahram's draft is an
> option that has been discussed before, and may be the least painful
> compromise.
> 
> Honestly, the worst possible outcome is to define two different solutions. We
> obviously don't expect vendors to implement both solutions.
> 
> I believe it is our obligation to reach a single solution for this problem.
> 
> Thanks,
> Tal.
> 
> 
> -----Original Message-----
> From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of Karen O'Donoghue
> Sent: Friday, December 06, 2013 11:03 PM
> To: tictoc@ietf.org; NTP Working Group
> Subject: [TICTOC] minutes for joint meeting of ntp/tictoc at IETF 88
> 
> Folks,
> 
> Below are the minutes for the joint meeting of tictoc and ntp at IETF 88. If you
> have any questions or comments, feel free to provide them.
> 
> Regards,
> Karen
>