[P2PSIP] time synchronization
"Songhaibin (A)" <haibin.song@huawei.com> Tue, 27 August 2013 01:22 UTC
Return-Path: <haibin.song@huawei.com>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6763C11E80EC for <p2psip@ietfa.amsl.com>; Mon, 26 Aug 2013 18:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2QhTKXLYuJOY for <p2psip@ietfa.amsl.com>; Mon, 26 Aug 2013 18:22:00 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id DC59D21F9B11 for <p2psip@ietf.org>; Mon, 26 Aug 2013 18:21:59 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AUT28161; Tue, 27 Aug 2013 01:21:57 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 27 Aug 2013 02:21:47 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 27 Aug 2013 02:21:54 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.96]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Tue, 27 Aug 2013 09:21:48 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "p2psip@ietf.org" <p2psip@ietf.org>
Thread-Topic: time synchronization
Thread-Index: Ac6iw8vha32C6L3XTRi3K+kmiEoC4Q==
Date: Tue, 27 Aug 2013 01:21:48 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F247830BB@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-cr-hashedpuzzle: AaGz AfE+ Al62 BNmJ DHyk EFAF FolR F//m HMh/ H4qH IDu7 IHOc INhf I2C6 JOJh Jq2W; 1; cAAyAHAAcwBpAHAAQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {A1702244-42BE-4E51-90DE-AE3968189564}; aABhAGkAYgBpAG4ALgBzAG8AbgBnAEAAaAB1AGEAdwBlAGkALgBjAG8AbQA=; Tue, 27 Aug 2013 01:21:46 GMT; dABpAG0AZQAgAHMAeQBuAGMAaAByAG8AbgBpAHoAYQB0AGkAbwBuAA==
x-cr-puzzleid: {A1702244-42BE-4E51-90DE-AE3968189564}
x-originating-ip: [10.138.41.66]
Content-Type: multipart/alternative; boundary="_000_E33E01DFD5BEA24B9F3F18671078951F247830BBnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [P2PSIP] time synchronization
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 01:22:05 -0000
Hi guys, Nobody responds to my previous time synchronization question. If there is no objection, we will leave it optional. And maybe we can extend the configuration file to explicitly note whether time synchronization is enforced in this overlay. BR, -Haibin
- [P2PSIP] time synchronization Songhaibin (A)