
From nobody Mon Oct  2 10:34:19 2017
Return-Path: <rodney.cummings@ni.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 DFEA3133039; Mon,  2 Oct 2017 10:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nio365.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VUfxYcM-mKsj; Mon,  2 Oct 2017 10:34:10 -0700 (PDT)
Received: from mx0b-00010702.pphosted.com (mx0a-00010702.pphosted.com [148.163.156.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BD8413301C; Mon,  2 Oct 2017 10:34:10 -0700 (PDT)
Received: from pps.filterd (m0098781.ppops.net [127.0.0.1]) by mx0a-00010702.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v92HIQVE031399; Mon, 2 Oct 2017 12:34:09 -0500
Received: from nam01-sn1-obe.outbound.protection.outlook.com (mail-sn1nam01lp0114.outbound.protection.outlook.com [207.46.163.114]) by mx0a-00010702.pphosted.com with ESMTP id 2dbsr783hj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 02 Oct 2017 12:34:08 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nio365.onmicrosoft.com; s=selector1-ni-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=LdjFlDWkcrDphXJL5i9bOqDal4rFkfkqmnhMFBcbLRg=; b=R+EMdh8MA7ARHpDbU+Kob/s4kT8e2sZvz9y8QWbo/txzrRYIOjHQIX9uIerYoMpFAw8xd8hsNegDemfXqSeCSUn7xfg9rkokMWZabEkvEpuUbJnl1eoYfwra2JnTZ++ro1Xt+C/PCa90WqIbzNc76xtS70op9wpTR5Euu2C8wpM=
Received: from DM2PR0401MB1389.namprd04.prod.outlook.com (10.160.219.156) by DM2PR0401MB1392.namprd04.prod.outlook.com (10.160.221.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.77.7; Mon, 2 Oct 2017 17:34:06 +0000
Received: from DM2PR0401MB1389.namprd04.prod.outlook.com ([fe80::b172:affa:cf1d:384e]) by DM2PR0401MB1389.namprd04.prod.outlook.com ([fe80::b172:affa:cf1d:384e%18]) with mapi id 15.20.0077.016; Mon, 2 Oct 2017 17:34:06 +0000
From: Rodney Cummings <rodney.cummings@ni.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: draft-ietf-tictoc-1588v2-yang-05: port-number
Thread-Index: AdM7naceqW92Otk+TBSUBZ12gBb0TQ==
Date: Mon, 2 Oct 2017 17:34:06 +0000
Message-ID: <DM2PR0401MB13896A98E4D5799F369EB71C927D0@DM2PR0401MB1389.namprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.164.62.43]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM2PR0401MB1392; 6:GUGnldwpr0AMAAgIf0YpNLvg/qGKbxpITTUuN+rpV/PBvocCC+IkhqAb0ZeEMJZLAeMYZ+2Oal70EFll7rwdrB+WI3l9PqZsp1T5XFj+CyV2AGhnoAri/MuzF7Il/BACsuI6CEt0iJVhKqKYQLFoA1h3ljz3qu3FVenfgnYoM1MdH+0a6eKg+eQhMKIpmuqZ3t4Jc/0Flg7MlG1WppIDB/0Ks4QwoKtwrQ3KmqqpgovcECLoHHLopnBornZ8LOoT86uGu3oakbH3oN57ResQAO/9YXyk7W5J5aUWd0G6Stm7g0lHWw9H732mTrIsYg5WKQpQsZU/loRdVIO2FWBOkg==; 5:zVcA6ffUlqoAOq/h4AcyUH31MUzauED96QMLygIGHvna9ry63KHwNZOtnhKq/8x7TbCODgmTJy+OOpncx//+4bec6T2cowhUT/n8pkvqSTZiUqkV/9LJkVz/MB96wUwaO60SKs3YOfI8V2dDXxpEyA==; 24:94NHTOc1It5jdOcX4agGaWZlseRRdFIitTvCcL9sGGeC5Wrx1gfNoNf4wxKgbRc0N1eGCugNnYmIox7DQ+rKshoZh+Nm5oHpJLJUiwCBriA=; 7:Rwr1ymVSTWphuqWWjae0n26Y4/6K5yrD0ReZrJx4Vvh6EyhSFRTPKlJe5ZnytOQr3iqbZC8cR3hWuBKv48Rr4SzUIEmAD9dibuLQv8pCMJ8qMctB6pHR0uLrQtJIlfOYpHa4N7iEPCW71l5HGpstqj/FqBUr7pjfCoAuTKUqGxwl4HQITbbqSIr8MWHkY74vEsoCvPLUre355ll9oG0HaMkh32i+OixOZfLSG8P2MrY=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: bb925758-a33c-4190-8618-08d509bbc81e
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254152)(2017052603199)(201703131423075)(201703031133081)(201702281549075); SRVR:DM2PR0401MB1392; 
x-ms-traffictypediagnostic: DM2PR0401MB1392:
x-exchange-antispam-report-test: UriScan:;
x-microsoft-antispam-prvs: <DM2PR0401MB1392BF66F9C1A4B058A1D5BB927D0@DM2PR0401MB1392.namprd04.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(100000703101)(100105400095)(3002001)(6041248)(20161123564025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123560025)(20161123558100)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DM2PR0401MB1392; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DM2PR0401MB1392; 
x-forefront-prvs: 0448A97BF2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(346002)(376002)(199003)(189002)(5250100002)(101416001)(14454004)(5660300001)(25786009)(81156014)(9686003)(2906002)(55016002)(53936002)(105586002)(8936002)(6116002)(305945005)(33656002)(6436002)(8676002)(106356001)(3846002)(99286003)(3660700001)(7736002)(6506006)(102836003)(3280700002)(2501003)(74316002)(2900100001)(81166006)(50986999)(110136005)(478600001)(7696004)(66066001)(54356999)(450100002)(86362001)(316002)(68736007)(230783001)(189998001)(97736004); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0401MB1392; H:DM2PR0401MB1389.namprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ni.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ni.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Oct 2017 17:34:06.1739 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 87ba1f9a-44cd-43a6-b008-6fdb45a5204e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0401MB1392
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-02_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=30 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=30 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710020252
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/lm1xq37jffkSMms2XJll3N-ydC0>
Subject: [TICTOC] draft-ietf-tictoc-1588v2-yang-05: port-number
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Oct 2017 17:34:12 -0000

Hi folks,

One of the last topics that we need to resolve for WG Last Call of draft-ie=
tf-tictoc-1588v2-yang-05 is the representation of port-number, which serves=
 as the key to the list of 1588 port data sets (i.e. port-list). I've had s=
ome offline discussion with IEEE 1588 WG members, and I'm copying NETMOD me=
mbers for YANG expertise.

I think we can narrow the possible options to two, so I'm starting a new th=
read to focus on those.

IEEE Std 1588-2008 is the time sync standard that specifies the information=
 model on which draft-ietf-tictoc-1588v2-yang-05 is based. In IEEE Std 1588=
-2008, subclause 5.3.5 specifies the following data type to identify each l=
ogical port in the 1588 product:
   struct PortIdentity {
      ClockIdentity clockIdentity;
      Uinteger16 portNumber;
   };
IEEE Std 1588-2008 uses this data type as the "portIdentity" of the port in=
 its on-the-wire protocol, state machines, and so on. In other words, in th=
e 1588 standard itself, portIdentity is a "real thing" with real implementa=
tion.
=20
IEEE Std 1588-2008 also specifies a list of logical ports in each "clock", =
and portIdentity.portNumber is used as the key to that list of ports.

In the YANG of draft-ietf-tictoc-1588v2-yang-05, we use YANG-style names (e=
.g. port-list, port-number), but otherwise we've tried to keep consistent t=
o the IEEE Std 1588-2008 information model.

We have a challenge with port-number. If YANG represents port-identity as a=
 container within port-list, YANG does not allow a key to be a leaf within =
a container, so we cannot use port-identity/port-number as the key to port-=
list.

It seems that we have two options:

Option 1: Use a leafref
---

YANG summary:

        list port-ds-list {
          key "port-number";
          leaf port-number {
            type uint16;
          }
          container port-identity {
             leaf clock-identity {
                type clock-identity-type;
                config false;
             }
             leaf port-number {
                type leafref{
                   path "../../port-number";
                }
                config false;
             }
          }
        }

This has disadvantages from the YANG perspective, in that port-number is du=
plicated. The "config false" is intended to mitigate YANG implementation ch=
allenges, such that only one value of port-number is provided for configura=
tion.

Option 2: Use a grouping
---

YANG summary:

     grouping port-identity-grouping {
       leaf clock-identity {
         type clock-identity-type;
       }
       leaf port-number {
         type uint16;
       }
     }
     list port-ds-list {
       key "port-number";
       uses port-identity-grouping;
     }

This has disadvantages from the 1588 perspective, in that it is not possibl=
e for a 1588-aware management client to "get" portIdentity. We are removing=
 a 1588 "real thing" from the data model in order to accommodate a syntax l=
imitation of YANG.=20

Question for NETMOD experts
---

My personal preference is Option 1 (leafref). Nevertheless, if the "config =
false" does not provide sufficient mitigation for today's YANG implementati=
ons, we can go with Option 2.=20

Feedback is very much appreciated.

Thanks folks,
Rodney Cummings
Co-author draft-ietf-tictoc-1588v2-yang-05


From nobody Mon Oct  2 11:14:40 2017
Return-Path: <mbj@tail-f.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 41370132FA7; Mon,  2 Oct 2017 11:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8xJtkhJ5NMGR; Mon,  2 Oct 2017 11:14:31 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6F03113469D; Mon,  2 Oct 2017 11:14:31 -0700 (PDT)
Received: from localhost (h-40-225.A165.priv.bahnhof.se [94.254.40.225]) by mail.tail-f.com (Postfix) with ESMTPSA id 547CD1AE018C; Mon,  2 Oct 2017 20:14:30 +0200 (CEST)
Date: Mon, 02 Oct 2017 20:14:30 +0200 (CEST)
Message-Id: <20171002.201430.1078877259363120382.mbj@tail-f.com>
To: rodney.cummings@ni.com
Cc: tictoc@ietf.org, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <DM2PR0401MB13896A98E4D5799F369EB71C927D0@DM2PR0401MB1389.namprd04.prod.outlook.com>
References: <DM2PR0401MB13896A98E4D5799F369EB71C927D0@DM2PR0401MB1389.namprd04.prod.outlook.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/2HpPEZsNT9JQ71BaprEOKsE2vdE>
Subject: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Oct 2017 18:14:33 -0000

Rodney Cummings <rodney.cummings@ni.com> wrote:
> Hi folks,
> 
> One of the last topics that we need to resolve for WG Last Call of
> draft-ietf-tictoc-1588v2-yang-05 is the representation of port-number,
> which serves as the key to the list of 1588 port data sets
> (i.e. port-list). I've had some offline discussion with IEEE 1588 WG
> members, and I'm copying NETMOD members for YANG expertise.
> 
> I think we can narrow the possible options to two, so I'm starting a
> new thread to focus on those.
> 
> IEEE Std 1588-2008 is the time sync standard that specifies the
> information model on which draft-ietf-tictoc-1588v2-yang-05 is
> based. In IEEE Std 1588-2008, subclause 5.3.5 specifies the following
> data type to identify each logical port in the 1588 product:
>    struct PortIdentity {
>       ClockIdentity clockIdentity;
>       Uinteger16 portNumber;
>    };
> IEEE Std 1588-2008 uses this data type as the "portIdentity" of the
> port in its on-the-wire protocol, state machines, and so on. In other
> words, in the 1588 standard itself, portIdentity is a "real thing"
> with real implementation.
>  
> IEEE Std 1588-2008 also specifies a list of logical ports in each
> "clock", and portIdentity.portNumber is used as the key to that list
> of ports.
> 
> In the YANG of draft-ietf-tictoc-1588v2-yang-05, we use YANG-style
> names (e.g. port-list, port-number), but otherwise we've tried to keep
> consistent to the IEEE Std 1588-2008 information model.
> 
> We have a challenge with port-number. If YANG represents port-identity
> as a container within port-list, YANG does not allow a key to be a
> leaf within a container, so we cannot use port-identity/port-number as
> the key to port-list.
> 
> It seems that we have two options:
> 
> Option 1: Use a leafref
> ---
> 
> YANG summary:
> 
>         list port-ds-list {
>           key "port-number";
>           leaf port-number {
>             type uint16;
>           }
>           container port-identity {
>              leaf clock-identity {
>                 type clock-identity-type;
>                 config false;
>              }
>              leaf port-number {
>                 type leafref{
>                    path "../../port-number";
>                 }
>                 config false;
>              }
>           }
>         }
> 
> This has disadvantages from the YANG perspective, in that port-number
> is duplicated. The "config false" is intended to mitigate YANG
> implementation challenges, such that only one value of port-number is
> provided for configuration.
> 
> Option 2: Use a grouping
> ---
> 
> YANG summary:
> 
>      grouping port-identity-grouping {
>        leaf clock-identity {
>          type clock-identity-type;
>        }
>        leaf port-number {
>          type uint16;
>        }
>      }
>      list port-ds-list {
>        key "port-number";
>        uses port-identity-grouping;
>      }
> 
> This has disadvantages from the 1588 perspective, in that it is not
> possible for a 1588-aware management client to "get" portIdentity. We
> are removing a 1588 "real thing" from the data model in order to
> accommodate a syntax limitation of YANG.

I think that in general when you go from an information model to a
concrete data model, you need to adapt to the data modelling language
you are using, and this will in most cases mean that there will be
some differences; in some cases the data model structure is different,
and in some cases the data model will result in a more detailed
model.  How keys are specified is one such example.  If you were to
use SMIv2, you'd have to change the names (so that they are unique),
and you'd have to map the structures to conceptual tables.

Clients need to understand the data model in use (not just the
information model behid it).

> Question for NETMOD experts
> ---
> 
> My personal preference is Option 1 (leafref). Nevertheless, if the
> "config false" does not provide sufficient mitigation for today's YANG
> implementations, we can go with Option 2.

I don't think any implementation would have any problem supporting
option 1, but it does look a bit odd.  Also, it only "helps" if the
client is getting the data using <get>, but it will not help if it is
using <get-config>.


I think that the cleanest solution is to not try to completely mimic
the structure from the information model, but make sure that the
text in the description statements make it clear that the data model
looks different compared to the information model, in order to help
the readers.



/martin



> 
> Feedback is very much appreciated.
> 
> Thanks folks,
> Rodney Cummings
> Co-author draft-ietf-tictoc-1588v2-yang-05
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
> 


From nobody Tue Oct  3 10:40:57 2017
Return-Path: <John.Fletcher@bbc.co.uk>
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 D6172133245 for <tictoc@ietfa.amsl.com>; Tue,  3 Oct 2017 10:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bEMefZz7aEM1 for <tictoc@ietfa.amsl.com>; Tue,  3 Oct 2017 10:40:52 -0700 (PDT)
Received: from mailout1.cwwtf.bbc.co.uk (mailout1.cwwtf.bbc.co.uk [132.185.160.180]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C20C134F5E for <tictoc@ietf.org>; Tue,  3 Oct 2017 10:40:52 -0700 (PDT)
Received: from BGB01XI1012.national.core.bbc.co.uk (bgb01xi1012.national.core.bbc.co.uk [10.161.14.16]) by mailout1.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id v93HekZo005447; Tue, 3 Oct 2017 18:40:46 +0100 (BST)
Received: from BGB01XUD1011.national.core.bbc.co.uk ([10.161.14.9]) by BGB01XI1012.national.core.bbc.co.uk ([10.161.14.16]) with mapi id 14.03.0319.002; Tue, 3 Oct 2017 18:40:46 +0100
From: John Fletcher <John.Fletcher@bbc.co.uk>
To: Rodney Cummings <rodney.cummings@ni.com>, Jiangyuanlong <jiangyuanlong@huawei.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: WGLC for draft-ietf-tictoc-1588v2-yang
Thread-Index: AQHTLMS9I02w6VlOokuuR++M6yrZg6K6tUOhgAAwdZCAAWox9IAFb8jQgAQPn+CADK4nMw==
Date: Tue, 3 Oct 2017 17:40:45 +0000
Message-ID: <B1D49063AD5FBD4688F3EEDEC68B2017C3934DEF@bgb01xud1011>
References: <2D6594B3-2C10-4B65-B789-788A2DBF8E30@isoc.org> <B1D49063AD5FBD4688F3EEDEC68B2017C390BE66@bgb01xud1011>, <DM2PR0401MB138949F3D4E4FBB99A00A07E92630@DM2PR0401MB1389.namprd04.prod.outlook.com> <B1D49063AD5FBD4688F3EEDEC68B2017C390D103@bgb01xud1011> <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5C77F5@dggeml507-mbx.china.huawei.com>, <DM2PR0401MB13892357FAFCF1E0C66A0B80927A0@DM2PR0401MB1389.namprd04.prod.outlook.com>
In-Reply-To: <DM2PR0401MB13892357FAFCF1E0C66A0B80927A0@DM2PR0401MB1389.namprd04.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.213]
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
x-tm-as-product-ver: SMEX-11.0.0.4255-8.100.1062-23370.000
x-tm-as-result: No--27.303600-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/_JTKIda0ybunzgX9tbWRm-U_ktg>
Subject: Re: [TICTOC] WGLC for draft-ietf-tictoc-1588v2-yang
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Oct 2017 17:40:56 -0000

Optional features are not necessarily defined by a dataset.  For example, t=
here is no dataset member corresponding to whether unicast negotiation is e=
nabled or not.  At a more basic level, devices can typically be configured =
to use unicast instead of multicast but, again, there is no dataset member =
for that.  So it seems that using the YANG model for configuration will alw=
ays be limited.  Maybe 1588-rev needs to introduce further datasets/members=
 so that the state of a device is fully described by the datasets.=0A=
=0A=
Regarding the optional features where there are datasets (e.g. unicastMaste=
rTable), I accept the opinion of the authors that this work can be deferred=
.=0A=
=0A=
John=0A=
________________________________________=0A=
From: Rodney Cummings [rodney.cummings@ni.com]=0A=
Sent: 25 September 2017 16:56=0A=
To: Jiangyuanlong; John Fletcher; tictoc@ietf.org=0A=
Subject: RE: WGLC for draft-ietf-tictoc-1588v2-yang=0A=
=0A=
Hi John and Yuanlong,=0A=
=0A=
I could be wrong, but I think there is some upcoming work in ITU-T that pla=
ns to use 1588's optional unicast negotiation feature. That being said, tha=
t feature was enhanced in 1588-rev, so ITU-T may be planning to use those e=
nhancements (not limited to 1588-2008).=0A=
=0A=
Regardless of what ITU-T is planning, for optional features that exist in 1=
588-2008 as a data set, it is reasonable to request those features in this =
YANG project.=0A=
=0A=
Nevertheless, my preference is to avoid those optional features in this YAN=
G project. As Yuanlong said:=0A=
> As we envisioned, this module should be the basic 1588 YANG model=0A=
The authors of this I-D are hoping to keep this YANG focused on the core 15=
88 data sets only, and avoid optional features. This presumably helps us to=
 reach RFC sooner. A profile or product that needs the optional features ca=
n create their own YANG augment for those features.=0A=
=0A=
Does this mean that we will never have 1588-wide (i.e. profile-independent)=
 YANG for the optional features?=0A=
        No... at least not in my opinion. We are simply deferring that work=
.=0A=
=0A=
In the IEEE 1588 working group, there is tentative consensus that as soon a=
s 1588-rev publishes (hopefully 1Q2018), the 1588 working group will create=
 an amendment PAR for 1588-rev YANG. That 1588-rev YANG will include all da=
ta sets, including all optional features. My tentative hope is that the 158=
8-rev YANG will be a revision of this 1588-2008 YANG project. That is one o=
f the reasons I was hoping to avoid optional features in this 1588-2008 YAN=
G, because the more this 1588-2008 YANG focuses on "basic 1588" only, the m=
ore likely we can revise it in the future to support the "optional 1588" fe=
atures.=0A=
=0A=
John... I'd appreciate your thoughts on this.=0A=
=0A=
Rodney=0A=
=0A=
=0A=
> -----Original Message-----=0A=
> From: Jiangyuanlong [mailto:jiangyuanlong@huawei.com]=0A=
> Sent: Friday, September 22, 2017 8:47 PM=0A=
> To: John Fletcher ; Rodney Cummings ; tictoc@ietf.org=0A=
> Subject: RE: WGLC for draft-ietf-tictoc-1588v2-yang=0A=
>=0A=
> Hi John and Rodney,=0A=
>=0A=
> Regarding "optional features", I would like to chime in:=0A=
> As we envisioned, this module should be the basic 1588 YANG model, and=0A=
> transport profile, bridge profile and router profile modules can import=
=0A=
> this module and add their new optional features respectively.=0A=
> However, it says in A.9 of G.8275.1 (2016):" Other optional features of=
=0A=
> [IEEE 1588] are not used in this version of the profile. These include=0A=
> unicast message negotiation...". thus, it is clear that ITU-T PTP profile=
=0A=
> don't need to support these optional features.=0A=
> Therefore, we'd better exclude unnecessary optional features and make sur=
e=0A=
> the module only include the most fundamental features.=0A=
>=0A=
> B.R.,=0A=
> Yuanlong=0A=
>=0A=
> -----Original Message-----=0A=
> From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of John Fletcher=
=0A=
> Sent: Wednesday, September 20, 2017 1:16 AM=0A=
> To: Rodney Cummings; tictoc@ietf.org=0A=
> Subject: Re: [TICTOC] WGLC for draft-ietf-tictoc-1588v2-yang=0A=
>=0A=
> Responses inline below prefixed [JF]=0A=
> ________________________________________=0A=
> From: Rodney Cummings [rodney.cummings@ni.com]=0A=
> Sent: 18 September 2017 20:08=0A=
> To: John Fletcher; tictoc@ietf.org=0A=
> Subject: RE: WGLC for draft-ietf-tictoc-1588v2-yang=0A=
>=0A=
> Great comments John... thanks.=0A=
>=0A=
> I'll offer some opinion below.=0A=
>=0A=
> As an introduction of sorts, although this YANG is limited to the=0A=
> published IEEE Std 1588-2008, some of the concepts from the ongoing 1588=
=0A=
> revision are having a subtle effect. The reason is simple: When a YANG=0A=
> module is created for the 1588 revision (likely 1588-2018), ideally it ca=
n=0A=
> be done as a revision of this 1588-2008 YANG module, such that the YANG=
=0A=
> revision complies fully with RFC 7950 section 11. There's no guarantee=0A=
> that this will be possible, but so far it seems feasible by keeping the=
=0A=
> fundamental hierarchy consistent with 1588-rev, while continuing to limit=
=0A=
> its nodes to 1588-2008.=0A=
>=0A=
> > There are configurable attributes beyond those listed.  For example:=0A=
> > attributes for the optional features of 1588-2008 clauses 16 and 17;=0A=
> > the sample period for variance estimation (clause 7.6.3.2) etc.  These=
=0A=
> > should be included.=0A=
>=0A=
> 1588-2008 didn't have a clear definition of "configurable by management"=
=0A=
> beyond the 1588-based messages of 1588-2008 clause 15. There are plans to=
=0A=
> clarify that topic in 1588-rev by recommending that the 1588 data sets=0A=
> serve as an information model for management. That already has precedent=
=0A=
> for 1588-2008 (e.g. RFC8173 and this YANG I-D), so it seems like a safe=
=0A=
> recommendation as we move forward.=0A=
>=0A=
> That being said, you're correct that 1588-2008 specifies data sets for th=
e=0A=
> optional features in clause 16 and 17. Nevertheless, in 1588-2008 those=
=0A=
> data sets are somewhat "disconnected" relative to the other data sets=0A=
> (i.e. overall management hierarchy). We're clarifying that topic in 1588-=
=0A=
> rev, so my slight preference would be to defer management of these=0A=
> features to the creation of a 1588-rev YANG revision. Nevertheless, one o=
f=0A=
> the goals of this 1588-2008 YANG is to serve shorter-term needs, so if yo=
u=0A=
> have a specific optional feature that you need to manage in current 1588-=
=0A=
> 2008 products, maybe we should add that to this I-D.=0A=
>=0A=
> [JF] Examples would be: Unicast negotiation enable, Unicast master table,=
=0A=
> Acceptable master table.=0A=
>=0A=
> As for the period for variance estimation in 7.6.3.2, that has no data se=
t=0A=
> member in 1588-2008. I seem to recall discussion in the 1588 working grou=
p=0A=
> of making that period manageable (i.e. a data set member), but that was=
=0A=
> rejected, and thus far the draft of 7.6.3.2 hasn't changed from 1588-2008=
.=0A=
> If you feel strongly that this period should be manageable, I'd recommend=
=0A=
> that you submit a comment for the 1588 revision. If you are an IEEE-SA=0A=
> member, you can do that during sponsor ballot (probably 1Q2018). If not,=
=0A=
> feel free to write something up and I'd be happy to submit it for you.=0A=
>=0A=
> [JF] 1588-2008 says the sample period shall be the value defined in the=
=0A=
> applicable PTP profile, which implies that if you want to configure a=0A=
> device according to a profile, you need to manage that value.  I'm not=0A=
> aware of any profiles that define a different value from the default=0A=
> profile, though, so not a big deal.=0A=
>=0A=
> > I find it confusing that the hierarchy shown in section 2 has every=0A=
> > node as "rw" even though many are not configurable.  Later, in section=
=0A=
> > 2.2, there is some explanation of this but I think a further note is=0A=
> > needed before the hierarchy diagram.=0A=
>=0A=
> Sounds good.=0A=
>=0A=
> > Section 2.1 says that "1588-2008 transparent clocks are domain=0A=
> > independent" but I don't think that is correct; transparent clocks=0A=
> > have a "primary syntonization domain".=0A=
>=0A=
> Correct. For the next draft, we can remove the "domain independent"=0A=
> language.=0A=
> That came from the NOTE in 1588-2008 subclause 8.3.1, and the concept=0A=
> isn't needed in this context.=0A=
>=0A=
> > instance-number description makes it sound like there is one PTP=0A=
> > dataset for each domain but I think the intention is one set of PTP=0A=
> > datasets, the set comprising default-ds, current-ds, parent-ds etc.=0A=
> > However, I don't see any reason to tie instances to domains.=0A=
> > Instances seem to be equivalent to clocks (one clock per instance).  A=
=0A=
> > device can contain mulitple clocks and there is no requirement that=0A=
> > all clocks in a device are in different domains.=0A=
>=0A=
> Correct.=0A=
>=0A=
> 1588-2008 implied this "instance" concept, and 1588-rev makes it explicit=
.=0A=
> The intention is exactly as you describe. It is simply an instance of the=
=0A=
> PTP standard's specifications. Two instances might use different=0A=
> domainNumber, or the same domainNumber (e.g. two disjoint physical=0A=
> networks).=0A=
> I'll work with my co-authors to clarify this in the text.=0A=
>=0A=
> > I think it would help to have a definition of PTP Instance.  A draft=0A=
> > of 1588-rev said: "A PTP Instance is one of the following: an Ordinary=
=0A=
> > Clock, a Boundary Clock, or a Transparent Clock".  The yang model here=
=0A=
> > seems to be assuming that a Transparent Clock is not an instance.  It=
=0A=
> > would be confusing to use a different definition of Instance than the=
=0A=
> > one in 1588- rev.  An alternative would be to stick with the terminolog=
y=0A=
> of 1588-2008.=0A=
>=0A=
> Correct. I'll work with my co-authors to clarify this in the text.=0A=
>=0A=
> You found the issue that makes this tricky... transparent clock.=0A=
>=0A=
> As the 1588 group worked through the 1588 revision, the group decided to=
=0A=
> clarify that each "PTP Instance" (i.e. the explicit instance concept)=0A=
> operates on one-and-only-one domain. That's fine for ordinary clock and=
=0A=
> boundary clock, but it was controversial for transparent clock due to the=
=0A=
> preceding "domain independent" concept. Some transparent clock=0A=
> implementations operate on all domains, in that the timestamp in the=0A=
> message is changed regardless of what the domainNumber field contains.=0A=
> Some other transparent clock implementations operate like a "PTP=0A=
> Instance", in that they only change the message when the domainNumber=0A=
> field matches the domainNumber in the transparent clock's data sets. The=
=0A=
> intent of=0A=
> 1588-2008 was the "instance" way, but it wasn't clear, and now there are=
=0A=
> products in the field today that implement it both ways. If you take a=0A=
> look at the latest 1588-rev draft, you'll see the current consensus, whic=
h=0A=
> is to a) keep the original transparent clock data sets outside of the=0A=
> instance, to allow for domain-independent, but recommend against that=0A=
> implementation in the future, b) add more explicit specs for a transparen=
t=0A=
> clock to be implemented using the instance data sets.=0A=
>=0A=
> I agree that the current hierarchy can be confusing (i.e. transparent=0A=
> clock outside of instance). Nevertheless, it seems to me that 1588-2008=
=0A=
> itself is the source of that confusion, in that its transparent clock=0A=
> specs have been interpreted in contradictory ways. Since this YANG is for=
=0A=
> 1588-2008 only, I'd prefer to leave it somewhat open to interpretation=0A=
> according to 1588-2008 text, rather than bring up the changes coming in=
=0A=
> 1588-rev. I'd appreciate your thoughts on it.=0A=
>=0A=
> [JF] After some reading of 1588-2008 and 1588-rev, I agree the current=0A=
> structure is the best choice.  In 1588-2008, it's clear that Transparent=
=0A=
> Clocks can (should) operate in multiple domains and that a Transparent=0A=
> Clock operating in multiple domains is regarded as a single Transparent=
=0A=
> Clock with single data sets.  In 1588-rev, this is allowed but deprecated=
=0A=
> and the preference is "The PTP Node can provide one or more Transparent=
=0A=
> Clocks (each with an entry in instanceList), and each Transparent Clock=
=0A=
> supports a single PTP Instance and domain".  In this case, the Transparen=
t=0A=
> Clock uses the same data sets as an Ordinary Clock or Boundary Clock.=0A=
>=0A=
> > number-ports description says "number of PTP ports on the device".  We=
=0A=
> > probably need a definition of "device" here.  You might think that=0A=
> > because default-ds is part of an instance, the members refer to the=0A=
> instance (e.g.=0A=
> > as clock-identity does).  However, in the case of number-ports, it=0A=
> > refers to the device, where a device is the root scope for this model=
=0A=
> > and can contain more than one instance.  Perhaps a root level node for=
=0A=
> > nunber- ports with default-ds/number-ports being a  link to that would=
=0A=
> help.=0A=
>=0A=
> The 1588-rev draft currently specifies numberPorts as:=0A=
> "The attribute, numberPorts, shall indicate the number of PTP Ports on th=
e=0A=
> PTP Instance."=0A=
> and PTP Port is currently defined as:=0A=
> "A logical access point of a PTP Instance for PTP Communications to the=
=0A=
> communications network."=0A=
> In other words, 1588's port is a logical entity that serves as the=0A=
> reference point for the 1588 instance. The 1588 standard tries to keep=0A=
> abstracted from "physical" ports (interfaces) as much as possible. In the=
=0A=
> YANG context, 1588 assumes that ietf-interface provides the list of=0A=
> physical ports (interfaces) in the product. The "underlying-interface"=0A=
> reference is intended to mean "Here's a reference to the physical=0A=
> interface used by this logical PTP port."=0A=
>=0A=
> I'd recommend that we change the number-ports description to "number of=
=0A=
> PTP ports on the instance".=0A=
>=0A=
> [JF] Yes, for defaultDS that seems the best route for compatibility with=
=0A=
> 1588-rev but for transparentClockDefaultDS it needs to be "number of PTP=
=0A=
> ports on the device" or maybe "number of PTP ports on the PTP Node".=0A=
>=0A=
> [JF] I think we need to define what the top level of the hierarchy=0A=
> corresponds to.  I think it would be a "PTP Node" in 1588-rev terminology=
.=0A=
> In 1588-2008, a "PTP Node" seems to be a single Clock but 1588-2008=0A=
> doesn't really allow for multiple "instances" in the same device.=0A=
>=0A=
> > Should there be a separate list of port-ds for each instance (as=0A=
> > shown) or should there be one list for the device?  Given that=0A=
> > port-identity includes clock-identity, it would seem the intention is=
=0A=
> > one list per device.=0A=
>=0A=
> See above. The device's list is ietf-interfaces.=0A=
>=0A=
> [JF] Addional comment: the title should not refer to 1588v2 but to 1588-=
=0A=
> 2008.  The version will still be 2 in 1588-rev.=0A=
>=0A=
> > Regards,=0A=
> > John Fletcher=0A=
>=0A=
> Thanks again John.=0A=
> [JF} Thanks for good discussion.=0A=
>=0A=
>=0A=
>=0A=
> -----------------------------=0A=
> https://urldefense.proofpoint.com/v2/url?u=3Dhttp-=0A=
> 3A__www.bbc.co.uk&d=3DDwIFgQ&c=3DI_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSj=
ixA&r=0A=
> =3DWA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=3Dq08sdix-=0A=
> IT4WEtYgvpO5Vc1bUOFvO-=0A=
> iWzjpVV7ymSVM&s=3Dn8KVe2hEurlWYuTojP8rcGy5y15wDqyrXhF24XeQGFg&e=3D=0A=
> This e-mail (and any attachments) is confidential and may contain persona=
l=0A=
> views which are not the views of the BBC unless specifically stated.=0A=
> If you have received it in=0A=
> error, please delete it from your system.=0A=
> Do not use, copy or disclose the=0A=
> information in any way nor act in reliance on it and notify the sender=0A=
> immediately.=0A=
> Please note that the BBC monitors e-mails sent or received.=0A=
> Further communication will signify your consent to this.=0A=
> -----------------------------=0A=
>=0A=
> _______________________________________________=0A=
> TICTOC mailing list=0A=
> TICTOC@ietf.org=0A=
> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-=0A=
> 3A__www.ietf.org_mailman_listinfo_tictoc&d=3DDwIFgQ&c=3DI_0YwoKy7z5LMTVdy=
O6YCi=0A=
> E2uzI1jjZZuIPelcSjixA&r=3DWA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=
=3Dq08s=0A=
> dix-IT4WEtYgvpO5Vc1bUOFvO-iWzjpVV7ymSVM&s=3DBbZVGr-=0A=
> smJLMoDi8n42rSt3QtircWOMV-E3lTmaXjNA&e=3D=0A=


From nobody Tue Oct  3 10:52:02 2017
Return-Path: <rodney.cummings@ni.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 E99F7132D89 for <tictoc@ietfa.amsl.com>; Tue,  3 Oct 2017 10:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nio365.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZgECsuZ5G77A for <tictoc@ietfa.amsl.com>; Tue,  3 Oct 2017 10:51:57 -0700 (PDT)
Received: from mx0b-00010702.pphosted.com (mx0b-00010702.pphosted.com [148.163.158.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 911BA134FB0 for <tictoc@ietf.org>; Tue,  3 Oct 2017 10:51:56 -0700 (PDT)
Received: from pps.filterd (m0098779.ppops.net [127.0.0.1]) by mx0b-00010702.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v93Hpdue013484; Tue, 3 Oct 2017 12:51:49 -0500
Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp0080.outbound.protection.outlook.com [207.46.163.80]) by mx0b-00010702.pphosted.com with ESMTP id 2dceccrkmp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 03 Oct 2017 12:51:49 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nio365.onmicrosoft.com; s=selector1-ni-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=5GT7IVJDx1peA1v41rOWXjCdyPQ/ORP155/hFY+Q2Yk=; b=dPqiyFMOCVkk04vXBRgqZ3HULv8lWkb3gYlpJeRymLT0JN3dv+/bTgs6l6tgltEGVQKE9wTuJriItjsQd1uciR+wyR7CLtA3Y3YeAcvxraYLSxhcllEzq9oiYSI4MzwzznDmjEZeFvg3djAFwuoEaFMlPwD11i5K4jhx+LZMlrY=
Received: from DM2PR0401MB1389.namprd04.prod.outlook.com (10.160.219.156) by DM2PR0401MB1391.namprd04.prod.outlook.com (10.160.221.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.77.7; Tue, 3 Oct 2017 17:51:46 +0000
Received: from DM2PR0401MB1389.namprd04.prod.outlook.com ([fe80::b172:affa:cf1d:384e]) by DM2PR0401MB1389.namprd04.prod.outlook.com ([fe80::b172:affa:cf1d:384e%18]) with mapi id 15.20.0077.016; Tue, 3 Oct 2017 17:51:46 +0000
From: Rodney Cummings <rodney.cummings@ni.com>
To: John Fletcher <John.Fletcher@bbc.co.uk>, Jiangyuanlong <jiangyuanlong@huawei.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: WGLC for draft-ietf-tictoc-1588v2-yang
Thread-Index: AQHTLMS9I02w6VlOokuuR++M6yrZg6K6tUOhgAAwdZCAAWox9IAFb8jQgAQPn+CADK4nM4AACGsA
Date: Tue, 3 Oct 2017 17:51:46 +0000
Message-ID: <DM2PR0401MB138993F5366938FA67FFDE6492720@DM2PR0401MB1389.namprd04.prod.outlook.com>
References: <2D6594B3-2C10-4B65-B789-788A2DBF8E30@isoc.org> <B1D49063AD5FBD4688F3EEDEC68B2017C390BE66@bgb01xud1011>, <DM2PR0401MB138949F3D4E4FBB99A00A07E92630@DM2PR0401MB1389.namprd04.prod.outlook.com> <B1D49063AD5FBD4688F3EEDEC68B2017C390D103@bgb01xud1011> <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5C77F5@dggeml507-mbx.china.huawei.com>, <DM2PR0401MB13892357FAFCF1E0C66A0B80927A0@DM2PR0401MB1389.namprd04.prod.outlook.com> <B1D49063AD5FBD4688F3EEDEC68B2017C3934DEF@bgb01xud1011>
In-Reply-To: <B1D49063AD5FBD4688F3EEDEC68B2017C3934DEF@bgb01xud1011>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.164.62.43]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM2PR0401MB1391; 6:9QBmp8nM2uJWs5HAoaa52W4GaeSw99z9SQQUrNq3Gzy0E4Zb6lKBZ+cuKlYwvYFzBEdaj5glLd81qN5CNu+SNoDa+mPcoqHJSXAmZlmzzaoBfpOmjl8wP9Km/uRfmGTCnX+35Z4n8iw2+51g6GPC8Q6rTnSXOlym/T3J40giGMEsn4wthVx/mie5Ilv7+sfen09V1xZaRW1bx2TfmSnrVXiRMaY5R77XqmLrp1A3yvyOttKZz4tB94FqBZHmvld65qRbqGRmUQqUvcsU+d/3yjVWMmJt4Uo/zt9wygkQ8knDkAuRpgAiMzhTv8uOX11Laf40fARXsE38NgbHyJb8lA==; 5:814EePcMQkfkrOZPXEmPUHoUNltouj1dokuADdsFMUz7L/w8ZvYq4S9u1cKwVq9qzLF1pa2zTjlGRCWgVYTH2NI0AWphckLx+ufYSrMYEu6XPlSBuIwRNqDgajw8FMmWQG5zdmZRwY+Z97R+e227ng==; 24:VBLm83AM0ty1ou7NGDrKRQKt0Ew9AWPjpwktDEURlEJogrO6J9vQKDIh4uPRiDI2YwQF4ClBbyhOWjaE7G0vHE2x/grLVpZCMAOk2tENHow=; 7:kCT0yto6ULL7oh0y8N8JEiC8gqEHyJfitTV3Sg8vrsFucqmJ0P7pgmB5fCjDH5VH0yzuPiBmpW2IEh/ug0+WSZSsqDYcQ7ntlkYp8UQD9/T+SCRSyA7lRIKWEw0cJwzefTEcXwxjb7fxf9Pqosq32BOg7bA5U26YS9KuhDtCrqiUd/MMdrMJgxkiPOW0xutYwWnue60XqUKzZ0RNCEIaisgN6WBpXAs7+Y/tZwGvmGw=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 6e802618-9085-4093-6e74-08d50a876a56
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254152)(2017052603199)(201703131423075)(201703031133081)(201702281549075); SRVR:DM2PR0401MB1391; 
x-ms-traffictypediagnostic: DM2PR0401MB1391:
x-exchange-antispam-report-test: UriScan:(10436049006162)(50582790962513)(100405760836317)(127952516941037)(145744241990776);
x-microsoft-antispam-prvs: <DM2PR0401MB1391D42E2AF0A41155E6A85792720@DM2PR0401MB1391.namprd04.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(100000703101)(100105400095)(3002001)(6041248)(20161123562025)(20161123564025)(20161123558100)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DM2PR0401MB1391; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DM2PR0401MB1391; 
x-forefront-prvs: 044968D9E1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(346002)(376002)(199003)(189002)(43784003)(13464003)(377454003)(33656002)(68736007)(53546010)(2906002)(3280700002)(3660700001)(2900100001)(106356001)(6436002)(478600001)(6506006)(25786009)(316002)(5250100002)(86362001)(93886005)(97736004)(2501003)(110136005)(5890100001)(14454004)(966005)(53946003)(2950100002)(54356999)(7696004)(9686003)(6306002)(6116002)(76176999)(102836003)(50986999)(53936002)(101416001)(3846002)(229853002)(105586002)(6246003)(81166006)(66066001)(74316002)(8936002)(230783001)(189998001)(5660300001)(81156014)(55016002)(99286003)(8676002)(7736002)(305945005)(19627235001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0401MB1391; H:DM2PR0401MB1389.namprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ni.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ni.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Oct 2017 17:51:46.1830 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 87ba1f9a-44cd-43a6-b008-6fdb45a5204e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0401MB1391
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-03_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=30 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=30 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710030252
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/uQkz1Rr6biX3n2Cvjcf6w2TyGrU>
Subject: Re: [TICTOC] WGLC for draft-ietf-tictoc-1588v2-yang
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Oct 2017 17:52:01 -0000

> Optional features are not necessarily defined by a dataset.  For example,
> there is no dataset member corresponding to whether unicast negotiation i=
s
> enabled or not.  At a more basic level, devices can typically be
> configured to use unicast instead of multicast but, again, there is no
> dataset member for that.  So it seems that using the YANG model for
> configuration will always be limited.  Maybe 1588-rev needs to introduce
> further datasets/members so that the state of a device is fully described
> by the datasets.

Agreed.=20

The IEEE 1588 WG just started the second WG ballot for the 1588-rev draft.=
=20
Take a look at subclause 8.2.18, and you'll find a new dataset member
that should meet your expectation:
	unicastNegotiationPortDS.enable
That is new to 1588-rev, so it doesn't exist in 1588-2008.
When 1588-rev publishes and we start work on YANG for 1588-rev,
the YANG revision will add this as a boolean leaf.

Rodney


> -----Original Message-----
> From: John Fletcher [mailto:John.Fletcher@bbc.co.uk]
> Sent: Tuesday, October 3, 2017 12:41 PM
> To: Rodney Cummings <rodney.cummings@ni.com>; Jiangyuanlong
> <jiangyuanlong@huawei.com>; tictoc@ietf.org
> Subject: RE: WGLC for draft-ietf-tictoc-1588v2-yang
>=20
> Optional features are not necessarily defined by a dataset.  For example,
> there is no dataset member corresponding to whether unicast negotiation i=
s
> enabled or not.  At a more basic level, devices can typically be
> configured to use unicast instead of multicast but, again, there is no
> dataset member for that.  So it seems that using the YANG model for
> configuration will always be limited.  Maybe 1588-rev needs to introduce
> further datasets/members so that the state of a device is fully described
> by the datasets.
>=20
> Regarding the optional features where there are datasets (e.g.
> unicastMasterTable), I accept the opinion of the authors that this work
> can be deferred.
>=20
> John
> ________________________________________
> From: Rodney Cummings [rodney.cummings@ni.com]
> Sent: 25 September 2017 16:56
> To: Jiangyuanlong; John Fletcher; tictoc@ietf.org
> Subject: RE: WGLC for draft-ietf-tictoc-1588v2-yang
>=20
> Hi John and Yuanlong,
>=20
> I could be wrong, but I think there is some upcoming work in ITU-T that
> plans to use 1588's optional unicast negotiation feature. That being said=
,
> that feature was enhanced in 1588-rev, so ITU-T may be planning to use
> those enhancements (not limited to 1588-2008).
>=20
> Regardless of what ITU-T is planning, for optional features that exist in
> 1588-2008 as a data set, it is reasonable to request those features in
> this YANG project.
>=20
> Nevertheless, my preference is to avoid those optional features in this
> YANG project. As Yuanlong said:
> > As we envisioned, this module should be the basic 1588 YANG model
> The authors of this I-D are hoping to keep this YANG focused on the core
> 1588 data sets only, and avoid optional features. This presumably helps u=
s
> to reach RFC sooner. A profile or product that needs the optional feature=
s
> can create their own YANG augment for those features.
>=20
> Does this mean that we will never have 1588-wide (i.e. profile-
> independent) YANG for the optional features?
>         No... at least not in my opinion. We are simply deferring that
> work.
>=20
> In the IEEE 1588 working group, there is tentative consensus that as soon
> as 1588-rev publishes (hopefully 1Q2018), the 1588 working group will
> create an amendment PAR for 1588-rev YANG. That 1588-rev YANG will includ=
e
> all data sets, including all optional features. My tentative hope is that
> the 1588-rev YANG will be a revision of this 1588-2008 YANG project. That
> is one of the reasons I was hoping to avoid optional features in this
> 1588-2008 YANG, because the more this 1588-2008 YANG focuses on "basic
> 1588" only, the more likely we can revise it in the future to support the
> "optional 1588" features.
>=20
> John... I'd appreciate your thoughts on this.
>=20
> Rodney
>=20
>=20
> > -----Original Message-----
> > From: Jiangyuanlong [mailto:jiangyuanlong@huawei.com]
> > Sent: Friday, September 22, 2017 8:47 PM
> > To: John Fletcher ; Rodney Cummings ; tictoc@ietf.org
> > Subject: RE: WGLC for draft-ietf-tictoc-1588v2-yang
> >
> > Hi John and Rodney,
> >
> > Regarding "optional features", I would like to chime in:
> > As we envisioned, this module should be the basic 1588 YANG model, and
> > transport profile, bridge profile and router profile modules can import
> > this module and add their new optional features respectively.
> > However, it says in A.9 of G.8275.1 (2016):" Other optional features of
> > [IEEE 1588] are not used in this version of the profile. These include
> > unicast message negotiation...". thus, it is clear that ITU-T PTP
> profile
> > don't need to support these optional features.
> > Therefore, we'd better exclude unnecessary optional features and make
> sure
> > the module only include the most fundamental features.
> >
> > B.R.,
> > Yuanlong
> >
> > -----Original Message-----
> > From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of John Fletche=
r
> > Sent: Wednesday, September 20, 2017 1:16 AM
> > To: Rodney Cummings; tictoc@ietf.org
> > Subject: Re: [TICTOC] WGLC for draft-ietf-tictoc-1588v2-yang
> >
> > Responses inline below prefixed [JF]
> > ________________________________________
> > From: Rodney Cummings [rodney.cummings@ni.com]
> > Sent: 18 September 2017 20:08
> > To: John Fletcher; tictoc@ietf.org
> > Subject: RE: WGLC for draft-ietf-tictoc-1588v2-yang
> >
> > Great comments John... thanks.
> >
> > I'll offer some opinion below.
> >
> > As an introduction of sorts, although this YANG is limited to the
> > published IEEE Std 1588-2008, some of the concepts from the ongoing 158=
8
> > revision are having a subtle effect. The reason is simple: When a YANG
> > module is created for the 1588 revision (likely 1588-2018), ideally it
> can
> > be done as a revision of this 1588-2008 YANG module, such that the YANG
> > revision complies fully with RFC 7950 section 11. There's no guarantee
> > that this will be possible, but so far it seems feasible by keeping the
> > fundamental hierarchy consistent with 1588-rev, while continuing to
> limit
> > its nodes to 1588-2008.
> >
> > > There are configurable attributes beyond those listed.  For example:
> > > attributes for the optional features of 1588-2008 clauses 16 and 17;
> > > the sample period for variance estimation (clause 7.6.3.2) etc.  Thes=
e
> > > should be included.
> >
> > 1588-2008 didn't have a clear definition of "configurable by management=
"
> > beyond the 1588-based messages of 1588-2008 clause 15. There are plans
> to
> > clarify that topic in 1588-rev by recommending that the 1588 data sets
> > serve as an information model for management. That already has preceden=
t
> > for 1588-2008 (e.g. RFC8173 and this YANG I-D), so it seems like a safe
> > recommendation as we move forward.
> >
> > That being said, you're correct that 1588-2008 specifies data sets for
> the
> > optional features in clause 16 and 17. Nevertheless, in 1588-2008 those
> > data sets are somewhat "disconnected" relative to the other data sets
> > (i.e. overall management hierarchy). We're clarifying that topic in
> 1588-
> > rev, so my slight preference would be to defer management of these
> > features to the creation of a 1588-rev YANG revision. Nevertheless, one
> of
> > the goals of this 1588-2008 YANG is to serve shorter-term needs, so if
> you
> > have a specific optional feature that you need to manage in current
> 1588-
> > 2008 products, maybe we should add that to this I-D.
> >
> > [JF] Examples would be: Unicast negotiation enable, Unicast master
> table,
> > Acceptable master table.
> >
> > As for the period for variance estimation in 7.6.3.2, that has no data
> set
> > member in 1588-2008. I seem to recall discussion in the 1588 working
> group
> > of making that period manageable (i.e. a data set member), but that was
> > rejected, and thus far the draft of 7.6.3.2 hasn't changed from 1588-
> 2008.
> > If you feel strongly that this period should be manageable, I'd
> recommend
> > that you submit a comment for the 1588 revision. If you are an IEEE-SA
> > member, you can do that during sponsor ballot (probably 1Q2018). If not=
,
> > feel free to write something up and I'd be happy to submit it for you.
> >
> > [JF] 1588-2008 says the sample period shall be the value defined in the
> > applicable PTP profile, which implies that if you want to configure a
> > device according to a profile, you need to manage that value.  I'm not
> > aware of any profiles that define a different value from the default
> > profile, though, so not a big deal.
> >
> > > I find it confusing that the hierarchy shown in section 2 has every
> > > node as "rw" even though many are not configurable.  Later, in sectio=
n
> > > 2.2, there is some explanation of this but I think a further note is
> > > needed before the hierarchy diagram.
> >
> > Sounds good.
> >
> > > Section 2.1 says that "1588-2008 transparent clocks are domain
> > > independent" but I don't think that is correct; transparent clocks
> > > have a "primary syntonization domain".
> >
> > Correct. For the next draft, we can remove the "domain independent"
> > language.
> > That came from the NOTE in 1588-2008 subclause 8.3.1, and the concept
> > isn't needed in this context.
> >
> > > instance-number description makes it sound like there is one PTP
> > > dataset for each domain but I think the intention is one set of PTP
> > > datasets, the set comprising default-ds, current-ds, parent-ds etc.
> > > However, I don't see any reason to tie instances to domains.
> > > Instances seem to be equivalent to clocks (one clock per instance).  =
A
> > > device can contain mulitple clocks and there is no requirement that
> > > all clocks in a device are in different domains.
> >
> > Correct.
> >
> > 1588-2008 implied this "instance" concept, and 1588-rev makes it
> explicit.
> > The intention is exactly as you describe. It is simply an instance of
> the
> > PTP standard's specifications. Two instances might use different
> > domainNumber, or the same domainNumber (e.g. two disjoint physical
> > networks).
> > I'll work with my co-authors to clarify this in the text.
> >
> > > I think it would help to have a definition of PTP Instance.  A draft
> > > of 1588-rev said: "A PTP Instance is one of the following: an Ordinar=
y
> > > Clock, a Boundary Clock, or a Transparent Clock".  The yang model her=
e
> > > seems to be assuming that a Transparent Clock is not an instance.  It
> > > would be confusing to use a different definition of Instance than the
> > > one in 1588- rev.  An alternative would be to stick with the
> terminology
> > of 1588-2008.
> >
> > Correct. I'll work with my co-authors to clarify this in the text.
> >
> > You found the issue that makes this tricky... transparent clock.
> >
> > As the 1588 group worked through the 1588 revision, the group decided t=
o
> > clarify that each "PTP Instance" (i.e. the explicit instance concept)
> > operates on one-and-only-one domain. That's fine for ordinary clock and
> > boundary clock, but it was controversial for transparent clock due to
> the
> > preceding "domain independent" concept. Some transparent clock
> > implementations operate on all domains, in that the timestamp in the
> > message is changed regardless of what the domainNumber field contains.
> > Some other transparent clock implementations operate like a "PTP
> > Instance", in that they only change the message when the domainNumber
> > field matches the domainNumber in the transparent clock's data sets. Th=
e
> > intent of
> > 1588-2008 was the "instance" way, but it wasn't clear, and now there ar=
e
> > products in the field today that implement it both ways. If you take a
> > look at the latest 1588-rev draft, you'll see the current consensus,
> which
> > is to a) keep the original transparent clock data sets outside of the
> > instance, to allow for domain-independent, but recommend against that
> > implementation in the future, b) add more explicit specs for a
> transparent
> > clock to be implemented using the instance data sets.
> >
> > I agree that the current hierarchy can be confusing (i.e. transparent
> > clock outside of instance). Nevertheless, it seems to me that 1588-2008
> > itself is the source of that confusion, in that its transparent clock
> > specs have been interpreted in contradictory ways. Since this YANG is
> for
> > 1588-2008 only, I'd prefer to leave it somewhat open to interpretation
> > according to 1588-2008 text, rather than bring up the changes coming in
> > 1588-rev. I'd appreciate your thoughts on it.
> >
> > [JF] After some reading of 1588-2008 and 1588-rev, I agree the current
> > structure is the best choice.  In 1588-2008, it's clear that Transparen=
t
> > Clocks can (should) operate in multiple domains and that a Transparent
> > Clock operating in multiple domains is regarded as a single Transparent
> > Clock with single data sets.  In 1588-rev, this is allowed but
> deprecated
> > and the preference is "The PTP Node can provide one or more Transparent
> > Clocks (each with an entry in instanceList), and each Transparent Clock
> > supports a single PTP Instance and domain".  In this case, the
> Transparent
> > Clock uses the same data sets as an Ordinary Clock or Boundary Clock.
> >
> > > number-ports description says "number of PTP ports on the device".  W=
e
> > > probably need a definition of "device" here.  You might think that
> > > because default-ds is part of an instance, the members refer to the
> > instance (e.g.
> > > as clock-identity does).  However, in the case of number-ports, it
> > > refers to the device, where a device is the root scope for this model
> > > and can contain more than one instance.  Perhaps a root level node fo=
r
> > > nunber- ports with default-ds/number-ports being a  link to that woul=
d
> > help.
> >
> > The 1588-rev draft currently specifies numberPorts as:
> > "The attribute, numberPorts, shall indicate the number of PTP Ports on
> the
> > PTP Instance."
> > and PTP Port is currently defined as:
> > "A logical access point of a PTP Instance for PTP Communications to the
> > communications network."
> > In other words, 1588's port is a logical entity that serves as the
> > reference point for the 1588 instance. The 1588 standard tries to keep
> > abstracted from "physical" ports (interfaces) as much as possible. In
> the
> > YANG context, 1588 assumes that ietf-interface provides the list of
> > physical ports (interfaces) in the product. The "underlying-interface"
> > reference is intended to mean "Here's a reference to the physical
> > interface used by this logical PTP port."
> >
> > I'd recommend that we change the number-ports description to "number of
> > PTP ports on the instance".
> >
> > [JF] Yes, for defaultDS that seems the best route for compatibility wit=
h
> > 1588-rev but for transparentClockDefaultDS it needs to be "number of PT=
P
> > ports on the device" or maybe "number of PTP ports on the PTP Node".
> >
> > [JF] I think we need to define what the top level of the hierarchy
> > corresponds to.  I think it would be a "PTP Node" in 1588-rev
> terminology.
> > In 1588-2008, a "PTP Node" seems to be a single Clock but 1588-2008
> > doesn't really allow for multiple "instances" in the same device.
> >
> > > Should there be a separate list of port-ds for each instance (as
> > > shown) or should there be one list for the device?  Given that
> > > port-identity includes clock-identity, it would seem the intention is
> > > one list per device.
> >
> > See above. The device's list is ietf-interfaces.
> >
> > [JF] Addional comment: the title should not refer to 1588v2 but to 1588=
-
> > 2008.  The version will still be 2 in 1588-rev.
> >
> > > Regards,
> > > John Fletcher
> >
> > Thanks again John.
> > [JF} Thanks for good discussion.
> >
> >
> >
> > -----------------------------
> > https://urldefense.proofpoint.com/v2/url?u=3Dhttp-
> >
> 3A__www.bbc.co.uk&d=3DDwIFgQ&c=3DI_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSj=
ixA&r
> > =3DWA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=3Dq08sdix-
> > IT4WEtYgvpO5Vc1bUOFvO-
> > iWzjpVV7ymSVM&s=3Dn8KVe2hEurlWYuTojP8rcGy5y15wDqyrXhF24XeQGFg&e=3D
> > This e-mail (and any attachments) is confidential and may contain
> personal
> > views which are not the views of the BBC unless specifically stated.
> > If you have received it in
> > error, please delete it from your system.
> > Do not use, copy or disclose the
> > information in any way nor act in reliance on it and notify the sender
> > immediately.
> > Please note that the BBC monitors e-mails sent or received.
> > Further communication will signify your consent to this.
> > -----------------------------
> >
> > _______________________________________________
> > TICTOC mailing list
> > TICTOC@ietf.org
> > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-
> >
> 3A__www.ietf.org_mailman_listinfo_tictoc&d=3DDwIFgQ&c=3DI_0YwoKy7z5LMTVdy=
O6YCi
> >
> E2uzI1jjZZuIPelcSjixA&r=3DWA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=
=3Dq08s
> > dix-IT4WEtYgvpO5Vc1bUOFvO-iWzjpVV7ymSVM&s=3DBbZVGr-
> > smJLMoDi8n42rSt3QtircWOMV-E3lTmaXjNA&e=3D


From nobody Tue Oct  3 10:56:49 2017
Return-Path: <ORonen@advaoptical.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 06CE21321C9 for <tictoc@ietfa.amsl.com>; Tue,  3 Oct 2017 10:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level: 
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOkljiTSNYet for <tictoc@ietfa.amsl.com>; Tue,  3 Oct 2017 10:56:44 -0700 (PDT)
Received: from mail.advaoptical.com (mail.advaoptical.com [91.217.199.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 275BB133075 for <tictoc@ietf.org>; Tue,  3 Oct 2017 10:56:44 -0700 (PDT)
Received: from MUC-S-EX16B.advaoptical.com ([172.20.1.15]) by muc-vsrv-fsmail.advaoptical.com (8.16.0.20/8.16.0.20) with ESMTPS id v93Huf62030572 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA256 bits=128 verify=FAIL) for <tictoc@ietf.org>; Tue, 3 Oct 2017 19:56:42 +0200
Received: from MUC-S-EX16C.advaoptical.com (172.20.1.27) by MUC-S-EX16B.advaoptical.com (172.20.1.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.27; Tue, 3 Oct 2017 19:56:41 +0200
Received: from MUC-S-EX16C.advaoptical.com (172.20.1.27) by MUC-S-EX16C.advaoptical.com (172.20.1.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1261.27; Tue, 3 Oct 2017 19:56:41 +0200
Received: from MUC-S-EX16C.advaoptical.com ([fe80::8863:592b:3654:9597]) by MUC-S-EX16C.advaoptical.com ([fe80::8863:592b:3654:9597%3]) with mapi id 15.01.1261.026; Tue, 3 Oct 2017 19:56:41 +0200
From: Opher Ronen <ORonen@advaoptical.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
Thread-Index: AdM8bdngM/8ciPVNQMCmZAXgPxsbzQ==
Date: Tue, 3 Oct 2017 17:56:41 +0000
Message-ID: <61ee5a45c081476ea39332fd27561090@advaoptical.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.1.231]
Content-Type: multipart/alternative; boundary="_000_61ee5a45c081476ea39332fd27561090advaopticalcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-03_07:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/7-oiajNHKiGeyXSPL54Eymjbd1Q>
Subject: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Oct 2017 17:56:48 -0000

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

Hi Rodney & all,

   I am somewhat belatedly posting a post to this thread following an offli=
ne correspondence with Rodney in context of this subject. I hope my feedbac=
k is not too late to be constructive, and will be posted correctly as this =
is my first post to this thread.

   I will also apologize in advance that I will be mostly offline till mid-=
October, so will likely be able to reply to responses only then.

   Rodney shared with me the consideration on this aspect, and I believe hi=
s recent post attempt to integrate my offline on this topic.

   I hope some more detailed feedback will hopefully assist this draft adva=
nce in a manner aligned with my perception on this aspect from my involveme=
nt in the P1588 WG in general and it's Management SC in specific.

   I will first comment that following my correspondence with Rodney that I=
 believe (with reservation given my low involvement in direct implementatio=
n of management interfaces) that an interface that would enable performing =
a get to obtain an overall structure including the information comprimsing =
a PTP portIdentity appears nice to have. I would assume that this informati=
on will not be the most frequent aspect a management system would query, bu=
t easing obtaining it if overhead is reasonable may be worthwhile.

   A possibly more significant comment is to stress that the clockIdentity =
portion of the portIdentity attribute is equal in all port within a PTP Ins=
tance, and equal to the clockIdentity attribute with the clock data set. Th=
is is explicitly stressed by a new sentence added to the next revision draf=
t, intended to clarify this to the reader: "The clockIdentity portion of a =
portIdentity is equal to the clockIdentity of the PTP Instance that the PTP=
 Port is included in, and is therefore equal among all PTP Ports inside the=
 PTP Instance."

  In my view regardless of the option followed for the data model for portI=
dentity, the ability to directly configure the clockIdentity portion of it =
should be prevented to avoid generating a configuration violating the above=
 status (possible hampering the operation of the PTP protocol if later used=
 as data for portIdentity on the wire).

   If I understood correct yang data model enable to provide a leafref poin=
ter to the clockIdentity from the instance data set level, possibly best re=
flecting the actual limitations regarding the portIdentity structure.



Best Regards,

    Opher Ronen



Rodney Cummings <rodney.cummings@ni.com><mailto:rodney.cummings@ni.com&gt>;=
 wrote:

> Hi folks,

>

> One of the last topics that we need to resolve for WG Last Call of

> draft-ietf-tictoc-1588v2-yang-05 is the representation of port-number,

> which serves as the key to the list of 1588 port data sets

> (i.e. port-list). I've had some offline discussion with IEEE 1588 WG

> members, and I'm copying NETMOD members for YANG expertise.

>

> I think we can narrow the possible options to two, so I'm starting a

> new thread to focus on those.

>

> IEEE Std 1588-2008 is the time sync standard that specifies the

> information model on which draft-ietf-tictoc-1588v2-yang-05 is

> based. In IEEE Std 1588-2008, subclause 5.3.5 specifies the following

> data type to identify each logical port in the 1588 product:

>    struct PortIdentity {

>       ClockIdentity clockIdentity;

>       Uinteger16 portNumber;

>    };

> IEEE Std 1588-2008 uses this data type as the "portIdentity" of the

> port in its on-the-wire protocol, state machines, and so on. In other

> words, in the 1588 standard itself, portIdentity is a "real thing"

> with real implementation.

>

> IEEE Std 1588-2008 also specifies a list of logical ports in each

> "clock", and portIdentity.portNumber is used as the key to that list

> of ports.

>

> In the YANG of draft-ietf-tictoc-1588v2-yang-05, we use YANG-style

> names (e.g. port-list, port-number), but otherwise we've tried to keep

> consistent to the IEEE Std 1588-2008 information model.

>

> We have a challenge with port-number. If YANG represents port-identity

> as a container within port-list, YANG does not allow a key to be a

> leaf within a container, so we cannot use port-identity/port-number as

> the key to port-list.

>

> It seems that we have two options:

>

> Option 1: Use a leafref

> ---

>

> YANG summary:

>

>         list port-ds-list {

>           key "port-number";

>           leaf port-number {

>             type uint16;

>           }

>           container port-identity {

>              leaf clock-identity {

>                 type clock-identity-type;

>                 config false;

>              }

>              leaf port-number {

>                 type leafref{

>                    path "../../port-number";

>                 }

>                 config false;

>              }

>           }

>         }

>

> This has disadvantages from the YANG perspective, in that port-number

> is duplicated. The "config false" is intended to mitigate YANG

> implementation challenges, such that only one value of port-number is

> provided for configuration.

>

> Option 2: Use a grouping

> ---

>

> YANG summary:

>

>      grouping port-identity-grouping {

>        leaf clock-identity {

>          type clock-identity-type;

>        }

>        leaf port-number {

>          type uint16;

>        }

>      }

>      list port-ds-list {

>        key "port-number";

>        uses port-identity-grouping;

>      }

>

> This has disadvantages from the 1588 perspective, in that it is not

> possible for a 1588-aware management client to "get" portIdentity. We

> are removing a 1588 "real thing" from the data model in order to

> accommodate a syntax limitation of YANG.



I think that in general when you go from an information model to a

concrete data model, you need to adapt to the data modelling language

you are using, and this will in most cases mean that there will be

some differences; in some cases the data model structure is different,

and in some cases the data model will result in a more detailed

model.  How keys are specified is one such example.  If you were to

use SMIv2, you'd have to change the names (so that they are unique),

and you'd have to map the structures to conceptual tables.



Clients need to understand the data model in use (not just the

information model behid it).



> Question for NETMOD experts

> ---

>

> My personal preference is Option 1 (leafref). Nevertheless, if the

> "config false" does not provide sufficient mitigation for today's YANG

> implementations, we can go with Option 2.



I don't think any implementation would have any problem supporting

option 1, but it does look a bit odd.  Also, it only "helps" if the

client is getting the data using <get>, but it will not help if it is

using <get-config>.





I think that the cleanest solution is to not try to completely mimic

the structure from the information model, but make sure that the

text in the description statements make it clear that the data model

looks different compared to the information model, in order to help

the readers.







/martin







>

> Feedback is very much appreciated.

>

> Thanks folks,

> Rodney Cummings

> Co-author draft-ietf-tictoc-1588v2-yang-05

>

> _______________________________________________

> netmod mailing list

> netmod@ietf.org<mailto:netmod@ietf.org>

> https://www.ietf.org/mailman/listinfo/netmod

>



References:

  *   [TICTOC] draft-ietf-tictoc-1588v2-yang-05: port-number<https://mailar=
chive.ietf.org/arch/msg/tictoc/lm1xq37jffkSMms2XJll3N-ydC0>
Rodney Cummings <rodney.cummings@ni.com>


--_000_61ee5a45c081476ea39332fd27561090advaopticalcom_
Content-Type: text/html; charset="us-ascii"
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:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:inherit;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:right;
	direction:rtl;
	unicode-bidi:embed;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h3
	{mso-style-priority:9;
	mso-style-link:"Heading 3 Char";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:13.5pt;
	font-family:"Times New Roman",serif;}
h4
	{mso-style-priority:9;
	mso-style-link:"Heading 4 Char";
	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;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 3";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
span.Heading4Char
	{mso-style-name:"Heading 4 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 4";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
p.msg-header, li.msg-header, div.msg-header
	{mso-style-name:msg-header;
	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;}
span.pipe
	{mso-style-name:pipe;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:23557176;
	mso-list-template-ids:-1662904164;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">Hi Rodney &amp; all,<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&nbsp;&nbsp; I am somewhat belatedly posting a =
post to this thread following an offline correspondence with Rodney in cont=
ext of this subject. I hope my feedback is not too late to be constructive,=
 and will be posted correctly as this is my first post to this thread.<o:p>=
</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&nbsp;&nbsp; I will also apologize in advance t=
hat I will be mostly offline till mid-October, so will likely be able to re=
ply to responses only then.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&nbsp;&nbsp; Rodney shared with me the consider=
ation on this aspect, and I believe his recent post attempt to integrate my=
 offline on this topic.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&nbsp;&nbsp; I hope some more detailed feedback=
 will hopefully assist this draft advance in a manner aligned with my perce=
ption on this aspect from my involvement in the P1588 WG in general and it'=
s Management SC in specific.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&nbsp;&nbsp; I will first comment that followin=
g my correspondence with Rodney that I believe (with reservation given my l=
ow involvement in direct implementation of management interfaces) that an i=
nterface that would enable performing a get to obtain an overall structure =
including the information comprimsing a PTP portIdentity appears nice to ha=
ve. I would assume that this information will not be the most frequent aspe=
ct a management system would query, but easing obtaining it if overhead is =
reasonable may be worthwhile.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&nbsp;&nbsp; A possibly more significant commen=
t is to stress that the clockIdentity portion of the portIdentity attribute=
 is equal in all port within a PTP Instance, and equal to the clockIdentity=
 attribute with the clock data set. This is explicitly stressed by a new se=
ntence added to the next revision draft, intended to clarify this to the re=
ader: &quot;The clockIdentity portion of a portIdentity is equal to the clo=
ckIdentity of the PTP Instance that the PTP Port is included in, and is the=
refore equal among all PTP Ports inside the PTP Instance.&quot; <o:p></o:p>=
</span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&nbsp;&nbsp;In my view regardless of the option=
 followed for the data model for portIdentity, the ability to directly conf=
igure the clockIdentity portion of it should be prevented to avoid generati=
ng a configuration violating the above status (possible hampering the opera=
tion of the PTP protocol if later used as data for portIdentity on the wire=
). &nbsp;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&nbsp;&nbsp;&nbsp;If I understood correct yang =
data model enable to provide a leafref pointer to the clockIdentity from th=
e instance data set level, possibly best reflecting the actual limitations =
regarding the portIdentity structure.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">Best Regards,<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&nbsp;&nbsp;&nbsp; Opher Ronen<o:p></o:p></span=
></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"> <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">Rodney Cummings &lt;<a href=3D"mailto:rodney.cu=
mmings@ni.com&amp;gt"><span style=3D"color:#337AB7;text-decoration:none">ro=
dney.cummings@ni.com&gt;</span></a>; wrote:<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; Hi folks,<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; One of the last topics that we need to res=
olve for WG Last Call of<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; draft-ietf-tictoc-1588v2-yang-05 is the re=
presentation of port-number,<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; which serves as the key to the list of 158=
8 port data sets<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; (i.e. port-list). I've had some offline di=
scussion with IEEE 1588 WG<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; members, and I'm copying NETMOD members fo=
r YANG expertise.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; I think we can narrow the possible options=
 to two, so I'm starting a<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; new thread to focus on those.<o:p></o:p></=
span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; IEEE Std 1588-2008 is the time sync standa=
rd that specifies the<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; information model on which draft-ietf-tict=
oc-1588v2-yang-05 is<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; based. In IEEE Std 1588-2008, subclause 5.=
3.5 specifies the following<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; data type to identify each logical port in=
 the 1588 product:<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp; struct PortIdentity {<o:=
p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ClockI=
dentity clockIdentity;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uinteg=
er16 portNumber;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp; };<o:p></o:p></span></pr=
e>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; IEEE Std 1588-2008 uses this data type as =
the &quot;portIdentity&quot; of the<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; port in its on-the-wire protocol, state ma=
chines, and so on. In other<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; words, in the 1588 standard itself, portId=
entity is a &quot;real thing&quot;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; with real implementation.<o:p></o:p></span=
></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; IEEE Std 1588-2008 also specifies a list o=
f logical ports in each<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; &quot;clock&quot;, and portIdentity.portNu=
mber is used as the key to that list<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; of ports.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; In the YANG of draft-ietf-tictoc-1588v2-ya=
ng-05, we use YANG-style<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; names (e.g. port-list, port-number), but o=
therwise we've tried to keep<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; consistent to the IEEE Std 1588-2008 infor=
mation model.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; We have a challenge with port-number. If Y=
ANG represents port-identity<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; as a container within port-list, YANG does=
 not allow a key to be a<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; leaf within a container, so we cannot use =
port-identity/port-number as<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; the key to port-list.<o:p></o:p></span></p=
re>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; It seems that we have two options:<o:p></o=
:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; Option 1: Use a leafref<o:p></o:p></span><=
/pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; ---<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; YANG summary:<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; list port-ds-list {<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; key &quot;port-number&quot;;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; leaf port-number {<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; type uint16;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; }<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; container port-identity {<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; leaf clock-identity {<o:p></o:p></span>=
</pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; type clock-identity-t=
ype;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; config false;<o:p></o=
:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; leaf port-number {<o:p></o:p></span></p=
re>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; type leafref{<o:p></o=
:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pat=
h &quot;../../port-number&quot;;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<o:p></o:p></span></=
pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; config false;<o:p></o=
:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; }<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; }<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; This has disadvantages from the YANG persp=
ective, in that port-number<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; is duplicated. The &quot;config false&quot=
; is intended to mitigate YANG<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; implementation challenges, such that only =
one value of port-number is<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; provided for configuration.<o:p></o:p></sp=
an></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; Option 2: Use a grouping<o:p></o:p></span>=
</pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; ---<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; YANG summary:<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; grouping por=
t-identity-grouping {<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
leaf clock-identity {<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; type clock-identity-type;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
}<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
leaf port-number {<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; type uint16;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
}<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<o:p></o:p>=
</span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; list port-ds=
-list {<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
key &quot;port-number&quot;;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
uses port-identity-grouping;<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<o:p></o:p>=
</span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; This has disadvantages from the 1588 persp=
ective, in that it is not<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; possible for a 1588-aware management clien=
t to &quot;get&quot; portIdentity. We<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; are removing a 1588 &quot;real thing&quot;=
 from the data model in order to<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; accommodate a syntax limitation of YANG.<o=
:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">I think that in general when you go from an inf=
ormation model to a<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">concrete data model, you need to adapt to the d=
ata modelling language<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">you are using, and this will in most cases mean=
 that there will be<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">some differences; in some cases the data model =
structure is different,<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">and in some cases the data model will result in=
 a more detailed<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">model.&nbsp; How keys are specified is one such=
 example.&nbsp; If you were to<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">use SMIv2, you'd have to change the names (so t=
hat they are unique),<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">and you'd have to map the structures to concept=
ual tables.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">Clients need to understand the data model in us=
e (not just the<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">information model behid it).<o:p></o:p></span><=
/pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; Question for NETMOD experts<o:p></o:p></sp=
an></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; ---<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; My personal preference is Option 1 (leafre=
f). Nevertheless, if the<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; &quot;config false&quot; does not provide =
sufficient mitigation for today's YANG<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; implementations, we can go with Option 2.<=
o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">I don't think any implementation would have any=
 problem supporting<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">option 1, but it does look a bit odd.&nbsp; Als=
o, it only &quot;helps&quot; if the<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">client is getting the data using &lt;get&gt;, b=
ut it will not help if it is<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">using &lt;get-config&gt;.<o:p></o:p></span></pr=
e>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">I think that the cleanest solution is to not tr=
y to completely mimic<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">the structure from the information model, but m=
ake sure that the<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">text in the description statements make it clea=
r that the data model<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">looks different compared to the information mod=
el, in order to help<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">the readers.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">/martin<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; Feedback is very much appreciated.<o:p></o=
:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; Thanks folks,<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; Rodney Cummings<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; Co-author draft-ietf-tictoc-1588v2-yang-05=
<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; __________________________________________=
_____<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; netmod mailing list<o:p></o:p></span></pre=
>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <a href=3D"mailto:netmod@ietf.org"><span s=
tyle=3D"color:#337AB7;text-decoration:none">netmod@ietf.org</span></a><o:p>=
</o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <a href=3D"https://www.ietf.org/mailman/li=
stinfo/netmod"><span style=3D"color:#337AB7;text-decoration:none">https://w=
ww.ietf.org/mailman/listinfo/netmod</span></a><o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333">&gt; <o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-fam=
ily:Consolas;color:#333333"><o:p>&nbsp;</o:p></span></pre>
<h4 style=3D"mso-margin-top-alt:7.5pt;margin-right:0cm;margin-bottom:7.5pt;=
margin-left:0cm;background:white;box-sizing: border-box;color:inherit">
<span style=3D"font-size:13.5pt;font-family:&quot;inherit&quot;,serif;color=
:#333333;font-weight:normal">References:<o:p></o:p></span></h4>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:#333333;mso-margin-top-alt:auto;marg=
in-right:0cm;mso-margin-bottom-alt:auto;margin-left:36.0pt;text-align:left;=
mso-list:l0 level1 lfo1;background:white;direction:ltr;unicode-bidi:embed;b=
ox-sizing: border-box">
<span style=3D"font-size:10.5pt;font-family:&quot;Helvetica&quot;,sans-seri=
f"><a href=3D"https://mailarchive.ietf.org/arch/msg/tictoc/lm1xq37jffkSMms2=
XJll3N-ydC0"><span style=3D"color:#337AB7;text-decoration:none">[TICTOC] dr=
aft-ietf-tictoc-1588v2-yang-05: port-number</span></a><br>
Rodney Cummings &lt;rodney.cummings@ni.com&gt;<o:p></o:p></span></li></ul>
<p class=3D"MsoNormal" dir=3D"RTL"><span dir=3D"LTR"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
</body>
</html>

--_000_61ee5a45c081476ea39332fd27561090advaopticalcom_--


From nobody Tue Oct  3 11:24:30 2017
Return-Path: <rodney.cummings@ni.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 E49CC134FCA; Tue,  3 Oct 2017 11:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nio365.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3DiIohfbcyIc; Tue,  3 Oct 2017 11:24:22 -0700 (PDT)
Received: from mx0b-00010702.pphosted.com (mx0a-00010702.pphosted.com [148.163.156.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 154DC134FC6; Tue,  3 Oct 2017 11:24:22 -0700 (PDT)
Received: from pps.filterd (m0098781.ppops.net [127.0.0.1]) by mx0a-00010702.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v93IKMBX005400; Tue, 3 Oct 2017 13:24:20 -0500
Received: from nam02-sn1-obe.outbound.protection.outlook.com (mail-sn1nam02lp0018.outbound.protection.outlook.com [216.32.180.18]) by mx0a-00010702.pphosted.com with ESMTP id 2dcfp4g2kc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 03 Oct 2017 13:24:19 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nio365.onmicrosoft.com; s=selector1-ni-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=hxIWRnDWa65EIDl1c6AqhIfFZncxNRA42UoAawJpgdM=; b=hiLMbA+fdNOYQl4VCtmwd7HHxqo/9neO+YJOIIU9BHCc0EDK1asdrpFEyk88KFfBM9pqhp69hRDq2gm5XOEkB4CsAhrP9v3htSGi8WX9UFoOIRMssXapUj9q0dZWtz5dMRpMhUek4oBfIaowJas0aT+eVoY+Y/vTrMKnIb4dSQA=
Received: from DM2PR0401MB1389.namprd04.prod.outlook.com (10.160.219.156) by DM2PR0401MB1392.namprd04.prod.outlook.com (10.160.221.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.77.7; Tue, 3 Oct 2017 18:24:17 +0000
Received: from DM2PR0401MB1389.namprd04.prod.outlook.com ([fe80::b172:affa:cf1d:384e]) by DM2PR0401MB1389.namprd04.prod.outlook.com ([fe80::b172:affa:cf1d:384e%18]) with mapi id 15.20.0077.016; Tue, 3 Oct 2017 18:24:17 +0000
From: Rodney Cummings <rodney.cummings@ni.com>
To: Martin Bjorklund <mbj@tail-f.com>
CC: "tictoc@ietf.org" <tictoc@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
Thread-Index: AdM7naceqW92Otk+TBSUBZ12gBb0TQADKMgAADGI7JA=
Date: Tue, 3 Oct 2017 18:24:17 +0000
Message-ID: <DM2PR0401MB1389477D61B90ED604E7EF0F92720@DM2PR0401MB1389.namprd04.prod.outlook.com>
References: <DM2PR0401MB13896A98E4D5799F369EB71C927D0@DM2PR0401MB1389.namprd04.prod.outlook.com> <20171002.201430.1078877259363120382.mbj@tail-f.com>
In-Reply-To: <20171002.201430.1078877259363120382.mbj@tail-f.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.164.62.43]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM2PR0401MB1392; 6:WAZVXN1MV8W/XZZDtYh+Sni28gtAZa7DH95PsVLnFZmnkgmQiWlaToy3T4kf8rg6kfGZMHbcZuPQOm6O3qzZXWS9YkRNY5GVgl2LSmH6cMU3jNCAQCRvmpIZcvzrVtkggS6X144mdutqvufOMIBDnxNU5su8JZXpYFv8MjTkySmkkKrt9TU1dKj6ZRPCC+ClvNuaUauKlAZl7MgvxvzZzTwfV53zrHJJtlIF0S6ytKcuJvkqamLpuCK5DndL/ooSnkq01IlCyW/ObuPodfP6qpJ+xEEp6rTr/oJnelFTjh8EGI/9y4dwtMONZouVrrlPD955XenuLunjThRxDCc1YQ==; 5:NwkrQ4tucDvMX9xlqpM0XqPf+3sXSPtvgAzri7axr8fBu5OcpAUOKJWSuJjS5lP7ggy9qTFc+YbSavFs9jjGpqAtlNw5BTWy9Alw9yxAj0rjqhrggZQTfTq0rYS6WsA/cFTyeih7hg5YPCkEdlK6Yg==; 24:/bQCkzJ2hIh0nzdKR3yn9i6Qeahi/DruyXraAq1lX5n+zr7NYcQzBfFWSOvk73IGhXGC4rh2bhdIZQrx2gWu8pNZNvuFd+5NY6yAizlT474=; 7:uOLysw97HuQqYvAvu2UPk1hOzX3iofwcU7FibQX6Hw739l5yDZH5zObMhugYZ90Gt1yzpvgvpa6EuTQYLaNJF12PxqU+h/vL4Thuv1B7ZpkCCGuRyH7xuKaUiZHztxojegViN32oocvMUB+PMvF8bHxe2oDVL8hlMSjnIaneSsfhR//Iz5ujiJk+MsId+7JDvX8HolUMFTIzqcoqbRMiMcA75G2waQa+xzMZrV13TiU=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: fe83d4fe-6c0a-49ac-afae-08d50a8bf58b
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254152)(2017052603199)(201703131423075)(201703031133081)(201702281549075); SRVR:DM2PR0401MB1392; 
x-ms-traffictypediagnostic: DM2PR0401MB1392:
x-exchange-antispam-report-test: UriScan:(10436049006162)(145744241990776);
x-microsoft-antispam-prvs: <DM2PR0401MB1392E874046252711E3876F092720@DM2PR0401MB1392.namprd04.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(100000703101)(100105400095)(3002001)(10201501046)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123555025)(20161123562025)(20161123564025)(20161123558100)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DM2PR0401MB1392; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DM2PR0401MB1392; 
x-forefront-prvs: 044968D9E1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(376002)(346002)(199003)(377454003)(51444003)(13464003)(189002)(24454002)(105586002)(2950100002)(74316002)(5660300001)(8676002)(6436002)(6916009)(81166006)(81156014)(7696004)(14454004)(50986999)(2906002)(54356999)(76176999)(3660700001)(6506006)(3280700002)(8936002)(25786009)(66066001)(229853002)(4326008)(3846002)(6116002)(102836003)(101416001)(33656002)(106356001)(966005)(478600001)(305945005)(7736002)(97736004)(99286003)(55016002)(53546010)(575784001)(230783001)(54906003)(9686003)(6306002)(2900100001)(53936002)(5250100002)(86362001)(6246003)(316002)(68736007)(189998001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0401MB1392; H:DM2PR0401MB1389.namprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ni.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ni.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Oct 2017 18:24:17.7534 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 87ba1f9a-44cd-43a6-b008-6fdb45a5204e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0401MB1392
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-03_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=30 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=30 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710030259
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/yYXcbYuDKw6PgFMdvCWiDKgVeYI>
Subject: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Oct 2017 18:24:25 -0000

Thanks Martin,

Your rationale sounds reasonable to me. We can use the description to
explain differences in the models for the reader.=20

Your rationale got me thinking a bit about clock-identity. The 1588
information model and protocol uses clock-identity as a member of
port-identity (along with port-number). Nevertheless, that
instance-list[instance-number]/port-identity/clock-identity=20
is equivalent to instance-list[instance-number]/clock-identity
(part of grouping default-ds-entry in draft-ietf-tictoc-1588v2-yang-05).
So... we are currently repeating clock-identity as we repeated
port-number. If we apply your rationale, we can remove that
repetition as well.

I propose that we go with Option 2, but without using a grouping,
and use the same approach for clock-identity.=20

This would look like:

list port-ds-list {
   key "port-number";
   leaf port-number {
      description=20
         "Port number.
         =20
         The data sets (i.e. information model) of IEEE Std 1588-2008
         specify a member portDS.portIdentity, which uses a typed=20
         struct with members clockIdentity and portNumber.

         In this YANG data model, portIdentity is not provided as
         a container, but both of its members are provided as a leaf.
         portIdentity.portNumber is provided as this port-number leaf
         in YANG. portIdentity.clockIdentity is provided as the
         clock-identity leaf in the instance (i.e. ../../clock-identity).";
      type uint16;
   }
}

Rodney

> -----Original Message-----
> From: Martin Bjorklund [mailto:mbj@tail-f.com]
> Sent: Monday, October 2, 2017 1:15 PM
> To: Rodney Cummings <rodney.cummings@ni.com>
> Cc: tictoc@ietf.org; netmod@ietf.org
> Subject: Re: [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
>=20
> Rodney Cummings <rodney.cummings@ni.com> wrote:
> > Hi folks,
> >
> > One of the last topics that we need to resolve for WG Last Call of
> > draft-ietf-tictoc-1588v2-yang-05 is the representation of port-number,
> > which serves as the key to the list of 1588 port data sets
> > (i.e. port-list). I've had some offline discussion with IEEE 1588 WG
> > members, and I'm copying NETMOD members for YANG expertise.
> >
> > I think we can narrow the possible options to two, so I'm starting a
> > new thread to focus on those.
> >
> > IEEE Std 1588-2008 is the time sync standard that specifies the
> > information model on which draft-ietf-tictoc-1588v2-yang-05 is
> > based. In IEEE Std 1588-2008, subclause 5.3.5 specifies the following
> > data type to identify each logical port in the 1588 product:
> >    struct PortIdentity {
> >       ClockIdentity clockIdentity;
> >       Uinteger16 portNumber;
> >    };
> > IEEE Std 1588-2008 uses this data type as the "portIdentity" of the
> > port in its on-the-wire protocol, state machines, and so on. In other
> > words, in the 1588 standard itself, portIdentity is a "real thing"
> > with real implementation.
> >
> > IEEE Std 1588-2008 also specifies a list of logical ports in each
> > "clock", and portIdentity.portNumber is used as the key to that list
> > of ports.
> >
> > In the YANG of draft-ietf-tictoc-1588v2-yang-05, we use YANG-style
> > names (e.g. port-list, port-number), but otherwise we've tried to keep
> > consistent to the IEEE Std 1588-2008 information model.
> >
> > We have a challenge with port-number. If YANG represents port-identity
> > as a container within port-list, YANG does not allow a key to be a
> > leaf within a container, so we cannot use port-identity/port-number as
> > the key to port-list.
> >
> > It seems that we have two options:
> >
> > Option 1: Use a leafref
> > ---
> >
> > YANG summary:
> >
> >         list port-ds-list {
> >           key "port-number";
> >           leaf port-number {
> >             type uint16;
> >           }
> >           container port-identity {
> >              leaf clock-identity {
> >                 type clock-identity-type;
> >                 config false;
> >              }
> >              leaf port-number {
> >                 type leafref{
> >                    path "../../port-number";
> >                 }
> >                 config false;
> >              }
> >           }
> >         }
> >
> > This has disadvantages from the YANG perspective, in that port-number
> > is duplicated. The "config false" is intended to mitigate YANG
> > implementation challenges, such that only one value of port-number is
> > provided for configuration.
> >
> > Option 2: Use a grouping
> > ---
> >
> > YANG summary:
> >
> >      grouping port-identity-grouping {
> >        leaf clock-identity {
> >          type clock-identity-type;
> >        }
> >        leaf port-number {
> >          type uint16;
> >        }
> >      }
> >      list port-ds-list {
> >        key "port-number";
> >        uses port-identity-grouping;
> >      }
> >
> > This has disadvantages from the 1588 perspective, in that it is not
> > possible for a 1588-aware management client to "get" portIdentity. We
> > are removing a 1588 "real thing" from the data model in order to
> > accommodate a syntax limitation of YANG.
>=20
> I think that in general when you go from an information model to a
> concrete data model, you need to adapt to the data modelling language
> you are using, and this will in most cases mean that there will be
> some differences; in some cases the data model structure is different,
> and in some cases the data model will result in a more detailed
> model.  How keys are specified is one such example.  If you were to
> use SMIv2, you'd have to change the names (so that they are unique),
> and you'd have to map the structures to conceptual tables.
>=20
> Clients need to understand the data model in use (not just the
> information model behid it).
>=20
> > Question for NETMOD experts
> > ---
> >
> > My personal preference is Option 1 (leafref). Nevertheless, if the
> > "config false" does not provide sufficient mitigation for today's YANG
> > implementations, we can go with Option 2.
>=20
> I don't think any implementation would have any problem supporting
> option 1, but it does look a bit odd.  Also, it only "helps" if the
> client is getting the data using <get>, but it will not help if it is
> using <get-config>.
>=20
>=20
> I think that the cleanest solution is to not try to completely mimic
> the structure from the information model, but make sure that the
> text in the description statements make it clear that the data model
> looks different compared to the information model, in order to help
> the readers.
>=20
>=20
>=20
> /martin
>=20
>=20
>=20
> >
> > Feedback is very much appreciated.
> >
> > Thanks folks,
> > Rodney Cummings
> > Co-author draft-ietf-tictoc-1588v2-yang-05
> >
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-
> 3A__www.ietf.org_mailman_listinfo_netmod&d=3DDwICAg&c=3DI_0YwoKy7z5LMTVdy=
O6YCi
> E2uzI1jjZZuIPelcSjixA&r=3DWA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=
=3DHQ-
> S1mMpOcwPGLxrc9fTcSPc3vMBTRPINVlW5icLVhI&s=3DvW2fbaZlyBrALsCxc0EC961aVU3t=
5gm
> DrURSXdnPR8A&e=3D
> >


From nobody Tue Oct  3 11:27:55 2017
Return-Path: <rodney.cummings@ni.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 42D26134FCD for <tictoc@ietfa.amsl.com>; Tue,  3 Oct 2017 11:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nio365.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uBbnsUYcP1aH for <tictoc@ietfa.amsl.com>; Tue,  3 Oct 2017 11:27:52 -0700 (PDT)
Received: from mx0b-00010702.pphosted.com (mx0b-00010702.pphosted.com [148.163.158.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E8E81346EB for <tictoc@ietf.org>; Tue,  3 Oct 2017 11:27:51 -0700 (PDT)
Received: from pps.filterd (m0098778.ppops.net [127.0.0.1]) by mx0b-00010702.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v93IR3sJ013723; Tue, 3 Oct 2017 13:27:47 -0500
Received: from nam02-sn1-obe.outbound.protection.outlook.com (mail-sn1nam02lp0017.outbound.protection.outlook.com [216.32.180.17]) by mx0b-00010702.pphosted.com with ESMTP id 2dcfa809er-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 03 Oct 2017 13:27:47 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nio365.onmicrosoft.com; s=selector1-ni-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Gzp4sRSkO4FDPBgFbE0Sns/AYOdaE8diqbb5LAvG1Ig=; b=e86z20zQOSyzcsukIeXzcI1GiKfhrUfCUNGFl6HXbnaYE7sbarCQcrF7py1pgJEdeianGTRsdFc57pGc43mHziXWPfUkasvZDKuTx7jA3sE2LaCc4UU8BMvcwz+3X9Mlueoyiw1ekvO9lq2rF7zQzIPBz1pgNUMzdo1r/HCRu/k=
Received: from DM2PR0401MB1389.namprd04.prod.outlook.com (10.160.219.156) by DM2PR0401MB1392.namprd04.prod.outlook.com (10.160.221.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.77.7; Tue, 3 Oct 2017 18:27:45 +0000
Received: from DM2PR0401MB1389.namprd04.prod.outlook.com ([fe80::b172:affa:cf1d:384e]) by DM2PR0401MB1389.namprd04.prod.outlook.com ([fe80::b172:affa:cf1d:384e%18]) with mapi id 15.20.0077.016; Tue, 3 Oct 2017 18:27:45 +0000
From: Rodney Cummings <rodney.cummings@ni.com>
To: Opher Ronen <ORonen@advaoptical.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
Thread-Index: AdM8bdngM/8ciPVNQMCmZAXgPxsbzQABysXQ
Date: Tue, 3 Oct 2017 18:27:45 +0000
Message-ID: <DM2PR0401MB1389F715891EC85EB25E7E3592720@DM2PR0401MB1389.namprd04.prod.outlook.com>
References: <61ee5a45c081476ea39332fd27561090@advaoptical.com>
In-Reply-To: <61ee5a45c081476ea39332fd27561090@advaoptical.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.164.62.43]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM2PR0401MB1392; 6:QVIsaOe2+aqR9yHGsr8Gp3+UASe+CpthBtjY3j+wUCMtdNvL/wmERY17GST8NUvDYFUBJOs5Q+mRF1WfVWTwM7HvQv7D3y7V/Ztp5T7ZB7gIuQUlOAx6SVQJaWX1InZq0aWZq3HlD6pmw5UtiFPVTkvTl1MDVa/6wGGavxC5yWsacrCo2Fs4BfcVviiG4PSOmdtj6Chy1AZYMiogEb3SzJIYEVimnrBIqUMxAodfRZ0exReTqB1x3LDOd/uxygELhvFcN99P/iDrtwWRZ4JR6lnxIgpBJ+eQ0M8KqVDyLvjB8DelMUOPlrxZtjYfhwap5rdYrlp195wAm1MjLww/BQ==; 5:sM+ipuaJQ2MoAalAAdLpjZzppKXFT3MQNoDLU2L0+MzMurGDEmRiBJy7calC8YHuXDlNIn+l/gIFqvNjW+8dpe00rkLrDKVlriGDxALjABQGxBVBPwF8k6x88nUsDiX/mA1x5ChzHqKzj55GMph4AA==; 24:yXB4YVWB5eApg/H3Q8g2giH+3KY3aUCE0J4Anr/d4LLzpbzAYClAsuPCwvfi3S+57U3E7kB9AFf5wfeMflIO60GsSFk/D4nutTcgu5XVsAQ=; 7:/MgOSerFEi9Ie1wwAMtXXWpoUst6JLdw7Eg7NpAKX6n5ZaHUuBjpSZoFhb6lzdWz/rbY9R4xpDmkcmRc1MRiiDC4PqIQe/73El+LfcQu2S3TG4/xe2iix2c44P2oYSVT/ji8qEHHvzFOJifZRF7fiWQlbrqRN3iOizJlaLws3EBEhmqXpPIAGx1ic3QEFV3OT7HdtjWBLYFa53i2wvefjGV7x2qnnmCCaqkJFXrqKMk=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: d5a34833-bab4-445b-c96b-08d50a8c7130
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254152)(2017052603199)(201703131423075)(201703031133081)(201702281549075); SRVR:DM2PR0401MB1392; 
x-ms-traffictypediagnostic: DM2PR0401MB1392:
x-exchange-antispam-report-test: UriScan:(10436049006162)(145744241990776)(17755550239193); 
x-microsoft-antispam-prvs: <DM2PR0401MB1392131C97B5112A2437736B92720@DM2PR0401MB1392.namprd04.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(100000703101)(100105400095)(3002001)(10201501046)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123555025)(20161123562025)(20161123564025)(20161123558100)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DM2PR0401MB1392; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DM2PR0401MB1392; 
x-forefront-prvs: 044968D9E1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(376002)(346002)(199003)(377454003)(51444003)(189002)(61484003)(105586002)(2950100002)(74316002)(5660300001)(8676002)(6436002)(81166006)(81156014)(7696004)(14454004)(50986999)(2906002)(54356999)(76176999)(561944003)(3660700001)(6506006)(3280700002)(8936002)(25786009)(66066001)(229853002)(3846002)(6116002)(102836003)(101416001)(33656002)(106356001)(966005)(478600001)(305945005)(7736002)(97736004)(99286003)(55016002)(53546010)(575784001)(2501003)(110136005)(230783001)(9686003)(6306002)(2900100001)(53936002)(5250100002)(86362001)(6246003)(316002)(68736007)(189998001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0401MB1392; H:DM2PR0401MB1389.namprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ni.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ni.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Oct 2017 18:27:45.1171 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 87ba1f9a-44cd-43a6-b008-6fdb45a5204e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0401MB1392
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-03_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=30 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=30 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710030261
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/HGVOfqtc_RwThw-fZZt1hiRgM8M>
Subject: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Oct 2017 18:27:54 -0000

As the kids say... "lol".

Our emails crossed paths.

The proposal I just sent reflects Opher's view (I hope), as well as others.=
=20

Opher: My latest proposal removes the duplicate clockIdentity entirely.=20

From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of Opher Ronen
Sent: Tuesday, October 3, 2017 12:57 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-numbe=
r

Hi Rodney & all,
=A0=A0 I am somewhat belatedly posting a post to this thread following an o=
ffline correspondence with Rodney in context of this subject. I hope my fee=
dback is not too late to be constructive, and will be posted correctly as t=
his is my first post to this thread.
=A0=A0 I will also apologize in advance that I will be mostly offline till =
mid-October, so will likely be able to reply to responses only then.
=A0=A0 Rodney shared with me the consideration on this aspect, and I believ=
e his recent post attempt to integrate my offline on this topic.
=A0=A0 I hope some more detailed feedback will hopefully assist this draft =
advance in a manner aligned with my perception on this aspect from my invol=
vement in the P1588 WG in general and it's Management SC in specific.
=A0=A0 I will first comment that following my correspondence with Rodney th=
at I believe (with reservation given my low involvement in direct implement=
ation of management interfaces) that an interface that would enable perform=
ing a get to obtain an overall structure including the information comprims=
ing a PTP portIdentity appears nice to have. I would assume that this infor=
mation will not be the most frequent aspect a management system would query=
, but easing obtaining it if overhead is reasonable may be worthwhile.
=A0=A0 A possibly more significant comment is to stress that the clockIdent=
ity portion of the portIdentity attribute is equal in all port within a PTP=
 Instance, and equal to the clockIdentity attribute with the clock data set=
. This is explicitly stressed by a new sentence added to the next revision =
draft, intended to clarify this to the reader: "The clockIdentity portion o=
f a portIdentity is equal to the clockIdentity of the PTP Instance that the=
 PTP Port is included in, and is therefore equal among all PTP Ports inside=
 the PTP Instance."=20
=A0=A0In my view regardless of the option followed for the data model for p=
ortIdentity, the ability to directly configure the clockIdentity portion of=
 it should be prevented to avoid generating a configuration violating the a=
bove status (possible hampering the operation of the PTP protocol if later =
used as data for portIdentity on the wire). =A0
=A0=A0=A0If I understood correct yang data model enable to provide a leafre=
f pointer to the clockIdentity from the instance data set level, possibly b=
est reflecting the actual limitations regarding the portIdentity structure.

Best Regards,
=A0=A0=A0 Opher Ronen
=20
Rodney Cummings <mailto:rodney.cummings@ni.com&gt; wrote:
> Hi folks,
>=20
> One of the last topics that we need to resolve for WG Last Call of
> draft-ietf-tictoc-1588v2-yang-05 is the representation of port-number,
> which serves as the key to the list of 1588 port data sets
> (i.e. port-list). I've had some offline discussion with IEEE 1588 WG
> members, and I'm copying NETMOD members for YANG expertise.
>=20
> I think we can narrow the possible options to two, so I'm starting a
> new thread to focus on those.
>=20
> IEEE Std 1588-2008 is the time sync standard that specifies the
> information model on which draft-ietf-tictoc-1588v2-yang-05 is
> based. In IEEE Std 1588-2008, subclause 5.3.5 specifies the following
> data type to identify each logical port in the 1588 product:
>=A0=A0=A0 struct PortIdentity {
>=A0=A0=A0=A0=A0=A0 ClockIdentity clockIdentity;
>=A0=A0=A0=A0=A0=A0 Uinteger16 portNumber;
>=A0=A0=A0 };
> IEEE Std 1588-2008 uses this data type as the "portIdentity" of the
> port in its on-the-wire protocol, state machines, and so on. In other
> words, in the 1588 standard itself, portIdentity is a "real thing"
> with real implementation.
>=A0=20
> IEEE Std 1588-2008 also specifies a list of logical ports in each
> "clock", and portIdentity.portNumber is used as the key to that list
> of ports.
>=20
> In the YANG of draft-ietf-tictoc-1588v2-yang-05, we use YANG-style
> names (e.g. port-list, port-number), but otherwise we've tried to keep
> consistent to the IEEE Std 1588-2008 information model.
>=20
> We have a challenge with port-number. If YANG represents port-identity
> as a container within port-list, YANG does not allow a key to be a
> leaf within a container, so we cannot use port-identity/port-number as
> the key to port-list.
>=20
> It seems that we have two options:
>=20
> Option 1: Use a leafref
> ---
>=20
> YANG summary:
>=20
>=A0=A0=A0=A0=A0=A0=A0=A0 list port-ds-list {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 key "port-number";
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 leaf port-number {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 type uint16;
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 }
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 container port-identity {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 leaf clock-identity {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 type clock-identity-type;
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 config false;
>=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 leaf port-number {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 type leafref{
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 path "../../port=
-number";
>=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=A0 config false;
>=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 }
>=20
> This has disadvantages from the YANG perspective, in that port-number
> is duplicated. The "config false" is intended to mitigate YANG
> implementation challenges, such that only one value of port-number is
> provided for configuration.
>=20
> Option 2: Use a grouping
> ---
>=20
> YANG summary:
>=20
>=A0=A0=A0=A0=A0 grouping port-identity-grouping {
>=A0=A0=A0=A0=A0=A0=A0 leaf clock-identity {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0 type clock-identity-type;
>=A0=A0=A0=A0=A0=A0=A0 }
>=A0=A0=A0=A0=A0=A0=A0 leaf port-number {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0 type uint16;
>=A0=A0=A0=A0=A0=A0=A0 }
>=A0=A0=A0=A0=A0 }
>=A0=A0=A0=A0=A0 list port-ds-list {
>=A0=A0=A0=A0=A0=A0=A0 key "port-number";
>=A0=A0=A0=A0=A0=A0=A0 uses port-identity-grouping;
>=A0=A0=A0=A0=A0 }
>=20
> This has disadvantages from the 1588 perspective, in that it is not
> possible for a 1588-aware management client to "get" portIdentity. We
> are removing a 1588 "real thing" from the data model in order to
> accommodate a syntax limitation of YANG.

I think that in general when you go from an information model to a
concrete data model, you need to adapt to the data modelling language
you are using, and this will in most cases mean that there will be
some differences; in some cases the data model structure is different,
and in some cases the data model will result in a more detailed
model.=A0 How keys are specified is one such example.=A0 If you were to
use SMIv2, you'd have to change the names (so that they are unique),
and you'd have to map the structures to conceptual tables.

Clients need to understand the data model in use (not just the
information model behid it).

> Question for NETMOD experts
> ---
>=20
> My personal preference is Option 1 (leafref). Nevertheless, if the
> "config false" does not provide sufficient mitigation for today's YANG
> implementations, we can go with Option 2.

I don't think any implementation would have any problem supporting
option 1, but it does look a bit odd.=A0 Also, it only "helps" if the
client is getting the data using <get>, but it will not help if it is
using <get-config>.


I think that the cleanest solution is to not try to completely mimic
the structure from the information model, but make sure that the
text in the description statements make it clear that the data model
looks different compared to the information model, in order to help
the readers.



/martin



>=20
> Feedback is very much appreciated.
>=20
> Thanks folks,
> Rodney Cummings
> Co-author draft-ietf-tictoc-1588v2-yang-05
>=20
> _______________________________________________
> netmod mailing list
> mailto:netmod@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailm=
an_listinfo_netmod&d=3DDwMFAg&c=3DI_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSji=
xA&r=3DWA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=3DTvq4PvUNekeS1IF42ycx=
_7KyiF9Ag9bUucZE51SFvCw&s=3DBahOyOIDKpAWICQOgrlu0aga7dBde8X07-oq2ilONkw&e=
=3D
>=20

References:
. https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__mailarchive.ietf.o=
rg_arch_msg_tictoc_lm1xq37jffkSMms2XJll3N-2DydC0&d=3DDwMFAg&c=3DI_0YwoKy7z5=
LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA&r=3DWA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnbo=
KbZ8k&m=3DTvq4PvUNekeS1IF42ycx_7KyiF9Ag9bUucZE51SFvCw&s=3D8SBqP6TRNUiieCBN4=
IZ6qzNQ5ZEW8pCBAm1kAULa-Mg&e=3D
Rodney Cummings <mailto:rodney.cummings@ni.com>


From nobody Tue Oct  3 11:39:53 2017
Return-Path: <ORonen@advaoptical.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 23567132EA7 for <tictoc@ietfa.amsl.com>; Tue,  3 Oct 2017 11:39:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZS_lwC0DCGNe for <tictoc@ietfa.amsl.com>; Tue,  3 Oct 2017 11:39:49 -0700 (PDT)
Received: from mail.advaoptical.com (mail.advaoptical.com [91.217.199.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4F50134658 for <tictoc@ietf.org>; Tue,  3 Oct 2017 11:39:48 -0700 (PDT)
Received: from MUC-S-EX16A.advaoptical.com ([172.20.1.18]) by muc-vsrv-fsmail.advaoptical.com (8.16.0.20/8.16.0.20) with ESMTPS id v93IdkGI005650 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA256 bits=128 verify=FAIL); Tue, 3 Oct 2017 20:39:46 +0200
Received: from MUC-S-EX16C.advaoptical.com (172.20.1.27) by MUC-S-EX16A.advaoptical.com (172.20.1.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.27; Tue, 3 Oct 2017 20:39:46 +0200
Received: from MUC-S-EX16C.advaoptical.com (172.20.1.27) by MUC-S-EX16C.advaoptical.com (172.20.1.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1261.27; Tue, 3 Oct 2017 20:39:46 +0200
Received: from MUC-S-EX16C.advaoptical.com ([fe80::8863:592b:3654:9597]) by MUC-S-EX16C.advaoptical.com ([fe80::8863:592b:3654:9597%3]) with mapi id 15.01.1261.026; Tue, 3 Oct 2017 20:39:46 +0200
From: Opher Ronen <ORonen@advaoptical.com>
To: Rodney Cummings <rodney.cummings@ni.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
Thread-Index: AdM8bdngM/8ciPVNQMCmZAXgPxsbzQABysXQAABLAdA=
Date: Tue, 3 Oct 2017 18:39:46 +0000
Message-ID: <bbdb4db2fcb84090b7cd705b810612a7@advaoptical.com>
References: <61ee5a45c081476ea39332fd27561090@advaoptical.com> <DM2PR0401MB1389F715891EC85EB25E7E3592720@DM2PR0401MB1389.namprd04.prod.outlook.com>
In-Reply-To: <DM2PR0401MB1389F715891EC85EB25E7E3592720@DM2PR0401MB1389.namprd04.prod.outlook.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.1.231]
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-03_08:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/FLoHEIDdLp11MaV2IOTpt8scUnI>
Subject: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Oct 2017 18:39:52 -0000

Thanks Rodney,

 If I understand your latest suggestion correctly it appears a good choice =
for this initial yang model, taking a "less-is-more" approach.

Someone interested in knowing e.g. all portId's currently configured can ap=
pend the port-number values from the port-ds-list to the clockID from the i=
nstance level.

I assume if more structured to "get" portID is deemed an important feature =
it can be added in a later version of the data-model.

Opher

-----Original Message-----
From: Rodney Cummings [mailto:rodney.cummings@ni.com]=20
Sent: Tuesday, October 3, 2017 9:28 PM
To: Opher Ronen <ORonen@advaoptical.com>; tictoc@ietf.org
Subject: RE: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-n=
umber

As the kids say... "lol".

Our emails crossed paths.

The proposal I just sent reflects Opher's view (I hope), as well as others.=
=20

Opher: My latest proposal removes the duplicate clockIdentity entirely.=20

From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of Opher Ronen
Sent: Tuesday, October 3, 2017 12:57 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-numbe=
r

Hi Rodney & all,
=A0=A0 I am somewhat belatedly posting a post to this thread following an o=
ffline correspondence with Rodney in context of this subject. I hope my fee=
dback is not too late to be constructive, and will be posted correctly as t=
his is my first post to this thread.
=A0=A0 I will also apologize in advance that I will be mostly offline till =
mid-October, so will likely be able to reply to responses only then.
=A0=A0 Rodney shared with me the consideration on this aspect, and I believ=
e his recent post attempt to integrate my offline on this topic.
=A0=A0 I hope some more detailed feedback will hopefully assist this draft =
advance in a manner aligned with my perception on this aspect from my invol=
vement in the P1588 WG in general and it's Management SC in specific.
=A0=A0 I will first comment that following my correspondence with Rodney th=
at I believe (with reservation given my low involvement in direct implement=
ation of management interfaces) that an interface that would enable perform=
ing a get to obtain an overall structure including the information comprims=
ing a PTP portIdentity appears nice to have. I would assume that this infor=
mation will not be the most frequent aspect a management system would query=
, but easing obtaining it if overhead is reasonable may be worthwhile.
=A0=A0 A possibly more significant comment is to stress that the clockIdent=
ity portion of the portIdentity attribute is equal in all port within a PTP=
 Instance, and equal to the clockIdentity attribute with the clock data set=
. This is explicitly stressed by a new sentence added to the next revision =
draft, intended to clarify this to the reader: "The clockIdentity portion o=
f a portIdentity is equal to the clockIdentity of the PTP Instance that the=
 PTP Port is included in, and is therefore equal among all PTP Ports inside=
 the PTP Instance."=20
=A0=A0In my view regardless of the option followed for the data model for p=
ortIdentity, the ability to directly configure the clockIdentity portion of=
 it should be prevented to avoid generating a configuration violating the a=
bove status (possible hampering the operation of the PTP protocol if later =
used as data for portIdentity on the wire).
=A0=A0=A0If I understood correct yang data model enable to provide a leafre=
f pointer to the clockIdentity from the instance data set level, possibly b=
est reflecting the actual limitations regarding the portIdentity structure.

Best Regards,
=A0=A0=A0 Opher Ronen
=20
Rodney Cummings <mailto:rodney.cummings@ni.com&gt; wrote:
> Hi folks,
>=20
> One of the last topics that we need to resolve for WG Last Call of
> draft-ietf-tictoc-1588v2-yang-05 is the representation of port-number,=20
> which serves as the key to the list of 1588 port data sets (i.e.=20
> port-list). I've had some offline discussion with IEEE 1588 WG=20
> members, and I'm copying NETMOD members for YANG expertise.
>=20
> I think we can narrow the possible options to two, so I'm starting a=20
> new thread to focus on those.
>=20
> IEEE Std 1588-2008 is the time sync standard that specifies the =20
>information model on which draft-ietf-tictoc-1588v2-yang-05 is  based.=20
>In IEEE Std 1588-2008, subclause 5.3.5 specifies the following  data=20
>type to identify each logical port in the 1588 product:
>=A0=A0=A0 struct PortIdentity {
>=A0=A0=A0=A0=A0=A0 ClockIdentity clockIdentity;
>=A0=A0=A0=A0=A0=A0 Uinteger16 portNumber;
>=A0=A0=A0 };
> IEEE Std 1588-2008 uses this data type as the "portIdentity" of the =20
>port in its on-the-wire protocol, state machines, and so on. In other =20
>words, in the 1588 standard itself, portIdentity is a "real thing"
> with real implementation.
>=A0=20
> IEEE Std 1588-2008 also specifies a list of logical ports in each=20
> "clock", and portIdentity.portNumber is used as the key to that list=20
> of ports.
>=20
> In the YANG of draft-ietf-tictoc-1588v2-yang-05, we use YANG-style=20
> names (e.g. port-list, port-number), but otherwise we've tried to keep=20
> consistent to the IEEE Std 1588-2008 information model.
>=20
> We have a challenge with port-number. If YANG represents port-identity=20
> as a container within port-list, YANG does not allow a key to be a=20
> leaf within a container, so we cannot use port-identity/port-number as=20
> the key to port-list.
>=20
> It seems that we have two options:
>=20
> Option 1: Use a leafref
> ---
>=20
> YANG summary:
>=20
>=A0=A0=A0=A0=A0=A0=A0=A0 list port-ds-list {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 key "port-number";
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 leaf port-number {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 type uint16;
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 }
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 container port-identity {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 leaf clock-identity {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 type clock-identity-type;
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 config false;
>=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 leaf port-number {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 type leafref{
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 path "../../port=
-number";
>=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=A0 config false;
>=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 }
>=20
> This has disadvantages from the YANG perspective, in that port-number=20
> is duplicated. The "config false" is intended to mitigate YANG=20
> implementation challenges, such that only one value of port-number is=20
> provided for configuration.
>=20
> Option 2: Use a grouping
> ---
>=20
> YANG summary:
>=20
>=A0=A0=A0=A0=A0 grouping port-identity-grouping {
>=A0=A0=A0=A0=A0=A0=A0 leaf clock-identity {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0 type clock-identity-type;
>=A0=A0=A0=A0=A0=A0=A0 }
>=A0=A0=A0=A0=A0=A0=A0 leaf port-number {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0 type uint16;
>=A0=A0=A0=A0=A0=A0=A0 }
>=A0=A0=A0=A0=A0 }
>=A0=A0=A0=A0=A0 list port-ds-list {
>=A0=A0=A0=A0=A0=A0=A0 key "port-number";
>=A0=A0=A0=A0=A0=A0=A0 uses port-identity-grouping;
>=A0=A0=A0=A0=A0 }
>=20
> This has disadvantages from the 1588 perspective, in that it is not=20
> possible for a 1588-aware management client to "get" portIdentity. We=20
> are removing a 1588 "real thing" from the data model in order to=20
> accommodate a syntax limitation of YANG.

I think that in general when you go from an information model to a concrete=
 data model, you need to adapt to the data modelling language you are using=
, and this will in most cases mean that there will be some differences; in =
some cases the data model structure is different, and in some cases the dat=
a model will result in a more detailed model.=A0 How keys are specified is =
one such example.=A0 If you were to use SMIv2, you'd have to change the nam=
es (so that they are unique), and you'd have to map the structures to conce=
ptual tables.

Clients need to understand the data model in use (not just the information =
model behid it).

> Question for NETMOD experts
> ---
>=20
> My personal preference is Option 1 (leafref). Nevertheless, if the=20
> "config false" does not provide sufficient mitigation for today's YANG=20
> implementations, we can go with Option 2.

I don't think any implementation would have any problem supporting option 1=
, but it does look a bit odd.=A0 Also, it only "helps" if the client is get=
ting the data using <get>, but it will not help if it is using <get-config>=
.


I think that the cleanest solution is to not try to completely mimic the st=
ructure from the information model, but make sure that the text in the desc=
ription statements make it clear that the data model looks different compar=
ed to the information model, in order to help the readers.



/martin



>=20
> Feedback is very much appreciated.
>=20
> Thanks folks,
> Rodney Cummings
> Co-author draft-ietf-tictoc-1588v2-yang-05
>=20
> _______________________________________________
> netmod mailing list
> mailto:netmod@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mail
> man_listinfo_netmod&d=3DDwMFAg&c=3DI_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelc=
S
> jixA&r=3DWA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=3DTvq4PvUNekeS1IF4=
2
> ycx_7KyiF9Ag9bUucZE51SFvCw&s=3DBahOyOIDKpAWICQOgrlu0aga7dBde8X07-oq2ilON
> kw&e=3D
>=20

References:
. https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__mailarchive.ietf.o=
rg_arch_msg_tictoc_lm1xq37jffkSMms2XJll3N-2DydC0&d=3DDwMFAg&c=3DI_0YwoKy7z5=
LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA&r=3DWA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnbo=
KbZ8k&m=3DTvq4PvUNekeS1IF42ycx_7KyiF9Ag9bUucZE51SFvCw&s=3D8SBqP6TRNUiieCBN4=
IZ6qzNQ5ZEW8pCBAm1kAULa-Mg&e=3D
Rodney Cummings <mailto:rodney.cummings@ni.com>


From nobody Mon Oct  9 04:47:35 2017
Return-Path: <jiangyuanlong@huawei.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 187C3134512 for <tictoc@ietfa.amsl.com>; Mon,  9 Oct 2017 04:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LPW4n9wOM7UM for <tictoc@ietfa.amsl.com>; Mon,  9 Oct 2017 04:47:31 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E77D134222 for <tictoc@ietf.org>; Mon,  9 Oct 2017 04:47:30 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML710-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DQE59619; Mon, 09 Oct 2017 11:47:28 +0000 (GMT)
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 9 Oct 2017 12:47:26 +0100
Received: from DGGEML507-MBX.china.huawei.com ([169.254.2.79]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0301.000; Mon, 9 Oct 2017 19:47:15 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: Opher Ronen <ORonen@advaoptical.com>, Rodney Cummings <rodney.cummings@ni.com>, "tictoc@ietf.org" <tictoc@ietf.org>
CC: Zongning <zongning@huawei.com>, "Liushucheng (Will Liu)" <liushucheng@huawei.com>, Zhuhengjun <zhuhengjun@huawei.com>
Thread-Topic: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
Thread-Index: AdM8bdngM/8ciPVNQMCmZAXgPxsbzQABysXQAABLAdABHxA5cA==
Date: Mon, 9 Oct 2017 11:47:15 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5D03AD@dggeml507-mbx.china.huawei.com>
References: <61ee5a45c081476ea39332fd27561090@advaoptical.com> <DM2PR0401MB1389F715891EC85EB25E7E3592720@DM2PR0401MB1389.namprd04.prod.outlook.com> <bbdb4db2fcb84090b7cd705b810612a7@advaoptical.com>
In-Reply-To: <bbdb4db2fcb84090b7cd705b810612a7@advaoptical.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.74.202.215]
Content-Type: text/plain; charset="utf-7"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.59DB61D0.0139, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.2.79, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 0e3ce6c446a90f0eb98a011f3f26556f
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/AOrUgpog-BVPgRhCOFJpUXnTnGo>
Subject: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Oct 2017 11:47:33 -0000

Hi Opher and all,

Thanks much for all the comments. So the consensus seems to me is - we agre=
ed to model both port-number and clock-identity in the port-ds-list.
This will reflected in our next revision of draft-ietf-tictoc-1588v2-yang.
Definitely, later versions can take another approach with version control c=
apability of YANG.

Cheers,
Yuanlong

-----Original Message-----
From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Behalf Of Ophe=
r Ronen
Sent: Wednesday, October 04, 2017 2:40 AM
To: Rodney Cummings+ADs- tictoc+AEA-ietf.org
Subject: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-1588v2-yan=
g-05: port-number

Thanks Rodney,

 If I understand your latest suggestion correctly it appears a good choice =
for this initial yang model, taking a +ACI-less-is-more+ACI- approach.

Someone interested in knowing e.g. all portId's currently configured can ap=
pend the port-number values from the port-ds-list to the clockID from the i=
nstance level.

I assume if more structured to +ACI-get+ACI- portID is deemed an important =
feature it can be added in a later version of the data-model.

Opher

-----Original Message-----
From: Rodney Cummings +AFs-mailto:rodney.cummings+AEA-ni.com+AF0-
Sent: Tuesday, October 3, 2017 9:28 PM
To: Opher Ronen +ADw-ORonen+AEA-advaoptical.com+AD4AOw- tictoc+AEA-ietf.org
Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-1588v2=
-yang-05: port-number

As the kids say... +ACI-lol+ACI-.

Our emails crossed paths.

The proposal I just sent reflects Opher's view (I hope), as well as others.=
=20

Opher: My latest proposal removes the duplicate clockIdentity entirely.=20

From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Behalf Of Ophe=
r Ronen
Sent: Tuesday, October 3, 2017 12:57 PM
To: tictoc+AEA-ietf.org
Subject: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-1588v2-yan=
g-05: port-number

Hi Rodney +ACY- all,
+AKAAoA- I am somewhat belatedly posting a post to this thread following an=
 offline correspondence with Rodney in context of this subject. I hope my f=
eedback is not too late to be constructive, and will be posted correctly as=
 this is my first post to this thread.
+AKAAoA- I will also apologize in advance that I will be mostly offline til=
l mid-October, so will likely be able to reply to responses only then.
+AKAAoA- Rodney shared with me the consideration on this aspect, and I beli=
eve his recent post attempt to integrate my offline on this topic.
+AKAAoA- I hope some more detailed feedback will hopefully assist this draf=
t advance in a manner aligned with my perception on this aspect from my inv=
olvement in the P1588 WG in general and it's Management SC in specific.
+AKAAoA- I will first comment that following my correspondence with Rodney =
that I believe (with reservation given my low involvement in direct impleme=
ntation of management interfaces) that an interface that would enable perfo=
rming a get to obtain an overall structure including the information compri=
msing a PTP portIdentity appears nice to have. I would assume that this inf=
ormation will not be the most frequent aspect a management system would que=
ry, but easing obtaining it if overhead is reasonable may be worthwhile.
+AKAAoA- A possibly more significant comment is to stress that the clockIde=
ntity portion of the portIdentity attribute is equal in all port within a P=
TP Instance, and equal to the clockIdentity attribute with the clock data s=
et. This is explicitly stressed by a new sentence added to the next revisio=
n draft, intended to clarify this to the reader: +ACI-The clockIdentity por=
tion of a portIdentity is equal to the clockIdentity of the PTP Instance th=
at the PTP Port is included in, and is therefore equal among all PTP Ports =
inside the PTP Instance.+ACI-=20
+AKAAoA-In my view regardless of the option followed for the data model for=
 portIdentity, the ability to directly configure the clockIdentity portion =
of it should be prevented to avoid generating a configuration violating the=
 above status (possible hampering the operation of the PTP protocol if late=
r used as data for portIdentity on the wire).
+AKAAoACg-If I understood correct yang data model enable to provide a leafr=
ef pointer to the clockIdentity from the instance data set level, possibly =
best reflecting the actual limitations regarding the portIdentity structure=
.

Best Regards,
+AKAAoACg- Opher Ronen
=20
Rodney Cummings +ADw-mailto:rodney.cummings+AEA-ni.com+ACY-gt+ADs- wrote:
+AD4- Hi folks,
+AD4-=20
+AD4- One of the last topics that we need to resolve for WG Last Call of
+AD4- draft-ietf-tictoc-1588v2-yang-05 is the representation of port-number=
,=20
+AD4- which serves as the key to the list of 1588 port data sets (i.e.
+AD4- port-list). I've had some offline discussion with IEEE 1588 WG=20
+AD4- members, and I'm copying NETMOD members for YANG expertise.
+AD4-=20
+AD4- I think we can narrow the possible options to two, so I'm starting a=
=20
+AD4- new thread to focus on those.
+AD4-=20
+AD4- IEEE Std 1588-2008 is the time sync standard that specifies the=20
+AD4-information model on which draft-ietf-tictoc-1588v2-yang-05 is  based.
+AD4-In IEEE Std 1588-2008, subclause 5.3.5 specifies the following  data=20
+AD4-type to identify each logical port in the 1588 product:
+AD4AoACgAKA- struct PortIdentity +AHs-
+AD4AoACgAKAAoACgAKA- ClockIdentity clockIdentity+ADs-
+AD4AoACgAKAAoACgAKA- Uinteger16 portNumber+ADs-
+AD4AoACgAKA- +AH0AOw-
+AD4- IEEE Std 1588-2008 uses this data type as the +ACI-portIdentity+ACI- =
of the=20
+AD4-port in its on-the-wire protocol, state machines, and so on. In other=
=20
+AD4-words, in the 1588 standard itself, portIdentity is a +ACI-real thing+=
ACI-
+AD4- with real implementation.
+AD4AoA-=20
+AD4- IEEE Std 1588-2008 also specifies a list of logical ports in each=20
+AD4- +ACI-clock+ACI-, and portIdentity.portNumber is used as the key to th=
at list=20
+AD4- of ports.
+AD4-=20
+AD4- In the YANG of draft-ietf-tictoc-1588v2-yang-05, we use YANG-style=20
+AD4- names (e.g. port-list, port-number), but otherwise we've tried to kee=
p=20
+AD4- consistent to the IEEE Std 1588-2008 information model.
+AD4-=20
+AD4- We have a challenge with port-number. If YANG represents port-identit=
y=20
+AD4- as a container within port-list, YANG does not allow a key to be a=20
+AD4- leaf within a container, so we cannot use port-identity/port-number a=
s=20
+AD4- the key to port-list.
+AD4-=20
+AD4- It seems that we have two options:
+AD4-=20
+AD4- Option 1: Use a leafref
+AD4- ---
+AD4-=20
+AD4- YANG summary:
+AD4-=20
+AD4AoACgAKAAoACgAKAAoACg- list port-ds-list +AHs-
+AD4AoACgAKAAoACgAKAAoACgAKAAoA- key +ACI-port-number+ACIAOw-
+AD4AoACgAKAAoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKA- type uint16+ADs-
+AD4AoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4AoACgAKAAoACgAKAAoACgAKAAoA- container port-identity +AHs-
+AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- leaf clock-identity +AHs-
+AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- type clock-identity-type+A=
Ds-
+AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- config false+ADs-
+AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- type leafref+AHs-
+AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- path +ACI-../../po=
rt-number+ACIAOw-
+AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- config false+ADs-
+AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4AoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4AoACgAKAAoACgAKAAoACg- +AH0-
+AD4-=20
+AD4- This has disadvantages from the YANG perspective, in that port-number=
=20
+AD4- is duplicated. The +ACI-config false+ACI- is intended to mitigate YAN=
G=20
+AD4- implementation challenges, such that only one value of port-number is=
=20
+AD4- provided for configuration.
+AD4-=20
+AD4- Option 2: Use a grouping
+AD4- ---
+AD4-=20
+AD4- YANG summary:
+AD4-=20
+AD4AoACgAKAAoACg- grouping port-identity-grouping +AHs-
+AD4AoACgAKAAoACgAKAAoA- leaf clock-identity +AHs-
+AD4AoACgAKAAoACgAKAAoACgAKA- type clock-identity-type+ADs-
+AD4AoACgAKAAoACgAKAAoA- +AH0-
+AD4AoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4AoACgAKAAoACgAKAAoACgAKA- type uint16+ADs-
+AD4AoACgAKAAoACgAKAAoA- +AH0-
+AD4AoACgAKAAoACg- +AH0-
+AD4AoACgAKAAoACg- list port-ds-list +AHs-
+AD4AoACgAKAAoACgAKAAoA- key +ACI-port-number+ACIAOw-
+AD4AoACgAKAAoACgAKAAoA- uses port-identity-grouping+ADs-
+AD4AoACgAKAAoACg- +AH0-
+AD4-=20
+AD4- This has disadvantages from the 1588 perspective, in that it is not=20
+AD4- possible for a 1588-aware management client to +ACI-get+ACI- portIden=
tity. We=20
+AD4- are removing a 1588 +ACI-real thing+ACI- from the data model in order=
 to=20
+AD4- accommodate a syntax limitation of YANG.

I think that in general when you go from an information model to a concrete=
 data model, you need to adapt to the data modelling language you are using=
, and this will in most cases mean that there will be some differences+ADs-=
 in some cases the data model structure is different, and in some cases the=
 data model will result in a more detailed model.+AKA- How keys are specifi=
ed is one such example.+AKA- If you were to use SMIv2, you'd have to change=
 the names (so that they are unique), and you'd have to map the structures =
to conceptual tables.

Clients need to understand the data model in use (not just the information =
model behid it).

+AD4- Question for NETMOD experts
+AD4- ---
+AD4-=20
+AD4- My personal preference is Option 1 (leafref). Nevertheless, if the=20
+AD4- +ACI-config false+ACI- does not provide sufficient mitigation for tod=
ay's YANG=20
+AD4- implementations, we can go with Option 2.

I don't think any implementation would have any problem supporting option 1=
, but it does look a bit odd.+AKA- Also, it only +ACI-helps+ACI- if the cli=
ent is getting the data using +ADw-get+AD4-, but it will not help if it is =
using +ADw-get-config+AD4-.


I think that the cleanest solution is to not try to completely mimic the st=
ructure from the information model, but make sure that the text in the desc=
ription statements make it clear that the data model looks different compar=
ed to the information model, in order to help the readers.



/martin



+AD4-=20
+AD4- Feedback is very much appreciated.
+AD4-=20
+AD4- Thanks folks,
+AD4- Rodney Cummings
+AD4- Co-author draft-ietf-tictoc-1588v2-yang-05
+AD4-=20
+AD4- +AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8A=
XwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
+AD4- netmod mailing list
+AD4- mailto:netmod+AEA-ietf.org
+AD4- https://urldefense.proofpoint.com/v2/url?u+AD0-https-3A+AF8AXw-www.ie=
tf.org+AF8-mail
+AD4- man+AF8-listinfo+AF8-netmod+ACY-d+AD0-DwMFAg+ACY-c+AD0-I+AF8-0YwoKy7z=
5LMTVdyO6YCiE2uzI1jjZZuIPelcS
+AD4- jixA+ACY-r+AD0-WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k+ACY-m+AD0-=
Tvq4PvUNekeS1IF42
+AD4- ycx+AF8-7KyiF9Ag9bUucZE51SFvCw+ACY-s+AD0-BahOyOIDKpAWICQOgrlu0aga7dBd=
e8X07-oq2ilON
+AD4- kw+ACY-e+AD0-
+AD4-=20

References:
. https://urldefense.proofpoint.com/v2/url?u+AD0-https-3A+AF8AXw-mailarchiv=
e.ietf.org+AF8-arch+AF8-msg+AF8-tictoc+AF8-lm1xq37jffkSMms2XJll3N-2DydC0+AC=
Y-d+AD0-DwMFAg+ACY-c+AD0-I+AF8-0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA+AC=
Y-r+AD0-WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k+ACY-m+AD0-Tvq4PvUNekeS1=
IF42ycx+AF8-7KyiF9Ag9bUucZE51SFvCw+ACY-s+AD0-8SBqP6TRNUiieCBN4IZ6qzNQ5ZEW8p=
CBAm1kAULa-Mg+ACY-e+AD0-
Rodney Cummings +ADw-mailto:rodney.cummings+AEA-ni.com+AD4-

+AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF=
8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
TICTOC mailing list
TICTOC+AEA-ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


From nobody Mon Oct  9 08:38:48 2017
Return-Path: <rodney.cummings@ni.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 06519132D79 for <tictoc@ietfa.amsl.com>; Mon,  9 Oct 2017 08:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nio365.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M7tVz2RD6mQu for <tictoc@ietfa.amsl.com>; Mon,  9 Oct 2017 08:38:44 -0700 (PDT)
Received: from mx0b-00010702.pphosted.com (mx0a-00010702.pphosted.com [148.163.156.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29000133070 for <tictoc@ietf.org>; Mon,  9 Oct 2017 08:38:44 -0700 (PDT)
Received: from pps.filterd (m0098780.ppops.net [127.0.0.1]) by mx0a-00010702.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v99FamTd013129; Mon, 9 Oct 2017 10:38:33 -0500
Received: from nam03-co1-obe.outbound.protection.outlook.com (mail-co1nam03lp0018.outbound.protection.outlook.com [216.32.181.18]) by mx0a-00010702.pphosted.com with ESMTP id 2dgbqxg38a-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 09 Oct 2017 10:38:32 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nio365.onmicrosoft.com; s=selector1-ni-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ldeWAOYjukp3EwjXX/CdrJPr3U8+zQwilgVVu7VtPmU=; b=kUUBoX0s3uULNmfVpbZo1JtJKyCHZUizIVVxgw/3PbRj/d1sZZEjbE4DGI9rFOJNdsKjhZYHn17tpTzYdCGuIdGcPg7rdRkPIPj68dkYccryZGCMFA2dHW0o6KK7FByK/yQVW16915MImS2IAwnKKN54Q+q+C1PdAMZdVPEk5h4=
Received: from CY1PR0401MB1536.namprd04.prod.outlook.com (10.163.19.154) by CY1PR0401MB1534.namprd04.prod.outlook.com (10.163.19.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.77.7; Mon, 9 Oct 2017 15:38:30 +0000
Received: from CY1PR0401MB1536.namprd04.prod.outlook.com ([10.163.19.154]) by CY1PR0401MB1536.namprd04.prod.outlook.com ([10.163.19.154]) with mapi id 15.20.0077.019; Mon, 9 Oct 2017 15:38:30 +0000
From: Rodney Cummings <rodney.cummings@ni.com>
To: Jiangyuanlong <jiangyuanlong@huawei.com>, Opher Ronen <ORonen@advaoptical.com>, "tictoc@ietf.org" <tictoc@ietf.org>
CC: Zongning <zongning@huawei.com>, "Liushucheng (Will Liu)" <liushucheng@huawei.com>, Zhuhengjun <zhuhengjun@huawei.com>
Thread-Topic: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
Thread-Index: AdM8bdngM/8ciPVNQMCmZAXgPxsbzQABysXQAABLAdABHxA5cAAIcc/w
Date: Mon, 9 Oct 2017 15:38:30 +0000
Message-ID: <CY1PR0401MB1536370FBF361DCF5242D0A792740@CY1PR0401MB1536.namprd04.prod.outlook.com>
References: <61ee5a45c081476ea39332fd27561090@advaoptical.com> <DM2PR0401MB1389F715891EC85EB25E7E3592720@DM2PR0401MB1389.namprd04.prod.outlook.com> <bbdb4db2fcb84090b7cd705b810612a7@advaoptical.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5D03AD@dggeml507-mbx.china.huawei.com>
In-Reply-To: <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5D03AD@dggeml507-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.164.62.43]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR0401MB1534; 6:1GHPC31JpvjlBVn7oksMwg9gP+WJ5oQ0ng56/eaQOJUbonbplJjsEBEx4PPu+tzk8nGylW62YcCUgvGdkyfFsOW76kGriV4YsTZf6fmQMvmL9MlPIlJJzlWMtAntg7bGtZlA70YrC7VxdjiIhy2uOZqs3930dzVicQjoIQlW2iCU0ICxv+GLoFXWub2Zkbzu6ZY2P/ZT9IupaUZ8l3twmOh4bJzlswacSEdw2PD8R6C+FnkwYbMv+K81kBgV0H61dfNYxZg45o6EnEEOJI0T9iCyU8GwUS15gMuK75zE3O4YsxF1z0qWWrk3NM0xRN0ofBVhY3qWOX70bF0S1i17TQ==; 5:lXn7yTakO0IETE3emkMyewXJY0AX7DsEDGFNyvT/lN/KXfl3ZxMOAGazWk0LD8pzE1rtr7oRnDi3rQ19/pk8a4d8qg36WtK43TiHKqYEV+FiwmN4IycQeQzc9tuaD3Dwnf4wpvroSGCjWOQIVdMjJA==; 24:whyY3dQRNiydeQJluGqQ8KFR9SIlHzOmPC5HsnTPMj7nA4Ital4Ybda4KoyXxqtppPqiY+emAOMzTrZLsAIueUzKZyqW1fLCUMPQJ+0ofm4=; 7:EQFVVWa1L71iFmXhXHN0EsZBgJ7ZAt2klapjUdMqoGBXbBZTB9CwWk6pdhwCY1aPKBqeovD73nPLg30UTZBsX8+mLfDXxlQDtka+lNjlGJKFTbqEl5V1V4HSY4JqHl+eL4mjLFsAI3ynkwD5lwVKrJl+q1q9Flpt0wdApFNw1V/PdF0ZupmnedBD5semwoV+6IyIAb8X4Q1Yatijcyq0lFTaRbAkyW1vIqMePij0m7A=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 43faf6bf-6a3d-4dff-5905-08d50f2bcad1
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254152)(2017052603199)(201703131423075)(201703031133081)(201702281549075); SRVR:CY1PR0401MB1534; 
x-ms-traffictypediagnostic: CY1PR0401MB1534:
x-exchange-antispam-report-test: UriScan:(10436049006162)(50582790962513)(100405760836317)(145744241990776)(17755550239193);
x-microsoft-antispam-prvs: <CY1PR0401MB153461B5D2408A492B361F4192740@CY1PR0401MB1534.namprd04.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(100000703101)(100105400095)(3002001)(10201501046)(6041248)(20161123558100)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123562025)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY1PR0401MB1534; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY1PR0401MB1534; 
x-forefront-prvs: 045584D28C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(346002)(376002)(199003)(13464003)(377454003)(189002)(51444003)(61484003)(2950100002)(101416001)(5660300001)(66066001)(229853002)(7696004)(230783001)(105586002)(53546010)(86362001)(575784001)(6506006)(6436002)(561944003)(106356001)(77096006)(68736007)(305945005)(74316002)(189998001)(7736002)(25786009)(316002)(8936002)(97736004)(53936002)(81166006)(8676002)(81156014)(93886005)(14454004)(478600001)(966005)(2501003)(33656002)(110136005)(50986999)(76176999)(54356999)(99286003)(55016002)(2900100001)(6246003)(6116002)(6306002)(54906003)(9686003)(102836003)(3846002)(4326008)(2906002)(3280700002)(3660700001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0401MB1534; H:CY1PR0401MB1536.namprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ni.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-7"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ni.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Oct 2017 15:38:30.2114 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 87ba1f9a-44cd-43a6-b008-6fdb45a5204e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0401MB1534
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-09_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=30 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=30 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710090228
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/PhrLq3fwJvdd2fUcV1vYndprYn0>
Subject: Re: [TICTOC] [netmod] draft-ietf-tictoc-1588v2-yang-05: port-number
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Oct 2017 15:38:47 -0000

Hi Yuanlong,

To be clear my proposal is:
- Model port-number directly in port-list as the key.
- Do not model clock-identity in port-list.
- Do not model port-identity in port-list.
- In the description of port-number, mention that port-identity is not expl=
icitly modeled in YANG, but implicitly through the use of port-list+AFsAXQ-=
/port-number and instance-list+AFsAXQ-/clock-identity. See my previous emai=
l for proposed text.

Rodney

+AD4- -----Original Message-----
+AD4- From: Jiangyuanlong +AFs-mailto:jiangyuanlong+AEA-huawei.com+AF0-
+AD4- Sent: Monday, October 9, 2017 6:47 AM
+AD4- To: Opher Ronen +ADs- Rodney Cummings +ADs- tictoc+AEA-ietf.org
+AD4- Cc: Zongning +ADs- Liushucheng (Will Liu) +ADs- Zhuhengjun
+AD4- Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-=
1588v2-yang-05: port-
+AD4- number
+AD4-=20
+AD4- Hi Opher and all,
+AD4-=20
+AD4- Thanks much for all the comments. So the consensus seems to me is - w=
e
+AD4- agreed to model both port-number and clock-identity in the port-ds-li=
st.
+AD4- This will reflected in our next revision of draft-ietf-tictoc-1588v2-=
yang.
+AD4- Definitely, later versions can take another approach with version con=
trol
+AD4- capability of YANG.
+AD4-=20
+AD4- Cheers,
+AD4- Yuanlong
+AD4-=20
+AD4- -----Original Message-----
+AD4- From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Behalf O=
f Opher Ronen
+AD4- Sent: Wednesday, October 04, 2017 2:40 AM
+AD4- To: Rodney Cummings+ADs- tictoc+AEA-ietf.org
+AD4- Subject: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-1588=
v2-yang-05: port-
+AD4- number
+AD4-=20
+AD4- Thanks Rodney,
+AD4-=20
+AD4-  If I understand your latest suggestion correctly it appears a good c=
hoice
+AD4- for this initial yang model, taking a +ACI-less-is-more+ACI- approach=
.
+AD4-=20
+AD4- Someone interested in knowing e.g. all portId's currently configured =
can
+AD4- append the port-number values from the port-ds-list to the clockID fr=
om
+AD4- the instance level.
+AD4-=20
+AD4- I assume if more structured to +ACI-get+ACI- portID is deemed an impo=
rtant feature
+AD4- it can be added in a later version of the data-model.
+AD4-=20
+AD4- Opher
+AD4-=20
+AD4- -----Original Message-----
+AD4- From: Rodney Cummings +AFs-mailto:rodney.cummings+AEA-ni.com+AF0-
+AD4- Sent: Tuesday, October 3, 2017 9:28 PM
+AD4- To: Opher Ronen +ADw-ORonen+AEA-advaoptical.com+AD4AOw- tictoc+AEA-ie=
tf.org
+AD4- Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-=
1588v2-yang-05: port-
+AD4- number
+AD4-=20
+AD4- As the kids say... +ACI-lol+ACI-.
+AD4-=20
+AD4- Our emails crossed paths.
+AD4-=20
+AD4- The proposal I just sent reflects Opher's view (I hope), as well as
+AD4- others.
+AD4-=20
+AD4- Opher: My latest proposal removes the duplicate clockIdentity entirel=
y.
+AD4-=20
+AD4- From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Behalf O=
f Opher Ronen
+AD4- Sent: Tuesday, October 3, 2017 12:57 PM
+AD4- To: tictoc+AEA-ietf.org
+AD4- Subject: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-1588=
v2-yang-05: port-
+AD4- number
+AD4-=20
+AD4- Hi Rodney +ACY- all,
+AD4- +AKAAoA- I am somewhat belatedly posting a post to this thread follow=
ing an
+AD4- offline correspondence with Rodney in context of this subject. I hope=
 my
+AD4- feedback is not too late to be constructive, and will be posted corre=
ctly
+AD4- as this is my first post to this thread.
+AD4- +AKAAoA- I will also apologize in advance that I will be mostly offli=
ne till
+AD4- mid-October, so will likely be able to reply to responses only then.
+AD4- +AKAAoA- Rodney shared with me the consideration on this aspect, and =
I believe
+AD4- his recent post attempt to integrate my offline on this topic.
+AD4- +AKAAoA- I hope some more detailed feedback will hopefully assist thi=
s draft
+AD4- advance in a manner aligned with my perception on this aspect from my
+AD4- involvement in the P1588 WG in general and it's Management SC in spec=
ific.
+AD4- +AKAAoA- I will first comment that following my correspondence with R=
odney that
+AD4- I believe (with reservation given my low involvement in direct
+AD4- implementation of management interfaces) that an interface that would
+AD4- enable performing a get to obtain an overall structure including the
+AD4- information comprimsing a PTP portIdentity appears nice to have. I wo=
uld
+AD4- assume that this information will not be the most frequent aspect a
+AD4- management system would query, but easing obtaining it if overhead is
+AD4- reasonable may be worthwhile.
+AD4- +AKAAoA- A possibly more significant comment is to stress that the cl=
ockIdentity
+AD4- portion of the portIdentity attribute is equal in all port within a P=
TP
+AD4- Instance, and equal to the clockIdentity attribute with the clock dat=
a
+AD4- set. This is explicitly stressed by a new sentence added to the next
+AD4- revision draft, intended to clarify this to the reader: +ACI-The cloc=
kIdentity
+AD4- portion of a portIdentity is equal to the clockIdentity of the PTP
+AD4- Instance that the PTP Port is included in, and is therefore equal amo=
ng
+AD4- all PTP Ports inside the PTP Instance.+ACI-
+AD4- +AKAAoA-In my view regardless of the option followed for the data mod=
el for
+AD4- portIdentity, the ability to directly configure the clockIdentity por=
tion
+AD4- of it should be prevented to avoid generating a configuration violati=
ng
+AD4- the above status (possible hampering the operation of the PTP protoco=
l if
+AD4- later used as data for portIdentity on the wire).
+AD4- +AKAAoACg-If I understood correct yang data model enable to provide a=
 leafref
+AD4- pointer to the clockIdentity from the instance data set level, possib=
ly
+AD4- best reflecting the actual limitations regarding the portIdentity
+AD4- structure.
+AD4-=20
+AD4- Best Regards,
+AD4- +AKAAoACg- Opher Ronen
+AD4-=20
+AD4- Rodney Cummings +ADw-mailto:rodney.cummings+AEA-ni.com+ACY-gt+ADs- wr=
ote:
+AD4- +AD4- Hi folks,
+AD4- +AD4-
+AD4- +AD4- One of the last topics that we need to resolve for WG Last Call=
 of
+AD4- +AD4- draft-ietf-tictoc-1588v2-yang-05 is the representation of port-=
number,
+AD4- +AD4- which serves as the key to the list of 1588 port data sets (i.e=
.
+AD4- +AD4- port-list). I've had some offline discussion with IEEE 1588 WG
+AD4- +AD4- members, and I'm copying NETMOD members for YANG expertise.
+AD4- +AD4-
+AD4- +AD4- I think we can narrow the possible options to two, so I'm start=
ing a
+AD4- +AD4- new thread to focus on those.
+AD4- +AD4-
+AD4- +AD4- IEEE Std 1588-2008 is the time sync standard that specifies the
+AD4- +AD4-information model on which draft-ietf-tictoc-1588v2-yang-05 is  =
based.
+AD4- +AD4-In IEEE Std 1588-2008, subclause 5.3.5 specifies the following  =
data
+AD4- +AD4-type to identify each logical port in the 1588 product:
+AD4- +AD4AoACgAKA- struct PortIdentity +AHs-
+AD4- +AD4AoACgAKAAoACgAKA- ClockIdentity clockIdentity+ADs-
+AD4- +AD4AoACgAKAAoACgAKA- Uinteger16 portNumber+ADs-
+AD4- +AD4AoACgAKA- +AH0AOw-
+AD4- +AD4- IEEE Std 1588-2008 uses this data type as the +ACI-portIdentity=
+ACI- of the
+AD4- +AD4-port in its on-the-wire protocol, state machines, and so on. In =
other
+AD4- +AD4-words, in the 1588 standard itself, portIdentity is a +ACI-real =
thing+ACI-
+AD4- +AD4- with real implementation.
+AD4- +AD4-
+AD4- +AD4- IEEE Std 1588-2008 also specifies a list of logical ports in ea=
ch
+AD4- +AD4- +ACI-clock+ACI-, and portIdentity.portNumber is used as the key=
 to that list
+AD4- +AD4- of ports.
+AD4- +AD4-
+AD4- +AD4- In the YANG of draft-ietf-tictoc-1588v2-yang-05, we use YANG-st=
yle
+AD4- +AD4- names (e.g. port-list, port-number), but otherwise we've tried =
to keep
+AD4- +AD4- consistent to the IEEE Std 1588-2008 information model.
+AD4- +AD4-
+AD4- +AD4- We have a challenge with port-number. If YANG represents port-i=
dentity
+AD4- +AD4- as a container within port-list, YANG does not allow a key to b=
e a
+AD4- +AD4- leaf within a container, so we cannot use port-identity/port-nu=
mber as
+AD4- +AD4- the key to port-list.
+AD4- +AD4-
+AD4- +AD4- It seems that we have two options:
+AD4- +AD4-
+AD4- +AD4- Option 1: Use a leafref
+AD4- +AD4- ---
+AD4- +AD4-
+AD4- +AD4- YANG summary:
+AD4- +AD4-
+AD4- +AD4AoACgAKAAoACgAKAAoACg- list port-ds-list +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- key +ACI-port-number+ACIAOw-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKA- type uint16+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- container port-identity +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- leaf clock-identity +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- type clock-identity-=
type+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- config false+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- type leafref+AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- path +ACI-..=
/../port-number+ACIAOw-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- config false+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoACg- +AH0-
+AD4- +AD4-
+AD4- +AD4- This has disadvantages from the YANG perspective, in that port-=
number
+AD4- +AD4- is duplicated. The +ACI-config false+ACI- is intended to mitiga=
te YANG
+AD4- +AD4- implementation challenges, such that only one value of port-num=
ber is
+AD4- +AD4- provided for configuration.
+AD4- +AD4-
+AD4- +AD4- Option 2: Use a grouping
+AD4- +AD4- ---
+AD4- +AD4-
+AD4- +AD4- YANG summary:
+AD4- +AD4-
+AD4- +AD4AoACgAKAAoACg- grouping port-identity-grouping +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoA- leaf clock-identity +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKA- type clock-identity-type+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKA- type uint16+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACg- +AH0-
+AD4- +AD4AoACgAKAAoACg- list port-ds-list +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoA- key +ACI-port-number+ACIAOw-
+AD4- +AD4AoACgAKAAoACgAKAAoA- uses port-identity-grouping+ADs-
+AD4- +AD4AoACgAKAAoACg- +AH0-
+AD4- +AD4-
+AD4- +AD4- This has disadvantages from the 1588 perspective, in that it is=
 not
+AD4- +AD4- possible for a 1588-aware management client to +ACI-get+ACI- po=
rtIdentity. We
+AD4- +AD4- are removing a 1588 +ACI-real thing+ACI- from the data model in=
 order to
+AD4- +AD4- accommodate a syntax limitation of YANG.
+AD4-=20
+AD4- I think that in general when you go from an information model to a
+AD4- concrete data model, you need to adapt to the data modelling language=
 you
+AD4- are using, and this will in most cases mean that there will be some
+AD4- differences+ADs- in some cases the data model structure is different,=
 and in
+AD4- some cases the data model will result in a more detailed model.+AKA- =
How keys
+AD4- are specified is one such example.+AKA- If you were to use SMIv2, you=
'd have
+AD4- to change the names (so that they are unique), and you'd have to map =
the
+AD4- structures to conceptual tables.
+AD4-=20
+AD4- Clients need to understand the data model in use (not just the inform=
ation
+AD4- model behid it).
+AD4-=20
+AD4- +AD4- Question for NETMOD experts
+AD4- +AD4- ---
+AD4- +AD4-
+AD4- +AD4- My personal preference is Option 1 (leafref). Nevertheless, if =
the
+AD4- +AD4- +ACI-config false+ACI- does not provide sufficient mitigation f=
or today's YANG
+AD4- +AD4- implementations, we can go with Option 2.
+AD4-=20
+AD4- I don't think any implementation would have any problem supporting op=
tion
+AD4- 1, but it does look a bit odd.+AKA- Also, it only +ACI-helps+ACI- if =
the client is
+AD4- getting the data using +ADw-get+AD4-, but it will not help if it is u=
sing +ADw-get-
+AD4- config+AD4-.
+AD4-=20
+AD4-=20
+AD4- I think that the cleanest solution is to not try to completely mimic =
the
+AD4- structure from the information model, but make sure that the text in =
the
+AD4- description statements make it clear that the data model looks differ=
ent
+AD4- compared to the information model, in order to help the readers.
+AD4-=20
+AD4-=20
+AD4-=20
+AD4- /martin
+AD4-=20
+AD4-=20
+AD4-=20
+AD4- +AD4-
+AD4- +AD4- Feedback is very much appreciated.
+AD4- +AD4-
+AD4- +AD4- Thanks folks,
+AD4- +AD4- Rodney Cummings
+AD4- +AD4- Co-author draft-ietf-tictoc-1588v2-yang-05
+AD4- +AD4-
+AD4- +AD4- +AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw=
BfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
+AD4- +AD4- netmod mailing list
+AD4- +AD4- mailto:netmod+AEA-ietf.org
+AD4- +AD4- https://urldefense.proofpoint.com/v2/url?u+AD0-https-3A+AF8AXw-=
www.ietf.org+AF8-mail
+AD4- +AD4- man+AF8-listinfo+AF8-netmod+ACY-d+AD0-DwMFAg+ACY-c+AD0-I+AF8-0Y=
woKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcS
+AD4- +AD4- jixA+ACY-r+AD0-WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k+ACY-=
m+AD0-Tvq4PvUNekeS1IF42
+AD4- +AD4- ycx+AF8-7KyiF9Ag9bUucZE51SFvCw+ACY-s+AD0-BahOyOIDKpAWICQOgrlu0a=
ga7dBde8X07-oq2ilON
+AD4- +AD4- kw+ACY-e+AD0-
+AD4- +AD4-
+AD4-=20
+AD4- References:
+AD4- . https://urldefense.proofpoint.com/v2/url?u+AD0-https-
+AD4- 3A+AF8AXw-mailarchive.ietf.org+AF8-arch+AF8-msg+AF8-tictoc+AF8-lm1xq3=
7jffkSMms2XJll3N-
+AD4- 2DydC0+ACY-d+AD0-DwMFAg+ACY-c+AD0-I+AF8-0YwoKy7z5LMTVdyO6YCiE2uzI1jjZ=
ZuIPelcSjixA+ACY-r+AD0-WA71sf2o7D
+AD4- w7CbYhFt24DPjt3lJuupswWYdnboKbZ8k+ACY-m+AD0-Tvq4PvUNekeS1IF42ycx+AF8-=
7KyiF9Ag9bUucZE51
+AD4- SFvCw+ACY-s+AD0-8SBqP6TRNUiieCBN4IZ6qzNQ5ZEW8pCBAm1kAULa-Mg+ACY-e+AD0=
-
+AD4- Rodney Cummings +ADw-mailto:rodney.cummings+AEA-ni.com+AD4-
+AD4-=20
+AD4- +AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8A=
XwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
+AD4- TICTOC mailing list
+AD4- TICTOC+AEA-ietf.org
+AD4- https://urldefense.proofpoint.com/v2/url?u+AD0-https-
+AD4- 3A+AF8AXw-www.ietf.org+AF8-mailman+AF8-listinfo+AF8-tictoc+ACY-d+AD0-=
DwIFgQ+ACY-c+AD0-I+AF8-0YwoKy7z5LMTVdyO6YCi
+AD4- E2uzI1jjZZuIPelcSjixA+ACY-r+AD0-WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnb=
oKbZ8k+ACY-m+AD0-3vIq
+AD4- KhIleK3ifzu2gqWugIUX62HPLM5VReDafflfyVY+ACY-s+AD0-jy6sTQ1a-
+AD4- mKqq1ymmNMj7g1kzyAcFvPE9emfALot4FE+ACY-e+AD0-


From nobody Mon Oct  9 18:56:11 2017
Return-Path: <jiangyuanlong@huawei.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 9E55F132F3F for <tictoc@ietfa.amsl.com>; Mon,  9 Oct 2017 18:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gy8SOo2euvrl for <tictoc@ietfa.amsl.com>; Mon,  9 Oct 2017 18:56:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80BBF133207 for <tictoc@ietf.org>; Mon,  9 Oct 2017 18:55:36 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML713-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DXF74515; Tue, 10 Oct 2017 01:55:34 +0000 (GMT)
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 10 Oct 2017 02:55:33 +0100
Received: from DGGEML507-MBX.china.huawei.com ([169.254.2.79]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0301.000; Tue, 10 Oct 2017 09:55:23 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: Rodney Cummings <rodney.cummings@ni.com>, Opher Ronen <ORonen@advaoptical.com>, "tictoc@ietf.org" <tictoc@ietf.org>
CC: Zongning <zongning@huawei.com>, "Liushucheng (Will Liu)" <liushucheng@huawei.com>, Zhuhengjun <zhuhengjun@huawei.com>
Thread-Topic: draft-ietf-tictoc-1588v2-yang-05: clock-identity
Thread-Index: AQHTQWrVPOrClJwZhkyYqnRCyN3fmQ==
Date: Tue, 10 Oct 2017 01:55:22 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5D06E2@dggeml507-mbx.china.huawei.com>
References: <61ee5a45c081476ea39332fd27561090@advaoptical.com> <DM2PR0401MB1389F715891EC85EB25E7E3592720@DM2PR0401MB1389.namprd04.prod.outlook.com> <bbdb4db2fcb84090b7cd705b810612a7@advaoptical.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5D03AD@dggeml507-mbx.china.huawei.com> <CY1PR0401MB1536370FBF361DCF5242D0A792740@CY1PR0401MB1536.namprd04.prod.outlook.com>
In-Reply-To: <CY1PR0401MB1536370FBF361DCF5242D0A792740@CY1PR0401MB1536.namprd04.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.74.202.215]
Content-Type: text/plain; charset="utf-7"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.59DC2897.002A, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.2.79, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 21af42cfdc22aad7bea9d242abec2274
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/_FozTAg2NzGgQ956k4Wp_I5NoO4>
Subject: [TICTOC] draft-ietf-tictoc-1588v2-yang-05: clock-identity
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 10 Oct 2017 01:56:10 -0000

Dear Rodney,

Thank a lot for the clarification.
It is not clear to me how clock-identity is modeled indeed (I changed the m=
essage title to reflect it).=20
Currently, clock-identity is a member attribute in quite a few containers, =
such as default-ds, parent-ds. parent-port-identity, port-ds-list+AFsAXQ-. =
port-identity, transparent-clock-default-ds, and transparent-clock-port-ds-=
list+AFsAXQ-.port-identity, but instance-list+AFsAXQ- does not have clock-i=
dentity as its member. Are you suggesting to move clock-identity from defau=
lt-ds into instance-list+AFsAXQ-?
How do we model clock-identity in the transparent-clock-port-ds-list+AFsAXQ=
-, remove it too?=20

Regards,
Yuanlong

-----Original Message-----
From: Rodney Cummings +AFs-mailto:rodney.cummings+AEA-ni.com+AF0-=20
Sent: Monday, October 09, 2017 11:39 PM
To: Jiangyuanlong+ADs- Opher Ronen+ADs- tictoc+AEA-ietf.org
Cc: Zongning+ADs- Liushucheng (Will Liu)+ADs- Zhuhengjun
Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-1588v2=
-yang-05: port-number

Hi Yuanlong,

To be clear my proposal is:
- Model port-number directly in port-list as the key.
- Do not model clock-identity in port-list.
- Do not model port-identity in port-list.
- In the description of port-number, mention that port-identity is not expl=
icitly modeled in YANG, but implicitly through the use of port-list+AFsAXQ-=
/port-number and instance-list+AFsAXQ-/clock-identity. See my previous emai=
l for proposed text.

Rodney

+AD4- -----Original Message-----
+AD4- From: Jiangyuanlong +AFs-mailto:jiangyuanlong+AEA-huawei.com+AF0-
+AD4- Sent: Monday, October 9, 2017 6:47 AM
+AD4- To: Opher Ronen +ADs- Rodney Cummings +ADs- tictoc+AEA-ietf.org
+AD4- Cc: Zongning +ADs- Liushucheng (Will Liu) +ADs- Zhuhengjun
+AD4- Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-=
1588v2-yang-05:=20
+AD4- port- number
+AD4-=20
+AD4- Hi Opher and all,
+AD4-=20
+AD4- Thanks much for all the comments. So the consensus seems to me is - w=
e=20
+AD4- agreed to model both port-number and clock-identity in the port-ds-li=
st.
+AD4- This will reflected in our next revision of draft-ietf-tictoc-1588v2-=
yang.
+AD4- Definitely, later versions can take another approach with version=20
+AD4- control capability of YANG.
+AD4-=20
+AD4- Cheers,
+AD4- Yuanlong
+AD4-=20
+AD4- -----Original Message-----
+AD4- From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Behalf O=
f Opher Ronen
+AD4- Sent: Wednesday, October 04, 2017 2:40 AM
+AD4- To: Rodney Cummings+ADs- tictoc+AEA-ietf.org
+AD4- Subject: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-1588=
v2-yang-05: port-=20
+AD4- number
+AD4-=20
+AD4- Thanks Rodney,
+AD4-=20
+AD4-  If I understand your latest suggestion correctly it appears a good=20
+AD4- choice for this initial yang model, taking a +ACI-less-is-more+ACI- a=
pproach.
+AD4-=20
+AD4- Someone interested in knowing e.g. all portId's currently configured=
=20
+AD4- can append the port-number values from the port-ds-list to the clockI=
D=20
+AD4- from the instance level.
+AD4-=20
+AD4- I assume if more structured to +ACI-get+ACI- portID is deemed an impo=
rtant=20
+AD4- feature it can be added in a later version of the data-model.
+AD4-=20
+AD4- Opher
+AD4-=20
+AD4- -----Original Message-----
+AD4- From: Rodney Cummings +AFs-mailto:rodney.cummings+AEA-ni.com+AF0-
+AD4- Sent: Tuesday, October 3, 2017 9:28 PM
+AD4- To: Opher Ronen +ADw-ORonen+AEA-advaoptical.com+AD4AOw- tictoc+AEA-ie=
tf.org
+AD4- Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-=
1588v2-yang-05:=20
+AD4- port- number
+AD4-=20
+AD4- As the kids say... +ACI-lol+ACI-.
+AD4-=20
+AD4- Our emails crossed paths.
+AD4-=20
+AD4- The proposal I just sent reflects Opher's view (I hope), as well as=20
+AD4- others.
+AD4-=20
+AD4- Opher: My latest proposal removes the duplicate clockIdentity entirel=
y.
+AD4-=20
+AD4- From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Behalf O=
f Opher Ronen
+AD4- Sent: Tuesday, October 3, 2017 12:57 PM
+AD4- To: tictoc+AEA-ietf.org
+AD4- Subject: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-1588=
v2-yang-05: port-=20
+AD4- number
+AD4-=20
+AD4- Hi Rodney +ACY- all,
+AD4- +AKAAoA- I am somewhat belatedly posting a post to this thread follow=
ing an=20
+AD4- offline correspondence with Rodney in context of this subject. I hope=
=20
+AD4- my feedback is not too late to be constructive, and will be posted=20
+AD4- correctly as this is my first post to this thread.
+AD4- +AKAAoA- I will also apologize in advance that I will be mostly offli=
ne till=20
+AD4- mid-October, so will likely be able to reply to responses only then.
+AD4- +AKAAoA- Rodney shared with me the consideration on this aspect, and =
I=20
+AD4- believe his recent post attempt to integrate my offline on this topic=
.
+AD4- +AKAAoA- I hope some more detailed feedback will hopefully assist thi=
s draft=20
+AD4- advance in a manner aligned with my perception on this aspect from my=
=20
+AD4- involvement in the P1588 WG in general and it's Management SC in spec=
ific.
+AD4- +AKAAoA- I will first comment that following my correspondence with R=
odney=20
+AD4- that I believe (with reservation given my low involvement in direct=20
+AD4- implementation of management interfaces) that an interface that would=
=20
+AD4- enable performing a get to obtain an overall structure including the=
=20
+AD4- information comprimsing a PTP portIdentity appears nice to have. I=20
+AD4- would assume that this information will not be the most frequent=20
+AD4- aspect a management system would query, but easing obtaining it if=20
+AD4- overhead is reasonable may be worthwhile.
+AD4- +AKAAoA- A possibly more significant comment is to stress that the=20
+AD4- clockIdentity portion of the portIdentity attribute is equal in all=20
+AD4- port within a PTP Instance, and equal to the clockIdentity attribute=
=20
+AD4- with the clock data set. This is explicitly stressed by a new sentenc=
e=20
+AD4- added to the next revision draft, intended to clarify this to the=20
+AD4- reader: +ACI-The clockIdentity portion of a portIdentity is equal to =
the=20
+AD4- clockIdentity of the PTP Instance that the PTP Port is included in,=20
+AD4- and is therefore equal among all PTP Ports inside the PTP Instance.+A=
CI-
+AD4- +AKAAoA-In my view regardless of the option followed for the data mod=
el for=20
+AD4- portIdentity, the ability to directly configure the clockIdentity=20
+AD4- portion of it should be prevented to avoid generating a configuration=
=20
+AD4- violating the above status (possible hampering the operation of the=20
+AD4- PTP protocol if later used as data for portIdentity on the wire).
+AD4- +AKAAoACg-If I understood correct yang data model enable to provide a=
 leafref=20
+AD4- pointer to the clockIdentity from the instance data set level,=20
+AD4- possibly best reflecting the actual limitations regarding the=20
+AD4- portIdentity structure.
+AD4-=20
+AD4- Best Regards,
+AD4- +AKAAoACg- Opher Ronen
+AD4-=20
+AD4- Rodney Cummings +ADw-mailto:rodney.cummings+AEA-ni.com+ACY-gt+ADs- wr=
ote:
+AD4- +AD4- Hi folks,
+AD4- +AD4-
+AD4- +AD4- One of the last topics that we need to resolve for WG Last Call=
 of
+AD4- +AD4- draft-ietf-tictoc-1588v2-yang-05 is the representation of=20
+AD4- +AD4- port-number, which serves as the key to the list of 1588 port d=
ata sets (i.e.
+AD4- +AD4- port-list). I've had some offline discussion with IEEE 1588 WG=
=20
+AD4- +AD4- members, and I'm copying NETMOD members for YANG expertise.
+AD4- +AD4-
+AD4- +AD4- I think we can narrow the possible options to two, so I'm start=
ing a=20
+AD4- +AD4- new thread to focus on those.
+AD4- +AD4-
+AD4- +AD4- IEEE Std 1588-2008 is the time sync standard that specifies the=
=20
+AD4- +AD4-information model on which draft-ietf-tictoc-1588v2-yang-05 is  =
based.
+AD4- +AD4-In IEEE Std 1588-2008, subclause 5.3.5 specifies the following  =
data=20
+AD4- +AD4-type to identify each logical port in the 1588 product:
+AD4- +AD4AoACgAKA- struct PortIdentity +AHs-
+AD4- +AD4AoACgAKAAoACgAKA- ClockIdentity clockIdentity+ADs-
+AD4- +AD4AoACgAKAAoACgAKA- Uinteger16 portNumber+ADs-
+AD4- +AD4AoACgAKA- +AH0AOw-
+AD4- +AD4- IEEE Std 1588-2008 uses this data type as the +ACI-portIdentity=
+ACI- of the=20
+AD4- +AD4-port in its on-the-wire protocol, state machines, and so on. In =
other=20
+AD4- +AD4-words, in the 1588 standard itself, portIdentity is a +ACI-real =
thing+ACI-
+AD4- +AD4- with real implementation.
+AD4- +AD4-
+AD4- +AD4- IEEE Std 1588-2008 also specifies a list of logical ports in ea=
ch=20
+AD4- +AD4- +ACI-clock+ACI-, and portIdentity.portNumber is used as the key=
 to that list=20
+AD4- +AD4- of ports.
+AD4- +AD4-
+AD4- +AD4- In the YANG of draft-ietf-tictoc-1588v2-yang-05, we use YANG-st=
yle=20
+AD4- +AD4- names (e.g. port-list, port-number), but otherwise we've tried =
to=20
+AD4- +AD4- keep consistent to the IEEE Std 1588-2008 information model.
+AD4- +AD4-
+AD4- +AD4- We have a challenge with port-number. If YANG represents=20
+AD4- +AD4- port-identity as a container within port-list, YANG does not al=
low a=20
+AD4- +AD4- key to be a leaf within a container, so we cannot use=20
+AD4- +AD4- port-identity/port-number as the key to port-list.
+AD4- +AD4-
+AD4- +AD4- It seems that we have two options:
+AD4- +AD4-
+AD4- +AD4- Option 1: Use a leafref
+AD4- +AD4- ---
+AD4- +AD4-
+AD4- +AD4- YANG summary:
+AD4- +AD4-
+AD4- +AD4AoACgAKAAoACgAKAAoACg- list port-ds-list +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- key +ACI-port-number+ACIAOw-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKA- type uint16+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- container port-identity +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- leaf clock-identity +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- type clock-identity-=
type+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- config false+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- type leafref+AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- path +ACI-..=
/../port-number+ACIAOw-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- config false+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoACg- +AH0-
+AD4- +AD4-
+AD4- +AD4- This has disadvantages from the YANG perspective, in that=20
+AD4- +AD4- port-number is duplicated. The +ACI-config false+ACI- is intend=
ed to=20
+AD4- +AD4- mitigate YANG implementation challenges, such that only one val=
ue of=20
+AD4- +AD4- port-number is provided for configuration.
+AD4- +AD4-
+AD4- +AD4- Option 2: Use a grouping
+AD4- +AD4- ---
+AD4- +AD4-
+AD4- +AD4- YANG summary:
+AD4- +AD4-
+AD4- +AD4AoACgAKAAoACg- grouping port-identity-grouping +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoA- leaf clock-identity +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKA- type clock-identity-type+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoACgAKA- type uint16+ADs-
+AD4- +AD4AoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4AoACgAKAAoACg- +AH0-
+AD4- +AD4AoACgAKAAoACg- list port-ds-list +AHs-
+AD4- +AD4AoACgAKAAoACgAKAAoA- key +ACI-port-number+ACIAOw-
+AD4- +AD4AoACgAKAAoACgAKAAoA- uses port-identity-grouping+ADs-
+AD4- +AD4AoACgAKAAoACg- +AH0-
+AD4- +AD4-
+AD4- +AD4- This has disadvantages from the 1588 perspective, in that it is=
 not=20
+AD4- +AD4- possible for a 1588-aware management client to +ACI-get+ACI- po=
rtIdentity.=20
+AD4- +AD4- We are removing a 1588 +ACI-real thing+ACI- from the data model=
 in order to=20
+AD4- +AD4- accommodate a syntax limitation of YANG.
+AD4-=20
+AD4- I think that in general when you go from an information model to a=20
+AD4- concrete data model, you need to adapt to the data modelling language=
=20
+AD4- you are using, and this will in most cases mean that there will be=20
+AD4- some differences+ADs- in some cases the data model structure is diffe=
rent,=20
+AD4- and in some cases the data model will result in a more detailed model=
.+AKA-=20
+AD4- How keys are specified is one such example.+AKA- If you were to use S=
MIv2,=20
+AD4- you'd have to change the names (so that they are unique), and you'd=20
+AD4- have to map the structures to conceptual tables.
+AD4-=20
+AD4- Clients need to understand the data model in use (not just the=20
+AD4- information model behid it).
+AD4-=20
+AD4- +AD4- Question for NETMOD experts
+AD4- +AD4- ---
+AD4- +AD4-
+AD4- +AD4- My personal preference is Option 1 (leafref). Nevertheless, if =
the=20
+AD4- +AD4- +ACI-config false+ACI- does not provide sufficient mitigation f=
or today's=20
+AD4- +AD4- YANG implementations, we can go with Option 2.
+AD4-=20
+AD4- I don't think any implementation would have any problem supporting=20
+AD4- option 1, but it does look a bit odd.+AKA- Also, it only +ACI-helps+A=
CI- if the=20
+AD4- client is getting the data using +ADw-get+AD4-, but it will not help =
if it is=20
+AD4- using +ADw-get-
+AD4- config+AD4-.
+AD4-=20
+AD4-=20
+AD4- I think that the cleanest solution is to not try to completely mimic=
=20
+AD4- the structure from the information model, but make sure that the text=
=20
+AD4- in the description statements make it clear that the data model looks=
=20
+AD4- different compared to the information model, in order to help the rea=
ders.
+AD4-=20
+AD4-=20
+AD4-=20
+AD4- /martin
+AD4-=20
+AD4-=20
+AD4-=20
+AD4- +AD4-
+AD4- +AD4- Feedback is very much appreciated.
+AD4- +AD4-
+AD4- +AD4- Thanks folks,
+AD4- +AD4- Rodney Cummings
+AD4- +AD4- Co-author draft-ietf-tictoc-1588v2-yang-05
+AD4- +AD4-
+AD4- +AD4- +AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw=
BfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
+AD4- +AD4- netmod mailing list
+AD4- +AD4- mailto:netmod+AEA-ietf.org
+AD4- +AD4- https://urldefense.proofpoint.com/v2/url?u+AD0-https-3A+AF8AXw-=
www.ietf.org+AF8-ma
+AD4- +AD4- il=20
+AD4- +AD4- man+AF8-listinfo+AF8-netmod+ACY-d+AD0-DwMFAg+ACY-c+AD0-I+AF8-0Y=
woKy7z5LMTVdyO6YCiE2uzI1jjZZuIPel
+AD4- +AD4- cS
+AD4- +AD4- jixA+ACY-r+AD0-WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k+ACY-=
m+AD0-Tvq4PvUNekeS1IF
+AD4- +AD4- 42=20
+AD4- +AD4- ycx+AF8-7KyiF9Ag9bUucZE51SFvCw+ACY-s+AD0-BahOyOIDKpAWICQOgrlu0a=
ga7dBde8X07-oq2il
+AD4- +AD4- ON
+AD4- +AD4- kw+ACY-e+AD0-
+AD4- +AD4-
+AD4-=20
+AD4- References:
+AD4- . https://urldefense.proofpoint.com/v2/url?u+AD0-https-
+AD4- 3A+AF8AXw-mailarchive.ietf.org+AF8-arch+AF8-msg+AF8-tictoc+AF8-lm1xq3=
7jffkSMms2XJll3N-
+AD4- 2DydC0+ACY-d+AD0-DwMFAg+ACY-c+AD0-I+AF8-0YwoKy7z5LMTVdyO6YCiE2uzI1jjZ=
ZuIPelcSjixA+ACY-r+AD0-WA71sf
+AD4- 2o7D
+AD4- w7CbYhFt24DPjt3lJuupswWYdnboKbZ8k+ACY-m+AD0-Tvq4PvUNekeS1IF42ycx+AF8-=
7KyiF9Ag9bUuc
+AD4- ZE51 SFvCw+ACY-s+AD0-8SBqP6TRNUiieCBN4IZ6qzNQ5ZEW8pCBAm1kAULa-Mg+ACY-=
e+AD0-
+AD4- Rodney Cummings +ADw-mailto:rodney.cummings+AEA-ni.com+AD4-
+AD4-=20
+AD4- +AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8A=
XwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
+AD4- TICTOC mailing list
+AD4- TICTOC+AEA-ietf.org
+AD4- https://urldefense.proofpoint.com/v2/url?u+AD0-https-
+AD4- 3A+AF8AXw-www.ietf.org+AF8-mailman+AF8-listinfo+AF8-tictoc+ACY-d+AD0-=
DwIFgQ+ACY-c+AD0-I+AF8-0YwoKy7z5LMTVdyO
+AD4- 6YCi=20
+AD4- E2uzI1jjZZuIPelcSjixA+ACY-r+AD0-WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnb=
oKbZ8k+ACY-m+AD0-
+AD4- 3vIq
+AD4- KhIleK3ifzu2gqWugIUX62HPLM5VReDafflfyVY+ACY-s+AD0-jy6sTQ1a-
+AD4- mKqq1ymmNMj7g1kzyAcFvPE9emfALot4FE+ACY-e+AD0-


From nobody Tue Oct 10 07:03:37 2017
Return-Path: <rodney.cummings@ni.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 CDCF5132F2C for <tictoc@ietfa.amsl.com>; Tue, 10 Oct 2017 07:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nio365.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XUMXLOWTxgbg for <tictoc@ietfa.amsl.com>; Tue, 10 Oct 2017 07:03:32 -0700 (PDT)
Received: from mx0b-00010702.pphosted.com (mx0b-00010702.pphosted.com [148.163.158.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40E4C134DEC for <tictoc@ietf.org>; Tue, 10 Oct 2017 07:02:43 -0700 (PDT)
Received: from pps.filterd (m0098778.ppops.net [127.0.0.1]) by mx0b-00010702.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v9AE0SXX031809; Tue, 10 Oct 2017 09:02:33 -0500
Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp0080.outbound.protection.outlook.com [207.46.163.80]) by mx0b-00010702.pphosted.com with ESMTP id 2dgw9r9jxh-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 10 Oct 2017 09:02:31 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nio365.onmicrosoft.com; s=selector1-ni-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=5C/o6ZqEaqIYlHQQPFXnr9rM5Nmmd5twToELxNv+ymc=; b=V1b9cD4+sQPI3hbn0GN7eDI5gbcEUoOQh8mTW0Yim5iuYcBOEb+sxbTorZFzOUuxQyKU165J7qnXOAQO3sPvix7K7dakcVY7BhZGWZbjlkRgopm0wGtLOZS+iS9jK/3fuHmAq3R2xhzKWPQ2MROs7tGS+8fMnHU4E6r7nD56EMo=
Received: from CY1PR0401MB1536.namprd04.prod.outlook.com (10.163.19.154) by CY1PR0401MB1536.namprd04.prod.outlook.com (10.163.19.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.77.7; Tue, 10 Oct 2017 14:02:29 +0000
Received: from CY1PR0401MB1536.namprd04.prod.outlook.com ([10.163.19.154]) by CY1PR0401MB1536.namprd04.prod.outlook.com ([10.163.19.154]) with mapi id 15.20.0077.019; Tue, 10 Oct 2017 14:02:29 +0000
From: Rodney Cummings <rodney.cummings@ni.com>
To: Jiangyuanlong <jiangyuanlong@huawei.com>, Opher Ronen <ORonen@advaoptical.com>, "tictoc@ietf.org" <tictoc@ietf.org>
CC: Zongning <zongning@huawei.com>, "Liushucheng (Will Liu)" <liushucheng@huawei.com>, Zhuhengjun <zhuhengjun@huawei.com>
Thread-Topic: draft-ietf-tictoc-1588v2-yang-05: clock-identity
Thread-Index: AQHTQWrjzv+D2Kji5kqjvITjk/Q0hKLdHYIA
Date: Tue, 10 Oct 2017 14:02:29 +0000
Message-ID: <CY1PR0401MB1536DD2C90056B52578172E292750@CY1PR0401MB1536.namprd04.prod.outlook.com>
References: <61ee5a45c081476ea39332fd27561090@advaoptical.com> <DM2PR0401MB1389F715891EC85EB25E7E3592720@DM2PR0401MB1389.namprd04.prod.outlook.com> <bbdb4db2fcb84090b7cd705b810612a7@advaoptical.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5D03AD@dggeml507-mbx.china.huawei.com> <CY1PR0401MB1536370FBF361DCF5242D0A792740@CY1PR0401MB1536.namprd04.prod.outlook.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5D06E2@dggeml507-mbx.china.huawei.com>
In-Reply-To: <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5D06E2@dggeml507-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.164.62.43]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR0401MB1536; 6:CfA9oqznvsfb9af/LCZG3ojO/qGn6Db6MP04AhnPYSJb+WYEXWJ9mjCPF3WlGIsO5GpGLNqnT9G1dBScVBTp0iDuzZWFt8V0wRBZRaoe20v9PiC5nC891+6MP64xGsHv/jE/yFGBZV1aR8QyJzpbBswQWmc27MiR4KG4f50hpz9yJW706mp8h5phddwTf7mZfxx4whl2lzRZFYSZU4MM37XA5yDm8fjzjYtePHD3EuU/91YciCJ7K1B8b1iwfPbdsISasnnQ5Y0go0pn8HcxMOFq7cjGLzlnvR7YqQtui7tN8sr4Xqd9H59HARa4pUK7bEldXrS/JrzkUojS6F5rDA==; 5:10A0PInhu2/oLhV0chZ8IG5o/Grf/gCnjxAQBfCE/+s+nmcg7SmheC2HCJwy5S1BRvv1IJyoDJwCDdClXGlTUltYEswpTd9wek0Kv0DirAqN2zIjwzBOZ4VHJQVv7OfhgabFLQTEJGHcBN8UsAUPeZIF/53E17vFKv1qyGZv/04=; 24:Tfd9I19hyQoNFdKkHoE5JoZ0fJQoDVfX60+TFLg35rhl6DeqwPLt2KwBVEk2sK1FroYwb7uFjOul52SrzcZ3bYQBLw1x1zEQp0zPi216pjQ=; 7:OevKBm/OgGefDSlBHuQw0j7yvBJIjRzenPzeZGBu5rVZM5TDERJ2XKP3nUjM7PMK3dOonMLMKk8h04aGlcJlTjpUXedBMRKnZcO9o1NupRc18BblWueRRY2IjFQLzqMJy/ixyn9xJbLLpDGF3BMA6+c9sO1lj660nTxv/1wP3pqOqI0/6VDI4EF/pspeNuSFR1xilvJ/fO88sgqbzLOC/pWoqDKWWg1TtHFhfjuRl6I=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: f07eea55-daaa-4db4-73a4-08d50fe78b76
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254152)(2017052603199)(201703131423075)(201703031133081)(201702281549075); SRVR:CY1PR0401MB1536; 
x-ms-traffictypediagnostic: CY1PR0401MB1536:
x-exchange-antispam-report-test: UriScan:(10436049006162)(50582790962513)(100405760836317)(145744241990776)(17755550239193);
x-microsoft-antispam-prvs: <CY1PR0401MB15366EF1EEB4B472B518CADC92750@CY1PR0401MB1536.namprd04.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(100000703101)(100105400095)(6041248)(20161123560025)(20161123558100)(20161123562025)(20161123564025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY1PR0401MB1536; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY1PR0401MB1536; 
x-forefront-prvs: 04569283F9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(376002)(346002)(61484003)(51444003)(189002)(377454003)(199003)(13464003)(81166006)(50986999)(102836003)(81156014)(105586002)(106356001)(5660300001)(4326008)(77096006)(3846002)(6116002)(2900100001)(7696004)(229853002)(561944003)(6246003)(76176999)(966005)(575784001)(97736004)(110136005)(54906003)(14454004)(478600001)(93886005)(99286003)(54356999)(55016002)(6306002)(316002)(53546010)(33656002)(74316002)(7736002)(305945005)(68736007)(189998001)(8676002)(2950100002)(101416001)(25786009)(3660700001)(6436002)(6506006)(9686003)(66066001)(86362001)(8936002)(3280700002)(53936002)(230783001)(2906002)(2501003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0401MB1536; H:CY1PR0401MB1536.namprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: ni.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-7"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ni.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Oct 2017 14:02:29.3357 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 87ba1f9a-44cd-43a6-b008-6fdb45a5204e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0401MB1536
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-10_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=30 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=30 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710100200
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/OcTyIGdSuqVUN-AowV57fq_XJyM>
Subject: Re: [TICTOC] draft-ietf-tictoc-1588v2-yang-05: clock-identity
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 10 Oct 2017 14:03:36 -0000

My apologies Yuanlong,

I meant to use instance-list+AFsAXQ-/default-ds/clock-identity. According t=
o the 1588 standards, the value there is the same as the value in 1588's +A=
CI-portDS.portIdentity.clockIdentity+ACI-.

The value of clock-identity in other locations is different.

Rodney

+AD4- -----Original Message-----
+AD4- From: Jiangyuanlong +AFs-mailto:jiangyuanlong+AEA-huawei.com+AF0-
+AD4- Sent: Monday, October 9, 2017 8:55 PM
+AD4- To: Rodney Cummings +ADs- Opher Ronen +ADs- tictoc+AEA-ietf.org
+AD4- Cc: Zongning +ADs- Liushucheng (Will Liu) +ADs- Zhuhengjun
+AD4- Subject: draft-ietf-tictoc-1588v2-yang-05: clock-identity
+AD4-=20
+AD4- Dear Rodney,
+AD4-=20
+AD4- Thank a lot for the clarification.
+AD4- It is not clear to me how clock-identity is modeled indeed (I changed=
 the
+AD4- message title to reflect it).
+AD4- Currently, clock-identity is a member attribute in quite a few contai=
ners,
+AD4- such as default-ds, parent-ds. parent-port-identity, port-ds-list+AFs=
AXQ-. port-
+AD4- identity, transparent-clock-default-ds, and transparent-clock-port-ds=
-
+AD4- list+AFsAXQ-.port-identity, but instance-list+AFsAXQ- does not have c=
lock-identity as
+AD4- its member. Are you suggesting to move clock-identity from default-ds=
 into
+AD4- instance-list+AFsAXQ-?
+AD4- How do we model clock-identity in the transparent-clock-port-ds-list+=
AFsAXQ-,
+AD4- remove it too?
+AD4-=20
+AD4- Regards,
+AD4- Yuanlong
+AD4-=20
+AD4- -----Original Message-----
+AD4- From: Rodney Cummings +AFs-mailto:rodney.cummings+AEA-ni.com+AF0-
+AD4- Sent: Monday, October 09, 2017 11:39 PM
+AD4- To: Jiangyuanlong+ADs- Opher Ronen+ADs- tictoc+AEA-ietf.org
+AD4- Cc: Zongning+ADs- Liushucheng (Will Liu)+ADs- Zhuhengjun
+AD4- Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-=
1588v2-yang-05: port-
+AD4- number
+AD4-=20
+AD4- Hi Yuanlong,
+AD4-=20
+AD4- To be clear my proposal is:
+AD4- - Model port-number directly in port-list as the key.
+AD4- - Do not model clock-identity in port-list.
+AD4- - Do not model port-identity in port-list.
+AD4- - In the description of port-number, mention that port-identity is no=
t
+AD4- explicitly modeled in YANG, but implicitly through the use of port-
+AD4- list+AFsAXQ-/port-number and instance-list+AFsAXQ-/clock-identity. Se=
e my previous
+AD4- email for proposed text.
+AD4-=20
+AD4- Rodney
+AD4-=20
+AD4- +AD4- -----Original Message-----
+AD4- +AD4- From: Jiangyuanlong +AFs-mailto:jiangyuanlong+AEA-huawei.com+AF=
0-
+AD4- +AD4- Sent: Monday, October 9, 2017 6:47 AM
+AD4- +AD4- To: Opher Ronen +ADs- Rodney Cummings +ADs- tictoc+AEA-ietf.org
+AD4- +AD4- Cc: Zongning +ADs- Liushucheng (Will Liu) +ADs- Zhuhengjun
+AD4- +AD4- Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-t=
ictoc-1588v2-yang-05:
+AD4- +AD4- port- number
+AD4- +AD4-
+AD4- +AD4- Hi Opher and all,
+AD4- +AD4-
+AD4- +AD4- Thanks much for all the comments. So the consensus seems to me =
is - we
+AD4- +AD4- agreed to model both port-number and clock-identity in the port=
-ds-list.
+AD4- +AD4- This will reflected in our next revision of draft-ietf-tictoc-1=
588v2-
+AD4- yang.
+AD4- +AD4- Definitely, later versions can take another approach with versi=
on
+AD4- +AD4- control capability of YANG.
+AD4- +AD4-
+AD4- +AD4- Cheers,
+AD4- +AD4- Yuanlong
+AD4- +AD4-
+AD4- +AD4- -----Original Message-----
+AD4- +AD4- From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Be=
half Of Opher Ronen
+AD4- +AD4- Sent: Wednesday, October 04, 2017 2:40 AM
+AD4- +AD4- To: Rodney Cummings+ADs- tictoc+AEA-ietf.org
+AD4- +AD4- Subject: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-ticto=
c-1588v2-yang-05: port-
+AD4- +AD4- number
+AD4- +AD4-
+AD4- +AD4- Thanks Rodney,
+AD4- +AD4-
+AD4- +AD4-  If I understand your latest suggestion correctly it appears a =
good
+AD4- +AD4- choice for this initial yang model, taking a +ACI-less-is-more+=
ACI- approach.
+AD4- +AD4-
+AD4- +AD4- Someone interested in knowing e.g. all portId's currently confi=
gured
+AD4- +AD4- can append the port-number values from the port-ds-list to the =
clockID
+AD4- +AD4- from the instance level.
+AD4- +AD4-
+AD4- +AD4- I assume if more structured to +ACI-get+ACI- portID is deemed a=
n important
+AD4- +AD4- feature it can be added in a later version of the data-model.
+AD4- +AD4-
+AD4- +AD4- Opher
+AD4- +AD4-
+AD4- +AD4- -----Original Message-----
+AD4- +AD4- From: Rodney Cummings +AFs-mailto:rodney.cummings+AEA-ni.com+AF=
0-
+AD4- +AD4- Sent: Tuesday, October 3, 2017 9:28 PM
+AD4- +AD4- To: Opher Ronen +ADw-ORonen+AEA-advaoptical.com+AD4AOw- tictoc+=
AEA-ietf.org
+AD4- +AD4- Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-t=
ictoc-1588v2-yang-05:
+AD4- +AD4- port- number
+AD4- +AD4-
+AD4- +AD4- As the kids say... +ACI-lol+ACI-.
+AD4- +AD4-
+AD4- +AD4- Our emails crossed paths.
+AD4- +AD4-
+AD4- +AD4- The proposal I just sent reflects Opher's view (I hope), as wel=
l as
+AD4- +AD4- others.
+AD4- +AD4-
+AD4- +AD4- Opher: My latest proposal removes the duplicate clockIdentity e=
ntirely.
+AD4- +AD4-
+AD4- +AD4- From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Be=
half Of Opher Ronen
+AD4- +AD4- Sent: Tuesday, October 3, 2017 12:57 PM
+AD4- +AD4- To: tictoc+AEA-ietf.org
+AD4- +AD4- Subject: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-ticto=
c-1588v2-yang-05: port-
+AD4- +AD4- number
+AD4- +AD4-
+AD4- +AD4- Hi Rodney +ACY- all,
+AD4- +AD4- +AKAAoA- I am somewhat belatedly posting a post to this thread =
following an
+AD4- +AD4- offline correspondence with Rodney in context of this subject. =
I hope
+AD4- +AD4- my feedback is not too late to be constructive, and will be pos=
ted
+AD4- +AD4- correctly as this is my first post to this thread.
+AD4- +AD4- +AKAAoA- I will also apologize in advance that I will be mostly=
 offline till
+AD4- +AD4- mid-October, so will likely be able to reply to responses only =
then.
+AD4- +AD4- +AKAAoA- Rodney shared with me the consideration on this aspect=
, and I
+AD4- +AD4- believe his recent post attempt to integrate my offline on this=
 topic.
+AD4- +AD4- +AKAAoA- I hope some more detailed feedback will hopefully assi=
st this draft
+AD4- +AD4- advance in a manner aligned with my perception on this aspect f=
rom my
+AD4- +AD4- involvement in the P1588 WG in general and it's Management SC i=
n
+AD4- specific.
+AD4- +AD4- +AKAAoA- I will first comment that following my correspondence =
with Rodney
+AD4- +AD4- that I believe (with reservation given my low involvement in di=
rect
+AD4- +AD4- implementation of management interfaces) that an interface that=
 would
+AD4- +AD4- enable performing a get to obtain an overall structure includin=
g the
+AD4- +AD4- information comprimsing a PTP portIdentity appears nice to have=
. I
+AD4- +AD4- would assume that this information will not be the most frequen=
t
+AD4- +AD4- aspect a management system would query, but easing obtaining it=
 if
+AD4- +AD4- overhead is reasonable may be worthwhile.
+AD4- +AD4- +AKAAoA- A possibly more significant comment is to stress that =
the
+AD4- +AD4- clockIdentity portion of the portIdentity attribute is equal in=
 all
+AD4- +AD4- port within a PTP Instance, and equal to the clockIdentity attr=
ibute
+AD4- +AD4- with the clock data set. This is explicitly stressed by a new s=
entence
+AD4- +AD4- added to the next revision draft, intended to clarify this to t=
he
+AD4- +AD4- reader: +ACI-The clockIdentity portion of a portIdentity is equ=
al to the
+AD4- +AD4- clockIdentity of the PTP Instance that the PTP Port is included=
 in,
+AD4- +AD4- and is therefore equal among all PTP Ports inside the PTP Insta=
nce.+ACI-
+AD4- +AD4- +AKAAoA-In my view regardless of the option followed for the da=
ta model for
+AD4- +AD4- portIdentity, the ability to directly configure the clockIdenti=
ty
+AD4- +AD4- portion of it should be prevented to avoid generating a configu=
ration
+AD4- +AD4- violating the above status (possible hampering the operation of=
 the
+AD4- +AD4- PTP protocol if later used as data for portIdentity on the wire=
).
+AD4- +AD4- +AKAAoACg-If I understood correct yang data model enable to pro=
vide a leafref
+AD4- +AD4- pointer to the clockIdentity from the instance data set level,
+AD4- +AD4- possibly best reflecting the actual limitations regarding the
+AD4- +AD4- portIdentity structure.
+AD4- +AD4-
+AD4- +AD4- Best Regards,
+AD4- +AD4- +AKAAoACg- Opher Ronen
+AD4- +AD4-
+AD4- +AD4- Rodney Cummings +ADw-mailto:rodney.cummings+AEA-ni.com+ACY-gt+A=
Ds- wrote:
+AD4- +AD4- +AD4- Hi folks,
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- One of the last topics that we need to resolve for WG Las=
t Call of
+AD4- +AD4- +AD4- draft-ietf-tictoc-1588v2-yang-05 is the representation of
+AD4- +AD4- +AD4- port-number, which serves as the key to the list of 1588 =
port data
+AD4- sets (i.e.
+AD4- +AD4- +AD4- port-list). I've had some offline discussion with IEEE 15=
88 WG
+AD4- +AD4- +AD4- members, and I'm copying NETMOD members for YANG expertis=
e.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- I think we can narrow the possible options to two, so I'm=
 starting a
+AD4- +AD4- +AD4- new thread to focus on those.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- IEEE Std 1588-2008 is the time sync standard that specifi=
es the
+AD4- +AD4- +AD4-information model on which draft-ietf-tictoc-1588v2-yang-0=
5 is  based.
+AD4- +AD4- +AD4-In IEEE Std 1588-2008, subclause 5.3.5 specifies the follo=
wing  data
+AD4- +AD4- +AD4-type to identify each logical port in the 1588 product:
+AD4- +AD4- +AD4AoACgAKA- struct PortIdentity +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKA- ClockIdentity clockIdentity+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKA- Uinteger16 portNumber+ADs-
+AD4- +AD4- +AD4AoACgAKA- +AH0AOw-
+AD4- +AD4- +AD4- IEEE Std 1588-2008 uses this data type as the +ACI-portId=
entity+ACI- of the
+AD4- +AD4- +AD4-port in its on-the-wire protocol, state machines, and so o=
n. In other
+AD4- +AD4- +AD4-words, in the 1588 standard itself, portIdentity is a +ACI=
-real thing+ACI-
+AD4- +AD4- +AD4- with real implementation.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- IEEE Std 1588-2008 also specifies a list of logical ports=
 in each
+AD4- +AD4- +AD4- +ACI-clock+ACI-, and portIdentity.portNumber is used as t=
he key to that list
+AD4- +AD4- +AD4- of ports.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- In the YANG of draft-ietf-tictoc-1588v2-yang-05, we use Y=
ANG-style
+AD4- +AD4- +AD4- names (e.g. port-list, port-number), but otherwise we've =
tried to
+AD4- +AD4- +AD4- keep consistent to the IEEE Std 1588-2008 information mod=
el.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- We have a challenge with port-number. If YANG represents
+AD4- +AD4- +AD4- port-identity as a container within port-list, YANG does =
not allow a
+AD4- +AD4- +AD4- key to be a leaf within a container, so we cannot use
+AD4- +AD4- +AD4- port-identity/port-number as the key to port-list.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- It seems that we have two options:
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- Option 1: Use a leafref
+AD4- +AD4- +AD4- ---
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- YANG summary:
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACg- list port-ds-list +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- key +ACI-port-number+ACIAOw-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKA- type uint16+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- container port-identity +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- leaf clock-identity +A=
Hs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- type clock-ide=
ntity-type+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- config false+A=
Ds-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- type leafref+A=
Hs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- path +=
ACI-../../port-number+ACIAOw-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- config false+A=
Ds-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACg- +AH0-
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- This has disadvantages from the YANG perspective, in that
+AD4- +AD4- +AD4- port-number is duplicated. The +ACI-config false+ACI- is =
intended to
+AD4- +AD4- +AD4- mitigate YANG implementation challenges, such that only o=
ne value of
+AD4- +AD4- +AD4- port-number is provided for configuration.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- Option 2: Use a grouping
+AD4- +AD4- +AD4- ---
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- YANG summary:
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4AoACgAKAAoACg- grouping port-identity-grouping +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- leaf clock-identity +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKA- type clock-identity-type+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKA- type uint16+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACg- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACg- list port-ds-list +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- key +ACI-port-number+ACIAOw-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- uses port-identity-grouping+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACg- +AH0-
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- This has disadvantages from the 1588 perspective, in that=
 it is not
+AD4- +AD4- +AD4- possible for a 1588-aware management client to +ACI-get+A=
CI- portIdentity.
+AD4- +AD4- +AD4- We are removing a 1588 +ACI-real thing+ACI- from the data=
 model in order to
+AD4- +AD4- +AD4- accommodate a syntax limitation of YANG.
+AD4- +AD4-
+AD4- +AD4- I think that in general when you go from an information model t=
o a
+AD4- +AD4- concrete data model, you need to adapt to the data modelling la=
nguage
+AD4- +AD4- you are using, and this will in most cases mean that there will=
 be
+AD4- +AD4- some differences+ADs- in some cases the data model structure is=
 different,
+AD4- +AD4- and in some cases the data model will result in a more detailed=
 model.
+AD4- +AD4- How keys are specified is one such example.+AKA- If you were to=
 use SMIv2,
+AD4- +AD4- you'd have to change the names (so that they are unique), and y=
ou'd
+AD4- +AD4- have to map the structures to conceptual tables.
+AD4- +AD4-
+AD4- +AD4- Clients need to understand the data model in use (not just the
+AD4- +AD4- information model behid it).
+AD4- +AD4-
+AD4- +AD4- +AD4- Question for NETMOD experts
+AD4- +AD4- +AD4- ---
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- My personal preference is Option 1 (leafref). Nevertheles=
s, if the
+AD4- +AD4- +AD4- +ACI-config false+ACI- does not provide sufficient mitiga=
tion for today's
+AD4- +AD4- +AD4- YANG implementations, we can go with Option 2.
+AD4- +AD4-
+AD4- +AD4- I don't think any implementation would have any problem support=
ing
+AD4- +AD4- option 1, but it does look a bit odd.+AKA- Also, it only +ACI-h=
elps+ACI- if the
+AD4- +AD4- client is getting the data using +ADw-get+AD4-, but it will not=
 help if it is
+AD4- +AD4- using +ADw-get-
+AD4- +AD4- config+AD4-.
+AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4- I think that the cleanest solution is to not try to completely =
mimic
+AD4- +AD4- the structure from the information model, but make sure that th=
e text
+AD4- +AD4- in the description statements make it clear that the data model=
 looks
+AD4- +AD4- different compared to the information model, in order to help t=
he
+AD4- readers.
+AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4- /martin
+AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- Feedback is very much appreciated.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- Thanks folks,
+AD4- +AD4- +AD4- Rodney Cummings
+AD4- +AD4- +AD4- Co-author draft-ietf-tictoc-1588v2-yang-05
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- +AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBf=
AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
+AD4- +AD4- +AD4- netmod mailing list
+AD4- +AD4- +AD4- mailto:netmod+AEA-ietf.org
+AD4- +AD4- +AD4- https://urldefense.proofpoint.com/v2/url?u+AD0-https-3A+A=
F8AXw-www.ietf.org+AF8-ma
+AD4- +AD4- +AD4- il
+AD4- +AD4- +AD4- man+AF8-listinfo+AF8-netmod+ACY-d+AD0-DwMFAg+ACY-c+AD0-I+=
AF8-0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPel
+AD4- +AD4- +AD4- cS
+AD4- +AD4- +AD4- jixA+ACY-r+AD0-WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8=
k+ACY-m+AD0-Tvq4PvUNekeS1IF
+AD4- +AD4- +AD4- 42
+AD4- +AD4- +AD4- ycx+AF8-7KyiF9Ag9bUucZE51SFvCw+ACY-s+AD0-BahOyOIDKpAWICQO=
grlu0aga7dBde8X07-oq2il
+AD4- +AD4- +AD4- ON
+AD4- +AD4- +AD4- kw+ACY-e+AD0-
+AD4- +AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4- References:
+AD4- +AD4- . https://urldefense.proofpoint.com/v2/url?u+AD0-https-
+AD4- +AD4- 3A+AF8AXw-mailarchive.ietf.org+AF8-arch+AF8-msg+AF8-tictoc+AF8-=
lm1xq37jffkSMms2XJll3N-
+AD4- +AD4- 2DydC0+ACY-d+AD0-DwMFAg+ACY-c+AD0-I+AF8-0YwoKy7z5LMTVdyO6YCiE2u=
zI1jjZZuIPelcSjixA+ACY-r+AD0-WA71sf
+AD4- +AD4- 2o7D
+AD4- +AD4- w7CbYhFt24DPjt3lJuupswWYdnboKbZ8k+ACY-m+AD0-Tvq4PvUNekeS1IF42yc=
x+AF8-7KyiF9Ag9bUuc
+AD4- +AD4- ZE51 SFvCw+ACY-s+AD0-8SBqP6TRNUiieCBN4IZ6qzNQ5ZEW8pCBAm1kAULa-M=
g+ACY-e+AD0-
+AD4- +AD4- Rodney Cummings +ADw-mailto:rodney.cummings+AEA-ni.com+AD4-
+AD4- +AD4-
+AD4- +AD4- +AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw=
BfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
+AD4- +AD4- TICTOC mailing list
+AD4- +AD4- TICTOC+AEA-ietf.org
+AD4- +AD4- https://urldefense.proofpoint.com/v2/url?u+AD0-https-
+AD4- +AD4- 3A+AF8AXw-www.ietf.org+AF8-mailman+AF8-listinfo+AF8-tictoc+ACY-=
d+AD0-DwIFgQ+ACY-c+AD0-I+AF8-0YwoKy7z5LMTVdyO
+AD4- +AD4- 6YCi
+AD4- +AD4- E2uzI1jjZZuIPelcSjixA+ACY-r+AD0-WA71sf2o7Dw7CbYhFt24DPjt3lJuups=
wWYdnboKbZ8k+ACY-m+AD0-
+AD4- +AD4- 3vIq
+AD4- +AD4- KhIleK3ifzu2gqWugIUX62HPLM5VReDafflfyVY+ACY-s+AD0-jy6sTQ1a-
+AD4- +AD4- mKqq1ymmNMj7g1kzyAcFvPE9emfALot4FE+ACY-e+AD0-


From nobody Wed Oct 11 01:44:51 2017
Return-Path: <jiangyuanlong@huawei.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 D494A132C3F for <tictoc@ietfa.amsl.com>; Wed, 11 Oct 2017 01:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id USZFiP-_WhJK for <tictoc@ietfa.amsl.com>; Wed, 11 Oct 2017 01:44:47 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5439C1321C7 for <tictoc@ietf.org>; Wed, 11 Oct 2017 01:44:46 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DXI35422; Wed, 11 Oct 2017 08:44:16 +0000 (GMT)
Received: from DGGEML403-HUB.china.huawei.com (10.3.17.33) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 11 Oct 2017 09:44:14 +0100
Received: from DGGEML507-MBX.china.huawei.com ([169.254.2.79]) by DGGEML403-HUB.china.huawei.com ([fe80::74d9:c659:fbec:21fa%31]) with mapi id 14.03.0301.000; Wed, 11 Oct 2017 16:44:02 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: Rodney Cummings <rodney.cummings@ni.com>, Opher Ronen <ORonen@advaoptical.com>, "tictoc@ietf.org" <tictoc@ietf.org>
CC: Zongning <zongning@huawei.com>, "Liushucheng (Will Liu)" <liushucheng@huawei.com>, Zhuhengjun <zhuhengjun@huawei.com>
Thread-Topic: draft-ietf-tictoc-1588v2-yang-05: clock-identity
Thread-Index: AQHTQWrVPOrClJwZhkyYqnRCyN3fmaLcl9+AgAG+wIA=
Date: Wed, 11 Oct 2017 08:44:02 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5D122C@dggeml507-mbx.china.huawei.com>
References: <61ee5a45c081476ea39332fd27561090@advaoptical.com> <DM2PR0401MB1389F715891EC85EB25E7E3592720@DM2PR0401MB1389.namprd04.prod.outlook.com> <bbdb4db2fcb84090b7cd705b810612a7@advaoptical.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5D03AD@dggeml507-mbx.china.huawei.com> <CY1PR0401MB1536370FBF361DCF5242D0A792740@CY1PR0401MB1536.namprd04.prod.outlook.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBB5D06E2@dggeml507-mbx.china.huawei.com> <CY1PR0401MB1536DD2C90056B52578172E292750@CY1PR0401MB1536.namprd04.prod.outlook.com>
In-Reply-To: <CY1PR0401MB1536DD2C90056B52578172E292750@CY1PR0401MB1536.namprd04.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.74.202.215]
Content-Type: text/plain; charset="utf-7"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.59DDD9F7.00A5, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.2.79, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: e057ab5650c453e78afc2d0bf0f4e71e
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/v1rQoFKZyFZ82-g_E5Yqe0wk7sw>
Subject: Re: [TICTOC] draft-ietf-tictoc-1588v2-yang-05: clock-identity
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Oct 2017 08:44:50 -0000

Rodney,

Thanks much, I got it now+ADs-)

Cheers,
Yuanlong

-----Original Message-----
From: Rodney Cummings +AFs-mailto:rodney.cummings+AEA-ni.com+AF0-=20
Sent: Tuesday, October 10, 2017 10:02 PM
To: Jiangyuanlong+ADs- Opher Ronen+ADs- tictoc+AEA-ietf.org
Cc: Zongning+ADs- Liushucheng (Will Liu)+ADs- Zhuhengjun
Subject: RE: draft-ietf-tictoc-1588v2-yang-05: clock-identity

My apologies Yuanlong,

I meant to use instance-list+AFsAXQ-/default-ds/clock-identity. According t=
o the 1588 standards, the value there is the same as the value in 1588's +A=
CI-portDS.portIdentity.clockIdentity+ACI-.

The value of clock-identity in other locations is different.

Rodney

+AD4- -----Original Message-----
+AD4- From: Jiangyuanlong +AFs-mailto:jiangyuanlong+AEA-huawei.com+AF0-
+AD4- Sent: Monday, October 9, 2017 8:55 PM
+AD4- To: Rodney Cummings +ADs- Opher Ronen +ADs- tictoc+AEA-ietf.org
+AD4- Cc: Zongning +ADs- Liushucheng (Will Liu) +ADs- Zhuhengjun
+AD4- Subject: draft-ietf-tictoc-1588v2-yang-05: clock-identity
+AD4-=20
+AD4- Dear Rodney,
+AD4-=20
+AD4- Thank a lot for the clarification.
+AD4- It is not clear to me how clock-identity is modeled indeed (I changed=
=20
+AD4- the message title to reflect it).
+AD4- Currently, clock-identity is a member attribute in quite a few=20
+AD4- containers, such as default-ds, parent-ds. parent-port-identity,=20
+AD4- port-ds-list+AFsAXQ-. port- identity, transparent-clock-default-ds, a=
nd=20
+AD4- transparent-clock-port-ds- list+AFsAXQ-.port-identity, but instance-l=
ist+AFsAXQ-=20
+AD4- does not have clock-identity as its member. Are you suggesting to mov=
e=20
+AD4- clock-identity from default-ds into instance-list+AFsAXQ-?
+AD4- How do we model clock-identity in the=20
+AD4- transparent-clock-port-ds-list+AFsAXQ-, remove it too?
+AD4-=20
+AD4- Regards,
+AD4- Yuanlong
+AD4-=20
+AD4- -----Original Message-----
+AD4- From: Rodney Cummings +AFs-mailto:rodney.cummings+AEA-ni.com+AF0-
+AD4- Sent: Monday, October 09, 2017 11:39 PM
+AD4- To: Jiangyuanlong+ADs- Opher Ronen+ADs- tictoc+AEA-ietf.org
+AD4- Cc: Zongning+ADs- Liushucheng (Will Liu)+ADs- Zhuhengjun
+AD4- Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-tictoc-=
1588v2-yang-05:=20
+AD4- port- number
+AD4-=20
+AD4- Hi Yuanlong,
+AD4-=20
+AD4- To be clear my proposal is:
+AD4- - Model port-number directly in port-list as the key.
+AD4- - Do not model clock-identity in port-list.
+AD4- - Do not model port-identity in port-list.
+AD4- - In the description of port-number, mention that port-identity is no=
t=20
+AD4- explicitly modeled in YANG, but implicitly through the use of port-=20
+AD4- list+AFsAXQ-/port-number and instance-list+AFsAXQ-/clock-identity. Se=
e my previous=20
+AD4- email for proposed text.
+AD4-=20
+AD4- Rodney
+AD4-=20
+AD4- +AD4- -----Original Message-----
+AD4- +AD4- From: Jiangyuanlong +AFs-mailto:jiangyuanlong+AEA-huawei.com+AF=
0-
+AD4- +AD4- Sent: Monday, October 9, 2017 6:47 AM
+AD4- +AD4- To: Opher Ronen +ADs- Rodney Cummings +ADs- tictoc+AEA-ietf.org
+AD4- +AD4- Cc: Zongning +ADs- Liushucheng (Will Liu) +ADs- Zhuhengjun
+AD4- +AD4- Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-t=
ictoc-1588v2-yang-05:
+AD4- +AD4- port- number
+AD4- +AD4-
+AD4- +AD4- Hi Opher and all,
+AD4- +AD4-
+AD4- +AD4- Thanks much for all the comments. So the consensus seems to me =
is -=20
+AD4- +AD4- we agreed to model both port-number and clock-identity in the p=
ort-ds-list.
+AD4- +AD4- This will reflected in our next revision of=20
+AD4- +AD4- draft-ietf-tictoc-1588v2-
+AD4- yang.
+AD4- +AD4- Definitely, later versions can take another approach with versi=
on=20
+AD4- +AD4- control capability of YANG.
+AD4- +AD4-
+AD4- +AD4- Cheers,
+AD4- +AD4- Yuanlong
+AD4- +AD4-
+AD4- +AD4- -----Original Message-----
+AD4- +AD4- From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Be=
half Of Opher=20
+AD4- +AD4- Ronen
+AD4- +AD4- Sent: Wednesday, October 04, 2017 2:40 AM
+AD4- +AD4- To: Rodney Cummings+ADs- tictoc+AEA-ietf.org
+AD4- +AD4- Subject: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-ticto=
c-1588v2-yang-05:=20
+AD4- +AD4- port- number
+AD4- +AD4-
+AD4- +AD4- Thanks Rodney,
+AD4- +AD4-
+AD4- +AD4-  If I understand your latest suggestion correctly it appears a =
good=20
+AD4- +AD4- choice for this initial yang model, taking a +ACI-less-is-more+=
ACI- approach.
+AD4- +AD4-
+AD4- +AD4- Someone interested in knowing e.g. all portId's currently confi=
gured=20
+AD4- +AD4- can append the port-number values from the port-ds-list to the=
=20
+AD4- +AD4- clockID from the instance level.
+AD4- +AD4-
+AD4- +AD4- I assume if more structured to +ACI-get+ACI- portID is deemed a=
n important=20
+AD4- +AD4- feature it can be added in a later version of the data-model.
+AD4- +AD4-
+AD4- +AD4- Opher
+AD4- +AD4-
+AD4- +AD4- -----Original Message-----
+AD4- +AD4- From: Rodney Cummings +AFs-mailto:rodney.cummings+AEA-ni.com+AF=
0-
+AD4- +AD4- Sent: Tuesday, October 3, 2017 9:28 PM
+AD4- +AD4- To: Opher Ronen +ADw-ORonen+AEA-advaoptical.com+AD4AOw- tictoc+=
AEA-ietf.org
+AD4- +AD4- Subject: RE: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-t=
ictoc-1588v2-yang-05:
+AD4- +AD4- port- number
+AD4- +AD4-
+AD4- +AD4- As the kids say... +ACI-lol+ACI-.
+AD4- +AD4-
+AD4- +AD4- Our emails crossed paths.
+AD4- +AD4-
+AD4- +AD4- The proposal I just sent reflects Opher's view (I hope), as wel=
l as=20
+AD4- +AD4- others.
+AD4- +AD4-
+AD4- +AD4- Opher: My latest proposal removes the duplicate clockIdentity e=
ntirely.
+AD4- +AD4-
+AD4- +AD4- From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Be=
half Of Opher=20
+AD4- +AD4- Ronen
+AD4- +AD4- Sent: Tuesday, October 3, 2017 12:57 PM
+AD4- +AD4- To: tictoc+AEA-ietf.org
+AD4- +AD4- Subject: Re: +AFs-TICTOC+AF0- +AFs-netmod+AF0- draft-ietf-ticto=
c-1588v2-yang-05:=20
+AD4- +AD4- port- number
+AD4- +AD4-
+AD4- +AD4- Hi Rodney +ACY- all,
+AD4- +AD4- +AKAAoA- I am somewhat belatedly posting a post to this thread =
following=20
+AD4- +AD4- an offline correspondence with Rodney in context of this subjec=
t. I=20
+AD4- +AD4- hope my feedback is not too late to be constructive, and will b=
e=20
+AD4- +AD4- posted correctly as this is my first post to this thread.
+AD4- +AD4- +AKAAoA- I will also apologize in advance that I will be mostly=
 offline=20
+AD4- +AD4- till mid-October, so will likely be able to reply to responses =
only then.
+AD4- +AD4- +AKAAoA- Rodney shared with me the consideration on this aspect=
, and I=20
+AD4- +AD4- believe his recent post attempt to integrate my offline on this=
 topic.
+AD4- +AD4- +AKAAoA- I hope some more detailed feedback will hopefully assi=
st this=20
+AD4- +AD4- draft advance in a manner aligned with my perception on this as=
pect=20
+AD4- +AD4- from my involvement in the P1588 WG in general and it's Managem=
ent=20
+AD4- +AD4- SC in
+AD4- specific.
+AD4- +AD4- +AKAAoA- I will first comment that following my correspondence =
with Rodney=20
+AD4- +AD4- that I believe (with reservation given my low involvement in di=
rect=20
+AD4- +AD4- implementation of management interfaces) that an interface that=
=20
+AD4- +AD4- would enable performing a get to obtain an overall structure=20
+AD4- +AD4- including the information comprimsing a PTP portIdentity appear=
s=20
+AD4- +AD4- nice to have. I would assume that this information will not be =
the=20
+AD4- +AD4- most frequent aspect a management system would query, but easin=
g=20
+AD4- +AD4- obtaining it if overhead is reasonable may be worthwhile.
+AD4- +AD4- +AKAAoA- A possibly more significant comment is to stress that =
the=20
+AD4- +AD4- clockIdentity portion of the portIdentity attribute is equal in=
 all=20
+AD4- +AD4- port within a PTP Instance, and equal to the clockIdentity attr=
ibute=20
+AD4- +AD4- with the clock data set. This is explicitly stressed by a new=20
+AD4- +AD4- sentence added to the next revision draft, intended to clarify =
this=20
+AD4- +AD4- to the
+AD4- +AD4- reader: +ACI-The clockIdentity portion of a portIdentity is equ=
al to the=20
+AD4- +AD4- clockIdentity of the PTP Instance that the PTP Port is included=
 in,=20
+AD4- +AD4- and is therefore equal among all PTP Ports inside the PTP Insta=
nce.+ACI-
+AD4- +AD4- +AKAAoA-In my view regardless of the option followed for the da=
ta model=20
+AD4- +AD4- for portIdentity, the ability to directly configure the=20
+AD4- +AD4- clockIdentity portion of it should be prevented to avoid genera=
ting=20
+AD4- +AD4- a configuration violating the above status (possible hampering =
the=20
+AD4- +AD4- operation of the PTP protocol if later used as data for portIde=
ntity on the wire).
+AD4- +AD4- +AKAAoACg-If I understood correct yang data model enable to pro=
vide a=20
+AD4- +AD4- leafref pointer to the clockIdentity from the instance data set=
=20
+AD4- +AD4- level, possibly best reflecting the actual limitations regardin=
g the=20
+AD4- +AD4- portIdentity structure.
+AD4- +AD4-
+AD4- +AD4- Best Regards,
+AD4- +AD4- +AKAAoACg- Opher Ronen
+AD4- +AD4-
+AD4- +AD4- Rodney Cummings +ADw-mailto:rodney.cummings+AEA-ni.com+ACY-gt+A=
Ds- wrote:
+AD4- +AD4- +AD4- Hi folks,
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- One of the last topics that we need to resolve for WG Las=
t Call of
+AD4- +AD4- +AD4- draft-ietf-tictoc-1588v2-yang-05 is the representation of=
=20
+AD4- +AD4- +AD4- port-number, which serves as the key to the list of 1588 =
port data
+AD4- sets (i.e.
+AD4- +AD4- +AD4- port-list). I've had some offline discussion with IEEE 15=
88 WG=20
+AD4- +AD4- +AD4- members, and I'm copying NETMOD members for YANG expertis=
e.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- I think we can narrow the possible options to two, so I'm=
 starting=20
+AD4- +AD4- +AD4- a new thread to focus on those.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- IEEE Std 1588-2008 is the time sync standard that specifi=
es the=20
+AD4- +AD4- +AD4-information model on which draft-ietf-tictoc-1588v2-yang-0=
5 is  based.
+AD4- +AD4- +AD4-In IEEE Std 1588-2008, subclause 5.3.5 specifies the follo=
wing =20
+AD4- +AD4- +AD4-data type to identify each logical port in the 1588 produc=
t:
+AD4- +AD4- +AD4AoACgAKA- struct PortIdentity +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKA- ClockIdentity clockIdentity+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKA- Uinteger16 portNumber+ADs-
+AD4- +AD4- +AD4AoACgAKA- +AH0AOw-
+AD4- +AD4- +AD4- IEEE Std 1588-2008 uses this data type as the +ACI-portId=
entity+ACI- of=20
+AD4- +AD4- +AD4-the port in its on-the-wire protocol, state machines, and =
so on. In=20
+AD4- +AD4- +AD4-other words, in the 1588 standard itself, portIdentity is =
a +ACI-real thing+ACI-
+AD4- +AD4- +AD4- with real implementation.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- IEEE Std 1588-2008 also specifies a list of logical ports=
 in each=20
+AD4- +AD4- +AD4- +ACI-clock+ACI-, and portIdentity.portNumber is used as t=
he key to that=20
+AD4- +AD4- +AD4- list of ports.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- In the YANG of draft-ietf-tictoc-1588v2-yang-05, we use Y=
ANG-style=20
+AD4- +AD4- +AD4- names (e.g. port-list, port-number), but otherwise we've =
tried to=20
+AD4- +AD4- +AD4- keep consistent to the IEEE Std 1588-2008 information mod=
el.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- We have a challenge with port-number. If YANG represents=
=20
+AD4- +AD4- +AD4- port-identity as a container within port-list, YANG does =
not allow=20
+AD4- +AD4- +AD4- a key to be a leaf within a container, so we cannot use=20
+AD4- +AD4- +AD4- port-identity/port-number as the key to port-list.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- It seems that we have two options:
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- Option 1: Use a leafref
+AD4- +AD4- +AD4- ---
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- YANG summary:
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACg- list port-ds-list +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- key +ACI-port-number+ACIAOw-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKA- type uint16+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- container port-identity +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- leaf clock-identity +A=
Hs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- type clock-ide=
ntity-type+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- config false+A=
Ds-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- type leafref+A=
Hs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- path +=
ACI-../../port-number+ACIAOw-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- config false+A=
Ds-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACg- +AH0-
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- This has disadvantages from the YANG perspective, in that=
=20
+AD4- +AD4- +AD4- port-number is duplicated. The +ACI-config false+ACI- is =
intended to=20
+AD4- +AD4- +AD4- mitigate YANG implementation challenges, such that only o=
ne value=20
+AD4- +AD4- +AD4- of port-number is provided for configuration.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- Option 2: Use a grouping
+AD4- +AD4- +AD4- ---
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- YANG summary:
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4AoACgAKAAoACg- grouping port-identity-grouping +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- leaf clock-identity +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKA- type clock-identity-type+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- leaf port-number +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoACgAKA- type uint16+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACg- +AH0-
+AD4- +AD4- +AD4AoACgAKAAoACg- list port-ds-list +AHs-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- key +ACI-port-number+ACIAOw-
+AD4- +AD4- +AD4AoACgAKAAoACgAKAAoA- uses port-identity-grouping+ADs-
+AD4- +AD4- +AD4AoACgAKAAoACg- +AH0-
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- This has disadvantages from the 1588 perspective, in that=
 it is=20
+AD4- +AD4- +AD4- not possible for a 1588-aware management client to +ACI-g=
et+ACI- portIdentity.
+AD4- +AD4- +AD4- We are removing a 1588 +ACI-real thing+ACI- from the data=
 model in order=20
+AD4- +AD4- +AD4- to accommodate a syntax limitation of YANG.
+AD4- +AD4-
+AD4- +AD4- I think that in general when you go from an information model t=
o a=20
+AD4- +AD4- concrete data model, you need to adapt to the data modelling=20
+AD4- +AD4- language you are using, and this will in most cases mean that t=
here=20
+AD4- +AD4- will be some differences+ADs- in some cases the data model stru=
cture is=20
+AD4- +AD4- different, and in some cases the data model will result in a mo=
re detailed model.
+AD4- +AD4- How keys are specified is one such example.+AKA- If you were to=
 use=20
+AD4- +AD4- SMIv2, you'd have to change the names (so that they are unique)=
, and=20
+AD4- +AD4- you'd have to map the structures to conceptual tables.
+AD4- +AD4-
+AD4- +AD4- Clients need to understand the data model in use (not just the=
=20
+AD4- +AD4- information model behid it).
+AD4- +AD4-
+AD4- +AD4- +AD4- Question for NETMOD experts
+AD4- +AD4- +AD4- ---
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- My personal preference is Option 1 (leafref). Nevertheles=
s, if the=20
+AD4- +AD4- +AD4- +ACI-config false+ACI- does not provide sufficient mitiga=
tion for today's=20
+AD4- +AD4- +AD4- YANG implementations, we can go with Option 2.
+AD4- +AD4-
+AD4- +AD4- I don't think any implementation would have any problem support=
ing=20
+AD4- +AD4- option 1, but it does look a bit odd.+AKA- Also, it only +ACI-h=
elps+ACI- if the=20
+AD4- +AD4- client is getting the data using +ADw-get+AD4-, but it will not=
 help if it=20
+AD4- +AD4- is using +ADw-get-
+AD4- +AD4- config+AD4-.
+AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4- I think that the cleanest solution is to not try to completely =
mimic=20
+AD4- +AD4- the structure from the information model, but make sure that th=
e=20
+AD4- +AD4- text in the description statements make it clear that the data =
model=20
+AD4- +AD4- looks different compared to the information model, in order to =
help=20
+AD4- +AD4- the
+AD4- readers.
+AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4- /martin
+AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- Feedback is very much appreciated.
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- Thanks folks,
+AD4- +AD4- +AD4- Rodney Cummings
+AD4- +AD4- +AD4- Co-author draft-ietf-tictoc-1588v2-yang-05
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- +AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBf=
AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
+AD4- +AD4- +AD4- netmod mailing list
+AD4- +AD4- +AD4- mailto:netmod+AEA-ietf.org
+AD4- +AD4- +AD4- https://urldefense.proofpoint.com/v2/url?u+AD0-https-3A+A=
F8AXw-www.ietf.org+AF8-
+AD4- +AD4- +AD4- ma
+AD4- +AD4- +AD4- il
+AD4- +AD4- +AD4- man+AF8-listinfo+AF8-netmod+ACY-d+AD0-DwMFAg+ACY-c+AD0-I+=
AF8-0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIP
+AD4- +AD4- +AD4- el
+AD4- +AD4- +AD4- cS
+AD4- +AD4- +AD4- jixA+ACY-r+AD0-WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8=
k+ACY-m+AD0-Tvq4PvUNekeS1
+AD4- +AD4- +AD4- IF
+AD4- +AD4- +AD4- 42
+AD4- +AD4- +AD4- ycx+AF8-7KyiF9Ag9bUucZE51SFvCw+ACY-s+AD0-BahOyOIDKpAWICQO=
grlu0aga7dBde8X07-oq2
+AD4- +AD4- +AD4- il
+AD4- +AD4- +AD4- ON
+AD4- +AD4- +AD4- kw+ACY-e+AD0-
+AD4- +AD4- +AD4-
+AD4- +AD4-
+AD4- +AD4- References:
+AD4- +AD4- . https://urldefense.proofpoint.com/v2/url?u+AD0-https-
+AD4- +AD4- 3A+AF8AXw-mailarchive.ietf.org+AF8-arch+AF8-msg+AF8-tictoc+AF8-=
lm1xq37jffkSMms2XJll3N-
+AD4- +AD4- 2DydC0+ACY-d+AD0-DwMFAg+ACY-c+AD0-I+AF8-0YwoKy7z5LMTVdyO6YCiE2u=
zI1jjZZuIPelcSjixA+ACY-r+AD0-WA71
+AD4- +AD4- sf
+AD4- +AD4- 2o7D
+AD4- +AD4- w7CbYhFt24DPjt3lJuupswWYdnboKbZ8k+ACY-m+AD0-Tvq4PvUNekeS1IF42yc=
x+AF8-7KyiF9Ag9bU
+AD4- +AD4- uc
+AD4- +AD4- ZE51 SFvCw+ACY-s+AD0-8SBqP6TRNUiieCBN4IZ6qzNQ5ZEW8pCBAm1kAULa-M=
g+ACY-e+AD0-
+AD4- +AD4- Rodney Cummings +ADw-mailto:rodney.cummings+AEA-ni.com+AD4-
+AD4- +AD4-
+AD4- +AD4- +AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw=
BfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
+AD4- +AD4- TICTOC mailing list
+AD4- +AD4- TICTOC+AEA-ietf.org
+AD4- +AD4- https://urldefense.proofpoint.com/v2/url?u+AD0-https-
+AD4- +AD4- 3A+AF8AXw-www.ietf.org+AF8-mailman+AF8-listinfo+AF8-tictoc+ACY-=
d+AD0-DwIFgQ+ACY-c+AD0-I+AF8-0YwoKy7z5LMTVd
+AD4- +AD4- yO
+AD4- +AD4- 6YCi
+AD4- +AD4- E2uzI1jjZZuIPelcSjixA+ACY-r+AD0-WA71sf2o7Dw7CbYhFt24DPjt3lJuups=
wWYdnboKbZ8k+ACY-
+AD4- +AD4- m+AD0-
+AD4- +AD4- 3vIq
+AD4- +AD4- KhIleK3ifzu2gqWugIUX62HPLM5VReDafflfyVY+ACY-s+AD0-jy6sTQ1a-
+AD4- +AD4- mKqq1ymmNMj7g1kzyAcFvPE9emfALot4FE+ACY-e+AD0-


From nobody Fri Oct 20 17:27:57 2017
Return-Path: <agenda@ietf.org>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 22D761344F1; Fri, 20 Oct 2017 17:24:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <tictoc-chairs@ietf.org>, <odonoghue@isoc.org>
Cc: tictoc@ietf.org, suresh@kaloom.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150854546113.20809.7558237292595168041.idtracker@ietfa.amsl.com>
Date: Fri, 20 Oct 2017 17:24:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/8C2Go9ZVEbvnNVdJKTQTpi05RiY>
Subject: [TICTOC] tictoc - Requested session has been scheduled for IETF 100
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Oct 2017 00:24:21 -0000

Dear Karen O&#39;Donoghue,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 

tictoc Session 1 (2:00:00)
    Monday, Afternoon Session I 1330-1530
    Room Name: VIP A size: 100
    ---------------------------------------------
    

Special Note: Joint session with NTP


Request Information:


---------------------------------------------------------
Working Group Name: Timing over IP Connection and Transfer of Clock
Area Name: Internet Area
Session Requester: Karen O&#39;Donoghue

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 30
Conflicts to Avoid: 
 First Priority: sacm oauth nfvrg bmwg cfrg saag trans mpls detnet acme ace tls ippm




People who must be present:
  Karen O&#39;Donoghue
  Suresh Krishnan
  Yaakov Stein
  Dieter Sibold

Resources Requested:

Special Requests:
  Please schedule a joint meeting with the NTP WG. Also, we would prefer a morning session if possible to facilitate participation from regular remote participants in the US. 
---------------------------------------------------------


From nobody Thu Oct 26 18:47:59 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AC7F13F4CB; Thu, 26 Oct 2017 18:47:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: tictoc@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150906887807.22201.1438956559860361452@ietfa.amsl.com>
Date: Thu, 26 Oct 2017 18:47:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/trASUa-_HwJUrauQ-1GqSAmP93g>
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588v2-yang-06.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 27 Oct 2017 01:47:58 -0000

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 WG of the IETF.

        Title           : YANG Data Model for IEEE 1588-2008
        Authors         : Yuanlong Jiang
                          Xian Liu
                          Jinchun Xu
                          Rodney Cummings
	Filename        : draft-ietf-tictoc-1588v2-yang-06.txt
	Pages           : 30
	Date            : 2017-10-26

Abstract:
   This document defines a YANG data model for the configuration of
   IEEE 1588-2008 devices and clocks, and also retrieval of the
   configuration information, data set and running states of IEEE
   1588-2008 clocks.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588v2-yang/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-tictoc-1588v2-yang-06
https://datatracker.ietf.org/doc/html/draft-ietf-tictoc-1588v2-yang-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-1588v2-yang-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Oct 26 19:21:27 2017
Return-Path: <jiangyuanlong@huawei.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 2258213F4FE; Thu, 26 Oct 2017 19:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZMLC1-Z1Px3i; Thu, 26 Oct 2017 19:21:18 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 152ED13968C; Thu, 26 Oct 2017 19:21:16 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DRJ84296; Fri, 27 Oct 2017 02:21:15 +0000 (GMT)
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.361.1; Fri, 27 Oct 2017 03:21:14 +0100
Received: from DGGEML507-MBX.china.huawei.com ([169.254.2.245]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0301.000; Fri, 27 Oct 2017 10:21:04 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
CC: "netmod@ietf.org" <netmod@ietf.org>, Xian Liu <lene.liuxian@foxmail.com>,  Rodney Cummings <rodney.cummings@ni.com>, Xujinchun <xujinchun@huawei.com>
Thread-Topic: WG Last Call resolutions incorporated in draft-ietf-tictoc-1588v2-yang-06
Thread-Index: AQHTTso91J0wdpBQm0ySMhnhc/8WWQ==
Date: Fri, 27 Oct 2017 02:21:04 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BBB604A97@dggeml507-mbx.china.huawei.com>
References: <150906887826.22201.5033565145094897903.idtracker@ietfa.amsl.com>
In-Reply-To: <150906887826.22201.5033565145094897903.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.74.202.215]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.59F2981B.0066, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.2.245, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 68bed10d5040c7f7edb6f7d7b4977f73
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/gKZiTs8QZZBVUskFuaLz9DLBT2E>
Subject: [TICTOC] WG Last Call resolutions incorporated in draft-ietf-tictoc-1588v2-yang-06
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 27 Oct 2017 02:21:20 -0000

RGVhciBhbGwsDQoNCkJhc2VkIG9uIGFsbCB0aGUgY29tbWVudHMgd2UgcmVjZWl2ZWQgZHVyaW5n
IHRoZSBXRyBMYXN0IENhbGwgcHJvY2Vzcywgd2UndmUgdXBkYXRlZCB0aGUgZG9jdW1lbnQgdG8g
dmVyc2lvbiA2Lg0KV2UgYmVsaWV2ZSBhbGwgdGhlIExDIGNvbW1lbnRzIGFyZSByZXNvbHZlZCBh
bmQgdGhlIGNvbnNlbnN1cyBpcyByZWZsZWN0ZWQgaW4gdGhpcyBuZXcgcmV2aXNpb24uIA0KTWFu
eSB0aGFua3MgdG8gTWFydGluLCBUYWwsIE9waGVyLCBBbGV4LCBKb2huIGFuZCBtYW55IG90aGVy
cyB3aG8gaGFkIHJldmlld2VkIGFuZCBjb21tZW50ZWQgb24gdGhpcyBkcmFmdC4NCg0KQ2hlZXJz
LA0KWXVhbmxvbmcgb24gYmVoYWxmIG9mIGFsbCBjb2F1dGhvcnMNCg0KLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCkZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVy
bmV0LWRyYWZ0c0BpZXRmLm9yZ10gDQpTZW50OiBGcmlkYXksIE9jdG9iZXIgMjcsIDIwMTcgOTo0
OCBBTQ0KVG86IFhpYW4gTGl1OyBSb2RuZXkgQ3VtbWluZ3M7IHJvZG5leS5jdW1taW5nc0BuaS5j
b207IEppYW5neXVhbmxvbmc7IFh1amluY2h1bg0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZp
Y2F0aW9uIGZvciBkcmFmdC1pZXRmLXRpY3RvYy0xNTg4djIteWFuZy0wNi50eHQNCg0KDQpBIG5l
dyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtaWV0Zi10aWN0b2MtMTU4OHYyLXlhbmctMDYudHh0DQpo
YXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFl1YW5sb25nIEppYW5nIGFuZCBwb3N0
ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KTmFtZToJCWRyYWZ0LWlldGYtdGljdG9jLTE1
ODh2Mi15YW5nDQpSZXZpc2lvbjoJMDYNClRpdGxlOgkJWUFORyBEYXRhIE1vZGVsIGZvciBJRUVF
IDE1ODgtMjAwOA0KRG9jdW1lbnQgZGF0ZToJMjAxNy0xMC0yNg0KR3JvdXA6CQl0aWN0b2MNClBh
Z2VzOgkJMzANClVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1k
cmFmdHMvZHJhZnQtaWV0Zi10aWN0b2MtMTU4OHYyLXlhbmctMDYudHh0DQpTdGF0dXM6ICAgICAg
ICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi10aWN0b2MtMTU4
OHYyLXlhbmcvDQpIdG1saXplZDogICAgICAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWlldGYtdGljdG9jLTE1ODh2Mi15YW5nLTA2DQpIdG1saXplZDogICAgICAgaHR0cHM6Ly9k
YXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvaHRtbC9kcmFmdC1pZXRmLXRpY3RvYy0xNTg4djIteWFu
Zy0wNg0KRGlmZjogICAgICAgICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1k
cmFmdC1pZXRmLXRpY3RvYy0xNTg4djIteWFuZy0wNg0KDQpBYnN0cmFjdDoNCiAgIFRoaXMgZG9j
dW1lbnQgZGVmaW5lcyBhIFlBTkcgZGF0YSBtb2RlbCBmb3IgdGhlIGNvbmZpZ3VyYXRpb24gb2YN
CiAgIElFRUUgMTU4OC0yMDA4IGRldmljZXMgYW5kIGNsb2NrcywgYW5kIGFsc28gcmV0cmlldmFs
IG9mIHRoZQ0KICAgY29uZmlndXJhdGlvbiBpbmZvcm1hdGlvbiwgZGF0YSBzZXQgYW5kIHJ1bm5p
bmcgc3RhdGVzIG9mIElFRUUNCiAgIDE1ODgtMjAwOCBjbG9ja3MuDQoNCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICANCg0KDQpQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9m
IG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uIHVudGlsIHRoZSBodG1saXplZCB2
ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQoNClRoZSBJ
RVRGIFNlY3JldGFyaWF0DQoNCg==


From nobody Sun Oct 29 19:15:17 2017
Return-Path: <Alex.Campbell@Aviatnet.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 58B1213FD5C; Sun, 29 Oct 2017 19:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DhymZUvK2iMA; Sun, 29 Oct 2017 19:15:13 -0700 (PDT)
Received: from mail-send.aviatnet.com (mail-send.aviatnet.com [192.147.115.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 478C813FB2F; Sun, 29 Oct 2017 19:15:13 -0700 (PDT)
From: Alex Campbell <Alex.Campbell@Aviatnet.com>
To: Jiangyuanlong <jiangyuanlong@huawei.com>, "tictoc@ietf.org" <tictoc@ietf.org>
CC: Xian Liu <lene.liuxian@foxmail.com>, Xujinchun <xujinchun@huawei.com>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: WG Last Call resolutions incorporated in draft-ietf-tictoc-1588v2-yang-06
Thread-Index: AQHTTso91J0wdpBQm0ySMhnhc/8WWaL7pCg3
Date: Mon, 30 Oct 2017 02:15:11 +0000
Message-ID: <1509329710965.52658@Aviatnet.com>
References: <150906887826.22201.5033565145094897903.idtracker@ietfa.amsl.com>,  <3B0A1BED22CAD649A1B3E97BE5DDD68BBB604A97@dggeml507-mbx.china.huawei.com>
In-Reply-To: <3B0A1BED22CAD649A1B3E97BE5DDD68BBB604A97@dggeml507-mbx.china.huawei.com>
Accept-Language: en-NZ, en-US
Content-Language: en-NZ
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.15.6.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/DsAikD3iQHNFt_6MkqaGGTG60RE>
Subject: Re: [TICTOC] WG Last Call resolutions incorporated in draft-ietf-tictoc-1588v2-yang-06
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Oct 2017 02:15:15 -0000

Hi,=0A=
I've reviewed this latest draft and have some more comments.=0A=
=0A=
1. I find the introduction to be unnecessarily wordy; it feels like it was =
written with a view of not missing any information out, rather than trying =
to keep it concise.=0A=
   For example, there is no need to elaborate on YANG data types here. It i=
s also not here to sell YANG.=0A=
=0A=
OLD:=0A=
=0A=
   As a synchronization protocol, IEEE 1588-2008 [IEEE1588] is widely=0A=
   supported in the carrier networks, industrial networks, automotive=0A=
   networks, and many other applications. It can provide high=0A=
   precision time synchronization as fine as nano-seconds. The=0A=
   protocol depends on a Precision Time Protocol (PTP) engine to=0A=
   decide its own state automatically, and a PTP transportation layer=0A=
   to carry the PTP timing and various quality messages. The=0A=
   configuration parameters and state data sets of IEEE 1588-2008 are=0A=
   numerous.=0A=
=0A=
   According to the concepts described in [RFC3444], IEEE 1588-2008=0A=
   itself provides an information model in its normative=0A=
   specifications for the data sets (in IEEE 1588-2008 clause 8). Some=0A=
   standardization organizations including the IETF have specified=0A=
   data models in MIBs (Management Information Bases) for IEEE 1588-=0A=
   2008 data sets (e.g. [RFC8173], [IEEE8021AS]). These MIBs are=0A=
   typically focused on retrieval of state data using the Simple=0A=
   Network Management Protocol (SNMP), furthermore, configuration of=0A=
   PTP data sets is not considered in [RFC8173].=0A=
=0A=
   Some service providers and applications require that the management=0A=
   of the IEEE 1588-2008 synchronization network be flexible and more=0A=
   Internet-based (typically overlaid on their transport networks).=0A=
   Software Defined Network (SDN) is another driving factor, which=0A=
   demands an improved configuration capability of synchronization=0A=
   networks.=0A=
=0A=
   YANG [RFC6020] is a data modeling language used to model=0A=
   configuration and state data manipulated by network management=0A=
   protocols like the Network Configuration Protocol (NETCONF)=0A=
   [RFC6241]. A small set of built-in data types are defined in=0A=
   [RFC6020], and a collection of common data types are further=0A=
   defined in [RFC6991]. Advantages of YANG include Internet based=0A=
   configuration capability, validation, rollback and so on. All of=0A=
   these characteristics make it attractive to become another=0A=
   candidate modeling language for IEEE 1588-2008.=0A=
=0A=
NEW:=0A=
=0A=
   IEEE 1588-2008 is a time protocol that provides high precision time=0A=
   synchronization as fine as nano-seconds.=0A=
=0A=
   IEEE 1588-2008 itself provides an information model in its normative=0A=
   specifications for the data sets (IEEE 1588-2008 clause 8).=0A=
   Standard information models (e.g. [RFC8173], [IEEE8021AS]) have been=0A=
   previously defined as MIBs focused on the retrieval of state data using=
=0A=
   SNMP [RFC1157].=0A=
=0A=
   YANG [RFC6020] is a data modeling language used to model configuration=
=0A=
   and state data manipulated by network management protocols like NETCONF=
=0A=
   [RFC6241].=0A=
=0A=
2. Can we refer to the system as simply PTP rather than IEEE 1588(-2008)?=
=0A=
=0A=
3. There is insufficient spacing here to separate the terms from their defi=
nitions:=0A=
OLD=0A=
=0A=
   PTP dataset  Structured attributes of clocks (an OC, BC or TC) used=0A=
   for PTP protocol decisions and for providing values for PTP message=0A=
   fields, see Section 8 of [IEEE1588].=0A=
=0A=
   PTP instance A PTP implementation in the device (i.e., an OC or BC)=0A=
   represented by a specific PTP dataset.=0A=
=0A=
NEW=0A=
=0A=
   PTP dataset=0A=
     Structured attributes of clocks (an OC, BC or TC) used=0A=
     for PTP protocol decisions and for providing values for PTP message=0A=
     fields, see Section 8 of [IEEE1588].=0A=
=0A=
   PTP instance=0A=
     A PTP implementation in the device (i.e., an OC or BC)=0A=
     represented by a specific PTP dataset.=0A=
=0A=
4. There's a singular/plural mismatch here:=0A=
=0A=
   module. Query and configuration of device wide or port specific=0A=
   configuration information and clock data set is described for this=0A=
   version.=0A=
=0A=
and here:=0A=
=0A=
   Query and configuration of clock information include:=0A=
=0A=
5. The choice of uint16 as instance-number limits implementations to 65536 =
distinct instances.=0A=
   While I have a hard time imagining a system with more than 65536 PTP ins=
tances, I would prefer to avoid imposing arbitrary limits.=0A=
   I would recommend changing instance-number to a string (and renaming it =
to instance-name or just name).=0A=
=0A=
6. I still recommend removing -ds from the YANG element names that still in=
clude it. It doesn't appear to add any value.=0A=
=0A=
7. What;s the relevance of injection attacks relevant to this YANG module?=
=0A=
=0A=
=0A=
Alex=0A=
=0A=
=0A=
________________________________________=0A=
From: netmod <netmod-bounces@ietf.org> on behalf of Jiangyuanlong <jiangyua=
nlong@huawei.com>=0A=
Sent: Friday, 27 October 2017 3:21 p.m.=0A=
To: tictoc@ietf.org=0A=
Cc: Xian Liu; Xujinchun; netmod@ietf.org=0A=
Subject: [netmod] WG Last Call resolutions incorporated in draft-ietf-ticto=
c-1588v2-yang-06=0A=
=0A=
Dear all,=0A=
=0A=
Based on all the comments we received during the WG Last Call process, we'v=
e updated the document to version 6.=0A=
We believe all the LC comments are resolved and the consensus is reflected =
in this new revision.=0A=
Many thanks to Martin, Tal, Opher, Alex, John and many others who had revie=
wed and commented on this draft.=0A=
=0A=
Cheers,=0A=
Yuanlong on behalf of all coauthors=0A=
=0A=
-----Original Message-----=0A=
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=0A=
Sent: Friday, October 27, 2017 9:48 AM=0A=
To: Xian Liu; Rodney Cummings; rodney.cummings@ni.com; Jiangyuanlong; Xujin=
chun=0A=
Subject: New Version Notification for draft-ietf-tictoc-1588v2-yang-06.txt=
=0A=
=0A=
=0A=
A new version of I-D, draft-ietf-tictoc-1588v2-yang-06.txt=0A=
has been successfully submitted by Yuanlong Jiang and posted to the IETF re=
pository.=0A=
=0A=
Name:           draft-ietf-tictoc-1588v2-yang=0A=
Revision:       06=0A=
Title:          YANG Data Model for IEEE 1588-2008=0A=
Document date:  2017-10-26=0A=
Group:          tictoc=0A=
Pages:          30=0A=
URL:            https://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588=
v2-yang-06.txt=0A=
Status:         https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588v2-y=
ang/=0A=
Htmlized:       https://tools.ietf.org/html/draft-ietf-tictoc-1588v2-yang-0=
6=0A=
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-tictoc-158=
8v2-yang-06=0A=
Diff:           https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tictoc-1588v=
2-yang-06=0A=
=0A=
Abstract:=0A=
   This document defines a YANG data model for the configuration of=0A=
   IEEE 1588-2008 devices and clocks, and also retrieval of the=0A=
   configuration information, data set and running states of IEEE=0A=
   1588-2008 clocks.=0A=
=0A=
=0A=
=0A=
=0A=
Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.=0A=
=0A=
The IETF Secretariat=0A=
=0A=
_______________________________________________=0A=
netmod mailing list=0A=
netmod@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/netmod=0A=

