Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt
Kevin Gross <kevin.gross@avanw.com> Mon, 10 June 2013 17:10 UTC
Return-Path: <kevin.gross@avanw.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F1CD21F9649 for <tictoc@ietfa.amsl.com>; Mon, 10 Jun 2013 10:10:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.186
X-Spam-Level:
X-Spam-Status: No, score=0.186 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1LXnnm534fFt for <tictoc@ietfa.amsl.com>; Mon, 10 Jun 2013 10:10:22 -0700 (PDT)
Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:56]) by ietfa.amsl.com (Postfix) with ESMTP id B58FE21F86AE for <tictoc@ietf.org>; Mon, 10 Jun 2013 10:10:21 -0700 (PDT)
Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta06.emeryville.ca.mail.comcast.net with comcast id mebA1l0050EPchoA6hAMiN; Mon, 10 Jun 2013 17:10:21 +0000
Received: from mail-ie0-x234.google.com ([IPv6:2607:f8b0:4001:c03::234]) by omta01.emeryville.ca.mail.comcast.net with comcast id mhAL1l01458t75Q8MhAML5; Mon, 10 Jun 2013 17:10:21 +0000
Received: by mail-ie0-f180.google.com with SMTP id f4so11804071iea.25 for <tictoc@ietf.org>; Mon, 10 Jun 2013 10:10:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xOvyOTHtdsXTZObJj20YA9DCNIH/PibeZJi3CdG9fB0=; b=PUbXPiEVYqCHhj6On5+dISM0+MRFUKVwpygNNfRqzkoqU2bdShAELkt0fBU9z3iRm2 dhvVBgoENMnVdKKbEY9eYqgC66jez2GTg8Ouxu53ugAcy9fC3pWWVzxijBJTESVWLUg+ hplau6fWb+zJQ6QGCfAa7sqa5GxuCBXZiH353ZwSzqX4mIHfCeSNgkHmjoZC7t+sf86c k6Crht8FUnUel3tCvneG8Bnxl5DSEq4uaufBDQSorIqK8Med0GNAofyrVFpymFBUjsQW mwFajRp/LG09/8Qlz9qsEc0DILineq0IvIVRGulM/SXkHQx/Z/jb52D6uOuLFuKi0kmj qrRQ==
MIME-Version: 1.0
X-Received: by 10.50.102.67 with SMTP id fm3mr4569816igb.5.1370884220609; Mon, 10 Jun 2013 10:10:20 -0700 (PDT)
Received: by 10.50.149.199 with HTTP; Mon, 10 Jun 2013 10:10:20 -0700 (PDT)
In-Reply-To: <4A4385BFBA1BC54C863E7394BD1AECB36EB1C82C@SJC-MBX-01.symmetricom.com>
References: <5194FE2F.2060504@isoc.org> <CALw1_Q3DxKFc+oNFj_0iyDPp4m59hNS3--7R+nX_i1OzOaeT-g@mail.gmail.com> <4A4385BFBA1BC54C863E7394BD1AECB36EB1C82C@SJC-MBX-01.symmetricom.com>
Date: Mon, 10 Jun 2013 11:10:20 -0600
Message-ID: <CALw1_Q1D+iCamS4j1C=GEvsehJ1wYTbFz9y34m12nurW7RgfNQ@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: Tim Frost <tfrost@symmetricom.com>
Content-Type: multipart/alternative; boundary="047d7b10ca13ff806204decfda85"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1370884221; bh=xOvyOTHtdsXTZObJj20YA9DCNIH/PibeZJi3CdG9fB0=; h=Received:Received:Received:MIME-Version:Received:Date:Message-ID: Subject:From:To:Content-Type; b=LTKRkYL+Oz0z5zbTnku46EXsCtV0uwl+9j0qYaeAEdR11Ty23FyuelbM6QpmBSNfT fgV1oZkKsZOi64NQ1UdocgyRPvh1Fl72kc3Van77V2oIn1JEDv14/SC6Vj4PT4Ug9B h2eA0D6MmU74uxhDFpv4fNXNtNozhOB/1hqBrrzG+fHPZ3PJgqCd/tGaqEUHi5siLW TOdFrR8cw+7MGQ2+u4SrWs1N83xAKJkuWuKQ4ztZNLwOOdmI1G6XoHvIhFjFHC1xIT w9NaYwOcDm3mb+3pQzzRKHdwq5LUcmT0op1wA2rQ4zhAzxrH2IStm2VUXpauMe0unc QSbHSZPtPsuHA==
Cc: "tictoc@ietf.org" <tictoc@ietf.org>, Karen ODonoghue <odonoghue@isoc.org>
Subject: Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 17:10:26 -0000
Thanks for addressing my comments. It looks like there are two outstanding. 1. ClockInstanceType and 2. ClockProfileType It sounds like you intend to address (1) in a future revision. With regards to (2), I think you misunderstand how the profileIdentifier works. Please have a look at Section 19.3.3 of IEEE 1588-2008. This is an EUI-48, not merely an OUI. Organizations can change the bottom 24 bits to indicate new profiles or revisions of existing ones. Maintaining our own enumeration of profiles does not seem like a feasible undertaking. Kevin Gross +1-303-447-0517 Media Network Consultant AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org On Fri, May 17, 2013 at 2:33 AM, Tim Frost <tfrost@symmetricom.com> wrote: > Hi Kevin,**** > > ** ** > > Thank you for taking the time to go through this MIB. We did consider your > comments, and they were addressed in -05 (the latest version, and the > subject of the last call). I’ve gone through each of your comments below; > it looks like we missed one, and decided against another, but the remainder > have been done.**** > > ** ** > > The change history from the -05 draft reads: **** > > ** ** > > -05 Feb 13 Several changes in response to comments from Alun Luchuk > and Kevin Gross: > - Modified the use of wellKnownTransportTypes and > wellKnownEncapsulationTypes > - changed ptpbaseClockPortSyncOneStep to > ptpbaseClockPortSyncTwoStep to match IEEE1588 > semantics > - Re-ordered textual conventions to be alphabetic > - Changed some types from Integer32 to use defined > textual conventions > - various minor descriptive text changes**** > > ** ** > > In detail: > > **** > > Abstract: Add a bracketed reference to IEEE 1588-2008 - DONE**** > > ** ** > > Section 1: s/defined to monitor, measure the performance/defined to > monitor and measure the performance - DONE**** > > ** ** > > Section 1.1 What in this MIB is profile dependent? I did not identify > anything in my review. It would be desirable. if possible, to have a > profile-independent MIB.**** > > **- **TF: Removed erroneous text about Telecom Profile – there is > nothing in this MIB that is particular to that profile. **** > > ** ** > > TEXTUAL-CONVENTION general issues - Consider alphabetizing - DONE**** > > ** ** > > ClockInstanceType TEXTUAL-CONVENTION definition - Description requires > elucidation or a reference. **** > > **- **TF: not done, looks like this one slipped through.**** > > ** ** > > ClockProfileType TEXTUAL-CONVENTION definition**** > > Consider using and OUI instead of an enumeration. IEEE 1588-1588 requires > an OUI be associated with each profile.**** > > **- **TF: OUI would be specific to the organization, not the profile. > If the ITU (for instance) developed more than one profile, then they would > have the same OUI. Therefore it is best (in the authors’ opinion) to stick > to using an enumeration**** > > ** ** > > OBJECT-TYPE general issues**** > > Consider being consistent about repeating TEXTUAL-CONVENTION descriptions, > explicitly referencing them or assuming readers will track down the > reference without reminder.**** > > **- **TF: We’ve tried to be as consistent as we can. Of 17 > TEXTUAL-CONVENTIONS, 13 are directly referenced to IEEE1588 sections. The > remainder don’t directly map onto IEEE1588 quantities, but onto associated > concepts, and we have tried to explain these in the description. Certainly > one could do with a better description, as you note above. **** > > ** ** > > ptpDomainClockPortsTotal OBJECT-TYPE**** > > I assume this is the number of ports for the managed PTP-capable system > (i.e. a router or switch). Suggest adding "in the system" to the > description to clarify scope of count. - DONE**** > > ** ** > > ptpbaseClockTimePropertiesDSTable OBJECT-TYPE **** > > s/clock Timeproperties Datasets for/clock time properties datasets for - DONE**** > > ** ** > > PtpbaseClockTransDefaultDSEntry SEQUENCE**** > > Use ClockDomainType textual convention instead of Integer32 for ptpbaseClockTransDefaultDSPrimaryDomain - DONE**** > > ** ** > > PtpbaseClockPortEntry SEQUENCE**** > > Change ptpbaseClockPortSyncOneStep to ptpbaseClockPortSyncTwoStep to match 1588 semantics for this Boolean – DONE**** > > ** ** > > ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE**** > > Needs a textual convention or description of allowed values and their meanings**** > > **- **TF: Now uses an autonomous type instead of Integer32**** > > ** ** > > ptpbaseClockPortTransDSlogMinPdelayReqInt OBJECT-TYPE**** > > Change to ClockIntervalBase2 type DONE**** > > ** ** > > Section 5: Copy-paste error: "creation and/or manipulation of tunnels"**** > > **- **TF: Section changed since -03, no longer has this phrase.**** > > ** ** > > Section 6: To be added - DONE**** > > ** ** > > ** ** > > Best regards,**** > > Tim Frost**** > > ** ** > > *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On > Behalf Of *Kevin Gross > *Sent:* 16 May 2013 18:09 > > *To:* Karen ODonoghue > *Cc:* tictoc@ietf.org > *Subject:* Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt**** > > ** ** > > I submitted comments on v03 11 January ( > http://www.ietf.org/mail-archive/web/tictoc/current/msg01331.html). Vinay > indicated in a short message on 23 January the comments would be addressed > in the next version ( > http://www.ietf.org/mail-archive/web/tictoc/current/msg01333.html). v04 > was published 31 January. I did not see any notes from the authors > associated with that revision. A quick check of the v03-v04 diff shows > evidence that not all my comments were directly addressed. Can I get a > summary of how my comments were addressed? I'm fine if some of these were > rejected but I would like to verify that they were given consideration.*** > * > > > **** > > Kevin Gross**** > > +1-303-447-0517**** > > Media Network Consultant**** > > AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org**** > > ** ** > > On Thu, May 16, 2013 at 9:41 AM, Karen O'Donoghue <odonoghue@isoc.org> > wrote:**** > > This message initiates a two week TICTOC Working Group Last Call on > advancing: > > Title : Precision Time Protocol Version 2 (PTPv2) Management Information > Base > Author(s) : Vinay Shankarkumar, Laurent Montini, Tim Frost, Greg Dowd > Filename : draft-ietf-tictoc-ptp-mib-05.txt > Pages : 77 > Date : 2013-02-25 > > http://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/?include_text=1 > > as a Standards Track RFC. Substantive comments and statements of support > for advancing this document should be directed to the mailing list. > Editorial suggestions can be sent directly to the authors. This last call > will end on 31 May 2013. > > _______________________________________________ > TICTOC mailing list > TICTOC@ietf.org > https://www.ietf.org/mailman/listinfo/tictoc**** > > ** ** >
- [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt Karen O'Donoghue
- Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05… Kevin Gross
- Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05… Smiley, Russell
- Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05… Karen O'Donoghue
- Re: [TICTOC] WG consensus to forward draft-ietf-t… Smiley, Russell
- Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05… Karen O'Donoghue
- Re: [TICTOC] WG consensus to forward draft-ietf-t… Karen O'Donoghue
- Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05… Tim Frost
- [TICTOC] Fwd: WGLC on draft-ietf-tictoc-ptp-mib-0… Karen O'Donoghue
- Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05… Alan Luchuk
- Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05… Kevin Gross
- Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05… Greg Dowd
- Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05… Kevin Gross