Re: [TICTOC] Questions (and one comment) on ietf-ptp
Rodney Cummings <rodney.cummings@ni.com> Wed, 04 April 2018 16:23 UTC
Return-Path: <prvs=3632af6211=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 D158A12E858 for <tictoc@ietfa.amsl.com>; Wed, 4 Apr 2018 09:23:14 -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, HTML_MESSAGE=0.001, 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 H3CnFBtx-Hfx for <tictoc@ietfa.amsl.com>; Wed, 4 Apr 2018 09:23:10 -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 534A912E04B for <tictoc@ietf.org>; Wed, 4 Apr 2018 09:23:10 -0700 (PDT)
Received: from pps.filterd (m0098778.ppops.net [127.0.0.1]) by mx0b-00010702.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w34GIOut017445; Wed, 4 Apr 2018 11:23:03 -0500
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0056.outbound.protection.outlook.com [216.32.180.56]) by mx0b-00010702.pphosted.com with ESMTP id 2h33uuyg43-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 04 Apr 2018 11:23:02 -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=3wPHqa9SuCPCW41Hp8zfhPFe8sLAGM/qavZYRkubOno=; b=YAmJhzqTA0VfbbbAC2TIN0Q1zOGuOq3LeLFEgoYL5jsmqXxpkW5iB+y706BbKi+mpVPLly/lSEahFcUarZpOO1rQwitq+1x2ZGkCN2ZYLx/ERngP8GoYJiD1cIQQzNfgp4T6cxoe+29er8eXftQGPbzIGx/7MzftNz1aDL3uFy4=
Received: from CY1PR0401MB1536.namprd04.prod.outlook.com (10.163.19.154) by CY1PR0401MB1673.namprd04.prod.outlook.com (10.162.166.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.653.12; Wed, 4 Apr 2018 16:22:59 +0000
Received: from CY1PR0401MB1536.namprd04.prod.outlook.com ([fe80::5c7b:7277:280a:e15b]) by CY1PR0401MB1536.namprd04.prod.outlook.com ([fe80::5c7b:7277:280a:e15b%13]) with mapi id 15.20.0631.013; Wed, 4 Apr 2018 16:22:59 +0000
From: Rodney Cummings <rodney.cummings@ni.com>
To: Jiangyuanlong <jiangyuanlong@huawei.com>, Alex Campbell <Alex.Campbell@Aviatnet.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Questions (and one comment) on ietf-ptp
Thread-Index: AQHTy6EhthiHDWHAOkiDbnTRANKrCaPv80LggAC1oFA=
Date: Wed, 04 Apr 2018 16:22:58 +0000
Message-ID: <CY1PR0401MB15368FDC00E18E0884D9C98792A40@CY1PR0401MB1536.namprd04.prod.outlook.com>
References: <1522797165709.26438@Aviatnet.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBB6C8B77@dggeml507-mbs.china.huawei.com>
In-Reply-To: <3B0A1BED22CAD649A1B3E97BE5DDD68BBB6C8B77@dggeml507-mbs.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.194]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR0401MB1673; 7:zEZyvUeGHtbXLQc+gA5Is7J759dWqwsy1JgKQz3qNFhRrZK/cL8HHR68KdWQtKkRV02RbTe8oSUn9AqNiDT6EN4oRR9kqlVx0nUXRgN9I+G+LS79d+NF/xzvd6Xx8Q6Dk69+/qsdT/7Ub3stvcdYK5AzucGvzGDDuSmb/iid7AIhe1Dk5s/PFYm12F96TJjE+e/OCIuxbdzTGXE7evmzqZkNDTmQ6kMGNBnyX/VIO938GPN9rmBP3T4hASzrv5cg
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 0569bc43-4f93-4cfd-7c9f-08d59a4854aa
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:CY1PR0401MB1673;
x-ms-traffictypediagnostic: CY1PR0401MB1673:
x-microsoft-antispam-prvs: <CY1PR0401MB1673A80852F364BD014F0F8892A40@CY1PR0401MB1673.namprd04.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(50582790962513)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231221)(944501327)(52105095)(6041310)(20161123558120)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(6072148)(201708071742011); SRVR:CY1PR0401MB1673; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0401MB1673;
x-forefront-prvs: 0632519F33
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(39380400002)(39860400002)(376002)(396003)(366004)(199004)(189003)(478600001)(25786009)(6116002)(790700001)(26005)(33656002)(6506007)(106356001)(86362001)(99286004)(7736002)(3846002)(66066001)(76176011)(74316002)(486006)(105586002)(14454004)(53546011)(102836004)(7696005)(186003)(229853002)(5660300001)(6246003)(2501003)(476003)(8936002)(55016002)(110136005)(5250100002)(97736004)(9686003)(11346002)(3660700001)(446003)(68736007)(54896002)(53936002)(236005)(2900100001)(81156014)(6306002)(6436002)(316002)(81166006)(8676002)(2906002)(3280700002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0401MB1673; H:CY1PR0401MB1536.namprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ni.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: K7cnFrJu0uTG1bAT5LKewfP36ZMVXBlNPcXkUMPpMxWh++/sjTBH+ww6XGPZdc+wVoM+N41n72+JKxvbQTyXEYsBZDnOr26sKwv0QTzN1QqzEjmMs04b0FhjRU6nrRzQagz5HUk2iJXfftJf8hrDd9imtftPJFIVrNg8zPgHirxx7OqEgSncrU1AoNoRMJO2aHbMvcfkfou5YcQGAUwrpr462pL6rvHuroVuDGZPcEU/BV+nPlAZPozEKGhPOIFNMr4MSvhaGGbE39lupeZBPnXC1CX+IWPvcbG9mkzXioLXcB4x9HtgVWqTueG0xYRa+gjiw6JBih89NgKqXmZXs4cqUjMR9cDfS6YvDrJvU6jlnDzpTxjdcomg5lFE37yvK36qEAnlMjRHNIITQE3auqtSbjU2lJkPQncRRGdOb5o=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY1PR0401MB15368FDC00E18E0884D9C98792A40CY1PR0401MB1536_"
MIME-Version: 1.0
X-OriginatorOrg: ni.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0569bc43-4f93-4cfd-7c9f-08d59a4854aa
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2018 16:22:58.9700 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 87ba1f9a-44cd-43a6-b008-6fdb45a5204e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0401MB1673
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-04-04_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=inbound_policy_notspam policy=inbound_policy score=30 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=30 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1804040164
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/Z2_LZg5W6kUq2KWekYNVqfhfRRw>
Subject: Re: [TICTOC] Questions (and one comment) on ietf-ptp
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, 04 Apr 2018 16:23:18 -0000
Hi guys, Regarding the last question on instances. Technically speaking, 1588-2008 did support multiple instances (including multiple domains), but the specifications were ambiguous. The upcoming 1588-rev clarifies the specifications for multiple instances. We've incorporated some of that multi-instance clarity into the 1588-2008 YANG. A single port can be configured as a member of more than one instance. As one example, you might have an instance that uses domainNumber=1, and a second instance that uses domainNumber=2, and the port is common to both instances at the edge, and redundant (i.e. each domainNumber on different ports) in the interior of the network (e.g. maximally redundant trees algorithm). Rodney From: Jiangyuanlong [mailto:jiangyuanlong@huawei.com] Sent: Tuesday, April 3, 2018 10:47 PM To: Alex Campbell ; tictoc@ietf.org<mailto:tictoc@ietf.org> Cc: Rodney Cummings Subject: RE: Questions (and one comment) on ietf-ptp Alex, Regarding the two questions, I think both are out of scope of 1588-2008 while they are valid for 1588v2.1: “Is there a way for the management system to determine the relationship between port numbers and interface names, when using transparent clock mode? port-ds-list has underlying-interface, which seems to solve exactly this problem. But there's no such leaf for transparent-clock-port-ds-list.” My opinion is, underlying-interface can also be introduced to transparent clock for the YANG module of 1588v2.1. “What should happen if a port is configured as a member of more than one instance (or one instance and transparent clock)?” My understanding is, IEEE 1588-2008 only deals with one domain (i.e., instance). I heard there were discussions on multiple instances in the new revision of 1588, maybe Rodney can give some hints. Thanks, Yuanlong From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of Alex Campbell Sent: Wednesday, April 04, 2018 7:13 AM To: tictoc@ietf.org<mailto:tictoc@ietf.org> Subject: [TICTOC] Questions (and one comment) on ietf-ptp Hi, Regarding the YANG model defined in draft-ietf-tictoc-1588v2-yang-07: When an arbitrary identifier is needed for a list key, most YANG models tend to use strings (e.g. ietf-hardware, ietf-interfaces, tend to use strings rather than numbers. I suggest changing instance-number to a string instance-name. Is there a way for the management system to determine the relationship between port numbers and interface names, when using transparent clock mode? port-ds-list has underlying-interface, which seems to solve exactly this problem. But there's no such leaf for transparent-clock-port-ds-list. Finally, what should happen if a port is configured as a member of more than one instance (or one instance and transparent clock)? Thanks, Alex
- [TICTOC] Questions (and one comment) on ietf-ptp Alex Campbell
- Re: [TICTOC] Questions (and one comment) on ietf-… Alex Campbell
- Re: [TICTOC] Questions (and one comment) on ietf-… Jiangyuanlong
- Re: [TICTOC] Questions (and one comment) on ietf-… Jiangyuanlong
- Re: [TICTOC] Questions (and one comment) on ietf-… BEN HADJ SAID Siwar
- Re: [TICTOC] Questions (and one comment) on ietf-… Rodney Cummings
- Re: [TICTOC] Questions (and one comment) on ietf-… Jiangyuanlong