
From yaakov_s@rad.com  Tue Feb  1 07:35:59 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C97A3A6D64 for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 07:35:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P8lyqdGFUBXc for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 07:35:58 -0800 (PST)
Received: from antivir1.rad.co.il (mx1-q.rad.co.il [80.74.100.136]) by core3.amsl.com (Postfix) with ESMTP id 037273A6D4A for <tictoc@ietf.org>; Tue,  1 Feb 2011 07:35:49 -0800 (PST)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir1.rad.co.il with ESMTP; 01 Feb 2011 17:39:04 +0200
Received: from EXUS4-DRP.ad.rad.co.il (192.114.24.119) by EXRAD5.ad.rad.co.il (192.114.24.28) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 1 Feb 2011 17:39:04 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Tue, 1 Feb 2011 17:39:04 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, Jack Kohn <kohn.jack@gmail.com>, Shahram Davari <davari@broadcom.com>
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AQHLtwvRa6CYok1lRYSvUt8QtgvK+ZPjbVwAgACmdwCAAAnKAIAAOHqAgAA1goCAAGBBAIAAg+MAgAS/WwCAABihgIAAFdWAgAC9NVD//+psgIAAYkwggABuCbCAAQafMA==
Date: Tue, 1 Feb 2011 15:39:03 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.170.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 01 Feb 2011 15:35:59 -0000

Hi all,=20

Interesting how everyone is changing their minds so quickly ...

When I brought up the question of NTP I was told that NTP is not interestin=
g / not possible
since the ONLY question here is TC.

I tried pushing the issue of prioritization, and hinted at the asymmetry is=
sue
(but wanted to discuss with the RSVP-TE experts first to see that it could =
be done)
and was told that I needed to explain why there is anything at all to do
in this regards.

Well, let's assume that I have become convinced by your arguments and reall=
y want TC.
Not just for 1588, but for the timing protocol that presently runs over the=
 Internet.
In that case your proposal falls somewhat short, but can be easily retrofit=
ted
to accomplish everything for both timing protocols.
If, in addition, I can get time correction for other protocols,
and measurement of one-way delay for PM,=20
that sounds like a major advantage from my point of view.

I fully understand the advantage of re-using existing hardware,
and am not suggesting that we not advance the present proposal.
However, I think the generic mechanism can easily be implemented
based on existing building blocks, and should be investigated as well.

Y(J)S


-----Original Message-----
From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
Sent: Tuesday, February 01, 2011 02:10
To: Yaakov Stein; Jack Kohn
Cc: tictoc@ietf.org
Subject: RE: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi Yaakov,
=20
I am not sure if I understand why you think that the method described in th=
is draft will not work for NTP? I agree that we have been concentrating on =
1588, but that's ok for a draft that's called "Transporting PTP messages (1=
588) over MPLS Networks". We would require some very minimal changes to als=
o accommodate NTP.

The draft states that a subset of PTP messages MUST be transported over som=
e dedicated LSPs, lets call them timing LSPs for now. When setting up the R=
SVP tunnel we had also given a pointer to the start of the packet, thus it =
is trivial for implementations to note whether the incoming packet is 1588 =
or some other. If its 1588 event messages then they may want to compensate =
for residence time by updating the PTP packet Correction Field. At the very=
 least such packets should be given some sort of priority over the others.=
=20

Now this draft can be easily extended to carry NTP as well. All we need to =
say is that NTP packets MUST be transported over the timing LSPs. We will n=
eed to change section 13 where we have described routing extensions to now =
indicate the protocol (1588 or NTP) that the router supports. Additionally,=
 it can also indicate that if its 1588, then is it capable of updating the =
CF. Similarly, we may need some minor changes in the RSVP section as well.

The section on ECMP and QoS will remain as is without any changes. There ca=
n be a subsection for 1588 where we discuss the UDP checksum, etc.

So I don't see why you think that this draft precludes the possibility of s=
upporting NTP.

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Yaakov Stein
> Sent: Monday, January 31, 2011 10.50 PM
> To: Jack Kohn
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Jack
>=20
> There was a long discussion at the conference call and on the list,
> with the draft authors and others maintaining that this method
> is not applicable to NTP (mainly because its sole purpose is=20
> to identify LSRs that can perform TC correction to 1588 packets).
>=20
> By label range I mean the method used to identify the timing packets
> in transit, whatever that method is.
>=20
> Y(J)S
>=20
> -----Original Message-----
> From: Jack Kohn [mailto:kohn.jack@gmail.com]=20
> Sent: Monday, January 31, 2011 15:26
> To: Yaakov Stein
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Yakov,
>=20
> > I am thus led to reiterate my proposal for completely=20
> generic MPLS mechanism for TC,
> > a method that eliminates all the FCS and UDP checksum=20
> problems that we have recently discussed.
> >
> > We need only to define a new PW type with an extended=20
> control word that carries a CF.
> > The payload could be anything - NTP, 1588, RFC-868, one-way=20
> delay OAM, etc.
> > We can use the label-range idea from the present draft, and=20
> similar routing extensions
>=20
> What label range are you referring to? AFAIK there isnt any label
> range defined in this document. The label that 1588 uses is signalled
> by RSVP to all the other nodes.
>=20
> Also, what prevents the same mechanism to be used for NTP? If its NTP
> that we are supporting then one does not need to provide the offset in
> the RSVP object. The routing extensions remain the same and it NTP
> also works. Thus the mechanism defined in this draft will work for NTP
> as well.
>=20
> Jack
>=20
> > to signal the TC capability.
> >
> > Y(J)S
> >
> >
> >
> > _______________________________________________
> > 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
>=20

From manav.bhatia@alcatel-lucent.com  Tue Feb  1 07:49:14 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A0433A6C1D for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 07:49:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.305
X-Spam-Level: 
X-Spam-Status: No, score=-6.305 tagged_above=-999 required=5 tests=[AWL=0.294,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w2bf-blnD1JH for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 07:49:13 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 26FB53A6AC9 for <tictoc@ietf.org>; Tue,  1 Feb 2011 07:49:13 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p11FqISc013898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 1 Feb 2011 09:52:22 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p11FqFrB018103 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 1 Feb 2011 21:22:16 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Tue, 1 Feb 2011 21:22:15 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Yaakov Stein <yaakov_s@rad.com>, Jack Kohn <kohn.jack@gmail.com>, Shahram Davari <davari@broadcom.com>
Date: Tue, 1 Feb 2011 21:22:13 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AQHLtwvRa6CYok1lRYSvUt8QtgvK+ZPjbVwAgACmdwCAAAnKAIAAOHqAgAA1goCAAGBBAIAAg+MAgAS/WwCAABihgIAAFdWAgAC9NVD//+psgIAAYkwggABuCbCAAQafMIAAAorQ
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 01 Feb 2011 15:49:14 -0000

Hi Yakov,

And I still stand by what I said earlier that I don't think NTP needs to be=
 included here. I'd rather that we keep NTP and 1588 separate and only merg=
e them if we think its absolutely essential that a common uniform solution =
is developed for the two protocols.=20

I responded to a comment on the list that the method described in this docu=
ment cannot be applied to NTP. I think it can with a few tweaks here and th=
ere as you also suggest in your email (and had alluded to in the call last =
time).

Cheers, Manav


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
> Sent: Tuesday, February 01, 2011 9.09 PM
> To: Bhatia, Manav (Manav); Jack Kohn; Shahram Davari
> Cc: tictoc@ietf.org
> Subject: RE: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Hi all,=20
>=20
> Interesting how everyone is changing their minds so quickly ...
>=20
> When I brought up the question of NTP I was told that NTP is=20
> not interesting / not possible
> since the ONLY question here is TC.
>=20
> I tried pushing the issue of prioritization, and hinted at=20
> the asymmetry issue
> (but wanted to discuss with the RSVP-TE experts first to see=20
> that it could be done)
> and was told that I needed to explain why there is anything=20
> at all to do
> in this regards.
>=20
> Well, let's assume that I have become convinced by your=20
> arguments and really want TC.
> Not just for 1588, but for the timing protocol that presently=20
> runs over the Internet.
> In that case your proposal falls somewhat short, but can be=20
> easily retrofitted
> to accomplish everything for both timing protocols.
> If, in addition, I can get time correction for other protocols,
> and measurement of one-way delay for PM,=20
> that sounds like a major advantage from my point of view.
>=20
> I fully understand the advantage of re-using existing hardware,
> and am not suggesting that we not advance the present proposal.
> However, I think the generic mechanism can easily be implemented
> based on existing building blocks, and should be investigated as well.
>=20
> Y(J)S
>=20
>=20
> -----Original Message-----
> From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
> Sent: Tuesday, February 01, 2011 02:10
> To: Yaakov Stein; Jack Kohn
> Cc: tictoc@ietf.org
> Subject: RE: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Hi Yaakov,
> =20
> I am not sure if I understand why you think that the method=20
> described in this draft will not work for NTP? I agree that=20
> we have been concentrating on 1588, but that's ok for a draft=20
> that's called "Transporting PTP messages (1588) over MPLS=20
> Networks". We would require some very minimal changes to also=20
> accommodate NTP.
>=20
> The draft states that a subset of PTP messages MUST be=20
> transported over some dedicated LSPs, lets call them timing=20
> LSPs for now. When setting up the RSVP tunnel we had also=20
> given a pointer to the start of the packet, thus it is=20
> trivial for implementations to note whether the incoming=20
> packet is 1588 or some other. If its 1588 event messages then=20
> they may want to compensate for residence time by updating=20
> the PTP packet Correction Field. At the very least such=20
> packets should be given some sort of priority over the others.=20
>=20
> Now this draft can be easily extended to carry NTP as well.=20
> All we need to say is that NTP packets MUST be transported=20
> over the timing LSPs. We will need to change section 13 where=20
> we have described routing extensions to now indicate the=20
> protocol (1588 or NTP) that the router supports.=20
> Additionally, it can also indicate that if its 1588, then is=20
> it capable of updating the CF. Similarly, we may need some=20
> minor changes in the RSVP section as well.
>=20
> The section on ECMP and QoS will remain as is without any=20
> changes. There can be a subsection for 1588 where we discuss=20
> the UDP checksum, etc.
>=20
> So I don't see why you think that this draft precludes the=20
> possibility of supporting NTP.
>=20
> Cheers, Manav
>=20
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org=20
> > [mailto:tictoc-bounces@ietf.org] On Behalf Of Yaakov Stein
> > Sent: Monday, January 31, 2011 10.50 PM
> > To: Jack Kohn
> > Cc: tictoc@ietf.org
> > Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> > MPLS Networks
> >=20
> > Jack
> >=20
> > There was a long discussion at the conference call and on the list,
> > with the draft authors and others maintaining that this method
> > is not applicable to NTP (mainly because its sole purpose is=20
> > to identify LSRs that can perform TC correction to 1588 packets).
> >=20
> > By label range I mean the method used to identify the timing packets
> > in transit, whatever that method is.
> >=20
> > Y(J)S
> >=20
> > -----Original Message-----
> > From: Jack Kohn [mailto:kohn.jack@gmail.com]=20
> > Sent: Monday, January 31, 2011 15:26
> > To: Yaakov Stein
> > Cc: tictoc@ietf.org
> > Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> > MPLS Networks
> >=20
> > Yakov,
> >=20
> > > I am thus led to reiterate my proposal for completely=20
> > generic MPLS mechanism for TC,
> > > a method that eliminates all the FCS and UDP checksum=20
> > problems that we have recently discussed.
> > >
> > > We need only to define a new PW type with an extended=20
> > control word that carries a CF.
> > > The payload could be anything - NTP, 1588, RFC-868, one-way=20
> > delay OAM, etc.
> > > We can use the label-range idea from the present draft, and=20
> > similar routing extensions
> >=20
> > What label range are you referring to? AFAIK there isnt any label
> > range defined in this document. The label that 1588 uses is=20
> signalled
> > by RSVP to all the other nodes.
> >=20
> > Also, what prevents the same mechanism to be used for NTP?=20
> If its NTP
> > that we are supporting then one does not need to provide=20
> the offset in
> > the RSVP object. The routing extensions remain the same and it NTP
> > also works. Thus the mechanism defined in this draft will=20
> work for NTP
> > as well.
> >=20
> > Jack
> >=20
> > > to signal the TC capability.
> > >
> > > Y(J)S
> > >
> > >
> > >
> > > _______________________________________________
> > > 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
> >=20
> =

From yaakov_s@rad.com  Tue Feb  1 07:58:29 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 083003A6B58 for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 07:58:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.503
X-Spam-Level: 
X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XlAEHKxQWtUL for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 07:58:27 -0800 (PST)
Received: from antivir2.rad.co.il (antivir2.rad.co.il [62.0.23.221]) by core3.amsl.com (Postfix) with ESMTP id 098363A6AC9 for <tictoc@ietf.org>; Tue,  1 Feb 2011 07:58:25 -0800 (PST)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir2.rad.co.il with ESMTP; 01 Feb 2011 18:01:41 +0200
Received: from EXUS4-DRP.ad.rad.co.il (192.114.24.119) by EXRAD5.ad.rad.co.il (192.114.24.28) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 1 Feb 2011 18:01:41 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Tue, 1 Feb 2011 18:01:41 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, Jack Kohn <kohn.jack@gmail.com>, Shahram Davari <davari@broadcom.com>
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AQHLtwvRa6CYok1lRYSvUt8QtgvK+ZPjbVwAgACmdwCAAAnKAIAAOHqAgAA1goCAAGBBAIAAg+MAgAS/WwCAABihgIAAFdWAgAC9NVD//+psgIAAYkwggABuCbCAAQafMIAAAorQgAAFy2A=
Date: Tue, 1 Feb 2011 16:01:40 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CDC0C4@EXRAD5.ad.rad.co.il>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.170.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 01 Feb 2011 15:58:29 -0000

Manav

Then we basically agree.

Y(J)S

-----Original Message-----
From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
Sent: Tuesday, February 01, 2011 17:52
To: Yaakov Stein; Jack Kohn; Shahram Davari
Cc: tictoc@ietf.org
Subject: RE: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi Yakov,

And I still stand by what I said earlier that I don't think NTP needs to be=
 included here. I'd rather that we keep NTP and 1588 separate and only merg=
e them if we think its absolutely essential that a common uniform solution =
is developed for the two protocols.=20

I responded to a comment on the list that the method described in this docu=
ment cannot be applied to NTP. I think it can with a few tweaks here and th=
ere as you also suggest in your email (and had alluded to in the call last =
time).

Cheers, Manav


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
> Sent: Tuesday, February 01, 2011 9.09 PM
> To: Bhatia, Manav (Manav); Jack Kohn; Shahram Davari
> Cc: tictoc@ietf.org
> Subject: RE: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Hi all,=20
>=20
> Interesting how everyone is changing their minds so quickly ...
>=20
> When I brought up the question of NTP I was told that NTP is=20
> not interesting / not possible
> since the ONLY question here is TC.
>=20
> I tried pushing the issue of prioritization, and hinted at=20
> the asymmetry issue
> (but wanted to discuss with the RSVP-TE experts first to see=20
> that it could be done)
> and was told that I needed to explain why there is anything=20
> at all to do
> in this regards.
>=20
> Well, let's assume that I have become convinced by your=20
> arguments and really want TC.
> Not just for 1588, but for the timing protocol that presently=20
> runs over the Internet.
> In that case your proposal falls somewhat short, but can be=20
> easily retrofitted
> to accomplish everything for both timing protocols.
> If, in addition, I can get time correction for other protocols,
> and measurement of one-way delay for PM,=20
> that sounds like a major advantage from my point of view.
>=20
> I fully understand the advantage of re-using existing hardware,
> and am not suggesting that we not advance the present proposal.
> However, I think the generic mechanism can easily be implemented
> based on existing building blocks, and should be investigated as well.
>=20
> Y(J)S
>=20
>=20
> -----Original Message-----
> From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
> Sent: Tuesday, February 01, 2011 02:10
> To: Yaakov Stein; Jack Kohn
> Cc: tictoc@ietf.org
> Subject: RE: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Hi Yaakov,
> =20
> I am not sure if I understand why you think that the method=20
> described in this draft will not work for NTP? I agree that=20
> we have been concentrating on 1588, but that's ok for a draft=20
> that's called "Transporting PTP messages (1588) over MPLS=20
> Networks". We would require some very minimal changes to also=20
> accommodate NTP.
>=20
> The draft states that a subset of PTP messages MUST be=20
> transported over some dedicated LSPs, lets call them timing=20
> LSPs for now. When setting up the RSVP tunnel we had also=20
> given a pointer to the start of the packet, thus it is=20
> trivial for implementations to note whether the incoming=20
> packet is 1588 or some other. If its 1588 event messages then=20
> they may want to compensate for residence time by updating=20
> the PTP packet Correction Field. At the very least such=20
> packets should be given some sort of priority over the others.=20
>=20
> Now this draft can be easily extended to carry NTP as well.=20
> All we need to say is that NTP packets MUST be transported=20
> over the timing LSPs. We will need to change section 13 where=20
> we have described routing extensions to now indicate the=20
> protocol (1588 or NTP) that the router supports.=20
> Additionally, it can also indicate that if its 1588, then is=20
> it capable of updating the CF. Similarly, we may need some=20
> minor changes in the RSVP section as well.
>=20
> The section on ECMP and QoS will remain as is without any=20
> changes. There can be a subsection for 1588 where we discuss=20
> the UDP checksum, etc.
>=20
> So I don't see why you think that this draft precludes the=20
> possibility of supporting NTP.
>=20
> Cheers, Manav
>=20
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org=20
> > [mailto:tictoc-bounces@ietf.org] On Behalf Of Yaakov Stein
> > Sent: Monday, January 31, 2011 10.50 PM
> > To: Jack Kohn
> > Cc: tictoc@ietf.org
> > Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> > MPLS Networks
> >=20
> > Jack
> >=20
> > There was a long discussion at the conference call and on the list,
> > with the draft authors and others maintaining that this method
> > is not applicable to NTP (mainly because its sole purpose is=20
> > to identify LSRs that can perform TC correction to 1588 packets).
> >=20
> > By label range I mean the method used to identify the timing packets
> > in transit, whatever that method is.
> >=20
> > Y(J)S
> >=20
> > -----Original Message-----
> > From: Jack Kohn [mailto:kohn.jack@gmail.com]=20
> > Sent: Monday, January 31, 2011 15:26
> > To: Yaakov Stein
> > Cc: tictoc@ietf.org
> > Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> > MPLS Networks
> >=20
> > Yakov,
> >=20
> > > I am thus led to reiterate my proposal for completely=20
> > generic MPLS mechanism for TC,
> > > a method that eliminates all the FCS and UDP checksum=20
> > problems that we have recently discussed.
> > >
> > > We need only to define a new PW type with an extended=20
> > control word that carries a CF.
> > > The payload could be anything - NTP, 1588, RFC-868, one-way=20
> > delay OAM, etc.
> > > We can use the label-range idea from the present draft, and=20
> > similar routing extensions
> >=20
> > What label range are you referring to? AFAIK there isnt any label
> > range defined in this document. The label that 1588 uses is=20
> signalled
> > by RSVP to all the other nodes.
> >=20
> > Also, what prevents the same mechanism to be used for NTP?=20
> If its NTP
> > that we are supporting then one does not need to provide=20
> the offset in
> > the RSVP object. The routing extensions remain the same and it NTP
> > also works. Thus the mechanism defined in this draft will=20
> work for NTP
> > as well.
> >=20
> > Jack
> >=20
> > > to signal the TC capability.
> > >
> > > Y(J)S
> > >
> > >
> > >
> > > _______________________________________________
> > > 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
> >=20
>=20

From stbryant@cisco.com  Tue Feb  1 09:45:08 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D75833A6D4A for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 09:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.561
X-Spam-Level: 
X-Spam-Status: No, score=-110.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cubwALfDclrf for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 09:45:08 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 022963A67D0 for <tictoc@ietf.org>; Tue,  1 Feb 2011 09:45:07 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEHALLVR01AZnwM/2dsb2JhbACWZI4jc6FRglcOAZg9hVMEjCM
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 01 Feb 2011 17:48:25 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p11HmOUc028942 for <tictoc@ietf.org>; Tue, 1 Feb 2011 17:48:25 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-110.cisco.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p11HmN811653; Tue, 1 Feb 2011 17:48:23 GMT
Message-ID: <4D484767.9050204@cisco.com>
Date: Tue, 01 Feb 2011 17:48:23 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: tictoc@ietf.org
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com>	<OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn>	<7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com>	<0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li>	<07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il>	<AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com>	<07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il>	<7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com>	<07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 01 Feb 2011 17:45:08 -0000

On 01/02/2011 15:52, Bhatia, Manav (Manav) wrote:
> Hi Yakov,
>
> And I still stand by what I said earlier that I don't think NTP needs to be included here. I'd rather that we keep NTP and 1588 separate and only merge them if we think its absolutely essential that a common uniform solution is developed for the two protocols.
Manav

It is the normal practice of the IETF to design a single common 
mechanism for a problem, so you need to justify why we need to develop a 
special purpose protocol rather than develop for instance a time 
correction protocol.

It would be better in my view to design a correction mechanism that sits 
as preamble to an opaque payload and then fix up the timing packet in 
the Timing equivalent of a PW NSP. That would work for any protocol that 
needed time of flight correction.

Stewart

From davari@broadcom.com  Tue Feb  1 11:34:24 2011
Return-Path: <davari@broadcom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2363F3A6D71 for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 11:34:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[AWL=0.603,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1b309wIwOom4 for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 11:34:23 -0800 (PST)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by core3.amsl.com (Postfix) with ESMTP id 3216D3A6DE0 for <tictoc@ietf.org>; Tue,  1 Feb 2011 11:34:23 -0800 (PST)
Received: from [10.16.192.232] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Tue, 01 Feb 2011 11:39:14 -0800
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Tue, 1 Feb 2011 11:37:31 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Tue, 1 Feb 2011 11:37:30 -0800
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AcvCOrj37WfIQ/KXTZiJXrutJn62XAACvt2A
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D484767.9050204@cisco.com>
In-Reply-To: <4D484767.9050204@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6156BEE83DG52132-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 01 Feb 2011 19:34:24 -0000

Hi Stewart,

I think with our mechanism you can support NTP as well. NTP does not need T=
C processing and only needs Transmit and Receive timestamps, which are loca=
l to the LSP ingress and Egress nodes. The UDP port number for NTP is diffe=
rent from PTP and therefore no TC processing will be applied to NTP packets=
.=20

So our mechanism could be generalized to NTP a well. The co-routed symmetry=
 is needed for both NTP and PTP. The PTP label is needed for the LSP egress=
 node (for both NTP and PTP) to sample the timestamp.

Thx
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Stewart Bryant
Sent: Tuesday, February 01, 2011 9:48 AM
To: tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

On 01/02/2011 15:52, Bhatia, Manav (Manav) wrote:
> Hi Yakov,
>
> And I still stand by what I said earlier that I don't think NTP needs to =
be included here. I'd rather that we keep NTP and 1588 separate and only me=
rge them if we think its absolutely essential that a common uniform solutio=
n is developed for the two protocols.
Manav

It is the normal practice of the IETF to design a single common=20
mechanism for a problem, so you need to justify why we need to develop a=20
special purpose protocol rather than develop for instance a time=20
correction protocol.

It would be better in my view to design a correction mechanism that sits=20
as preamble to an opaque payload and then fix up the timing packet in=20
the Timing equivalent of a PW NSP. That would work for any protocol that=20
needed time of flight correction.

Stewart
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc



From stbryant@cisco.com  Tue Feb  1 14:19:05 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1B4F3A6C8D for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 14:19:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.561
X-Spam-Level: 
X-Spam-Status: No, score=-110.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hXqQxGZXtvbN for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 14:19:03 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 49B2B3A6C52 for <tictoc@ietf.org>; Tue,  1 Feb 2011 14:19:03 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlYCAFYWSE1AZnwM/2dsb2JhbACWKo5ic6FuglcOAZg2hVMEjCM
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 01 Feb 2011 22:22:21 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p11MMKNN003489; Tue, 1 Feb 2011 22:22:20 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p11MMI829137; Tue, 1 Feb 2011 22:22:18 GMT
Message-ID: <4D48879A.1040505@cisco.com>
Date: Tue, 01 Feb 2011 22:22:18 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Shahram Davari <davari@broadcom.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D484767.9050204@cisco.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 01 Feb 2011 22:19:05 -0000

Well, you need to signal protocol type as well as offset which 
complicates the P nodes because of the different formats, whereas if you 
just have the correction field immediately after the BoS followed by the 
opaque payload, the P nodes can use a canonical time format and the 
correction can be applied in the PEs.

Stewart

On 01/02/2011 19:37, Shahram Davari wrote:
> Hi Stewart,
>
> I think with our mechanism you can support NTP as well. NTP does not need TC processing and only needs Transmit and Receive timestamps, which are local to the LSP ingress and Egress nodes. The UDP port number for NTP is different from PTP and therefore no TC processing will be applied to NTP packets.
>
> So our mechanism could be generalized to NTP a well. The co-routed symmetry is needed for both NTP and PTP. The PTP label is needed for the LSP egress node (for both NTP and PTP) to sample the timestamp.
>
> Thx
> Shahram
>
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: Tuesday, February 01, 2011 9:48 AM
> To: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
>
> On 01/02/2011 15:52, Bhatia, Manav (Manav) wrote:
>> Hi Yakov,
>>
>> And I still stand by what I said earlier that I don't think NTP needs to be included here. I'd rather that we keep NTP and 1588 separate and only merge them if we think its absolutely essential that a common uniform solution is developed for the two protocols.
> Manav
>
> It is the normal practice of the IETF to design a single common
> mechanism for a problem, so you need to justify why we need to develop a
> special purpose protocol rather than develop for instance a time
> correction protocol.
>
> It would be better in my view to design a correction mechanism that sits
> as preamble to an opaque payload and then fix up the timing packet in
> the Timing equivalent of a PW NSP. That would work for any protocol that
> needed time of flight correction.
>
> Stewart
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From davari@broadcom.com  Tue Feb  1 14:22:49 2011
Return-Path: <davari@broadcom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E1903A6C52 for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 14:22:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.063
X-Spam-Level: 
X-Spam-Status: No, score=-2.063 tagged_above=-999 required=5 tests=[AWL=0.536,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CxRNtBr5oNHg for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 14:22:38 -0800 (PST)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by core3.amsl.com (Postfix) with ESMTP id E99743A6C4D for <tictoc@ietf.org>; Tue,  1 Feb 2011 14:22:37 -0800 (PST)
Received: from [10.16.192.232] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Tue, 01 Feb 2011 14:27:29 -0800
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Tue, 1 Feb 2011 14:25:46 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Date: Tue, 1 Feb 2011 14:25:45 -0800
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AcvCXoNuoriNJSvGR6y2ViBFp/R5mAAABz9A
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6941B652F50@SJEXCHCCR02.corp.ad.broadcom.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D484767.9050204@cisco.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com> <4D48879A.1040505@cisco.com>
In-Reply-To: <4D48879A.1040505@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6156575B3DG135698-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 01 Feb 2011 22:22:50 -0000

Hi Stewart,

For NTP there is no need to signal the offset since there is no CF update. =
And to be honest signaling the offset for PTP is not mandatory either, it j=
ust simplifies the HW parsing. There is also no need to signal the NTP sinc=
e it can be derived from UDP port number.

Regards,
Shahram

-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com]=20
Sent: Tuesday, February 01, 2011 2:22 PM
To: Shahram Davari
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Well, you need to signal protocol type as well as offset which=20
complicates the P nodes because of the different formats, whereas if you=20
just have the correction field immediately after the BoS followed by the=20
opaque payload, the P nodes can use a canonical time format and the=20
correction can be applied in the PEs.

Stewart

On 01/02/2011 19:37, Shahram Davari wrote:
> Hi Stewart,
>
> I think with our mechanism you can support NTP as well. NTP does not need=
 TC processing and only needs Transmit and Receive timestamps, which are lo=
cal to the LSP ingress and Egress nodes. The UDP port number for NTP is dif=
ferent from PTP and therefore no TC processing will be applied to NTP packe=
ts.
>
> So our mechanism could be generalized to NTP a well. The co-routed symmet=
ry is needed for both NTP and PTP. The PTP label is needed for the LSP egre=
ss node (for both NTP and PTP) to sample the timestamp.
>
> Thx
> Shahram
>
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Stewart Bryant
> Sent: Tuesday, February 01, 2011 9:48 AM
> To: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
>
> On 01/02/2011 15:52, Bhatia, Manav (Manav) wrote:
>> Hi Yakov,
>>
>> And I still stand by what I said earlier that I don't think NTP needs to=
 be included here. I'd rather that we keep NTP and 1588 separate and only m=
erge them if we think its absolutely essential that a common uniform soluti=
on is developed for the two protocols.
> Manav
>
> It is the normal practice of the IETF to design a single common
> mechanism for a problem, so you need to justify why we need to develop a
> special purpose protocol rather than develop for instance a time
> correction protocol.
>
> It would be better in my view to design a correction mechanism that sits
> as preamble to an opaque payload and then fix up the timing packet in
> the Timing equivalent of a PW NSP. That would work for any protocol that
> needed time of flight correction.
>
> Stewart
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>
>


--=20
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html





From manav.bhatia@alcatel-lucent.com  Tue Feb  1 16:23:52 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D75F3A7006 for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 16:23:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.309
X-Spam-Level: 
X-Spam-Status: No, score=-6.309 tagged_above=-999 required=5 tests=[AWL=0.290,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GN9KkcYzdpnE for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 16:23:51 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 813753A7005 for <tictoc@ietf.org>; Tue,  1 Feb 2011 16:23:50 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p120R2aq011573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 1 Feb 2011 18:27:05 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p120R0O3001431 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 2 Feb 2011 05:57:01 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Wed, 2 Feb 2011 05:57:00 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Shahram Davari <davari@broadcom.com>, "stbryant@cisco.com" <stbryant@cisco.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 2 Feb 2011 05:56:59 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AcvCOrj37WfIQ/KXTZiJXrutJn62XAACvt2AAApapVA=
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB23E1E9@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D484767.9050204@cisco.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 02 Feb 2011 00:23:52 -0000

I agree with Shahram. There is not much that needs to be done for NTP in ca=
se we would like to extend this mechanism for NTP as well. NTP is almost li=
ke a BC where the LSP will terminate. There is no TC happening in NTP. Thus=
 the only thing that needs to be done for NTP is to map an LSP/PW with NTP =
so that it can be adequately processed by the end nodes. Once the end nodes=
 identify a labelled packet with NTP they should HW timestamp it asap and p=
ass it on to CPU for further processing.

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Shahram Davari
> Sent: Wednesday, February 02, 2011 1.08 AM
> To: stbryant@cisco.com; tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Hi Stewart,
>=20
> I think with our mechanism you can support NTP as well. NTP=20
> does not need TC processing and only needs Transmit and=20
> Receive timestamps, which are local to the LSP ingress and=20
> Egress nodes. The UDP port number for NTP is different from=20
> PTP and therefore no TC processing will be applied to NTP packets.=20
>=20
> So our mechanism could be generalized to NTP a well. The=20
> co-routed symmetry is needed for both NTP and PTP. The PTP=20
> label is needed for the LSP egress node (for both NTP and=20
> PTP) to sample the timestamp.
>=20
> Thx
> Shahram
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: Tuesday, February 01, 2011 9:48 AM
> To: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> On 01/02/2011 15:52, Bhatia, Manav (Manav) wrote:
> > Hi Yakov,
> >
> > And I still stand by what I said earlier that I don't think=20
> NTP needs to be included here. I'd rather that we keep NTP=20
> and 1588 separate and only merge them if we think its=20
> absolutely essential that a common uniform solution is=20
> developed for the two protocols.
> Manav
>=20
> It is the normal practice of the IETF to design a single common=20
> mechanism for a problem, so you need to justify why we need=20
> to develop a=20
> special purpose protocol rather than develop for instance a time=20
> correction protocol.
>=20
> It would be better in my view to design a correction=20
> mechanism that sits=20
> as preamble to an opaque payload and then fix up the timing packet in=20
> the Timing equivalent of a PW NSP. That would work for any=20
> protocol that=20
> needed time of flight correction.
>=20
> Stewart
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> =

From manav.bhatia@alcatel-lucent.com  Tue Feb  1 16:28:00 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD6743A6B26 for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 16:28:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.313
X-Spam-Level: 
X-Spam-Status: No, score=-6.313 tagged_above=-999 required=5 tests=[AWL=0.286,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eHE3XdoLeYNA for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 16:27:59 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id B3B2B3A6C8E for <tictoc@ietf.org>; Tue,  1 Feb 2011 16:27:59 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p120VBEa013302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 1 Feb 2011 18:31:14 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p120VAs0019075 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 2 Feb 2011 06:01:11 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Wed, 2 Feb 2011 06:01:10 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Shahram Davari <davari@broadcom.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Date: Wed, 2 Feb 2011 06:01:10 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AcvCXoNuoriNJSvGR6y2ViBFp/R5mAAABz9AAARSrRA=
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB23E1EA@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D484767.9050204@cisco.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com> <4D48879A.1040505@cisco.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B652F50@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6941B652F50@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 02 Feb 2011 00:28:00 -0000

The draft clearly says the following on the offset that's sent in RSVP:

The OFFSET to the start of the PTP message header MAY also be signaled. Imp=
lementations can trivially locate the correctionField (CF) location given t=
his information.

When used for NTP this will be set to 0.

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Shahram Davari
> Sent: Wednesday, February 02, 2011 3.56 AM
> To: stbryant@cisco.com
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Hi Stewart,
>=20
> For NTP there is no need to signal the offset since there is=20
> no CF update. And to be honest signaling the offset for PTP=20
> is not mandatory either, it just simplifies the HW parsing.=20
> There is also no need to signal the NTP since it can be=20
> derived from UDP port number.
>=20
> Regards,
> Shahram
>=20
> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]=20
> Sent: Tuesday, February 01, 2011 2:22 PM
> To: Shahram Davari
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Well, you need to signal protocol type as well as offset which=20
> complicates the P nodes because of the different formats,=20
> whereas if you=20
> just have the correction field immediately after the BoS=20
> followed by the=20
> opaque payload, the P nodes can use a canonical time format and the=20
> correction can be applied in the PEs.
>=20
> Stewart
>=20
> On 01/02/2011 19:37, Shahram Davari wrote:
> > Hi Stewart,
> >
> > I think with our mechanism you can support NTP as well. NTP=20
> does not need TC processing and only needs Transmit and=20
> Receive timestamps, which are local to the LSP ingress and=20
> Egress nodes. The UDP port number for NTP is different from=20
> PTP and therefore no TC processing will be applied to NTP packets.
> >
> > So our mechanism could be generalized to NTP a well. The=20
> co-routed symmetry is needed for both NTP and PTP. The PTP=20
> label is needed for the LSP egress node (for both NTP and=20
> PTP) to sample the timestamp.
> >
> > Thx
> > Shahram
> >
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Stewart Bryant
> > Sent: Tuesday, February 01, 2011 9:48 AM
> > To: tictoc@ietf.org
> > Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
> >
> > On 01/02/2011 15:52, Bhatia, Manav (Manav) wrote:
> >> Hi Yakov,
> >>
> >> And I still stand by what I said earlier that I don't=20
> think NTP needs to be included here. I'd rather that we keep=20
> NTP and 1588 separate and only merge them if we think its=20
> absolutely essential that a common uniform solution is=20
> developed for the two protocols.
> > Manav
> >
> > It is the normal practice of the IETF to design a single common
> > mechanism for a problem, so you need to justify why we need=20
> to develop a
> > special purpose protocol rather than develop for instance a time
> > correction protocol.
> >
> > It would be better in my view to design a correction=20
> mechanism that sits
> > as preamble to an opaque payload and then fix up the timing=20
> packet in
> > the Timing equivalent of a PW NSP. That would work for any=20
> protocol that
> > needed time of flight correction.
> >
> > Stewart
> > _______________________________________________
> > TICTOC mailing list
> > TICTOC@ietf.org
> > https://www.ietf.org/mailman/listinfo/tictoc
> >
> >
> >
>=20
>=20
> --=20
> For corporate legal information go to:
>=20
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>=20
>=20
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> =

From manav.bhatia@alcatel-lucent.com  Tue Feb  1 18:11:39 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1DED3A7126 for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 18:11:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.317
X-Spam-Level: 
X-Spam-Status: No, score=-6.317 tagged_above=-999 required=5 tests=[AWL=0.281,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WgzAACpjfu9J for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 18:11:38 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 35C6B3A6CB3 for <tictoc@ietf.org>; Tue,  1 Feb 2011 18:11:37 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p122Ek5w023265 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 1 Feb 2011 20:14:49 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p122Ei6J023613 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 2 Feb 2011 07:44:45 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Wed, 2 Feb 2011 07:44:41 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn>
Date: Wed, 2 Feb 2011 07:44:39 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AcvA34Abj614MnXFST6TOmU7SK6fNAAC7RbQAGTi8SA=
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB23E1FA@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7C362EEF9C7896468B36C9B79200D8350CFB23E1FAINBANSXCHMBSA_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 02 Feb 2011 02:11:39 -0000

--_000_7C362EEF9C7896468B36C9B79200D8350CFB23E1FAINBANSXCHMBSA_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

BTW, this will only work in the GMPLS environments. We still dont have a so=
lution to asymmetric paths in the regular MPLS, so the problem still stands=
.

Cheers, Manav

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: Monday, January 31, 2011 7.38 AM
To: lizhong.jin@zte.com.cn
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi Lizhong,

As a result of this discussion the RTGWG will add another requirement where=
 the solution should be able to indicate to a composite link that both the =
directions of a bidirectional LSP must be bound to the same component link.

This is indeed what we want for 1588. We will also include a pointer to thi=
s in the next revision.

Cheers, Manav

________________________________
From: lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn]
Sent: Monday, January 31, 2011 6.10 AM
To: Bhatia, Manav (Manav)
Cc: tictoc@ietf.org
Subject: RE: [TICTOC] Transporting PTP messages (1588) over MPLS Networks


Hi Manav,
I see the discussion at RTGWG, it is good.
Share within TICTOC: http://www.ietf.org/mail-archive/web/rtgwg/current/msg=
03181.html

Thanks
Lizhong


"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com> wrote on 2011-01-=
28 08:09:50:

> Lizhong,
>
> > [Lizhong] I mean the LAG between two end-points,
> > not MC-LAG. E.g, one LAG interface with physical link
> > A & B between two end-points, it is possible that the forward
> > path will go through A, and backward path will go through B,
> > then the physical path is not symmetric. If I understand correctly,
> > you just assume the transport delay on link A & B are the
>
> On an ordinary lag, unless it's a MC-LAG this can be assumed to be
> more or less the same.
>
> > same, but this is not always true, especially for the composite
> > link defined in RTGWG (draft-ietf-rtgwg-cl-requirement).
>
> I quickly glanced through this draft and these can imo be easily
> avoided by defining a new link type - Composite link, in the link
> type sub-TLV of Link TLV in OSPF [RFC3630]. Such links MUST be
> avoided for setting up the PTP LSPs. Similarly the extended IS
> reachability TLV could be extended for IS-IS to avoid composite links.
>
> One could also use coloring to avoid these links, but this would
> entail manual configuration which may not be desirable.
>
> Cheers, Manav
>


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is =
solely property of the sender's organization. This mail communication is co=
nfidential. Recipients named above are obligated to maintain secrecy and ar=
e not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended =
solely for the use of the individual or entity to whom they are addressed. =
If you have received this email in error please notify the originator of th=
e message. Any views expressed in this message are those of the individual =
sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.


--_000_7C362EEF9C7896468B36C9B79200D8350CFB23E1FAINBANSXCHMBSA_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.6049" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D700151302-02022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>BTW, this will only work in the GMPLS environments=
. We=20
still dont have a solution to asymmetric paths in the regular MPLS, so the=
=20
problem still stands.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D700151302-02022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D700151302-02022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Cheers, Manav</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> tictoc-bounces@ietf.org=20
  [mailto:tictoc-bounces@ietf.org] <B>On Behalf Of </B>Bhatia, Manav=20
  (Manav)<BR><B>Sent:</B> Monday, January 31, 2011 7.38 AM<BR><B>To:</B>=20
  lizhong.jin@zte.com.cn<BR><B>Cc:</B> tictoc@ietf.org<BR><B>Subject:</B> R=
e:=20
  [TICTOC] Transporting PTP messages (1588) over MPLS=20
  Networks<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=
=3DArial=20
  color=3D#0000ff size=3D2>Hi Lizhong,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=
=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=
=3DArial=20
  color=3D#0000ff size=3D2>As a result of this discussion the RTGWG will ad=
d another=20
  requirement where the solution should be able to indicate to a composite =
link=20
  that both the directions of a bidirectional LSP must be bound to the same=
=20
  component link. </FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=
=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=
=3DArial=20
  color=3D#0000ff size=3D2>This is indeed what we want for 1588.&nbsp;We wi=
ll also=20
  include a pointer to this in the next revision.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=
=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=
=3DArial=20
  color=3D#0000ff size=3D2>Cheers, Manav</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=
=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  </DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma size=3D2><B>From:</B>=20
  lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn] <BR><B>Sent:</B>=20
  Monday, January 31, 2011 6.10 AM<BR><B>To:</B> Bhatia, Manav=20
  (Manav)<BR><B>Cc:</B> tictoc@ietf.org<BR><B>Subject:</B> RE: [TICTOC]=20
  Transporting PTP messages (1588) over MPLS Networks<BR></FONT><BR></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px so=
lid; MARGIN-RIGHT: 0px">
    <DIV></DIV><BR><FONT face=3Dsans-serif size=3D2>Hi Manav,</FONT> <BR><F=
ONT=20
    face=3Dsans-serif size=3D2>I see the discussion at RTGWG, it is good.</=
FONT>=20
    <BR><FONT face=3Dsans-serif size=3D2>Share within TICTOC:=20
    http://www.ietf.org/mail-archive/web/rtgwg/current/msg03181.html</FONT>=
=20
    <BR><BR><FONT face=3Dsans-serif size=3D2>Thanks</FONT> <BR><FONT face=
=3Dsans-serif=20
    size=3D2>Lizhong</FONT> <BR><FONT face=3DArial size=3D1>&nbsp;</FONT>=20
    <BR><BR><TT><FONT size=3D2>"Bhatia, Manav (Manav)"=20
    &lt;manav.bhatia@alcatel-lucent.com&gt; wrote on 2011-01-28=20
    08:09:50:<BR><BR>&gt; Lizhong,<BR>&gt; &nbsp;<BR>&gt; &gt; [Lizhong] I =
mean=20
    the LAG between two end-points, <BR>&gt; &gt; not MC-LAG. E.g, one LAG=
=20
    interface with physical link <BR>&gt; &gt; A &amp; B between two end-po=
ints,=20
    it is possible that the forward <BR>&gt; &gt; path will go through A, a=
nd=20
    backward path will go through B, <BR>&gt; &gt; then the physical path i=
s not=20
    symmetric. If I understand correctly, <BR>&gt; &gt; you just assume the=
=20
    transport delay on link A &amp; B are the <BR>&gt; <BR>&gt; On an ordin=
ary=20
    lag, unless it's a MC-LAG this can be assumed to be <BR>&gt; more or le=
ss=20
    the same.<BR>&gt; <BR>&gt; &gt; same, but this is not always true,=20
    especially for the composite <BR>&gt; &gt; link defined in RTGWG=20
    (draft-ietf-rtgwg-cl-requirement). <BR>&gt; <BR>&gt; I quickly glanced=
=20
    through this draft and these can imo be easily <BR>&gt; avoided by defi=
ning=20
    a new link type - Composite link, in the link <BR>&gt; type sub-TLV of =
Link=20
    TLV in OSPF [RFC3630]. Such links MUST be <BR>&gt; avoided for setting =
up=20
    the PTP LSPs. Similarly the extended IS <BR>&gt; reachability TLV could=
 be=20
    extended for IS-IS to avoid composite links.<BR>&gt; <BR>&gt; One could=
 also=20
    use coloring to avoid these links, but this would <BR>&gt; entail manua=
l=20
    configuration which may not be desirable.<BR>&gt; <BR>&gt; Cheers,=20
    Manav<BR>&gt; <BR></FONT></TT><BR><PRE>--------------------------------=
------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&n=
bsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property=
&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp=
;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;a=
bove&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nb=
sp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents=
&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbs=
p;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for=
&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbs=
p;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;hav=
e&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;no=
tify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;=
views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbs=
p;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbs=
p;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</PRE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--_000_7C362EEF9C7896468B36C9B79200D8350CFB23E1FAINBANSXCHMBSA_--

From manav.bhatia@alcatel-lucent.com  Tue Feb  1 18:54:39 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A7733A6CAA for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 18:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.325
X-Spam-Level: 
X-Spam-Status: No, score=-6.325 tagged_above=-999 required=5 tests=[AWL=0.274,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EnvyfzdbbbAi for <tictoc@core3.amsl.com>; Tue,  1 Feb 2011 18:54:38 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 652873A6BB6 for <tictoc@ietf.org>; Tue,  1 Feb 2011 18:54:38 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p122vrP6009317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <tictoc@ietf.org>; Tue, 1 Feb 2011 20:57:55 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p122vqNH008777 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <tictoc@ietf.org>; Wed, 2 Feb 2011 08:27:52 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Wed, 2 Feb 2011 08:27:52 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 2 Feb 2011 08:27:50 +0530
Thread-Topic: Bidirectional LSPs for timing packets
Thread-Index: AcvChPqua5SlSSW/Q/6IuLqbxshfLw==
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB23E20A@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Subject: [TICTOC] Bidirectional LSPs for timing packets
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 02 Feb 2011 02:54:39 -0000

Hi,

We had some discussion about using bidirectional LSPs for 1588 (and possibl=
y NTP as well) in our mailing list. The reason we discussed this was to ens=
ure that the forward and the reverse paths are same for the timing packets =
as an asymmetrical path will adversely affect the timing operation.

This becomes a challenge with MPLS as LSPs are unidirectional. The bidirect=
ional LSPs are guaranteed only in GMPLS and they will be symmetric. The sta=
ndard MPLS has no such thing. LSPs in each direction can use different path=
s. We would need to define some mechanism to set up symmetrical LSP paths f=
or regular MPLS as well. We could technically use RROs to trace back the pa=
th but that can fail the TE requirements in the reverse direction. Also the=
 paths cannot be guaranteed when doing FRR in case of failures.

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

 =

From yaakov_s@rad.com  Wed Feb  2 01:50:17 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E57A83A6BB3 for <tictoc@core3.amsl.com>; Wed,  2 Feb 2011 01:50:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bB+sbXYSh-NQ for <tictoc@core3.amsl.com>; Wed,  2 Feb 2011 01:50:14 -0800 (PST)
Received: from antivir2.rad.co.il (mx2-q.rad.co.il [80.74.100.144]) by core3.amsl.com (Postfix) with ESMTP id 2E3E13A682E for <tictoc@ietf.org>; Wed,  2 Feb 2011 01:50:11 -0800 (PST)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir2.rad.co.il with ESMTP; 02 Feb 2011 11:53:28 +0200
Received: from EXUS4-DRP.ad.rad.co.il (192.114.24.119) by EXRAD5.ad.rad.co.il (192.114.24.28) with Microsoft SMTP Server (TLS) id 14.1.218.12; Wed, 2 Feb 2011 11:53:28 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Wed, 2 Feb 2011 11:53:28 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, Shahram Davari <davari@broadcom.com>, "stbryant@cisco.com" <stbryant@cisco.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AQHLtwvRa6CYok1lRYSvUt8QtgvK+ZPjbVwAgACmdwCAAAnKAIAAOHqAgAA1goCAAGBBAIAAg+MAgAS/WwCAABihgIAAFdWAgAC9NVD//+psgIAAYkwggABuCbCAAQafMIAAAorQgAACJYCAAB58AIAAUOKAgAC+RiA=
Date: Wed, 2 Feb 2011 09:53:27 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CDC48E@EXRAD5.ad.rad.co.il>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D484767.9050204@cisco.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB23E1E9@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB23E1E9@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [207.232.33.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 02 Feb 2011 09:50:17 -0000

Manav and Shahram

The whole idea of my proposal is that it can add TC capability to NTP witho=
ut opening up the protocol at the IP level.

This can not be done using the present proposal.

Furthermore, think of a one-way delay measurement OAM packet.
Instead of having to first have a local clock converge at the remote site,
we can just send a packet with the proposed MPLS-level CF, and read the del=
ay
(assuming that the packet handling time is much longer than flight time -
otherwise we still need some bidirectional processing).

So I disagree that there is no advantage to the generic mechanism.

Y(J)S

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: Wednesday, February 02, 2011 02:27
To: Shahram Davari; stbryant@cisco.com; tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

I agree with Shahram. There is not much that needs to be done for NTP in ca=
se we would like to extend this mechanism for NTP as well. NTP is almost li=
ke a BC where the LSP will terminate. There is no TC happening in NTP. Thus=
 the only thing that needs to be done for NTP is to map an LSP/PW with NTP =
so that it can be adequately processed by the end nodes. Once the end nodes=
 identify a labelled packet with NTP they should HW timestamp it asap and p=
ass it on to CPU for further processing.

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Shahram Davari
> Sent: Wednesday, February 02, 2011 1.08 AM
> To: stbryant@cisco.com; tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Hi Stewart,
>=20
> I think with our mechanism you can support NTP as well. NTP=20
> does not need TC processing and only needs Transmit and=20
> Receive timestamps, which are local to the LSP ingress and=20
> Egress nodes. The UDP port number for NTP is different from=20
> PTP and therefore no TC processing will be applied to NTP packets.=20
>=20
> So our mechanism could be generalized to NTP a well. The=20
> co-routed symmetry is needed for both NTP and PTP. The PTP=20
> label is needed for the LSP egress node (for both NTP and=20
> PTP) to sample the timestamp.
>=20
> Thx
> Shahram
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: Tuesday, February 01, 2011 9:48 AM
> To: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> On 01/02/2011 15:52, Bhatia, Manav (Manav) wrote:
> > Hi Yakov,
> >
> > And I still stand by what I said earlier that I don't think=20
> NTP needs to be included here. I'd rather that we keep NTP=20
> and 1588 separate and only merge them if we think its=20
> absolutely essential that a common uniform solution is=20
> developed for the two protocols.
> Manav
>=20
> It is the normal practice of the IETF to design a single common=20
> mechanism for a problem, so you need to justify why we need=20
> to develop a=20
> special purpose protocol rather than develop for instance a time=20
> correction protocol.
>=20
> It would be better in my view to design a correction=20
> mechanism that sits=20
> as preamble to an opaque payload and then fix up the timing packet in=20
> the Timing equivalent of a PW NSP. That would work for any=20
> protocol that=20
> needed time of flight correction.
>=20
> Stewart
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc

From davari@broadcom.com  Wed Feb  2 09:59:49 2011
Return-Path: <davari@broadcom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05CD73A6DAD for <tictoc@core3.amsl.com>; Wed,  2 Feb 2011 09:59:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level: 
X-Spam-Status: No, score=-2.117 tagged_above=-999 required=5 tests=[AWL=0.482,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Vh8ue30QatK for <tictoc@core3.amsl.com>; Wed,  2 Feb 2011 09:59:48 -0800 (PST)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by core3.amsl.com (Postfix) with ESMTP id 12FD23A6DAA for <tictoc@ietf.org>; Wed,  2 Feb 2011 09:59:48 -0800 (PST)
Received: from [10.16.192.232] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Wed, 02 Feb 2011 10:04:33 -0800
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Wed, 2 Feb 2011 10:02:56 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "Yaakov Stein" <yaakov_s@rad.com>, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "stbryant@cisco.com" <stbryant@cisco.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 2 Feb 2011 10:02:54 -0800
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AQHLtwvRa6CYok1lRYSvUt8QtgvK+ZPjbVwAgACmdwCAAAnKAIAAOHqAgAA1goCAAGBBAIAAg+MAgAS/WwCAABihgIAAFdWAgAC9NVD//+psgIAAYkwggABuCbCAAQafMIAAAorQgAACJYCAAB58AIAAUOKAgAC+RiCAAIku0A==
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6941B6EFDEA@SJEXCHCCR02.corp.ad.broadcom.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D484767.9050204@cisco.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB23E1E9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC48E@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC903CDC48E@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6157433B3H014681054-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 02 Feb 2011 17:59:49 -0000

Hi Yaakov,

But I thought NTP doesn't require TC capability (Correction Field Update) a=
t every hop. If so then why do we need such capability for NTP? If what you=
 have in mind is for faster synchronization without waiting for local clock=
 convergence then that is not the way NTP is implemented today.

Thx
Shahram

-----Original Message-----
From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
Sent: Wednesday, February 02, 2011 1:53 AM
To: Bhatia, Manav (Manav); Shahram Davari; stbryant@cisco.com; tictoc@ietf.=
org
Subject: RE: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Manav and Shahram

The whole idea of my proposal is that it can add TC capability to NTP witho=
ut opening up the protocol at the IP level.

This can not be done using the present proposal.

Furthermore, think of a one-way delay measurement OAM packet.
Instead of having to first have a local clock converge at the remote site,
we can just send a packet with the proposed MPLS-level CF, and read the del=
ay
(assuming that the packet handling time is much longer than flight time -
otherwise we still need some bidirectional processing).

So I disagree that there is no advantage to the generic mechanism.

Y(J)S

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: Wednesday, February 02, 2011 02:27
To: Shahram Davari; stbryant@cisco.com; tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

I agree with Shahram. There is not much that needs to be done for NTP in ca=
se we would like to extend this mechanism for NTP as well. NTP is almost li=
ke a BC where the LSP will terminate. There is no TC happening in NTP. Thus=
 the only thing that needs to be done for NTP is to map an LSP/PW with NTP =
so that it can be adequately processed by the end nodes. Once the end nodes=
 identify a labelled packet with NTP they should HW timestamp it asap and p=
ass it on to CPU for further processing.

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Shahram Davari
> Sent: Wednesday, February 02, 2011 1.08 AM
> To: stbryant@cisco.com; tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Hi Stewart,
>=20
> I think with our mechanism you can support NTP as well. NTP=20
> does not need TC processing and only needs Transmit and=20
> Receive timestamps, which are local to the LSP ingress and=20
> Egress nodes. The UDP port number for NTP is different from=20
> PTP and therefore no TC processing will be applied to NTP packets.=20
>=20
> So our mechanism could be generalized to NTP a well. The=20
> co-routed symmetry is needed for both NTP and PTP. The PTP=20
> label is needed for the LSP egress node (for both NTP and=20
> PTP) to sample the timestamp.
>=20
> Thx
> Shahram
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: Tuesday, February 01, 2011 9:48 AM
> To: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> On 01/02/2011 15:52, Bhatia, Manav (Manav) wrote:
> > Hi Yakov,
> >
> > And I still stand by what I said earlier that I don't think=20
> NTP needs to be included here. I'd rather that we keep NTP=20
> and 1588 separate and only merge them if we think its=20
> absolutely essential that a common uniform solution is=20
> developed for the two protocols.
> Manav
>=20
> It is the normal practice of the IETF to design a single common=20
> mechanism for a problem, so you need to justify why we need=20
> to develop a=20
> special purpose protocol rather than develop for instance a time=20
> correction protocol.
>=20
> It would be better in my view to design a correction=20
> mechanism that sits=20
> as preamble to an opaque payload and then fix up the timing packet in=20
> the Timing equivalent of a PW NSP. That would work for any=20
> protocol that=20
> needed time of flight correction.
>=20
> Stewart
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc



From stbryant@cisco.com  Wed Feb  2 10:16:21 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D259C3A6D9A for <tictoc@core3.amsl.com>; Wed,  2 Feb 2011 10:16:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.562
X-Spam-Level: 
X-Spam-Status: No, score=-110.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lu4c85z5WTci for <tictoc@core3.amsl.com>; Wed,  2 Feb 2011 10:16:21 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 0BE393A6D94 for <tictoc@ietf.org>; Wed,  2 Feb 2011 10:16:20 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGouSU1AZnwN/2dsb2JhbAClHHOgUIJZDgGYQIVTBIth
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 02 Feb 2011 18:19:41 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p12IJej7002527; Wed, 2 Feb 2011 18:19:40 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-110.cisco.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p12IJb809473; Wed, 2 Feb 2011 18:19:38 GMT
Message-ID: <4D49A039.5020606@cisco.com>
Date: Wed, 02 Feb 2011 18:19:37 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Shahram Davari <davari@broadcom.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D484767.9050204@cisco.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB23E1E9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC48E@EXRAD5.ad.rad.co.il> <2C2F1EBA8050E74EA81502D5740B4BD6941B6EFDEA@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6941B6EFDEA@SJEXCHCCR02.corp.ad.broadcom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 02 Feb 2011 18:16:21 -0000

Shahram

I think that it would be useful to retrofit TC to NTP to give it greater 
accuracy.

There are far more NTP clients out  there than there 1588 clients, a 
situation that is likely to continue for the foreseeable future.

Stewart


On 02/02/2011 18:02, Shahram Davari wrote:
> Hi Yaakov,
>
> But I thought NTP doesn't require TC capability (Correction Field Update) at every hop. If so then why do we need such capability for NTP? If what you have in mind is for faster synchronization without waiting for local clock convergence then that is not the way NTP is implemented today.
>
> Thx
> Shahram


From davari@broadcom.com  Wed Feb  2 10:25:04 2011
Return-Path: <davari@broadcom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A073C3A67B7 for <tictoc@core3.amsl.com>; Wed,  2 Feb 2011 10:25:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.16
X-Spam-Level: 
X-Spam-Status: No, score=-2.16 tagged_above=-999 required=5 tests=[AWL=0.439,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PEdkwD8k1eq4 for <tictoc@core3.amsl.com>; Wed,  2 Feb 2011 10:25:03 -0800 (PST)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id DB9033A6DD3 for <tictoc@ietf.org>; Wed,  2 Feb 2011 10:25:03 -0800 (PST)
Received: from [10.16.192.232] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Wed, 02 Feb 2011 10:29:50 -0800
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Wed, 2 Feb 2011 10:28:12 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Date: Wed, 2 Feb 2011 10:28:11 -0800
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AcvDBcmMyODJelv7T4+/VxhDMiGWPgAABrJw
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6941B6EFE27@SJEXCHCCR02.corp.ad.broadcom.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D484767.9050204@cisco.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB23E1E9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC48E@EXRAD5.ad.rad.co.il> <2C2F1EBA8050E74EA81502D5740B4BD6941B6EFDEA@SJEXCHCCR02.corp.ad.broadcom.com> <4D49A039.5020606@cisco.com>
In-Reply-To: <4D49A039.5020606@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 61577D14060638795-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 02 Feb 2011 18:25:04 -0000

Hi Stewart,

That is a bigger issue which is outside the scope of this draft. We shouldn=
't add capabilities to this draft for an NTP function that doesn't exist ye=
t.

Besides even assuming NTP is retrofitted with CF capability you still can u=
se our draft to update its CF since existing HW can easily parse an IP/UDP =
packet. But adding new fields to CW is something that requires extensive HW=
 change.

Thanks,
Shahram

-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com]=20
Sent: Wednesday, February 02, 2011 10:20 AM
To: Shahram Davari
Cc: Yaakov Stein; Bhatia, Manav (Manav); tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Shahram

I think that it would be useful to retrofit TC to NTP to give it greater=20
accuracy.

There are far more NTP clients out  there than there 1588 clients, a=20
situation that is likely to continue for the foreseeable future.

Stewart


On 02/02/2011 18:02, Shahram Davari wrote:
> Hi Yaakov,
>
> But I thought NTP doesn't require TC capability (Correction Field Update)=
 at every hop. If so then why do we need such capability for NTP? If what y=
ou have in mind is for faster synchronization without waiting for local clo=
ck convergence then that is not the way NTP is implemented today.
>
> Thx
> Shahram




From manav.bhatia@alcatel-lucent.com  Wed Feb  2 15:28:09 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBE283A6C80 for <tictoc@core3.amsl.com>; Wed,  2 Feb 2011 15:28:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.332
X-Spam-Level: 
X-Spam-Status: No, score=-6.332 tagged_above=-999 required=5 tests=[AWL=0.267,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qNahnTZ+pgKF for <tictoc@core3.amsl.com>; Wed,  2 Feb 2011 15:28:09 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id D60233A6C7A for <tictoc@ietf.org>; Wed,  2 Feb 2011 15:28:08 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p12NVLKO015746 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 2 Feb 2011 17:31:24 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p12NVJ61017820 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 3 Feb 2011 05:01:19 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Thu, 3 Feb 2011 05:01:19 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, Shahram Davari <davari@broadcom.com>
Date: Thu, 3 Feb 2011 05:01:22 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AcvDBcVsIXxFWatPTHuWMTK0h2w1bQAKrVOg
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB23E558@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D484767.9050204@cisco.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB23E1E9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC48E@EXRAD5.ad.rad.co.il> <2C2F1EBA8050E74EA81502D5740B4BD6941B6EFDEA@SJEXCHCCR02.corp.ad.broadcom.com> <4D49A039.5020606@cisco.com>
In-Reply-To: <4D49A039.5020606@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 02 Feb 2011 23:28:09 -0000

Stewart,

Shouldn't the work on retrofitting TC to NTP happen in the NTP WG? This sou=
nds like NTPv4++ to me.

Also as Shahram has earlier said, if we do decide to extend NTP for TC, the=
n all that needs to change in the current draft is that the RSVP object wil=
l now point to the start of the NTP header instead of the PTP header. Most =
of the things defined in this draft should work for NTP as well.

Cheers, Manav

> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]=20
> Sent: Wednesday, February 02, 2011 11.50 PM
> To: Shahram Davari
> Cc: Yaakov Stein; Bhatia, Manav (Manav); tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Shahram
>=20
> I think that it would be useful to retrofit TC to NTP to give=20
> it greater=20
> accuracy.
>=20
> There are far more NTP clients out  there than there 1588 clients, a=20
> situation that is likely to continue for the foreseeable future.
>=20
> Stewart
>=20
>=20
> On 02/02/2011 18:02, Shahram Davari wrote:
> > Hi Yaakov,
> >
> > But I thought NTP doesn't require TC capability (Correction=20
> Field Update) at every hop. If so then why do we need such=20
> capability for NTP? If what you have in mind is for faster=20
> synchronization without waiting for local clock convergence=20
> then that is not the way NTP is implemented today.
> >
> > Thx
> > Shahram
>=20
> =

From yaakov_s@rad.com  Fri Feb  4 02:29:55 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D6DC3A6900 for <tictoc@core3.amsl.com>; Fri,  4 Feb 2011 02:29:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fea7nc1v3rmt for <tictoc@core3.amsl.com>; Fri,  4 Feb 2011 02:29:54 -0800 (PST)
Received: from antivir2.rad.co.il (antivir2.rad.co.il [62.0.23.221]) by core3.amsl.com (Postfix) with ESMTP id BD94A3A68D5 for <tictoc@ietf.org>; Fri,  4 Feb 2011 02:29:50 -0800 (PST)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir2.rad.co.il with ESMTP; 04 Feb 2011 12:33:14 +0200
Received: from EXUS4-DRP.ad.rad.co.il (192.114.24.119) by EXRAD5.ad.rad.co.il (192.114.24.28) with Microsoft SMTP Server (TLS) id 14.1.218.12; Fri, 4 Feb 2011 12:33:00 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Fri, 4 Feb 2011 12:33:00 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, Shahram Davari <davari@broadcom.com>
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AQHLtwvRa6CYok1lRYSvUt8QtgvK+ZPjbVwAgACmdwCAAAnKAIAAOHqAgAA1goCAAGBBAIAAg+MAgAS/WwCAABihgIAAFdWAgAC9NVD//+psgIAAYkwggABuCbCAAQafMIAAAorQgAACJYCAAB58AIAAUOKAgAC+RiCAAIku0P//5DyAgABXGgCAAmrA4A==
Date: Fri, 4 Feb 2011 10:32:59 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CDD284@EXRAD5.ad.rad.co.il>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC032@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB23E180@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D484767.9050204@cisco.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B652E08@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB23E1E9@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CDC48E@EXRAD5.ad.rad.co.il> <2C2F1EBA8050E74EA81502D5740B4BD6941B6EFDEA@SJEXCHCCR02.corp.ad.broadcom.com> <4D49A039.5020606@cisco.com> <7C362EEF9C7896468B36C9B79200D8350CFB23E558@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB23E558@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [207.232.33.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Feb 2011 10:29:55 -0000

Manav and Shahram

What I proposed is exactly NOT updating NTP,
but making a generic mechanism that MAY be used for ANY protocol that cares=
 about time.

For NTP, all one needs to do is to give the present code corrected arrival =
times,
that will automatically reduce PDV and thus increase accuracy.

For RFC-868 the ToD is delivered with much reduced delay error.

Where change is needed is for one-way delay measurement (e.g., OWAMP).

Regarding updating NTP to a new generation,
that is precisely one of TICTOC's charter items
(and indeed in some people's eyes the only thing we should be doing).
TICTOC's purpose is to find improvements to both NTP and 1588,
certainly not only 1588 (which is an IEEE protocol, not an IETF one).

Y(J)S


-----Original Message-----
From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
Sent: Thursday, February 03, 2011 01:31
To: stbryant@cisco.com; Shahram Davari
Cc: Yaakov Stein; tictoc@ietf.org
Subject: RE: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Stewart,

Shouldn't the work on retrofitting TC to NTP happen in the NTP WG? This sou=
nds like NTPv4++ to me.

Also as Shahram has earlier said, if we do decide to extend NTP for TC, the=
n all that needs to change in the current draft is that the RSVP object wil=
l now point to the start of the NTP header instead of the PTP header. Most =
of the things defined in this draft should work for NTP as well.

Cheers, Manav

> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]=20
> Sent: Wednesday, February 02, 2011 11.50 PM
> To: Shahram Davari
> Cc: Yaakov Stein; Bhatia, Manav (Manav); tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Shahram
>=20
> I think that it would be useful to retrofit TC to NTP to give=20
> it greater=20
> accuracy.
>=20
> There are far more NTP clients out  there than there 1588 clients, a=20
> situation that is likely to continue for the foreseeable future.
>=20
> Stewart
>=20
>=20
> On 02/02/2011 18:02, Shahram Davari wrote:
> > Hi Yaakov,
> >
> > But I thought NTP doesn't require TC capability (Correction=20
> Field Update) at every hop. If so then why do we need such=20
> capability for NTP? If what you have in mind is for faster=20
> synchronization without waiting for local clock convergence=20
> then that is not the way NTP is implemented today.
> >
> > Thx
> > Shahram
>=20
>=20

From Peter.Meyer@Zarlink.Com  Wed Feb  9 00:30:07 2011
Return-Path: <Peter.Meyer@Zarlink.Com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D38783A692E for <tictoc@core3.amsl.com>; Wed,  9 Feb 2011 00:30:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wbGy1GPd27TG for <tictoc@core3.amsl.com>; Wed,  9 Feb 2011 00:30:06 -0800 (PST)
Received: from semigate.zarlink.com (semigate.zarlink.com [209.226.172.67]) by core3.amsl.com (Postfix) with ESMTP id 08BEA3A6885 for <tictoc@ietf.org>; Wed,  9 Feb 2011 00:30:05 -0800 (PST)
Received: from ottmta01.zarlink.com (ottmta01 [134.199.14.110]) by semigate.zarlink.com (8.11.6+Sun/8.11.6) with ESMTP id p198U2h27544 for <tictoc@ietf.org>; Wed, 9 Feb 2011 03:30:07 -0500 (EST)
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB18B516@INBANSXCHMBSA1.in.alcatel-lucent.com>
Sensitivity: 
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
X-Mailer: Lotus Notes Release 6.5.1 January 21, 2004
Message-ID: <OF701EB840.07D54922-ON85257832.002AEFCC-85257832.002EAE93@Zarlink.Com>
From: Peter.Meyer@Zarlink.Com
Date: Wed, 9 Feb 2011 03:29:53 -0500
X-MIMETrack: Serialize by Router on ottmta01/Zarlink(Release 7.0.3FP1|February 24, 2008) at 02/09/2011 03:30:06 AM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 09 Feb 2011 08:30:07 -0000

Hi Manav,


A high level point is that for the pure MPLS mapping (section 5.3) , I
wonder if what is really needed is a PTP profile for MPLS -- similar to=

Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For example the IP &=

Ethernet profiles include other information such as the port addressing=
 for
the unicast master table and acceptable master table.  Without a full
profile, although the intermediate notes may operate in TC, the server,=

client and boundary nodes may not operate successfully.

Its not clear if this draft is intended to cover all clock types (OC, B=
C &
TC) or only TC.  There are many sections that talk only about TC withou=
t
considering OC and BC behaviour or impact.  Is BC intended to be covere=
d as
a Client-side OC + Server-side OC model, or is BC excluded from
consideration in this draft?  Perhaps this draft should be either
cleaned-up to consider all clock types or should be restricted to only =
TC
clock type with OC & BC out of scope.


Some specific comments

+ The abstract could be clarified to indicate there are three mappings,=
 not
two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
third mapping may be under discussion, so perhaps this is premature.

+ A few places in the text the phrase "proper handling of these packets=
" or
"properly handle PTP messages" or "perform proper  processing"  is used=
 to
mean transparent clock.  I would propose to remove such language as fro=
m
the ITU-T studies of timing performances of PTP one could argue the
"proper" way is to implement a boundary clock.  Where the intention is =
to
aid the designer of a TC that is fine to describe the implementation
recommendation, but not to suggest this is the way to acheive the best
performance or even the desired way to deploy PTP over MPLS.

+ I would like to see a statement added in the document that the
performance aspects (e.g. the phase or frequency alignment) are outside=
 the
scope of the document.

+ Section 6, 7, 8, 10 and 13 seems to focus only on the TC case between=

OC's and does not consider BC situation.

+ Section 12 text on checksums could be improved to indicate this only
applies to TC and not to OC & BC.

+ Section 16 seems to address only TC clocks and not OC or BC clocks.

+ Section 16.3 implies that the only possible way to handle PTP is TC,
excluding BC --- "don't have the capability to process 1588 packets (e.=
g.
TC processing)" and "   Non-1588-aware LSRs ignore the RSVP 1588_PTP_LS=
P
object and just switch the MPLS packets carrying 1588 messages as data
packets and don't perform any TC processing."


Regards,


ZARLINK Semiconductor
Peter Meyer
Timing & Synchronization
Communication Products Group
Office: +1-613-270-7203=A0 |=A0 Fax: +1-613-592-1010
peter.meyer@zarlink.com =A0| www.zarlink.com



                                                                       =
    
             "Bhatia, Manav                                            =
    
             (Manav)"                                                  =
    
             <manav.bhatia@alc                                         =
 To 
             atel-lucent.com>          "tictoc@ietf.org" <tictoc@ietf.o=
rg> 
             Sent by:                                                  =
 cc 
             <tictoc-bounces@i                                         =
    
             etf.org>                                              Subj=
ect 
                                       [TICTOC]                        =
    
                                       draft-ietf-tictoc-1588overmpls-0=
0.t 
             26/01/2011 11:22          xt                              =
    
             AM                                                        =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    




Hi,

We've tried incorporating most of the comments that we received on the
list. Please ping me if you think we have missed some.

Would be great if the WG can go through this and provide feedback on th=
e
same.

The draft is available here:
http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588overmpls-00.t=
xt

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.or=
g
> Sent: Wednesday, January 26, 2011 9.30 PM
> To: i-d-announce@ietf.org
> Cc: tictoc@ietf.org
> Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> MPLS Networks
>            Author(s)       : S. Davari, et al.
>            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
>            Pages           : 35
>            Date            : 2011-01-26
>
> This document defines the method for transporting PTP messages (PDUs)=

> over an MPLS network to enable a proper handling of these packets
> (e.g. implementation of Transparent Clocks (TC)) in LSRs.
>

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc

=



From manav.bhatia@alcatel-lucent.com  Wed Feb  9 05:20:31 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 280293A69A7 for <tictoc@core3.amsl.com>; Wed,  9 Feb 2011 05:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.529
X-Spam-Level: 
X-Spam-Status: No, score=-6.529 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VX76AxSeLapn for <tictoc@core3.amsl.com>; Wed,  9 Feb 2011 05:20:29 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 2F4EF3A69B9 for <tictoc@ietf.org>; Wed,  9 Feb 2011 05:20:28 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p19DKYNi005862 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 9 Feb 2011 07:20:37 -0600 (CST)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p19DKVa3026625 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 9 Feb 2011 18:50:33 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Wed, 9 Feb 2011 18:50:31 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "Peter.Meyer@Zarlink.Com" <Peter.Meyer@Zarlink.Com>
Date: Wed, 9 Feb 2011 18:50:27 +0530
Thread-Topic: [TICTOC] 1588overmpls-00 / MPLS profile & BC
Thread-Index: AcvIM6+KkbVWG1nCTEGUkVW668T/TQAJwZZw
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB2F6F41@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B516@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF701EB840.07D54922-ON85257832.002AEFCC-85257832.002EAE93@Zarlink.Com>
In-Reply-To: <OF701EB840.07D54922-ON85257832.002AEFCC-85257832.002EAE93@Zarlink.Com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 09 Feb 2011 13:20:31 -0000

Hi Peter,

Very valid comments.=20

This draft covers all clock types - TC, BC and OC. The reason it seems we'v=
e been concentrating on TC is because that's the clock type that requires s=
pecial MPLS processing.=20

For BC's and OC's there is no special processing involved. One just needs a=
n MPLS LSP that terminates on a BC and OC and things will just work. Howeve=
r, I get the drift of what youre saying and we can update the draft to expl=
icitly state this.

I will let someone more knowledgeable respond to your question on whether a=
 separate profile for MPLS is required or not. To my untrained eye it looks=
 that we might.

Cheers, Manav=20

> -----Original Message-----
> From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com]=20
> Sent: Wednesday, February 09, 2011 2.00 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>=20
>=20
> Hi Manav,
>=20
>=20
> A high level point is that for the pure MPLS mapping (section 5.3) , I
> wonder if what is really needed is a PTP profile for MPLS --=20
> similar to
> Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For=20
> example the IP &
> Ethernet profiles include other information such as the port=20
> addressing for
> the unicast master table and acceptable master table.  Without a full
> profile, although the intermediate notes may operate in TC,=20
> the server,
> client and boundary nodes may not operate successfully.
>=20
> Its not clear if this draft is intended to cover all clock=20
> types (OC, BC &
> TC) or only TC.  There are many sections that talk only about=20
> TC without
> considering OC and BC behaviour or impact.  Is BC intended to=20
> be covered as
> a Client-side OC + Server-side OC model, or is BC excluded from
> consideration in this draft?  Perhaps this draft should be either
> cleaned-up to consider all clock types or should be=20
> restricted to only TC
> clock type with OC & BC out of scope.
>=20
>=20
> Some specific comments
>=20
> + The abstract could be clarified to indicate there are three=20
> mappings, not
> two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
> third mapping may be under discussion, so perhaps this is premature.
>=20
> + A few places in the text the phrase "proper handling of=20
> these packets" or
> "properly handle PTP messages" or "perform proper =20
> processing"  is used to
> mean transparent clock.  I would propose to remove such=20
> language as from
> the ITU-T studies of timing performances of PTP one could argue the
> "proper" way is to implement a boundary clock.  Where the=20
> intention is to
> aid the designer of a TC that is fine to describe the implementation
> recommendation, but not to suggest this is the way to acheive the best
> performance or even the desired way to deploy PTP over MPLS.
>=20
> + I would like to see a statement added in the document that the
> performance aspects (e.g. the phase or frequency alignment)=20
> are outside the
> scope of the document.
>=20
> + Section 6, 7, 8, 10 and 13 seems to focus only on the TC=20
> case between
> OC's and does not consider BC situation.
>=20
> + Section 12 text on checksums could be improved to indicate this only
> applies to TC and not to OC & BC.
>=20
> + Section 16 seems to address only TC clocks and not OC or BC clocks.
>=20
> + Section 16.3 implies that the only possible way to handle PTP is TC,
> excluding BC --- "don't have the capability to process 1588=20
> packets (e.g.
> TC processing)" and "   Non-1588-aware LSRs ignore the RSVP=20
> 1588_PTP_LSP
> object and just switch the MPLS packets carrying 1588 messages as data
> packets and don't perform any TC processing."
>=20
>=20
> Regards,
>=20
>=20
> ZARLINK Semiconductor
> Peter Meyer
> Timing & Synchronization
> Communication Products Group
> Office: +1-613-270-7203=A0 |=A0 Fax: +1-613-592-1010
> peter.meyer@zarlink.com =A0| www.zarlink.com
>=20
>=20
>=20
>                                                              =20
>             =20
>              "Bhatia, Manav                                  =20
>             =20
>              (Manav)"                                        =20
>             =20
>              <manav.bhatia@alc                               =20
>           To=20
>              atel-lucent.com>          "tictoc@ietf.org"=20
> <tictoc@ietf.org>=20
>              Sent by:                                        =20
>           cc=20
>              <tictoc-bounces@i                               =20
>             =20
>              etf.org>                                        =20
>      Subject=20
>                                        [TICTOC]              =20
>             =20
>                                       =20
> draft-ietf-tictoc-1588overmpls-00.t=20
>              26/01/2011 11:22          xt                    =20
>             =20
>              AM                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>=20
>=20
>=20
>=20
> Hi,
>=20
> We've tried incorporating most of the comments that we received on the
> list. Please ping me if you think we have missed some.
>=20
> Would be great if the WG can go through this and provide=20
> feedback on the
> same.
>=20
> The draft is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over
> mpls-00.txt
>=20
> Cheers, Manav
>=20
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org
> > [mailto:tictoc-bounces@ietf.org] On Behalf Of=20
> Internet-Drafts@ietf.org
> > Sent: Wednesday, January 26, 2011 9.30 PM
> > To: i-d-announce@ietf.org
> > Cc: tictoc@ietf.org
> > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > MPLS Networks
> >            Author(s)       : S. Davari, et al.
> >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> >            Pages           : 35
> >            Date            : 2011-01-26
> >
> > This document defines the method for transporting PTP=20
> messages (PDUs)
> > over an MPLS network to enable a proper handling of these packets
> > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> >
>=20
> Cheers, Manav
>=20
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
>=20
> ----------
> This email is confidential and may contain information that=20
> is privileged and
> exempt from disclosure by law.  If you have received it in=20
> error, please contact
> the sender immediately by return email and then delete it=20
> from your system; you
> should not copy it or disclose its contents to anyone. =20
> Emails are not secure
> and cannot be guaranteed to be error free as they can be=20
> intercepted, amended,
> lost or destroyed, or contain viruses.  Anyone who=20
> communicates with us by email
> is taken to accept these risks.
> =

From peter.roberts@alcatel-lucent.com  Wed Feb  9 05:52:06 2011
Return-Path: <peter.roberts@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFD623A69C1 for <tictoc@core3.amsl.com>; Wed,  9 Feb 2011 05:52:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id crrEd3fppydC for <tictoc@core3.amsl.com>; Wed,  9 Feb 2011 05:52:05 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 164773A69AD for <tictoc@ietf.org>; Wed,  9 Feb 2011 05:52:05 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p19DqCJR013015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 Feb 2011 07:52:12 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p19DqAaK030269 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 9 Feb 2011 07:52:11 -0600
Received: from USNAVSXCHMBSC2.ndc.alcatel-lucent.com ([135.3.39.147]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Wed, 9 Feb 2011 07:52:11 -0600
From: "Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "Peter.Meyer@Zarlink.Com" <Peter.Meyer@Zarlink.Com>
Date: Wed, 9 Feb 2011 07:52:10 -0600
Thread-Topic: [TICTOC] 1588overmpls-00 / MPLS profile & BC
Thread-Index: AcvIM6+KkbVWG1nCTEGUkVW668T/TQAJwZZwAAD3HSA=
Message-ID: <CA2959F3E75BA645A43E81C3B071F6320ACFEA9560@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B516@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF701EB840.07D54922-ON85257832.002AEFCC-85257832.002EAE93@Zarlink.Com> <7C362EEF9C7896468B36C9B79200D8350CFB2F6F41@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB2F6F41@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 09 Feb 2011 13:52:06 -0000

Peter,
With respect to your comments on the profile, the Annexes are not profiles.=
  They are the portions of the standard that define the rules for running P=
TP over specific lower layer protocols.  These can then be included or excl=
uded from specific profiles that are defined.  This draft is defining these=
 rules for the MPLS environment. =20
The draft covers all the clock types but as you point out this is not all t=
hat clear.  This can be added.
In addition, I don't believe the ITU-T has concluded anything about perform=
ance of BC vs TC.  They have just started studying the issue.  But this dra=
ft is not making any claims about performance and as stated earlier should =
be applicable for any of the clock types.  We can review it to remove any c=
ontentious wording in respect to performance.
Peter R.

  =20

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: February 9, 2011 8:20 AM
To: Peter.Meyer@Zarlink.Com
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Hi Peter,

Very valid comments.=20

This draft covers all clock types - TC, BC and OC. The reason it seems we'v=
e been concentrating on TC is because that's the clock type that requires s=
pecial MPLS processing.=20

For BC's and OC's there is no special processing involved. One just needs a=
n MPLS LSP that terminates on a BC and OC and things will just work. Howeve=
r, I get the drift of what youre saying and we can update the draft to expl=
icitly state this.

I will let someone more knowledgeable respond to your question on whether a=
 separate profile for MPLS is required or not. To my untrained eye it looks=
 that we might.

Cheers, Manav=20

> -----Original Message-----
> From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com]=20
> Sent: Wednesday, February 09, 2011 2.00 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>=20
>=20
> Hi Manav,
>=20
>=20
> A high level point is that for the pure MPLS mapping (section 5.3) , I
> wonder if what is really needed is a PTP profile for MPLS --=20
> similar to
> Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For=20
> example the IP &
> Ethernet profiles include other information such as the port=20
> addressing for
> the unicast master table and acceptable master table.  Without a full
> profile, although the intermediate notes may operate in TC,=20
> the server,
> client and boundary nodes may not operate successfully.
>=20
> Its not clear if this draft is intended to cover all clock=20
> types (OC, BC &
> TC) or only TC.  There are many sections that talk only about=20
> TC without
> considering OC and BC behaviour or impact.  Is BC intended to=20
> be covered as
> a Client-side OC + Server-side OC model, or is BC excluded from
> consideration in this draft?  Perhaps this draft should be either
> cleaned-up to consider all clock types or should be=20
> restricted to only TC
> clock type with OC & BC out of scope.
>=20
>=20
> Some specific comments
>=20
> + The abstract could be clarified to indicate there are three=20
> mappings, not
> two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
> third mapping may be under discussion, so perhaps this is premature.
>=20
> + A few places in the text the phrase "proper handling of=20
> these packets" or
> "properly handle PTP messages" or "perform proper =20
> processing"  is used to
> mean transparent clock.  I would propose to remove such=20
> language as from
> the ITU-T studies of timing performances of PTP one could argue the
> "proper" way is to implement a boundary clock.  Where the=20
> intention is to
> aid the designer of a TC that is fine to describe the implementation
> recommendation, but not to suggest this is the way to acheive the best
> performance or even the desired way to deploy PTP over MPLS.
>=20
> + I would like to see a statement added in the document that the
> performance aspects (e.g. the phase or frequency alignment)=20
> are outside the
> scope of the document.
>=20
> + Section 6, 7, 8, 10 and 13 seems to focus only on the TC=20
> case between
> OC's and does not consider BC situation.
>=20
> + Section 12 text on checksums could be improved to indicate this only
> applies to TC and not to OC & BC.
>=20
> + Section 16 seems to address only TC clocks and not OC or BC clocks.
>=20
> + Section 16.3 implies that the only possible way to handle PTP is TC,
> excluding BC --- "don't have the capability to process 1588=20
> packets (e.g.
> TC processing)" and "   Non-1588-aware LSRs ignore the RSVP=20
> 1588_PTP_LSP
> object and just switch the MPLS packets carrying 1588 messages as data
> packets and don't perform any TC processing."
>=20
>=20
> Regards,
>=20
>=20
> ZARLINK Semiconductor
> Peter Meyer
> Timing & Synchronization
> Communication Products Group
> Office: +1-613-270-7203=A0 |=A0 Fax: +1-613-592-1010
> peter.meyer@zarlink.com =A0| www.zarlink.com
>=20
>=20
>=20
>                                                              =20
>             =20
>              "Bhatia, Manav                                  =20
>             =20
>              (Manav)"                                        =20
>             =20
>              <manav.bhatia@alc                               =20
>           To=20
>              atel-lucent.com>          "tictoc@ietf.org"=20
> <tictoc@ietf.org>=20
>              Sent by:                                        =20
>           cc=20
>              <tictoc-bounces@i                               =20
>             =20
>              etf.org>                                        =20
>      Subject=20
>                                        [TICTOC]              =20
>             =20
>                                       =20
> draft-ietf-tictoc-1588overmpls-00.t=20
>              26/01/2011 11:22          xt                    =20
>             =20
>              AM                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>=20
>=20
>=20
>=20
> Hi,
>=20
> We've tried incorporating most of the comments that we received on the
> list. Please ping me if you think we have missed some.
>=20
> Would be great if the WG can go through this and provide=20
> feedback on the
> same.
>=20
> The draft is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over
> mpls-00.txt
>=20
> Cheers, Manav
>=20
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org
> > [mailto:tictoc-bounces@ietf.org] On Behalf Of=20
> Internet-Drafts@ietf.org
> > Sent: Wednesday, January 26, 2011 9.30 PM
> > To: i-d-announce@ietf.org
> > Cc: tictoc@ietf.org
> > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > MPLS Networks
> >            Author(s)       : S. Davari, et al.
> >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> >            Pages           : 35
> >            Date            : 2011-01-26
> >
> > This document defines the method for transporting PTP=20
> messages (PDUs)
> > over an MPLS network to enable a proper handling of these packets
> > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> >
>=20
> Cheers, Manav
>=20
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
>=20
> ----------
> This email is confidential and may contain information that=20
> is privileged and
> exempt from disclosure by law.  If you have received it in=20
> error, please contact
> the sender immediately by return email and then delete it=20
> from your system; you
> should not copy it or disclose its contents to anyone. =20
> Emails are not secure
> and cannot be guaranteed to be error free as they can be=20
> intercepted, amended,
> lost or destroyed, or contain viruses.  Anyone who=20
> communicates with us by email
> is taken to accept these risks.
>=20
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc

From Peter.Meyer@Zarlink.Com  Wed Feb  9 07:05:18 2011
Return-Path: <Peter.Meyer@Zarlink.Com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 626353A69B4; Wed,  9 Feb 2011 07:05:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b4QqMFMhP3cD; Wed,  9 Feb 2011 07:05:16 -0800 (PST)
Received: from semigate.zarlink.com (semigate.zarlink.com [209.226.172.67]) by core3.amsl.com (Postfix) with ESMTP id C2A6E3A69A8; Wed,  9 Feb 2011 07:05:15 -0800 (PST)
Received: from ottmta01.zarlink.com (ottmta01 [134.199.14.110]) by semigate.zarlink.com (8.11.6+Sun/8.11.6) with ESMTP id p19F5Dh08613;  Wed, 9 Feb 2011 10:05:18 -0500 (EST)
In-Reply-To: <CA2959F3E75BA645A43E81C3B071F6320ACFEA9560@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
To: "Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.4 March 23, 2009
Message-ID: <OF23A1DD85.5C87F3B6-ON85257832.0052BB99-85257832.0052DDFF@Zarlink.Com>
From: Peter.Meyer@Zarlink.Com
Date: Wed, 9 Feb 2011 10:05:30 -0500
X-MIMETrack: Serialize by Router on ottmta01/Zarlink(Release 7.0.3FP1|February 24, 2008) at 02/09/2011 10:05:17 AM, Serialize complete at 02/09/2011 10:05:17 AM
Content-Type: multipart/alternative; boundary="=_alternative 0052DDFE85257832_="
Cc: "tictoc@ietf.org" <tictoc@ietf.org>, tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 09 Feb 2011 15:05:18 -0000

This is a multipart message in MIME format.
--=_alternative 0052DDFE85257832_=
Content-Type: text/plain; charset="US-ASCII"

Thanks.

Yes, a poor choice of words on the Annexes being "profiles".  We would 
still need to fill out the Annex info though re: port addresses and the 
like to ensure inter-operability.

I am fine to be neutral on performance aspects -- I would recommend to 
indicate they are not within scope of the document. 
ZARLINK Semiconductor
Peter Meyer
Timing & Synchronization
Communication Products Group
Office: +1-613-270-7203  |  Fax: +1-613-592-1010
peter.meyer@zarlink.com  | www.zarlink.com





"Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com> 
Sent by: <tictoc-bounces@ietf.org>
09/02/2011 08:52 AM

To
"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, 
"Peter.Meyer@Zarlink.Com" <Peter.Meyer@zarlink.com>
cc
"tictoc@ietf.org" <tictoc@ietf.org>
Subject
Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC






Peter,
With respect to your comments on the profile, the Annexes are not 
profiles.  They are the portions of the standard that define the rules for 
running PTP over specific lower layer protocols.  These can then be 
included or excluded from specific profiles that are defined.  This draft 
is defining these rules for the MPLS environment. 
The draft covers all the clock types but as you point out this is not all 
that clear.  This can be added.
In addition, I don't believe the ITU-T has concluded anything about 
performance of BC vs TC.  They have just started studying the issue.  But 
this draft is not making any claims about performance and as stated 
earlier should be applicable for any of the clock types.  We can review it 
to remove any contentious wording in respect to performance.
Peter R.

 

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf 
Of Bhatia, Manav (Manav)
Sent: February 9, 2011 8:20 AM
To: Peter.Meyer@Zarlink.Com
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Hi Peter,

Very valid comments. 

This draft covers all clock types - TC, BC and OC. The reason it seems 
we've been concentrating on TC is because that's the clock type that 
requires special MPLS processing. 

For BC's and OC's there is no special processing involved. One just needs 
an MPLS LSP that terminates on a BC and OC and things will just work. 
However, I get the drift of what youre saying and we can update the draft 
to explicitly state this.

I will let someone more knowledgeable respond to your question on whether 
a separate profile for MPLS is required or not. To my untrained eye it 
looks that we might.

Cheers, Manav 

> -----Original Message-----
> From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com] 
> Sent: Wednesday, February 09, 2011 2.00 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
> 
> 
> Hi Manav,
> 
> 
> A high level point is that for the pure MPLS mapping (section 5.3) , I
> wonder if what is really needed is a PTP profile for MPLS -- 
> similar to
> Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For 
> example the IP &
> Ethernet profiles include other information such as the port 
> addressing for
> the unicast master table and acceptable master table.  Without a full
> profile, although the intermediate notes may operate in TC, 
> the server,
> client and boundary nodes may not operate successfully.
> 
> Its not clear if this draft is intended to cover all clock 
> types (OC, BC &
> TC) or only TC.  There are many sections that talk only about 
> TC without
> considering OC and BC behaviour or impact.  Is BC intended to 
> be covered as
> a Client-side OC + Server-side OC model, or is BC excluded from
> consideration in this draft?  Perhaps this draft should be either
> cleaned-up to consider all clock types or should be 
> restricted to only TC
> clock type with OC & BC out of scope.
> 
> 
> Some specific comments
> 
> + The abstract could be clarified to indicate there are three 
> mappings, not
> two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
> third mapping may be under discussion, so perhaps this is premature.
> 
> + A few places in the text the phrase "proper handling of 
> these packets" or
> "properly handle PTP messages" or "perform proper 
> processing"  is used to
> mean transparent clock.  I would propose to remove such 
> language as from
> the ITU-T studies of timing performances of PTP one could argue the
> "proper" way is to implement a boundary clock.  Where the 
> intention is to
> aid the designer of a TC that is fine to describe the implementation
> recommendation, but not to suggest this is the way to acheive the best
> performance or even the desired way to deploy PTP over MPLS.
> 
> + I would like to see a statement added in the document that the
> performance aspects (e.g. the phase or frequency alignment) 
> are outside the
> scope of the document.
> 
> + Section 6, 7, 8, 10 and 13 seems to focus only on the TC 
> case between
> OC's and does not consider BC situation.
> 
> + Section 12 text on checksums could be improved to indicate this only
> applies to TC and not to OC & BC.
> 
> + Section 16 seems to address only TC clocks and not OC or BC clocks.
> 
> + Section 16.3 implies that the only possible way to handle PTP is TC,
> excluding BC --- "don't have the capability to process 1588 
> packets (e.g.
> TC processing)" and "   Non-1588-aware LSRs ignore the RSVP 
> 1588_PTP_LSP
> object and just switch the MPLS packets carrying 1588 messages as data
> packets and don't perform any TC processing."
> 
> 
> Regards,
> 
> 
> ZARLINK Semiconductor
> Peter Meyer
> Timing & Synchronization
> Communication Products Group
> Office: +1-613-270-7203  |  Fax: +1-613-592-1010
> peter.meyer@zarlink.com  | www.zarlink.com
> 
> 
> 
> 
> 
>              "Bhatia, Manav 
> 
>              (Manav)" 
> 
>              <manav.bhatia@alc 
>           To 
>              atel-lucent.com>          "tictoc@ietf.org" 
> <tictoc@ietf.org> 
>              Sent by: 
>           cc 
>              <tictoc-bounces@i 
> 
>              etf.org> 
>      Subject 
>                                        [TICTOC] 
> 
> 
> draft-ietf-tictoc-1588overmpls-00.t 
>              26/01/2011 11:22          xt 
> 
>              AM 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Hi,
> 
> We've tried incorporating most of the comments that we received on the
> list. Please ping me if you think we have missed some.
> 
> Would be great if the WG can go through this and provide 
> feedback on the
> same.
> 
> The draft is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over
> mpls-00.txt
> 
> Cheers, Manav
> 
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org
> > [mailto:tictoc-bounces@ietf.org] On Behalf Of 
> Internet-Drafts@ietf.org
> > Sent: Wednesday, January 26, 2011 9.30 PM
> > To: i-d-announce@ietf.org
> > Cc: tictoc@ietf.org
> > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > MPLS Networks
> >            Author(s)       : S. Davari, et al.
> >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> >            Pages           : 35
> >            Date            : 2011-01-26
> >
> > This document defines the method for transporting PTP 
> messages (PDUs)
> > over an MPLS network to enable a proper handling of these packets
> > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> >
> 
> Cheers, Manav
> 
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
> 
> 
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> 
> 
> 
> ----------
> This email is confidential and may contain information that 
> is privileged and
> exempt from disclosure by law.  If you have received it in 
> error, please contact
> the sender immediately by return email and then delete it 
> from your system; you
> should not copy it or disclose its contents to anyone. 
> Emails are not secure
> and cannot be guaranteed to be error free as they can be 
> intercepted, amended,
> lost or destroyed, or contain viruses.  Anyone who 
> communicates with us by email
> is taken to accept these risks.
> 
_______________________________________________
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



--=_alternative 0052DDFE85257832_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Thanks.</font>
<br>
<br><font size=2 face="sans-serif">Yes, a poor choice of words on the Annexes
being &quot;profiles&quot;. &nbsp;We would still need to fill out the Annex
info though re: port addresses and the like to ensure inter-operability.</font>
<br>
<br><font size=2 face="sans-serif">I am fine to be neutral on performance
aspects -- I would recommend to indicate they are not within scope of the
document.</font><font size=2 face="Arial Black"> </font>
<p><font size=2 face="Arial Black"><b>ZARLINK</b></font><font size=3 face="Arial Black"><b>
</b></font><font size=1 face="Trebuchet MS">Semiconductor<b><br>
Peter Meyer</b></font><font size=1 color=#808080 face="Trebuchet MS"><b><i><br>
Timing &amp; Synchronization<br>
Communication Products Group</i></b></font><font size=1 face="Trebuchet MS"><i><br>
Office: +1-613-270-7203</i></font><font size=1 face="Trebuchet MS"><b>&nbsp;
|&nbsp; </b></font><font size=1 face="Trebuchet MS"><i>Fax: +1-613-592-1010</i></font><font size=1 color=blue face="Trebuchet MS"><u><br>
</u></font><a href=mailto:employee.name@zarlink.com><font size=1 color=blue face="Trebuchet MS"><u>peter.meyer@zarlink.com</u></font></a><font size=1 face="Trebuchet MS">
</font><font size=1 face="Trebuchet MS"><b>&nbsp;| </b></font><a href=http://www.zarlink.com/><font size=1 color=blue face="Trebuchet MS"><u>www.zarlink.com</u></font></a><font size=1 face="Trebuchet MS"><br>
</font>
<p>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Roberts, Peter (Peter)&quot;
&lt;peter.roberts@alcatel-lucent.com&gt;</b> </font>
<br><font size=1 face="sans-serif">Sent by: &lt;tictoc-bounces@ietf.org&gt;</font>
<p><font size=1 face="sans-serif">09/02/2011 08:52 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">&quot;Bhatia, Manav (Manav)&quot; &lt;manav.bhatia@alcatel-lucent.com&gt;,
&quot;Peter.Meyer@Zarlink.Com&quot; &lt;Peter.Meyer@zarlink.com&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">&quot;tictoc@ietf.org&quot; &lt;tictoc@ietf.org&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [TICTOC] 1588overmpls-00 / MPLS
profile &amp; BC</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Peter,<br>
With respect to your comments on the profile, the Annexes are not profiles.
&nbsp;They are the portions of the standard that define the rules for running
PTP over specific lower layer protocols. &nbsp;These can then be included
or excluded from specific profiles that are defined. &nbsp;This draft is
defining these rules for the MPLS environment. &nbsp;<br>
The draft covers all the clock types but as you point out this is not all
that clear. &nbsp;This can be added.<br>
In addition, I don't believe the ITU-T has concluded anything about performance
of BC vs TC. &nbsp;They have just started studying the issue. &nbsp;But
this draft is not making any claims about performance and as stated earlier
should be applicable for any of the clock types. &nbsp;We can review it
to remove any contentious wording in respect to performance.<br>
Peter R.<br>
<br>
 &nbsp; <br>
<br>
-----Original Message-----<br>
From: tictoc-bounces@ietf.org [</font></tt><a href="mailto:tictoc-bounces@ietf.org"><tt><font size=2>mailto:tictoc-bounces@ietf.org</font></tt></a><tt><font size=2>]
On Behalf Of Bhatia, Manav (Manav)<br>
Sent: February 9, 2011 8:20 AM<br>
To: Peter.Meyer@Zarlink.Com<br>
Cc: tictoc@ietf.org<br>
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC<br>
<br>
Hi Peter,<br>
<br>
Very valid comments. <br>
<br>
This draft covers all clock types - TC, BC and OC. The reason it seems
we've been concentrating on TC is because that's the clock type that requires
special MPLS processing. <br>
<br>
For BC's and OC's there is no special processing involved. One just needs
an MPLS LSP that terminates on a BC and OC and things will just work. However,
I get the drift of what youre saying and we can update the draft to explicitly
state this.<br>
<br>
I will let someone more knowledgeable respond to your question on whether
a separate profile for MPLS is required or not. To my untrained eye it
looks that we might.<br>
<br>
Cheers, Manav <br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Peter.Meyer@Zarlink.Com [</font></tt><a href=mailto:Peter.Meyer@Zarlink.Com><tt><font size=2>mailto:Peter.Meyer@Zarlink.Com</font></tt></a><tt><font size=2>]
<br>
&gt; Sent: Wednesday, February 09, 2011 2.00 PM<br>
&gt; To: Bhatia, Manav (Manav)<br>
&gt; Cc: tictoc@ietf.org<br>
&gt; Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC<br>
&gt; <br>
&gt; <br>
&gt; Hi Manav,<br>
&gt; <br>
&gt; <br>
&gt; A high level point is that for the pure MPLS mapping (section 5.3)
, I<br>
&gt; wonder if what is really needed is a PTP profile for MPLS -- <br>
&gt; similar to<br>
&gt; Annex D/E/F for IPv4/IPv6/Ethernet, respectively. &nbsp;For <br>
&gt; example the IP &amp;<br>
&gt; Ethernet profiles include other information such as the port <br>
&gt; addressing for<br>
&gt; the unicast master table and acceptable master table. &nbsp;Without
a full<br>
&gt; profile, although the intermediate notes may operate in TC, <br>
&gt; the server,<br>
&gt; client and boundary nodes may not operate successfully.<br>
&gt; <br>
&gt; Its not clear if this draft is intended to cover all clock <br>
&gt; types (OC, BC &amp;<br>
&gt; TC) or only TC. &nbsp;There are many sections that talk only about
<br>
&gt; TC without<br>
&gt; considering OC and BC behaviour or impact. &nbsp;Is BC intended to
<br>
&gt; be covered as<br>
&gt; a Client-side OC + Server-side OC model, or is BC excluded from<br>
&gt; consideration in this draft? &nbsp;Perhaps this draft should be either<br>
&gt; cleaned-up to consider all clock types or should be <br>
&gt; restricted to only TC<br>
&gt; clock type with OC &amp; BC out of scope.<br>
&gt; <br>
&gt; <br>
&gt; Some specific comments<br>
&gt; <br>
&gt; + The abstract could be clarified to indicate there are three <br>
&gt; mappings, not<br>
&gt; two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS). &nbsp;I
think the<br>
&gt; third mapping may be under discussion, so perhaps this is premature.<br>
&gt; <br>
&gt; + A few places in the text the phrase &quot;proper handling of <br>
&gt; these packets&quot; or<br>
&gt; &quot;properly handle PTP messages&quot; or &quot;perform proper &nbsp;<br>
&gt; processing&quot; &nbsp;is used to<br>
&gt; mean transparent clock. &nbsp;I would propose to remove such <br>
&gt; language as from<br>
&gt; the ITU-T studies of timing performances of PTP one could argue the<br>
&gt; &quot;proper&quot; way is to implement a boundary clock. &nbsp;Where
the <br>
&gt; intention is to<br>
&gt; aid the designer of a TC that is fine to describe the implementation<br>
&gt; recommendation, but not to suggest this is the way to acheive the
best<br>
&gt; performance or even the desired way to deploy PTP over MPLS.<br>
&gt; <br>
&gt; + I would like to see a statement added in the document that the<br>
&gt; performance aspects (e.g. the phase or frequency alignment) <br>
&gt; are outside the<br>
&gt; scope of the document.<br>
&gt; <br>
&gt; + Section 6, 7, 8, 10 and 13 seems to focus only on the TC <br>
&gt; case between<br>
&gt; OC's and does not consider BC situation.<br>
&gt; <br>
&gt; + Section 12 text on checksums could be improved to indicate this
only<br>
&gt; applies to TC and not to OC &amp; BC.<br>
&gt; <br>
&gt; + Section 16 seems to address only TC clocks and not OC or BC clocks.<br>
&gt; <br>
&gt; + Section 16.3 implies that the only possible way to handle PTP is
TC,<br>
&gt; excluding BC --- &quot;don't have the capability to process 1588 <br>
&gt; packets (e.g.<br>
&gt; TC processing)&quot; and &quot; &nbsp; Non-1588-aware LSRs ignore
the RSVP <br>
&gt; 1588_PTP_LSP<br>
&gt; object and just switch the MPLS packets carrying 1588 messages as
data<br>
&gt; packets and don't perform any TC processing.&quot;<br>
&gt; <br>
&gt; <br>
&gt; Regards,<br>
&gt; <br>
&gt; <br>
&gt; ZARLINK Semiconductor<br>
&gt; Peter Meyer<br>
&gt; Timing &amp; Synchronization<br>
&gt; Communication Products Group<br>
&gt; Office: +1-613-270-7203&nbsp; |&nbsp; Fax: +1-613-592-1010<br>
&gt; peter.meyer@zarlink.com &nbsp;| </font></tt><a href=www.zarlink.com><tt><font size=2>www.zarlink.com</font></tt></a><tt><font size=2><br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;Bhatia, Manav
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(Manav)&quot; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;manav.bhatia@alc
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; To <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;atel-lucent.com&gt;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;tictoc@ietf.org&quot; <br>
&gt; &lt;tictoc@ietf.org&gt; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Sent by: &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; cc <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;tictoc-bounces@i
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;etf.org&gt; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp;Subject <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[TICTOC]
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; draft-ietf-tictoc-1588overmpls-00.t <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;26/01/2011 11:22 &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;xt &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AM &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Hi,<br>
&gt; <br>
&gt; We've tried incorporating most of the comments that we received on
the<br>
&gt; list. Please ping me if you think we have missed some.<br>
&gt; <br>
&gt; Would be great if the WG can go through this and provide <br>
&gt; feedback on the<br>
&gt; same.<br>
&gt; <br>
&gt; The draft is available here:<br>
&gt; </font></tt><a href="http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over"><tt><font size=2>http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over</font></tt></a><tt><font size=2><br>
&gt; mpls-00.txt<br>
&gt; <br>
&gt; Cheers, Manav<br>
&gt; <br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: tictoc-bounces@ietf.org<br>
&gt; &gt; [</font></tt><a href="mailto:tictoc-bounces@ietf.org"><tt><font size=2>mailto:tictoc-bounces@ietf.org</font></tt></a><tt><font size=2>]
On Behalf Of <br>
&gt; Internet-Drafts@ietf.org<br>
&gt; &gt; Sent: Wednesday, January 26, 2011 9.30 PM<br>
&gt; &gt; To: i-d-announce@ietf.org<br>
&gt; &gt; Cc: tictoc@ietf.org<br>
&gt; &gt; Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.txt<br>
&gt; &gt;<br>
&gt; &gt; A New Internet-Draft is available from the on-line<br>
&gt; &gt; Internet-Drafts directories.<br>
&gt; &gt; This draft is a work item of the Timing over IP Connection<br>
&gt; &gt; and Transfer of Clock Working Group of the IETF.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Title &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; : Transporting PTP messages (1588) over<br>
&gt; &gt; MPLS Networks<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Author(s) &nbsp; &nbsp;
&nbsp; : S. Davari, et al.<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Filename &nbsp; &nbsp;
&nbsp; &nbsp;: draft-ietf-tictoc-1588overmpls-00.txt<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Pages &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; : 35<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Date &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp;: 2011-01-26<br>
&gt; &gt;<br>
&gt; &gt; This document defines the method for transporting PTP <br>
&gt; messages (PDUs)<br>
&gt; &gt; over an MPLS network to enable a proper handling of these packets<br>
&gt; &gt; (e.g. implementation of Transparent Clocks (TC)) in LSRs.<br>
&gt; &gt;<br>
&gt; <br>
&gt; Cheers, Manav<br>
&gt; <br>
&gt; --<br>
&gt; Manav Bhatia,<br>
&gt; IP Division, Alcatel-Lucent,<br>
&gt; Bangalore - India<br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; TICTOC mailing list<br>
&gt; TICTOC@ietf.org<br>
&gt; </font></tt><a href=https://www.ietf.org/mailman/listinfo/tictoc><tt><font size=2>https://www.ietf.org/mailman/listinfo/tictoc</font></tt></a><tt><font size=2><br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; ----------<br>
&gt; This email is confidential and may contain information that <br>
&gt; is privileged and<br>
&gt; exempt from disclosure by law. &nbsp;If you have received it in <br>
&gt; error, please contact<br>
&gt; the sender immediately by return email and then delete it <br>
&gt; from your system; you<br>
&gt; should not copy it or disclose its contents to anyone. &nbsp;<br>
&gt; Emails are not secure<br>
&gt; and cannot be guaranteed to be error free as they can be <br>
&gt; intercepted, amended,<br>
&gt; lost or destroyed, or contain viruses. &nbsp;Anyone who <br>
&gt; communicates with us by email<br>
&gt; is taken to accept these risks.<br>
&gt; <br>
_______________________________________________<br>
TICTOC mailing list<br>
TICTOC@ietf.org<br>
</font></tt><a href=https://www.ietf.org/mailman/listinfo/tictoc><tt><font size=2>https://www.ietf.org/mailman/listinfo/tictoc</font></tt></a><tt><font size=2><br>
_______________________________________________<br>
TICTOC mailing list<br>
TICTOC@ietf.org<br>
</font></tt><a href=https://www.ietf.org/mailman/listinfo/tictoc><tt><font size=2>https://www.ietf.org/mailman/listinfo/tictoc</font></tt></a><tt><font size=2><br>
<br>
</font></tt>
<br>
--=_alternative 0052DDFE85257832_=--

From stefano.ruffini@ericsson.com  Thu Feb 10 08:34:57 2011
Return-Path: <stefano.ruffini@ericsson.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 07D113A69F9; Thu, 10 Feb 2011 08:34:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sOblGPYKDR9N; Thu, 10 Feb 2011 08:34:54 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 8E6BA3A659A; Thu, 10 Feb 2011 08:34:51 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-38-4d5413b789b7
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 36.95.13987.7B3145D4; Thu, 10 Feb 2011 17:35:03 +0100 (CET)
Received: from ESESSCMS0360.eemea.ericsson.se ([169.254.1.40]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Thu, 10 Feb 2011 17:35:02 +0100
From: Stefano Ruffini <stefano.ruffini@ericsson.com>
To: "Peter.Meyer@Zarlink.Com" <Peter.Meyer@Zarlink.Com>, "Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>
Date: Thu, 10 Feb 2011 17:35:02 +0100
Thread-Topic: [TICTOC] 1588overmpls-00 / MPLS profile & BC
Thread-Index: AcvIasz/fGOkmQBQT+GvX7xpCJOr9AA1XK5A
Message-ID: <28C9B1CD4D27844E9CD8F02BFEB70564075118B097@ESESSCMS0360.eemea.ericsson.se>
References: <CA2959F3E75BA645A43E81C3B071F6320ACFEA9560@USNAVSXCHMBSC2.ndc.alcatel-lucent.com> <OF23A1DD85.5C87F3B6-ON85257832.0052BB99-85257832.0052DDFF@Zarlink.Com>
In-Reply-To: <OF23A1DD85.5C87F3B6-ON85257832.0052BB99-85257832.0052DDFF@Zarlink.Com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_28C9B1CD4D27844E9CD8F02BFEB70564075118B097ESESSCMS0360e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "tictoc@ietf.org" <tictoc@ietf.org>, "tictoc-bounces@ietf.org" <tictoc-bounces@ietf.org>
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 10 Feb 2011 16:34:57 -0000

--_000_28C9B1CD4D27844E9CD8F02BFEB70564075118B097ESESSCMS0360e_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Peter M., Peter R.

I wonder if there is really a need (use case) for section 5.3 (pure MPLS ma=
pping) ?

 Best Regards

Stefano

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Peter.Meyer@Zarlink.Com
Sent: mercoled=EC 9 febbraio 2011 16.06
To: Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC


Thanks.

Yes, a poor choice of words on the Annexes being "profiles".  We would stil=
l need to fill out the Annex info though re: port addresses and the like to=
 ensure inter-operability.

I am fine to be neutral on performance aspects -- I would recommend to indi=
cate they are not within scope of the document.

ZARLINK Semiconductor
Peter Meyer
Timing & Synchronization
Communication Products Group
Office: +1-613-270-7203  |  Fax: +1-613-592-1010
peter.meyer@zarlink.com<mailto:employee.name@zarlink.com>  | www.zarlink.co=
m<http://www.zarlink.com/>



"Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>
Sent by: <tictoc-bounces@ietf.org>

09/02/2011 08:52 AM

To
"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "Peter.Meyer@Zar=
link.Com" <Peter.Meyer@zarlink.com>
cc
"tictoc@ietf.org" <tictoc@ietf.org>
Subject
Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC





Peter,
With respect to your comments on the profile, the Annexes are not profiles.=
  They are the portions of the standard that define the rules for running P=
TP over specific lower layer protocols.  These can then be included or excl=
uded from specific profiles that are defined.  This draft is defining these=
 rules for the MPLS environment.
The draft covers all the clock types but as you point out this is not all t=
hat clear.  This can be added.
In addition, I don't believe the ITU-T has concluded anything about perform=
ance of BC vs TC.  They have just started studying the issue.  But this dra=
ft is not making any claims about performance and as stated earlier should =
be applicable for any of the clock types.  We can review it to remove any c=
ontentious wording in respect to performance.
Peter R.



-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: February 9, 2011 8:20 AM
To: Peter.Meyer@Zarlink.Com
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Hi Peter,

Very valid comments.

This draft covers all clock types - TC, BC and OC. The reason it seems we'v=
e been concentrating on TC is because that's the clock type that requires s=
pecial MPLS processing.

For BC's and OC's there is no special processing involved. One just needs a=
n MPLS LSP that terminates on a BC and OC and things will just work. Howeve=
r, I get the drift of what youre saying and we can update the draft to expl=
icitly state this.

I will let someone more knowledgeable respond to your question on whether a=
 separate profile for MPLS is required or not. To my untrained eye it looks=
 that we might.

Cheers, Manav

> -----Original Message-----
> From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com]
> Sent: Wednesday, February 09, 2011 2.00 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
> Hi Manav,
>
>
> A high level point is that for the pure MPLS mapping (section 5.3) , I
> wonder if what is really needed is a PTP profile for MPLS --
> similar to
> Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For
> example the IP &
> Ethernet profiles include other information such as the port
> addressing for
> the unicast master table and acceptable master table.  Without a full
> profile, although the intermediate notes may operate in TC,
> the server,
> client and boundary nodes may not operate successfully.
>
> Its not clear if this draft is intended to cover all clock
> types (OC, BC &
> TC) or only TC.  There are many sections that talk only about
> TC without
> considering OC and BC behaviour or impact.  Is BC intended to
> be covered as
> a Client-side OC + Server-side OC model, or is BC excluded from
> consideration in this draft?  Perhaps this draft should be either
> cleaned-up to consider all clock types or should be
> restricted to only TC
> clock type with OC & BC out of scope.
>
>
> Some specific comments
>
> + The abstract could be clarified to indicate there are three
> mappings, not
> two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
> third mapping may be under discussion, so perhaps this is premature.
>
> + A few places in the text the phrase "proper handling of
> these packets" or
> "properly handle PTP messages" or "perform proper
> processing"  is used to
> mean transparent clock.  I would propose to remove such
> language as from
> the ITU-T studies of timing performances of PTP one could argue the
> "proper" way is to implement a boundary clock.  Where the
> intention is to
> aid the designer of a TC that is fine to describe the implementation
> recommendation, but not to suggest this is the way to acheive the best
> performance or even the desired way to deploy PTP over MPLS.
>
> + I would like to see a statement added in the document that the
> performance aspects (e.g. the phase or frequency alignment)
> are outside the
> scope of the document.
>
> + Section 6, 7, 8, 10 and 13 seems to focus only on the TC
> case between
> OC's and does not consider BC situation.
>
> + Section 12 text on checksums could be improved to indicate this only
> applies to TC and not to OC & BC.
>
> + Section 16 seems to address only TC clocks and not OC or BC clocks.
>
> + Section 16.3 implies that the only possible way to handle PTP is TC,
> excluding BC --- "don't have the capability to process 1588
> packets (e.g.
> TC processing)" and "   Non-1588-aware LSRs ignore the RSVP
> 1588_PTP_LSP
> object and just switch the MPLS packets carrying 1588 messages as data
> packets and don't perform any TC processing."
>
>
> Regards,
>
>
> ZARLINK Semiconductor
> Peter Meyer
> Timing & Synchronization
> Communication Products Group
> Office: +1-613-270-7203  |  Fax: +1-613-592-1010
> peter.meyer@zarlink.com  | www.zarlink.com
>
>
>
>
>
>              "Bhatia, Manav
>
>              (Manav)"
>
>              <manav.bhatia@alc
>           To
>              atel-lucent.com>          "tictoc@ietf.org"
> <tictoc@ietf.org>
>              Sent by:
>           cc
>              <tictoc-bounces@i
>
>              etf.org>
>      Subject
>                                        [TICTOC]
>
>
> draft-ietf-tictoc-1588overmpls-00.t
>              26/01/2011 11:22          xt
>
>              AM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi,
>
> We've tried incorporating most of the comments that we received on the
> list. Please ping me if you think we have missed some.
>
> Would be great if the WG can go through this and provide
> feedback on the
> same.
>
> The draft is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over
> mpls-00.txt
>
> Cheers, Manav
>
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org
> > [mailto:tictoc-bounces@ietf.org] On Behalf Of
> Internet-Drafts@ietf.org
> > Sent: Wednesday, January 26, 2011 9.30 PM
> > To: i-d-announce@ietf.org
> > Cc: tictoc@ietf.org
> > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > MPLS Networks
> >            Author(s)       : S. Davari, et al.
> >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> >            Pages           : 35
> >            Date            : 2011-01-26
> >
> > This document defines the method for transporting PTP
> messages (PDUs)
> > over an MPLS network to enable a proper handling of these packets
> > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> >
>
> Cheers, Manav
>
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>
>
> ----------
> This email is confidential and may contain information that
> is privileged and
> exempt from disclosure by law.  If you have received it in
> error, please contact
> the sender immediately by return email and then delete it
> from your system; you
> should not copy it or disclose its contents to anyone.
> Emails are not secure
> and cannot be guaranteed to be error free as they can be
> intercepted, amended,
> lost or destroyed, or contain viruses.  Anyone who
> communicates with us by email
> is taken to accept these risks.
>
_______________________________________________
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



--_000_28C9B1CD4D27844E9CD8F02BFEB70564075118B097ESESSCMS0360e_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.6001.18527" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN lang=3DIT>
<P><SPAN class=3D449293316-10022011>Peter M., Peter R.</SPAN></P>
<P><SPAN class=3D449293316-10022011></SPAN><SPAN class=3D449293316-10022011=
>I wonder=20
if there is really a need (</SPAN>use case<SPAN=20
class=3D449293316-10022011>)</SPAN> for section 5.3 (pure MPLS mapping)<SPA=
N=20
class=3D449293316-10022011> ?</SPAN></P>
<P><SPAN class=3D449293316-10022011>&nbsp;</SPAN>Best Regards</P>
<P>Stefano </P></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> tictoc-bounces@ietf.org=20
[mailto:tictoc-bounces@ietf.org] <B>On Behalf Of=20
</B>Peter.Meyer@Zarlink.Com<BR><B>Sent:</B> mercoled=EC 9 febbraio 2011=20
16.06<BR><B>To:</B> Roberts, Peter (Peter)<BR><B>Cc:</B> tictoc@ietf.org;=20
tictoc-bounces@ietf.org<BR><B>Subject:</B> Re: [TICTOC] 1588overmpls-00 / M=
PLS=20
profile &amp; BC<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=3Dsans-serif size=3D2>Thanks.</FONT> <BR><BR><FON=
T=20
face=3Dsans-serif size=3D2>Yes, a poor choice of words on the Annexes being=
=20
"profiles". &nbsp;We would still need to fill out the Annex info though re:=
 port=20
addresses and the like to ensure inter-operability.</FONT> <BR><BR><FONT=20
face=3Dsans-serif size=3D2>I am fine to be neutral on performance aspects -=
- I would=20
recommend to indicate they are not within scope of the document.</FONT><FON=
T=20
face=3D"Arial Black" size=3D2> </FONT>
<P><FONT face=3D"Arial Black" size=3D2><B>ZARLINK</B></FONT><FONT face=3D"A=
rial Black"=20
size=3D3><B> </B></FONT><FONT face=3D"Trebuchet MS" size=3D1>Semiconductor<=
B><BR>Peter=20
Meyer</B></FONT><FONT face=3D"Trebuchet MS" color=3D#808080 size=3D1><B><I>=
<BR>Timing=20
&amp; Synchronization<BR>Communication Products Group</I></B></FONT><FONT=20
face=3D"Trebuchet MS" size=3D1><I><BR>Office: +1-613-270-7203</I></FONT><FO=
NT=20
face=3D"Trebuchet MS" size=3D1><B>&nbsp; |&nbsp; </B></FONT><FONT=20
face=3D"Trebuchet MS" size=3D1><I>Fax: +1-613-592-1010</I></FONT><FONT=20
face=3D"Trebuchet MS" color=3Dblue size=3D1><U><BR></U></FONT><A=20
href=3D"mailto:employee.name@zarlink.com"><FONT face=3D"Trebuchet MS" color=
=3Dblue=20
size=3D1><U>peter.meyer@zarlink.com</U></FONT></A><FONT face=3D"Trebuchet M=
S"=20
size=3D1> </FONT><FONT face=3D"Trebuchet MS" size=3D1><B>&nbsp;| </B></FONT=
><A=20
href=3D"http://www.zarlink.com/"><FONT face=3D"Trebuchet MS" color=3Dblue=20
size=3D1><U>www.zarlink.com</U></FONT></A><FONT face=3D"Trebuchet MS"=20
size=3D1><BR></FONT>
<P><BR><BR><BR>
<TABLE width=3D"100%">
  <TBODY>
  <TR vAlign=3Dtop>
    <TD width=3D"40%"><FONT face=3Dsans-serif size=3D1><B>"Roberts, Peter (=
Peter)"=20
      &lt;peter.roberts@alcatel-lucent.com&gt;</B> </FONT><BR><FONT=20
      face=3Dsans-serif size=3D1>Sent by: &lt;tictoc-bounces@ietf.org&gt;</=
FONT>=20
      <P><FONT face=3Dsans-serif size=3D1>09/02/2011 08:52 AM</FONT> </P>
    <TD width=3D"59%">
      <TABLE width=3D"100%">
        <TBODY>
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT face=3Dsans-serif size=3D1>To</FONT></=
DIV>
          <TD><FONT face=3Dsans-serif size=3D1>"Bhatia, Manav (Manav)"=20
            &lt;manav.bhatia@alcatel-lucent.com&gt;, "Peter.Meyer@Zarlink.C=
om"=20
            &lt;Peter.Meyer@zarlink.com&gt;</FONT>=20
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT face=3Dsans-serif size=3D1>cc</FONT></=
DIV>
          <TD><FONT face=3Dsans-serif size=3D1>"tictoc@ietf.org"=20
            &lt;tictoc@ietf.org&gt;</FONT>=20
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT face=3Dsans-serif size=3D1>Subject</FO=
NT></DIV>
          <TD><FONT face=3Dsans-serif size=3D1>Re: [TICTOC] 1588overmpls-00=
 / MPLS=20
            profile &amp; BC</FONT></TR></TBODY></TABLE><BR>
      <TABLE>
        <TBODY>
        <TR vAlign=3Dtop>
          <TD>
          <TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><TT=
><FONT=20
size=3D2>Peter,<BR>With respect to your comments on the profile, the Annexe=
s are=20
not profiles. &nbsp;They are the portions of the standard that define the r=
ules=20
for running PTP over specific lower layer protocols. &nbsp;These can then b=
e=20
included or excluded from specific profiles that are defined. &nbsp;This dr=
aft=20
is defining these rules for the MPLS environment. &nbsp;<BR>The draft cover=
s all=20
the clock types but as you point out this is not all that clear. &nbsp;This=
 can=20
be added.<BR>In addition, I don't believe the ITU-T has concluded anything =
about=20
performance of BC vs TC. &nbsp;They have just started studying the issue.=20
&nbsp;But this draft is not making any claims about performance and as stat=
ed=20
earlier should be applicable for any of the clock types. &nbsp;We can revie=
w it=20
to remove any contentious wording in respect to performance.<BR>Peter=20
R.<BR><BR>&nbsp; <BR><BR>-----Original Message-----<BR>From:=20
tictoc-bounces@ietf.org [</FONT></TT><A=20
href=3D"mailto:tictoc-bounces@ietf.org"><TT><FONT=20
size=3D2>mailto:tictoc-bounces@ietf.org</FONT></TT></A><TT><FONT size=3D2>]=
 On=20
Behalf Of Bhatia, Manav (Manav)<BR>Sent: February 9, 2011 8:20 AM<BR>To:=20
Peter.Meyer@Zarlink.Com<BR>Cc: tictoc@ietf.org<BR>Subject: Re: [TICTOC]=20
1588overmpls-00 / MPLS profile &amp; BC<BR><BR>Hi Peter,<BR><BR>Very valid=
=20
comments. <BR><BR>This draft covers all clock types - TC, BC and OC. The re=
ason=20
it seems we've been concentrating on TC is because that's the clock type th=
at=20
requires special MPLS processing. <BR><BR>For BC's and OC's there is no spe=
cial=20
processing involved. One just needs an MPLS LSP that terminates on a BC and=
 OC=20
and things will just work. However, I get the drift of what youre saying an=
d we=20
can update the draft to explicitly state this.<BR><BR>I will let someone mo=
re=20
knowledgeable respond to your question on whether a separate profile for MP=
LS is=20
required or not. To my untrained eye it looks that we might.<BR><BR>Cheers,=
=20
Manav <BR><BR>&gt; -----Original Message-----<BR>&gt; From:=20
Peter.Meyer@Zarlink.Com [</FONT></TT><A=20
href=3D"mailto:Peter.Meyer@Zarlink.Com"><TT><FONT=20
size=3D2>mailto:Peter.Meyer@Zarlink.Com</FONT></TT></A><TT><FONT size=3D2>]=
 <BR>&gt;=20
Sent: Wednesday, February 09, 2011 2.00 PM<BR>&gt; To: Bhatia, Manav=20
(Manav)<BR>&gt; Cc: tictoc@ietf.org<BR>&gt; Subject: Re: [TICTOC]=20
1588overmpls-00 / MPLS profile &amp; BC<BR>&gt; <BR>&gt; <BR>&gt; Hi=20
Manav,<BR>&gt; <BR>&gt; <BR>&gt; A high level point is that for the pure MP=
LS=20
mapping (section 5.3) , I<BR>&gt; wonder if what is really needed is a PTP=
=20
profile for MPLS -- <BR>&gt; similar to<BR>&gt; Annex D/E/F for=20
IPv4/IPv6/Ethernet, respectively. &nbsp;For <BR>&gt; example the IP=20
&amp;<BR>&gt; Ethernet profiles include other information such as the port=
=20
<BR>&gt; addressing for<BR>&gt; the unicast master table and acceptable mas=
ter=20
table. &nbsp;Without a full<BR>&gt; profile, although the intermediate note=
s may=20
operate in TC, <BR>&gt; the server,<BR>&gt; client and boundary nodes may n=
ot=20
operate successfully.<BR>&gt; <BR>&gt; Its not clear if this draft is inten=
ded=20
to cover all clock <BR>&gt; types (OC, BC &amp;<BR>&gt; TC) or only TC.=20
&nbsp;There are many sections that talk only about <BR>&gt; TC without<BR>&=
gt;=20
considering OC and BC behaviour or impact. &nbsp;Is BC intended to <BR>&gt;=
 be=20
covered as<BR>&gt; a Client-side OC + Server-side OC model, or is BC exclud=
ed=20
from<BR>&gt; consideration in this draft? &nbsp;Perhaps this draft should b=
e=20
either<BR>&gt; cleaned-up to consider all clock types or should be <BR>&gt;=
=20
restricted to only TC<BR>&gt; clock type with OC &amp; BC out of scope.<BR>=
&gt;=20
<BR>&gt; <BR>&gt; Some specific comments<BR>&gt; <BR>&gt; + The abstract co=
uld=20
be clarified to indicate there are three <BR>&gt; mappings, not<BR>&gt; two=
=20
(pure MPLS, UDP/IP over MPLS and Ethernet over MPLS). &nbsp;I think the<BR>=
&gt;=20
third mapping may be under discussion, so perhaps this is premature.<BR>&gt=
;=20
<BR>&gt; + A few places in the text the phrase "proper handling of <BR>&gt;=
=20
these packets" or<BR>&gt; "properly handle PTP messages" or "perform proper=
=20
&nbsp;<BR>&gt; processing" &nbsp;is used to<BR>&gt; mean transparent clock.=
=20
&nbsp;I would propose to remove such <BR>&gt; language as from<BR>&gt; the =
ITU-T=20
studies of timing performances of PTP one could argue the<BR>&gt; "proper" =
way=20
is to implement a boundary clock. &nbsp;Where the <BR>&gt; intention is=20
to<BR>&gt; aid the designer of a TC that is fine to describe the=20
implementation<BR>&gt; recommendation, but not to suggest this is the way t=
o=20
acheive the best<BR>&gt; performance or even the desired way to deploy PTP =
over=20
MPLS.<BR>&gt; <BR>&gt; + I would like to see a statement added in the docum=
ent=20
that the<BR>&gt; performance aspects (e.g. the phase or frequency alignment=
)=20
<BR>&gt; are outside the<BR>&gt; scope of the document.<BR>&gt; <BR>&gt; +=
=20
Section 6, 7, 8, 10 and 13 seems to focus only on the TC <BR>&gt; case=20
between<BR>&gt; OC's and does not consider BC situation.<BR>&gt; <BR>&gt; +=
=20
Section 12 text on checksums could be improved to indicate this only<BR>&gt=
;=20
applies to TC and not to OC &amp; BC.<BR>&gt; <BR>&gt; + Section 16 seems t=
o=20
address only TC clocks and not OC or BC clocks.<BR>&gt; <BR>&gt; + Section =
16.3=20
implies that the only possible way to handle PTP is TC,<BR>&gt; excluding B=
C ---=20
"don't have the capability to process 1588 <BR>&gt; packets (e.g.<BR>&gt; T=
C=20
processing)" and " &nbsp; Non-1588-aware LSRs ignore the RSVP <BR>&gt;=20
1588_PTP_LSP<BR>&gt; object and just switch the MPLS packets carrying 1588=
=20
messages as data<BR>&gt; packets and don't perform any TC processing."<BR>&=
gt;=20
<BR>&gt; <BR>&gt; Regards,<BR>&gt; <BR>&gt; <BR>&gt; ZARLINK=20
Semiconductor<BR>&gt; Peter Meyer<BR>&gt; Timing &amp; Synchronization<BR>&=
gt;=20
Communication Products Group<BR>&gt; Office: +1-613-270-7203&nbsp; |&nbsp; =
Fax:=20
+1-613-592-1010<BR>&gt; peter.meyer@zarlink.com &nbsp;| </FONT></TT><A=20
href=3D"www.zarlink.com"><TT><FONT size=3D2>www.zarlink.com</FONT></TT></A>=
<TT><FONT=20
size=3D2><BR>&gt; <BR>&gt; <BR>&gt; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"Bhatia, Man=
av=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;(Manav)" &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &n=
bsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;manav.bhatia@alc &nbsp; &nbsp; &nbsp;=
=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; To <BR>&gt; &nbsp;=
=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;atel-lucent.com&gt; &nbsp; &nbsp;=
=20
&nbsp; &nbsp; &nbsp;"tictoc@ietf.org" <BR>&gt; &lt;tictoc@ietf.org&gt; <BR>=
&gt;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Sent by: &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; cc <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;&lt;tictoc-bounces@i &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp;etf.org&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp;Subject <BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[TICTOC] &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;<BR>&gt; draft-ietf-tictoc-1588overmpls-00.t <BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp;26/01/2011 11:22 &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;xt=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&=
gt;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp;AM &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &n=
bsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nb=
sp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &n=
bsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; <BR>&gt; <BR>&gt; <BR>&gt; <BR>&gt;=20
Hi,<BR>&gt; <BR>&gt; We've tried incorporating most of the comments that we=
=20
received on the<BR>&gt; list. Please ping me if you think we have missed=20
some.<BR>&gt; <BR>&gt; Would be great if the WG can go through this and pro=
vide=20
<BR>&gt; feedback on the<BR>&gt; same.<BR>&gt; <BR>&gt; The draft is availa=
ble=20
here:<BR>&gt; </FONT></TT><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over"><TT=
><FONT=20
size=3D2>http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over</FO=
NT></TT></A><TT><FONT=20
size=3D2><BR>&gt; mpls-00.txt<BR>&gt; <BR>&gt; Cheers, Manav<BR>&gt; <BR>&g=
t; &gt;=20
-----Original Message-----<BR>&gt; &gt; From: tictoc-bounces@ietf.org<BR>&g=
t;=20
&gt; [</FONT></TT><A href=3D"mailto:tictoc-bounces@ietf.org"><TT><FONT=20
size=3D2>mailto:tictoc-bounces@ietf.org</FONT></TT></A><TT><FONT size=3D2>]=
 On=20
Behalf Of <BR>&gt; Internet-Drafts@ietf.org<BR>&gt; &gt; Sent: Wednesday,=20
January 26, 2011 9.30 PM<BR>&gt; &gt; To: i-d-announce@ietf.org<BR>&gt; &gt=
; Cc:=20
tictoc@ietf.org<BR>&gt; &gt; Subject: [TICTOC] I-D=20
Action:draft-ietf-tictoc-1588overmpls-00.txt<BR>&gt; &gt;<BR>&gt; &gt; A Ne=
w=20
Internet-Draft is available from the on-line<BR>&gt; &gt; Internet-Drafts=20
directories.<BR>&gt; &gt; This draft is a work item of the Timing over IP=20
Connection<BR>&gt; &gt; and Transfer of Clock Working Group of the IETF.<BR=
>&gt;=20
&gt;<BR>&gt; &gt;<BR>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Tit=
le=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : Transporting PTP messages (1588)=20
over<BR>&gt; &gt; MPLS Networks<BR>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;=20
&nbsp;Author(s) &nbsp; &nbsp; &nbsp; : S. Davari, et al.<BR>&gt; &gt; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Filename &nbsp; &nbsp; &nbsp; &nbsp;:=20
draft-ietf-tictoc-1588overmpls-00.txt<BR>&gt; &gt; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; &nbsp;Pages &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 35<BR>&gt; &gt; &nb=
sp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Date &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;: 2011-01-26<BR>&gt; &gt;<BR>&gt; &gt; This document defines the meth=
od=20
for transporting PTP <BR>&gt; messages (PDUs)<BR>&gt; &gt; over an MPLS net=
work=20
to enable a proper handling of these packets<BR>&gt; &gt; (e.g. implementat=
ion=20
of Transparent Clocks (TC)) in LSRs.<BR>&gt; &gt;<BR>&gt; <BR>&gt; Cheers,=
=20
Manav<BR>&gt; <BR>&gt; --<BR>&gt; Manav Bhatia,<BR>&gt; IP Division,=20
Alcatel-Lucent,<BR>&gt; Bangalore - India<BR>&gt; <BR>&gt; <BR>&gt;=20
_______________________________________________<BR>&gt; TICTOC mailing=20
list<BR>&gt; TICTOC@ietf.org<BR>&gt; </FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/tictoc</FONT></TT></A><TT><F=
ONT=20
size=3D2><BR>&gt; <BR>&gt; <BR>&gt; <BR>&gt; ----------<BR>&gt; This email =
is=20
confidential and may contain information that <BR>&gt; is privileged and<BR=
>&gt;=20
exempt from disclosure by law. &nbsp;If you have received it in <BR>&gt; er=
ror,=20
please contact<BR>&gt; the sender immediately by return email and then dele=
te it=20
<BR>&gt; from your system; you<BR>&gt; should not copy it or disclose its=20
contents to anyone. &nbsp;<BR>&gt; Emails are not secure<BR>&gt; and cannot=
 be=20
guaranteed to be error free as they can be <BR>&gt; intercepted,=20
amended,<BR>&gt; lost or destroyed, or contain viruses. &nbsp;Anyone who=20
<BR>&gt; communicates with us by email<BR>&gt; is taken to accept these=20
risks.<BR>&gt; <BR>_______________________________________________<BR>TICTO=
C=20
mailing list<BR>TICTOC@ietf.org<BR></FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/tictoc</FONT></TT></A><TT><F=
ONT=20
size=3D2><BR>_______________________________________________<BR>TICTOC mail=
ing=20
list<BR>TICTOC@ietf.org<BR></FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/tictoc</FONT></TT></A><TT><F=
ONT=20
size=3D2><BR><BR></FONT></TT><BR></P></BODY></HTML>

--_000_28C9B1CD4D27844E9CD8F02BFEB70564075118B097ESESSCMS0360e_--

From Peter.Meyer@Zarlink.Com  Thu Feb 10 16:27:16 2011
Return-Path: <Peter.Meyer@Zarlink.Com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 596FD3A6B18 for <tictoc@core3.amsl.com>; Thu, 10 Feb 2011 16:27:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7RjtDaE117jW for <tictoc@core3.amsl.com>; Thu, 10 Feb 2011 16:27:13 -0800 (PST)
Received: from semigate.zarlink.com (semigate.zarlink.com [209.226.172.67]) by core3.amsl.com (Postfix) with ESMTP id 434633A6813 for <tictoc@ietf.org>; Thu, 10 Feb 2011 16:27:12 -0800 (PST)
Received: from ottmta01.zarlink.com (ottmta01 [134.199.14.110]) by semigate.zarlink.com (8.11.6+Sun/8.11.6) with ESMTP id p1B0NYd04366 for <tictoc@ietf.org>; Thu, 10 Feb 2011 19:27:25 -0500 (EST)
In-Reply-To: <28C9B1CD4D27844E9CD8F02BFEB70564075118B097@ESESSCMS0360.eemea.ericsson.se>
To: Stefano Ruffini <stefano.ruffini@ericsson.com>
X-Mailer: Lotus Notes Release 6.5.1 January 21, 2004
Message-ID: <OF357355FD.A2511CF3-ON85257834.0001E94E-85257834.00022452@Zarlink.Com>
From: Peter.Meyer@Zarlink.Com
Date: Thu, 10 Feb 2011 19:23:23 -0500
X-MIMETrack: Serialize by Router on ottmta01/Zarlink(Release 7.0.3FP1|February 24, 2008) at 02/10/2011 07:27:24 PM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Feb 2011 00:27:16 -0000

Hi Stefano,

I do not know if there is a need for pure MPLS mapping, it is not reall=
y an
area with which I am familiar.

My opinion is only that if an MPLS mapping is added for PTP, that we mu=
st
fully define the PTP operation (in-line with the other Annexes in IEEE
1588) to support all the PTP features and ensure inter-operability.

Regards,


ZARLINK Semiconductor
Peter Meyer
Timing & Synchronization
Communication Products Group
Office: +1-613-270-7203=A0 |=A0 Fax: +1-613-592-1010
peter.meyer@zarlink.com =A0| www.zarlink.com



                                                                       =
    
             Stefano Ruffini                                           =
    
             <stefano.ruffini@                                         =
    
             ericsson.com>                                             =
 To 
             Sent by:                  "Peter.Meyer@Zarlink.Com"       =
    
             <tictoc-bounces@i         <Peter.Meyer@zarlink.com>,      =
    
             etf.org>                  "Roberts, Peter       (Peter)"  =
    
                                       <peter.roberts@alcatel-lucent.co=
m>  
                                                                       =
 cc 
             10/02/2011 11:35          "tictoc@ietf.org"               =
    
             AM                        <tictoc@ietf.org>,              =
    
                                       "tictoc-bounces@ietf.org"       =
    
                                       <tictoc-bounces@ietf.org>       =
    
                                                                   Subj=
ect 
                                       Re: [TICTOC] 1588overmpls-00 / M=
PLS 
                                       profile & BC                    =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    




Peter M., Peter R.


I wonder if there is really a need (use case) for section 5.3 (pure MPL=
S
mapping) ?


 Best Regards


Stefano



From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behal=
f Of
Peter.Meyer@Zarlink.Com
Sent: mercoled=EC 9 febbraio 2011 16.06
To: Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC


Thanks.

Yes, a poor choice of words on the Annexes being "profiles".  We would
still need to fill out the Annex info though re: port addresses and the=

like to ensure inter-operability.

I am fine to be neutral on performance aspects -- I would recommend to
indicate they are not within scope of the document.


ZARLINK Semiconductor
Peter Meyer
Timing & Synchronization
Communication Products Group
Office: +1-613-270-7203  |  Fax: +1-613-592-1010
peter.meyer@zarlink.com  | www.zarlink.com




                                                                       =
    
 "Roberts, Peter (Peter)"                                              =
    
 <peter.roberts@alcatel-luc                                            =
    
 ent.com>                                                              =
    
 Sent by:                                                              =
 To 
 <tictoc-bounces@ietf.org>                      "Bhatia, Manav (Manav)"=
    
                                                <manav.bhatia@alcatel-l=
uce 
                                                nt.com>,               =
    
 09/02/2011 08:52 AM                            "Peter.Meyer@Zarlink.Co=
m"  
                                                <Peter.Meyer@zarlink.co=
m>  
                                                                       =
 cc 
                                                "tictoc@ietf.org"      =
    
                                                <tictoc@ietf.org>      =
    
                                                                   Subj=
ect 
                                                Re: [TICTOC]           =
    
                                                1588overmpls-00 / MPLS =
    
                                                profile & BC           =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    





Peter,
With respect to your comments on the profile, the Annexes are not profi=
les.
They are the portions of the standard that define the rules for running=
 PTP
over specific lower layer protocols.  These can then be included or
excluded from specific profiles that are defined.  This draft is defini=
ng
these rules for the MPLS environment.
The draft covers all the clock types but as you point out this is not a=
ll
that clear.  This can be added.
In addition, I don't believe the ITU-T has concluded anything about
performance of BC vs TC.  They have just started studying the issue.  B=
ut
this draft is not making any claims about performance and as stated ear=
lier
should be applicable for any of the clock types.  We can review it to
remove any contentious wording in respect to performance.
Peter R.



-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behal=
f Of
Bhatia, Manav (Manav)
Sent: February 9, 2011 8:20 AM
To: Peter.Meyer@Zarlink.Com
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Hi Peter,

Very valid comments.

This draft covers all clock types - TC, BC and OC. The reason it seems
we've been concentrating on TC is because that's the clock type that
requires special MPLS processing.

For BC's and OC's there is no special processing involved. One just nee=
ds
an MPLS LSP that terminates on a BC and OC and things will just work.
However, I get the drift of what youre saying and we can update the dra=
ft
to explicitly state this.

I will let someone more knowledgeable respond to your question on wheth=
er a
separate profile for MPLS is required or not. To my untrained eye it lo=
oks
that we might.

Cheers, Manav

> -----Original Message-----
> From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com]
> Sent: Wednesday, February 09, 2011 2.00 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
> Hi Manav,
>
>
> A high level point is that for the pure MPLS mapping (section 5.3) , =
I
> wonder if what is really needed is a PTP profile for MPLS --
> similar to
> Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For
> example the IP &
> Ethernet profiles include other information such as the port
> addressing for
> the unicast master table and acceptable master table.  Without a full=

> profile, although the intermediate notes may operate in TC,
> the server,
> client and boundary nodes may not operate successfully.
>
> Its not clear if this draft is intended to cover all clock
> types (OC, BC &
> TC) or only TC.  There are many sections that talk only about
> TC without
> considering OC and BC behaviour or impact.  Is BC intended to
> be covered as
> a Client-side OC + Server-side OC model, or is BC excluded from
> consideration in this draft?  Perhaps this draft should be either
> cleaned-up to consider all clock types or should be
> restricted to only TC
> clock type with OC & BC out of scope.
>
>
> Some specific comments
>
> + The abstract could be clarified to indicate there are three
> mappings, not
> two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think th=
e
> third mapping may be under discussion, so perhaps this is premature.
>
> + A few places in the text the phrase "proper handling of
> these packets" or
> "properly handle PTP messages" or "perform proper
> processing"  is used to
> mean transparent clock.  I would propose to remove such
> language as from
> the ITU-T studies of timing performances of PTP one could argue the
> "proper" way is to implement a boundary clock.  Where the
> intention is to
> aid the designer of a TC that is fine to describe the implementation
> recommendation, but not to suggest this is the way to acheive the bes=
t
> performance or even the desired way to deploy PTP over MPLS.
>
> + I would like to see a statement added in the document that the
> performance aspects (e.g. the phase or frequency alignment)
> are outside the
> scope of the document.
>
> + Section 6, 7, 8, 10 and 13 seems to focus only on the TC
> case between
> OC's and does not consider BC situation.
>
> + Section 12 text on checksums could be improved to indicate this onl=
y
> applies to TC and not to OC & BC.
>
> + Section 16 seems to address only TC clocks and not OC or BC clocks.=

>
> + Section 16.3 implies that the only possible way to handle PTP is TC=
,
> excluding BC --- "don't have the capability to process 1588
> packets (e.g.
> TC processing)" and "   Non-1588-aware LSRs ignore the RSVP
> 1588_PTP_LSP
> object and just switch the MPLS packets carrying 1588 messages as dat=
a
> packets and don't perform any TC processing."
>
>
> Regards,
>
>
> ZARLINK Semiconductor
> Peter Meyer
> Timing & Synchronization
> Communication Products Group
> Office: +1-613-270-7203  |  Fax: +1-613-592-1010
> peter.meyer@zarlink.com  | www.zarlink.com
>
>
>
>
>
>              "Bhatia, Manav
>
>              (Manav)"
>
>              <manav.bhatia@alc
>           To
>              atel-lucent.com>          "tictoc@ietf.org"
> <tictoc@ietf.org>
>              Sent by:
>           cc
>              <tictoc-bounces@i
>
>              etf.org>
>      Subject
>                                        [TICTOC]
>
>
> draft-ietf-tictoc-1588overmpls-00.t
>              26/01/2011 11:22          xt
>
>              AM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi,
>
> We've tried incorporating most of the comments that we received on th=
e
> list. Please ping me if you think we have missed some.
>
> Would be great if the WG can go through this and provide
> feedback on the
> same.
>
> The draft is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over
> mpls-00.txt
>
> Cheers, Manav
>
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org
> > [mailto:tictoc-bounces@ietf.org] On Behalf Of
> Internet-Drafts@ietf.org
> > Sent: Wednesday, January 26, 2011 9.30 PM
> > To: i-d-announce@ietf.org
> > Cc: tictoc@ietf.org
> > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > MPLS Networks
> >            Author(s)       : S. Davari, et al.
> >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> >            Pages           : 35
> >            Date            : 2011-01-26
> >
> > This document defines the method for transporting PTP
> messages (PDUs)
> > over an MPLS network to enable a proper handling of these packets
> > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> >
>
> Cheers, Manav
>
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>
>
> ----------
> This email is confidential and may contain information that
> is privileged and
> exempt from disclosure by law.  If you have received it in
> error, please contact
> the sender immediately by return email and then delete it
> from your system; you
> should not copy it or disclose its contents to anyone.
> Emails are not secure
> and cannot be guaranteed to be error free as they can be
> intercepted, amended,
> lost or destroyed, or contain viruses.  Anyone who
> communicates with us by email
> is taken to accept these risks.
>
_______________________________________________
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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc
=



From mike.gilson@bt.com  Fri Feb 11 09:53:33 2011
Return-Path: <mike.gilson@bt.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 805263A69E7; Fri, 11 Feb 2011 09:53:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.045
X-Spam-Level: 
X-Spam-Status: No, score=-2.045 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 555qh99RPMLC; Fri, 11 Feb 2011 09:53:30 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtp63.intersmtp.COM [62.239.224.236]) by core3.amsl.com (Postfix) with ESMTP id 1D4B33A69CF; Fri, 11 Feb 2011 09:53:30 -0800 (PST)
Received: from EVMHT67-UKRD.domain1.systemhost.net (10.36.3.104) by RDW083A007ED63.smtp-e3.hygiene.service (10.187.98.12) with Microsoft SMTP Server (TLS) id 8.3.106.1; Fri, 11 Feb 2011 17:53:44 +0000
Received: from EVMHT33-UKDY.domain1.systemhost.net (193.113.31.251) by EVMHT67-UKRD.domain1.systemhost.net (10.36.3.104) with Microsoft SMTP Server (TLS) id 8.3.106.1; Fri, 11 Feb 2011 17:53:44 +0000
Received: from EMV35-UKDY.domain1.systemhost.net ([169.254.1.94]) by EVMHT33-UKDY.domain1.systemhost.net ([2002:c171:1ffb::c171:1ffb]) with mapi; Fri, 11 Feb 2011 17:53:44 +0000
From: <mike.gilson@bt.com>
To: <stefano.ruffini@ericsson.com>, <Peter.Meyer@Zarlink.Com>, <peter.roberts@alcatel-lucent.com>
Date: Fri, 11 Feb 2011 17:53:43 +0000
Thread-Topic: [TICTOC] 1588overmpls-00 / MPLS profile & BC
Thread-Index: AcvIasz/fGOkmQBQT+GvX7xpCJOr9AA1XK5AADTxErA=
Message-ID: <6D53E9696A81554B9B2E14FF508BA7C80979D6426B@EMV35-UKDY.domain1.systemhost.net>
References: <CA2959F3E75BA645A43E81C3B071F6320ACFEA9560@USNAVSXCHMBSC2.ndc.alcatel-lucent.com> <OF23A1DD85.5C87F3B6-ON85257832.0052BB99-85257832.0052DDFF@Zarlink.Com> <28C9B1CD4D27844E9CD8F02BFEB70564075118B097@ESESSCMS0360.eemea.ericsson.se>
In-Reply-To: <28C9B1CD4D27844E9CD8F02BFEB70564075118B097@ESESSCMS0360.eemea.ericsson.se>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: multipart/alternative; boundary="_000_6D53E9696A81554B9B2E14FF508BA7C80979D6426BEMV35UKDYdoma_"
MIME-Version: 1.0
Cc: tictoc@ietf.org, tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Feb 2011 17:53:33 -0000

--_000_6D53E9696A81554B9B2E14FF508BA7C80979D6426BEMV35UKDYdoma_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I would think the interface would be Ethernet. How many interfaces are ther=
e that are pure MPLS or another.

Maybe someone can expand on this.

Regards,

Mike

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Stefano Ruffini
Sent: 10 February 2011 16:35
To: Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC


Peter M., Peter R.

I wonder if there is really a need (use case) for section 5.3 (pure MPLS ma=
pping) ?

 Best Regards

Stefano

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Peter.Meyer@Zarlink.Com
Sent: mercoled=EC 9 febbraio 2011 16.06
To: Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC


Thanks.

Yes, a poor choice of words on the Annexes being "profiles".  We would stil=
l need to fill out the Annex info though re: port addresses and the like to=
 ensure inter-operability.

I am fine to be neutral on performance aspects -- I would recommend to indi=
cate they are not within scope of the document.

ZARLINK Semiconductor
Peter Meyer
Timing & Synchronization
Communication Products Group
Office: +1-613-270-7203  |  Fax: +1-613-592-1010
peter.meyer@zarlink.com<mailto:employee.name@zarlink.com>  | www.zarlink.co=
m<http://www.zarlink.com/>



"Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>
Sent by: <tictoc-bounces@ietf.org>

09/02/2011 08:52 AM

To
"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "Peter.Meyer@Zar=
link.Com" <Peter.Meyer@zarlink.com>
cc
"tictoc@ietf.org" <tictoc@ietf.org>
Subject
Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC







Peter,
With respect to your comments on the profile, the Annexes are not profiles.=
  They are the portions of the standard that define the rules for running P=
TP over specific lower layer protocols.  These can then be included or excl=
uded from specific profiles that are defined.  This draft is defining these=
 rules for the MPLS environment.
The draft covers all the clock types but as you point out this is not all t=
hat clear.  This can be added.
In addition, I don't believe the ITU-T has concluded anything about perform=
ance of BC vs TC.  They have just started studying the issue.  But this dra=
ft is not making any claims about performance and as stated earlier should =
be applicable for any of the clock types.  We can review it to remove any c=
ontentious wording in respect to performance.
Peter R.



-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: February 9, 2011 8:20 AM
To: Peter.Meyer@Zarlink.Com
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Hi Peter,

Very valid comments.

This draft covers all clock types - TC, BC and OC. The reason it seems we'v=
e been concentrating on TC is because that's the clock type that requires s=
pecial MPLS processing.

For BC's and OC's there is no special processing involved. One just needs a=
n MPLS LSP that terminates on a BC and OC and things will just work. Howeve=
r, I get the drift of what youre saying and we can update the draft to expl=
icitly state this.

I will let someone more knowledgeable respond to your question on whether a=
 separate profile for MPLS is required or not. To my untrained eye it looks=
 that we might.

Cheers, Manav

> -----Original Message-----
> From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com]
> Sent: Wednesday, February 09, 2011 2.00 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
> Hi Manav,
>
>
> A high level point is that for the pure MPLS mapping (section 5.3) , I
> wonder if what is really needed is a PTP profile for MPLS --
> similar to
> Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For
> example the IP &
> Ethernet profiles include other information such as the port
> addressing for
> the unicast master table and acceptable master table.  Without a full
> profile, although the intermediate notes may operate in TC,
> the server,
> client and boundary nodes may not operate successfully.
>
> Its not clear if this draft is intended to cover all clock
> types (OC, BC &
> TC) or only TC.  There are many sections that talk only about
> TC without
> considering OC and BC behaviour or impact.  Is BC intended to
> be covered as
> a Client-side OC + Server-side OC model, or is BC excluded from
> consideration in this draft?  Perhaps this draft should be either
> cleaned-up to consider all clock types or should be
> restricted to only TC
> clock type with OC & BC out of scope.
>
>
> Some specific comments
>
> + The abstract could be clarified to indicate there are three
> mappings, not
> two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
> third mapping may be under discussion, so perhaps this is premature.
>
> + A few places in the text the phrase "proper handling of
> these packets" or
> "properly handle PTP messages" or "perform proper
> processing"  is used to
> mean transparent clock.  I would propose to remove such
> language as from
> the ITU-T studies of timing performances of PTP one could argue the
> "proper" way is to implement a boundary clock.  Where the
> intention is to
> aid the designer of a TC that is fine to describe the implementation
> recommendation, but not to suggest this is the way to acheive the best
> performance or even the desired way to deploy PTP over MPLS.
>
> + I would like to see a statement added in the document that the
> performance aspects (e.g. the phase or frequency alignment)
> are outside the
> scope of the document.
>
> + Section 6, 7, 8, 10 and 13 seems to focus only on the TC
> case between
> OC's and does not consider BC situation.
>
> + Section 12 text on checksums could be improved to indicate this only
> applies to TC and not to OC & BC.
>
> + Section 16 seems to address only TC clocks and not OC or BC clocks.
>
> + Section 16.3 implies that the only possible way to handle PTP is TC,
> excluding BC --- "don't have the capability to process 1588
> packets (e.g.
> TC processing)" and "   Non-1588-aware LSRs ignore the RSVP
> 1588_PTP_LSP
> object and just switch the MPLS packets carrying 1588 messages as data
> packets and don't perform any TC processing."
>
>
> Regards,
>
>
> ZARLINK Semiconductor
> Peter Meyer
> Timing & Synchronization
> Communication Products Group
> Office: +1-613-270-7203  |  Fax: +1-613-592-1010
> peter.meyer@zarlink.com  | www.zarlink.com
>
>
>
>
>
>              "Bhatia, Manav
>
>              (Manav)"
>
>              <manav.bhatia@alc
>           To
>              atel-lucent.com>          "tictoc@ietf.org"
> <tictoc@ietf.org>
>              Sent by:
>           cc
>              <tictoc-bounces@i
>
>              etf.org>
>      Subject
>                                        [TICTOC]
>
>
> draft-ietf-tictoc-1588overmpls-00.t
>              26/01/2011 11:22          xt
>
>              AM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi,
>
> We've tried incorporating most of the comments that we received on the
> list. Please ping me if you think we have missed some.
>
> Would be great if the WG can go through this and provide
> feedback on the
> same.
>
> The draft is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over
> mpls-00.txt
>
> Cheers, Manav
>
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org
> > [mailto:tictoc-bounces@ietf.org] On Behalf Of
> Internet-Drafts@ietf.org
> > Sent: Wednesday, January 26, 2011 9.30 PM
> > To: i-d-announce@ietf.org
> > Cc: tictoc@ietf.org
> > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > MPLS Networks
> >            Author(s)       : S. Davari, et al.
> >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> >            Pages           : 35
> >            Date            : 2011-01-26
> >
> > This document defines the method for transporting PTP
> messages (PDUs)
> > over an MPLS network to enable a proper handling of these packets
> > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> >
>
> Cheers, Manav
>
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>
>
> ----------
> This email is confidential and may contain information that
> is privileged and
> exempt from disclosure by law.  If you have received it in
> error, please contact
> the sender immediately by return email and then delete it
> from your system; you
> should not copy it or disclose its contents to anyone.
> Emails are not secure
> and cannot be guaranteed to be error free as they can be
> intercepted, amended,
> lost or destroyed, or contain viruses.  Anyone who
> communicates with us by email
> is taken to accept these risks.
>
_______________________________________________
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



--_000_6D53E9696A81554B9B2E14FF508BA7C80979D6426BEMV35UKDYdoma_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.6000.17093" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D565224917-11022011>I would think the interface would be Ethernet.&n=
bsp;How=20
many interfaces are there that are pure MPLS or another.</SPAN></FONT></DIV=
>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D565224917-11022011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D565224917-11022011>Maybe someone can expand on this.</SPAN></FONT><=
/DIV>
<DIV><SPAN lang=3Den-gb><FONT face=3DArial size=3D2></FONT></SPAN>&nbsp;</D=
IV>
<DIV><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Regards,</FONT></SPAN> =
</DIV>
<P><SPAN lang=3Den-gb><I><FONT face=3D"Comic Sans MS" color=3D#0000ff=20
size=3D4>Mike</FONT></I></SPAN> </P>
<DIV>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> tictoc-bounces@ietf.org=20
[mailto:tictoc-bounces@ietf.org] <B>On Behalf Of </B>Stefano=20
Ruffini<BR><B>Sent:</B> 10 February 2011 16:35<BR><B>To:</B>=20
Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)<BR><B>Cc:</B> tictoc@ietf.o=
rg;=20
tictoc-bounces@ietf.org<BR><B>Subject:</B> Re: [TICTOC] 1588overmpls-00 / M=
PLS=20
profile &amp; BC<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN lang=3DIT>
<P><SPAN class=3D449293316-10022011>Peter M., Peter R.</SPAN></P>
<P><SPAN class=3D449293316-10022011></SPAN><SPAN class=3D449293316-10022011=
>I wonder=20
if there is really a need (</SPAN>use case<SPAN=20
class=3D449293316-10022011>)</SPAN> for section 5.3 (pure MPLS mapping)<SPA=
N=20
class=3D449293316-10022011> ?</SPAN></P>
<P><SPAN class=3D449293316-10022011>&nbsp;</SPAN>Best Regards</P>
<P>Stefano </P></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> tictoc-bounces@ietf.org=20
[mailto:tictoc-bounces@ietf.org] <B>On Behalf Of=20
</B>Peter.Meyer@Zarlink.Com<BR><B>Sent:</B> mercoled=EC 9 febbraio 2011=20
16.06<BR><B>To:</B> Roberts, Peter (Peter)<BR><B>Cc:</B> tictoc@ietf.org;=20
tictoc-bounces@ietf.org<BR><B>Subject:</B> Re: [TICTOC] 1588overmpls-00 / M=
PLS=20
profile &amp; BC<BR></FONT><BR></DIV>
<DIV></DIV><FONT face=3DArial color=3D#0000ff></FONT><BR><FONT face=3Dsans-=
serif=20
size=3D2>Thanks.</FONT> <BR><BR><FONT face=3Dsans-serif size=3D2>Yes, a poo=
r choice of=20
words on the Annexes being "profiles". &nbsp;We would still need to fill ou=
t the=20
Annex info though re: port addresses and the like to ensure=20
inter-operability.</FONT> <BR><BR><FONT face=3Dsans-serif size=3D2>I am fin=
e to be=20
neutral on performance aspects -- I would recommend to indicate they are no=
t=20
within scope of the document.</FONT><FONT face=3D"Arial Black" size=3D2> </=
FONT>
<P><FONT face=3D"Arial Black" size=3D2><B>ZARLINK</B></FONT><FONT face=3D"A=
rial Black"=20
size=3D3><B> </B></FONT><FONT face=3D"Trebuchet MS" size=3D1>Semiconductor<=
B><BR>Peter=20
Meyer</B></FONT><FONT face=3D"Trebuchet MS" color=3D#808080 size=3D1><B><I>=
<BR>Timing=20
&amp; Synchronization<BR>Communication Products Group</I></B></FONT><FONT=20
face=3D"Trebuchet MS" size=3D1><I><BR>Office: +1-613-270-7203</I></FONT><FO=
NT=20
face=3D"Trebuchet MS" size=3D1><B>&nbsp; |&nbsp; </B></FONT><FONT=20
face=3D"Trebuchet MS" size=3D1><I>Fax: +1-613-592-1010</I></FONT><FONT=20
face=3D"Trebuchet MS" color=3Dblue size=3D1><U><BR></U></FONT><A=20
href=3D"mailto:employee.name@zarlink.com"><FONT face=3D"Trebuchet MS" color=
=3Dblue=20
size=3D1><U>peter.meyer@zarlink.com</U></FONT></A><FONT face=3D"Trebuchet M=
S"=20
size=3D1> </FONT><FONT face=3D"Trebuchet MS" size=3D1><B>&nbsp;| </B></FONT=
><A=20
href=3D"http://www.zarlink.com/"><FONT face=3D"Trebuchet MS" color=3Dblue=20
size=3D1><U>www.zarlink.com</U></FONT></A><FONT face=3D"Trebuchet MS"=20
size=3D1><BR></FONT>
<P><BR><BR><BR>
<TABLE width=3D"100%">
  <TBODY>
  <TR vAlign=3Dtop>
    <TD width=3D"40%"><FONT face=3Dsans-serif size=3D1><B>"Roberts, Peter (=
Peter)"=20
      &lt;peter.roberts@alcatel-lucent.com&gt;</B> </FONT><BR><FONT=20
      face=3Dsans-serif size=3D1>Sent by: &lt;tictoc-bounces@ietf.org&gt;</=
FONT>=20
      <P><FONT face=3Dsans-serif size=3D1>09/02/2011 08:52 AM</FONT> </P>
    <TD width=3D"59%">
      <TABLE width=3D"100%">
        <TBODY>
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT face=3Dsans-serif size=3D1>To</FONT></=
DIV>
          <TD><FONT face=3Dsans-serif size=3D1>"Bhatia, Manav (Manav)"=20
            &lt;manav.bhatia@alcatel-lucent.com&gt;, "Peter.Meyer@Zarlink.C=
om"=20
            &lt;Peter.Meyer@zarlink.com&gt;</FONT>=20
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT face=3Dsans-serif size=3D1>cc</FONT></=
DIV>
          <TD><FONT face=3Dsans-serif size=3D1>"tictoc@ietf.org"=20
            &lt;tictoc@ietf.org&gt;</FONT>=20
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT face=3Dsans-serif size=3D1>Subject</FO=
NT></DIV>
          <TD><FONT face=3Dsans-serif size=3D1>Re: [TICTOC] 1588overmpls-00=
 / MPLS=20
            profile &amp; BC</FONT></TD></TR></TBODY></TABLE><BR>
      <TABLE>
        <TBODY>
        <TR vAlign=3Dtop>
          <TD>
          <TD></TD></TR></TBODY></TABLE><BR></TD></TR></TBODY></TABLE><BR><=
BR><BR><TT><FONT=20
size=3D2>Peter,<BR>With respect to your comments on the profile, the Annexe=
s are=20
not profiles. &nbsp;They are the portions of the standard that define the r=
ules=20
for running PTP over specific lower layer protocols. &nbsp;These can then b=
e=20
included or excluded from specific profiles that are defined. &nbsp;This dr=
aft=20
is defining these rules for the MPLS environment. &nbsp;<BR>The draft cover=
s all=20
the clock types but as you point out this is not all that clear. &nbsp;This=
 can=20
be added.<BR>In addition, I don't believe the ITU-T has concluded anything =
about=20
performance of BC vs TC. &nbsp;They have just started studying the issue.=20
&nbsp;But this draft is not making any claims about performance and as stat=
ed=20
earlier should be applicable for any of the clock types. &nbsp;We can revie=
w it=20
to remove any contentious wording in respect to performance.<BR>Peter=20
R.<BR><BR>&nbsp; <BR><BR>-----Original Message-----<BR>From:=20
tictoc-bounces@ietf.org [</FONT></TT><A=20
href=3D"mailto:tictoc-bounces@ietf.org"><TT><FONT=20
size=3D2>mailto:tictoc-bounces@ietf.org</FONT></TT></A><TT><FONT size=3D2>]=
 On=20
Behalf Of Bhatia, Manav (Manav)<BR>Sent: February 9, 2011 8:20 AM<BR>To:=20
Peter.Meyer@Zarlink.Com<BR>Cc: tictoc@ietf.org<BR>Subject: Re: [TICTOC]=20
1588overmpls-00 / MPLS profile &amp; BC<BR><BR>Hi Peter,<BR><BR>Very valid=
=20
comments. <BR><BR>This draft covers all clock types - TC, BC and OC. The re=
ason=20
it seems we've been concentrating on TC is because that's the clock type th=
at=20
requires special MPLS processing. <BR><BR>For BC's and OC's there is no spe=
cial=20
processing involved. One just needs an MPLS LSP that terminates on a BC and=
 OC=20
and things will just work. However, I get the drift of what youre saying an=
d we=20
can update the draft to explicitly state this.<BR><BR>I will let someone mo=
re=20
knowledgeable respond to your question on whether a separate profile for MP=
LS is=20
required or not. To my untrained eye it looks that we might.<BR><BR>Cheers,=
=20
Manav <BR><BR>&gt; -----Original Message-----<BR>&gt; From:=20
Peter.Meyer@Zarlink.Com [</FONT></TT><A=20
href=3D"mailto:Peter.Meyer@Zarlink.Com"><TT><FONT=20
size=3D2>mailto:Peter.Meyer@Zarlink.Com</FONT></TT></A><TT><FONT size=3D2>]=
 <BR>&gt;=20
Sent: Wednesday, February 09, 2011 2.00 PM<BR>&gt; To: Bhatia, Manav=20
(Manav)<BR>&gt; Cc: tictoc@ietf.org<BR>&gt; Subject: Re: [TICTOC]=20
1588overmpls-00 / MPLS profile &amp; BC<BR>&gt; <BR>&gt; <BR>&gt; Hi=20
Manav,<BR>&gt; <BR>&gt; <BR>&gt; A high level point is that for the pure MP=
LS=20
mapping (section 5.3) , I<BR>&gt; wonder if what is really needed is a PTP=
=20
profile for MPLS -- <BR>&gt; similar to<BR>&gt; Annex D/E/F for=20
IPv4/IPv6/Ethernet, respectively. &nbsp;For <BR>&gt; example the IP=20
&amp;<BR>&gt; Ethernet profiles include other information such as the port=
=20
<BR>&gt; addressing for<BR>&gt; the unicast master table and acceptable mas=
ter=20
table. &nbsp;Without a full<BR>&gt; profile, although the intermediate note=
s may=20
operate in TC, <BR>&gt; the server,<BR>&gt; client and boundary nodes may n=
ot=20
operate successfully.<BR>&gt; <BR>&gt; Its not clear if this draft is inten=
ded=20
to cover all clock <BR>&gt; types (OC, BC &amp;<BR>&gt; TC) or only TC.=20
&nbsp;There are many sections that talk only about <BR>&gt; TC without<BR>&=
gt;=20
considering OC and BC behaviour or impact. &nbsp;Is BC intended to <BR>&gt;=
 be=20
covered as<BR>&gt; a Client-side OC + Server-side OC model, or is BC exclud=
ed=20
from<BR>&gt; consideration in this draft? &nbsp;Perhaps this draft should b=
e=20
either<BR>&gt; cleaned-up to consider all clock types or should be <BR>&gt;=
=20
restricted to only TC<BR>&gt; clock type with OC &amp; BC out of scope.<BR>=
&gt;=20
<BR>&gt; <BR>&gt; Some specific comments<BR>&gt; <BR>&gt; + The abstract co=
uld=20
be clarified to indicate there are three <BR>&gt; mappings, not<BR>&gt; two=
=20
(pure MPLS, UDP/IP over MPLS and Ethernet over MPLS). &nbsp;I think the<BR>=
&gt;=20
third mapping may be under discussion, so perhaps this is premature.<BR>&gt=
;=20
<BR>&gt; + A few places in the text the phrase "proper handling of <BR>&gt;=
=20
these packets" or<BR>&gt; "properly handle PTP messages" or "perform proper=
=20
&nbsp;<BR>&gt; processing" &nbsp;is used to<BR>&gt; mean transparent clock.=
=20
&nbsp;I would propose to remove such <BR>&gt; language as from<BR>&gt; the =
ITU-T=20
studies of timing performances of PTP one could argue the<BR>&gt; "proper" =
way=20
is to implement a boundary clock. &nbsp;Where the <BR>&gt; intention is=20
to<BR>&gt; aid the designer of a TC that is fine to describe the=20
implementation<BR>&gt; recommendation, but not to suggest this is the way t=
o=20
acheive the best<BR>&gt; performance or even the desired way to deploy PTP =
over=20
MPLS.<BR>&gt; <BR>&gt; + I would like to see a statement added in the docum=
ent=20
that the<BR>&gt; performance aspects (e.g. the phase or frequency alignment=
)=20
<BR>&gt; are outside the<BR>&gt; scope of the document.<BR>&gt; <BR>&gt; +=
=20
Section 6, 7, 8, 10 and 13 seems to focus only on the TC <BR>&gt; case=20
between<BR>&gt; OC's and does not consider BC situation.<BR>&gt; <BR>&gt; +=
=20
Section 12 text on checksums could be improved to indicate this only<BR>&gt=
;=20
applies to TC and not to OC &amp; BC.<BR>&gt; <BR>&gt; + Section 16 seems t=
o=20
address only TC clocks and not OC or BC clocks.<BR>&gt; <BR>&gt; + Section =
16.3=20
implies that the only possible way to handle PTP is TC,<BR>&gt; excluding B=
C ---=20
"don't have the capability to process 1588 <BR>&gt; packets (e.g.<BR>&gt; T=
C=20
processing)" and " &nbsp; Non-1588-aware LSRs ignore the RSVP <BR>&gt;=20
1588_PTP_LSP<BR>&gt; object and just switch the MPLS packets carrying 1588=
=20
messages as data<BR>&gt; packets and don't perform any TC processing."<BR>&=
gt;=20
<BR>&gt; <BR>&gt; Regards,<BR>&gt; <BR>&gt; <BR>&gt; ZARLINK=20
Semiconductor<BR>&gt; Peter Meyer<BR>&gt; Timing &amp; Synchronization<BR>&=
gt;=20
Communication Products Group<BR>&gt; Office: +1-613-270-7203&nbsp; |&nbsp; =
Fax:=20
+1-613-592-1010<BR>&gt; peter.meyer@zarlink.com &nbsp;| </FONT></TT><A=20
href=3D"www.zarlink.com"><TT><FONT size=3D2>www.zarlink.com</FONT></TT></A>=
<TT><FONT=20
size=3D2><BR>&gt; <BR>&gt; <BR>&gt; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"Bhatia, Man=
av=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;(Manav)" &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &n=
bsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;manav.bhatia@alc &nbsp; &nbsp; &nbsp;=
=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; To <BR>&gt; &nbsp;=
=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;atel-lucent.com&gt; &nbsp; &nbsp;=
=20
&nbsp; &nbsp; &nbsp;"tictoc@ietf.org" <BR>&gt; &lt;tictoc@ietf.org&gt; <BR>=
&gt;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Sent by: &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; cc <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;&lt;tictoc-bounces@i &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp;etf.org&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp;Subject <BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[TICTOC] &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;<BR>&gt; draft-ietf-tictoc-1588overmpls-00.t <BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp;26/01/2011 11:22 &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;xt=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&=
gt;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp;AM &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &n=
bsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nb=
sp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp;<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; &nbsp; &n=
bsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <BR>&gt; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; &nbsp; &nbsp; &nbsp;<BR>&gt; <BR>&gt; <BR>&gt; <BR>&gt; <BR>&gt;=20
Hi,<BR>&gt; <BR>&gt; We've tried incorporating most of the comments that we=
=20
received on the<BR>&gt; list. Please ping me if you think we have missed=20
some.<BR>&gt; <BR>&gt; Would be great if the WG can go through this and pro=
vide=20
<BR>&gt; feedback on the<BR>&gt; same.<BR>&gt; <BR>&gt; The draft is availa=
ble=20
here:<BR>&gt; </FONT></TT><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over"><TT=
><FONT=20
size=3D2>http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over</FO=
NT></TT></A><TT><FONT=20
size=3D2><BR>&gt; mpls-00.txt<BR>&gt; <BR>&gt; Cheers, Manav<BR>&gt; <BR>&g=
t; &gt;=20
-----Original Message-----<BR>&gt; &gt; From: tictoc-bounces@ietf.org<BR>&g=
t;=20
&gt; [</FONT></TT><A href=3D"mailto:tictoc-bounces@ietf.org"><TT><FONT=20
size=3D2>mailto:tictoc-bounces@ietf.org</FONT></TT></A><TT><FONT size=3D2>]=
 On=20
Behalf Of <BR>&gt; Internet-Drafts@ietf.org<BR>&gt; &gt; Sent: Wednesday,=20
January 26, 2011 9.30 PM<BR>&gt; &gt; To: i-d-announce@ietf.org<BR>&gt; &gt=
; Cc:=20
tictoc@ietf.org<BR>&gt; &gt; Subject: [TICTOC] I-D=20
Action:draft-ietf-tictoc-1588overmpls-00.txt<BR>&gt; &gt;<BR>&gt; &gt; A Ne=
w=20
Internet-Draft is available from the on-line<BR>&gt; &gt; Internet-Drafts=20
directories.<BR>&gt; &gt; This draft is a work item of the Timing over IP=20
Connection<BR>&gt; &gt; and Transfer of Clock Working Group of the IETF.<BR=
>&gt;=20
&gt;<BR>&gt; &gt;<BR>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Tit=
le=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : Transporting PTP messages (1588)=20
over<BR>&gt; &gt; MPLS Networks<BR>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;=20
&nbsp;Author(s) &nbsp; &nbsp; &nbsp; : S. Davari, et al.<BR>&gt; &gt; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Filename &nbsp; &nbsp; &nbsp; &nbsp;:=20
draft-ietf-tictoc-1588overmpls-00.txt<BR>&gt; &gt; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
&nbsp; &nbsp;Pages &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 35<BR>&gt; &gt; &nb=
sp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Date &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;: 2011-01-26<BR>&gt; &gt;<BR>&gt; &gt; This document defines the meth=
od=20
for transporting PTP <BR>&gt; messages (PDUs)<BR>&gt; &gt; over an MPLS net=
work=20
to enable a proper handling of these packets<BR>&gt; &gt; (e.g. implementat=
ion=20
of Transparent Clocks (TC)) in LSRs.<BR>&gt; &gt;<BR>&gt; <BR>&gt; Cheers,=
=20
Manav<BR>&gt; <BR>&gt; --<BR>&gt; Manav Bhatia,<BR>&gt; IP Division,=20
Alcatel-Lucent,<BR>&gt; Bangalore - India<BR>&gt; <BR>&gt; <BR>&gt;=20
_______________________________________________<BR>&gt; TICTOC mailing=20
list<BR>&gt; TICTOC@ietf.org<BR>&gt; </FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/tictoc</FONT></TT></A><TT><F=
ONT=20
size=3D2><BR>&gt; <BR>&gt; <BR>&gt; <BR>&gt; ----------<BR>&gt; This email =
is=20
confidential and may contain information that <BR>&gt; is privileged and<BR=
>&gt;=20
exempt from disclosure by law. &nbsp;If you have received it in <BR>&gt; er=
ror,=20
please contact<BR>&gt; the sender immediately by return email and then dele=
te it=20
<BR>&gt; from your system; you<BR>&gt; should not copy it or disclose its=20
contents to anyone. &nbsp;<BR>&gt; Emails are not secure<BR>&gt; and cannot=
 be=20
guaranteed to be error free as they can be <BR>&gt; intercepted,=20
amended,<BR>&gt; lost or destroyed, or contain viruses. &nbsp;Anyone who=20
<BR>&gt; communicates with us by email<BR>&gt; is taken to accept these=20
risks.<BR>&gt; <BR>_______________________________________________<BR>TICTO=
C=20
mailing list<BR>TICTOC@ietf.org<BR></FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/tictoc</FONT></TT></A><TT><F=
ONT=20
size=3D2><BR>_______________________________________________<BR>TICTOC mail=
ing=20
list<BR>TICTOC@ietf.org<BR></FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/tictoc</FONT></TT></A><TT><F=
ONT=20
size=3D2><BR><BR></FONT></TT><BR></P></BODY></HTML>

--_000_6D53E9696A81554B9B2E14FF508BA7C80979D6426BEMV35UKDYdoma_--

From davari@broadcom.com  Fri Feb 11 10:10:59 2011
Return-Path: <davari@broadcom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 078483A696E; Fri, 11 Feb 2011 10:10:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66c45LqFfh5G; Fri, 11 Feb 2011 10:10:55 -0800 (PST)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by core3.amsl.com (Postfix) with ESMTP id 5014D3A6860; Fri, 11 Feb 2011 10:10:55 -0800 (PST)
Received: from [10.16.192.232] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Fri, 11 Feb 2011 10:12:58 -0800
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Fri, 11 Feb 2011 10:11:03 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "mike.gilson@bt.com" <mike.gilson@bt.com>, "stefano.ruffini@ericsson.com" <stefano.ruffini@ericsson.com>, "Peter.Meyer@Zarlink.Com" <Peter.Meyer@Zarlink.Com>, "peter.roberts@alcatel-lucent.com" <peter.roberts@alcatel-lucent.com>
Date: Fri, 11 Feb 2011 10:11:01 -0800
Thread-Topic: [TICTOC] 1588overmpls-00 / MPLS profile & BC
Thread-Index: AcvIasz/fGOkmQBQT+GvX7xpCJOr9AA1XK5AADTxErAAAKlwMA==
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6941B906F42@SJEXCHCCR02.corp.ad.broadcom.com>
References: <CA2959F3E75BA645A43E81C3B071F6320ACFEA9560@USNAVSXCHMBSC2.ndc.alcatel-lucent.com> <OF23A1DD85.5C87F3B6-ON85257832.0052BB99-85257832.0052DDFF@Zarlink.Com> <28C9B1CD4D27844E9CD8F02BFEB70564075118B097@ESESSCMS0360.eemea.ericsson.se> <6D53E9696A81554B9B2E14FF508BA7C80979D6426B@EMV35-UKDY.domain1.systemhost.net>
In-Reply-To: <6D53E9696A81554B9B2E14FF508BA7C80979D6426B@EMV35-UKDY.domain1.systemhost.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 614BA3A03DG6535424-01-01
Content-Type: multipart/alternative; boundary=_000_2C2F1EBA8050E74EA81502D5740B4BD6941B906F42SJEXCHCCR02co_
Cc: "tictoc@ietf.org" <tictoc@ietf.org>, "tictoc-bounces@ietf.org" <tictoc-bounces@ietf.org>
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Feb 2011 18:10:59 -0000

--_000_2C2F1EBA8050E74EA81502D5740B4BD6941B906F42SJEXCHCCR02co_
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

RAW mapping to MPLS has huge HW impact. No HW can support such a format tod=
ay, and to be honest not justified when we already have Ethernet and IP enc=
apsulations. We need to have a very good reason to add yet a 3rd option.

Thx
Shahram

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 mike.gilson@bt.com
Sent: Friday, February 11, 2011 9:54 AM
To: stefano.ruffini@ericsson.com; Peter.Meyer@Zarlink.Com; peter.roberts@al=
catel-lucent.com
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

I would think the interface would be Ethernet. How many interfaces are ther=
e that are pure MPLS or another.

Maybe someone can expand on this.

Regards,

Mike

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Stefano Ruffini
Sent: 10 February 2011 16:35
To: Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Peter M., Peter R.

I wonder if there is really a need (use case) for section 5.3 (pure MPLS ma=
pping) ?

 Best Regards

Stefano

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Peter.Meyer@Zarlink.Com
Sent: mercoled=EC 9 febbraio 2011 16.06
To: Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Thanks.

Yes, a poor choice of words on the Annexes being "profiles".  We would stil=
l need to fill out the Annex info though re: port addresses and the like to=
 ensure inter-operability.

I am fine to be neutral on performance aspects -- I would recommend to indi=
cate they are not within scope of the document.

ZARLINK Semiconductor
Peter Meyer
Timing & Synchronization
Communication Products Group
Office: +1-613-270-7203  |  Fax: +1-613-592-1010
peter.meyer@zarlink.com<mailto:employee.name@zarlink.com>  | www.zarlink.co=
m<http://www.zarlink.com/>


"Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>
Sent by: <tictoc-bounces@ietf.org>

09/02/2011 08:52 AM

To

"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "Peter.Meyer@Zar=
link.Com" <Peter.Meyer@zarlink.com>

cc

"tictoc@ietf.org" <tictoc@ietf.org>

Subject

Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC







Peter,
With respect to your comments on the profile, the Annexes are not profiles.=
  They are the portions of the standard that define the rules for running P=
TP over specific lower layer protocols.  These can then be included or excl=
uded from specific profiles that are defined.  This draft is defining these=
 rules for the MPLS environment.
The draft covers all the clock types but as you point out this is not all t=
hat clear.  This can be added.
In addition, I don't believe the ITU-T has concluded anything about perform=
ance of BC vs TC.  They have just started studying the issue.  But this dra=
ft is not making any claims about performance and as stated earlier should =
be applicable for any of the clock types.  We can review it to remove any c=
ontentious wording in respect to performance.
Peter R.



-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: February 9, 2011 8:20 AM
To: Peter.Meyer@Zarlink.Com
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Hi Peter,

Very valid comments.

This draft covers all clock types - TC, BC and OC. The reason it seems we'v=
e been concentrating on TC is because that's the clock type that requires s=
pecial MPLS processing.

For BC's and OC's there is no special processing involved. One just needs a=
n MPLS LSP that terminates on a BC and OC and things will just work. Howeve=
r, I get the drift of what youre saying and we can update the draft to expl=
icitly state this.

I will let someone more knowledgeable respond to your question on whether a=
 separate profile for MPLS is required or not. To my untrained eye it looks=
 that we might.

Cheers, Manav

> -----Original Message-----
> From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com]
> Sent: Wednesday, February 09, 2011 2.00 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
> Hi Manav,
>
>
> A high level point is that for the pure MPLS mapping (section 5.3) , I
> wonder if what is really needed is a PTP profile for MPLS --
> similar to
> Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For
> example the IP &
> Ethernet profiles include other information such as the port
> addressing for
> the unicast master table and acceptable master table.  Without a full
> profile, although the intermediate notes may operate in TC,
> the server,
> client and boundary nodes may not operate successfully.
>
> Its not clear if this draft is intended to cover all clock
> types (OC, BC &
> TC) or only TC.  There are many sections that talk only about
> TC without
> considering OC and BC behaviour or impact.  Is BC intended to
> be covered as
> a Client-side OC + Server-side OC model, or is BC excluded from
> consideration in this draft?  Perhaps this draft should be either
> cleaned-up to consider all clock types or should be
> restricted to only TC
> clock type with OC & BC out of scope.
>
>
> Some specific comments
>
> + The abstract could be clarified to indicate there are three
> mappings, not
> two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
> third mapping may be under discussion, so perhaps this is premature.
>
> + A few places in the text the phrase "proper handling of
> these packets" or
> "properly handle PTP messages" or "perform proper
> processing"  is used to
> mean transparent clock.  I would propose to remove such
> language as from
> the ITU-T studies of timing performances of PTP one could argue the
> "proper" way is to implement a boundary clock.  Where the
> intention is to
> aid the designer of a TC that is fine to describe the implementation
> recommendation, but not to suggest this is the way to acheive the best
> performance or even the desired way to deploy PTP over MPLS.
>
> + I would like to see a statement added in the document that the
> performance aspects (e.g. the phase or frequency alignment)
> are outside the
> scope of the document.
>
> + Section 6, 7, 8, 10 and 13 seems to focus only on the TC
> case between
> OC's and does not consider BC situation.
>
> + Section 12 text on checksums could be improved to indicate this only
> applies to TC and not to OC & BC.
>
> + Section 16 seems to address only TC clocks and not OC or BC clocks.
>
> + Section 16.3 implies that the only possible way to handle PTP is TC,
> excluding BC --- "don't have the capability to process 1588
> packets (e.g.
> TC processing)" and "   Non-1588-aware LSRs ignore the RSVP
> 1588_PTP_LSP
> object and just switch the MPLS packets carrying 1588 messages as data
> packets and don't perform any TC processing."
>
>
> Regards,
>
>
> ZARLINK Semiconductor
> Peter Meyer
> Timing & Synchronization
> Communication Products Group
> Office: +1-613-270-7203  |  Fax: +1-613-592-1010
> peter.meyer@zarlink.com  | www.zarlink.com
>
>
>
>
>
>              "Bhatia, Manav
>
>              (Manav)"
>
>              <manav.bhatia@alc
>           To
>              atel-lucent.com>          "tictoc@ietf.org"
> <tictoc@ietf.org>
>              Sent by:
>           cc
>              <tictoc-bounces@i
>
>              etf.org>
>      Subject
>                                        [TICTOC]
>
>
> draft-ietf-tictoc-1588overmpls-00.t
>              26/01/2011 11:22          xt
>
>              AM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi,
>
> We've tried incorporating most of the comments that we received on the
> list. Please ping me if you think we have missed some.
>
> Would be great if the WG can go through this and provide
> feedback on the
> same.
>
> The draft is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over
> mpls-00.txt
>
> Cheers, Manav
>
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org
> > [mailto:tictoc-bounces@ietf.org] On Behalf Of
> Internet-Drafts@ietf.org
> > Sent: Wednesday, January 26, 2011 9.30 PM
> > To: i-d-announce@ietf.org
> > Cc: tictoc@ietf.org
> > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > MPLS Networks
> >            Author(s)       : S. Davari, et al.
> >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> >            Pages           : 35
> >            Date            : 2011-01-26
> >
> > This document defines the method for transporting PTP
> messages (PDUs)
> > over an MPLS network to enable a proper handling of these packets
> > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> >
>
> Cheers, Manav
>
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>
>
> ----------
> This email is confidential and may contain information that
> is privileged and
> exempt from disclosure by law.  If you have received it in
> error, please contact
> the sender immediately by return email and then delete it
> from your system; you
> should not copy it or disclose its contents to anyone.
> Emails are not secure
> and cannot be guaranteed to be error free as they can be
> intercepted, amended,
> lost or destroyed, or contain viruses.  Anyone who
> communicates with us by email
> is taken to accept these risks.
>
_______________________________________________
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


--_000_2C2F1EBA8050E74EA81502D5740B4BD6941B906F42SJEXCHCCR02co_
Content-Type: text/html;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>

<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;}
@font-face
	{font-family:"Arial Black";
	panose-1:2 11 10 4 2 1 2 2 2 4;}
@font-face
	{font-family:"Trebuchet MS";
	panose-1:2 11 6 3 2 2 2 2 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>RAW mapping to MPLS has huge HW impact. No HW can support su=
ch a
format today, and to be honest not justified when we already have Ethernet =
and
IP encapsulations. We need to have a very good reason to add yet a 3<sup>rd=
</sup>
option.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Thx<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Shahram<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] <b>On Behalf Of </=
b>mike.gilson@bt.com<br>
<b>Sent:</b> Friday, February 11, 2011 9:54 AM<br>
<b>To:</b> stefano.ruffini@ericsson.com; Peter.Meyer@Zarlink.Com;
peter.roberts@alcatel-lucent.com<br>
<b>Cc:</b> tictoc@ietf.org; tictoc-bounces@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC<o:p></=
o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-family:"Arial","sans-serif";color:=
blue'>I
would think the interface would be Ethernet.&nbsp;How many interfaces are t=
here
that are pure MPLS or another.</span><o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-family:"Arial","sans-serif";color:=
blue'>Maybe
someone can expand on this.</span><o:p></o:p></p>

<div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:10.0pt;font-fami=
ly:"Arial","sans-serif"'>Regards,</span><span
lang=3DEN-GB> </span><o:p></o:p></p>

</div>

<p><i><span lang=3DEN-GB style=3D'font-size:13.5pt;font-family:"Comic Sans =
MS";
color:blue'>Mike</span></i><span lang=3DEN-GB> </span><o:p></o:p></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span style=3D'font-=
size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size=
:10.0pt;
font-family:"Tahoma","sans-serif"'> tictoc-bounces@ietf.org
[mailto:tictoc-bounces@ietf.org] <b>On Behalf Of </b>Stefano Ruffini<br>
<b>Sent:</b> 10 February 2011 16:35<br>
<b>To:</b> Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)<br>
<b>Cc:</b> tictoc@ietf.org; tictoc-bounces@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</span>=
<o:p></o:p></p>

</div>

<p><span lang=3DIT>Peter M., Peter R.<o:p></o:p></span></p>

<p><span lang=3DIT>I wonder if there is really a need (use case) for sectio=
n 5.3
(pure MPLS mapping) ?<o:p></o:p></span></p>

<p><span lang=3DIT>&nbsp;Best Regards<o:p></o:p></span></p>

<p><span lang=3DIT>Stefano <o:p></o:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span style=3D'font-=
size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size=
:10.0pt;
font-family:"Tahoma","sans-serif"'> tictoc-bounces@ietf.org
[mailto:tictoc-bounces@ietf.org] <b>On Behalf Of </b>Peter.Meyer@Zarlink.Co=
m<br>
<b>Sent:</b> mercoled=EC 9 febbraio 2011 16.06<br>
<b>To:</b> Roberts, Peter (Peter)<br>
<b>Cc:</b> tictoc@ietf.org; tictoc-bounces@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</span>=
<o:p></o:p></p>

<p class=3DMsoNormal><br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Thanks.</=
span> <br>
<br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Yes, a po=
or
choice of words on the Annexes being &quot;profiles&quot;. &nbsp;We would s=
till
need to fill out the Annex info though re: port addresses and the like to
ensure inter-operability.</span> <br>
<br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>I am fine=
 to be
neutral on performance aspects -- I would recommend to indicate they are no=
t
within scope of the document.</span><span style=3D'font-size:10.0pt;font-fa=
mily:
"Arial Black","sans-serif"'> </span><o:p></o:p></p>

<p><b><span style=3D'font-size:10.0pt;font-family:"Arial Black","sans-serif=
"'>ZARLINK</span></b><b><span
style=3D'font-family:"Arial Black","sans-serif"'> </span></b><span
style=3D'font-size:7.5pt;font-family:"Trebuchet MS","sans-serif"'>Semicondu=
ctor<b><br>
Peter Meyer<i><span style=3D'color:gray'><br>
Timing &amp; Synchronization<br>
Communication Products Group</span></i></b><i><br>
Office: +1-613-270-7203</i><b>&nbsp; |&nbsp; </b><i>Fax: +1-613-592-1010</i=
><u><span
style=3D'color:blue'><br>
</span></u></span><a href=3D"mailto:employee.name@zarlink.com"><span
style=3D'font-size:7.5pt;font-family:"Trebuchet MS","sans-serif"'>peter.mey=
er@zarlink.com</span></a><span
style=3D'font-size:7.5pt;font-family:"Trebuchet MS","sans-serif"'> <b>&nbsp=
;| </b></span><a
href=3D"http://www.zarlink.com/"><span style=3D'font-size:7.5pt;font-family=
:"Trebuchet MS","sans-serif"'>www.zarlink.com</span></a><o:p></o:p></p>

<p style=3D'margin-bottom:12.0pt'><br>
<br>
<o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%"
 style=3D'width:100.0%'>
 <tr>
  <td width=3D"40%" valign=3Dtop style=3D'width:40.0%;padding:.75pt .75pt .=
75pt .75pt'>
  <p class=3DMsoNormal><b><span style=3D'font-size:7.5pt;font-family:"Arial=
","sans-serif"'>&quot;Roberts,
  Peter (Peter)&quot; &lt;peter.roberts@alcatel-lucent.com&gt;</span></b><s=
pan
  style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'> </span><br>
  <span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>Sent by:
  &lt;tictoc-bounces@ietf.org&gt;</span> <o:p></o:p></p>
  <p><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>09/02=
/2011
  08:52 AM</span> <o:p></o:p></p>
  </td>
  <td width=3D"59%" valign=3Dtop style=3D'width:59.0%;padding:.75pt .75pt .=
75pt .75pt'>
  <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%"
   style=3D'width:100.0%'>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
    style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>To</span><o:=
p></o:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"=
,"sans-serif"'>&quot;Bhatia,
    Manav (Manav)&quot; &lt;manav.bhatia@alcatel-lucent.com&gt;,
    &quot;Peter.Meyer@Zarlink.Com&quot; &lt;Peter.Meyer@zarlink.com&gt;</sp=
an> <o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
    style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>cc</span><o:=
p></o:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"=
,"sans-serif"'>&quot;tictoc@ietf.org&quot;
    &lt;tictoc@ietf.org&gt;</span> <o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
    style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>Subject</spa=
n><o:p></o:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"=
,"sans-serif"'>Re:
    [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</span><o:p></o:p></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><o:p>&nbsp;</o:p></p>
  <table class=3DMsoNormalTable border=3D0 cellpadding=3D0>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td>
   </tr>
  </table>
  </td>
 </tr>
</table>

<p style=3D'margin-bottom:12.0pt'><br>
<br>
<br>
<tt><span style=3D'font-size:10.0pt'>Peter,</span></tt><span style=3D'font-=
size:
10.0pt;font-family:"Courier New"'><br>
<tt>With respect to your comments on the profile, the Annexes are not profi=
les.
&nbsp;They are the portions of the standard that define the rules for runni=
ng
PTP over specific lower layer protocols. &nbsp;These can then be included o=
r
excluded from specific profiles that are defined. &nbsp;This draft is defin=
ing
these rules for the MPLS environment. &nbsp;</tt><br>
<tt>The draft covers all the clock types but as you point out this is not a=
ll
that clear. &nbsp;This can be added.</tt><br>
<tt>In addition, I don't believe the ITU-T has concluded anything about per=
formance
of BC vs TC. &nbsp;They have just started studying the issue. &nbsp;But thi=
s
draft is not making any claims about performance and as stated earlier shou=
ld
be applicable for any of the clock types. &nbsp;We can review it to remove =
any
contentious wording in respect to performance.</tt><br>
<tt>Peter R.</tt><br>
<br>
<tt>&nbsp; </tt><br>
<br>
<tt>-----Original Message-----</tt><br>
<tt>From: tictoc-bounces@ietf.org [</tt></span><a
href=3D"mailto:tictoc-bounces@ietf.org"><tt><span style=3D'font-size:10.0pt=
'>mailto:tictoc-bounces@ietf.org</span></tt></a><tt><span
style=3D'font-size:10.0pt'>] On Behalf Of Bhatia, Manav (Manav)</span></tt>=
<span
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>Sent: February 9, 2011 8:20 AM</tt><br>
<tt>To: Peter.Meyer@Zarlink.Com</tt><br>
<tt>Cc: tictoc@ietf.org</tt><br>
<tt>Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</tt><br>
<br>
<tt>Hi Peter,</tt><br>
<br>
<tt>Very valid comments. </tt><br>
<br>
<tt>This draft covers all clock types - TC, BC and OC. The reason it seems
we've been concentrating on TC is because that's the clock type that requir=
es
special MPLS processing. </tt><br>
<br>
<tt>For BC's and OC's there is no special processing involved. One just nee=
ds
an MPLS LSP that terminates on a BC and OC and things will just work. Howev=
er,
I get the drift of what youre saying and we can update the draft to explici=
tly
state this.</tt><br>
<br>
<tt>I will let someone more knowledgeable respond to your question on wheth=
er a
separate profile for MPLS is required or not. To my untrained eye it looks =
that
we might.</tt><br>
<br>
<tt>Cheers, Manav </tt><br>
<br>
<tt>&gt; -----Original Message-----</tt><br>
<tt>&gt; From: Peter.Meyer@Zarlink.Com [</tt></span><a
href=3D"mailto:Peter.Meyer@Zarlink.Com"><tt><span style=3D'font-size:10.0pt=
'>mailto:Peter.Meyer@Zarlink.Com</span></tt></a><tt><span
style=3D'font-size:10.0pt'>] </span></tt><span style=3D'font-size:10.0pt;
font-family:"Courier New"'><br>
<tt>&gt; Sent: Wednesday, February 09, 2011 2.00 PM</tt><br>
<tt>&gt; To: Bhatia, Manav (Manav)</tt><br>
<tt>&gt; Cc: tictoc@ietf.org</tt><br>
<tt>&gt; Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</tt>=
<br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi Manav,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; A high level point is that for the pure MPLS mapping (section 5.3)=
 , I</tt><br>
<tt>&gt; wonder if what is really needed is a PTP profile for MPLS -- </tt>=
<br>
<tt>&gt; similar to</tt><br>
<tt>&gt; Annex D/E/F for IPv4/IPv6/Ethernet, respectively. &nbsp;For </tt><=
br>
<tt>&gt; example the IP &amp;</tt><br>
<tt>&gt; Ethernet profiles include other information such as the port </tt>=
<br>
<tt>&gt; addressing for</tt><br>
<tt>&gt; the unicast master table and acceptable master table. &nbsp;Withou=
t a
full</tt><br>
<tt>&gt; profile, although the intermediate notes may operate in TC, </tt><=
br>
<tt>&gt; the server,</tt><br>
<tt>&gt; client and boundary nodes may not operate successfully.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Its not clear if this draft is intended to cover all clock </tt><b=
r>
<tt>&gt; types (OC, BC &amp;</tt><br>
<tt>&gt; TC) or only TC. &nbsp;There are many sections that talk only about=
 </tt><br>
<tt>&gt; TC without</tt><br>
<tt>&gt; considering OC and BC behaviour or impact. &nbsp;Is BC intended to=
 </tt><br>
<tt>&gt; be covered as</tt><br>
<tt>&gt; a Client-side OC + Server-side OC model, or is BC excluded from</t=
t><br>
<tt>&gt; consideration in this draft? &nbsp;Perhaps this draft should be ei=
ther</tt><br>
<tt>&gt; cleaned-up to consider all clock types or should be </tt><br>
<tt>&gt; restricted to only TC</tt><br>
<tt>&gt; clock type with OC &amp; BC out of scope.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Some specific comments</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + The abstract could be clarified to indicate there are three </tt=
><br>
<tt>&gt; mappings, not</tt><br>
<tt>&gt; two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS). &nbsp;I
think the</tt><br>
<tt>&gt; third mapping may be under discussion, so perhaps this is prematur=
e.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + A few places in the text the phrase &quot;proper handling of </t=
t><br>
<tt>&gt; these packets&quot; or</tt><br>
<tt>&gt; &quot;properly handle PTP messages&quot; or &quot;perform proper
&nbsp;</tt><br>
<tt>&gt; processing&quot; &nbsp;is used to</tt><br>
<tt>&gt; mean transparent clock. &nbsp;I would propose to remove such </tt>=
<br>
<tt>&gt; language as from</tt><br>
<tt>&gt; the ITU-T studies of timing performances of PTP one could argue th=
e</tt><br>
<tt>&gt; &quot;proper&quot; way is to implement a boundary clock. &nbsp;Whe=
re
the </tt><br>
<tt>&gt; intention is to</tt><br>
<tt>&gt; aid the designer of a TC that is fine to describe the implementati=
on</tt><br>
<tt>&gt; recommendation, but not to suggest this is the way to acheive the =
best</tt><br>
<tt>&gt; performance or even the desired way to deploy PTP over MPLS.</tt><=
br>
<tt>&gt; </tt><br>
<tt>&gt; + I would like to see a statement added in the document that the</=
tt><br>
<tt>&gt; performance aspects (e.g. the phase or frequency alignment) </tt><=
br>
<tt>&gt; are outside the</tt><br>
<tt>&gt; scope of the document.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 6, 7, 8, 10 and 13 seems to focus only on the TC </tt><b=
r>
<tt>&gt; case between</tt><br>
<tt>&gt; OC's and does not consider BC situation.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 12 text on checksums could be improved to indicate this =
only</tt><br>
<tt>&gt; applies to TC and not to OC &amp; BC.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 16 seems to address only TC clocks and not OC or BC cloc=
ks.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 16.3 implies that the only possible way to handle PTP is=
 TC,</tt><br>
<tt>&gt; excluding BC --- &quot;don't have the capability to process 1588 <=
/tt><br>
<tt>&gt; packets (e.g.</tt><br>
<tt>&gt; TC processing)&quot; and &quot; &nbsp; Non-1588-aware LSRs ignore =
the
RSVP </tt><br>
<tt>&gt; 1588_PTP_LSP</tt><br>
<tt>&gt; object and just switch the MPLS packets carrying 1588 messages as =
data</tt><br>
<tt>&gt; packets and don't perform any TC processing.&quot;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Regards,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ZARLINK Semiconductor</tt><br>
<tt>&gt; Peter Meyer</tt><br>
<tt>&gt; Timing &amp; Synchronization</tt><br>
<tt>&gt; Communication Products Group</tt><br>
<tt>&gt; Office: +1-613-270-7203&nbsp; |&nbsp; Fax: +1-613-592-1010</tt><br=
>
<tt>&gt; peter.meyer@zarlink.com &nbsp;| </tt></span><a href=3D"www.zarlink=
.com"><tt><span
style=3D'font-size:10.0pt'>www.zarlink.com</span></tt></a><span style=3D'fo=
nt-size:
10.0pt;font-family:"Courier New"'><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt>=
<br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;Bhatia, Mana=
v
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(Manav)&quot; &nbs=
p;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;manav.bhatia@a=
lc
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; To </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;atel-lucent.com&gt=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;tictoc@ietf.org&quot; </tt><br>
<tt>&gt; &lt;tictoc@ietf.org&gt; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Sent by: &nbsp; &n=
bsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; cc </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;tictoc-bounces=
@i
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;etf.org&gt; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp;Subject </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[TICTO=
C]
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><=
br>
<tt>&gt; draft-ietf-tictoc-1588overmpls-00.t </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;26/01/2011 11:22
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;xt &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;
&nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AM &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt>=
<br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt>=
<br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt>=
<br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt>=
<br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt>=
<br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt>=
<br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; We've tried incorporating most of the comments that we received on=
 the</tt><br>
<tt>&gt; list. Please ping me if you think we have missed some.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Would be great if the WG can go through this and provide </tt><br>
<tt>&gt; feedback on the</tt><br>
<tt>&gt; same.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; The draft is available here:</tt><br>
<tt>&gt; </tt></span><a
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over"><tt=
><span
style=3D'font-size:10.0pt'>http://www.ietf.org/internet-drafts/draft-ietf-t=
ictoc-1588over</span></tt></a><span
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; mpls-00.txt</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &gt; -----Original Message-----</tt><br>
<tt>&gt; &gt; From: tictoc-bounces@ietf.org</tt><br>
<tt>&gt; &gt; [</tt></span><a href=3D"mailto:tictoc-bounces@ietf.org"><tt><=
span
style=3D'font-size:10.0pt'>mailto:tictoc-bounces@ietf.org</span></tt></a><t=
t><span
style=3D'font-size:10.0pt'>] On Behalf Of </span></tt><span style=3D'font-s=
ize:
10.0pt;font-family:"Courier New"'><br>
<tt>&gt; Internet-Drafts@ietf.org</tt><br>
<tt>&gt; &gt; Sent: Wednesday, January 26, 2011 9.30 PM</tt><br>
<tt>&gt; &gt; To: i-d-announce@ietf.org</tt><br>
<tt>&gt; &gt; Cc: tictoc@ietf.org</tt><br>
<tt>&gt; &gt; Subject: [TICTOC] I-D
Action:draft-ietf-tictoc-1588overmpls-00.txt</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; A New Internet-Draft is available from the on-line</tt><br>
<tt>&gt; &gt; Internet-Drafts directories.</tt><br>
<tt>&gt; &gt; This draft is a work item of the Timing over IP Connection</t=
t><br>
<tt>&gt; &gt; and Transfer of Clock Working Group of the IETF.</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Title &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; : Transporting PTP messages (1588) over</tt><br>
<tt>&gt; &gt; MPLS Networks</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Author(s) &nbsp; &nb=
sp;
&nbsp; : S. Davari, et al.</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Filename &nbsp; &nbs=
p;
&nbsp; &nbsp;: draft-ietf-tictoc-1588overmpls-00.txt</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Pages &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; : 35</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Date &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;: 2011-01-26</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; This document defines the method for transporting PTP </tt><b=
r>
<tt>&gt; messages (PDUs)</tt><br>
<tt>&gt; &gt; over an MPLS network to enable a proper handling of these pac=
kets</tt><br>
<tt>&gt; &gt; (e.g. implementation of Transparent Clocks (TC)) in LSRs.</tt=
><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; --</tt><br>
<tt>&gt; Manav Bhatia,</tt><br>
<tt>&gt; IP Division, Alcatel-Lucent,</tt><br>
<tt>&gt; Bangalore - India</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; _______________________________________________</tt><br>
<tt>&gt; TICTOC mailing list</tt><br>
<tt>&gt; TICTOC@ietf.org</tt><br>
<tt>&gt; </tt></span><a href=3D"https://www.ietf.org/mailman/listinfo/ticto=
c"><tt><span
style=3D'font-size:10.0pt'>https://www.ietf.org/mailman/listinfo/tictoc</sp=
an></tt></a><span
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ----------</tt><br>
<tt>&gt; This email is confidential and may contain information that </tt><=
br>
<tt>&gt; is privileged and</tt><br>
<tt>&gt; exempt from disclosure by law. &nbsp;If you have received it in </=
tt><br>
<tt>&gt; error, please contact</tt><br>
<tt>&gt; the sender immediately by return email and then delete it </tt><br=
>
<tt>&gt; from your system; you</tt><br>
<tt>&gt; should not copy it or disclose its contents to anyone. &nbsp;</tt>=
<br>
<tt>&gt; Emails are not secure</tt><br>
<tt>&gt; and cannot be guaranteed to be error free as they can be </tt><br>
<tt>&gt; intercepted, amended,</tt><br>
<tt>&gt; lost or destroyed, or contain viruses. &nbsp;Anyone who </tt><br>
<tt>&gt; communicates with us by email</tt><br>
<tt>&gt; is taken to accept these risks.</tt><br>
<tt>&gt; </tt><br>
<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt>TICTOC@ietf.org</tt><br>
</span><a href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><tt><span
style=3D'font-size:10.0pt'>https://www.ietf.org/mailman/listinfo/tictoc</sp=
an></tt></a><span
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt>TICTOC@ietf.org</tt><br>
</span><a href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><tt><span
style=3D'font-size:10.0pt'>https://www.ietf.org/mailman/listinfo/tictoc</sp=
an></tt></a><span
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<br>
</span><o:p></o:p></p>

</div>

</body>

</html>

--_000_2C2F1EBA8050E74EA81502D5740B4BD6941B906F42SJEXCHCCR02co_--


From sebastien.jobert@orange-ftgroup.com  Fri Feb 11 14:31:36 2011
Return-Path: <sebastien.jobert@orange-ftgroup.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B5263A67D8; Fri, 11 Feb 2011 14:31:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N2HSuKJlekgI; Fri, 11 Feb 2011 14:31:24 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 456D43A69DA; Fri, 11 Feb 2011 14:31:23 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id D8BC9858001; Fri, 11 Feb 2011 23:36:48 +0100 (CET)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id C70F5778003; Fri, 11 Feb 2011 23:36:48 +0100 (CET)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 11 Feb 2011 23:31:38 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBCA3B.71C594FB"
Date: Fri, 11 Feb 2011 23:31:35 +0100
Message-ID: <AFC377AFCC0FBD4DABE49F4B81EC4F1A02485533@ftrdmel1>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6941B906F42@SJEXCHCCR02.corp.ad.broadcom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [TICTOC] 1588overmpls-00 / MPLS profile & BC
Thread-Index: AcvIasz/fGOkmQBQT+GvX7xpCJOr9AA1XK5AADTxErAAAKlwMAAIbcKA
References: <CA2959F3E75BA645A43E81C3B071F6320ACFEA9560@USNAVSXCHMBSC2.ndc.alcatel-lucent.com><OF23A1DD85.5C87F3B6-ON85257832.0052BB99-85257832.0052DDFF@Zarlink.Com><28C9B1CD4D27844E9CD8F02BFEB70564075118B097@ESESSCMS0360.eemea.ericsson.se><6D53E9696A81554B9B2E14FF508BA7C80979D6426B@EMV35-UKDY.domain1.systemhost.net> <2C2F1EBA8050E74EA81502D5740B4BD6941B906F42@SJEXCHCCR02.corp.ad.broadcom.com>
From: <sebastien.jobert@orange-ftgroup.com>
To: <davari@broadcom.com>, <mike.gilson@bt.com>, <stefano.ruffini@ericsson.com>, <Peter.Meyer@Zarlink.Com>, <peter.roberts@alcatel-lucent.com>
X-OriginalArrivalTime: 11 Feb 2011 22:31:38.0251 (UTC) FILETIME=[72778DB0:01CBCA3B]
Cc: tictoc@ietf.org, tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Feb 2011 22:31:36 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBCA3B.71C594FB
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear all,

=20

Although I had not the opportunity to read the new versions of the draft =
that is discussed in this thread, I'll tend to share the same view as =
expressed by Stefano and Mike in case BCs only are considered.

=20

If we make the assumption that an MPLS node has to support an Ethernet =
physical layer, then I don't understand the reason to discuss PTP over =
MPLS (at least, when using BCs only).

That is: why transporting the PTP messages over an MPLS stack, and not =
simply directly over Ethernet (e.g. using the standard Ethernet mapping =
specified in IEEE1588-2008)?

(for those of you who have access to ITU-T contributions, you can refer =
to WD30 discussed during the SG15/Q13 interim meeting in Shenzhen, which =
tried to explain more in details this point)

=20

It seems to me that TCs are really the reason for this MPLS mapping. But =
in my opinion, the applicability of TCs in telecoms still needs to be =
discussed.

The justification of the pure MPLS mapping might be the case of =
tunneling.

=20

BTW: did you discuss in this draft the issue of identifying the position =
of the PTP payload (to modify the correction field in the case of TC) in =
the packet once a packet has been identified as a PTP message?

Indeed, in the general case, nothing forces the PTP payload to be in a =
fixed location (potential tunneling issue again).

=20

Thanks.

=20

BR,

=20

S=E9bastien

=20

De : tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] De la part =
de Shahram Davari
Envoy=E9 : vendredi 11 f=E9vrier 2011 19:11
=C0 : mike.gilson@bt.com; stefano.ruffini@ericsson.com; =
Peter.Meyer@Zarlink.Com; peter.roberts@alcatel-lucent.com
Cc : tictoc@ietf.org; tictoc-bounces@ietf.org
Objet : Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

=20

RAW mapping to MPLS has huge HW impact. No HW can support such a format =
today, and to be honest not justified when we already have Ethernet and =
IP encapsulations. We need to have a very good reason to add yet a 3rd =
option.

=20

Thx

Shahram

=20

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of mike.gilson@bt.com
Sent: Friday, February 11, 2011 9:54 AM
To: stefano.ruffini@ericsson.com; Peter.Meyer@Zarlink.Com; =
peter.roberts@alcatel-lucent.com
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

=20

I would think the interface would be Ethernet. How many interfaces are =
there that are pure MPLS or another.

=20

Maybe someone can expand on this.

=20

Regards,=20

Mike=20

________________________________

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Stefano Ruffini
Sent: 10 February 2011 16:35
To: Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Peter M., Peter R.

I wonder if there is really a need (use case) for section 5.3 (pure MPLS =
mapping) ?

 Best Regards

Stefano=20

=20

________________________________

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Peter.Meyer@Zarlink.Com
Sent: mercoled=EC 9 febbraio 2011 16.06
To: Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC


Thanks.=20

Yes, a poor choice of words on the Annexes being "profiles".  We would =
still need to fill out the Annex info though re: port addresses and the =
like to ensure inter-operability.=20

I am fine to be neutral on performance aspects -- I would recommend to =
indicate they are not within scope of the document.=20

ZARLINK Semiconductor
Peter Meyer
Timing & Synchronization
Communication Products Group
Office: +1-613-270-7203  |  Fax: +1-613-592-1010
peter.meyer@zarlink.com <mailto:employee.name@zarlink.com>   | =
www.zarlink.com <http://www.zarlink.com/>=20

=20

"Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>=20
Sent by: <tictoc-bounces@ietf.org>=20

09/02/2011 08:52 AM=20

To

"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, =
"Peter.Meyer@Zarlink.Com" <Peter.Meyer@zarlink.com>=20

cc

"tictoc@ietf.org" <tictoc@ietf.org>=20

Subject

Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

=20

	=09




Peter,
With respect to your comments on the profile, the Annexes are not =
profiles.  They are the portions of the standard that define the rules =
for running PTP over specific lower layer protocols.  These can then be =
included or excluded from specific profiles that are defined.  This =
draft is defining these rules for the MPLS environment. =20
The draft covers all the clock types but as you point out this is not =
all that clear.  This can be added.
In addition, I don't believe the ITU-T has concluded anything about =
performance of BC vs TC.  They have just started studying the issue.  =
But this draft is not making any claims about performance and as stated =
earlier should be applicable for any of the clock types.  We can review =
it to remove any contentious wording in respect to performance.
Peter R.

 =20

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org =
<mailto:tictoc-bounces@ietf.org> ] On Behalf Of Bhatia, Manav (Manav)
Sent: February 9, 2011 8:20 AM
To: Peter.Meyer@Zarlink.Com
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Hi Peter,

Very valid comments.=20

This draft covers all clock types - TC, BC and OC. The reason it seems =
we've been concentrating on TC is because that's the clock type that =
requires special MPLS processing.=20

For BC's and OC's there is no special processing involved. One just =
needs an MPLS LSP that terminates on a BC and OC and things will just =
work. However, I get the drift of what youre saying and we can update =
the draft to explicitly state this.

I will let someone more knowledgeable respond to your question on =
whether a separate profile for MPLS is required or not. To my untrained =
eye it looks that we might.

Cheers, Manav=20

> -----Original Message-----
> From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com =
<mailto:Peter.Meyer@Zarlink.Com> ]=20
> Sent: Wednesday, February 09, 2011 2.00 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>=20
>=20
> Hi Manav,
>=20
>=20
> A high level point is that for the pure MPLS mapping (section 5.3) , I
> wonder if what is really needed is a PTP profile for MPLS --=20
> similar to
> Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For=20
> example the IP &
> Ethernet profiles include other information such as the port=20
> addressing for
> the unicast master table and acceptable master table.  Without a full
> profile, although the intermediate notes may operate in TC,=20
> the server,
> client and boundary nodes may not operate successfully.
>=20
> Its not clear if this draft is intended to cover all clock=20
> types (OC, BC &
> TC) or only TC.  There are many sections that talk only about=20
> TC without
> considering OC and BC behaviour or impact.  Is BC intended to=20
> be covered as
> a Client-side OC + Server-side OC model, or is BC excluded from
> consideration in this draft?  Perhaps this draft should be either
> cleaned-up to consider all clock types or should be=20
> restricted to only TC
> clock type with OC & BC out of scope.
>=20
>=20
> Some specific comments
>=20
> + The abstract could be clarified to indicate there are three=20
> mappings, not
> two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
> third mapping may be under discussion, so perhaps this is premature.
>=20
> + A few places in the text the phrase "proper handling of=20
> these packets" or
> "properly handle PTP messages" or "perform proper =20
> processing"  is used to
> mean transparent clock.  I would propose to remove such=20
> language as from
> the ITU-T studies of timing performances of PTP one could argue the
> "proper" way is to implement a boundary clock.  Where the=20
> intention is to
> aid the designer of a TC that is fine to describe the implementation
> recommendation, but not to suggest this is the way to acheive the best
> performance or even the desired way to deploy PTP over MPLS.
>=20
> + I would like to see a statement added in the document that the
> performance aspects (e.g. the phase or frequency alignment)=20
> are outside the
> scope of the document.
>=20
> + Section 6, 7, 8, 10 and 13 seems to focus only on the TC=20
> case between
> OC's and does not consider BC situation.
>=20
> + Section 12 text on checksums could be improved to indicate this only
> applies to TC and not to OC & BC.
>=20
> + Section 16 seems to address only TC clocks and not OC or BC clocks.
>=20
> + Section 16.3 implies that the only possible way to handle PTP is TC,
> excluding BC --- "don't have the capability to process 1588=20
> packets (e.g.
> TC processing)" and "   Non-1588-aware LSRs ignore the RSVP=20
> 1588_PTP_LSP
> object and just switch the MPLS packets carrying 1588 messages as data
> packets and don't perform any TC processing."
>=20
>=20
> Regards,
>=20
>=20
> ZARLINK Semiconductor
> Peter Meyer
> Timing & Synchronization
> Communication Products Group
> Office: +1-613-270-7203  |  Fax: +1-613-592-1010
> peter.meyer@zarlink.com  | www.zarlink.com
>=20
>=20
>=20
>                                                              =20
>             =20
>              "Bhatia, Manav                                  =20
>             =20
>              (Manav)"                                        =20
>             =20
>              <manav.bhatia@alc                               =20
>           To=20
>              atel-lucent.com>          "tictoc@ietf.org"=20
> <tictoc@ietf.org>=20
>              Sent by:                                        =20
>           cc=20
>              <tictoc-bounces@i                               =20
>             =20
>              etf.org>                                        =20
>      Subject=20
>                                        [TICTOC]              =20
>             =20
>                                       =20
> draft-ietf-tictoc-1588overmpls-00.t=20
>              26/01/2011 11:22          xt                    =20
>             =20
>              AM                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>=20
>=20
>=20
>=20
> Hi,
>=20
> We've tried incorporating most of the comments that we received on the
> list. Please ping me if you think we have missed some.
>=20
> Would be great if the WG can go through this and provide=20
> feedback on the
> same.
>=20
> The draft is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over =
<http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over>=20
> mpls-00.txt
>=20
> Cheers, Manav
>=20
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org
> > [mailto:tictoc-bounces@ietf.org <mailto:tictoc-bounces@ietf.org> ] =
On Behalf Of=20
> Internet-Drafts@ietf.org
> > Sent: Wednesday, January 26, 2011 9.30 PM
> > To: i-d-announce@ietf.org
> > Cc: tictoc@ietf.org
> > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > MPLS Networks
> >            Author(s)       : S. Davari, et al.
> >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> >            Pages           : 35
> >            Date            : 2011-01-26
> >
> > This document defines the method for transporting PTP=20
> messages (PDUs)
> > over an MPLS network to enable a proper handling of these packets
> > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> >
>=20
> Cheers, Manav
>=20
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc =
<https://www.ietf.org/mailman/listinfo/tictoc>=20
>=20
>=20
>=20
> ----------
> This email is confidential and may contain information that=20
> is privileged and
> exempt from disclosure by law.  If you have received it in=20
> error, please contact
> the sender immediately by return email and then delete it=20
> from your system; you
> should not copy it or disclose its contents to anyone. =20
> Emails are not secure
> and cannot be guaranteed to be error free as they can be=20
> intercepted, amended,
> lost or destroyed, or contain viruses.  Anyone who=20
> communicates with us by email
> is taken to accept these risks.
>=20
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc =
<https://www.ietf.org/mailman/listinfo/tictoc>=20
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc =
<https://www.ietf.org/mailman/listinfo/tictoc>=20


------_=_NextPart_001_01CBCA3B.71C594FB
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;}
@font-face
	{font-family:"Arial Black";
	panose-1:2 11 10 4 2 1 2 2 2 4;}
@font-face
	{font-family:"Trebuchet MS";
	panose-1:2 11 6 3 2 2 2 2 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dear all,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Although I had not the opportunity to read the new =
versions of
the draft that is discussed in this thread, I&#8217;ll tend to share the =
same view
as expressed by Stefano and Mike in case BCs only are =
considered.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If we make the assumption that an MPLS node has to =
support an
Ethernet physical layer, then I don&#8217;t understand the reason to =
discuss
PTP over MPLS (at least, when using BCs only).<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>That is: why transporting the PTP messages over an MPLS =
stack,
and not simply directly over Ethernet (e.g. using the standard Ethernet =
mapping
specified in IEEE1588-2008)?<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>(for those of you who have access to ITU-T contributions, =
you
can refer to WD30 discussed during the SG15/Q13 interim meeting in =
Shenzhen,
which tried to explain more in details this point)<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It seems to me that TCs are really the reason for this =
MPLS
mapping. But in my opinion, the applicability of TCs in telecoms still =
needs to
be discussed.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The justification of the pure MPLS mapping might be the =
case of
tunneling.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>BTW: did you discuss in this draft the issue of =
identifying the
position of the PTP payload (to modify the correction field in the case =
of TC) in
the packet once a packet has been identified as a PTP =
message?<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Indeed, in the general case, nothing forces the PTP =
payload to
be in a fixed location (potential tunneling issue =
again).<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>BR,<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>S=E9bastien<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</s=
pan></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] <b>De la part =
de</b>
Shahram Davari<br>
<b>Envoy=E9&nbsp;:</b> vendredi 11 f=E9vrier 2011 19:11<br>
<b>=C0&nbsp;:</b> mike.gilson@bt.com; stefano.ruffini@ericsson.com;
Peter.Meyer@Zarlink.Com; peter.roberts@alcatel-lucent.com<br>
<b>Cc&nbsp;:</b> tictoc@ietf.org; tictoc-bounces@ietf.org<br>
<b>Objet&nbsp;:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>RAW mapping to MPLS has huge HW impact. No HW can support =
such a
format today, and to be honest not justified when we already have =
Ethernet and
IP encapsulations. We need to have a very good reason to add yet a =
3<sup>rd</sup>
option.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thx<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Shahram<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> tictoc-bounces@ietf.org
[mailto:tictoc-bounces@ietf.org] <b>On Behalf Of =
</b>mike.gilson@bt.com<br>
<b>Sent:</b> Friday, February 11, 2011 9:54 AM<br>
<b>To:</b> stefano.ruffini@ericsson.com; Peter.Meyer@Zarlink.Com;
peter.roberts@alcatel-lucent.com<br>
<b>Cc:</b> tictoc@ietf.org; tictoc-bounces@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";
color:blue'>I would think the interface would be Ethernet.&nbsp;How many
interfaces are there that are pure MPLS or another.</span><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";
color:blue'>Maybe someone can expand on this.</span><span =
lang=3DEN-US><o:p></o:p></span></p>

<div>

<p class=3DMsoNormal><span lang=3DEN-US>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Regards,</spa=
n><span
lang=3DEN-GB> </span><span lang=3DEN-US><o:p></o:p></span></p>

</div>

<p><i><span lang=3DEN-GB style=3D'font-size:13.5pt;font-family:"Comic =
Sans MS";
color:blue'>Mike</span></i><span lang=3DEN-GB> </span><span =
lang=3DEN-US><o:p></o:p></span></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span =
lang=3DEN-US>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] <b>On Behalf Of =
</b>Stefano
Ruffini<br>
<b>Sent:</b> 10 February 2011 16:35<br>
<b>To:</b> Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)<br>
<b>Cc:</b> tictoc@ietf.org; tictoc-bounces@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC</span><span
lang=3DEN-US><o:p></o:p></span></p>

</div>

<p><span lang=3DIT>Peter M., Peter R.<o:p></o:p></span></p>

<p><span lang=3DIT>I wonder if there is really a need (use case) for =
section 5.3
(pure MPLS mapping) ?<o:p></o:p></span></p>

<p><span lang=3DIT>&nbsp;Best Regards<o:p></o:p></span></p>

<p><span lang=3DIT>Stefano <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span =
lang=3DEN-US>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tictoc-bounces@ietf.org
[mailto:tictoc-bounces@ietf.org] <b>On Behalf Of =
</b>Peter.Meyer@Zarlink.Com<br>
<b>Sent:</b> mercoled=EC 9 febbraio 2011 16.06<br>
<b>To:</b> Roberts, Peter (Peter)<br>
<b>Cc:</b> tictoc@ietf.org; tictoc-bounces@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><br>
</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Thanks.</span=
><span
lang=3DEN-US> <br>
<br>
</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Yes,
a poor choice of words on the Annexes being &quot;profiles&quot;. =
&nbsp;We
would still need to fill out the Annex info though re: port addresses =
and the
like to ensure inter-operability.</span><span lang=3DEN-US> <br>
<br>
</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>I
am fine to be neutral on performance aspects -- I would recommend to =
indicate
they are not within scope of the document.</span><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:"Arial Black","sans-serif"'> =
</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p><b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Arial =
Black","sans-serif"'>ZARLINK</span></b><b><span
lang=3DEN-US style=3D'font-family:"Arial Black","sans-serif"'> =
</span></b><span
lang=3DEN-US style=3D'font-size:7.5pt;font-family:"Trebuchet =
MS","sans-serif"'>Semiconductor<b><br>
Peter Meyer<i><span style=3D'color:gray'><br>
Timing &amp; Synchronization<br>
Communication Products Group</span></i></b><i><br>
Office: +1-613-270-7203</i><b>&nbsp; |&nbsp; </b><i>Fax: =
+1-613-592-1010</i><u><span
style=3D'color:blue'><br>
</span></u></span><span lang=3DEN-US><a =
href=3D"mailto:employee.name@zarlink.com"><span
style=3D'font-size:7.5pt;font-family:"Trebuchet =
MS","sans-serif"'>peter.meyer@zarlink.com</span></a></span><span
lang=3DEN-US style=3D'font-size:7.5pt;font-family:"Trebuchet =
MS","sans-serif"'> <b>&nbsp;|
</b></span><span lang=3DEN-US><a href=3D"http://www.zarlink.com/"><span
style=3D'font-size:7.5pt;font-family:"Trebuchet =
MS","sans-serif"'>www.zarlink.com</span></a><o:p></o:p></span></p>

<p style=3D'margin-bottom:12.0pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%"
 style=3D'width:100.0%'>
 <tr>
  <td width=3D"40%" valign=3Dtop style=3D'width:40.0%;padding:.75pt =
.75pt .75pt .75pt'>
  <p class=3DMsoNormal><b><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>&quot;Roberts,=

  Peter (Peter)&quot; =
&lt;peter.roberts@alcatel-lucent.com&gt;</span></b><span
  style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'> =
</span><br>
  <span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>Sent =
by:
  &lt;tictoc-bounces@ietf.org&gt;</span> <o:p></o:p></p>
  <p><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>09/02/2011
  08:52 AM</span> <o:p></o:p></p>
  </td>
  <td width=3D"59%" valign=3Dtop style=3D'width:59.0%;padding:.75pt =
.75pt .75pt .75pt'>
  <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 =
width=3D"100%"
   style=3D'width:100.0%'>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
    =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>To</span><o:p>=
</o:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>&quot;Bhatia,
    Manav (Manav)&quot; &lt;manav.bhatia@alcatel-lucent.com&gt;,
    &quot;Peter.Meyer@Zarlink.Com&quot; =
&lt;Peter.Meyer@zarlink.com&gt;</span> <o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
    =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>cc</span><o:p>=
</o:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>&quot;tictoc@i=
etf.org&quot;
    &lt;tictoc@ietf.org&gt;</span> <o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
    =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>Subject</span>=
<o:p></o:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>Re:
    [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC</span><o:p></o:p></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><o:p>&nbsp;</o:p></p>
  <table class=3DMsoNormalTable border=3D0 cellpadding=3D0>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td>
   </tr>
  </table>
  <p class=3DMsoNormal><o:p></o:p></p>
  </td>
 </tr>
</table>

<p style=3D'margin-bottom:12.0pt'><span lang=3DEN-US><br>
<br>
<br>
</span><tt><span lang=3DEN-US =
style=3D'font-size:10.0pt'>Peter,</span></tt><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>With respect to your comments on the profile, the Annexes are not =
profiles.
&nbsp;They are the portions of the standard that define the rules for =
running
PTP over specific lower layer protocols. &nbsp;These can then be =
included or
excluded from specific profiles that are defined. &nbsp;This draft is =
defining
these rules for the MPLS environment. &nbsp;</tt><br>
<tt>The draft covers all the clock types but as you point out this is =
not all
that clear. &nbsp;This can be added.</tt><br>
<tt>In addition, I don't believe the ITU-T has concluded anything about =
performance
of BC vs TC. &nbsp;They have just started studying the issue. &nbsp;But =
this
draft is not making any claims about performance and as stated earlier =
should
be applicable for any of the clock types. &nbsp;We can review it to =
remove any
contentious wording in respect to performance.</tt><br>
<tt>Peter R.</tt><br>
<br>
<tt>&nbsp; </tt><br>
<br>
<tt>-----Original Message-----</tt><br>
<tt>From: tictoc-bounces@ietf.org [</tt></span><span lang=3DEN-US><a
href=3D"mailto:tictoc-bounces@ietf.org"><tt><span =
style=3D'font-size:10.0pt'>mailto:tictoc-bounces@ietf.org</span></tt></a>=
</span><tt><span
lang=3DEN-US style=3D'font-size:10.0pt'>] On Behalf Of Bhatia, Manav =
(Manav)</span></tt><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>Sent: February 9, 2011 8:20 AM</tt><br>
<tt>To: Peter.Meyer@Zarlink.Com</tt><br>
<tt>Cc: tictoc@ietf.org</tt><br>
<tt>Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC</tt><br>
<br>
<tt>Hi Peter,</tt><br>
<br>
<tt>Very valid comments. </tt><br>
<br>
<tt>This draft covers all clock types - TC, BC and OC. The reason it =
seems
we've been concentrating on TC is because that's the clock type that =
requires
special MPLS processing. </tt><br>
<br>
<tt>For BC's and OC's there is no special processing involved. One just =
needs
an MPLS LSP that terminates on a BC and OC and things will just work. =
However,
I get the drift of what youre saying and we can update the draft to =
explicitly
state this.</tt><br>
<br>
<tt>I will let someone more knowledgeable respond to your question on =
whether a
separate profile for MPLS is required or not. To my untrained eye it =
looks that
we might.</tt><br>
<br>
<tt>Cheers, Manav </tt><br>
<br>
<tt>&gt; -----Original Message-----</tt><br>
<tt>&gt; From: Peter.Meyer@Zarlink.Com [</tt></span><span =
lang=3DEN-US><a
href=3D"mailto:Peter.Meyer@Zarlink.Com"><tt><span =
style=3D'font-size:10.0pt'>mailto:Peter.Meyer@Zarlink.Com</span></tt></a>=
</span><tt><span
lang=3DEN-US style=3D'font-size:10.0pt'>] </span></tt><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; Sent: Wednesday, February 09, 2011 2.00 PM</tt><br>
<tt>&gt; To: Bhatia, Manav (Manav)</tt><br>
<tt>&gt; Cc: tictoc@ietf.org</tt><br>
<tt>&gt; Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi Manav,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; A high level point is that for the pure MPLS mapping (section =
5.3) , I</tt><br>
<tt>&gt; wonder if what is really needed is a PTP profile for MPLS -- =
</tt><br>
<tt>&gt; similar to</tt><br>
<tt>&gt; Annex D/E/F for IPv4/IPv6/Ethernet, respectively. &nbsp;For =
</tt><br>
<tt>&gt; example the IP &amp;</tt><br>
<tt>&gt; Ethernet profiles include other information such as the port =
</tt><br>
<tt>&gt; addressing for</tt><br>
<tt>&gt; the unicast master table and acceptable master table. =
&nbsp;Without a
full</tt><br>
<tt>&gt; profile, although the intermediate notes may operate in TC, =
</tt><br>
<tt>&gt; the server,</tt><br>
<tt>&gt; client and boundary nodes may not operate =
successfully.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Its not clear if this draft is intended to cover all clock =
</tt><br>
<tt>&gt; types (OC, BC &amp;</tt><br>
<tt>&gt; TC) or only TC. &nbsp;There are many sections that talk only =
about </tt><br>
<tt>&gt; TC without</tt><br>
<tt>&gt; considering OC and BC behaviour or impact. &nbsp;Is BC intended =
to </tt><br>
<tt>&gt; be covered as</tt><br>
<tt>&gt; a Client-side OC + Server-side OC model, or is BC excluded =
from</tt><br>
<tt>&gt; consideration in this draft? &nbsp;Perhaps this draft should be =
either</tt><br>
<tt>&gt; cleaned-up to consider all clock types or should be </tt><br>
<tt>&gt; restricted to only TC</tt><br>
<tt>&gt; clock type with OC &amp; BC out of scope.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Some specific comments</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + The abstract could be clarified to indicate there are three =
</tt><br>
<tt>&gt; mappings, not</tt><br>
<tt>&gt; two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS). =
&nbsp;I
think the</tt><br>
<tt>&gt; third mapping may be under discussion, so perhaps this is =
premature.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + A few places in the text the phrase &quot;proper handling of =
</tt><br>
<tt>&gt; these packets&quot; or</tt><br>
<tt>&gt; &quot;properly handle PTP messages&quot; or &quot;perform =
proper
&nbsp;</tt><br>
<tt>&gt; processing&quot; &nbsp;is used to</tt><br>
<tt>&gt; mean transparent clock. &nbsp;I would propose to remove such =
</tt><br>
<tt>&gt; language as from</tt><br>
<tt>&gt; the ITU-T studies of timing performances of PTP one could argue =
the</tt><br>
<tt>&gt; &quot;proper&quot; way is to implement a boundary clock. =
&nbsp;Where
the </tt><br>
<tt>&gt; intention is to</tt><br>
<tt>&gt; aid the designer of a TC that is fine to describe the =
implementation</tt><br>
<tt>&gt; recommendation, but not to suggest this is the way to acheive =
the best</tt><br>
<tt>&gt; performance or even the desired way to deploy PTP over =
MPLS.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + I would like to see a statement added in the document that =
the</tt><br>
<tt>&gt; performance aspects (e.g. the phase or frequency alignment) =
</tt><br>
<tt>&gt; are outside the</tt><br>
<tt>&gt; scope of the document.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 6, 7, 8, 10 and 13 seems to focus only on the TC =
</tt><br>
<tt>&gt; case between</tt><br>
<tt>&gt; OC's and does not consider BC situation.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 12 text on checksums could be improved to indicate =
this only</tt><br>
<tt>&gt; applies to TC and not to OC &amp; BC.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 16 seems to address only TC clocks and not OC or BC =
clocks.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 16.3 implies that the only possible way to handle PTP =
is TC,</tt><br>
<tt>&gt; excluding BC --- &quot;don't have the capability to process =
1588 </tt><br>
<tt>&gt; packets (e.g.</tt><br>
<tt>&gt; TC processing)&quot; and &quot; &nbsp; Non-1588-aware LSRs =
ignore the
RSVP </tt><br>
<tt>&gt; 1588_PTP_LSP</tt><br>
<tt>&gt; object and just switch the MPLS packets carrying 1588 messages =
as data</tt><br>
<tt>&gt; packets and don't perform any TC processing.&quot;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Regards,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ZARLINK Semiconductor</tt><br>
<tt>&gt; Peter Meyer</tt><br>
<tt>&gt; Timing &amp; Synchronization</tt><br>
<tt>&gt; Communication Products Group</tt><br>
<tt>&gt; Office: +1-613-270-7203&nbsp; |&nbsp; Fax: =
+1-613-592-1010</tt><br>
<tt>&gt; peter.meyer@zarlink.com &nbsp;| </tt></span><span =
lang=3DEN-US><a
href=3D"www.zarlink.com"><tt><span =
style=3D'font-size:10.0pt'>www.zarlink.com</span></tt></a></span><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;Bhatia, =
Manav
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(Manav)&quot; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&lt;manav.bhatia@alc
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; To </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;atel-lucent.com&gt;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;tictoc@ietf.org&quot; </tt><br>
<tt>&gt; &lt;tictoc@ietf.org&gt; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Sent by: &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; cc </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&lt;tictoc-bounces@i
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;etf.org&gt; =
&nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp;Subject </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;[TICTOC]
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;</tt><br>
<tt>&gt; draft-ietf-tictoc-1588overmpls-00.t </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;26/01/2011 =
11:22
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;xt &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AM &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; We've tried incorporating most of the comments that we received =
on the</tt><br>
<tt>&gt; list. Please ping me if you think we have missed some.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Would be great if the WG can go through this and provide =
</tt><br>
<tt>&gt; feedback on the</tt><br>
<tt>&gt; same.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; The draft is available here:</tt><br>
<tt>&gt; </tt></span><span lang=3DEN-US><a
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over"><=
tt><span
style=3D'font-size:10.0pt'>http://www.ietf.org/internet-drafts/draft-ietf=
-tictoc-1588over</span></tt></a></span><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; mpls-00.txt</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &gt; -----Original Message-----</tt><br>
<tt>&gt; &gt; From: tictoc-bounces@ietf.org</tt><br>
<tt>&gt; &gt; [</tt></span><span lang=3DEN-US><a
href=3D"mailto:tictoc-bounces@ietf.org"><tt><span =
style=3D'font-size:10.0pt'>mailto:tictoc-bounces@ietf.org</span></tt></a>=
</span><tt><span
lang=3DEN-US style=3D'font-size:10.0pt'>] On Behalf Of </span></tt><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; Internet-Drafts@ietf.org</tt><br>
<tt>&gt; &gt; Sent: Wednesday, January 26, 2011 9.30 PM</tt><br>
<tt>&gt; &gt; To: i-d-announce@ietf.org</tt><br>
<tt>&gt; &gt; Cc: tictoc@ietf.org</tt><br>
<tt>&gt; &gt; Subject: [TICTOC] I-D
Action:draft-ietf-tictoc-1588overmpls-00.txt</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; A New Internet-Draft is available from the =
on-line</tt><br>
<tt>&gt; &gt; Internet-Drafts directories.</tt><br>
<tt>&gt; &gt; This draft is a work item of the Timing over IP =
Connection</tt><br>
<tt>&gt; &gt; and Transfer of Clock Working Group of the IETF.</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Title &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; : Transporting PTP messages (1588) over</tt><br>
<tt>&gt; &gt; MPLS Networks</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Author(s) &nbsp; =
&nbsp;
&nbsp; : S. Davari, et al.</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Filename &nbsp; =
&nbsp;
&nbsp; &nbsp;: draft-ietf-tictoc-1588overmpls-00.txt</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Pages &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; : 35</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Date &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;: 2011-01-26</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; This document defines the method for transporting PTP =
</tt><br>
<tt>&gt; messages (PDUs)</tt><br>
<tt>&gt; &gt; over an MPLS network to enable a proper handling of these =
packets</tt><br>
<tt>&gt; &gt; (e.g. implementation of Transparent Clocks (TC)) in =
LSRs.</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; --</tt><br>
<tt>&gt; Manav Bhatia,</tt><br>
<tt>&gt; IP Division, Alcatel-Lucent,</tt><br>
<tt>&gt; Bangalore - India</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; _______________________________________________</tt><br>
<tt>&gt; TICTOC mailing list</tt><br>
<tt>&gt; TICTOC@ietf.org</tt><br>
<tt>&gt; </tt></span><span lang=3DEN-US><a
href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><tt><span =
style=3D'font-size:
10.0pt'>https://www.ietf.org/mailman/listinfo/tictoc</span></tt></a></spa=
n><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ----------</tt><br>
<tt>&gt; This email is confidential and may contain information that =
</tt><br>
<tt>&gt; is privileged and</tt><br>
<tt>&gt; exempt from disclosure by law. &nbsp;If you have received it in =
</tt><br>
<tt>&gt; error, please contact</tt><br>
<tt>&gt; the sender immediately by return email and then delete it =
</tt><br>
<tt>&gt; from your system; you</tt><br>
<tt>&gt; should not copy it or disclose its contents to anyone. =
&nbsp;</tt><br>
<tt>&gt; Emails are not secure</tt><br>
<tt>&gt; and cannot be guaranteed to be error free as they can be =
</tt><br>
<tt>&gt; intercepted, amended,</tt><br>
<tt>&gt; lost or destroyed, or contain viruses. &nbsp;Anyone who =
</tt><br>
<tt>&gt; communicates with us by email</tt><br>
<tt>&gt; is taken to accept these risks.</tt><br>
<tt>&gt; </tt><br>
<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt>TICTOC@ietf.org</tt><br>
</span><span lang=3DEN-US><a =
href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><tt><span
style=3D'font-size:10.0pt'>https://www.ietf.org/mailman/listinfo/tictoc</=
span></tt></a></span><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt>TICTOC@ietf.org</tt><br>
</span><span lang=3DEN-US><a =
href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><tt><span
style=3D'font-size:10.0pt'>https://www.ietf.org/mailman/listinfo/tictoc</=
span></tt></a><o:p></o:p></span></p>

</div>

</body>

</html>

------_=_NextPart_001_01CBCA3B.71C594FB--

From le@vitesse.com  Sat Feb 12 02:06:37 2011
Return-Path: <le@vitesse.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5131A3A6898; Sat, 12 Feb 2011 02:06:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VxKGb6dwbgyS; Sat, 12 Feb 2011 02:06:27 -0800 (PST)
Received: from na3sys009aog101.obsmtp.com (na3sys009aog101.obsmtp.com [74.125.149.67]) by core3.amsl.com (Postfix) with SMTP id E5CD03A68B8; Sat, 12 Feb 2011 02:06:25 -0800 (PST)
Received: from source ([67.78.86.101]) (using TLSv1) by na3sys009aob101.postini.com ([74.125.148.12]) with SMTP ID DSNKTVZbruZA5kFaI98GcXD+X/sKE2/YMsiP@postini.com; Sat, 12 Feb 2011 02:06:43 PST
Received: from MBOX-TXA2.vitesse.com ([fe80::9c05:6cd3:4567:4bb0]) by cash-txa2.vitesse.com ([::1]) with mapi id 14.01.0270.001; Sat, 12 Feb 2011 04:06:29 -0600
From: Lars Ellegaard <le@vitesse.com>
To: "mike.gilson@bt.com" <mike.gilson@bt.com>, "stefano.ruffini@ericsson.com" <stefano.ruffini@ericsson.com>, "Peter.Meyer@Zarlink.Com" <Peter.Meyer@Zarlink.Com>, "peter.roberts@alcatel-lucent.com" <peter.roberts@alcatel-lucent.com>
Thread-Topic: [TICTOC] 1588overmpls-00 / MPLS profile & BC
Thread-Index: AQHLyDQNOpo7YeKsLEesn8fodpIEL5P5jGiAgAAI3ACAABR+AIABq1gAgAHJ2ID//5kXoA==
Date: Sat, 12 Feb 2011 10:06:28 +0000
Message-ID: <785DA01679B0C44F951747BE9CF66E6B04F3E7FC@mbox-txa2.vitesse.com>
References: <CA2959F3E75BA645A43E81C3B071F6320ACFEA9560@USNAVSXCHMBSC2.ndc.alcatel-lucent.com> <OF23A1DD85.5C87F3B6-ON85257832.0052BB99-85257832.0052DDFF@Zarlink.Com> <28C9B1CD4D27844E9CD8F02BFEB70564075118B097@ESESSCMS0360.eemea.ericsson.se> <6D53E9696A81554B9B2E14FF508BA7C80979D6426B@EMV35-UKDY.domain1.systemhost.net>
In-Reply-To: <6D53E9696A81554B9B2E14FF508BA7C80979D6426B@EMV35-UKDY.domain1.systemhost.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.9.64.2]
Content-Type: multipart/alternative; boundary="_000_785DA01679B0C44F951747BE9CF66E6B04F3E7FCmboxtxa2vitesse_"
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>, "tictoc-bounces@ietf.org" <tictoc-bounces@ietf.org>
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 12 Feb 2011 10:06:37 -0000

--_000_785DA01679B0C44F951747BE9CF66E6B04F3E7FCmboxtxa2vitesse_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This would be PTPoverACHoMPLSoETH (or other link layer technologies).

In my view MPLS(-TP) provides "transport" of an application, which is behin=
d some form of addressing (typically IP, Ethernet).
Only exception are (MPLS) transport associated mechanisms like OAM. MPLS(-T=
P) does not have an addressing scheme.
It would therefore be a violation of this if the PTP application (which req=
uires multicast/unicast addressing) is carried directly after the label (ev=
en after the ACH).
In other words even though it is possible, I suggest not to support PTPoACH=
oMPLS or PTPoMPLS.

BR Lars


From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 mike.gilson@bt.com
Sent: 11 February 2011 18:54
To: stefano.ruffini@ericsson.com; Peter.Meyer@Zarlink.Com; peter.roberts@al=
catel-lucent.com
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

I would think the interface would be Ethernet. How many interfaces are ther=
e that are pure MPLS or another.

Maybe someone can expand on this.

Regards,

Mike

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Stefano Ruffini
Sent: 10 February 2011 16:35
To: Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Peter M., Peter R.

I wonder if there is really a need (use case) for section 5.3 (pure MPLS ma=
pping) ?

 Best Regards

Stefano

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Peter.Meyer@Zarlink.Com
Sent: mercoled=EC 9 febbraio 2011 16.06
To: Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Thanks.

Yes, a poor choice of words on the Annexes being "profiles".  We would stil=
l need to fill out the Annex info though re: port addresses and the like to=
 ensure inter-operability.

I am fine to be neutral on performance aspects -- I would recommend to indi=
cate they are not within scope of the document.

ZARLINK Semiconductor
Peter Meyer
Timing & Synchronization
Communication Products Group
Office: +1-613-270-7203  |  Fax: +1-613-592-1010
peter.meyer@zarlink.com<mailto:employee.name@zarlink.com>  | www.zarlink.co=
m<http://www.zarlink.com/>


"Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>
Sent by: <tictoc-bounces@ietf.org>

09/02/2011 08:52 AM

To

"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "Peter.Meyer@Zar=
link.Com" <Peter.Meyer@zarlink.com>

cc

"tictoc@ietf.org" <tictoc@ietf.org>

Subject

Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC







Peter,
With respect to your comments on the profile, the Annexes are not profiles.=
  They are the portions of the standard that define the rules for running P=
TP over specific lower layer protocols.  These can then be included or excl=
uded from specific profiles that are defined.  This draft is defining these=
 rules for the MPLS environment.
The draft covers all the clock types but as you point out this is not all t=
hat clear.  This can be added.
In addition, I don't believe the ITU-T has concluded anything about perform=
ance of BC vs TC.  They have just started studying the issue.  But this dra=
ft is not making any claims about performance and as stated earlier should =
be applicable for any of the clock types.  We can review it to remove any c=
ontentious wording in respect to performance.
Peter R.



-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: February 9, 2011 8:20 AM
To: Peter.Meyer@Zarlink.Com
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Hi Peter,

Very valid comments.

This draft covers all clock types - TC, BC and OC. The reason it seems we'v=
e been concentrating on TC is because that's the clock type that requires s=
pecial MPLS processing.

For BC's and OC's there is no special processing involved. One just needs a=
n MPLS LSP that terminates on a BC and OC and things will just work. Howeve=
r, I get the drift of what youre saying and we can update the draft to expl=
icitly state this.

I will let someone more knowledgeable respond to your question on whether a=
 separate profile for MPLS is required or not. To my untrained eye it looks=
 that we might.

Cheers, Manav

> -----Original Message-----
> From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com]
> Sent: Wednesday, February 09, 2011 2.00 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
> Hi Manav,
>
>
> A high level point is that for the pure MPLS mapping (section 5.3) , I
> wonder if what is really needed is a PTP profile for MPLS --
> similar to
> Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For
> example the IP &
> Ethernet profiles include other information such as the port
> addressing for
> the unicast master table and acceptable master table.  Without a full
> profile, although the intermediate notes may operate in TC,
> the server,
> client and boundary nodes may not operate successfully.
>
> Its not clear if this draft is intended to cover all clock
> types (OC, BC &
> TC) or only TC.  There are many sections that talk only about
> TC without
> considering OC and BC behaviour or impact.  Is BC intended to
> be covered as
> a Client-side OC + Server-side OC model, or is BC excluded from
> consideration in this draft?  Perhaps this draft should be either
> cleaned-up to consider all clock types or should be
> restricted to only TC
> clock type with OC & BC out of scope.
>
>
> Some specific comments
>
> + The abstract could be clarified to indicate there are three
> mappings, not
> two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
> third mapping may be under discussion, so perhaps this is premature.
>
> + A few places in the text the phrase "proper handling of
> these packets" or
> "properly handle PTP messages" or "perform proper
> processing"  is used to
> mean transparent clock.  I would propose to remove such
> language as from
> the ITU-T studies of timing performances of PTP one could argue the
> "proper" way is to implement a boundary clock.  Where the
> intention is to
> aid the designer of a TC that is fine to describe the implementation
> recommendation, but not to suggest this is the way to acheive the best
> performance or even the desired way to deploy PTP over MPLS.
>
> + I would like to see a statement added in the document that the
> performance aspects (e.g. the phase or frequency alignment)
> are outside the
> scope of the document.
>
> + Section 6, 7, 8, 10 and 13 seems to focus only on the TC
> case between
> OC's and does not consider BC situation.
>
> + Section 12 text on checksums could be improved to indicate this only
> applies to TC and not to OC & BC.
>
> + Section 16 seems to address only TC clocks and not OC or BC clocks.
>
> + Section 16.3 implies that the only possible way to handle PTP is TC,
> excluding BC --- "don't have the capability to process 1588
> packets (e.g.
> TC processing)" and "   Non-1588-aware LSRs ignore the RSVP
> 1588_PTP_LSP
> object and just switch the MPLS packets carrying 1588 messages as data
> packets and don't perform any TC processing."
>
>
> Regards,
>
>
> ZARLINK Semiconductor
> Peter Meyer
> Timing & Synchronization
> Communication Products Group
> Office: +1-613-270-7203  |  Fax: +1-613-592-1010
> peter.meyer@zarlink.com  | www.zarlink.com
>
>
>
>
>
>              "Bhatia, Manav
>
>              (Manav)"
>
>              <manav.bhatia@alc
>           To
>              atel-lucent.com>          "tictoc@ietf.org"
> <tictoc@ietf.org>
>              Sent by:
>           cc
>              <tictoc-bounces@i
>
>              etf.org>
>      Subject
>                                        [TICTOC]
>
>
> draft-ietf-tictoc-1588overmpls-00.t
>              26/01/2011 11:22          xt
>
>              AM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi,
>
> We've tried incorporating most of the comments that we received on the
> list. Please ping me if you think we have missed some.
>
> Would be great if the WG can go through this and provide
> feedback on the
> same.
>
> The draft is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over
> mpls-00.txt
>
> Cheers, Manav
>
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org
> > [mailto:tictoc-bounces@ietf.org] On Behalf Of
> Internet-Drafts@ietf.org
> > Sent: Wednesday, January 26, 2011 9.30 PM
> > To: i-d-announce@ietf.org
> > Cc: tictoc@ietf.org
> > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > MPLS Networks
> >            Author(s)       : S. Davari, et al.
> >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> >            Pages           : 35
> >            Date            : 2011-01-26
> >
> > This document defines the method for transporting PTP
> messages (PDUs)
> > over an MPLS network to enable a proper handling of these packets
> > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> >
>
> Cheers, Manav
>
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>
>
> ----------
> This email is confidential and may contain information that
> is privileged and
> exempt from disclosure by law.  If you have received it in
> error, please contact
> the sender immediately by return email and then delete it
> from your system; you
> should not copy it or disclose its contents to anyone.
> Emails are not secure
> and cannot be guaranteed to be error free as they can be
> intercepted, amended,
> lost or destroyed, or contain viruses.  Anyone who
> communicates with us by email
> is taken to accept these risks.
>
_______________________________________________
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


--_000_785DA01679B0C44F951747BE9CF66E6B04F3E7FCmboxtxa2vitesse_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;}
@font-face
	{font-family:"Arial Black";
	panose-1:2 11 10 4 2 1 2 2 2 4;}
@font-face
	{font-family:"Trebuchet MS";
	panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">This would be PTPoverACHo=
MPLSoETH (or other link layer technologies).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">In my view MPLS(-TP) prov=
ides &#8220;transport&#8221; of an application, which is behind some form o=
f addressing (typically IP, Ethernet).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Only exception are (MPLS)=
 transport associated mechanisms like OAM. MPLS(-TP) does not have an addre=
ssing scheme.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">It would therefore be a v=
iolation of this if the PTP application (which requires multicast/unicast a=
ddressing) is carried directly after the label (even after
 the ACH).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">In other words even thoug=
h it is possible, I suggest not to support PTPoACHoMPLS or PTPoMPLS.<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">BR Lars<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tictoc-b=
ounces@ietf.org [mailto:tictoc-bounces@ietf.org]
<b>On Behalf Of </b>mike.gilson@bt.com<br>
<b>Sent:</b> 11 February 2011 18:54<br>
<b>To:</b> stefano.ruffini@ericsson.com; Peter.Meyer@Zarlink.Com; peter.rob=
erts@alcatel-lucent.com<br>
<b>Cc:</b> tictoc@ietf.org; tictoc-bounces@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC<o:p></=
o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:blue">I would think the interface would be Ethernet.&=
nbsp;How many interfaces are there that are pure MPLS or another.</span><o:=
p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:blue">Maybe someone can expand on this.</span><o:p></=
o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-=
family:&quot;Arial&quot;,&quot;sans-serif&quot;">Regards,</span><span lang=
=3D"EN-GB">
</span><o:p></o:p></p>
</div>
<p><i><span lang=3D"EN-GB" style=3D"font-size:13.5pt;font-family:&quot;Comi=
c Sans MS&quot;;color:blue">Mike</span></i><span lang=3D"EN-GB">
</span><o:p></o:p></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:<=
/span></b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&q=
uot;sans-serif&quot;"> tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.=
org]
<b>On Behalf Of </b>Stefano Ruffini<br>
<b>Sent:</b> 10 February 2011 16:35<br>
<b>To:</b> Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)<br>
<b>Cc:</b> tictoc@ietf.org; tictoc-bounces@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</span>=
<o:p></o:p></p>
</div>
<p><span lang=3D"IT">Peter M., Peter R.<o:p></o:p></span></p>
<p><span lang=3D"IT">I wonder if there is really a need (use case) for sect=
ion 5.3 (pure MPLS mapping) ?<o:p></o:p></span></p>
<p><span lang=3D"IT">&nbsp;Best Regards<o:p></o:p></span></p>
<p><span lang=3D"IT">Stefano <o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:<=
/span></b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&q=
uot;sans-serif&quot;"> tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.=
org]
<b>On Behalf Of </b>Peter.Meyer@Zarlink.Com<br>
<b>Sent:</b> mercoled=EC 9 febbraio 2011 16.06<br>
<b>To:</b> Roberts, Peter (Peter)<br>
<b>Cc:</b> tictoc@ietf.org; tictoc-bounces@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</span>=
<o:p></o:p></p>
<p class=3D"MsoNormal"><br>
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">Thanks.</span> <br>
<br>
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">Yes, a poor choice of words on the Annexes being &quot;profiles&=
quot;. &nbsp;We would still need to fill out the Annex info though re: port=
 addresses and the like to ensure inter-operability.</span>
<br>
<br>
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">I am fine to be neutral on performance aspects -- I would recomm=
end to indicate they are not within scope of the document.</span><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Arial Black&quot;,&quot;sans-serif&=
quot;">
</span><o:p></o:p></p>
<p><b><span style=3D"font-size:10.0pt;font-family:&quot;Arial Black&quot;,&=
quot;sans-serif&quot;">ZARLINK</span></b><b><span style=3D"font-family:&quo=
t;Arial Black&quot;,&quot;sans-serif&quot;">
</span></b><span style=3D"font-size:7.5pt;font-family:&quot;Trebuchet MS&qu=
ot;,&quot;sans-serif&quot;">Semiconductor<b><br>
Peter Meyer<i><span style=3D"color:gray"><br>
Timing &amp; Synchronization<br>
Communication Products Group</span></i></b><i><br>
Office: &#43;1-613-270-7203</i><b>&nbsp; |&nbsp; </b><i>Fax: &#43;1-613-592=
-1010</i><u><span style=3D"color:blue"><br>
</span></u></span><a href=3D"mailto:employee.name@zarlink.com"><span style=
=3D"font-size:7.5pt;font-family:&quot;Trebuchet MS&quot;,&quot;sans-serif&q=
uot;">peter.meyer@zarlink.com</span></a><span style=3D"font-size:7.5pt;font=
-family:&quot;Trebuchet MS&quot;,&quot;sans-serif&quot;">
<b>&nbsp;| </b></span><a href=3D"http://www.zarlink.com/"><span style=3D"fo=
nt-size:7.5pt;font-family:&quot;Trebuchet MS&quot;,&quot;sans-serif&quot;">=
www.zarlink.com</span></a><o:p></o:p></p>
<p style=3D"margin-bottom:12.0pt"><br>
<br>
<o:p></o:p></p>
<table class=3D"MsoNormalTable" border=3D"0" cellpadding=3D"0" width=3D"100=
%" style=3D"width:100.0%">
<tbody>
<tr>
<td width=3D"40%" valign=3D"top" style=3D"width:40.0%;padding:.75pt .75pt .=
75pt .75pt">
<p class=3D"MsoNormal"><b><span style=3D"font-size:7.5pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">&quot;Roberts, Peter (Peter)&quot; &lt;=
peter.roberts@alcatel-lucent.com&gt;</span></b><span style=3D"font-size:7.5=
pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">
</span><br>
<span style=3D"font-size:7.5pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;">Sent by: &lt;tictoc-bounces@ietf.org&gt;</span>
<o:p></o:p></p>
<p><span style=3D"font-size:7.5pt;font-family:&quot;Arial&quot;,&quot;sans-=
serif&quot;">09/02/2011 08:52 AM</span>
<o:p></o:p></p>
</td>
<td width=3D"59%" valign=3D"top" style=3D"width:59.0%;padding:.75pt .75pt .=
75pt .75pt">
<table class=3D"MsoNormalTable" border=3D"0" cellpadding=3D"0" width=3D"100=
%" style=3D"width:100.0%">
<tbody>
<tr>
<td valign=3D"top" style=3D"padding:.75pt .75pt .75pt .75pt">
<p class=3D"MsoNormal" align=3D"right" style=3D"text-align:right"><span sty=
le=3D"font-size:7.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"=
>To</span><o:p></o:p></p>
</td>
<td valign=3D"top" style=3D"padding:.75pt .75pt .75pt .75pt">
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">&quot;Bhatia, Manav (Manav)&quot; &lt;mana=
v.bhatia@alcatel-lucent.com&gt;, &quot;Peter.Meyer@Zarlink.Com&quot; &lt;Pe=
ter.Meyer@zarlink.com&gt;</span>
<o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=3D"top" style=3D"padding:.75pt .75pt .75pt .75pt">
<p class=3D"MsoNormal" align=3D"right" style=3D"text-align:right"><span sty=
le=3D"font-size:7.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"=
>cc</span><o:p></o:p></p>
</td>
<td valign=3D"top" style=3D"padding:.75pt .75pt .75pt .75pt">
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">&quot;tictoc@ietf.org&quot; &lt;tictoc@iet=
f.org&gt;</span>
<o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=3D"top" style=3D"padding:.75pt .75pt .75pt .75pt">
<p class=3D"MsoNormal" align=3D"right" style=3D"text-align:right"><span sty=
le=3D"font-size:7.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"=
>Subject</span><o:p></o:p></p>
</td>
<td valign=3D"top" style=3D"padding:.75pt .75pt .75pt .75pt">
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">Re: [TICTOC] 1588overmpls-00 / MPLS profil=
e &amp; BC</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<table class=3D"MsoNormalTable" border=3D"0" cellpadding=3D"0">
<tbody>
<tr>
<td valign=3D"top" style=3D"padding:.75pt .75pt .75pt .75pt"></td>
<td valign=3D"top" style=3D"padding:.75pt .75pt .75pt .75pt"></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p style=3D"margin-bottom:12.0pt"><br>
<br>
<br>
<tt><span style=3D"font-size:10.0pt">Peter,</span></tt><span style=3D"font-=
size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<tt>With respect to your comments on the profile, the Annexes are not profi=
les. &nbsp;They are the portions of the standard that define the rules for =
running PTP over specific lower layer protocols. &nbsp;These can then be in=
cluded or excluded from specific profiles
 that are defined. &nbsp;This draft is defining these rules for the MPLS en=
vironment. &nbsp;</tt><br>
<tt>The draft covers all the clock types but as you point out this is not a=
ll that clear. &nbsp;This can be added.</tt><br>
<tt>In addition, I don't believe the ITU-T has concluded anything about per=
formance of BC vs TC. &nbsp;They have just started studying the issue. &nbs=
p;But this draft is not making any claims about performance and as stated e=
arlier should be applicable for any of the
 clock types. &nbsp;We can review it to remove any contentious wording in r=
espect to performance.</tt><br>
<tt>Peter R.</tt><br>
<br>
<tt>&nbsp; </tt><br>
<br>
<tt>-----Original Message-----</tt><br>
<tt>From: tictoc-bounces@ietf.org [</tt></span><a href=3D"mailto:tictoc-bou=
nces@ietf.org"><tt><span style=3D"font-size:10.0pt">mailto:tictoc-bounces@i=
etf.org</span></tt></a><tt><span style=3D"font-size:10.0pt">] On Behalf Of =
Bhatia, Manav (Manav)</span></tt><span style=3D"font-size:10.0pt;font-famil=
y:&quot;Courier New&quot;"><br>
<tt>Sent: February 9, 2011 8:20 AM</tt><br>
<tt>To: Peter.Meyer@Zarlink.Com</tt><br>
<tt>Cc: tictoc@ietf.org</tt><br>
<tt>Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</tt><br>
<br>
<tt>Hi Peter,</tt><br>
<br>
<tt>Very valid comments. </tt><br>
<br>
<tt>This draft covers all clock types - TC, BC and OC. The reason it seems =
we've been concentrating on TC is because that's the clock type that requir=
es special MPLS processing.
</tt><br>
<br>
<tt>For BC's and OC's there is no special processing involved. One just nee=
ds an MPLS LSP that terminates on a BC and OC and things will just work. Ho=
wever, I get the drift of what youre saying and we can update the draft to =
explicitly state this.</tt><br>
<br>
<tt>I will let someone more knowledgeable respond to your question on wheth=
er a separate profile for MPLS is required or not. To my untrained eye it l=
ooks that we might.</tt><br>
<br>
<tt>Cheers, Manav </tt><br>
<br>
<tt>&gt; -----Original Message-----</tt><br>
<tt>&gt; From: Peter.Meyer@Zarlink.Com [</tt></span><a href=3D"mailto:Peter=
.Meyer@Zarlink.Com"><tt><span style=3D"font-size:10.0pt">mailto:Peter.Meyer=
@Zarlink.Com</span></tt></a><tt><span style=3D"font-size:10.0pt">]
</span></tt><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&q=
uot;"><br>
<tt>&gt; Sent: Wednesday, February 09, 2011 2.00 PM</tt><br>
<tt>&gt; To: Bhatia, Manav (Manav)</tt><br>
<tt>&gt; Cc: tictoc@ietf.org</tt><br>
<tt>&gt; Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</tt>=
<br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi Manav,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; A high level point is that for the pure MPLS mapping (section 5.3)=
 , I</tt><br>
<tt>&gt; wonder if what is really needed is a PTP profile for MPLS -- </tt>=
<br>
<tt>&gt; similar to</tt><br>
<tt>&gt; Annex D/E/F for IPv4/IPv6/Ethernet, respectively. &nbsp;For </tt><=
br>
<tt>&gt; example the IP &amp;</tt><br>
<tt>&gt; Ethernet profiles include other information such as the port </tt>=
<br>
<tt>&gt; addressing for</tt><br>
<tt>&gt; the unicast master table and acceptable master table. &nbsp;Withou=
t a full</tt><br>
<tt>&gt; profile, although the intermediate notes may operate in TC, </tt><=
br>
<tt>&gt; the server,</tt><br>
<tt>&gt; client and boundary nodes may not operate successfully.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Its not clear if this draft is intended to cover all clock </tt><b=
r>
<tt>&gt; types (OC, BC &amp;</tt><br>
<tt>&gt; TC) or only TC. &nbsp;There are many sections that talk only about=
 </tt><br>
<tt>&gt; TC without</tt><br>
<tt>&gt; considering OC and BC behaviour or impact. &nbsp;Is BC intended to=
 </tt><br>
<tt>&gt; be covered as</tt><br>
<tt>&gt; a Client-side OC &#43; Server-side OC model, or is BC excluded fro=
m</tt><br>
<tt>&gt; consideration in this draft? &nbsp;Perhaps this draft should be ei=
ther</tt><br>
<tt>&gt; cleaned-up to consider all clock types or should be </tt><br>
<tt>&gt; restricted to only TC</tt><br>
<tt>&gt; clock type with OC &amp; BC out of scope.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Some specific comments</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &#43; The abstract could be clarified to indicate there are three =
</tt><br>
<tt>&gt; mappings, not</tt><br>
<tt>&gt; two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS). &nbsp;I =
think the</tt><br>
<tt>&gt; third mapping may be under discussion, so perhaps this is prematur=
e.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &#43; A few places in the text the phrase &quot;proper handling of=
 </tt><br>
<tt>&gt; these packets&quot; or</tt><br>
<tt>&gt; &quot;properly handle PTP messages&quot; or &quot;perform proper &=
nbsp;</tt><br>
<tt>&gt; processing&quot; &nbsp;is used to</tt><br>
<tt>&gt; mean transparent clock. &nbsp;I would propose to remove such </tt>=
<br>
<tt>&gt; language as from</tt><br>
<tt>&gt; the ITU-T studies of timing performances of PTP one could argue th=
e</tt><br>
<tt>&gt; &quot;proper&quot; way is to implement a boundary clock. &nbsp;Whe=
re the </tt><br>
<tt>&gt; intention is to</tt><br>
<tt>&gt; aid the designer of a TC that is fine to describe the implementati=
on</tt><br>
<tt>&gt; recommendation, but not to suggest this is the way to acheive the =
best</tt><br>
<tt>&gt; performance or even the desired way to deploy PTP over MPLS.</tt><=
br>
<tt>&gt; </tt><br>
<tt>&gt; &#43; I would like to see a statement added in the document that t=
he</tt><br>
<tt>&gt; performance aspects (e.g. the phase or frequency alignment) </tt><=
br>
<tt>&gt; are outside the</tt><br>
<tt>&gt; scope of the document.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &#43; Section 6, 7, 8, 10 and 13 seems to focus only on the TC </t=
t><br>
<tt>&gt; case between</tt><br>
<tt>&gt; OC's and does not consider BC situation.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &#43; Section 12 text on checksums could be improved to indicate t=
his only</tt><br>
<tt>&gt; applies to TC and not to OC &amp; BC.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &#43; Section 16 seems to address only TC clocks and not OC or BC =
clocks.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &#43; Section 16.3 implies that the only possible way to handle PT=
P is TC,</tt><br>
<tt>&gt; excluding BC --- &quot;don't have the capability to process 1588 <=
/tt><br>
<tt>&gt; packets (e.g.</tt><br>
<tt>&gt; TC processing)&quot; and &quot; &nbsp; Non-1588-aware LSRs ignore =
the RSVP </tt><br>
<tt>&gt; 1588_PTP_LSP</tt><br>
<tt>&gt; object and just switch the MPLS packets carrying 1588 messages as =
data</tt><br>
<tt>&gt; packets and don't perform any TC processing.&quot;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Regards,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ZARLINK Semiconductor</tt><br>
<tt>&gt; Peter Meyer</tt><br>
<tt>&gt; Timing &amp; Synchronization</tt><br>
<tt>&gt; Communication Products Group</tt><br>
<tt>&gt; Office: &#43;1-613-270-7203&nbsp; |&nbsp; Fax: &#43;1-613-592-1010=
</tt><br>
<tt>&gt; peter.meyer@zarlink.com &nbsp;| </tt></span><a href=3D"www.zarlink=
.com"><tt><span style=3D"font-size:10.0pt">www.zarlink.com</span></tt></a><=
span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;Bhatia, Mana=
v &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(Manav)&quot; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;manav.bhatia@a=
lc &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; To </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;atel-lucent.com&gt=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;tictoc@ietf.org&quot; </tt><br>
<tt>&gt; &lt;tictoc@ietf.org&gt; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Sent by: &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; cc </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;tictoc-bounces=
@i &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;etf.org&gt; &nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp;Subject </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[T=
ICTOC] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</=
tt><br>
<tt>&gt; draft-ietf-tictoc-1588overmpls-00.t </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;26/01/2011 11:22 &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp;xt &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AM &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt=
><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; We've tried incorporating most of the comments that we received on=
 the</tt><br>
<tt>&gt; list. Please ping me if you think we have missed some.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Would be great if the WG can go through this and provide </tt><br>
<tt>&gt; feedback on the</tt><br>
<tt>&gt; same.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; The draft is available here:</tt><br>
<tt>&gt; </tt></span><a href=3D"http://www.ietf.org/internet-drafts/draft-i=
etf-tictoc-1588over"><tt><span style=3D"font-size:10.0pt">http://www.ietf.o=
rg/internet-drafts/draft-ietf-tictoc-1588over</span></tt></a><span style=3D=
"font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<tt>&gt; mpls-00.txt</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &gt; -----Original Message-----</tt><br>
<tt>&gt; &gt; From: tictoc-bounces@ietf.org</tt><br>
<tt>&gt; &gt; [</tt></span><a href=3D"mailto:tictoc-bounces@ietf.org"><tt><=
span style=3D"font-size:10.0pt">mailto:tictoc-bounces@ietf.org</span></tt><=
/a><tt><span style=3D"font-size:10.0pt">] On Behalf Of
</span></tt><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&q=
uot;"><br>
<tt>&gt; Internet-Drafts@ietf.org</tt><br>
<tt>&gt; &gt; Sent: Wednesday, January 26, 2011 9.30 PM</tt><br>
<tt>&gt; &gt; To: i-d-announce@ietf.org</tt><br>
<tt>&gt; &gt; Cc: tictoc@ietf.org</tt><br>
<tt>&gt; &gt; Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-0=
0.txt</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; A New Internet-Draft is available from the on-line</tt><br>
<tt>&gt; &gt; Internet-Drafts directories.</tt><br>
<tt>&gt; &gt; This draft is a work item of the Timing over IP Connection</t=
t><br>
<tt>&gt; &gt; and Transfer of Clock Working Group of the IETF.</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Title &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; : Transporting PTP messages (1588) over</tt><br>
<tt>&gt; &gt; MPLS Networks</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Author(s) &nbsp; &nb=
sp; &nbsp; : S. Davari, et al.</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Filename &nbsp; &nbs=
p; &nbsp; &nbsp;: draft-ietf-tictoc-1588overmpls-00.txt</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Pages &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; : 35</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Date &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp;: 2011-01-26</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; This document defines the method for transporting PTP </tt><b=
r>
<tt>&gt; messages (PDUs)</tt><br>
<tt>&gt; &gt; over an MPLS network to enable a proper handling of these pac=
kets</tt><br>
<tt>&gt; &gt; (e.g. implementation of Transparent Clocks (TC)) in LSRs.</tt=
><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; --</tt><br>
<tt>&gt; Manav Bhatia,</tt><br>
<tt>&gt; IP Division, Alcatel-Lucent,</tt><br>
<tt>&gt; Bangalore - India</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; _______________________________________________</tt><br>
<tt>&gt; TICTOC mailing list</tt><br>
<tt>&gt; TICTOC@ietf.org</tt><br>
<tt>&gt; </tt></span><a href=3D"https://www.ietf.org/mailman/listinfo/ticto=
c"><tt><span style=3D"font-size:10.0pt">https://www.ietf.org/mailman/listin=
fo/tictoc</span></tt></a><span style=3D"font-size:10.0pt;font-family:&quot;=
Courier New&quot;"><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ----------</tt><br>
<tt>&gt; This email is confidential and may contain information that </tt><=
br>
<tt>&gt; is privileged and</tt><br>
<tt>&gt; exempt from disclosure by law. &nbsp;If you have received it in </=
tt><br>
<tt>&gt; error, please contact</tt><br>
<tt>&gt; the sender immediately by return email and then delete it </tt><br=
>
<tt>&gt; from your system; you</tt><br>
<tt>&gt; should not copy it or disclose its contents to anyone. &nbsp;</tt>=
<br>
<tt>&gt; Emails are not secure</tt><br>
<tt>&gt; and cannot be guaranteed to be error free as they can be </tt><br>
<tt>&gt; intercepted, amended,</tt><br>
<tt>&gt; lost or destroyed, or contain viruses. &nbsp;Anyone who </tt><br>
<tt>&gt; communicates with us by email</tt><br>
<tt>&gt; is taken to accept these risks.</tt><br>
<tt>&gt; </tt><br>
<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt>TICTOC@ietf.org</tt><br>
</span><a href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><tt><span s=
tyle=3D"font-size:10.0pt">https://www.ietf.org/mailman/listinfo/tictoc</spa=
n></tt></a><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&qu=
ot;"><br>
<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt>TICTOC@ietf.org</tt><br>
</span><a href=3D"https://www.ietf.org/mailman/listinfo/tictoc"><tt><span s=
tyle=3D"font-size:10.0pt">https://www.ietf.org/mailman/listinfo/tictoc</spa=
n></tt></a><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&qu=
ot;"><br>
<br>
</span><o:p></o:p></p>
</div>
</body>
</html>

--_000_785DA01679B0C44F951747BE9CF66E6B04F3E7FCmboxtxa2vitesse_--

From ronc.ntear@gmail.com  Sat Feb 12 23:51:12 2011
Return-Path: <ronc.ntear@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 544563A6AB3; Sat, 12 Feb 2011 23:51:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0CmuU7pVFSXO; Sat, 12 Feb 2011 23:51:09 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 31A763A689A; Sat, 12 Feb 2011 23:51:08 -0800 (PST)
Received: by wwa36 with SMTP id 36so3879603wwa.13 for <multiple recipients>; Sat, 12 Feb 2011 23:51:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=LUl9JT1fapDbwFkmqWPctw5pFYAoMS3S/TdVhXfNjaM=; b=KuNDYw7DUV5WEtjRXshwd1dtf2BmjjFDINuKovMmPWnZQs6MfIx2adcIAFPCWeet79 0AipRPxn1+obMDGxx7ajyfrUp9fqTtZ6zHad4fUAnzf6VU7P4B8ACnXdLFih+XVwbP9b 6MdB3FMjXX8IQGEKMgYur+ZYzGo/wnCbsCLmE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=S0cJ1fKs+xcnmswOYoJNC9Lkrxi7yt9PlEIaOFE88i/NNlfn0GkbJpyDgJIZG9j5z4 BOovfSzUeBPnxY9bHdKSkRQbeE8DXRPJZfI6ihs9VKQktBIL+UBxrENtwPs0tbGxh6BA yyRHLHucvcFVpFWwJkvUwIAeKIaKrKh8cnoFY=
MIME-Version: 1.0
Received: by 10.216.13.194 with SMTP id b44mr2060498web.68.1297583485752; Sat, 12 Feb 2011 23:51:25 -0800 (PST)
Received: by 10.216.173.197 with HTTP; Sat, 12 Feb 2011 23:51:25 -0800 (PST)
In-Reply-To: <785DA01679B0C44F951747BE9CF66E6B04F3E7FC@mbox-txa2.vitesse.com>
References: <CA2959F3E75BA645A43E81C3B071F6320ACFEA9560@USNAVSXCHMBSC2.ndc.alcatel-lucent.com> <OF23A1DD85.5C87F3B6-ON85257832.0052BB99-85257832.0052DDFF@Zarlink.Com> <28C9B1CD4D27844E9CD8F02BFEB70564075118B097@ESESSCMS0360.eemea.ericsson.se> <6D53E9696A81554B9B2E14FF508BA7C80979D6426B@EMV35-UKDY.domain1.systemhost.net> <785DA01679B0C44F951747BE9CF66E6B04F3E7FC@mbox-txa2.vitesse.com>
Date: Sun, 13 Feb 2011 09:51:25 +0200
Message-ID: <AANLkTinwCtfCkKWFA4vmJXZGnrPx6vJEufva4L19L1JR@mail.gmail.com>
From: Ron Cohen <ronc.ntear@gmail.com>
To: Lars Ellegaard <le@vitesse.com>
Content-Type: multipart/alternative; boundary=0016e64c1bbebc15ce049c25325e
Cc: "tictoc-bounces@ietf.org" <tictoc-bounces@ietf.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 13 Feb 2011 07:51:12 -0000

--0016e64c1bbebc15ce049c25325e
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,

Here is how I see it.

There are several advantages for TC over BC it terms of implementation: you
don't need to maintain a clock, and you can implement all (most) of
operations in hardware, and as a result its much easier to upgrade equipmen=
t
to be PTP capable (see my previous post on per-port vs. per node PTP-capabl=
e
attribute). TCs also allows transport of multiple timescales with ease,
while this complicates BC considerably (This may or may not be needed in ou=
r
case though).

Hence, I see an advantage in deploying a BC on the boundary of the MPLS
domain, and implementing TCs within the MPLS domain, connecting the edge
BCs.

MPLS allows you to set a label-switched-path (LSP) which is fully
controlled: you can select hop by hop how the messages are transported,
selecting paths that support PTP at each hop (and not necessarily the
shortest path), that are symmetric (or for which asymmetry is known), that
are shared with SyncE synchronization chain (although I don't think its
necessary), etc.

MPLS advantage is that regardless of the underlying layer1/2 technology,
whether it is Ethernet, SONET, RPR etc, MPLS will allow setting these path
using the same procedures. Over an MPLS domain, this is maybe the only setu=
p
protocol suite available.

Hence MPLS will allow setting PTP MPLS LSPs through the MPLS domain TCs.

Not all features available in MPLS are relevant for PTP transport. The PTP
profile should define all this. For example, many of the MPLS protection
features should be carefully selected, in order not to introduce phase
transients in downstream slaves.

Assuming the above makes sense, there is a need to define an MPLS PTP
profile, for which the current draft is a first step. The profile may
include MPLS to PTP event propagation (i.e. failures in MPLS signaled withi=
n
PTP messages),  etc. Raw PTP over MPLS encapsulation makes sense in this
scenario too, especially as the latest draft defines signaling offset of PT=
P
header, to avoid deep packet inspection on top of MPLS, and hence supports
also new encaps  (Hence I don't understand Shahram point).

Best,
Ron


On Sat, Feb 12, 2011 at 12:06 PM, Lars Ellegaard <le@vitesse.com> wrote:

>  This would be PTPoverACHoMPLSoETH (or other link layer technologies).
>
>
>
> In my view MPLS(-TP) provides =93transport=94 of an application, which is
> behind some form of addressing (typically IP, Ethernet).
>
> Only exception are (MPLS) transport associated mechanisms like OAM.
> MPLS(-TP) does not have an addressing scheme.
>
> It would therefore be a violation of this if the PTP application (which
> requires multicast/unicast addressing) is carried directly after the labe=
l
> (even after the ACH).
>
> In other words even though it is possible, I suggest not to support
> PTPoACHoMPLS or PTPoMPLS.
>
>
>
> BR Lars
>
>
>
>
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *mike.gilson@bt.com
> *Sent:* 11 February 2011 18:54
> *To:* stefano.ruffini@ericsson.com; Peter.Meyer@Zarlink.Com;
> peter.roberts@alcatel-lucent.com
>
> *Cc:* tictoc@ietf.org; tictoc-bounces@ietf.org
> *Subject:* Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
>
> I would think the interface would be Ethernet. How many interfaces are
> there that are pure MPLS or another.
>
>
>
> Maybe someone can expand on this.
>
>
>
> Regards,
>
> *Mike*
>  ------------------------------
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Stefano Ruffini
> *Sent:* 10 February 2011 16:35
> *To:* Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)
> *Cc:* tictoc@ietf.org; tictoc-bounces@ietf.org
> *Subject:* Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
> Peter M., Peter R.
>
> I wonder if there is really a need (use case) for section 5.3 (pure MPLS
> mapping) ?
>
>  Best Regards
>
> Stefano
>
>
>  ------------------------------
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Peter.Meyer@Zarlink.Com
> *Sent:* mercoled=EC 9 febbraio 2011 16.06
> *To:* Roberts, Peter (Peter)
> *Cc:* tictoc@ietf.org; tictoc-bounces@ietf.org
> *Subject:* Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
> Thanks.
>
> Yes, a poor choice of words on the Annexes being "profiles".  We would
> still need to fill out the Annex info though re: port addresses and the l=
ike
> to ensure inter-operability.
>
> I am fine to be neutral on performance aspects -- I would recommend to
> indicate they are not within scope of the document.
>
> *ZARLINK** *Semiconductor*
> Peter Meyer
> Timing & Synchronization
> Communication Products Group**
> Office: +1-613-270-7203**  |  **Fax: +1-613-592-1010**
> *peter.meyer@zarlink.com <employee.name@zarlink.com> * | *www.zarlink.com
>
>
>
>    *"Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>*
> Sent by: <tictoc-bounces@ietf.org>
>
> 09/02/2011 08:52 AM
>
> To
>
> "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>,
> "Peter.Meyer@Zarlink.Com" <Peter.Meyer@zarlink.com>
>
> cc
>
> "tictoc@ietf.org" <tictoc@ietf.org>
>
> Subject
>
> Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
>
>
>
>
> Peter,
> With respect to your comments on the profile, the Annexes are not profile=
s.
>  They are the portions of the standard that define the rules for running =
PTP
> over specific lower layer protocols.  These can then be included or exclu=
ded
> from specific profiles that are defined.  This draft is defining these ru=
les
> for the MPLS environment.
> The draft covers all the clock types but as you point out this is not all
> that clear.  This can be added.
> In addition, I don't believe the ITU-T has concluded anything about
> performance of BC vs TC.  They have just started studying the issue.  But
> this draft is not making any claims about performance and as stated earli=
er
> should be applicable for any of the clock types.  We can review it to rem=
ove
> any contentious wording in respect to performance.
> Peter R.
>
>
>
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org<tictoc-boun=
ces@ietf.org>]
> On Behalf Of Bhatia, Manav (Manav)
> Sent: February 9, 2011 8:20 AM
> To: Peter.Meyer@Zarlink.Com
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
> Hi Peter,
>
> Very valid comments.
>
> This draft covers all clock types - TC, BC and OC. The reason it seems
> we've been concentrating on TC is because that's the clock type that
> requires special MPLS processing.
>
> For BC's and OC's there is no special processing involved. One just needs
> an MPLS LSP that terminates on a BC and OC and things will just work.
> However, I get the drift of what youre saying and we can update the draft=
 to
> explicitly state this.
>
> I will let someone more knowledgeable respond to your question on whether=
 a
> separate profile for MPLS is required or not. To my untrained eye it look=
s
> that we might.
>
> Cheers, Manav
>
> > -----Original Message-----
> > From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com<Peter.Mey=
er@Zarlink.Com>]
>
> > Sent: Wednesday, February 09, 2011 2.00 PM
> > To: Bhatia, Manav (Manav)
> > Cc: tictoc@ietf.org
> > Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
> >
> >
> > Hi Manav,
> >
> >
> > A high level point is that for the pure MPLS mapping (section 5.3) , I
> > wonder if what is really needed is a PTP profile for MPLS --
> > similar to
> > Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For
> > example the IP &
> > Ethernet profiles include other information such as the port
> > addressing for
> > the unicast master table and acceptable master table.  Without a full
> > profile, although the intermediate notes may operate in TC,
> > the server,
> > client and boundary nodes may not operate successfully.
> >
> > Its not clear if this draft is intended to cover all clock
> > types (OC, BC &
> > TC) or only TC.  There are many sections that talk only about
> > TC without
> > considering OC and BC behaviour or impact.  Is BC intended to
> > be covered as
> > a Client-side OC + Server-side OC model, or is BC excluded from
> > consideration in this draft?  Perhaps this draft should be either
> > cleaned-up to consider all clock types or should be
> > restricted to only TC
> > clock type with OC & BC out of scope.
> >
> >
> > Some specific comments
> >
> > + The abstract could be clarified to indicate there are three
> > mappings, not
> > two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
> > third mapping may be under discussion, so perhaps this is premature.
> >
> > + A few places in the text the phrase "proper handling of
> > these packets" or
> > "properly handle PTP messages" or "perform proper
> > processing"  is used to
> > mean transparent clock.  I would propose to remove such
> > language as from
> > the ITU-T studies of timing performances of PTP one could argue the
> > "proper" way is to implement a boundary clock.  Where the
> > intention is to
> > aid the designer of a TC that is fine to describe the implementation
> > recommendation, but not to suggest this is the way to acheive the best
> > performance or even the desired way to deploy PTP over MPLS.
> >
> > + I would like to see a statement added in the document that the
> > performance aspects (e.g. the phase or frequency alignment)
> > are outside the
> > scope of the document.
> >
> > + Section 6, 7, 8, 10 and 13 seems to focus only on the TC
> > case between
> > OC's and does not consider BC situation.
> >
> > + Section 12 text on checksums could be improved to indicate this only
> > applies to TC and not to OC & BC.
> >
> > + Section 16 seems to address only TC clocks and not OC or BC clocks.
> >
> > + Section 16.3 implies that the only possible way to handle PTP is TC,
> > excluding BC --- "don't have the capability to process 1588
> > packets (e.g.
> > TC processing)" and "   Non-1588-aware LSRs ignore the RSVP
> > 1588_PTP_LSP
> > object and just switch the MPLS packets carrying 1588 messages as data
> > packets and don't perform any TC processing."
> >
> >
> > Regards,
> >
> >
> > ZARLINK Semiconductor
> > Peter Meyer
> > Timing & Synchronization
> > Communication Products Group
> > Office: +1-613-270-7203  |  Fax: +1-613-592-1010
> > peter.meyer@zarlink.com  | www.zarlink.com
> >
> >
> >
> >
> >
> >              "Bhatia, Manav
> >
> >              (Manav)"
> >
> >              <manav.bhatia@alc
> >           To
> >              atel-lucent.com>          "tictoc@ietf.org"
> > <tictoc@ietf.org>
> >              Sent by:
> >           cc
> >              <tictoc-bounces@i
> >
> >              etf.org>
> >      Subject
> >                                        [TICTOC]
> >
> >
> > draft-ietf-tictoc-1588overmpls-00.t
> >              26/01/2011 11:22          xt
> >
> >              AM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi,
> >
> > We've tried incorporating most of the comments that we received on the
> > list. Please ping me if you think we have missed some.
> >
> > Would be great if the WG can go through this and provide
> > feedback on the
> > same.
> >
> > The draft is available here:
> > http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over
> > mpls-00.txt
> >
> > Cheers, Manav
> >
> > > -----Original Message-----
> > > From: tictoc-bounces@ietf.org
> > > [mailto:tictoc-bounces@ietf.org <tictoc-bounces@ietf.org>] On Behalf
> Of
> > Internet-Drafts@ietf.org
> > > Sent: Wednesday, January 26, 2011 9.30 PM
> > > To: i-d-announce@ietf.org
> > > Cc: tictoc@ietf.org
> > > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > > MPLS Networks
> > >            Author(s)       : S. Davari, et al.
> > >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> > >            Pages           : 35
> > >            Date            : 2011-01-26
> > >
> > > This document defines the method for transporting PTP
> > messages (PDUs)
> > > over an MPLS network to enable a proper handling of these packets
> > > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> > >
> >
> > Cheers, Manav
> >
> > --
> > Manav Bhatia,
> > IP Division, Alcatel-Lucent,
> > Bangalore - India
> >
> >
> > _______________________________________________
> > TICTOC mailing list
> > TICTOC@ietf.org
> > https://www.ietf.org/mailman/listinfo/tictoc
> >
> >
> >
> > ----------
> > This email is confidential and may contain information that
> > is privileged and
> > exempt from disclosure by law.  If you have received it in
> > error, please contact
> > the sender immediately by return email and then delete it
> > from your system; you
> > should not copy it or disclose its contents to anyone.
> > Emails are not secure
> > and cannot be guaranteed to be error free as they can be
> > intercepted, amended,
> > lost or destroyed, or contain viruses.  Anyone who
> > communicates with us by email
> > is taken to accept these risks.
> >
> _______________________________________________
> 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
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>

--0016e64c1bbebc15ce049c25325e
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<br><br>Here is how I see it.<br><br>There are several =
advantages for TC over BC it terms of implementation: you don&#39;t need to=
 maintain a clock, and you can implement all (most) of operations in hardwa=
re, and as a result its much easier to upgrade equipment to be PTP capable =
(see my previous post on per-port vs. per node PTP-capable attribute). TCs =
also allows transport of multiple timescales with ease, while this complica=
tes BC considerably (This may or may not be needed in our case though).<br>
=A0<br>Hence, I see an advantage in deploying a BC on the boundary of the M=
PLS domain, and implementing TCs within the MPLS domain, connecting the edg=
e BCs.<br><br>MPLS allows you to set a label-switched-path (LSP) which is f=
ully controlled: you can select hop by hop how the messages are transported=
, selecting paths that support PTP at each hop (and not necessarily the sho=
rtest path), that are symmetric (or for which asymmetry is known), that are=
 shared with SyncE synchronization chain (although I don&#39;t think its ne=
cessary), etc. <br>
<br>MPLS advantage is that regardless of the underlying layer1/2 technology=
, whether it is Ethernet, SONET, RPR etc, MPLS will allow setting these pat=
h using the same procedures. Over an MPLS domain, this is maybe the only se=
tup protocol suite available.<br>
<br>Hence MPLS will allow setting PTP MPLS LSPs through the MPLS domain TCs=
.<br><br>Not all features available in MPLS are relevant for PTP transport.=
 The PTP profile should define all this. For example, many of the MPLS prot=
ection features should be carefully selected, in order not to introduce pha=
se transients in downstream slaves. <br>
<br>Assuming the above makes sense, there is a need to define an MPLS PTP p=
rofile, for which the current draft is a first step. The profile may includ=
e MPLS to PTP event propagation (i.e. failures in MPLS signaled within PTP =
messages),=A0 etc. Raw PTP over MPLS encapsulation makes sense in this scen=
ario too, especially as the latest draft defines signaling offset of PTP he=
ader, to avoid deep packet inspection on top of MPLS, and hence supports al=
so new encaps=A0 (Hence I don&#39;t understand Shahram point). <br>
<br>Best,<br>Ron<br><br><br><div class=3D"gmail_quote">On Sat, Feb 12, 2011=
 at 12:06 PM, Lars Ellegaard <span dir=3D"ltr">&lt;<a href=3D"mailto:le@vit=
esse.com">le@vitesse.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204=
, 204, 204); padding-left: 1ex;">






<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">This would be PTPoverACHoMPLSoETH (or other link layer technologies).=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">In my view MPLS(-TP) provides =93transport=94 of an application, whic=
h is behind some form of addressing (typically IP, Ethernet).</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">Only exception are (MPLS) transport associated mechanisms like OAM. M=
PLS(-TP) does not have an addressing scheme.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">It would therefore be a violation of this if the PTP application (whi=
ch requires multicast/unicast addressing) is carried directly after the lab=
el (even after
 the ACH).</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">In other words even though it is possible, I suggest not to support P=
TPoACHoMPLS or PTPoMPLS.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">BR Lars</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">=A0</span></p>
<div>
<div style=3D"border-width: 1pt medium medium; border-style: solid none non=
e; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color=
; padding: 3pt 0cm 0cm;">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt;">From:</span></b>=
<span style=3D"font-size: 10pt;"> <a href=3D"mailto:tictoc-bounces@ietf.org=
" target=3D"_blank">tictoc-bounces@ietf.org</a> [mailto:<a href=3D"mailto:t=
ictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:mike.gilson@bt.com" target=3D"_blank"=
>mike.gilson@bt.com</a><br>
<b>Sent:</b> 11 February 2011 18:54<br>
<b>To:</b> <a href=3D"mailto:stefano.ruffini@ericsson.com" target=3D"_blank=
">stefano.ruffini@ericsson.com</a>; Peter.Meyer@Zarlink.Com; <a href=3D"mai=
lto:peter.roberts@alcatel-lucent.com" target=3D"_blank">peter.roberts@alcat=
el-lucent.com</a><div>
<div></div><div class=3D"h5"><br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a>; <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tict=
oc-bounces@ietf.org</a><br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</div><=
/div></span></p>
</div>
</div><div><div></div><div class=3D"h5">
<p class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal"><span style=3D"color: blue;">I would think the inter=
face would be Ethernet.=A0How many interfaces are there that are pure MPLS =
or another.</span></p>
<p class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal"><span style=3D"color: blue;">Maybe someone can expan=
d on this.</span></p>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt;" lang=3D"EN-GB">Rega=
rds,</span><span lang=3D"EN-GB">
</span></p>
</div>
<p><i><span style=3D"font-size: 13.5pt; font-family: &quot;Comic Sans MS&qu=
ot;; color: blue;" lang=3D"EN-GB">Mike</span></i><span lang=3D"EN-GB">
</span></p>
<div>
<div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center">
<hr size=3D"2" align=3D"center" width=3D"100%">
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><b><span style=3D"fon=
t-size: 10pt;">From:</span></b><span style=3D"font-size: 10pt;"> <a href=3D=
"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces@ietf.org<=
/a> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">ti=
ctoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Stefano Ruffini<br>
<b>Sent:</b> 10 February 2011 16:35<br>
<b>To:</b> Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a>; <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tict=
oc-bounces@ietf.org</a><br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</span>=
</p>
</div>
<p><span lang=3D"IT">Peter M., Peter R.</span></p>
<p><span lang=3D"IT">I wonder if there is really a need (use case) for sect=
ion 5.3 (pure MPLS mapping) ?</span></p>
<p><span lang=3D"IT">=A0Best Regards</span></p>
<p><span lang=3D"IT">Stefano </span></p>
<p class=3D"MsoNormal">=A0</p>
<div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center">
<hr size=3D"2" align=3D"center" width=3D"100%">
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><b><span style=3D"fon=
t-size: 10pt;">From:</span></b><span style=3D"font-size: 10pt;"> <a href=3D=
"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces@ietf.org<=
/a> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">ti=
ctoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Peter.Meyer@Zarlink.Com<br>
<b>Sent:</b> mercoled=EC 9 febbraio 2011 16.06<br>
<b>To:</b> Roberts, Peter (Peter)<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a>; <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tict=
oc-bounces@ietf.org</a><br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</span>=
</p>
<p class=3D"MsoNormal"><br>
<span style=3D"font-size: 10pt;">Thanks.</span> <br>
<br>
<span style=3D"font-size: 10pt;">Yes, a poor choice of words on the Annexes=
 being &quot;profiles&quot;. =A0We would still need to fill out the Annex i=
nfo though re: port addresses and the like to ensure inter-operability.</sp=
an>
<br>
<br>
<span style=3D"font-size: 10pt;">I am fine to be neutral on performance asp=
ects -- I would recommend to indicate they are not within scope of the docu=
ment.</span><span style=3D"font-size: 10pt;">
</span></p>
<p><b><span style=3D"font-size: 10pt;">ZARLINK</span></b><b><span>
</span></b><span style=3D"font-size: 7.5pt;">Semiconductor<b><br>
Peter Meyer<i><span style=3D"color: gray;"><br>
Timing &amp; Synchronization<br>
Communication Products Group</span></i></b><i><br>
Office: +1-613-270-7203</i><b>=A0 |=A0 </b><i>Fax: +1-613-592-1010</i><u><s=
pan style=3D"color: blue;"><br>
</span></u></span><a href=3D"mailto:employee.name@zarlink.com" target=3D"_b=
lank"><span style=3D"font-size: 7.5pt;">peter.meyer@zarlink.com</span></a><=
span style=3D"font-size: 7.5pt;">
<b>=A0| </b></span><a href=3D"http://www.zarlink.com/" target=3D"_blank"><s=
pan style=3D"font-size: 7.5pt;">www.zarlink.com</span></a></p>
<p style=3D"margin-bottom: 12pt;"><br>
<br>
</p>
<table style=3D"width: 100%;" border=3D"0" cellpadding=3D"0" width=3D"100%"=
>
<tbody>
<tr>
<td style=3D"width: 40%; padding: 0.75pt;" valign=3D"top" width=3D"40%">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 7.5pt;">&quot;Roberts, =
Peter (Peter)&quot; &lt;<a href=3D"mailto:peter.roberts@alcatel-lucent.com"=
 target=3D"_blank">peter.roberts@alcatel-lucent.com</a>&gt;</span></b><span=
 style=3D"font-size: 7.5pt;">
</span><br>
<span style=3D"font-size: 7.5pt;">Sent by: &lt;<a href=3D"mailto:tictoc-bou=
nces@ietf.org" target=3D"_blank">tictoc-bounces@ietf.org</a>&gt;</span>
</p>
<p><span style=3D"font-size: 7.5pt;">09/02/2011 08:52 AM</span>
</p>
</td>
<td style=3D"width: 59%; padding: 0.75pt;" valign=3D"top" width=3D"59%">
<table style=3D"width: 100%;" border=3D"0" cellpadding=3D"0" width=3D"100%"=
>
<tbody>
<tr>
<td style=3D"padding: 0.75pt;" valign=3D"top">
<p class=3D"MsoNormal" style=3D"text-align: right;" align=3D"right"><span s=
tyle=3D"font-size: 7.5pt;">To</span></p>
</td>
<td style=3D"padding: 0.75pt;" valign=3D"top">
<p class=3D"MsoNormal"><span style=3D"font-size: 7.5pt;">&quot;Bhatia, Mana=
v (Manav)&quot; &lt;<a href=3D"mailto:manav.bhatia@alcatel-lucent.com" targ=
et=3D"_blank">manav.bhatia@alcatel-lucent.com</a>&gt;, &quot;Peter.Meyer@Za=
rlink.Com&quot; &lt;<a href=3D"mailto:Peter.Meyer@zarlink.com" target=3D"_b=
lank">Peter.Meyer@zarlink.com</a>&gt;</span>
</p>
</td>
</tr>
<tr>
<td style=3D"padding: 0.75pt;" valign=3D"top">
<p class=3D"MsoNormal" style=3D"text-align: right;" align=3D"right"><span s=
tyle=3D"font-size: 7.5pt;">cc</span></p>
</td>
<td style=3D"padding: 0.75pt;" valign=3D"top">
<p class=3D"MsoNormal"><span style=3D"font-size: 7.5pt;">&quot;<a href=3D"m=
ailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf.org</a>&quot; &lt;<a h=
ref=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf.org</a>&gt;</s=
pan>
</p>
</td>
</tr>
<tr>
<td style=3D"padding: 0.75pt;" valign=3D"top">
<p class=3D"MsoNormal" style=3D"text-align: right;" align=3D"right"><span s=
tyle=3D"font-size: 7.5pt;">Subject</span></p>
</td>
<td style=3D"padding: 0.75pt;" valign=3D"top">
<p class=3D"MsoNormal"><span style=3D"font-size: 7.5pt;">Re: [TICTOC] 1588o=
vermpls-00 / MPLS profile &amp; BC</span></p>
</td>
</tr>
</tbody>
</table>
<p class=3D"MsoNormal">=A0</p>
<table border=3D"0" cellpadding=3D"0">
<tbody>
<tr>
<td style=3D"padding: 0.75pt;" valign=3D"top"></td>
<td style=3D"padding: 0.75pt;" valign=3D"top"></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p style=3D"margin-bottom: 12pt;"><br>
<br>
<br>
<tt><span style=3D"font-size: 10pt;">Peter,</span></tt><span style=3D"font-=
size: 10pt; font-family: &quot;Courier New&quot;;"><br>
<tt>With respect to your comments on the profile, the Annexes are not profi=
les. =A0They are the portions of the standard that define the rules for run=
ning PTP over specific lower layer protocols. =A0These can then be included=
 or excluded from specific profiles
 that are defined. =A0This draft is defining these rules for the MPLS envir=
onment. =A0</tt><br>
<tt>The draft covers all the clock types but as you point out this is not a=
ll that clear. =A0This can be added.</tt><br>
<tt>In addition, I don&#39;t believe the ITU-T has concluded anything about=
 performance of BC vs TC. =A0They have just started studying the issue. =A0=
But this draft is not making any claims about performance and as stated ear=
lier should be applicable for any of the
 clock types. =A0We can review it to remove any contentious wording in resp=
ect to performance.</tt><br>
<tt>Peter R.</tt><br>
<br>
<tt>=A0 </tt><br>
<br>
<tt>-----Original Message-----</tt><br>
<tt>From: <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tict=
oc-bounces@ietf.org</a> [</tt></span><a href=3D"mailto:tictoc-bounces@ietf.=
org" target=3D"_blank"><tt><span style=3D"font-size: 10pt;">mailto:tictoc-b=
ounces@ietf.org</span></tt></a><tt><span style=3D"font-size: 10pt;">] On Be=
half Of Bhatia, Manav (Manav)</span></tt><span style=3D"font-size: 10pt; fo=
nt-family: &quot;Courier New&quot;;"><br>

<tt>Sent: February 9, 2011 8:20 AM</tt><br>
<tt>To: Peter.Meyer@Zarlink.Com</tt><br>
<tt>Cc: <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf.or=
g</a></tt><br>
<tt>Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</tt><br>
<br>
<tt>Hi Peter,</tt><br>
<br>
<tt>Very valid comments. </tt><br>
<br>
<tt>This draft covers all clock types - TC, BC and OC. The reason it seems =
we&#39;ve been concentrating on TC is because that&#39;s the clock type tha=
t requires special MPLS processing.
</tt><br>
<br>
<tt>For BC&#39;s and OC&#39;s there is no special processing involved. One =
just needs an MPLS LSP that terminates on a BC and OC and things will just =
work. However, I get the drift of what youre saying and we can update the d=
raft to explicitly state this.</tt><br>

<br>
<tt>I will let someone more knowledgeable respond to your question on wheth=
er a separate profile for MPLS is required or not. To my untrained eye it l=
ooks that we might.</tt><br>
<br>
<tt>Cheers, Manav </tt><br>
<br>
<tt>&gt; -----Original Message-----</tt><br>
<tt>&gt; From: Peter.Meyer@Zarlink.Com [</tt></span><a href=3D"mailto:Peter=
.Meyer@Zarlink.Com" target=3D"_blank"><tt><span style=3D"font-size: 10pt;">=
mailto:Peter.Meyer@Zarlink.Com</span></tt></a><tt><span style=3D"font-size:=
 10pt;">]
</span></tt><span style=3D"font-size: 10pt; font-family: &quot;Courier New&=
quot;;"><br>
<tt>&gt; Sent: Wednesday, February 09, 2011 2.00 PM</tt><br>
<tt>&gt; To: Bhatia, Manav (Manav)</tt><br>
<tt>&gt; Cc: <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ie=
tf.org</a></tt><br>
<tt>&gt; Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</tt>=
<br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi Manav,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; A high level point is that for the pure MPLS mapping (section 5.3)=
 , I</tt><br>
<tt>&gt; wonder if what is really needed is a PTP profile for MPLS -- </tt>=
<br>
<tt>&gt; similar to</tt><br>
<tt>&gt; Annex D/E/F for IPv4/IPv6/Ethernet, respectively. =A0For </tt><br>
<tt>&gt; example the IP &amp;</tt><br>
<tt>&gt; Ethernet profiles include other information such as the port </tt>=
<br>
<tt>&gt; addressing for</tt><br>
<tt>&gt; the unicast master table and acceptable master table. =A0Without a=
 full</tt><br>
<tt>&gt; profile, although the intermediate notes may operate in TC, </tt><=
br>
<tt>&gt; the server,</tt><br>
<tt>&gt; client and boundary nodes may not operate successfully.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Its not clear if this draft is intended to cover all clock </tt><b=
r>
<tt>&gt; types (OC, BC &amp;</tt><br>
<tt>&gt; TC) or only TC. =A0There are many sections that talk only about </=
tt><br>
<tt>&gt; TC without</tt><br>
<tt>&gt; considering OC and BC behaviour or impact. =A0Is BC intended to </=
tt><br>
<tt>&gt; be covered as</tt><br>
<tt>&gt; a Client-side OC + Server-side OC model, or is BC excluded from</t=
t><br>
<tt>&gt; consideration in this draft? =A0Perhaps this draft should be eithe=
r</tt><br>
<tt>&gt; cleaned-up to consider all clock types or should be </tt><br>
<tt>&gt; restricted to only TC</tt><br>
<tt>&gt; clock type with OC &amp; BC out of scope.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Some specific comments</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + The abstract could be clarified to indicate there are three </tt=
><br>
<tt>&gt; mappings, not</tt><br>
<tt>&gt; two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS). =A0I thi=
nk the</tt><br>
<tt>&gt; third mapping may be under discussion, so perhaps this is prematur=
e.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + A few places in the text the phrase &quot;proper handling of </t=
t><br>
<tt>&gt; these packets&quot; or</tt><br>
<tt>&gt; &quot;properly handle PTP messages&quot; or &quot;perform proper =
=A0</tt><br>
<tt>&gt; processing&quot; =A0is used to</tt><br>
<tt>&gt; mean transparent clock. =A0I would propose to remove such </tt><br=
>
<tt>&gt; language as from</tt><br>
<tt>&gt; the ITU-T studies of timing performances of PTP one could argue th=
e</tt><br>
<tt>&gt; &quot;proper&quot; way is to implement a boundary clock. =A0Where =
the </tt><br>
<tt>&gt; intention is to</tt><br>
<tt>&gt; aid the designer of a TC that is fine to describe the implementati=
on</tt><br>
<tt>&gt; recommendation, but not to suggest this is the way to acheive the =
best</tt><br>
<tt>&gt; performance or even the desired way to deploy PTP over MPLS.</tt><=
br>
<tt>&gt; </tt><br>
<tt>&gt; + I would like to see a statement added in the document that the</=
tt><br>
<tt>&gt; performance aspects (e.g. the phase or frequency alignment) </tt><=
br>
<tt>&gt; are outside the</tt><br>
<tt>&gt; scope of the document.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 6, 7, 8, 10 and 13 seems to focus only on the TC </tt><b=
r>
<tt>&gt; case between</tt><br>
<tt>&gt; OC&#39;s and does not consider BC situation.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 12 text on checksums could be improved to indicate this =
only</tt><br>
<tt>&gt; applies to TC and not to OC &amp; BC.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 16 seems to address only TC clocks and not OC or BC cloc=
ks.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 16.3 implies that the only possible way to handle PTP is=
 TC,</tt><br>
<tt>&gt; excluding BC --- &quot;don&#39;t have the capability to process 15=
88 </tt><br>
<tt>&gt; packets (e.g.</tt><br>
<tt>&gt; TC processing)&quot; and &quot; =A0 Non-1588-aware LSRs ignore the=
 RSVP </tt><br>
<tt>&gt; 1588_PTP_LSP</tt><br>
<tt>&gt; object and just switch the MPLS packets carrying 1588 messages as =
data</tt><br>
<tt>&gt; packets and don&#39;t perform any TC processing.&quot;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Regards,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ZARLINK Semiconductor</tt><br>
<tt>&gt; Peter Meyer</tt><br>
<tt>&gt; Timing &amp; Synchronization</tt><br>
<tt>&gt; Communication Products Group</tt><br>
<tt>&gt; Office: +1-613-270-7203=A0 |=A0 Fax: +1-613-592-1010</tt><br>
<tt>&gt; <a href=3D"mailto:peter.meyer@zarlink.com" target=3D"_blank">peter=
.meyer@zarlink.com</a> =A0| </tt></span><a href=3D"http://www.zarlink.com" =
target=3D"_blank"><tt><span style=3D"font-size: 10pt;">www.zarlink.com</spa=
n></tt></a><span style=3D"font-size: 10pt; font-family: &quot;Courier New&q=
uot;;"><br>

<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;Bhatia, Manav =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0(Manav)&quot; =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0&lt;manav.bhatia@alc =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 To </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0<a href=3D"http://atel-lucent.com" targ=
et=3D"_blank">atel-lucent.com</a>&gt; =A0 =A0 =A0 =A0 =A0&quot;<a href=3D"m=
ailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf.org</a>&quot; </tt><br=
>
<tt>&gt; &lt;<a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ie=
tf.org</a>&gt; </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0Sent by: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 cc </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0&lt;tictoc-bounces@i =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0<a href=3D"http://etf.org" target=3D"_b=
lank">etf.org</a>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0Subject </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0[TICTOC] =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0</tt><br>
<tt>&gt; draft-ietf-tictoc-1588overmpls-00.t </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A026/01/2011 11:22 =A0 =A0 =A0 =A0 =A0xt =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0AM =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; We&#39;ve tried incorporating most of the comments that we receive=
d on the</tt><br>
<tt>&gt; list. Please ping me if you think we have missed some.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Would be great if the WG can go through this and provide </tt><br>
<tt>&gt; feedback on the</tt><br>
<tt>&gt; same.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; The draft is available here:</tt><br>
<tt>&gt; </tt></span><a href=3D"http://www.ietf.org/internet-drafts/draft-i=
etf-tictoc-1588over" target=3D"_blank"><tt><span style=3D"font-size: 10pt;"=
>http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over</span></tt>=
</a><span style=3D"font-size: 10pt; font-family: &quot;Courier New&quot;;">=
<br>

<tt>&gt; mpls-00.txt</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &gt; -----Original Message-----</tt><br>
<tt>&gt; &gt; From: <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_b=
lank">tictoc-bounces@ietf.org</a></tt><br>
<tt>&gt; &gt; [</tt></span><a href=3D"mailto:tictoc-bounces@ietf.org" targe=
t=3D"_blank"><tt><span style=3D"font-size: 10pt;">mailto:tictoc-bounces@iet=
f.org</span></tt></a><tt><span style=3D"font-size: 10pt;">] On Behalf Of
</span></tt><span style=3D"font-size: 10pt; font-family: &quot;Courier New&=
quot;;"><br>
<tt>&gt; <a href=3D"mailto:Internet-Drafts@ietf.org" target=3D"_blank">Inte=
rnet-Drafts@ietf.org</a></tt><br>
<tt>&gt; &gt; Sent: Wednesday, January 26, 2011 9.30 PM</tt><br>
<tt>&gt; &gt; To: <a href=3D"mailto:i-d-announce@ietf.org" target=3D"_blank=
">i-d-announce@ietf.org</a></tt><br>
<tt>&gt; &gt; Cc: <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tict=
oc@ietf.org</a></tt><br>
<tt>&gt; &gt; Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-0=
0.txt</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; A New Internet-Draft is available from the on-line</tt><br>
<tt>&gt; &gt; Internet-Drafts directories.</tt><br>
<tt>&gt; &gt; This draft is a work item of the Timing over IP Connection</t=
t><br>
<tt>&gt; &gt; and Transfer of Clock Working Group of the IETF.</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Transporti=
ng PTP messages (1588) over</tt><br>
<tt>&gt; &gt; MPLS Networks</tt><br>
<tt>&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : S. Davari, et =
al.</tt><br>
<tt>&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-t=
ictoc-1588overmpls-00.txt</tt><br>
<tt>&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 35</tt><br=
>
<tt>&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-01-=
26</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; This document defines the method for transporting PTP </tt><b=
r>
<tt>&gt; messages (PDUs)</tt><br>
<tt>&gt; &gt; over an MPLS network to enable a proper handling of these pac=
kets</tt><br>
<tt>&gt; &gt; (e.g. implementation of Transparent Clocks (TC)) in LSRs.</tt=
><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; --</tt><br>
<tt>&gt; Manav Bhatia,</tt><br>
<tt>&gt; IP Division, Alcatel-Lucent,</tt><br>
<tt>&gt; Bangalore - India</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; _______________________________________________</tt><br>
<tt>&gt; TICTOC mailing list</tt><br>
<tt>&gt; <a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.o=
rg</a></tt><br>
<tt>&gt; </tt></span><a href=3D"https://www.ietf.org/mailman/listinfo/ticto=
c" target=3D"_blank"><tt><span style=3D"font-size: 10pt;">https://www.ietf.=
org/mailman/listinfo/tictoc</span></tt></a><span style=3D"font-size: 10pt; =
font-family: &quot;Courier New&quot;;"><br>

<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ----------</tt><br>
<tt>&gt; This email is confidential and may contain information that </tt><=
br>
<tt>&gt; is privileged and</tt><br>
<tt>&gt; exempt from disclosure by law. =A0If you have received it in </tt>=
<br>
<tt>&gt; error, please contact</tt><br>
<tt>&gt; the sender immediately by return email and then delete it </tt><br=
>
<tt>&gt; from your system; you</tt><br>
<tt>&gt; should not copy it or disclose its contents to anyone. =A0</tt><br=
>
<tt>&gt; Emails are not secure</tt><br>
<tt>&gt; and cannot be guaranteed to be error free as they can be </tt><br>
<tt>&gt; intercepted, amended,</tt><br>
<tt>&gt; lost or destroyed, or contain viruses. =A0Anyone who </tt><br>
<tt>&gt; communicates with us by email</tt><br>
<tt>&gt; is taken to accept these risks.</tt><br>
<tt>&gt; </tt><br>
<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt><a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a=
></tt><br>
</span><a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_=
blank"><tt><span style=3D"font-size: 10pt;">https://www.ietf.org/mailman/li=
stinfo/tictoc</span></tt></a><span style=3D"font-size: 10pt; font-family: &=
quot;Courier New&quot;;"><br>

<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt><a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a=
></tt><br>
</span><a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_=
blank"><tt><span style=3D"font-size: 10pt;">https://www.ietf.org/mailman/li=
stinfo/tictoc</span></tt></a><span style=3D"font-size: 10pt; font-family: &=
quot;Courier New&quot;;"><br>

<br>
</span></p>
</div></div></div>
</div>

<br>_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
<br></blockquote></div><br><div style=3D"visibility: hidden; left: -5000px;=
 position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-=
top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size:=
 10px; text-align: left; line-height: 130%;" id=3D"avg_ls_inline_popup">
</div></div>

--0016e64c1bbebc15ce049c25325e--

From sebastien.jobert@orange-ftgroup.com  Sun Feb 13 05:05:59 2011
Return-Path: <sebastien.jobert@orange-ftgroup.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60BE83A6981; Sun, 13 Feb 2011 05:05:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gpVDY-Asjort; Sun, 13 Feb 2011 05:05:44 -0800 (PST)
Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id 3B0F93A69D6; Sun, 13 Feb 2011 05:05:43 -0800 (PST)
Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 80CBA6C0005; Sun, 13 Feb 2011 14:06:32 +0100 (CET)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id 6673E6C0003; Sun, 13 Feb 2011 14:06:32 +0100 (CET)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 13 Feb 2011 14:06:02 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBCB7E.C323517F"
Date: Sun, 13 Feb 2011 14:04:19 +0100
Message-ID: <AFC377AFCC0FBD4DABE49F4B81EC4F1A02485667@ftrdmel1>
In-Reply-To: <AANLkTinwCtfCkKWFA4vmJXZGnrPx6vJEufva4L19L1JR@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [TICTOC] 1588overmpls-00 / MPLS profile & BC
Thread-Index: AcvLUusUxIFYlqXjTp6hVFlFpSAzqwAKtAaQ
References: <CA2959F3E75BA645A43E81C3B071F6320ACFEA9560@USNAVSXCHMBSC2.ndc.alcatel-lucent.com><OF23A1DD85.5C87F3B6-ON85257832.0052BB99-85257832.0052DDFF@Zarlink.Com><28C9B1CD4D27844E9CD8F02BFEB70564075118B097@ESESSCMS0360.eemea.ericsson.se><6D53E9696A81554B9B2E14FF508BA7C80979D6426B@EMV35-UKDY.domain1.systemhost.net><785DA01679B0C44F951747BE9CF66E6B04F3E7FC@mbox-txa2.vitesse.com> <AANLkTinwCtfCkKWFA4vmJXZGnrPx6vJEufva4L19L1JR@mail.gmail.com>
From: <sebastien.jobert@orange-ftgroup.com>
To: <ronc.ntear@gmail.com>, <le@vitesse.com>
X-OriginalArrivalTime: 13 Feb 2011 13:06:02.0203 (UTC) FILETIME=[C3D512B0:01CBCB7E]
Cc: tictoc-bounces@ietf.org, tictoc@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 13 Feb 2011 13:05:59 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBCB7E.C323517F
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Ron,

=20

Interesting view. As far as I understand, it sounds however a bit =
misaligned with the on-going work at ITU-T.

=20

Just a quick question for my clarification: how do you manage the case =
when another transport technology (e.g. Ethernet) is used between two =
MPLS nodes if only an "MPLS mapping" is considered? (I understand that =
it may happen within an MPLS domain). The two MPLS nodes may even not be =
aware that there is something in the middle.

=20

Thanks.

=20

BR,

=20

S=E9bastien

=20

De : tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] De la part =
de Ron Cohen
Envoy=E9 : dimanche 13 f=E9vrier 2011 08:51
=C0 : Lars Ellegaard
Cc : tictoc-bounces@ietf.org; tictoc@ietf.org
Objet : Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

=20

Hi,

Here is how I see it.

There are several advantages for TC over BC it terms of implementation: =
you don't need to maintain a clock, and you can implement all (most) of =
operations in hardware, and as a result its much easier to upgrade =
equipment to be PTP capable (see my previous post on per-port vs. per =
node PTP-capable attribute). TCs also allows transport of multiple =
timescales with ease, while this complicates BC considerably (This may =
or may not be needed in our case though).
=20
Hence, I see an advantage in deploying a BC on the boundary of the MPLS =
domain, and implementing TCs within the MPLS domain, connecting the edge =
BCs.

MPLS allows you to set a label-switched-path (LSP) which is fully =
controlled: you can select hop by hop how the messages are transported, =
selecting paths that support PTP at each hop (and not necessarily the =
shortest path), that are symmetric (or for which asymmetry is known), =
that are shared with SyncE synchronization chain (although I don't think =
its necessary), etc.=20

MPLS advantage is that regardless of the underlying layer1/2 technology, =
whether it is Ethernet, SONET, RPR etc, MPLS will allow setting these =
path using the same procedures. Over an MPLS domain, this is maybe the =
only setup protocol suite available.

Hence MPLS will allow setting PTP MPLS LSPs through the MPLS domain TCs.

Not all features available in MPLS are relevant for PTP transport. The =
PTP profile should define all this. For example, many of the MPLS =
protection features should be carefully selected, in order not to =
introduce phase transients in downstream slaves.=20

Assuming the above makes sense, there is a need to define an MPLS PTP =
profile, for which the current draft is a first step. The profile may =
include MPLS to PTP event propagation (i.e. failures in MPLS signaled =
within PTP messages),  etc. Raw PTP over MPLS encapsulation makes sense =
in this scenario too, especially as the latest draft defines signaling =
offset of PTP header, to avoid deep packet inspection on top of MPLS, =
and hence supports also new encaps  (Hence I don't understand Shahram =
point).=20

Best,
Ron



On Sat, Feb 12, 2011 at 12:06 PM, Lars Ellegaard <le@vitesse.com> wrote:

This would be PTPoverACHoMPLSoETH (or other link layer technologies).

=20

In my view MPLS(-TP) provides "transport" of an application, which is =
behind some form of addressing (typically IP, Ethernet).

Only exception are (MPLS) transport associated mechanisms like OAM. =
MPLS(-TP) does not have an addressing scheme.

It would therefore be a violation of this if the PTP application (which =
requires multicast/unicast addressing) is carried directly after the =
label (even after the ACH).

In other words even though it is possible, I suggest not to support =
PTPoACHoMPLS or PTPoMPLS.

=20

BR Lars

=20

=20

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of mike.gilson@bt.com
Sent: 11 February 2011 18:54
To: stefano.ruffini@ericsson.com; Peter.Meyer@Zarlink.Com; =
peter.roberts@alcatel-lucent.com


Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

=20

I would think the interface would be Ethernet. How many interfaces are =
there that are pure MPLS or another.

=20

Maybe someone can expand on this.

=20

Regards,=20

Mike=20

________________________________

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Stefano Ruffini
Sent: 10 February 2011 16:35
To: Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Peter M., Peter R.

I wonder if there is really a need (use case) for section 5.3 (pure MPLS =
mapping) ?

 Best Regards

Stefano=20

=20

________________________________

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Peter.Meyer@Zarlink.Com
Sent: mercoled=EC 9 febbraio 2011 16.06
To: Roberts, Peter (Peter)
Cc: tictoc@ietf.org; tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC


Thanks.=20

Yes, a poor choice of words on the Annexes being "profiles".  We would =
still need to fill out the Annex info though re: port addresses and the =
like to ensure inter-operability.=20

I am fine to be neutral on performance aspects -- I would recommend to =
indicate they are not within scope of the document.=20

ZARLINK Semiconductor
Peter Meyer
Timing & Synchronization
Communication Products Group
Office: +1-613-270-7203  |  Fax: +1-613-592-1010
peter.meyer@zarlink.com <mailto:employee.name@zarlink.com>   | =
www.zarlink.com <http://www.zarlink.com/>=20

=20

"Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>=20
Sent by: <tictoc-bounces@ietf.org>=20

09/02/2011 08:52 AM=20

To

"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, =
"Peter.Meyer@Zarlink.Com" <Peter.Meyer@zarlink.com>=20

cc

"tictoc@ietf.org" <tictoc@ietf.org>=20

Subject

Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

=20

	=09




Peter,
With respect to your comments on the profile, the Annexes are not =
profiles.  They are the portions of the standard that define the rules =
for running PTP over specific lower layer protocols.  These can then be =
included or excluded from specific profiles that are defined.  This =
draft is defining these rules for the MPLS environment. =20
The draft covers all the clock types but as you point out this is not =
all that clear.  This can be added.
In addition, I don't believe the ITU-T has concluded anything about =
performance of BC vs TC.  They have just started studying the issue.  =
But this draft is not making any claims about performance and as stated =
earlier should be applicable for any of the clock types.  We can review =
it to remove any contentious wording in respect to performance.
Peter R.

 =20

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org =
<mailto:tictoc-bounces@ietf.org> ] On Behalf Of Bhatia, Manav (Manav)
Sent: February 9, 2011 8:20 AM
To: Peter.Meyer@Zarlink.Com
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC

Hi Peter,

Very valid comments.=20

This draft covers all clock types - TC, BC and OC. The reason it seems =
we've been concentrating on TC is because that's the clock type that =
requires special MPLS processing.=20

For BC's and OC's there is no special processing involved. One just =
needs an MPLS LSP that terminates on a BC and OC and things will just =
work. However, I get the drift of what youre saying and we can update =
the draft to explicitly state this.

I will let someone more knowledgeable respond to your question on =
whether a separate profile for MPLS is required or not. To my untrained =
eye it looks that we might.

Cheers, Manav=20

> -----Original Message-----
> From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com =
<mailto:Peter.Meyer@Zarlink.Com> ]=20
> Sent: Wednesday, February 09, 2011 2.00 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>=20
>=20
> Hi Manav,
>=20
>=20
> A high level point is that for the pure MPLS mapping (section 5.3) , I
> wonder if what is really needed is a PTP profile for MPLS --=20
> similar to
> Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For=20
> example the IP &
> Ethernet profiles include other information such as the port=20
> addressing for
> the unicast master table and acceptable master table.  Without a full
> profile, although the intermediate notes may operate in TC,=20
> the server,
> client and boundary nodes may not operate successfully.
>=20
> Its not clear if this draft is intended to cover all clock=20
> types (OC, BC &
> TC) or only TC.  There are many sections that talk only about=20
> TC without
> considering OC and BC behaviour or impact.  Is BC intended to=20
> be covered as
> a Client-side OC + Server-side OC model, or is BC excluded from
> consideration in this draft?  Perhaps this draft should be either
> cleaned-up to consider all clock types or should be=20
> restricted to only TC
> clock type with OC & BC out of scope.
>=20
>=20
> Some specific comments
>=20
> + The abstract could be clarified to indicate there are three=20
> mappings, not
> two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
> third mapping may be under discussion, so perhaps this is premature.
>=20
> + A few places in the text the phrase "proper handling of=20
> these packets" or
> "properly handle PTP messages" or "perform proper =20
> processing"  is used to
> mean transparent clock.  I would propose to remove such=20
> language as from
> the ITU-T studies of timing performances of PTP one could argue the
> "proper" way is to implement a boundary clock.  Where the=20
> intention is to
> aid the designer of a TC that is fine to describe the implementation
> recommendation, but not to suggest this is the way to acheive the best
> performance or even the desired way to deploy PTP over MPLS.
>=20
> + I would like to see a statement added in the document that the
> performance aspects (e.g. the phase or frequency alignment)=20
> are outside the
> scope of the document.
>=20
> + Section 6, 7, 8, 10 and 13 seems to focus only on the TC=20
> case between
> OC's and does not consider BC situation.
>=20
> + Section 12 text on checksums could be improved to indicate this only
> applies to TC and not to OC & BC.
>=20
> + Section 16 seems to address only TC clocks and not OC or BC clocks.
>=20
> + Section 16.3 implies that the only possible way to handle PTP is TC,
> excluding BC --- "don't have the capability to process 1588=20
> packets (e.g.
> TC processing)" and "   Non-1588-aware LSRs ignore the RSVP=20
> 1588_PTP_LSP
> object and just switch the MPLS packets carrying 1588 messages as data
> packets and don't perform any TC processing."
>=20
>=20
> Regards,
>=20
>=20
> ZARLINK Semiconductor
> Peter Meyer
> Timing & Synchronization
> Communication Products Group
> Office: +1-613-270-7203  |  Fax: +1-613-592-1010
> peter.meyer@zarlink.com  | www.zarlink.com <http://www.zarlink.com>=20
>=20
>=20
>=20
>                                                              =20
>             =20
>              "Bhatia, Manav                                  =20
>             =20
>              (Manav)"                                        =20
>             =20
>              <manav.bhatia@alc                               =20
>           To=20
>              atel-lucent.com>          "tictoc@ietf.org"=20
> <tictoc@ietf.org>=20
>              Sent by:                                        =20
>           cc=20
>              <tictoc-bounces@i                               =20
>             =20
>              etf.org>                                        =20
>      Subject=20
>                                        [TICTOC]              =20
>             =20
>                                       =20
> draft-ietf-tictoc-1588overmpls-00.t=20
>              26/01/2011 11:22          xt                    =20
>             =20
>              AM                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>                                                              =20
>             =20
>=20
>=20
>=20
>=20
> Hi,
>=20
> We've tried incorporating most of the comments that we received on the
> list. Please ping me if you think we have missed some.
>=20
> Would be great if the WG can go through this and provide=20
> feedback on the
> same.
>=20
> The draft is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over =
<http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over>=20
> mpls-00.txt
>=20
> Cheers, Manav
>=20
> > -----Original Message-----
> > From: tictoc-bounces@ietf.org
> > [mailto:tictoc-bounces@ietf.org <mailto:tictoc-bounces@ietf.org> ] =
On Behalf Of=20
> Internet-Drafts@ietf.org
> > Sent: Wednesday, January 26, 2011 9.30 PM
> > To: i-d-announce@ietf.org
> > Cc: tictoc@ietf.org
> > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > MPLS Networks
> >            Author(s)       : S. Davari, et al.
> >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> >            Pages           : 35
> >            Date            : 2011-01-26
> >
> > This document defines the method for transporting PTP=20
> messages (PDUs)
> > over an MPLS network to enable a proper handling of these packets
> > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> >
>=20
> Cheers, Manav
>=20
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc =
<https://www.ietf.org/mailman/listinfo/tictoc>=20
>=20
>=20
>=20
> ----------
> This email is confidential and may contain information that=20
> is privileged and
> exempt from disclosure by law.  If you have received it in=20
> error, please contact
> the sender immediately by return email and then delete it=20
> from your system; you
> should not copy it or disclose its contents to anyone. =20
> Emails are not secure
> and cannot be guaranteed to be error free as they can be=20
> intercepted, amended,
> lost or destroyed, or contain viruses.  Anyone who=20
> communicates with us by email
> is taken to accept these risks.
>=20
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc =
<https://www.ietf.org/mailman/listinfo/tictoc>=20
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc =
<https://www.ietf.org/mailman/listinfo/tictoc>=20


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc

=20


------_=_NextPart_001_01CBCB7E.C323517F
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Ron,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Interesting view. As far as I understand, it sounds =
however a
bit misaligned with the on-going work at ITU-T.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Just a quick question for my clarification: how do you =
manage the
case when another transport technology (e.g. Ethernet) is used between =
two MPLS
nodes if only an &#8220;MPLS mapping&#8221; is considered? (I understand =
that
it may happen within an MPLS domain). The two MPLS nodes may even not be =
aware
that there is something in the middle.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>BR,<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>S=E9bastien<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</s=
pan></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] <b>De la part =
de</b>
Ron Cohen<br>
<b>Envoy=E9&nbsp;:</b> dimanche 13 f=E9vrier 2011 08:51<br>
<b>=C0&nbsp;:</b> Lars Ellegaard<br>
<b>Cc&nbsp;:</b> tictoc-bounces@ietf.org; tictoc@ietf.org<br>
<b>Objet&nbsp;:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC<o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Hi,<br>
<br>
Here is how I see it.<br>
<br>
There are several advantages for TC over BC it terms of implementation: =
you
don't need to maintain a clock, and you can implement all (most) of =
operations
in hardware, and as a result its much easier to upgrade equipment to be =
PTP
capable (see my previous post on per-port vs. per node PTP-capable =
attribute).
TCs also allows transport of multiple timescales with ease, while this
complicates BC considerably (This may or may not be needed in our case =
though).<br>
&nbsp;<br>
Hence, I see an advantage in deploying a BC on the boundary of the MPLS =
domain,
and implementing TCs within the MPLS domain, connecting the edge =
BCs.<br>
<br>
MPLS allows you to set a label-switched-path (LSP) which is fully =
controlled:
you can select hop by hop how the messages are transported, selecting =
paths
that support PTP at each hop (and not necessarily the shortest path), =
that are
symmetric (or for which asymmetry is known), that are shared with SyncE
synchronization chain (although I don't think its necessary), etc. <br>
<br>
MPLS advantage is that regardless of the underlying layer1/2 technology,
whether it is Ethernet, SONET, RPR etc, MPLS will allow setting these =
path
using the same procedures. Over an MPLS domain, this is maybe the only =
setup
protocol suite available.<br>
<br>
Hence MPLS will allow setting PTP MPLS LSPs through the MPLS domain =
TCs.<br>
<br>
Not all features available in MPLS are relevant for PTP transport. The =
PTP
profile should define all this. For example, many of the MPLS protection
features should be carefully selected, in order not to introduce phase
transients in downstream slaves. <br>
<br>
Assuming the above makes sense, there is a need to define an MPLS PTP =
profile,
for which the current draft is a first step. The profile may include =
MPLS to
PTP event propagation (i.e. failures in MPLS signaled within PTP
messages),&nbsp; etc. Raw PTP over MPLS encapsulation makes sense in =
this
scenario too, especially as the latest draft defines signaling offset of =
PTP
header, to avoid deep packet inspection on top of MPLS, and hence =
supports also
new encaps&nbsp; (Hence I don't understand Shahram point). <br>
<br>
Best,<br>
Ron<br>
<br>
<o:p></o:p></p>

<div>

<p class=3DMsoNormal>On Sat, Feb 12, 2011 at 12:06 PM, Lars Ellegaard =
&lt;<a
href=3D"mailto:le@vitesse.com">le@vitesse.com</a>&gt; =
wrote:<o:p></o:p></p>

<div>

<div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>This would be
PTPoverACHoMPLSoETH (or other link layer technologies).</span><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>In my view =
MPLS(-TP) provides
&#8220;transport&#8221; of an application, which is behind some form of
addressing (typically IP, Ethernet).</span><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>Only exception are =
(MPLS)
transport associated mechanisms like OAM. MPLS(-TP) does not have an =
addressing
scheme.</span><span lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>It would therefore =
be a
violation of this if the PTP application (which requires =
multicast/unicast
addressing) is carried directly after the label (even after the =
ACH).</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>In other words =
even though it
is possible, I suggest not to support PTPoACHoMPLS or =
PTPoMPLS.</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>BR =
Lars</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><span
lang=3DEN-US><o:p></o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid windowtext =
1.0pt;padding:3.0pt 0cm 0cm 0cm;
border-color:-moz-use-text-color -moz-use-text-color'>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
lang=3DEN-US style=3D'font-size:10.0pt'>From:</span></b><span =
lang=3DEN-US
style=3D'font-size:10.0pt'> <a href=3D"mailto:tictoc-bounces@ietf.org"
target=3D"_blank">tictoc-bounces@ietf.org</a> [mailto:<a
href=3D"mailto:tictoc-bounces@ietf.org" =
target=3D"_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:mike.gilson@bt.com" =
target=3D"_blank">mike.gilson@bt.com</a><br>
<b>Sent:</b> 11 February 2011 18:54<br>
<b>To:</b> <a href=3D"mailto:stefano.ruffini@ericsson.com" =
target=3D"_blank">stefano.ruffini@ericsson.com</a>;
Peter.Meyer@Zarlink.Com; <a =
href=3D"mailto:peter.roberts@alcatel-lucent.com"
target=3D"_blank">peter.roberts@alcatel-lucent.com</a><o:p></o:p></span><=
/p>

<div>

<div>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.0pt'><br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" =
target=3D"_blank">tictoc@ietf.org</a>;
<a href=3D"mailto:tictoc-bounces@ietf.org" =
target=3D"_blank">tictoc-bounces@ietf.org</a><br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC<o:p></o:p></span></p>

</div>

</div>

</div>

</div>

<div>

<div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'color:blue'>I would think the interface would be
Ethernet.&nbsp;How many interfaces are there that are pure MPLS or =
another.</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US style=3D'color:blue'>Maybe someone can expand on =
this.</span><span
lang=3DEN-US><o:p></o:p></span></p>

<div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-GB style=3D'font-size:10.0pt'>Regards,</span><span =
lang=3DEN-GB> </span><span
lang=3DEN-US><o:p></o:p></span></p>

</div>

<p><i><span lang=3DEN-GB style=3D'font-size:13.5pt;font-family:"Comic =
Sans MS";
color:blue'>Mike</span></i><span lang=3DEN-GB> </span><span =
lang=3DEN-US><o:p></o:p></span></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span =
lang=3DEN-US>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><b><span
lang=3DEN-US style=3D'font-size:10.0pt'>From:</span></b><span =
lang=3DEN-US
style=3D'font-size:10.0pt'> <a href=3D"mailto:tictoc-bounces@ietf.org"
target=3D"_blank">tictoc-bounces@ietf.org</a> [mailto:<a
href=3D"mailto:tictoc-bounces@ietf.org" =
target=3D"_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Stefano Ruffini<br>
<b>Sent:</b> 10 February 2011 16:35<br>
<b>To:</b> Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" =
target=3D"_blank">tictoc@ietf.org</a>;
<a href=3D"mailto:tictoc-bounces@ietf.org" =
target=3D"_blank">tictoc-bounces@ietf.org</a><br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC</span><span
lang=3DEN-US><o:p></o:p></span></p>

</div>

<p><span lang=3DIT>Peter M., Peter R.</span><span =
lang=3DEN-US><o:p></o:p></span></p>

<p><span lang=3DIT>I wonder if there is really a need (use case) for =
section 5.3
(pure MPLS mapping) ?</span><span lang=3DEN-US><o:p></o:p></span></p>

<p><span lang=3DIT>&nbsp;Best Regards</span><span =
lang=3DEN-US><o:p></o:p></span></p>

<p><span lang=3DIT>Stefano </span><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US>&nbsp;<o:p></o:p></span></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span =
lang=3DEN-US>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><b><span
lang=3DEN-US style=3D'font-size:10.0pt'>From:</span></b><span =
lang=3DEN-US
style=3D'font-size:10.0pt'> <a href=3D"mailto:tictoc-bounces@ietf.org"
target=3D"_blank">tictoc-bounces@ietf.org</a> [mailto:<a
href=3D"mailto:tictoc-bounces@ietf.org" =
target=3D"_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Peter.Meyer@Zarlink.Com<br>
<b>Sent:</b> mercoled=EC 9 febbraio 2011 16.06<br>
<b>To:</b> Roberts, Peter (Peter)<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" =
target=3D"_blank">tictoc@ietf.org</a>;
<a href=3D"mailto:tictoc-bounces@ietf.org" =
target=3D"_blank">tictoc-bounces@ietf.org</a><br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=3DEN-US><br>
</span><span lang=3DEN-US style=3D'font-size:10.0pt'>Thanks.</span><span
lang=3DEN-US> <br>
<br>
</span><span lang=3DEN-US style=3D'font-size:10.0pt'>Yes, a poor choice =
of words on
the Annexes being &quot;profiles&quot;. &nbsp;We would still need to =
fill out
the Annex info though re: port addresses and the like to ensure
inter-operability.</span><span lang=3DEN-US> <br>
<br>
</span><span lang=3DEN-US style=3D'font-size:10.0pt'>I am fine to be =
neutral on
performance aspects -- I would recommend to indicate they are not within =
scope
of the document. </span><span lang=3DEN-US><o:p></o:p></span></p>

<p><b><span lang=3DEN-US =
style=3D'font-size:10.0pt'>ZARLINK</span></b><b><span
lang=3DEN-US> </span></b><span lang=3DEN-US =
style=3D'font-size:7.5pt'>Semiconductor<b><br>
Peter Meyer<i><span style=3D'color:gray'><br>
Timing &amp; Synchronization<br>
Communication Products Group</span></i></b><i><br>
Office: +1-613-270-7203</i><b>&nbsp; |&nbsp; </b><i>Fax: =
+1-613-592-1010</i><u><span
style=3D'color:blue'><br>
</span></u></span><span lang=3DEN-US><a =
href=3D"mailto:employee.name@zarlink.com"
target=3D"_blank"><span =
style=3D'font-size:7.5pt'>peter.meyer@zarlink.com</span></a></span><span
lang=3DEN-US style=3D'font-size:7.5pt'> <b>&nbsp;| </b></span><span =
lang=3DEN-US><a
href=3D"http://www.zarlink.com/" target=3D"_blank"><span =
style=3D'font-size:7.5pt'>www.zarlink.com</span></a><o:p></o:p></span></p=
>

<p style=3D'margin-bottom:12.0pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%"
 style=3D'width:100.0%'>
 <tr>
  <td width=3D"40%" valign=3Dtop style=3D'width:40.0%;padding:.75pt =
.75pt .75pt .75pt'>
  <p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
  style=3D'font-size:7.5pt'>&quot;Roberts, Peter (Peter)&quot; &lt;<a
  href=3D"mailto:peter.roberts@alcatel-lucent.com" =
target=3D"_blank">peter.roberts@alcatel-lucent.com</a>&gt;</span></b><spa=
n
  style=3D'font-size:7.5pt'> </span><br>
  <span style=3D'font-size:7.5pt'>Sent by: &lt;<a
  href=3D"mailto:tictoc-bounces@ietf.org" =
target=3D"_blank">tictoc-bounces@ietf.org</a>&gt;</span>
  <o:p></o:p></p>
  <p><span style=3D'font-size:7.5pt'>09/02/2011 08:52 AM</span> =
<o:p></o:p></p>
  </td>
  <td width=3D"59%" valign=3Dtop style=3D'width:59.0%;padding:.75pt =
.75pt .75pt .75pt'>
  <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 =
width=3D"100%"
   style=3D'width:100.0%'>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:
    auto;text-align:right'><span =
style=3D'font-size:7.5pt'>To</span><o:p></o:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:
    auto'><span style=3D'font-size:7.5pt'>&quot;Bhatia, Manav =
(Manav)&quot; &lt;<a
    href=3D"mailto:manav.bhatia@alcatel-lucent.com" =
target=3D"_blank">manav.bhatia@alcatel-lucent.com</a>&gt;,
    &quot;Peter.Meyer@Zarlink.Com&quot; &lt;<a
    href=3D"mailto:Peter.Meyer@zarlink.com" =
target=3D"_blank">Peter.Meyer@zarlink.com</a>&gt;</span>
    <o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:
    auto;text-align:right'><span =
style=3D'font-size:7.5pt'>cc</span><o:p></o:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:
    auto'><span style=3D'font-size:7.5pt'>&quot;<a =
href=3D"mailto:tictoc@ietf.org"
    target=3D"_blank">tictoc@ietf.org</a>&quot; &lt;<a
    href=3D"mailto:tictoc@ietf.org" =
target=3D"_blank">tictoc@ietf.org</a>&gt;</span>
    <o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:
    auto;text-align:right'><span =
style=3D'font-size:7.5pt'>Subject</span><o:p></o:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:
    auto'><span style=3D'font-size:7.5pt'>Re: [TICTOC] 1588overmpls-00 / =
MPLS
    profile &amp; BC</span><o:p></o:p></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p>
  <table class=3DMsoNormalTable border=3D0 cellpadding=3D0>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td>
   </tr>
  </table>
  </td>
 </tr>
</table>

<p style=3D'margin-bottom:12.0pt'><span lang=3DEN-US><br>
<br>
<br>
</span><tt><span lang=3DEN-US =
style=3D'font-size:10.0pt'>Peter,</span></tt><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>With respect to your comments on the profile, the Annexes are not =
profiles.
&nbsp;They are the portions of the standard that define the rules for =
running
PTP over specific lower layer protocols. &nbsp;These can then be =
included or
excluded from specific profiles that are defined. &nbsp;This draft is =
defining
these rules for the MPLS environment. &nbsp;</tt><br>
<tt>The draft covers all the clock types but as you point out this is =
not all
that clear. &nbsp;This can be added.</tt><br>
<tt>In addition, I don't believe the ITU-T has concluded anything about =
performance
of BC vs TC. &nbsp;They have just started studying the issue. &nbsp;But =
this
draft is not making any claims about performance and as stated earlier =
should
be applicable for any of the clock types. &nbsp;We can review it to =
remove any
contentious wording in respect to performance.</tt><br>
<tt>Peter R.</tt><br>
<br>
<tt>&nbsp; </tt><br>
<br>
<tt>-----Original Message-----</tt><br>
<tt>From: <a href=3D"mailto:tictoc-bounces@ietf.org" =
target=3D"_blank">tictoc-bounces@ietf.org</a>
[</tt></span><span lang=3DEN-US><a =
href=3D"mailto:tictoc-bounces@ietf.org"
target=3D"_blank"><tt><span =
style=3D'font-size:10.0pt'>mailto:tictoc-bounces@ietf.org</span></tt></a>=
</span><tt><span
lang=3DEN-US style=3D'font-size:10.0pt'>] On Behalf Of Bhatia, Manav =
(Manav)</span></tt><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>Sent: February 9, 2011 8:20 AM</tt><br>
<tt>To: Peter.Meyer@Zarlink.Com</tt><br>
<tt>Cc: <a href=3D"mailto:tictoc@ietf.org" =
target=3D"_blank">tictoc@ietf.org</a></tt><br>
<tt>Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC</tt><br>
<br>
<tt>Hi Peter,</tt><br>
<br>
<tt>Very valid comments. </tt><br>
<br>
<tt>This draft covers all clock types - TC, BC and OC. The reason it =
seems
we've been concentrating on TC is because that's the clock type that =
requires
special MPLS processing. </tt><br>
<br>
<tt>For BC's and OC's there is no special processing involved. One just =
needs
an MPLS LSP that terminates on a BC and OC and things will just work. =
However,
I get the drift of what youre saying and we can update the draft to =
explicitly
state this.</tt><br>
<br>
<tt>I will let someone more knowledgeable respond to your question on =
whether a
separate profile for MPLS is required or not. To my untrained eye it =
looks that
we might.</tt><br>
<br>
<tt>Cheers, Manav </tt><br>
<br>
<tt>&gt; -----Original Message-----</tt><br>
<tt>&gt; From: Peter.Meyer@Zarlink.Com [</tt></span><span =
lang=3DEN-US><a
href=3D"mailto:Peter.Meyer@Zarlink.Com" target=3D"_blank"><tt><span
style=3D'font-size:10.0pt'>mailto:Peter.Meyer@Zarlink.Com</span></tt></a>=
</span><tt><span
lang=3DEN-US style=3D'font-size:10.0pt'>] </span></tt><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; Sent: Wednesday, February 09, 2011 2.00 PM</tt><br>
<tt>&gt; To: Bhatia, Manav (Manav)</tt><br>
<tt>&gt; Cc: <a href=3D"mailto:tictoc@ietf.org" =
target=3D"_blank">tictoc@ietf.org</a></tt><br>
<tt>&gt; Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; =
BC</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi Manav,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; A high level point is that for the pure MPLS mapping (section =
5.3) , I</tt><br>
<tt>&gt; wonder if what is really needed is a PTP profile for MPLS -- =
</tt><br>
<tt>&gt; similar to</tt><br>
<tt>&gt; Annex D/E/F for IPv4/IPv6/Ethernet, respectively. &nbsp;For =
</tt><br>
<tt>&gt; example the IP &amp;</tt><br>
<tt>&gt; Ethernet profiles include other information such as the port =
</tt><br>
<tt>&gt; addressing for</tt><br>
<tt>&gt; the unicast master table and acceptable master table. =
&nbsp;Without a
full</tt><br>
<tt>&gt; profile, although the intermediate notes may operate in TC, =
</tt><br>
<tt>&gt; the server,</tt><br>
<tt>&gt; client and boundary nodes may not operate =
successfully.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Its not clear if this draft is intended to cover all clock =
</tt><br>
<tt>&gt; types (OC, BC &amp;</tt><br>
<tt>&gt; TC) or only TC. &nbsp;There are many sections that talk only =
about </tt><br>
<tt>&gt; TC without</tt><br>
<tt>&gt; considering OC and BC behaviour or impact. &nbsp;Is BC intended =
to </tt><br>
<tt>&gt; be covered as</tt><br>
<tt>&gt; a Client-side OC + Server-side OC model, or is BC excluded =
from</tt><br>
<tt>&gt; consideration in this draft? &nbsp;Perhaps this draft should be =
either</tt><br>
<tt>&gt; cleaned-up to consider all clock types or should be </tt><br>
<tt>&gt; restricted to only TC</tt><br>
<tt>&gt; clock type with OC &amp; BC out of scope.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Some specific comments</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + The abstract could be clarified to indicate there are three =
</tt><br>
<tt>&gt; mappings, not</tt><br>
<tt>&gt; two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS). =
&nbsp;I
think the</tt><br>
<tt>&gt; third mapping may be under discussion, so perhaps this is =
premature.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + A few places in the text the phrase &quot;proper handling of =
</tt><br>
<tt>&gt; these packets&quot; or</tt><br>
<tt>&gt; &quot;properly handle PTP messages&quot; or &quot;perform =
proper
&nbsp;</tt><br>
<tt>&gt; processing&quot; &nbsp;is used to</tt><br>
<tt>&gt; mean transparent clock. &nbsp;I would propose to remove such =
</tt><br>
<tt>&gt; language as from</tt><br>
<tt>&gt; the ITU-T studies of timing performances of PTP one could argue =
the</tt><br>
<tt>&gt; &quot;proper&quot; way is to implement a boundary clock. =
&nbsp;Where
the </tt><br>
<tt>&gt; intention is to</tt><br>
<tt>&gt; aid the designer of a TC that is fine to describe the =
implementation</tt><br>
<tt>&gt; recommendation, but not to suggest this is the way to acheive =
the best</tt><br>
<tt>&gt; performance or even the desired way to deploy PTP over =
MPLS.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + I would like to see a statement added in the document that =
the</tt><br>
<tt>&gt; performance aspects (e.g. the phase or frequency alignment) =
</tt><br>
<tt>&gt; are outside the</tt><br>
<tt>&gt; scope of the document.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 6, 7, 8, 10 and 13 seems to focus only on the TC =
</tt><br>
<tt>&gt; case between</tt><br>
<tt>&gt; OC's and does not consider BC situation.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 12 text on checksums could be improved to indicate =
this only</tt><br>
<tt>&gt; applies to TC and not to OC &amp; BC.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 16 seems to address only TC clocks and not OC or BC =
clocks.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 16.3 implies that the only possible way to handle PTP =
is TC,</tt><br>
<tt>&gt; excluding BC --- &quot;don't have the capability to process =
1588 </tt><br>
<tt>&gt; packets (e.g.</tt><br>
<tt>&gt; TC processing)&quot; and &quot; &nbsp; Non-1588-aware LSRs =
ignore the
RSVP </tt><br>
<tt>&gt; 1588_PTP_LSP</tt><br>
<tt>&gt; object and just switch the MPLS packets carrying 1588 messages =
as data</tt><br>
<tt>&gt; packets and don't perform any TC processing.&quot;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Regards,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ZARLINK Semiconductor</tt><br>
<tt>&gt; Peter Meyer</tt><br>
<tt>&gt; Timing &amp; Synchronization</tt><br>
<tt>&gt; Communication Products Group</tt><br>
<tt>&gt; Office: +1-613-270-7203&nbsp; |&nbsp; Fax: =
+1-613-592-1010</tt><br>
<tt>&gt; <a href=3D"mailto:peter.meyer@zarlink.com" =
target=3D"_blank">peter.meyer@zarlink.com</a>
&nbsp;| </tt></span><span lang=3DEN-US><a =
href=3D"http://www.zarlink.com"
target=3D"_blank"><tt><span =
style=3D'font-size:10.0pt'>www.zarlink.com</span></tt></a></span><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;Bhatia, =
Manav
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(Manav)&quot; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&lt;manav.bhatia@alc
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; To </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a
href=3D"http://atel-lucent.com" =
target=3D"_blank">atel-lucent.com</a>&gt; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;&quot;<a href=3D"mailto:tictoc@ietf.org"
target=3D"_blank">tictoc@ietf.org</a>&quot; </tt><br>
<tt>&gt; &lt;<a href=3D"mailto:tictoc@ietf.org" =
target=3D"_blank">tictoc@ietf.org</a>&gt;
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Sent by: &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; cc </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&lt;tictoc-bounces@i
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a
href=3D"http://etf.org" target=3D"_blank">etf.org</a>&gt; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp;Subject </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;[TICTOC]
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;</tt><br>
<tt>&gt; draft-ietf-tictoc-1588overmpls-00.t </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;26/01/2011 =
11:22
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;xt &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; </tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AM &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
</tt><br>
<tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; We've tried incorporating most of the comments that we received =
on the</tt><br>
<tt>&gt; list. Please ping me if you think we have missed some.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Would be great if the WG can go through this and provide =
</tt><br>
<tt>&gt; feedback on the</tt><br>
<tt>&gt; same.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; The draft is available here:</tt><br>
<tt>&gt; </tt></span><span lang=3DEN-US><a
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over"
target=3D"_blank"><tt><span =
style=3D'font-size:10.0pt'>http://www.ietf.org/internet-drafts/draft-ietf=
-tictoc-1588over</span></tt></a></span><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; mpls-00.txt</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &gt; -----Original Message-----</tt><br>
<tt>&gt; &gt; From: <a href=3D"mailto:tictoc-bounces@ietf.org" =
target=3D"_blank">tictoc-bounces@ietf.org</a></tt><br>
<tt>&gt; &gt; [</tt></span><span lang=3DEN-US><a
href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank"><tt><span
style=3D'font-size:10.0pt'>mailto:tictoc-bounces@ietf.org</span></tt></a>=
</span><tt><span
lang=3DEN-US style=3D'font-size:10.0pt'>] On Behalf Of </span></tt><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; <a href=3D"mailto:Internet-Drafts@ietf.org" =
target=3D"_blank">Internet-Drafts@ietf.org</a></tt><br>
<tt>&gt; &gt; Sent: Wednesday, January 26, 2011 9.30 PM</tt><br>
<tt>&gt; &gt; To: <a href=3D"mailto:i-d-announce@ietf.org" =
target=3D"_blank">i-d-announce@ietf.org</a></tt><br>
<tt>&gt; &gt; Cc: <a href=3D"mailto:tictoc@ietf.org" =
target=3D"_blank">tictoc@ietf.org</a></tt><br>
<tt>&gt; &gt; Subject: [TICTOC] I-D
Action:draft-ietf-tictoc-1588overmpls-00.txt</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; A New Internet-Draft is available from the =
on-line</tt><br>
<tt>&gt; &gt; Internet-Drafts directories.</tt><br>
<tt>&gt; &gt; This draft is a work item of the Timing over IP =
Connection</tt><br>
<tt>&gt; &gt; and Transfer of Clock Working Group of the IETF.</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Title &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; : Transporting PTP messages (1588) over</tt><br>
<tt>&gt; &gt; MPLS Networks</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Author(s) &nbsp; =
&nbsp;
&nbsp; : S. Davari, et al.</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Filename &nbsp; =
&nbsp;
&nbsp; &nbsp;: draft-ietf-tictoc-1588overmpls-00.txt</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Pages &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; : 35</tt><br>
<tt>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Date &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;: 2011-01-26</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; This document defines the method for transporting PTP =
</tt><br>
<tt>&gt; messages (PDUs)</tt><br>
<tt>&gt; &gt; over an MPLS network to enable a proper handling of these =
packets</tt><br>
<tt>&gt; &gt; (e.g. implementation of Transparent Clocks (TC)) in =
LSRs.</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; --</tt><br>
<tt>&gt; Manav Bhatia,</tt><br>
<tt>&gt; IP Division, Alcatel-Lucent,</tt><br>
<tt>&gt; Bangalore - India</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; _______________________________________________</tt><br>
<tt>&gt; TICTOC mailing list</tt><br>
<tt>&gt; <a href=3D"mailto:TICTOC@ietf.org" =
target=3D"_blank">TICTOC@ietf.org</a></tt><br>
<tt>&gt; </tt></span><span lang=3DEN-US><a
href=3D"https://www.ietf.org/mailman/listinfo/tictoc" =
target=3D"_blank"><tt><span
style=3D'font-size:10.0pt'>https://www.ietf.org/mailman/listinfo/tictoc</=
span></tt></a></span><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ----------</tt><br>
<tt>&gt; This email is confidential and may contain information that =
</tt><br>
<tt>&gt; is privileged and</tt><br>
<tt>&gt; exempt from disclosure by law. &nbsp;If you have received it in =
</tt><br>
<tt>&gt; error, please contact</tt><br>
<tt>&gt; the sender immediately by return email and then delete it =
</tt><br>
<tt>&gt; from your system; you</tt><br>
<tt>&gt; should not copy it or disclose its contents to anyone. =
&nbsp;</tt><br>
<tt>&gt; Emails are not secure</tt><br>
<tt>&gt; and cannot be guaranteed to be error free as they can be =
</tt><br>
<tt>&gt; intercepted, amended,</tt><br>
<tt>&gt; lost or destroyed, or contain viruses. &nbsp;Anyone who =
</tt><br>
<tt>&gt; communicates with us by email</tt><br>
<tt>&gt; is taken to accept these risks.</tt><br>
<tt>&gt; </tt><br>
<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt><a href=3D"mailto:TICTOC@ietf.org" =
target=3D"_blank">TICTOC@ietf.org</a></tt><br>
</span><span lang=3DEN-US><a =
href=3D"https://www.ietf.org/mailman/listinfo/tictoc"
target=3D"_blank"><tt><span =
style=3D'font-size:10.0pt'>https://www.ietf.org/mailman/listinfo/tictoc</=
span></tt></a></span><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt><a href=3D"mailto:TICTOC@ietf.org" =
target=3D"_blank">TICTOC@ietf.org</a></tt><br>
</span><span lang=3DEN-US><a =
href=3D"https://www.ietf.org/mailman/listinfo/tictoc"
target=3D"_blank"><tt><span =
style=3D'font-size:10.0pt'>https://www.ietf.org/mailman/listinfo/tictoc</=
span></tt></a><o:p></o:p></span></p>

</div>

</div>

</div>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/tictoc</a><o:p></=
o:p></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01CBCB7E.C323517F--

From ronc.ntear@gmail.com  Sun Feb 13 05:49:42 2011
Return-Path: <ronc.ntear@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 332203A6A7C; Sun, 13 Feb 2011 05:49:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yCtOCD6miFps; Sun, 13 Feb 2011 05:49:39 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 06DEC3A6A6E; Sun, 13 Feb 2011 05:49:37 -0800 (PST)
Received: by wwa36 with SMTP id 36so4007123wwa.13 for <multiple recipients>; Sun, 13 Feb 2011 05:49:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=KKHYsm92PQ1kk2ORDdUEmcIbi4iqaSydM8rEP1S8ibI=; b=F7LtHrhrPEWNLSW7+Azk1YPmxppVK68HCBSGozwK/EGK9AngYvXgoqjcnHaUWm9Ats zDN0KFBaaj0ctfCznDJJYeeArcE7oWztzgaVJOG364QYT+/kL9+8xxk1l9wSdyA6CXBc 8cZoQdHWCcfYqmW9NumfcJRUeugB2AHFioNIA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=wMk1wtbY+JteHrp+jU/YE1gdSL6OpqP/4L6ZY3P6EkxV6vHA2p/lWOIvsqITOo/7Qb w4dQuwhDqURBBHcg86aXUYu609Gb/jKNd+mRCWJjg4iJ75+/Qvl/axEXWkhfefyzAvru 6m9ki+6uShe8x+q65dxZ1lvaIgSJCiT7TIk9U=
MIME-Version: 1.0
Received: by 10.216.19.133 with SMTP id n5mr2264716wen.83.1297604996102; Sun, 13 Feb 2011 05:49:56 -0800 (PST)
Received: by 10.216.173.197 with HTTP; Sun, 13 Feb 2011 05:49:56 -0800 (PST)
In-Reply-To: <AFC377AFCC0FBD4DABE49F4B81EC4F1A02485667@ftrdmel1>
References: <CA2959F3E75BA645A43E81C3B071F6320ACFEA9560@USNAVSXCHMBSC2.ndc.alcatel-lucent.com> <OF23A1DD85.5C87F3B6-ON85257832.0052BB99-85257832.0052DDFF@Zarlink.Com> <28C9B1CD4D27844E9CD8F02BFEB70564075118B097@ESESSCMS0360.eemea.ericsson.se> <6D53E9696A81554B9B2E14FF508BA7C80979D6426B@EMV35-UKDY.domain1.systemhost.net> <785DA01679B0C44F951747BE9CF66E6B04F3E7FC@mbox-txa2.vitesse.com> <AANLkTinwCtfCkKWFA4vmJXZGnrPx6vJEufva4L19L1JR@mail.gmail.com> <AFC377AFCC0FBD4DABE49F4B81EC4F1A02485667@ftrdmel1>
Date: Sun, 13 Feb 2011 15:49:56 +0200
Message-ID: <AANLkTinSiV+sTYoVo7Rxt+1c93kPQi6G=sUxHu9xKnzt@mail.gmail.com>
From: Ron Cohen <ronc.ntear@gmail.com>
To: sebastien.jobert@orange-ftgroup.com
Content-Type: multipart/alternative; boundary=0016368e3059da0eba049c2a3494
Cc: tictoc@ietf.org, tictoc-bounces@ietf.org
Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 13 Feb 2011 13:49:42 -0000

--0016368e3059da0eba049c2a3494
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Sebastien,

I'm not sure I understand the question, so my answer below may be off topic=
.

One of the requirements for PTP-LSP should be that it is PTP-capable at eac=
h
segment. Therefore the LSP will not be setup over segments which include
non-PTP capable nodes in the middle, even if these nodes support MPLS
switching. Although MPLS allows hierarchy through label stacking, the PTP
over MPLS profile may specify, in my opinion, that only single label stack
should be used, unless we are in a special scenario yet to be discussed.

Not all MPLS LSR are also 802.1 bridges. That is, even if an LSR has
Ethernet interfaces it may not be able to forward Ethernet messages
according to their destination address. If the LSR is also a BC it may or
may not be configured to process the PTP messages. If what is required is T=
C
functionality, and the LSR doesn't support bridging, these messages will no=
t
be forwarded at all, hence some form of PTP over MPLS (whether raw, IP or
other) is needed.

Best,
Ron



On Sun, Feb 13, 2011 at 3:04 PM, <sebastien.jobert@orange-ftgroup.com>wrote=
:

>  Hi Ron,
>
>
>
> Interesting view. As far as I understand, it sounds however a bit
> misaligned with the on-going work at ITU-T.
>
>
>
> Just a quick question for my clarification: how do you manage the case wh=
en
> another transport technology (e.g. Ethernet) is used between two MPLS nod=
es
> if only an =93MPLS mapping=94 is considered? (I understand that it may ha=
ppen
> within an MPLS domain). The two MPLS nodes may even not be aware that the=
re
> is something in the middle.
>
>
>
> Thanks.
>
>
>
> BR,
>
>
>
> S=E9bastien
>
>
>
> *De :* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *De la
> part de* Ron Cohen
> *Envoy=E9 :* dimanche 13 f=E9vrier 2011 08:51
> *=C0 :* Lars Ellegaard
> *Cc :* tictoc-bounces@ietf.org; tictoc@ietf.org
> *Objet :* Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
>
> Hi,
>
> Here is how I see it.
>
> There are several advantages for TC over BC it terms of implementation: y=
ou
> don't need to maintain a clock, and you can implement all (most) of
> operations in hardware, and as a result its much easier to upgrade equipm=
ent
> to be PTP capable (see my previous post on per-port vs. per node PTP-capa=
ble
> attribute). TCs also allows transport of multiple timescales with ease,
> while this complicates BC considerably (This may or may not be needed in =
our
> case though).
>
> Hence, I see an advantage in deploying a BC on the boundary of the MPLS
> domain, and implementing TCs within the MPLS domain, connecting the edge
> BCs.
>
> MPLS allows you to set a label-switched-path (LSP) which is fully
> controlled: you can select hop by hop how the messages are transported,
> selecting paths that support PTP at each hop (and not necessarily the
> shortest path), that are symmetric (or for which asymmetry is known), tha=
t
> are shared with SyncE synchronization chain (although I don't think its
> necessary), etc.
>
> MPLS advantage is that regardless of the underlying layer1/2 technology,
> whether it is Ethernet, SONET, RPR etc, MPLS will allow setting these pat=
h
> using the same procedures. Over an MPLS domain, this is maybe the only se=
tup
> protocol suite available.
>
> Hence MPLS will allow setting PTP MPLS LSPs through the MPLS domain TCs.
>
> Not all features available in MPLS are relevant for PTP transport. The PT=
P
> profile should define all this. For example, many of the MPLS protection
> features should be carefully selected, in order not to introduce phase
> transients in downstream slaves.
>
> Assuming the above makes sense, there is a need to define an MPLS PTP
> profile, for which the current draft is a first step. The profile may
> include MPLS to PTP event propagation (i.e. failures in MPLS signaled wit=
hin
> PTP messages),  etc. Raw PTP over MPLS encapsulation makes sense in this
> scenario too, especially as the latest draft defines signaling offset of =
PTP
> header, to avoid deep packet inspection on top of MPLS, and hence support=
s
> also new encaps  (Hence I don't understand Shahram point).
>
> Best,
> Ron
>
>  On Sat, Feb 12, 2011 at 12:06 PM, Lars Ellegaard <le@vitesse.com> wrote:
>
> This would be PTPoverACHoMPLSoETH (or other link layer technologies).
>
>
>
> In my view MPLS(-TP) provides =93transport=94 of an application, which is
> behind some form of addressing (typically IP, Ethernet).
>
> Only exception are (MPLS) transport associated mechanisms like OAM.
> MPLS(-TP) does not have an addressing scheme.
>
> It would therefore be a violation of this if the PTP application (which
> requires multicast/unicast addressing) is carried directly after the labe=
l
> (even after the ACH).
>
> In other words even though it is possible, I suggest not to support
> PTPoACHoMPLS or PTPoMPLS.
>
>
>
> BR Lars
>
>
>
>
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *mike.gilson@bt.com
> *Sent:* 11 February 2011 18:54
> *To:* stefano.ruffini@ericsson.com; Peter.Meyer@Zarlink.Com;
> peter.roberts@alcatel-lucent.com
>
>
> *Cc:* tictoc@ietf.org; tictoc-bounces@ietf.org
> *Subject:* Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
>
> I would think the interface would be Ethernet. How many interfaces are
> there that are pure MPLS or another.
>
>
>
> Maybe someone can expand on this.
>
>
>
> Regards,
>
> *Mike*
>  ------------------------------
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Stefano Ruffini
> *Sent:* 10 February 2011 16:35
> *To:* Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)
> *Cc:* tictoc@ietf.org; tictoc-bounces@ietf.org
> *Subject:* Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
> Peter M., Peter R.
>
> I wonder if there is really a need (use case) for section 5.3 (pure MPLS
> mapping) ?
>
>  Best Regards
>
> Stefano
>
>
>  ------------------------------
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Peter.Meyer@Zarlink.Com
> *Sent:* mercoled=EC 9 febbraio 2011 16.06
> *To:* Roberts, Peter (Peter)
> *Cc:* tictoc@ietf.org; tictoc-bounces@ietf.org
> *Subject:* Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
> Thanks.
>
> Yes, a poor choice of words on the Annexes being "profiles".  We would
> still need to fill out the Annex info though re: port addresses and the l=
ike
> to ensure inter-operability.
>
> I am fine to be neutral on performance aspects -- I would recommend to
> indicate they are not within scope of the document.
>
> *ZARLINK** *Semiconductor*
> Peter Meyer
> Timing & Synchronization
> Communication Products Group**
> Office: +1-613-270-7203**  |  **Fax: +1-613-592-1010**
> *peter.meyer@zarlink.com <employee.name@zarlink.com> * | *www.zarlink.com
>
>
>
> *"Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>*
> Sent by: <tictoc-bounces@ietf.org>
>
> 09/02/2011 08:52 AM
>
> To
>
> "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>,
> "Peter.Meyer@Zarlink.Com" <Peter.Meyer@zarlink.com>
>
> cc
>
> "tictoc@ietf.org" <tictoc@ietf.org>
>
> Subject
>
> Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
>
>
>
>
>
> Peter,
> With respect to your comments on the profile, the Annexes are not profile=
s.
>  They are the portions of the standard that define the rules for running =
PTP
> over specific lower layer protocols.  These can then be included or exclu=
ded
> from specific profiles that are defined.  This draft is defining these ru=
les
> for the MPLS environment.
> The draft covers all the clock types but as you point out this is not all
> that clear.  This can be added.
> In addition, I don't believe the ITU-T has concluded anything about
> performance of BC vs TC.  They have just started studying the issue.  But
> this draft is not making any claims about performance and as stated earli=
er
> should be applicable for any of the clock types.  We can review it to rem=
ove
> any contentious wording in respect to performance.
> Peter R.
>
>
>
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org<tictoc-boun=
ces@ietf.org>]
> On Behalf Of Bhatia, Manav (Manav)
> Sent: February 9, 2011 8:20 AM
> To: Peter.Meyer@Zarlink.Com
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
>
> Hi Peter,
>
> Very valid comments.
>
> This draft covers all clock types - TC, BC and OC. The reason it seems
> we've been concentrating on TC is because that's the clock type that
> requires special MPLS processing.
>
> For BC's and OC's there is no special processing involved. One just needs
> an MPLS LSP that terminates on a BC and OC and things will just work.
> However, I get the drift of what youre saying and we can update the draft=
 to
> explicitly state this.
>
> I will let someone more knowledgeable respond to your question on whether=
 a
> separate profile for MPLS is required or not. To my untrained eye it look=
s
> that we might.
>
> Cheers, Manav
>
> > -----Original Message-----
> > From: Peter.Meyer@Zarlink.Com [mailto:Peter.Meyer@Zarlink.Com<Peter.Mey=
er@Zarlink.Com>]
>
> > Sent: Wednesday, February 09, 2011 2.00 PM
> > To: Bhatia, Manav (Manav)
> > Cc: tictoc@ietf.org
> > Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile & BC
> >
> >
> > Hi Manav,
> >
> >
> > A high level point is that for the pure MPLS mapping (section 5.3) , I
> > wonder if what is really needed is a PTP profile for MPLS --
> > similar to
> > Annex D/E/F for IPv4/IPv6/Ethernet, respectively.  For
> > example the IP &
> > Ethernet profiles include other information such as the port
> > addressing for
> > the unicast master table and acceptable master table.  Without a full
> > profile, although the intermediate notes may operate in TC,
> > the server,
> > client and boundary nodes may not operate successfully.
> >
> > Its not clear if this draft is intended to cover all clock
> > types (OC, BC &
> > TC) or only TC.  There are many sections that talk only about
> > TC without
> > considering OC and BC behaviour or impact.  Is BC intended to
> > be covered as
> > a Client-side OC + Server-side OC model, or is BC excluded from
> > consideration in this draft?  Perhaps this draft should be either
> > cleaned-up to consider all clock types or should be
> > restricted to only TC
> > clock type with OC & BC out of scope.
> >
> >
> > Some specific comments
> >
> > + The abstract could be clarified to indicate there are three
> > mappings, not
> > two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS).  I think the
> > third mapping may be under discussion, so perhaps this is premature.
> >
> > + A few places in the text the phrase "proper handling of
> > these packets" or
> > "properly handle PTP messages" or "perform proper
> > processing"  is used to
> > mean transparent clock.  I would propose to remove such
> > language as from
> > the ITU-T studies of timing performances of PTP one could argue the
> > "proper" way is to implement a boundary clock.  Where the
> > intention is to
> > aid the designer of a TC that is fine to describe the implementation
> > recommendation, but not to suggest this is the way to acheive the best
> > performance or even the desired way to deploy PTP over MPLS.
> >
> > + I would like to see a statement added in the document that the
> > performance aspects (e.g. the phase or frequency alignment)
> > are outside the
> > scope of the document.
> >
> > + Section 6, 7, 8, 10 and 13 seems to focus only on the TC
> > case between
> > OC's and does not consider BC situation.
> >
> > + Section 12 text on checksums could be improved to indicate this only
> > applies to TC and not to OC & BC.
> >
> > + Section 16 seems to address only TC clocks and not OC or BC clocks.
> >
> > + Section 16.3 implies that the only possible way to handle PTP is TC,
> > excluding BC --- "don't have the capability to process 1588
> > packets (e.g.
> > TC processing)" and "   Non-1588-aware LSRs ignore the RSVP
> > 1588_PTP_LSP
> > object and just switch the MPLS packets carrying 1588 messages as data
> > packets and don't perform any TC processing."
> >
> >
> > Regards,
> >
> >
> > ZARLINK Semiconductor
> > Peter Meyer
> > Timing & Synchronization
> > Communication Products Group
> > Office: +1-613-270-7203  |  Fax: +1-613-592-1010
> > peter.meyer@zarlink.com  | www.zarlink.com
> >
> >
> >
> >
> >
> >              "Bhatia, Manav
> >
> >              (Manav)"
> >
> >              <manav.bhatia@alc
> >           To
> >              atel-lucent.com>          "tictoc@ietf.org"
> > <tictoc@ietf.org>
> >              Sent by:
> >           cc
> >              <tictoc-bounces@i
> >
> >              etf.org>
> >      Subject
> >                                        [TICTOC]
> >
> >
> > draft-ietf-tictoc-1588overmpls-00.t
> >              26/01/2011 11:22          xt
> >
> >              AM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi,
> >
> > We've tried incorporating most of the comments that we received on the
> > list. Please ping me if you think we have missed some.
> >
> > Would be great if the WG can go through this and provide
> > feedback on the
> > same.
> >
> > The draft is available here:
> > http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over
> > mpls-00.txt
> >
> > Cheers, Manav
> >
> > > -----Original Message-----
> > > From: tictoc-bounces@ietf.org
> > > [mailto:tictoc-bounces@ietf.org <tictoc-bounces@ietf.org>] On Behalf
> Of
> > Internet-Drafts@ietf.org
> > > Sent: Wednesday, January 26, 2011 9.30 PM
> > > To: i-d-announce@ietf.org
> > > Cc: tictoc@ietf.org
> > > Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.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 PTP messages (1588) over
> > > MPLS Networks
> > >            Author(s)       : S. Davari, et al.
> > >            Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> > >            Pages           : 35
> > >            Date            : 2011-01-26
> > >
> > > This document defines the method for transporting PTP
> > messages (PDUs)
> > > over an MPLS network to enable a proper handling of these packets
> > > (e.g. implementation of Transparent Clocks (TC)) in LSRs.
> > >
> >
> > Cheers, Manav
> >
> > --
> > Manav Bhatia,
> > IP Division, Alcatel-Lucent,
> > Bangalore - India
> >
> >
> > _______________________________________________
> > TICTOC mailing list
> > TICTOC@ietf.org
> > https://www.ietf.org/mailman/listinfo/tictoc
> >
> >
> >
> > ----------
> > This email is confidential and may contain information that
> > is privileged and
> > exempt from disclosure by law.  If you have received it in
> > error, please contact
> > the sender immediately by return email and then delete it
> > from your system; you
> > should not copy it or disclose its contents to anyone.
> > Emails are not secure
> > and cannot be guaranteed to be error free as they can be
> > intercepted, amended,
> > lost or destroyed, or contain viruses.  Anyone who
> > communicates with us by email
> > is taken to accept these risks.
> >
> _______________________________________________
> 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
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>
>

--0016368e3059da0eba049c2a3494
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Sebastien,<br><br>I&#39;m not sure I understand the que=
stion, so my answer below may be off topic.<br><br>One of the requirements =
for PTP-LSP should be that it is PTP-capable at each segment. Therefore the=
 LSP will not be setup over segments which include non-PTP capable nodes in=
 the middle, even if these nodes support MPLS switching. Although MPLS allo=
ws hierarchy through label stacking, the PTP over MPLS profile may specify,=
 in my opinion, that only single label stack should be used, unless we are =
in a special scenario yet to be discussed.<br>
<br>Not all MPLS LSR are also 802.1 bridges. That is, even if an LSR has Et=
hernet interfaces it may not be able to forward Ethernet messages according=
 to their destination address. If the LSR is also a BC it may or may not be=
 configured to process the PTP messages. If what is required is TC function=
ality, and the LSR doesn&#39;t support bridging, these messages will not be=
 forwarded at all, hence some form of PTP over MPLS (whether raw, IP or oth=
er) is needed.<br>
<br>Best,<br>Ron<br><br><br><br><div class=3D"gmail_quote">On Sun, Feb 13, =
2011 at 3:04 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:sebastien.jobert@=
orange-ftgroup.com">sebastien.jobert@orange-ftgroup.com</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">









<div link=3D"blue" vlink=3D"purple" lang=3D"FR">

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">Hi Ron,</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">=A0</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">Interesting view. As far as I understand, it sounds ho=
wever a
bit misaligned with the on-going work at ITU-T.</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">=A0</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">Just a quick question for my clarification: how do you=
 manage the
case when another transport technology (e.g. Ethernet) is used between two =
MPLS
nodes if only an =93MPLS mapping=94 is considered? (I understand that
it may happen within an MPLS domain). The two MPLS nodes may even not be aw=
are
that there is something in the middle.</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">=A0</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">Thanks.</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">=A0</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">BR,</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">=A0</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">S=E9bastien</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">=A0</span></p>

<div style=3D"border-width: 1pt medium medium; border-style: solid none non=
e; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color=
; padding: 3pt 0cm 0cm;">

<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt;">De=A0:</span></b=
><span style=3D"font-size: 10pt;">
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"=
_blank">tictoc-bounces@ietf.org</a>] <b>De la part de</b>
Ron Cohen<br>
<b>Envoy=E9=A0:</b> dimanche 13 f=E9vrier 2011 08:51<br>
<b>=C0=A0:</b> Lars Ellegaard<br>
<b>Cc=A0:</b> <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">=
tictoc-bounces@ietf.org</a>; <a href=3D"mailto:tictoc@ietf.org" target=3D"_=
blank">tictoc@ietf.org</a><br>
<b>Objet=A0:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</span=
></p>

</div><div><div></div><div class=3D"h5">

<p class=3D"MsoNormal">=A0</p>

<div>

<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;">Hi,<br>
<br>
Here is how I see it.<br>
<br>
There are several advantages for TC over BC it terms of implementation: you
don&#39;t need to maintain a clock, and you can implement all (most) of ope=
rations
in hardware, and as a result its much easier to upgrade equipment to be PTP
capable (see my previous post on per-port vs. per node PTP-capable attribut=
e).
TCs also allows transport of multiple timescales with ease, while this
complicates BC considerably (This may or may not be needed in our case thou=
gh).<br>
=A0<br>
Hence, I see an advantage in deploying a BC on the boundary of the MPLS dom=
ain,
and implementing TCs within the MPLS domain, connecting the edge BCs.<br>
<br>
MPLS allows you to set a label-switched-path (LSP) which is fully controlle=
d:
you can select hop by hop how the messages are transported, selecting paths
that support PTP at each hop (and not necessarily the shortest path), that =
are
symmetric (or for which asymmetry is known), that are shared with SyncE
synchronization chain (although I don&#39;t think its necessary), etc. <br>
<br>
MPLS advantage is that regardless of the underlying layer1/2 technology,
whether it is Ethernet, SONET, RPR etc, MPLS will allow setting these path
using the same procedures. Over an MPLS domain, this is maybe the only setu=
p
protocol suite available.<br>
<br>
Hence MPLS will allow setting PTP MPLS LSPs through the MPLS domain TCs.<br=
>
<br>
Not all features available in MPLS are relevant for PTP transport. The PTP
profile should define all this. For example, many of the MPLS protection
features should be carefully selected, in order not to introduce phase
transients in downstream slaves. <br>
<br>
Assuming the above makes sense, there is a need to define an MPLS PTP profi=
le,
for which the current draft is a first step. The profile may include MPLS t=
o
PTP event propagation (i.e. failures in MPLS signaled within PTP
messages),=A0 etc. Raw PTP over MPLS encapsulation makes sense in this
scenario too, especially as the latest draft defines signaling offset of PT=
P
header, to avoid deep packet inspection on top of MPLS, and hence supports =
also
new encaps=A0 (Hence I don&#39;t understand Shahram point). <br>
<br>
Best,<br>
Ron<br>
<br>
</p>

<div>

<p class=3D"MsoNormal">On Sat, Feb 12, 2011 at 12:06 PM, Lars Ellegaard &lt=
;<a href=3D"mailto:le@vitesse.com" target=3D"_blank">le@vitesse.com</a>&gt;=
 wrote:</p>

<div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">This would be
PTPoverACHoMPLSoETH (or other link layer technologies).</span><span lang=3D=
"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">=A0</span><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">In my view MPLS(-TP) provides
=93transport=94 of an application, which is behind some form of
addressing (typically IP, Ethernet).</span><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">Only exception are (MPLS)
transport associated mechanisms like OAM. MPLS(-TP) does not have an addres=
sing
scheme.</span><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">It would therefore be a
violation of this if the PTP application (which requires multicast/unicast
addressing) is carried directly after the label (even after the ACH).</span=
><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">In other words even though it
is possible, I suggest not to support PTPoACHoMPLS or PTPoMPLS.</span><span=
 lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">=A0</span><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">BR Lars</span><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">=A0</span><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);" lang=3D"EN-US">=A0</span><span lang=3D"EN-US"></span></p>

<div>

<div style=3D"border-width: 1pt medium medium; border-style: solid none non=
e; padding: 3pt 0cm 0cm; border-color: -moz-use-text-color;">

<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt;" lang=3D"EN-US">F=
rom:</span></b><span style=3D"font-size: 10pt;" lang=3D"EN-US"> <a href=3D"=
mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tic=
toc-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:mike.gilson@bt.com" target=3D"_blank"=
>mike.gilson@bt.com</a><br>
<b>Sent:</b> 11 February 2011 18:54<br>
<b>To:</b> <a href=3D"mailto:stefano.ruffini@ericsson.com" target=3D"_blank=
">stefano.ruffini@ericsson.com</a>;
Peter.Meyer@Zarlink.Com; <a href=3D"mailto:peter.roberts@alcatel-lucent.com=
" target=3D"_blank">peter.roberts@alcatel-lucent.com</a></span></p>

<div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt;" lang=3D"EN-US"><br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a>;
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a><br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</span>=
</p>

</div>

</div>

</div>

</div>

<div>

<div>

<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0</span></p>

<p class=3D"MsoNormal"><span style=3D"color: blue;" lang=3D"EN-US">I would =
think the interface would be
Ethernet.=A0How many interfaces are there that are pure MPLS or another.</s=
pan><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0</span></p>

<p class=3D"MsoNormal"><span style=3D"color: blue;" lang=3D"EN-US">Maybe so=
meone can expand on this.</span><span lang=3D"EN-US"></span></p>

<div>

<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt;" lang=3D"EN-GB">Rega=
rds,</span><span lang=3D"EN-GB"> </span><span lang=3D"EN-US"></span></p>

</div>

<p><i><span style=3D"font-size: 13.5pt; font-family: &quot;Comic Sans MS&qu=
ot;; color: blue;" lang=3D"EN-GB">Mike</span></i><span lang=3D"EN-GB"> </sp=
an><span lang=3D"EN-US"></span></p>

<div>

<div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center"><sp=
an lang=3D"EN-US">

<hr size=3D"2" align=3D"center" width=3D"100%">

</span></div>

<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><b><span style=3D"fon=
t-size: 10pt;" lang=3D"EN-US">From:</span></b><span style=3D"font-size: 10p=
t;" lang=3D"EN-US"> <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_b=
lank">tictoc-bounces@ietf.org</a> [mailto:<a href=3D"mailto:tictoc-bounces@=
ietf.org" target=3D"_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Stefano Ruffini<br>
<b>Sent:</b> 10 February 2011 16:35<br>
<b>To:</b> Peter.Meyer@Zarlink.Com; Roberts, Peter (Peter)<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a>;
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a><br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</span>=
<span lang=3D"EN-US"></span></p>

</div>

<p><span lang=3D"IT">Peter M., Peter R.</span><span lang=3D"EN-US"></span><=
/p>

<p><span lang=3D"IT">I wonder if there is really a need (use case) for sect=
ion 5.3
(pure MPLS mapping) ?</span><span lang=3D"EN-US"></span></p>

<p><span lang=3D"IT">=A0Best Regards</span><span lang=3D"EN-US"></span></p>

<p><span lang=3D"IT">Stefano </span><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0</span></p>

<div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center"><sp=
an lang=3D"EN-US">

<hr size=3D"2" align=3D"center" width=3D"100%">

</span></div>

<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><b><span style=3D"fon=
t-size: 10pt;" lang=3D"EN-US">From:</span></b><span style=3D"font-size: 10p=
t;" lang=3D"EN-US"> <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_b=
lank">tictoc-bounces@ietf.org</a> [mailto:<a href=3D"mailto:tictoc-bounces@=
ietf.org" target=3D"_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Peter.Meyer@Zarlink.Com<br>
<b>Sent:</b> mercoled=EC 9 febbraio 2011 16.06<br>
<b>To:</b> Roberts, Peter (Peter)<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a>;
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a><br>
<b>Subject:</b> Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</span>=
<span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
</span><span style=3D"font-size: 10pt;" lang=3D"EN-US">Thanks.</span><span =
lang=3D"EN-US"> <br>
<br>
</span><span style=3D"font-size: 10pt;" lang=3D"EN-US">Yes, a poor choice o=
f words on
the Annexes being &quot;profiles&quot;. =A0We would still need to fill out
the Annex info though re: port addresses and the like to ensure
inter-operability.</span><span lang=3D"EN-US"> <br>
<br>
</span><span style=3D"font-size: 10pt;" lang=3D"EN-US">I am fine to be neut=
ral on
performance aspects -- I would recommend to indicate they are not within sc=
ope
of the document. </span><span lang=3D"EN-US"></span></p>

<p><b><span style=3D"font-size: 10pt;" lang=3D"EN-US">ZARLINK</span></b><b>=
<span lang=3D"EN-US"> </span></b><span style=3D"font-size: 7.5pt;" lang=3D"=
EN-US">Semiconductor<b><br>
Peter Meyer<i><span style=3D"color: gray;"><br>
Timing &amp; Synchronization<br>
Communication Products Group</span></i></b><i><br>
Office: +1-613-270-7203</i><b>=A0 |=A0 </b><i>Fax: +1-613-592-1010</i><u><s=
pan style=3D"color: blue;"><br>
</span></u></span><span lang=3D"EN-US"><a href=3D"mailto:employee.name@zarl=
ink.com" target=3D"_blank"><span style=3D"font-size: 7.5pt;">peter.meyer@za=
rlink.com</span></a></span><span style=3D"font-size: 7.5pt;" lang=3D"EN-US"=
> <b>=A0| </b></span><span lang=3D"EN-US"><a href=3D"http://www.zarlink.com=
/" target=3D"_blank"><span style=3D"font-size: 7.5pt;">www.zarlink.com</spa=
n></a></span></p>


<p style=3D"margin-bottom: 12pt;"><span lang=3D"EN-US">=A0</span></p>

<table style=3D"width: 100%;" border=3D"0" cellpadding=3D"0" width=3D"100%"=
>
 <tbody><tr>
  <td style=3D"width: 40%; padding: 0.75pt;" valign=3D"top" width=3D"40%">
  <p class=3D"MsoNormal"><b><span style=3D"font-size: 7.5pt;">&quot;Roberts=
, Peter (Peter)&quot; &lt;<a href=3D"mailto:peter.roberts@alcatel-lucent.co=
m" target=3D"_blank">peter.roberts@alcatel-lucent.com</a>&gt;</span></b><sp=
an style=3D"font-size: 7.5pt;"> </span><br>

  <span style=3D"font-size: 7.5pt;">Sent by: &lt;<a href=3D"mailto:tictoc-b=
ounces@ietf.org" target=3D"_blank">tictoc-bounces@ietf.org</a>&gt;</span>
  </p>
  <p><span style=3D"font-size: 7.5pt;">09/02/2011 08:52 AM</span> </p>
  </td>
  <td style=3D"width: 59%; padding: 0.75pt;" valign=3D"top" width=3D"59%">
  <table style=3D"width: 100%;" border=3D"0" cellpadding=3D"0" width=3D"100=
%">
   <tbody><tr>
    <td style=3D"padding: 0.75pt;" valign=3D"top">
    <p class=3D"MsoNormal" style=3D"text-align: right;" align=3D"right"><sp=
an style=3D"font-size: 7.5pt;">To</span></p>
    </td>
    <td style=3D"padding: 0.75pt;" valign=3D"top">
    <p class=3D"MsoNormal"><span style=3D"font-size: 7.5pt;">&quot;Bhatia, =
Manav (Manav)&quot; &lt;<a href=3D"mailto:manav.bhatia@alcatel-lucent.com" =
target=3D"_blank">manav.bhatia@alcatel-lucent.com</a>&gt;,
    &quot;Peter.Meyer@Zarlink.Com&quot; &lt;<a href=3D"mailto:Peter.Meyer@z=
arlink.com" target=3D"_blank">Peter.Meyer@zarlink.com</a>&gt;</span>
    </p>
    </td>
   </tr>
   <tr>
    <td style=3D"padding: 0.75pt;" valign=3D"top">
    <p class=3D"MsoNormal" style=3D"text-align: right;" align=3D"right"><sp=
an style=3D"font-size: 7.5pt;">cc</span></p>
    </td>
    <td style=3D"padding: 0.75pt;" valign=3D"top">
    <p class=3D"MsoNormal"><span style=3D"font-size: 7.5pt;">&quot;<a href=
=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf.org</a>&quot; &lt=
;<a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf.org</a>&g=
t;</span>
    </p>
    </td>
   </tr>
   <tr>
    <td style=3D"padding: 0.75pt;" valign=3D"top">
    <p class=3D"MsoNormal" style=3D"text-align: right;" align=3D"right"><sp=
an style=3D"font-size: 7.5pt;">Subject</span></p>
    </td>
    <td style=3D"padding: 0.75pt;" valign=3D"top">
    <p class=3D"MsoNormal"><span style=3D"font-size: 7.5pt;">Re: [TICTOC] 1=
588overmpls-00 / MPLS
    profile &amp; BC</span></p>
    </td>
   </tr>
  </tbody></table>
  <p class=3D"MsoNormal">=A0</p>
  <table border=3D"0" cellpadding=3D"0">
   <tbody><tr>
    <td style=3D"padding: 0.75pt;" valign=3D"top"></td>
    <td style=3D"padding: 0.75pt;" valign=3D"top"></td>
   </tr>
  </tbody></table>
  </td>
 </tr>
</tbody></table>

<p style=3D"margin-bottom: 12pt;"><span lang=3D"EN-US"><br>
<br>
<br>
</span><tt><span style=3D"font-size: 10pt;" lang=3D"EN-US">Peter,</span></t=
t><span style=3D"font-size: 10pt; font-family: &quot;Courier New&quot;;" la=
ng=3D"EN-US"><br>
<tt>With respect to your comments on the profile, the Annexes are not profi=
les.
=A0They are the portions of the standard that define the rules for running
PTP over specific lower layer protocols. =A0These can then be included or
excluded from specific profiles that are defined. =A0This draft is defining
these rules for the MPLS environment. =A0</tt><br>
<tt>The draft covers all the clock types but as you point out this is not a=
ll
that clear. =A0This can be added.</tt><br>
<tt>In addition, I don&#39;t believe the ITU-T has concluded anything about=
 performance
of BC vs TC. =A0They have just started studying the issue. =A0But this
draft is not making any claims about performance and as stated earlier shou=
ld
be applicable for any of the clock types. =A0We can review it to remove any
contentious wording in respect to performance.</tt><br>
<tt>Peter R.</tt><br>
<br>
<tt>=A0 </tt><br>
<br>
<tt>-----Original Message-----</tt><br>
<tt>From: <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tict=
oc-bounces@ietf.org</a>
[</tt></span><span lang=3D"EN-US"><a href=3D"mailto:tictoc-bounces@ietf.org=
" target=3D"_blank"><tt><span style=3D"font-size: 10pt;">mailto:tictoc-boun=
ces@ietf.org</span></tt></a></span><tt><span style=3D"font-size: 10pt;" lan=
g=3D"EN-US">] On Behalf Of Bhatia, Manav (Manav)</span></tt><span style=3D"=
font-size: 10pt; font-family: &quot;Courier New&quot;;" lang=3D"EN-US"><br>

<tt>Sent: February 9, 2011 8:20 AM</tt><br>
<tt>To: Peter.Meyer@Zarlink.Com</tt><br>
<tt>Cc: <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf.or=
g</a></tt><br>
<tt>Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</tt><br>
<br>
<tt>Hi Peter,</tt><br>
<br>
<tt>Very valid comments. </tt><br>
<br>
<tt>This draft covers all clock types - TC, BC and OC. The reason it seems
we&#39;ve been concentrating on TC is because that&#39;s the clock type tha=
t requires
special MPLS processing. </tt><br>
<br>
<tt>For BC&#39;s and OC&#39;s there is no special processing involved. One =
just needs
an MPLS LSP that terminates on a BC and OC and things will just work. Howev=
er,
I get the drift of what youre saying and we can update the draft to explici=
tly
state this.</tt><br>
<br>
<tt>I will let someone more knowledgeable respond to your question on wheth=
er a
separate profile for MPLS is required or not. To my untrained eye it looks =
that
we might.</tt><br>
<br>
<tt>Cheers, Manav </tt><br>
<br>
<tt>&gt; -----Original Message-----</tt><br>
<tt>&gt; From: Peter.Meyer@Zarlink.Com [</tt></span><span lang=3D"EN-US"><a=
 href=3D"mailto:Peter.Meyer@Zarlink.Com" target=3D"_blank"><tt><span style=
=3D"font-size: 10pt;">mailto:Peter.Meyer@Zarlink.Com</span></tt></a></span>=
<tt><span style=3D"font-size: 10pt;" lang=3D"EN-US">] </span></tt><span sty=
le=3D"font-size: 10pt; font-family: &quot;Courier New&quot;;" lang=3D"EN-US=
"><br>

<tt>&gt; Sent: Wednesday, February 09, 2011 2.00 PM</tt><br>
<tt>&gt; To: Bhatia, Manav (Manav)</tt><br>
<tt>&gt; Cc: <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ie=
tf.org</a></tt><br>
<tt>&gt; Subject: Re: [TICTOC] 1588overmpls-00 / MPLS profile &amp; BC</tt>=
<br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi Manav,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; A high level point is that for the pure MPLS mapping (section 5.3)=
 , I</tt><br>
<tt>&gt; wonder if what is really needed is a PTP profile for MPLS -- </tt>=
<br>
<tt>&gt; similar to</tt><br>
<tt>&gt; Annex D/E/F for IPv4/IPv6/Ethernet, respectively. =A0For </tt><br>
<tt>&gt; example the IP &amp;</tt><br>
<tt>&gt; Ethernet profiles include other information such as the port </tt>=
<br>
<tt>&gt; addressing for</tt><br>
<tt>&gt; the unicast master table and acceptable master table. =A0Without a
full</tt><br>
<tt>&gt; profile, although the intermediate notes may operate in TC, </tt><=
br>
<tt>&gt; the server,</tt><br>
<tt>&gt; client and boundary nodes may not operate successfully.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Its not clear if this draft is intended to cover all clock </tt><b=
r>
<tt>&gt; types (OC, BC &amp;</tt><br>
<tt>&gt; TC) or only TC. =A0There are many sections that talk only about </=
tt><br>
<tt>&gt; TC without</tt><br>
<tt>&gt; considering OC and BC behaviour or impact. =A0Is BC intended to </=
tt><br>
<tt>&gt; be covered as</tt><br>
<tt>&gt; a Client-side OC + Server-side OC model, or is BC excluded from</t=
t><br>
<tt>&gt; consideration in this draft? =A0Perhaps this draft should be eithe=
r</tt><br>
<tt>&gt; cleaned-up to consider all clock types or should be </tt><br>
<tt>&gt; restricted to only TC</tt><br>
<tt>&gt; clock type with OC &amp; BC out of scope.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Some specific comments</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + The abstract could be clarified to indicate there are three </tt=
><br>
<tt>&gt; mappings, not</tt><br>
<tt>&gt; two (pure MPLS, UDP/IP over MPLS and Ethernet over MPLS). =A0I
think the</tt><br>
<tt>&gt; third mapping may be under discussion, so perhaps this is prematur=
e.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + A few places in the text the phrase &quot;proper handling of </t=
t><br>
<tt>&gt; these packets&quot; or</tt><br>
<tt>&gt; &quot;properly handle PTP messages&quot; or &quot;perform proper
=A0</tt><br>
<tt>&gt; processing&quot; =A0is used to</tt><br>
<tt>&gt; mean transparent clock. =A0I would propose to remove such </tt><br=
>
<tt>&gt; language as from</tt><br>
<tt>&gt; the ITU-T studies of timing performances of PTP one could argue th=
e</tt><br>
<tt>&gt; &quot;proper&quot; way is to implement a boundary clock. =A0Where
the </tt><br>
<tt>&gt; intention is to</tt><br>
<tt>&gt; aid the designer of a TC that is fine to describe the implementati=
on</tt><br>
<tt>&gt; recommendation, but not to suggest this is the way to acheive the =
best</tt><br>
<tt>&gt; performance or even the desired way to deploy PTP over MPLS.</tt><=
br>
<tt>&gt; </tt><br>
<tt>&gt; + I would like to see a statement added in the document that the</=
tt><br>
<tt>&gt; performance aspects (e.g. the phase or frequency alignment) </tt><=
br>
<tt>&gt; are outside the</tt><br>
<tt>&gt; scope of the document.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 6, 7, 8, 10 and 13 seems to focus only on the TC </tt><b=
r>
<tt>&gt; case between</tt><br>
<tt>&gt; OC&#39;s and does not consider BC situation.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 12 text on checksums could be improved to indicate this =
only</tt><br>
<tt>&gt; applies to TC and not to OC &amp; BC.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 16 seems to address only TC clocks and not OC or BC cloc=
ks.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; + Section 16.3 implies that the only possible way to handle PTP is=
 TC,</tt><br>
<tt>&gt; excluding BC --- &quot;don&#39;t have the capability to process 15=
88 </tt><br>
<tt>&gt; packets (e.g.</tt><br>
<tt>&gt; TC processing)&quot; and &quot; =A0 Non-1588-aware LSRs ignore the
RSVP </tt><br>
<tt>&gt; 1588_PTP_LSP</tt><br>
<tt>&gt; object and just switch the MPLS packets carrying 1588 messages as =
data</tt><br>
<tt>&gt; packets and don&#39;t perform any TC processing.&quot;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Regards,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ZARLINK Semiconductor</tt><br>
<tt>&gt; Peter Meyer</tt><br>
<tt>&gt; Timing &amp; Synchronization</tt><br>
<tt>&gt; Communication Products Group</tt><br>
<tt>&gt; Office: +1-613-270-7203=A0 |=A0 Fax: +1-613-592-1010</tt><br>
<tt>&gt; <a href=3D"mailto:peter.meyer@zarlink.com" target=3D"_blank">peter=
.meyer@zarlink.com</a>
=A0| </tt></span><span lang=3D"EN-US"><a href=3D"http://www.zarlink.com" ta=
rget=3D"_blank"><tt><span style=3D"font-size: 10pt;">www.zarlink.com</span>=
</tt></a></span><span style=3D"font-size: 10pt; font-family: &quot;Courier =
New&quot;;" lang=3D"EN-US"><br>

<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;Bhatia, Manav
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0(Manav)&quot; =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0&lt;manav.bhatia@alc
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 To </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0<a href=3D"http://atel-lucent.com" targ=
et=3D"_blank">atel-lucent.com</a>&gt; =A0
=A0 =A0 =A0 =A0&quot;<a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">t=
ictoc@ietf.org</a>&quot; </tt><br>
<tt>&gt; &lt;<a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ie=
tf.org</a>&gt;
</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0Sent by: =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 cc </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0&lt;tictoc-bounces@i
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0<a href=3D"http://etf.org" target=3D"_b=
lank">etf.org</a>&gt; =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0Subject </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0[TICTOC]
=A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; draft-ietf-tictoc-1588overmpls-00.t </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A026/01/2011 11:22
=A0 =A0 =A0 =A0 =A0xt =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0AM =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </tt><br>
<tt>&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Hi,</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; We&#39;ve tried incorporating most of the comments that we receive=
d on the</tt><br>
<tt>&gt; list. Please ping me if you think we have missed some.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Would be great if the WG can go through this and provide </tt><br>
<tt>&gt; feedback on the</tt><br>
<tt>&gt; same.</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; The draft is available here:</tt><br>
<tt>&gt; </tt></span><span lang=3D"EN-US"><a href=3D"http://www.ietf.org/in=
ternet-drafts/draft-ietf-tictoc-1588over" target=3D"_blank"><tt><span style=
=3D"font-size: 10pt;">http://www.ietf.org/internet-drafts/draft-ietf-tictoc=
-1588over</span></tt></a></span><span style=3D"font-size: 10pt; font-family=
: &quot;Courier New&quot;;" lang=3D"EN-US"><br>

<tt>&gt; mpls-00.txt</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; &gt; -----Original Message-----</tt><br>
<tt>&gt; &gt; From: <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_b=
lank">tictoc-bounces@ietf.org</a></tt><br>
<tt>&gt; &gt; [</tt></span><span lang=3D"EN-US"><a href=3D"mailto:tictoc-bo=
unces@ietf.org" target=3D"_blank"><tt><span style=3D"font-size: 10pt;">mail=
to:tictoc-bounces@ietf.org</span></tt></a></span><tt><span style=3D"font-si=
ze: 10pt;" lang=3D"EN-US">] On Behalf Of </span></tt><span style=3D"font-si=
ze: 10pt; font-family: &quot;Courier New&quot;;" lang=3D"EN-US"><br>

<tt>&gt; <a href=3D"mailto:Internet-Drafts@ietf.org" target=3D"_blank">Inte=
rnet-Drafts@ietf.org</a></tt><br>
<tt>&gt; &gt; Sent: Wednesday, January 26, 2011 9.30 PM</tt><br>
<tt>&gt; &gt; To: <a href=3D"mailto:i-d-announce@ietf.org" target=3D"_blank=
">i-d-announce@ietf.org</a></tt><br>
<tt>&gt; &gt; Cc: <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tict=
oc@ietf.org</a></tt><br>
<tt>&gt; &gt; Subject: [TICTOC] I-D
Action:draft-ietf-tictoc-1588overmpls-00.txt</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; A New Internet-Draft is available from the on-line</tt><br>
<tt>&gt; &gt; Internet-Drafts directories.</tt><br>
<tt>&gt; &gt; This draft is a work item of the Timing over IP Connection</t=
t><br>
<tt>&gt; &gt; and Transfer of Clock Working Group of the IETF.</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0Title =A0 =A0
=A0 =A0 =A0 : Transporting PTP messages (1588) over</tt><br>
<tt>&gt; &gt; MPLS Networks</tt><br>
<tt>&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0Author(s) =A0 =A0
=A0 : S. Davari, et al.</tt><br>
<tt>&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0Filename =A0 =A0
=A0 =A0: draft-ietf-tictoc-1588overmpls-00.txt</tt><br>
<tt>&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0Pages =A0 =A0
=A0 =A0 =A0 : 35</tt><br>
<tt>&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0Date =A0 =A0
=A0 =A0 =A0 =A0: 2011-01-26</tt><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; &gt; This document defines the method for transporting PTP </tt><b=
r>
<tt>&gt; messages (PDUs)</tt><br>
<tt>&gt; &gt; over an MPLS network to enable a proper handling of these pac=
kets</tt><br>
<tt>&gt; &gt; (e.g. implementation of Transparent Clocks (TC)) in LSRs.</tt=
><br>
<tt>&gt; &gt;</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; Cheers, Manav</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; --</tt><br>
<tt>&gt; Manav Bhatia,</tt><br>
<tt>&gt; IP Division, Alcatel-Lucent,</tt><br>
<tt>&gt; Bangalore - India</tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; _______________________________________________</tt><br>
<tt>&gt; TICTOC mailing list</tt><br>
<tt>&gt; <a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.o=
rg</a></tt><br>
<tt>&gt; </tt></span><span lang=3D"EN-US"><a href=3D"https://www.ietf.org/m=
ailman/listinfo/tictoc" target=3D"_blank"><tt><span style=3D"font-size: 10p=
t;">https://www.ietf.org/mailman/listinfo/tictoc</span></tt></a></span><spa=
n style=3D"font-size: 10pt; font-family: &quot;Courier New&quot;;" lang=3D"=
EN-US"><br>

<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; </tt><br>
<tt>&gt; ----------</tt><br>
<tt>&gt; This email is confidential and may contain information that </tt><=
br>
<tt>&gt; is privileged and</tt><br>
<tt>&gt; exempt from disclosure by law. =A0If you have received it in </tt>=
<br>
<tt>&gt; error, please contact</tt><br>
<tt>&gt; the sender immediately by return email and then delete it </tt><br=
>
<tt>&gt; from your system; you</tt><br>
<tt>&gt; should not copy it or disclose its contents to anyone. =A0</tt><br=
>
<tt>&gt; Emails are not secure</tt><br>
<tt>&gt; and cannot be guaranteed to be error free as they can be </tt><br>
<tt>&gt; intercepted, amended,</tt><br>
<tt>&gt; lost or destroyed, or contain viruses. =A0Anyone who </tt><br>
<tt>&gt; communicates with us by email</tt><br>
<tt>&gt; is taken to accept these risks.</tt><br>
<tt>&gt; </tt><br>
<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt><a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a=
></tt><br>
</span><span lang=3D"EN-US"><a href=3D"https://www.ietf.org/mailman/listinf=
o/tictoc" target=3D"_blank"><tt><span style=3D"font-size: 10pt;">https://ww=
w.ietf.org/mailman/listinfo/tictoc</span></tt></a></span><span style=3D"fon=
t-size: 10pt; font-family: &quot;Courier New&quot;;" lang=3D"EN-US"><br>

<tt>_______________________________________________</tt><br>
<tt>TICTOC mailing list</tt><br>
<tt><a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a=
></tt><br>
</span><span lang=3D"EN-US"><a href=3D"https://www.ietf.org/mailman/listinf=
o/tictoc" target=3D"_blank"><tt><span style=3D"font-size: 10pt;">https://ww=
w.ietf.org/mailman/listinfo/tictoc</span></tt></a></span></p>

</div>

</div>

</div>

</div>

<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a></p>

</div>

<p class=3D"MsoNormal">=A0</p>

</div>

</div></div></div>

</div>


</blockquote></div><br><div style=3D"visibility: hidden; left: -5000px; pos=
ition: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top:=
 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10p=
x; text-align: left; line-height: 130%;" id=3D"avg_ls_inline_popup">
</div></div>

--0016368e3059da0eba049c2a3494--

From odonoghue@isoc.org  Tue Feb 15 01:02:30 2011
Return-Path: <odonoghue@isoc.org>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 759B93A6AE5 for <tictoc@core3.amsl.com>; Tue, 15 Feb 2011 01:02:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CsmPDf5mpMBp for <tictoc@core3.amsl.com>; Tue, 15 Feb 2011 01:02:29 -0800 (PST)
Received: from smtp125.iad.emailsrvr.com (smtp125.iad.emailsrvr.com [207.97.245.125]) by core3.amsl.com (Postfix) with ESMTP id 036B33A6AE4 for <tictoc@ietf.org>; Tue, 15 Feb 2011 01:02:29 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp42.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 20B251484C1; Tue, 15 Feb 2011 04:01:56 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp42.relay.iad1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id 6BEF5148373;  Tue, 15 Feb 2011 04:01:55 -0500 (EST)
Message-ID: <4D5A4105.9080609@isoc.org>
Date: Tue, 15 Feb 2011 10:01:57 +0100
From: Karen O'Donoghue <odonoghue@isoc.org>
Organization: ISOC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: tictoc@ietf.org
Content-Type: multipart/alternative; boundary="------------070700030309000506090800"
Subject: [TICTOC] tictoc webex conference, Tuesday 22 February, 1700 UTC (0900 PST/1200 EST/1800 CET)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: odonoghue@isoc.org
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Feb 2011 09:02:30 -0000

This is a multi-part message in MIME format.
--------------070700030309000506090800
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Folks,

As discussed at our last meeting, we will be meeting again on Tuesday, 
22 February, 2011. This meeting will be one hour later than our 
customary meeting time to accommodate those attending ITU-T meetings. 
The webex information is included below.

Regards,
Karen


Hello ,

IETF Secretariat invites you to attend this online meeting.

Topic: TICTOC
Date: Tuesday, February 22, 2011
Time: 9:00 am, Pacific Standard Time (San Francisco, GMT-08:00)
Meeting Number: 964 368 281
Meeting Password: (This meeting does not require a password.)


-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to 
https://workgreen.webex.com/workgreen/j.php?ED=150774992&UID=1201204917&RT=MiM0 
<https://workgreen.webex.com/workgreen/j.php?ED=150774992&UID=1201204917&RT=MiM0> 

2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: (This meeting 
does not require a password.)
4. Click "Join".

To view in other time zones or languages, please click the link:
https://workgreen.webex.com/workgreen/j.php?ED=150774992&UID=1201204917&ORT=MiM0 
<https://workgreen.webex.com/workgreen/j.php?ED=150774992&UID=1201204917&ORT=MiM0> 


-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the 
meeting, or call the number below and enter the access code.
Call-in toll number (US/Canada): 1-408-792-6300
Global call-in numbers: 
https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&ED=150774992&tollFree=0 
<https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&ED=150774992&tollFree=0> 


Access code:964 368 281

-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://workgreen.webex.com/workgreen/mc
2. On the left navigation bar, click "Support".

You can contact me at:
amorris@amsl.com <mailto:amorris@amsl.com>
1-510-492-4081

To add this meeting to your calendar program (for example Microsoft 
Outlook), click this link:
https://workgreen.webex.com/workgreen/j.php?ED=150774992&UID=1201204917&ICS=MI&LD=1&RD=2&ST=1&SHA2=fV4bYOmQ8z0Xn9u86-jURMJxkQehMQ6QTEegoA21Wxk=&RT=MiM0 
<https://workgreen.webex.com/workgreen/j.php?ED=150774992&UID=1201204917&ICS=MI&LD=1&RD=2&ST=1&SHA2=fV4bYOmQ8z0Xn9u86-jURMJxkQehMQ6QTEegoA21Wxk=&RT=MiM0> 


The playback of UCF (Universal Communications Format) rich media files 
requires appropriate players. To view this type of rich media files in 
the meeting, please check whether you have the players installed on your 
computer by going to 
https://workgreen.webex.com/workgreen/systemdiagnosis.php

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com

CCP:+14087926300x964368281#

IMPORTANT NOTICE: This WebEx service includes a feature that allows 
audio and any documents and other materials exchanged or viewed during 
the session to be recorded. By joining this session, you automatically 
consent to such recordings. If you do not consent to the recording, 
discuss your concerns with the meeting host prior to the start of the 
recording or do not join the session. Please note that any such 
recordings may be subject to discovery in the event of litigation.


--------------070700030309000506090800
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Folks,<br>
    <br>
    As discussed at our last meeting, we will be meeting again on
    Tuesday, 22 February, 2011. This meeting will be one hour later than
    our customary meeting time to accommodate those attending ITU-T
    meetings. The webex information is included below. <br>
    <br>
    Regards,<br>
    Karen<br>
    <br>
    <font face="Tahoma, Arial, sans-serif, Helvetica, Geneva" size="2"><br>
      Hello , <br>
      <br>
      IETF Secretariat invites you to attend this online meeting. <br>
      <br>
      Topic: TICTOC <br>
      Date: Tuesday, February 22, 2011 <br>
      Time: 9:00 am, Pacific Standard Time (San Francisco, GMT-08:00) <br>
      Meeting Number: 964 368 281 <br>
      Meeting Password: (This meeting does not require a password.) <br>
      <br>
      <br>
      ------------------------------------------------------- <br>
      To join the online meeting (Now from mobile devices!) <br>
      ------------------------------------------------------- <br>
      1. Go to <a moz-do-not-send="true"
href="https://workgreen.webex.com/workgreen/j.php?ED=150774992&amp;UID=1201204917&amp;RT=MiM0"
        target="_blank">https://workgreen.webex.com/workgreen/j.php?ED=150774992&amp;UID=1201204917&amp;RT=MiM0</a>
      <br>
      2. If requested, enter your name and email address. <br>
      3. If a password is required, enter the meeting password: (This
      meeting does not require a password.) <br>
      4. Click "Join". <br>
      <br>
      To view in other time zones or languages, please click the link: <br>
      <a moz-do-not-send="true"
href="https://workgreen.webex.com/workgreen/j.php?ED=150774992&amp;UID=1201204917&amp;ORT=MiM0"
        target="_blank">https://workgreen.webex.com/workgreen/j.php?ED=150774992&amp;UID=1201204917&amp;ORT=MiM0</a>
      <br>
      <br>
      ------------------------------------------------------- <br>
      To join the audio conference only <br>
      ------------------------------------------------------- <br>
      To receive a call back, provide your phone number when you join
      the meeting, or call the number below and enter the access code. <br>
      Call-in toll number (US/Canada): 1-408-792-6300 <br>
      Global call-in numbers: <a moz-do-not-send="true"
href="https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&amp;ED=150774992&amp;tollFree=0"
        target="_blank">https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&amp;ED=150774992&amp;tollFree=0</a>
      <br>
      <br>
      Access code:964 368 281 <br>
      <br>
      ------------------------------------------------------- <br>
      For assistance <br>
      ------------------------------------------------------- <br>
      1. Go to <a moz-do-not-send="true"
        href="https://workgreen.webex.com/workgreen/mc" target="_blank">https://workgreen.webex.com/workgreen/mc</a>
      <br>
      2. On the left navigation bar, click "Support". <br>
      <br>
      You can contact me at: <br>
      <a moz-do-not-send="true" href="mailto:amorris@amsl.com">amorris@amsl.com</a>
      <br>
      1-510-492-4081 <br>
      <br>
      To add this meeting to your calendar program (for example
      Microsoft Outlook), click this link: <br>
      <a moz-do-not-send="true"
href="https://workgreen.webex.com/workgreen/j.php?ED=150774992&amp;UID=1201204917&amp;ICS=MI&amp;LD=1&amp;RD=2&amp;ST=1&amp;SHA2=fV4bYOmQ8z0Xn9u86-jURMJxkQehMQ6QTEegoA21Wxk=&amp;RT=MiM0"
        target="_blank">https://workgreen.webex.com/workgreen/j.php?ED=150774992&amp;UID=1201204917&amp;ICS=MI&amp;LD=1&amp;RD=2&amp;ST=1&amp;SHA2=fV4bYOmQ8z0Xn9u86-jURMJxkQehMQ6QTEegoA21Wxk=&amp;RT=MiM0</a>
      <br>
      <br>
      The playback of UCF (Universal Communications Format) rich media
      files requires appropriate players. To view this type of rich
      media files in the meeting, please check whether you have the
      players installed on your computer by going to <a
        moz-do-not-send="true"
        href="https://workgreen.webex.com/workgreen/systemdiagnosis.php"
        target="_blank">https://workgreen.webex.com/workgreen/systemdiagnosis.php</a>
      <br>
      <br>
      Sign up for a free trial of WebEx <br>
      <a moz-do-not-send="true"
        href="http://www.webex.com/go/mcemfreetrial" target="_blank">http://www.webex.com/go/mcemfreetrial</a>
      <br>
      <br>
      <a moz-do-not-send="true" href="http://www.webex.com"
        target="_blank">http://www.webex.com</a> <br>
      <br>
      CCP:+14087926300x964368281# <br>
      <br>
      IMPORTANT NOTICE: This WebEx service includes a feature that
      allows audio and any documents and other materials exchanged or
      viewed during the session to be recorded. By joining this session,
      you automatically consent to such recordings. If you do not
      consent to the recording, discuss your concerns with the meeting
      host prior to the start of the recording or do not join the
      session. Please note that any such recordings may be subject to
      discovery in the event of litigation. <br>
    </font><br>
  </body>
</html>

--------------070700030309000506090800--

From stefano.ruffini@ericsson.com  Mon Feb 21 23:20:39 2011
Return-Path: <stefano.ruffini@ericsson.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C97F3A67ED for <tictoc@core3.amsl.com>; Mon, 21 Feb 2011 23:20:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KhBXY-rzCZt0 for <tictoc@core3.amsl.com>; Mon, 21 Feb 2011 23:20:37 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 1260F3A67E7 for <tictoc@ietf.org>; Mon, 21 Feb 2011 23:20:36 -0800 (PST)
X-AuditID: c1b4fb3d-b7c78ae000005844-fa-4d6363ef7422
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 8B.DE.22596.FE3636D4; Tue, 22 Feb 2011 08:21:19 +0100 (CET)
Received: from ESESSCMS0360.eemea.ericsson.se ([169.254.1.137]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Tue, 22 Feb 2011 08:21:19 +0100
From: Stefano Ruffini <stefano.ruffini@ericsson.com>
To: "odonoghue@isoc.org" <odonoghue@isoc.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Tue, 22 Feb 2011 08:21:17 +0100
Thread-Topic: [TICTOC] tictoc webex conference, Tuesday 22 February, 1700 UTC (0900 PST/1200 EST/1800 CET)
Thread-Index: AcvM7ybGB7hS9DsXTtmNNz2ncSMLdgFcWKKw
Message-ID: <28C9B1CD4D27844E9CD8F02BFEB705640752893D04@ESESSCMS0360.eemea.ericsson.se>
References: <4D5A4105.9080609@isoc.org>
In-Reply-To: <4D5A4105.9080609@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_28C9B1CD4D27844E9CD8F02BFEB705640752893D04ESESSCMS0360e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [TICTOC] tictoc webex conference, Tuesday 22 February, 1700 UTC (0900 PST/1200 EST/1800 CET)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 22 Feb 2011 07:20:39 -0000

--_000_28C9B1CD4D27844E9CD8F02BFEB705640752893D04ESESSCMS0360e_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All

for people attending the ITU-T meeting and plan to attend the TICTOC meetin=
g today, we have room H2 in the Montbrillant building .

Best Regards
Stefano

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Karen O'Donoghue
Sent: marted=EC 15 febbraio 2011 10.02
To: tictoc@ietf.org
Subject: [TICTOC] tictoc webex conference, Tuesday 22 February, 1700 UTC (0=
900 PST/1200 EST/1800 CET)

Folks,

As discussed at our last meeting, we will be meeting again on Tuesday, 22 F=
ebruary, 2011. This meeting will be one hour later than our customary meeti=
ng time to accommodate those attending ITU-T meetings. The webex informatio=
n is included below.

Regards,
Karen


Hello ,

IETF Secretariat invites you to attend this online meeting.

Topic: TICTOC
Date: Tuesday, February 22, 2011
Time: 9:00 am, Pacific Standard Time (San Francisco, GMT-08:00)
Meeting Number: 964 368 281
Meeting Password: (This meeting does not require a password.)


-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&UID=3D1=
201204917&RT=3DMiM0
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: (This meeting doe=
s not require a password.)
4. Click "Join".

To view in other time zones or languages, please click the link:
https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&UID=3D1201204917=
&ORT=3DMiM0

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll number (US/Canada): 1-408-792-6300
Global call-in numbers: https://workgreen.webex.com/workgreen/globalcallin.=
php?serviceType=3DMC&ED=3D150774992&tollFree=3D0

Access code:964 368 281

-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://workgreen.webex.com/workgreen/mc
2. On the left navigation bar, click "Support".

You can contact me at:
amorris@amsl.com<mailto:amorris@amsl.com>
1-510-492-4081

To add this meeting to your calendar program (for example Microsoft Outlook=
), click this link:
https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&UID=3D1201204917=
&ICS=3DMI&LD=3D1&RD=3D2&ST=3D1&SHA2=3DfV4bYOmQ8z0Xn9u86-jURMJxkQehMQ6QTEego=
A21Wxk=3D&RT=3DMiM0

The playback of UCF (Universal Communications Format) rich media files requ=
ires appropriate players. To view this type of rich media files in the meet=
ing, please check whether you have the players installed on your computer b=
y going to https://workgreen.webex.com/workgreen/systemdiagnosis.php

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com

CCP:+14087926300x964368281#

IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent to the recording, discuss your concerns =
with the meeting host prior to the start of the recording or do not join th=
e session. Please note that any such recordings may be subject to discovery=
 in the event of litigation.


--_000_28C9B1CD4D27844E9CD8F02BFEB705640752893D04ESESSCMS0360e_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.6001.18527" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D265171707-22022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi All</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D265171707-22022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D265171707-22022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>for people attending the ITU-T meeting and plan to=
 attend=20
the TICTOC meeting today, we have room H2 in the Montbrillant building=20
.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D265171707-22022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D265171707-22022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Best Regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D265171707-22022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Stefano</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> tictoc-bounces@ietf.org=20
[mailto:tictoc-bounces@ietf.org] <B>On Behalf Of </B>Karen=20
O'Donoghue<BR><B>Sent:</B> marted=EC 15 febbraio 2011 10.02<BR><B>To:</B>=20
tictoc@ietf.org<BR><B>Subject:</B> [TICTOC] tictoc webex conference, Tuesda=
y 22=20
February, 1700 UTC (0900 PST/1200 EST/1800 CET)<BR></FONT><BR></DIV>
<DIV></DIV>Folks,<BR><BR>As discussed at our last meeting, we will be meeti=
ng=20
again on Tuesday, 22 February, 2011. This meeting will be one hour later th=
an=20
our customary meeting time to accommodate those attending ITU-T meetings. T=
he=20
webex information is included below. <BR><BR>Regards,<BR>Karen<BR><BR><FONT=
=20
face=3D"Tahoma, Arial, sans-serif, Helvetica, Geneva" size=3D2><BR>Hello ,=
=20
<BR><BR>IETF Secretariat invites you to attend this online meeting.=20
<BR><BR>Topic: TICTOC <BR>Date: Tuesday, February 22, 2011 <BR>Time: 9:00 a=
m,=20
Pacific Standard Time (San Francisco, GMT-08:00) <BR>Meeting Number: 964 36=
8 281=20
<BR>Meeting Password: (This meeting does not require a password.)=20
<BR><BR><BR>------------------------------------------------------- <BR>To =
join=20
the online meeting (Now from mobile devices!)=20
<BR>------------------------------------------------------- <BR>1. Go to <A=
=20
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&amp;UID=
=3D1201204917&amp;RT=3DMiM0"=20
target=3D_blank=20
moz-do-not-send=3D"true">https://workgreen.webex.com/workgreen/j.php?ED=3D1=
50774992&amp;UID=3D1201204917&amp;RT=3DMiM0</A>=20
<BR>2. If requested, enter your name and email address. <BR>3. If a passwor=
d is=20
required, enter the meeting password: (This meeting does not require a=20
password.) <BR>4. Click "Join". <BR><BR>To view in other time zones or=20
languages, please click the link: <BR><A=20
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&amp;UID=
=3D1201204917&amp;ORT=3DMiM0"=20
target=3D_blank=20
moz-do-not-send=3D"true">https://workgreen.webex.com/workgreen/j.php?ED=3D1=
50774992&amp;UID=3D1201204917&amp;ORT=3DMiM0</A>=20
<BR><BR>------------------------------------------------------- <BR>To join=
 the=20
audio conference only=20
<BR>------------------------------------------------------- <BR>To receive =
a=20
call back, provide your phone number when you join the meeting, or call the=
=20
number below and enter the access code. <BR>Call-in toll number (US/Canada)=
:=20
1-408-792-6300 <BR>Global call-in numbers: <A=20
href=3D"https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=
=3DMC&amp;ED=3D150774992&amp;tollFree=3D0"=20
target=3D_blank=20
moz-do-not-send=3D"true">https://workgreen.webex.com/workgreen/globalcallin=
.php?serviceType=3DMC&amp;ED=3D150774992&amp;tollFree=3D0</A>=20
<BR><BR>Access code:964 368 281=20
<BR><BR>------------------------------------------------------- <BR>For=20
assistance <BR>------------------------------------------------------- <BR>=
1. Go=20
to <A href=3D"https://workgreen.webex.com/workgreen/mc" target=3D_blank=20
moz-do-not-send=3D"true">https://workgreen.webex.com/workgreen/mc</A> <BR>2=
. On=20
the left navigation bar, click "Support". <BR><BR>You can contact me at: <B=
R><A=20
href=3D"mailto:amorris@amsl.com" moz-do-not-send=3D"true">amorris@amsl.com<=
/A>=20
<BR>1-510-492-4081 <BR><BR>To add this meeting to your calendar program (fo=
r=20
example Microsoft Outlook), click this link: <BR><A=20
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&amp;UID=
=3D1201204917&amp;ICS=3DMI&amp;LD=3D1&amp;RD=3D2&amp;ST=3D1&amp;SHA2=3DfV4b=
YOmQ8z0Xn9u86-jURMJxkQehMQ6QTEegoA21Wxk=3D&amp;RT=3DMiM0"=20
target=3D_blank=20
moz-do-not-send=3D"true">https://workgreen.webex.com/workgreen/j.php?ED=3D1=
50774992&amp;UID=3D1201204917&amp;ICS=3DMI&amp;LD=3D1&amp;RD=3D2&amp;ST=3D1=
&amp;SHA2=3DfV4bYOmQ8z0Xn9u86-jURMJxkQehMQ6QTEegoA21Wxk=3D&amp;RT=3DMiM0</A=
>=20
<BR><BR>The playback of UCF (Universal Communications Format) rich media fi=
les=20
requires appropriate players. To view this type of rich media files in the=
=20
meeting, please check whether you have the players installed on your comput=
er by=20
going to <A href=3D"https://workgreen.webex.com/workgreen/systemdiagnosis.p=
hp"=20
target=3D_blank=20
moz-do-not-send=3D"true">https://workgreen.webex.com/workgreen/systemdiagno=
sis.php</A>=20
<BR><BR>Sign up for a free trial of WebEx <BR><A=20
href=3D"http://www.webex.com/go/mcemfreetrial" target=3D_blank=20
moz-do-not-send=3D"true">http://www.webex.com/go/mcemfreetrial</A> <BR><BR>=
<A=20
href=3D"http://www.webex.com" target=3D_blank=20
moz-do-not-send=3D"true">http://www.webex.com</A>=20
<BR><BR>CCP:+14087926300x964368281# <BR><BR>IMPORTANT NOTICE: This WebEx se=
rvice=20
includes a feature that allows audio and any documents and other materials=
=20
exchanged or viewed during the session to be recorded. By joining this sess=
ion,=20
you automatically consent to such recordings. If you do not consent to the=
=20
recording, discuss your concerns with the meeting host prior to the start o=
f the=20
recording or do not join the session. Please note that any such recordings =
may=20
be subject to discovery in the event of litigation.=20
<BR></FONT><BR></BODY></HTML>

--_000_28C9B1CD4D27844E9CD8F02BFEB705640752893D04ESESSCMS0360e_--

From davari@broadcom.com  Tue Feb 22 09:46:48 2011
Return-Path: <davari@broadcom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A1F383A6940 for <tictoc@core3.amsl.com>; Tue, 22 Feb 2011 09:46:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.473
X-Spam-Level: 
X-Spam-Status: No, score=-2.473 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7QAZr0-ZN21I for <tictoc@core3.amsl.com>; Tue, 22 Feb 2011 09:46:41 -0800 (PST)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id AA7E63A68E7 for <tictoc@ietf.org>; Tue, 22 Feb 2011 09:46:41 -0800 (PST)
Received: from [10.16.192.224] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Tue, 22 Feb 2011 09:49:13 -0800
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Tue, 22 Feb 2011 09:47:12 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "Stefano Ruffini" <stefano.ruffini@ericsson.com>, "odonoghue@isoc.org" <odonoghue@isoc.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Tue, 22 Feb 2011 09:47:09 -0800
Thread-Topic: [TICTOC] tictoc webex conference, Tuesday 22 February, 1700 UTC (0900 PST/1200 EST/1800 CET)
Thread-Index: AcvM7ybGB7hS9DsXTtmNNz2ncSMLdgFcWKKwABX6wwA=
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6942ACA1C29@SJEXCHCCR02.corp.ad.broadcom.com>
References: <4D5A4105.9080609@isoc.org> <28C9B1CD4D27844E9CD8F02BFEB705640752893D04@ESESSCMS0360.eemea.ericsson.se>
In-Reply-To: <28C9B1CD4D27844E9CD8F02BFEB705640752893D04@ESESSCMS0360.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 617D289326W1908590-01-01
Content-Type: multipart/alternative; boundary=_000_2C2F1EBA8050E74EA81502D5740B4BD6942ACA1C29SJEXCHCCR02co_
Subject: Re: [TICTOC] tictoc webex conference, Tuesday 22 February, 1700 UTC (0900 PST/1200 EST/1800 CET)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 22 Feb 2011 17:46:48 -0000

--_000_2C2F1EBA8050E74EA81502D5740B4BD6942ACA1C29SJEXCHCCR02co_
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Stefano,

Isn't the conf call at 10:00 AM PT?

Thx
Shahram

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Stefano Ruffini
Sent: Monday, February 21, 2011 11:21 PM
To: odonoghue@isoc.org; tictoc@ietf.org
Subject: Re: [TICTOC] tictoc webex conference, Tuesday 22 February, 1700 UT=
C (0900 PST/1200 EST/1800 CET)

Hi All

for people attending the ITU-T meeting and plan to attend the TICTOC meetin=
g today, we have room H2 in the Montbrillant building .

Best Regards
Stefano

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Karen O'Donoghue
Sent: marted=EC 15 febbraio 2011 10.02
To: tictoc@ietf.org
Subject: [TICTOC] tictoc webex conference, Tuesday 22 February, 1700 UTC (0=
900 PST/1200 EST/1800 CET)
Folks,

As discussed at our last meeting, we will be meeting again on Tuesday, 22 F=
ebruary, 2011. This meeting will be one hour later than our customary meeti=
ng time to accommodate those attending ITU-T meetings. The webex informatio=
n is included below.

Regards,
Karen


Hello ,

IETF Secretariat invites you to attend this online meeting.

Topic: TICTOC
Date: Tuesday, February 22, 2011
Time: 9:00 am, Pacific Standard Time (San Francisco, GMT-08:00)
Meeting Number: 964 368 281
Meeting Password: (This meeting does not require a password.)


-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&UID=3D1=
201204917&RT=3DMiM0
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: (This meeting doe=
s not require a password.)
4. Click "Join".

To view in other time zones or languages, please click the link:
https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&UID=3D1201204917=
&ORT=3DMiM0

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll number (US/Canada): 1-408-792-6300
Global call-in numbers: https://workgreen.webex.com/workgreen/globalcallin.=
php?serviceType=3DMC&ED=3D150774992&tollFree=3D0

Access code:964 368 281

-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://workgreen.webex.com/workgreen/mc
2. On the left navigation bar, click "Support".

You can contact me at:
amorris@amsl.com<mailto:amorris@amsl.com>
1-510-492-4081

To add this meeting to your calendar program (for example Microsoft Outlook=
), click this link:
https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&UID=3D1201204917=
&ICS=3DMI&LD=3D1&RD=3D2&ST=3D1&SHA2=3DfV4bYOmQ8z0Xn9u86-jURMJxkQehMQ6QTEego=
A21Wxk=3D&RT=3DMiM0

The playback of UCF (Universal Communications Format) rich media files requ=
ires appropriate players. To view this type of rich media files in the meet=
ing, please check whether you have the players installed on your computer b=
y going to https://workgreen.webex.com/workgreen/systemdiagnosis.php

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com

CCP:+14087926300x964368281#

IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent to the recording, discuss your concerns =
with the meeting host prior to the start of the recording or do not join th=
e session. Please note that any such recordings may be subject to discovery=
 in the event of litigation.

--_000_2C2F1EBA8050E74EA81502D5740B4BD6942ACA1C29SJEXCHCCR02co_
Content-Type: text/html;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>

<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Hi Stefano,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Isn&#8217;t the conf call at 10:00 AM PT?<o:p></o:p></span><=
/p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Thx<br>
Shahram<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";
color:windowtext'>From:</span></b><span style=3D'font-size:10.0pt;font-fami=
ly:
"Tahoma","sans-serif";color:windowtext'> tictoc-bounces@ietf.org
[mailto:tictoc-bounces@ietf.org] <b>On Behalf Of </b>Stefano Ruffini<br>
<b>Sent:</b> Monday, February 21, 2011 11:21 PM<br>
<b>To:</b> odonoghue@isoc.org; tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] tictoc webex conference, Tuesday 22 February, =
1700
UTC (0900 PST/1200 EST/1800 CET)<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Hi All</span><o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>for people attending the ITU-T meeting and plan to attend the
TICTOC meeting today, we have room H2 in the Montbrillant building .</span>=
<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Best Regards</span><o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Stefano</span><o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span style=3D'font-=
size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size=
:10.0pt;
font-family:"Tahoma","sans-serif"'> tictoc-bounces@ietf.org
[mailto:tictoc-bounces@ietf.org] <b>On Behalf Of </b>Karen O'Donoghue<br>
<b>Sent:</b> marted=EC 15 febbraio 2011 10.02<br>
<b>To:</b> tictoc@ietf.org<br>
<b>Subject:</b> [TICTOC] tictoc webex conference, Tuesday 22 February, 1700=
 UTC
(0900 PST/1200 EST/1800 CET)</span><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Folks,<br>
<br>
As discussed at our last meeting, we will be meeting again on Tuesday, 22
February, 2011. This meeting will be one hour later than our customary meet=
ing
time to accommodate those attending ITU-T meetings. The webex information i=
s
included below. <br>
<br>
Regards,<br>
Karen<br>
<br>
<span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br>
Hello , <br>
<br>
IETF Secretariat invites you to attend this online meeting. <br>
<br>
Topic: TICTOC <br>
Date: Tuesday, February 22, 2011 <br>
Time: 9:00 am, Pacific Standard Time (San Francisco, GMT-08:00) <br>
Meeting Number: 964 368 281 <br>
Meeting Password: (This meeting does not require a password.) <br>
<br>
<br>
------------------------------------------------------- <br>
To join the online meeting (Now from mobile devices!) <br>
------------------------------------------------------- <br>
1. Go to <a
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&amp;UID=
=3D1201204917&amp;RT=3DMiM0"
target=3D"_blank">https://workgreen.webex.com/workgreen/j.php?ED=3D15077499=
2&amp;UID=3D1201204917&amp;RT=3DMiM0</a>
<br>
2. If requested, enter your name and email address. <br>
3. If a password is required, enter the meeting password: (This meeting doe=
s
not require a password.) <br>
4. Click &quot;Join&quot;. <br>
<br>
To view in other time zones or languages, please click the link: <br>
<a
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&amp;UID=
=3D1201204917&amp;ORT=3DMiM0"
target=3D"_blank">https://workgreen.webex.com/workgreen/j.php?ED=3D15077499=
2&amp;UID=3D1201204917&amp;ORT=3DMiM0</a>
<br>
<br>
------------------------------------------------------- <br>
To join the audio conference only <br>
------------------------------------------------------- <br>
To receive a call back, provide your phone number when you join the meeting=
, or
call the number below and enter the access code. <br>
Call-in toll number (US/Canada): 1-408-792-6300 <br>
Global call-in numbers: <a
href=3D"https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=
=3DMC&amp;ED=3D150774992&amp;tollFree=3D0"
target=3D"_blank">https://workgreen.webex.com/workgreen/globalcallin.php?se=
rviceType=3DMC&amp;ED=3D150774992&amp;tollFree=3D0</a>
<br>
<br>
Access code:964 368 281 <br>
<br>
------------------------------------------------------- <br>
For assistance <br>
------------------------------------------------------- <br>
1. Go to <a href=3D"https://workgreen.webex.com/workgreen/mc" target=3D"_bl=
ank">https://workgreen.webex.com/workgreen/mc</a>
<br>
2. On the left navigation bar, click &quot;Support&quot;. <br>
<br>
You can contact me at: <br>
<a href=3D"mailto:amorris@amsl.com">amorris@amsl.com</a> <br>
1-510-492-4081 <br>
<br>
To add this meeting to your calendar program (for example Microsoft Outlook=
),
click this link: <br>
<a
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D150774992&amp;UID=
=3D1201204917&amp;ICS=3DMI&amp;LD=3D1&amp;RD=3D2&amp;ST=3D1&amp;SHA2=3DfV4b=
YOmQ8z0Xn9u86-jURMJxkQehMQ6QTEegoA21Wxk=3D&amp;RT=3DMiM0"
target=3D"_blank">https://workgreen.webex.com/workgreen/j.php?ED=3D15077499=
2&amp;UID=3D1201204917&amp;ICS=3DMI&amp;LD=3D1&amp;RD=3D2&amp;ST=3D1&amp;SH=
A2=3DfV4bYOmQ8z0Xn9u86-jURMJxkQehMQ6QTEegoA21Wxk=3D&amp;RT=3DMiM0</a>
<br>
<br>
The playback of UCF (Universal Communications Format) rich media files requ=
ires
appropriate players. To view this type of rich media files in the meeting,
please check whether you have the players installed on your computer by goi=
ng
to <a href=3D"https://workgreen.webex.com/workgreen/systemdiagnosis.php"
target=3D"_blank">https://workgreen.webex.com/workgreen/systemdiagnosis.php=
</a> <br>
<br>
Sign up for a free trial of WebEx <br>
<a href=3D"http://www.webex.com/go/mcemfreetrial" target=3D"_blank">http://=
www.webex.com/go/mcemfreetrial</a>
<br>
<br>
<a href=3D"http://www.webex.com" target=3D"_blank">http://www.webex.com</a>=
 <br>
<br>
CCP:+14087926300x964368281# <br>
<br>
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd
any documents and other materials exchanged or viewed during the session to=
 be
recorded. By joining this session, you automatically consent to such
recordings. If you do not consent to the recording, discuss your concerns w=
ith
the meeting host prior to the start of the recording or do not join the
session. Please note that any such recordings may be subject to discovery i=
n
the event of litigation. </span><o:p></o:p></p>

</div>

</body>

</html>

--_000_2C2F1EBA8050E74EA81502D5740B4BD6942ACA1C29SJEXCHCCR02co_--

