From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sun Jan 1 18:43:34 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF70311E808C for ; Sun, 1 Jan 2012 18:43:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.223 X-Spam-Level: X-Spam-Status: No, score=-4.223 tagged_above=-999 required=5 tests=[AWL=2.377, BAYES_00=-2.599, 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 LHkkoJohq3lq for ; Sun, 1 Jan 2012 18:43:33 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 838DD11E808A for ; Sun, 1 Jan 2012 18:43:33 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 98FE786D9FE for ; Mon, 2 Jan 2012 02:43:32 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 8287C86D4F0 for ; Mon, 26 Dec 2011 17:37:51 +0000 (UTC) Received: from mail-iy0-f175.google.com ([209.85.210.175]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RfEUe-000917-6a for ntpwg@lists.ntp.org; Mon, 26 Dec 2011 17:37:51 +0000 Received: by iakh37 with SMTP id h37so15572133iak.6 for ; Mon, 26 Dec 2011 09:37:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=x-rim-org-msg-ref-id:message-id:content-transfer-encoding:reply-to :x-priority:references:in-reply-to:sensitivity:importance:subject:to :cc:from:date:content-type:mime-version; bh=ILvAvNqeTFkGrBL9lCUlhgojkwm8x7eqODIJE+NyPvU=; b=kgAmvClEnkznkgfTMCfniQhaGb8gt28oi21PTVmcXJJUpOkCYEVAKTZKo0pr96vy4A uq+5jt7SqWmlEIUC6pCmd/LRo1bBiEM5OTnIxw8WPIJLFYLeybJo86kGmvttLThj/PXl m5evAPHNjOK+b8Qmbw0Z/XrxNWq/abHl7H1iI= Received: by 10.50.194.202 with SMTP id hy10mr27290565igc.23.1324921060224; Mon, 26 Dec 2011 09:37:40 -0800 (PST) Received: from 172.29.195.212 (bda-74-82-80-222.bis6.us.blackberry.com. [74.82.80.222]) by mx.google.com with ESMTPS id l35sm79807505ibj.0.2011.12.26.09.37.39 (version=SSLv3 cipher=OTHER); Mon, 26 Dec 2011 09:37:39 -0800 (PST) X-rim-org-msg-ref-id: 1646878607 Message-ID: <1646878607-1324921058-cardhu_decombobulator_blackberry.rim.net-966888399-@b27.c2.bise6.blackberry> X-Priority: Normal References: <4EF791B1.9020200@gis.net> <4EF7B326.7050504@isoc.org> <4EF7E138.6060800@ntp.org> <4EF8AB20.7000803@udel.edu> In-Reply-To: <4EF8AB20.7000803@udel.edu> Sensitivity: Normal Importance: Normal To: "Dave Mills" , tictoc-bounces@ietf.org, "Danny Mayer" From: kodonog@gmail.com Date: Mon, 26 Dec 2011 17:37:37 +0000 MIME-Version: 1.0 X-SA-Exim-Connect-IP: 209.85.210.175 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: kodonog@gmail.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) X-Mailman-Approved-At: Mon, 02 Jan 2012 02:41:42 +0000 Cc: NTP Working Group , "tictoc@ietf.org" , Karen O'Donoghue Subject: Re: [ntpwg] [TICTOC] Control Messages Protocol for Use with Network Time Protocol Version 4 X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: kodonog@gmail.com List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Dave, This is the document I gave you a heads up on last fall. You suggested I bring Dave Hart into the loop. Dave provided the updates reflected in -01. As a listed author, you should be receiving the draft announcements. If this isn't happening, I will need to look into why. Anyhow, I am looking to the ntp developer community to provide the update and review necessary to make this accurate. The material was not captured in the update to RFC 1305 and we'd like to fix that. Karen Sent from my Verizon Wireless BlackBerry -----Original Message----- From: "David L. Mills" Sender: tictoc-bounces@ietf.org Date: Mon, 26 Dec 2011 17:13:04 To: Danny Mayer Cc: NTP Working Group; tictoc@ietf.org; Subject: Re: [TICTOC] [ntpwg] Control Messages Protocol for Use with Network Time Protocol Version 4 _______________________________________________ TICTOC mailing list TICTOC@ietf.org https://www.ietf.org/mailman/listinfo/tictoc _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Mon Jan 2 00:11:50 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17F3A21F8C4E for ; Mon, 2 Jan 2012 00:11:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.924 X-Spam-Level: X-Spam-Status: No, score=-4.924 tagged_above=-999 required=5 tests=[AWL=1.675, BAYES_00=-2.599, 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 Ovh7hE9jZ0uf for ; Mon, 2 Jan 2012 00:11:49 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id F379721F8C4C for ; Mon, 2 Jan 2012 00:11:48 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 2B10C86D769 for ; Mon, 2 Jan 2012 08:11:48 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id B1F3286D333 for ; Mon, 2 Jan 2012 08:08:08 +0000 (UTC) Received: from rrzmta2.uni-regensburg.de ([194.94.155.52]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RhcwA-000Mtf-Vs for ntpwg@lists.ntp.org; Mon, 02 Jan 2012 08:08:08 +0000 Received: from rrzmta2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 18FE558C8 for ; Mon, 2 Jan 2012 09:07:59 +0100 (CET) Received: from gwsmtp1.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by rrzmta2.uni-regensburg.de (Postfix) with ESMTP id DB5DE578B for ; Mon, 2 Jan 2012 09:07:58 +0100 (CET) Received: from uni-regensburg-smtp1-MTA by gwsmtp1.uni-regensburg.de with Novell_GroupWise; Mon, 02 Jan 2012 09:07:58 +0100 Message-Id: <4F0173E9020000A10000890C@gwsmtp1.uni-regensburg.de> X-Mailer: Novell GroupWise Internet Agent 12.0.0 Date: Mon, 02 Jan 2012 09:07:53 +0100 From: "Ulrich Windl" To: "Danny Mayer" ,"David L. Mills" References: <4EF791B1.9020200@gis.net> <4EF7B326.7050504@isoc.org> <4EF7E138.6060800@ntp.org> <4EF8AB20.7000803@udel.edu> <4EFA71B2.1070605@ntp.org> In-Reply-To: <4EFA71B2.1070605@ntp.org> Mime-Version: 1.0 Content-Disposition: inline X-SA-Exim-Connect-IP: 194.94.155.52 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: Ulrich.Windl@rz.uni-regensburg.de X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: NTP Working Group , "tictoc@ietf.org" , odonoghue@isoc.org Subject: [ntpwg] Antw: Re: Control Messages Protocol for Use with Network Time Protocol Version 4 X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Hello! IMHO anything that is part of a packet on the network should be documented. Also if they are neccessary for understanding the algorithm, they should also be documented. And preferrably a specific code shouldn't change it's meaning over time; it's better to use a new code instead. I'm not deeply in NTP at the moment, but felt to comment. Regards, Ulrich >>> Danny Mayer schrieb am 28.12.2011 um 02:32 in Nachricht <4EFA71B2.1070605@ntp.org>: > Dave, > > I don't think that event codes should be documented in an RFC. They > belong in the reference implementation documentation. They are specific > to the reference implementation but other implementations need to be > doing the own thing in this regard. I'm sure chrony doesn't use them, > for example. If the status words are standard then they belong in the RFC. > > Danny > > On 12/26/2011 12:13 PM, David L. Mills wrote: > > Danny, > > > > This is the first I have seen the document, but my name is on it, so I > > should respond. > > > > The document from which this is derived is twenty years old, although > > it has been updated for recent developments. However, the system per and > > clock status words do not align with those defined in the current ntpq > > and status/event codes defined in the current reference implementation > > documenttation. I suggest the description of the status words in the ID > > be changed to agree with the documentaiton or the documentatino and > > implementation be changed to agree with the ID. > > > > The intent in the event codes is to align them with the protostats > > statistics file messages. These are define din the header files. While > > these change from time to time, some kind of reference should be made to > > the current list. I don't think this should be the IANA, so maybe the > > reference should be to the current documentation. > > > > Dave > _______________________________________________ > ntpwg mailing list > ntpwg@lists.ntp.org > http://lists.ntp.org/listinfo/ntpwg > _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Mon Jan 2 11:12:58 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1E3221F84B9 for ; Mon, 2 Jan 2012 11:12:58 -0800 (PST) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version" X-Spam-Flag: NO X-Spam-Score: -2.798 X-Spam-Level: X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6, J_CHICKENPOX_57=0.6, 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 MfZa7AbcI790 for ; Mon, 2 Jan 2012 11:12:57 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 7F27821F84B7 for ; Mon, 2 Jan 2012 11:12:57 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 95FA886D762 for ; Mon, 2 Jan 2012 19:12:55 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 8FE4686D333 for ; Mon, 2 Jan 2012 17:22:18 +0000 (UTC) Received: from smtp3.bmf.com.br ([200.19.56.27]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RhlaR-000BXy-Fq for ntpwg@lists.ntp.org; Mon, 02 Jan 2012 17:22:18 +0000 Content-Type: multipart/mixed; boundary="===============0589066146==" MIME-Version: 1.0 Received: from b5cf7.static.pacific.net.au (HELO EXCCOR0201P.corporate.int) ([125.255.60.247]) by bmfas511irop.bmf.com.br with ESMTP; 02 Jan 2012 15:24:18 -0200 Received: from EXCCOR01CP.corporate.int ([169.254.1.95]) by exccor0201p ([125.255.60.247]) with mapi; Mon, 2 Jan 2012 15:22:12 -0200 From: Juliano Rodrigo De Oliveira Souza To: "ntpwg@lists.ntp.org" Date: Mon, 2 Jan 2012 15:22:10 -0200 Thread-Topic: symmetricom s350 mib Thread-Index: AczJcw9h16l4978TTimOWDLMAd0TOQ== Message-ID: <02C5BE0E4BEDE74B84AF8D7306AA5E2B5BCE3D745B@EXCCOR01CP.corporate.int> Accept-Language: pt-BR X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: pt-BR MIME-Version: 1.0 X-SA-Exim-Connect-IP: 200.19.56.27 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: prvs=3418f8560=jusouza@bvmf.com.br X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) X-Mailman-Approved-At: Mon, 02 Jan 2012 19:10:15 +0000 Subject: [ntpwg] symmetricom s350 mib X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org --===============0589066146== Content-Language: pt-BR Content-Type: multipart/alternative; boundary="_000_02C5BE0E4BEDE74B84AF8D7306AA5E2B5BCE3D745BEXCCOR01CPcor_" --_000_02C5BE0E4BEDE74B84AF8D7306AA5E2B5BCE3D745BEXCCOR01CPcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hy folks! The SYMM-SMI mib for the s350 (Symmetricom) returns the valid codes(see bel= ow): But where is the REACH inside that? We calling via modem(Stratum 0) to have the timeclock. Maybe the NTPv4-MIB can return that value? Regards, SYMM-SMI::ntpSysLeap.0 =3D INTEGER: noWarning(0) SYMM-SMI::ntpSysStratum.0 =3D INTEGER: 2 SYMM-SMI::ntpSysPrecision.0 =3D INTEGER: -20 SYMM-SMI::ntpSysRootDelay.0 =3D STRING: "0.000432" SYMM-SMI::ntpSysRootDispersion.0 =3D STRING: "0.751901" SYMM-SMI::ntpSysRefID.0 =3D STRING: "12.13.14.33" SYMM-SMI::ntpSysRefTime.0 =3D STRING: "3534513241.35040" SYMM-SMI::ntpSysPoll.0 =3D INTEGER: 4 SYMM-SMI::ntpSysPeer.0 =3D Gauge32: 890507436 SYMM-SMI::ntpSysPhase.0 =3D STRING: "-0.000032" SYMM-SMI::ntpSysFreq.0 =3D STRING: "-33.656860 PPM" SYMM-SMI::ntpSysError.0 =3D STRING: "No error" SYMM-SMI::ntpSysClock.0 =3D STRING: "Mon Jan 2 15:15:06 2012" SYMM-SMI::ntpSysSystem.0 =3D STRING: "Symmetricom SyncServer" SYMM-SMI::ntpSysProcessor.0 =3D STRING: "X86 Processor" SYMM-SMI::ntpSysNotrust.0 =3D INTEGER: 1 SYMM-SMI::ntpSysPktsReceived.0 =3D INTEGER: 666993 SYMM-SMI::ntpSysMode.0 =3D INTEGER: client(3) SYMM-SMI::ntpSysVersion.0 =3D STRING: "ntpd 4.2.4p8@1.1607-o Tue Dec 14 23:= 47:30 UTC 2010 (1)" SYMM-SMI::tymingStatus.0 =3D STRING: "Good" SYMM-SMI::tymingSource.0 =3D STRING: "4" SYMM-SMI::tymingTime.0 =3D STRING: "Mon Jan 2 15:15:06 2012" SYMM-SMI::tymingVersion.0 =3D STRING: "2.102" SYMM-SMI::tymingFlyPeriod.0 =3D INTEGER: 0 SYMM-SMI::gpsPosition.0 =3D STRING: "1 0 0 0 0 1 0 0 0 0 0" SYMM-SMI::gpsUTCOffset.0 =3D INTEGER: 0 SYMM-SMI::gpsHealth.0 =3D STRING: "Receiver Health: 2" SYMM-SMI::gpsSatlist.0 =3D STRING: "0" SYMM-SMI::gpsMode.0 =3D STRING: "Receiver Mode: Survey" SYMM-SMI::etcVersion.0 =3D STRING: "2.62" SYMM-SMI::etcSerialNbr.0 =3D STRING: "1114A33703" SYMM-SMI::etcModel.0 =3D STRING: "S350" SYMM-SMI::etcUpgrade.0 =3D STRING: "Update value: 0" SYMM-SMI::etcUpgradeServer.0 =3D STRING: "www.symmetricom.com" SYMM-SMI::etcAlarmString.0 =3D "" ___________ Juliano Souza --_000_02C5BE0E4BEDE74B84AF8D7306AA5E2B5BCE3D745BEXCCOR01CPcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hy folks!

<= o:p> 

The SYMM= -SMI mib for the s350 (Symmetricom) returns the valid codes(see below):

But where is the = REACH inside that?

 

We calling via modem(Stratum 0) to have the timeclock.

Maybe the NTPv4-MIB can retur= n that value?

=  

Regards= ,

 <= /o:p>

SYMM-SMI::ntpSysLea= p.0 =3D INTEGER: noWarning(0)

SYMM-SMI::ntpSysStratum.0 =3D INTEGER: 2<= /p>

SYMM-SMI::ntpSysPrecision.0 =3D = INTEGER: -20

S= YMM-SMI::ntpSysRootDelay.0 =3D STRING: "0.000432"

SYMM-SMI::ntpSysRootDispersio= n.0 =3D STRING: "0.751901"

SYMM-SMI::ntpSysRefID.0 =3D STRING: "12.13.14.3= 3"

SYMM-S= MI::ntpSysRefTime.0 =3D STRING: "3534513241.35040"

SYMM-SMI::ntpSysPoll.0 =3D I= NTEGER: 4

SYMM= -SMI::ntpSysPeer.0 =3D Gauge32: 890507436

SYMM-SMI::ntpSysPhase.0 =3D STRING: "-0.00= 0032"

SYM= M-SMI::ntpSysFreq.0 =3D STRING: "-33.656860 PPM"

SYMM-SMI::ntpSysError.0 =3D ST= RING: "No error"

SYMM-SMI::ntpSysClock.0 =3D STRING: "Mon Jan  2 15:1= 5:06 2012"

SYMM-SMI::ntpSysSystem.0 =3D STRING: "Symmetricom SyncServer"

SYMM-SMI::ntpSy= sProcessor.0 =3D STRING: "X86 Processor"

SYMM-SMI::ntpSysNotrust.0 =3D INTEGER:= 1

SYMM-SMI::n= tpSysPktsReceived.0 =3D INTEGER: 666993

SYMM-SMI::ntpSysMode.0 =3D INTEGER: client(3)

SYMM-SMI::ntpSysV= ersion.0 =3D STRING: "ntpd 4.2.4p8@1.1607-o Tue Dec 14 23:47:30 UTC 20= 10 (1)"

S= YMM-SMI::tymingStatus.0 =3D STRING: "Good"

<= p class=3DMsoNormal>SYMM-SMI::tymingSource.0 =3D STRING:= "4"

SYMM-SMI::tymingTime.0 =3D STRING: "Mon Jan  2 15:15:06 2012&quo= t;

SYMM-SMI::t= ymingVersion.0 =3D STRING: "2.102"

SYMM-SMI::tymingFlyPeriod.0 =3D INTEGER: 0<= o:p>

SYMM-SMI::gpsP= osition.0 =3D STRING: "1 0 0 0 0 1 0 0 0 0 0"

SYMM-SMI::gpsUTCOffset.0 =3D INTE= GER: 0

SYMM-SM= I::gpsHealth.0 =3D STRING: "Receiver Health: 2"=

SYMM-SMI::gpsSatlist.0 =3D STRI= NG: "0"

SYMM-SMI::gpsMode.0 =3D STRING: "Receiver Mode: Survey"<= /o:p>

SYMM-SMI::etcVersio= n.0 =3D STRING: "2.62"

= SYMM-SMI::etcSerialNbr.0 =3D STRING: "1114A33703&qu= ot;

SYMM-SMI::= etcModel.0 =3D STRING: "S350"

SYMM-SMI::etcUpgrade.0 =3D STRING: "Update v= alue: 0"

= SYMM-SMI::etcUpgradeServer.0 =3D STRING: "www.symmetricom.com"

SYMM-SMI::etcAla= rmString.0 =3D ""

 

___________

Juliano Souza

= --_000_02C5BE0E4BEDE74B84AF8D7306AA5E2B5BCE3D745BEXCCOR01CPcor_-- --===============0589066146== Content-Type: multipart/alternative; boundary="===============1452992196==" MIME-Version: 1.0 Content-Disposition: inline --===============1452992196== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable --------------------------------------- A BOLSA =C3=A9 para VOC=C3=8A! Quer investir em a=C3=A7=C3=B5es? = Acesse: www.quersersocio.com.br --------------------------------------- Esta mensagem pode conter informa=C3=A7=C3=A3o confidencial e/ou privilegia= da. Se voc=C3=AA n=C3=A3o for o destinat=C3=A1rio ou a pessoa autorizada a = receber esta mensagem, n=C3=A3o dever=C3=A1 utilizar, copiar, alterar, divu= lgar a informa=C3=A7=C3=A3o nela contida ou tomar qualquer a=C3=A7=C3=A3o b= aseada nessas informa=C3=A7=C3=B5es. Se voc=C3=AA recebeu esta mensagem por= engano, por favor avise imediatamente o remetente, respondendo o e-mail e = em seguida apague-o. Agradecemos sua coopera=C3=A7=C3=A3o. = This message may contain confidential and/or privileged information. If you= are not the addressee or authorized to receive this for the addressee, you= must not use, copy, disclose, change, take any action based on this messag= e or any information herein. If you have received this message in error, pl= ease advise the sender immediately by reply e-mail and delete this message.= Thank you for your cooperation. --===============1452992196== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable

---------------------------------------
A BOLSA =C3=A9 para VOC=C3=8A!
Quer investir em a=C3=A7=C3=B5es?
Acesse: www.quersersocio.com.br
---------------------------------------

Esta mensagem pode conter informa=C3=A7=C3=A3o confidencial e/ou privile= giada. Se voc=C3=AA n=C3=A3o for o destinat=C3=A1rio ou a pessoa autorizada= a receber esta mensagem, n=C3=A3o dever=C3=A1 utilizar, copiar, alterar, d= ivulgar a informa=C3=A7=C3=A3o nela contida ou tomar qualquer a=C3=A7=C3=A3= o baseada nessas informa=C3=A7=C3=B5es. Se voc=C3=AA recebeu esta mensagem = por engano, por favor avise imediatamente o remetente, respondendo o e-mail= e em seguida apague-o. Agradecemos sua coopera=C3=A7=C3=A3o.

This message may contain confidential and/or privileged information. If = you are not the addressee or authorized to receive this for the addressee, = you must not use, copy, disclose, change, take any action based on this mes= sage or any information herein. If you have received this message in error,= please advise the sender immediately by reply e-mail and delete this messa= ge. Thank you for your cooperation.

--===============1452992196==-- --===============0589066146== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg --===============0589066146==-- From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Mon Jan 2 13:14:04 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1F311E8093 for ; Mon, 2 Jan 2012 13:14:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.399 X-Spam-Level: X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_53=0.6, J_CHICKENPOX_57=0.6, 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 J6DeMhoQAQPL for ; Mon, 2 Jan 2012 13:14:03 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 460E011E8083 for ; Mon, 2 Jan 2012 13:14:03 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id A733D86D761 for ; Mon, 2 Jan 2012 21:14:01 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 8508D86D333 for ; Mon, 2 Jan 2012 21:12:40 +0000 (UTC) Received: from mx04.gis.net ([208.218.130.12]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RhpBO-0001tm-Kp for ntpwg@lists.ntp.org; Mon, 02 Jan 2012 21:12:40 +0000 Received: from [10.10.10.102] ([141.157.189.77]) by mx04.gis.net; Mon, 02 Jan 2012 16:12:30 -0500 Message-ID: <4F021DBE.2010507@ntp.org> Date: Mon, 02 Jan 2012 16:12:30 -0500 From: Danny Mayer Organization: NTP User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Juliano Rodrigo De Oliveira Souza References: <02C5BE0E4BEDE74B84AF8D7306AA5E2B5BCE3D745B@EXCCOR01CP.corporate.int> In-Reply-To: <02C5BE0E4BEDE74B84AF8D7306AA5E2B5BCE3D745B@EXCCOR01CP.corporate.int> X-Enigmail-Version: 1.3.4 X-SA-Exim-Connect-IP: 208.218.130.12 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: mayer@ntp.org X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" Subject: Re: [ntpwg] symmetricom s350 mib X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: mayer@ntp.org List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org On 1/2/2012 12:22 PM, Juliano Rodrigo De Oliveira Souza wrote: > Hy folks! > > > > The SYMM-SMI mib for the s350 (Symmetricom) returns the valid codes(see > below): > > But where is the *REACH* inside that? > > > > We calling via modem(Stratum 0) to have the timeclock. > > Maybe the NTPv4-MIB can return that value? > This is the NTP Working Group mailing list. We only deal with protocols. You should contact Symmetricom for information like this. They probably have mailing lists for users of their equipment. RFC 5907 documents the information that the MIB can have. Outside of that you need to contact the vendor. > > Regards, > > Juliano Souza > > > > This message may contain confidential and/or privileged information. If > you are not the addressee or authorized to receive this for the > addressee, you must not use, copy, disclose, change, take any action > based on this message or any information herein. If you have received > this message in error, please advise the sender immediately by reply > e-mail and delete this message. Thank you for your cooperation. Nope. This is a public mailing list ans gets disseminated and archived in searchable locations. Danny _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Jan 3 09:30:49 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B38D21F859D for ; Tue, 3 Jan 2012 09:30:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.397 X-Spam-Level: X-Spam-Status: No, score=-5.397 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6, J_CHICKENPOX_57=0.6, MIME_HTML_MOSTLY=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 B1Mb1+oDPpot for ; Tue, 3 Jan 2012 09:30:48 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 1B04921F856B for ; Tue, 3 Jan 2012 09:30:47 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 3918086D750 for ; Tue, 3 Jan 2012 17:30:47 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id F137D86D41E for ; Tue, 3 Jan 2012 17:21:13 +0000 (UTC) Received: from mail5.symmetricom.com ([69.25.98.10]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Ri82x-000A25-9E for ntpwg@lists.ntp.org; Tue, 03 Jan 2012 17:21:13 +0000 X-ASG-Debug-ID: 1325611265-3e5bb6bc0001-dac64w Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id JodUp2hxT6PQb6iZ; Tue, 03 Jan 2012 09:21:05 -0800 (PST) X-Barracuda-Envelope-From: gdowd@symmetricom.com X-ASG-Whitelist: Client Received: from SJC-MBX-01.symmetricom.com ([169.254.1.77]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Tue, 3 Jan 2012 09:21:05 -0800 From: Greg Dowd To: Juliano Rodrigo De Oliveira Souza , "ntpwg@lists.ntp.org" Thread-Topic: symmetricom s350 mib X-ASG-Orig-Subj: RE: symmetricom s350 mib Thread-Index: AczJcw9h16l4978TTimOWDLMAd0TOQAx2hIw Date: Tue, 3 Jan 2012 17:21:04 +0000 Message-ID: <26FBD265CD8D234EAF41115A180F92BB38B74F16@SJC-MBX-01.symmetricom.com> References: <02C5BE0E4BEDE74B84AF8D7306AA5E2B5BCE3D745B@EXCCOR01CP.corporate.int> In-Reply-To: <02C5BE0E4BEDE74B84AF8D7306AA5E2B5BCE3D745B@EXCCOR01CP.corporate.int> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.3.9] MIME-Version: 1.0 X-Barracuda-Connect: UNKNOWN[192.168.10.171] X-Barracuda-Start-Time: 1325611265 X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at symmetricom.com X-SA-Exim-Connect-IP: 69.25.98.10 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: btv1==349b25d4897==gdowd@symmetricom.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Subject: Re: [ntpwg] symmetricom s350 mib X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0245617857499578147==" Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org --===============0245617857499578147== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_26FBD265CD8D234EAF41115A180F92BB38B74F16SJCMBX01symmetr_" --_000_26FBD265CD8D234EAF41115A180F92BB38B74F16SJCMBX01symmetr_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable These enterprise MIBs predate the ntpwg work by well over a decade. Most o= f these devices were originally created as Stratum 1 devices so you will of= ten find source specific error messages for analyzing connections. It look= s like the peer reach register is not there as a generic. For dialup, mayb= e one of the error messages would tell you if a call failed? If you just w= ant to verify current operations, maybe the reference time would show the l= ast call. I would echo the suggestion to contact the tech support guys if = you have more questions. Happy New Year. Greg Dowd gdowd at symmetricom dot com (antispam format) Symmetricom, Inc. www.symmetricom.com "A clever person solves a problem. A wise person avoids it." Albert Einste= in From: ntpwg-bounces+gdowd=3Dsymmetricom.com@lists.ntp.org [mailto:ntpwg-bou= nces+gdowd=3Dsymmetricom.com@lists.ntp.org] On Behalf Of Juliano Rodrigo De= Oliveira Souza Sent: Monday, January 02, 2012 9:22 AM To: ntpwg@lists.ntp.org Subject: [ntpwg] symmetricom s350 mib Hy folks! The SYMM-SMI mib for the s350 (Symmetricom) returns the valid codes(see bel= ow): But where is the REACH inside that? We calling via modem(Stratum 0) to have the timeclock. Maybe the NTPv4-MIB can return that value? Regards, SYMM-SMI::ntpSysLeap.0 =3D INTEGER: noWarning(0) SYMM-SMI::ntpSysStratum.0 =3D INTEGER: 2 SYMM-SMI::ntpSysPrecision.0 =3D INTEGER: -20 SYMM-SMI::ntpSysRootDelay.0 =3D STRING: "0.000432" SYMM-SMI::ntpSysRootDispersion.0 =3D STRING: "0.751901" SYMM-SMI::ntpSysRefID.0 =3D STRING: "12.13.14.33" SYMM-SMI::ntpSysRefTime.0 =3D STRING: "3534513241.35040" SYMM-SMI::ntpSysPoll.0 =3D INTEGER: 4 SYMM-SMI::ntpSysPeer.0 =3D Gauge32: 890507436 SYMM-SMI::ntpSysPhase.0 =3D STRING: "-0.000032" SYMM-SMI::ntpSysFreq.0 =3D STRING: "-33.656860 PPM" SYMM-SMI::ntpSysError.0 =3D STRING: "No error" SYMM-SMI::ntpSysClock.0 =3D STRING: "Mon Jan 2 15:15:06 2012" SYMM-SMI::ntpSysSystem.0 =3D STRING: "Symmetricom SyncServer" SYMM-SMI::ntpSysProcessor.0 =3D STRING: "X86 Processor" SYMM-SMI::ntpSysNotrust.0 =3D INTEGER: 1 SYMM-SMI::ntpSysPktsReceived.0 =3D INTEGER: 666993 SYMM-SMI::ntpSysMode.0 =3D INTEGER: client(3) SYMM-SMI::ntpSysVersion.0 =3D STRING: "ntpd 4.2.4p8@1.1607-o Tue Dec 14 23:= 47:30 UTC 2010 (1)" SYMM-SMI::tymingStatus.0 =3D STRING: "Good" SYMM-SMI::tymingSource.0 =3D STRING: "4" SYMM-SMI::tymingTime.0 =3D STRING: "Mon Jan 2 15:15:06 2012" SYMM-SMI::tymingVersion.0 =3D STRING: "2.102" SYMM-SMI::tymingFlyPeriod.0 =3D INTEGER: 0 SYMM-SMI::gpsPosition.0 =3D STRING: "1 0 0 0 0 1 0 0 0 0 0" SYMM-SMI::gpsUTCOffset.0 =3D INTEGER: 0 SYMM-SMI::gpsHealth.0 =3D STRING: "Receiver Health: 2" SYMM-SMI::gpsSatlist.0 =3D STRING: "0" SYMM-SMI::gpsMode.0 =3D STRING: "Receiver Mode: Survey" SYMM-SMI::etcVersion.0 =3D STRING: "2.62" SYMM-SMI::etcSerialNbr.0 =3D STRING: "1114A33703" SYMM-SMI::etcModel.0 =3D STRING: "S350" SYMM-SMI::etcUpgrade.0 =3D STRING: "Update value: 0" SYMM-SMI::etcUpgradeServer.0 =3D STRING: "www.symmetricom.com" SYMM-SMI::etcAlarmString.0 =3D "" ___________ Juliano Souza --_000_26FBD265CD8D234EAF41115A180F92BB38B74F16SJCMBX01symmetr_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

These enterprise MIBs = predate the ntpwg work by well over a decade.  Most of these devices w= ere originally created as Stratum 1 devices so you will often find source s= pecific error messages for analyzing connections.  It looks like the peer reach register is not there as a generic.  For= dialup, maybe one of the error messages would tell you if a call failed?&n= bsp; If you just want to verify current operations, maybe the reference tim= e would show the last call.  I would echo the suggestion to contact the tech support guys if you have more questions= .  Happy New Year.

 

 

Greg Dowd

gdowd at symmetricom dot com (antispam format)

Symmetricom, Inc.<= /o:p>

www.symmetricom.com

"A clever person solves a problem.  A wise person = avoids it." Albert Einstein<= /o:p>

 

From: ntpwg-bo= unces+gdowd=3Dsymmetricom.com@lists.ntp.org [mailto:ntpwg-bounces+g= dowd=3Dsymmetricom.com@lists.ntp.org] On Behalf Of Juliano Rodrigo De Oliveira Souza
Sent: Monday, January 02, 2012 9:22 AM
To: ntpwg@lists.ntp.org
Subject: [ntpwg] symmetricom s350 mib

 

Hy folks!

 

The SYMM-SMI mib for the s350 (Symmetricom) returns = the valid codes(see below):

But where is the REACH inside that?

 

We calling via modem(Stratum 0) to have the timecloc= k.

Maybe the NTPv4-MIB can return that value?

 

Regards,

 

SYMM-SMI::ntpSysLeap.0 =3D INTEGER: noWarning(0)

SYMM-SMI::ntpSysStratum.0 =3D INTEGER: 2<= /p>

SYMM-SMI::ntpSysPrecision.0 =3D INTEGER: -20

SYMM-SMI::ntpSysRootDelay.0 =3D STRING: "0.0004= 32"

SYMM-SMI::ntpSysRootDispersion.0 =3D STRING: "0= .751901"

SYMM-SMI::ntpSysRefID.0 =3D STRING: "12.13.14.3= 3"

SYMM-SMI::ntpSysRefTime.0 =3D STRING: "35345132= 41.35040"

SYMM-SMI::ntpSysPoll.0 =3D INTEGER: 4

SYMM-SMI::ntpSysPeer.0 =3D Gauge32: 890507436

SYMM-SMI::ntpSysPhase.0 =3D STRING: "-0.000032&= quot;

SYMM-SMI::ntpSysFreq.0 =3D STRING: "-33.656860 = PPM"

SYMM-SMI::ntpSysError.0 =3D STRING: "No error&q= uot;

SYMM-SMI::ntpSysClock.0 =3D STRING: "Mon Jan&nb= sp; 2 15:15:06 2012"

SYMM-SMI::ntpSysSystem.0 =3D STRING: "Symmetric= om SyncServer"

SYMM-SMI::ntpSysProcessor.0 =3D STRING: "X86 Pr= ocessor"

SYMM-SMI::ntpSysNotrust.0 =3D INTEGER: 1<= /p>

SYMM-SMI::ntpSysPktsReceived.0 =3D INTEGER: 666993

SYMM-SMI::ntpSysMode.0 =3D INTEGER: client(3)

SYMM-SMI::ntpSysVersion.0 =3D STRING: "ntpd 4.2= .4p8@1.1607-o Tue Dec 14 23:47:30 UTC 2010 (1)"

SYMM-SMI::tymingStatus.0 =3D STRING: "Good"= ;

SYMM-SMI::tymingSource.0 =3D STRING: "4"

SYMM-SMI::tymingTime.0 =3D STRING: "Mon Jan&nbs= p; 2 15:15:06 2012"

SYMM-SMI::tymingVersion.0 =3D STRING: "2.102&qu= ot;

SYMM-SMI::tymingFlyPeriod.0 =3D INTEGER: 0

SYMM-SMI::gpsPosition.0 =3D STRING: "1 0 0 0 0 = 1 0 0 0 0 0"

SYMM-SMI::gpsUTCOffset.0 =3D INTEGER: 0

SYMM-SMI::gpsHealth.0 =3D STRING: "Receiver Hea= lth: 2"

SYMM-SMI::gpsSatlist.0 =3D STRING: "0"

SYMM-SMI::gpsMode.0 =3D STRING: "Receiver Mode:= Survey"

SYMM-SMI::etcVersion.0 =3D STRING: "2.62"<= o:p>

SYMM-SMI::etcSerialNbr.0 =3D STRING: "1114A3370= 3"

SYMM-SMI::etcModel.0 =3D STRING: "S350"

SYMM-SMI::etcUpgrade.0 =3D STRING: "Update valu= e: 0"

SYMM-SMI::etcUpgradeServer.0 =3D STRING: "www.s= ymmetricom.com"

SYMM-SMI::etcAlarmString.0 =3D ""

 

___________

Juliano Souza

--_000_26FBD265CD8D234EAF41115A180F92BB38B74F16SJCMBX01symmetr_-- --===============0245617857499578147== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg --===============0245617857499578147==-- From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sun Jan 22 11:52:06 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3065C21F851A for ; Sun, 22 Jan 2012 11:52:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.097 X-Spam-Level: X-Spam-Status: No, score=-4.097 tagged_above=-999 required=5 tests=[AWL=2.502, BAYES_00=-2.599, 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 Dxh7c7emaUlC for ; Sun, 22 Jan 2012 11:52:05 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 7BDFF21F8504 for ; Sun, 22 Jan 2012 11:52:02 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 2BD5D86DA02 for ; Sun, 22 Jan 2012 19:52:00 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 4301B86D4F0 for ; Sun, 22 Jan 2012 19:49:26 +0000 (UTC) Received: from elasmtp-scoter.atl.sa.earthlink.net ([209.86.89.67]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Rp3Pp-000F6h-Ng for ntpwg@lists.ntp.org; Sun, 22 Jan 2012 19:49:26 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ncPFB3X4aGQljLHWxPWkFD78ZisaaTrtJw4Ub4LTKdzVjgtu44j8vL/jBpL6RgS7; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [67.180.133.66] (helo=[192.168.1.100]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1Rp3Pj-0008Kv-BT for ntpwg@lists.ntp.org; Sun, 22 Jan 2012 14:49:19 -0500 Message-ID: <4F1C683D.4010307@earthlink.net> Date: Sun, 22 Jan 2012 11:49:17 -0800 From: todd glassey User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: "ntpwg@lists.ntp.org" X-Opacus-Archived: none X-Opacus-Archived: none X-Enigmail-Version: 1.3.4 X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec791fc6dee1b6296c19b001949d17900846350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 67.180.133.66 X-SA-Exim-Connect-IP: 209.86.89.67 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: tglassey@earthlink.net X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Subject: [ntpwg] NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Because of all of the pain on which timescale should be used, NTP should also allow the transmission of a TZ Token identifier of some form in the packet. This is for forensic use more than anything but would be valuable in a number of audit models for NTP. It also makes sense that it should be able to message the client app about what issues it needs to do to the time to make it proper for the client's location. Those issues are outside of traditional synchronization models but should be considered too herein. todd -- Todd S. Glassey This is from my personal email account and any materials from this account come with personal disclaimers. Further I OPT OUT of any and all commercial emailings. _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sun Jan 22 23:37:45 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 197AA1F0C3C for ; Sun, 22 Jan 2012 23:37:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.761 X-Spam-Level: X-Spam-Status: No, score=-5.761 tagged_above=-999 required=5 tests=[AWL=0.837, BAYES_00=-2.599, 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 Mq436PZ9syUf for ; Sun, 22 Jan 2012 23:37:44 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id ADF911F0C38 for ; Sun, 22 Jan 2012 23:37:38 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id DAF0186DA10 for ; Mon, 23 Jan 2012 07:37:37 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 472C086D4F0 for ; Mon, 23 Jan 2012 07:35:10 +0000 (UTC) Received: from rrzmta2.uni-regensburg.de ([194.94.155.52]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RpEQn-0004N6-TD for ntpwg@lists.ntp.org; Mon, 23 Jan 2012 07:35:10 +0000 Received: from rrzmta2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id EC74B59E9 for ; Mon, 23 Jan 2012 08:35:02 +0100 (CET) Received: from gwsmtp1.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by rrzmta2.uni-regensburg.de (Postfix) with ESMTP id DAA354594 for ; Mon, 23 Jan 2012 08:35:02 +0100 (CET) Received: from uni-regensburg-smtp1-MTA by gwsmtp1.uni-regensburg.de with Novell_GroupWise; Mon, 23 Jan 2012 08:35:03 +0100 Message-Id: <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> X-Mailer: Novell GroupWise Internet Agent 12.0.0 Date: Mon, 23 Jan 2012 08:34:56 +0100 From: "Ulrich Windl" To: "todd glassey" , "ntpwg@lists.ntp.org" References: <4F1C683D.4010307@earthlink.net> In-Reply-To: <4F1C683D.4010307@earthlink.net> Mime-Version: 1.0 Content-Disposition: inline X-SA-Exim-Connect-IP: 194.94.155.52 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: Ulrich.Windl@rz.uni-regensburg.de X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Subject: [ntpwg] Antw: NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Hi! if NTP ist using UTC as time "format", why have a timezone? I don't get it. Regards, Ulrich >>> todd glassey schrieb am 22.01.2012 um 20:49 in Nachricht <4F1C683D.4010307@earthlink.net>: > Because of all of the pain on which timescale should be used, NTP should > also allow the transmission of a TZ Token identifier of some form in the > packet. > > This is for forensic use more than anything but would be valuable in a > number of audit models for NTP. > > It also makes sense that it should be able to message the client app > about what issues it needs to do to the time to make it proper for the > client's location. Those issues are outside of traditional > synchronization models but should be considered too herein. > > todd _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Mon Jan 23 05:23:12 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB72521F8732 for ; Mon, 23 Jan 2012 05:23:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fYfQ211PRraP for ; Mon, 23 Jan 2012 05:23:12 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id C96A021F871B for ; Mon, 23 Jan 2012 05:23:11 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 56E0186DA1E for ; Mon, 23 Jan 2012 13:23:11 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 545D186D4F0 for ; Mon, 23 Jan 2012 13:20:46 +0000 (UTC) Received: from acsinet15.oracle.com ([141.146.126.227]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RpJpF-000FYV-7j for ntpwg@lists.ntp.org; Mon, 23 Jan 2012 13:20:46 +0000 Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by acsinet15.oracle.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id q0NDKB7E018246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 23 Jan 2012 13:20:12 GMT Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q0NDKAqU009480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Jan 2012 13:20:10 GMT Received: from abhmt107.oracle.com (abhmt107.oracle.com [141.146.116.59]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q0NDKAOC000805; Mon, 23 Jan 2012 07:20:10 -0600 Received: from [10.195.0.197] (/10.195.0.197) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 23 Jan 2012 05:20:09 -0800 Message-ID: <4F1D5E89.5030203@oracle.com> Date: Mon, 23 Jan 2012 08:20:09 -0500 From: Brian Utterback Organization: Oracle User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:6.0) Gecko/20110814 Thunderbird/6.0 MIME-Version: 1.0 To: Ulrich Windl References: <4F1C683D.4010307@earthlink.net> <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> In-Reply-To: <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> X-Source-IP: acsinet22.oracle.com [141.146.126.238] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090208.4F1D5E8C.0147,ss=1,re=0.000,fgs=0 X-SA-Exim-Connect-IP: 141.146.126.227 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: brian.utterback@oracle.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" Subject: Re: [ntpwg] Antw: NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org I was wondering the same thing. I would like to hear a use case. But while we are on the subject, I think an extension that contains the epoch number would be handy at startup. I don't know if you would include it all the time or only when requested (client server is obvious, but what about peer and broadcast?). But it would solve the rollover problem without all the kludgy "set the earliest date we will accept" stuff. On 01/23/12 02:34, Ulrich Windl wrote: > Hi! > > if NTP ist using UTC as time "format", why have a timezone? I don't get it. > > Regards, > Ulrich > >>>> todd glassey schrieb am 22.01.2012 um 20:49 in > Nachricht<4F1C683D.4010307@earthlink.net>: >> Because of all of the pain on which timescale should be used, NTP should >> also allow the transmission of a TZ Token identifier of some form in the >> packet. >> >> This is for forensic use more than anything but would be valuable in a >> number of audit models for NTP. >> >> It also makes sense that it should be able to message the client app >> about what issues it needs to do to the time to make it proper for the >> client's location. Those issues are outside of traditional >> synchronization models but should be considered too herein. >> >> todd > > > > > _______________________________________________ > ntpwg mailing list > ntpwg@lists.ntp.org > http://lists.ntp.org/listinfo/ntpwg -- blu Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. - Martin Golding -----------------------------------------------------------------------| Brian Utterback - Solaris RPE, Oracle Corporation. Ph:603-262-3916, Em:brian.utterback@oracle.com _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Mon Jan 23 07:23:44 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A07321F86CA for ; Mon, 23 Jan 2012 07:23:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PUVWGL+nEu2J for ; Mon, 23 Jan 2012 07:23:43 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 8597421F86C7 for ; Mon, 23 Jan 2012 07:23:42 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 2B32086DA2C for ; Mon, 23 Jan 2012 15:23:42 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 52D4586D4F0 for ; Mon, 23 Jan 2012 15:15:10 +0000 (UTC) Received: from bsdimp.com ([199.45.160.85] helo=harmony.bsdimp.com) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RpLbx-000Hpn-Rl for ntpwg@lists.ntp.org; Mon, 23 Jan 2012 15:15:10 +0000 Received: from [10.203.62.117] ([74.5.120.186]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id q0NFB3oc076053 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Mon, 23 Jan 2012 08:11:09 -0700 (MST) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) From: Warner Losh In-Reply-To: <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> Date: Mon, 23 Jan 2012 09:11:01 -0600 Message-Id: <20F89B21-E5BB-46C0-B421-3C9A2AC5302A@bsdimp.com> References: <4F1C683D.4010307@earthlink.net> <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> To: "Ulrich Windl" X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Mon, 23 Jan 2012 08:11:12 -0700 (MST) X-SA-Exim-Connect-IP: 199.45.160.85 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: imp@bsdimp.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" Subject: Re: [ntpwg] Antw: NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org On Jan 23, 2012, at 1:34 AM, Ulrich Windl wrote: > if NTP ist using UTC as time "format", why have a timezone? I don't get it. Not so much timezone, but it would be useful for distinguishing when people are running "GPS" time servers, or TAI servers, or the new putative "TI" time that might happen if leap seconds are ever abolished. Some crazy people are talking about running their servers on UT time. A token would allow dissimilar servers to not accidentally freak when they communicate. Warner > Regards, > Ulrich > >>>> todd glassey schrieb am 22.01.2012 um 20:49 in > Nachricht <4F1C683D.4010307@earthlink.net>: >> Because of all of the pain on which timescale should be used, NTP should >> also allow the transmission of a TZ Token identifier of some form in the >> packet. >> >> This is for forensic use more than anything but would be valuable in a >> number of audit models for NTP. >> >> It also makes sense that it should be able to message the client app >> about what issues it needs to do to the time to make it proper for the >> client's location. Those issues are outside of traditional >> synchronization models but should be considered too herein. >> >> todd > > > > > > _______________________________________________ > ntpwg mailing list > ntpwg@lists.ntp.org > http://lists.ntp.org/listinfo/ntpwg > > _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Mon Jan 23 12:16:17 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1075921F86DA for ; Mon, 23 Jan 2012 12:16:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.299 X-Spam-Level: X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[AWL=1.700, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, 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 V0BzQcrSAKDI for ; Mon, 23 Jan 2012 12:16:16 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 17CCE21F86D1 for ; Mon, 23 Jan 2012 12:16:15 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 675CB86DA18 for ; Mon, 23 Jan 2012 20:16:15 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 9FFB586D4F0 for ; Mon, 23 Jan 2012 20:13:44 +0000 (UTC) Received: from elasmtp-dupuy.atl.sa.earthlink.net ([209.86.89.62]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RpQGs-000OAl-2T for ntpwg@lists.ntp.org; Mon, 23 Jan 2012 20:13:44 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=F4Qd7CIFxYQ+7Mu+/U/UdqwNO3v+2vdzG9Q/aCh1U2FclebopI23hzvi8L8KnRly; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [216.171.124.254] (helo=[192.168.0.4]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1RpQFr-0007WK-L9; Mon, 23 Jan 2012 15:12:39 -0500 Message-ID: <4F1DBF35.5010807@earthlink.net> Date: Mon, 23 Jan 2012 12:12:37 -0800 From: todd glassey User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Warner Losh References: <4F1C683D.4010307@earthlink.net> <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> <20F89B21-E5BB-46C0-B421-3C9A2AC5302A@bsdimp.com> In-Reply-To: <20F89B21-E5BB-46C0-B421-3C9A2AC5302A@bsdimp.com> X-Enigmail-Version: 1.3.4 X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec793759edbdd619aa0a5ebf0f03253ee19b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 216.171.124.254 X-SA-Exim-Connect-IP: 209.86.89.62 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: tglassey@earthlink.net X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" Subject: Re: [ntpwg] Antw: NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org On 1/23/2012 7:11 AM, Warner Losh wrote: > > On Jan 23, 2012, at 1:34 AM, Ulrich Windl wrote: >> if NTP ist using UTC as time "format", why have a timezone? I don't get it. > > Not so much timezone, but it would be useful for distinguishing when people are running "GPS" time servers, or TAI servers, or the new putative "TI" time that might happen if leap seconds are ever abolished. Some crazy people are talking about running their servers on UT time. A token would allow dissimilar servers to not accidentally freak when they communicate. > > Warner True - so the issue becomes how the policies of the time practice are implemented. If there are policies like "We only want to take time from TI type systems" then these would need some way of being integrated with existing system models. Also, there are other tools setting up time servers, and they (NEA and DHCP) both need to be able to deal with those issues. As I have said to several off you offlist - we are building a new version of NTP which is totally policy-control centric with the wondrous (and YES DAMNIT I MEAN THAT) time transfer practice and timely interrupt processing models that NTP is based on. We call it Secure Time Protocol or sec*tp for short. SEC*TP takes NTP and breaks the auth token and policy controls out from the daemon itself and places them into a proxy layer which handles them and then passes the data into a NTP port type model. Functionally our model does away with Autokey by creating a OOB proxy/controller node which sets up the time-setting and time-tracking event. The structure of the NTP service is rock-solid because the event certifying tokens are delivered to both the client and the intended server(s) through an OOB SSL Tunnel based interface. This is used to setup a OTPW and ON-DEMAND TOKEN based time service model which is really going to be hard to do anything nasty too. Additionally the service works independently between PTP and NTP transports and can create the proper tokens therein. YES WE WILL RELEASE IT ONCE ITS DONE, but we filed for a patent on this, and if the group wants to see this IP we are willing to disclose it here. Todd > >> Regards, >> Ulrich >> >>>>> todd glassey schrieb am 22.01.2012 um 20:49 in >> Nachricht <4F1C683D.4010307@earthlink.net>: >>> Because of all of the pain on which timescale should be used, NTP should >>> also allow the transmission of a TZ Token identifier of some form in the >>> packet. >>> >>> This is for forensic use more than anything but would be valuable in a >>> number of audit models for NTP. >>> >>> It also makes sense that it should be able to message the client app >>> about what issues it needs to do to the time to make it proper for the >>> client's location. Those issues are outside of traditional >>> synchronization models but should be considered too herein. >>> >>> todd >> >> >> >> >> >> _______________________________________________ >> ntpwg mailing list >> ntpwg@lists.ntp.org >> http://lists.ntp.org/listinfo/ntpwg >> >> > > -- Todd S. Glassey This is from my personal email account and any materials from this account come with personal disclaimers. Further I OPT OUT of any and all commercial emailings. _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Mon Jan 23 19:13:14 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05A0121F85E5 for ; Mon, 23 Jan 2012 19:13:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id isEhnIxWLcpB for ; Mon, 23 Jan 2012 19:13:13 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 5E56B21F85E1 for ; Mon, 23 Jan 2012 19:13:13 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 8A70486DA2B for ; Tue, 24 Jan 2012 03:13:12 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from stenn.ntp.org (stenn.ntp.org [IPv6:2001:4f8:fff7:1::30]) by lists.ntp.org (Postfix) with ESMTP id 9C1C486D4F0 for ; Tue, 24 Jan 2012 03:04:02 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RpWfx-0006uY-NH; Mon, 23 Jan 2012 19:04:01 -0800 To: todd glassey In-reply-to: <4F1DBF35.5010807@earthlink.net> References: <4F1C683D.4010307@earthlink.net> <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> <20F89B21-E5BB-46C0-B421-3C9A2AC5302A@bsdimp.com> <4F1DBF35.5010807@earthlink.net> Comments: In-reply-to todd glassey message dated "Mon, 23 Jan 2012 12:12:37 -0800." X-Mailer: MH-E 7.4.2; nmh 1.3; XEmacs 21.4 (patch 22) Mime-Version: 1.0 (generated by tm-edit 1.8) Date: Mon, 23 Jan 2012 19:04:01 -0800 From: Harlan Stenn Message-Id: Cc: "ntpwg@lists.ntp.org" Subject: Re: [ntpwg] Antw: NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Todd wrote: > ... > YES WE WILL RELEASE IT ONCE ITS DONE, but we filed for a patent on > this, and if the group wants to see this IP we are willing to disclose > it here. > > Todd I'd like to see the IP/patent applications. If you'd please send the info either here to the list or to me I'd appreciate it. H _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Jan 24 05:00:28 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC0321F8542 for ; Tue, 24 Jan 2012 05:00:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bu85AyGe1Xgg for ; Tue, 24 Jan 2012 05:00:27 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id AA9E921F8565 for ; Tue, 24 Jan 2012 05:00:27 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 77B5286D9F8 for ; Tue, 24 Jan 2012 13:00:26 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 57DF686D4F0 for ; Tue, 24 Jan 2012 12:50:49 +0000 (UTC) Received: from [198.22.153.29] (helo=[10.2.64.42]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Rpfpo-000NG7-IX; Tue, 24 Jan 2012 12:50:48 +0000 Message-ID: <4F1EA91E.5010608@ntp.org> Date: Tue, 24 Jan 2012 07:50:38 -0500 From: Danny Mayer User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Harlan Stenn References: <4F1C683D.4010307@earthlink.net> <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> <20F89B21-E5BB-46C0-B421-3C9A2AC5302A@bsdimp.com> <4F1DBF35.5010807@earthlink.net> In-Reply-To: X-Enigmail-Version: 1.3.4 X-SA-Exim-Connect-IP: 198.22.153.29 X-SA-Exim-Rcpt-To: stenn@ntp.org, tglassey@earthlink.net, ntpwg@lists.ntp.org X-SA-Exim-Mail-From: mayer@ntp.org X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" Subject: Re: [ntpwg] Antw: NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org On 1/23/2012 10:04 PM, Harlan Stenn wrote: > Todd wrote: >> ... >> YES WE WILL RELEASE IT ONCE ITS DONE, but we filed for a patent on >> this, and if the group wants to see this IP we are willing to disclose >> it here. >> >> Todd > > I'd like to see the IP/patent applications. If you'd please send the > info either here to the list or to me I'd appreciate it. Do not send ANY IP or patent information to the working group. That is inappropriate for any IETF working group. Furthermore no working group within IETF can consider any IP or patent information except where the claimant has formally notified the IETF through established procedures of any claims on any protocol or process under active consideration by the Working Group. Working Group cannot consider them, it's a legal issue at that point and not a technical issue. The IETF can only issue unencumbered RFC's. Danny _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Jan 24 13:31:32 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10DBF21F8669 for ; Tue, 24 Jan 2012 13:31:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.166 X-Spam-Level: X-Spam-Status: No, score=-5.166 tagged_above=-999 required=5 tests=[AWL=1.433, BAYES_00=-2.599, 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 QjQutoFlQE+8 for ; Tue, 24 Jan 2012 13:31:31 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 284AD21F854C for ; Tue, 24 Jan 2012 13:31:30 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 61B8886D75D for ; Tue, 24 Jan 2012 21:31:30 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 3CC9086D534 for ; Tue, 24 Jan 2012 21:21:57 +0000 (UTC) Received: from elasmtp-galgo.atl.sa.earthlink.net ([209.86.89.61]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RpnoR-00089I-Ca; Tue, 24 Jan 2012 21:21:56 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=s3BYDe0rEV36p6/gv12s3gf/qTSPcygl+yYznqFvwysmJU17/U4d2+LD+Z5GbpJO; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [216.171.124.254] (helo=[192.168.0.4]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1RpnoL-0002iC-9g; Tue, 24 Jan 2012 16:21:49 -0500 Message-ID: <4F1F20EB.4070408@earthlink.net> Date: Tue, 24 Jan 2012 13:21:47 -0800 From: todd glassey User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Danny Mayer References: <4F1C683D.4010307@earthlink.net> <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> <20F89B21-E5BB-46C0-B421-3C9A2AC5302A@bsdimp.com> <4F1DBF35.5010807@earthlink.net> <4F1EA91E.5010608@ntp.org> In-Reply-To: <4F1EA91E.5010608@ntp.org> X-Opacus-Archived: none X-Opacus-Archived: none X-Enigmail-Version: 1.3.4 X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec799e1d7cdf41510ed0e882c5a681c0dd0e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 216.171.124.254 X-SA-Exim-Connect-IP: 209.86.89.61 X-SA-Exim-Rcpt-To: mayer@ntp.org, stenn@ntp.org, ntpwg@lists.ntp.org X-SA-Exim-Mail-From: tglassey@earthlink.net X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" Subject: Re: [ntpwg] Antw: NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org On 1/24/2012 4:50 AM, Danny Mayer wrote: > On 1/23/2012 10:04 PM, Harlan Stenn wrote: >> Todd wrote: >>> ... >>> YES WE WILL RELEASE IT ONCE ITS DONE, but we filed for a patent on >>> this, and if the group wants to see this IP we are willing to disclose >>> it here. >>> >>> Todd >> >> I'd like to see the IP/patent applications. If you'd please send the >> info either here to the list or to me I'd appreciate it. > > Do not send ANY IP or patent information to the working group. That is > inappropriate for any IETF working group. Furthermore no working group > within IETF can consider any IP or patent information except where the > claimant has formally notified the IETF through established procedures > of any claims on any protocol or process under active consideration by > the Working Group. Working Group cannot consider them, it's a legal > issue at that point and not a technical issue. The IETF can only issue > unencumbered RFC's. Danny who in this statement formally do you represent and who is their formal legal point of service? Todd Glassey > > Danny > > -- Todd S. Glassey This is from my personal email account and any materials from this account come with personal disclaimers. Further I OPT OUT of any and all commercial emailings. _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Jan 24 14:02:58 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 623E01F0C44 for ; Tue, 24 Jan 2012 14:02:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.903 X-Spam-Level: X-Spam-Status: No, score=-4.903 tagged_above=-999 required=5 tests=[AWL=1.695, 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 uL99IOR0YJQB for ; Tue, 24 Jan 2012 14:02:57 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id C4EFF1F0C42 for ; Tue, 24 Jan 2012 14:02:56 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 3074A86DA33 for ; Tue, 24 Jan 2012 22:02:55 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id F1A8F86D534 for ; Tue, 24 Jan 2012 21:42:37 +0000 (UTC) Received: from mail5.symmetricom.com ([69.25.98.10]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Rpo8S-0008fx-MU for ntpwg@lists.ntp.org; Tue, 24 Jan 2012 21:42:37 +0000 X-ASG-Debug-ID: 1327441350-3e5b01af0001-dac64w Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id ZWOlhAF4WvRaxxLN for ; Tue, 24 Jan 2012 13:42:30 -0800 (PST) X-Barracuda-Envelope-From: gdowd@symmetricom.com X-ASG-Whitelist: Client Received: from SJC-MBX-01.symmetricom.com ([169.254.1.132]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Tue, 24 Jan 2012 13:42:31 -0800 From: Greg Dowd To: "ntpwg@lists.ntp.org" Thread-Topic: Observation of IETF Policy on Mailing Lists X-ASG-Orig-Subj: Observation of IETF Policy on Mailing Lists Thread-Index: Acza4RIGep68z0slRJC+bDNLR2rviA== Date: Tue, 24 Jan 2012 21:42:29 +0000 Message-ID: <26FBD265CD8D234EAF41115A180F92BB38BA7023@SJC-MBX-01.symmetricom.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.3.9] MIME-Version: 1.0 X-Barracuda-Connect: UNKNOWN[192.168.10.171] X-Barracuda-Start-Time: 1327441350 X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at symmetricom.com X-SA-Exim-Connect-IP: 69.25.98.10 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: btv1==3701f8b46ca==gdowd@symmetricom.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Subject: [ntpwg] Observation of IETF Policy on Mailing Lists X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3975063006003513889==" Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org --===============3975063006003513889== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_26FBD265CD8D234EAF41115A180F92BB38BA7023SJCMBX01symmetr_" --_000_26FBD265CD8D234EAF41115A180F92BB38BA7023SJCMBX01symmetr_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Note Well Any submission to the IETF intended by the Contributor for publication as a= ll or part of an IETF Internet-Draft or RFC and any statement made within t= he context of an IETF activity is considered an "IETF Contribution." Such s= tatements include oral statements in IETF sessions, as well as written and = electronic communications made at any time or place, which are addressed to= : * The IETF plenary session * The IESG, or any member thereof on behalf of the IESG * Any IETF mailing list, including the IETF list itself, any working gr= oup or design team list, or any other list functioning under IETF auspices * Any IETF working group or portion thereof * Any Birds of a Feather (BOF) session * The IAB or any member thereof on behalf of the IAB * The RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (up= dated by RFC 4879). Statements made outside of an IETF session, mailing list or other function,= that are clearly not intended to be input to an IETF activity, group or fu= nction, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details. A participant in any IETF activity is deemed to accept all IETF rules of pr= ocess, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and vid= eo records of meetings may be made and may be available to the public. Greg Dowd gdowd at symmetricom dot com (antispam format) Symmetricom, Inc. www.symmetricom.com "A clever person solves a problem. A wise person avoids it." Albert Einste= in --_000_26FBD265CD8D234EAF41115A180F92BB38BA7023SJCMBX01symmetr_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Note Well

Any submission to the IETF intended by the Contributor = for publication as all or part of an IETF Internet-Draft or RFC and any sta= tement made within the context of an IETF activity is considered an "I= ETF Contribution." Such statements include oral statements in IETF sessions, as well as written and electronic commun= ications made at any time or place, which are addressed to:

  • The IETF plenary session
  • The IESG, or any member thereof on behalf of the IESG
  • Any IETF mailing list, including the IETF list itself, any working group or= design team list, or any other list functioning under IETF auspices
  • Any IETF working group or portion thereof
  • Any Birds of a Feather (BOF) session
  • The IAB or any member thereof on behalf of the IAB
  • The RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879). <= /p>

Statements made outside of an IETF session, mailing lis= t or other function, that are clearly not intended to be input to an IETF a= ctivity, group or function, are not IETF Contributions in the context of th= is notice.

Please consult RFC 5378 and RFC 3979 for details.

A participant in any IETF activity is deemed to accept = all IETF rules of process, as documented in Best Current Practices RFCs and= IESG Statements.

A participant in any IETF activity acknowledges that wr= itten, audio and video records of meetings may be made and may be available= to the public.

 

 

Greg Dowd

gdowd at symmetricom dot com (antispam fo= rmat)

Symmetricom, Inc.

www.symmetricom.com

"A clever person solves a problem.&n= bsp; A wise person avoids it." Albert Einstein

 

--_000_26FBD265CD8D234EAF41115A180F92BB38BA7023SJCMBX01symmetr_-- --===============3975063006003513889== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg --===============3975063006003513889==-- From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Jan 24 14:20:54 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0CB71F0C3C for ; Tue, 24 Jan 2012 14:20:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.999 X-Spam-Level: X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, 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 eAfgkJbMTNoC for ; Tue, 24 Jan 2012 14:20:53 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 967371F0C35 for ; Tue, 24 Jan 2012 14:20:53 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 371AC86DA2B for ; Tue, 24 Jan 2012 22:20:53 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 25CFA86D534 for ; Tue, 24 Jan 2012 21:54:02 +0000 (UTC) Received: from mx04.gis.net ([208.218.130.12]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RpoJW-00099D-44 for ntpwg@lists.ntp.org; Tue, 24 Jan 2012 21:54:02 +0000 Received: from [10.2.64.42] ([198.22.153.29]) by mx04.gis.net; Tue, 24 Jan 2012 16:53:57 -0500 Message-ID: <4F1F2872.1000804@ntp.org> Date: Tue, 24 Jan 2012 16:53:54 -0500 From: Danny Mayer Organization: NTP User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: todd glassey References: <4F1C683D.4010307@earthlink.net> <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> <20F89B21-E5BB-46C0-B421-3C9A2AC5302A@bsdimp.com> <4F1DBF35.5010807@earthlink.net> <4F1EA91E.5010608@ntp.org> <4F1F20EB.4070408@earthlink.net> In-Reply-To: <4F1F20EB.4070408@earthlink.net> X-Enigmail-Version: 1.3.4 X-SA-Exim-Connect-IP: 208.218.130.12 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: mayer@ntp.org X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" Subject: Re: [ntpwg] Antw: NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: mayer@ntp.org List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org On 1/24/2012 4:21 PM, todd glassey wrote: > On 1/24/2012 4:50 AM, Danny Mayer wrote: >> On 1/23/2012 10:04 PM, Harlan Stenn wrote: >>> Todd wrote: >>>> ... >>>> YES WE WILL RELEASE IT ONCE ITS DONE, but we filed for a patent on >>>> this, and if the group wants to see this IP we are willing to disclose >>>> it here. >>>> >>>> Todd >>> >>> I'd like to see the IP/patent applications. If you'd please send the >>> info either here to the list or to me I'd appreciate it. >> >> Do not send ANY IP or patent information to the working group. That is >> inappropriate for any IETF working group. Furthermore no working group >> within IETF can consider any IP or patent information except where the >> claimant has formally notified the IETF through established procedures >> of any claims on any protocol or process under active consideration by >> the Working Group. Working Group cannot consider them, it's a legal >> issue at that point and not a technical issue. The IETF can only issue >> unencumbered RFC's. > > Danny who in this statement formally do you represent and who is their > formal legal point of service? > > Todd Glassey Intellectual Property claims and procedures in the IETF are described here: http://www.ietf.org/ipr/ along with the relevant RFC's. Danny _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Jan 24 15:53:44 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D79621F84F5 for ; Tue, 24 Jan 2012 15:53:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9INWdmWt2Uq7 for ; Tue, 24 Jan 2012 15:53:44 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id BAC2621F84F4 for ; Tue, 24 Jan 2012 15:53:43 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 3E01D86D9F5 for ; Tue, 24 Jan 2012 23:53:43 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from stenn.ntp.org (stenn.ntp.org [IPv6:2001:4f8:fff7:1::30]) by lists.ntp.org (Postfix) with ESMTP id DC58586D534 for ; Tue, 24 Jan 2012 23:22:09 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Rppgl-0008BW-BK; Tue, 24 Jan 2012 15:22:07 -0800 To: todd glassey In-reply-to: <4F1F20EB.4070408@earthlink.net> References: <4F1C683D.4010307@earthlink.net> <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> <20F89B21-E5BB-46C0-B421-3C9A2AC5302A@bsdimp.com> <4F1DBF35.5010807@earthlink.net> <4F1EA91E.5010608@ntp.org> <4F1F20EB.4070408@earthlink.net> Comments: In-reply-to todd glassey message dated "Tue, 24 Jan 2012 13:21:47 -0800." X-Mailer: MH-E 7.4.2; nmh 1.3; XEmacs 21.4 (patch 22) Mime-Version: 1.0 (generated by tm-edit 1.8) Date: Tue, 24 Jan 2012 15:22:07 -0800 From: Harlan Stenn Message-Id: Cc: "ntpwg@lists.ntp.org" Subject: Re: [ntpwg] Antw: NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Todd wrote: > On 1/24/2012 4:50 AM, Danny Mayer wrote: > > On 1/23/2012 10:04 PM, Harlan Stenn wrote: > >> Todd wrote: > >>> ... > >>> YES WE WILL RELEASE IT ONCE ITS DONE, but we filed for a patent on > >>> this, and if the group wants to see this IP we are willing to disclose > >>> it here. > >>> > >>> Todd > >> > >> I'd like to see the IP/patent applications. If you'd please send the > >> info either here to the list or to me I'd appreciate it. Having read what Todd wrote below, I was speaking personally when I wrote the above. My intent was to a) express interest, and b) informally request/invite Todd to follow thru on his offer. That's about as far down this road as I plan to go. H -- > > Do not send ANY IP or patent information to the working group. That is > > inappropriate for any IETF working group. Furthermore no working group > > within IETF can consider any IP or patent information except where the > > claimant has formally notified the IETF through established procedures > > of any claims on any protocol or process under active consideration by > > the Working Group. Working Group cannot consider them, it's a legal > > issue at that point and not a technical issue. The IETF can only issue > > unencumbered RFC's. > > Danny who in this statement formally do you represent and who is their > formal legal point of service? > > Todd Glassey > > > > > Danny > > > > > > > -- > Todd S. Glassey > This is from my personal email account and any materials from this > account come with personal disclaimers. > > Further I OPT OUT of any and all commercial emailings. _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Jan 24 18:41:31 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFA2721F85C2 for ; Tue, 24 Jan 2012 18:41:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.722 X-Spam-Level: X-Spam-Status: No, score=-4.722 tagged_above=-999 required=5 tests=[AWL=1.877, BAYES_00=-2.599, 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 smOywQSnuu9a for ; Tue, 24 Jan 2012 18:41:31 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id CF85E21F8596 for ; Tue, 24 Jan 2012 18:41:30 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 6ECC686DA08 for ; Wed, 25 Jan 2012 02:41:30 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id D0CD486D534 for ; Wed, 25 Jan 2012 02:18:06 +0000 (UTC) Received: from elasmtp-curtail.atl.sa.earthlink.net ([209.86.89.64]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RpsR2-000Ega-JA; Wed, 25 Jan 2012 02:18:05 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=qJHnBD4Pu4ADDiMA8iRigmJN7crxZWJdF1HtsLFe72YO3mVKX/6MmVuRX+9dR5Rs; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Opacus-Archived:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [67.180.133.66] (helo=[192.168.1.100]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1RpsQw-0000F0-TA; Tue, 24 Jan 2012 21:17:58 -0500 Message-ID: <4F1F6653.2040201@earthlink.net> Date: Tue, 24 Jan 2012 18:17:55 -0800 From: todd glassey User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: mayer@ntp.org References: <4F1C683D.4010307@earthlink.net> <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> <20F89B21-E5BB-46C0-B421-3C9A2AC5302A@bsdimp.com> <4F1DBF35.5010807@earthlink.net> <4F1EA91E.5010608@ntp.org> <4F1F20EB.4070408@earthlink.net> <4F1F2872.1000804@ntp.org> In-Reply-To: <4F1F2872.1000804@ntp.org> X-Opacus-Archived: none X-Enigmail-Version: 1.3.4 X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79d6fba0249014866872c82c849c9d5aa3350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 67.180.133.66 X-SA-Exim-Connect-IP: 209.86.89.64 X-SA-Exim-Rcpt-To: mayer@ntp.org, stenn@ntp.org, ntpwg@lists.ntp.org X-SA-Exim-Mail-From: tglassey@earthlink.net X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" Subject: Re: [ntpwg] Antw: NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org On 1/24/2012 1:53 PM, Danny Mayer wrote: > On 1/24/2012 4:21 PM, todd glassey wrote: >> On 1/24/2012 4:50 AM, Danny Mayer wrote: >>> On 1/23/2012 10:04 PM, Harlan Stenn wrote: >>>> Todd wrote: >>>>> ... >>>>> YES WE WILL RELEASE IT ONCE ITS DONE, but we filed for a patent on >>>>> this, and if the group wants to see this IP we are willing to disclose >>>>> it here. IPR with Use License guarentee now on file with the IPR group in the Secretariates office Danny. I listed you as the provocateur therein only I didnt have a tele number for you so I used the ISC. Fix it if you want. Todd >>>>> >>>>> Todd >>>> >>>> I'd like to see the IP/patent applications. If you'd please send the >>>> info either here to the list or to me I'd appreciate it. >>> >>> Do not send ANY IP or patent information to the working group. That is >>> inappropriate for any IETF working group. Furthermore no working group >>> within IETF can consider any IP or patent information except where the >>> claimant has formally notified the IETF through established procedures >>> of any claims on any protocol or process under active consideration by >>> the Working Group. Working Group cannot consider them, it's a legal >>> issue at that point and not a technical issue. The IETF can only issue >>> unencumbered RFC's. >> >> Danny who in this statement formally do you represent and who is their >> formal legal point of service? >> >> Todd Glassey > > Intellectual Property claims and procedures in the IETF are described > here: http://www.ietf.org/ipr/ along with the relevant RFC's. > > Danny > -- Todd S. Glassey This is from my personal email account and any materials from this account come with personal disclaimers. Further I OPT OUT of any and all commercial emailings. _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Jan 24 19:28:35 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4DC711E80A2 for ; Tue, 24 Jan 2012 19:28:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.098 X-Spam-Level: X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[AWL=1.501, BAYES_00=-2.599, 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 oWPwr7TuKZUV for ; Tue, 24 Jan 2012 19:28:35 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id BB11E11E8086 for ; Tue, 24 Jan 2012 19:28:34 -0800 (PST) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 4BFDB86DA2F for ; Wed, 25 Jan 2012 03:28:34 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id D1FCE86D534 for ; Wed, 25 Jan 2012 03:00:43 +0000 (UTC) Received: from elasmtp-kukur.atl.sa.earthlink.net ([209.86.89.65]) by mail1.ntp.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Rpt6I-000FYB-Hk; Wed, 25 Jan 2012 03:00:43 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=SzdHOhTBWTjLN0HeXDl++sk1TVZu+kkb4hQu34P583tJwCSBD3UAGt39DdAPxWsA; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [67.180.133.66] (helo=[192.168.1.100]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1Rpt6C-0003oU-FQ; Tue, 24 Jan 2012 22:00:36 -0500 Message-ID: <4F1F7051.3040006@earthlink.net> Date: Tue, 24 Jan 2012 19:00:33 -0800 From: todd glassey User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Harlan Stenn References: <4F1C683D.4010307@earthlink.net> <4F1D1BB0020000A100008BF9@gwsmtp1.uni-regensburg.de> <20F89B21-E5BB-46C0-B421-3C9A2AC5302A@bsdimp.com> <4F1DBF35.5010807@earthlink.net> <4F1EA91E.5010608@ntp.org> <4F1F20EB.4070408@earthlink.net> In-Reply-To: X-Opacus-Archived: none X-Opacus-Archived: none X-Enigmail-Version: 1.3.4 X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79e0242b574e5d3f47bd57be9212a80bbf350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 67.180.133.66 X-SA-Exim-Connect-IP: 209.86.89.65 X-SA-Exim-Rcpt-To: stenn@ntp.org, mayer@ntp.org, ntpwg@lists.ntp.org X-SA-Exim-Mail-From: tglassey@earthlink.net X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" Subject: Re: [ntpwg] Antw: NTPv5 suggestions X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org On 1/24/2012 3:22 PM, Harlan Stenn wrote: > Todd wrote: >> On 1/24/2012 4:50 AM, Danny Mayer wrote: >>> On 1/23/2012 10:04 PM, Harlan Stenn wrote: >>>> Todd wrote: >>>>> ... >>>>> YES WE WILL RELEASE IT ONCE ITS DONE, but we filed for a patent on >>>>> this, and if the group wants to see this IP we are willing to disclose >>>>> it here. >>>>> >>>>> Todd >>>> >>>> I'd like to see the IP/patent applications. If you'd please send the >>>> info either here to the list or to me I'd appreciate it. > > Having read what Todd wrote below, I was speaking personally when I > wrote the above. My intent was to a) express interest, and b) > informally request/invite Todd to follow thru on his offer. > > That's about as far down this road as I plan to go. > > H > -- >>> Do not send ANY IP or patent information to the working group. That is >>> inappropriate for any IETF working group. Furthermore no working group >>> within IETF can consider any IP or patent information except where the >>> claimant has formally notified the IETF through established procedures >>> of any claims on any protocol or process under active consideration by >>> the Working Group. Working Group cannot consider them, it's a legal >>> issue at that point and not a technical issue. The IETF can only issue >>> unencumbered RFC's. >> >> Danny who in this statement formally do you represent and who is their >> formal legal point of service? Ohhh. sorry my bad - I should have rephrased that. I am with lawyers a lot these days so... How this should sound is that there is a kicker on this license. You have to renew it yearly and report the uses. Its there so we can track the use and for commercial use there is a licensing fee as well. No pain beyond that Harlan. T. >> >> Todd Glassey >> >>> >>> Danny >>> >>> >> >> >> -- >> Todd S. Glassey >> This is from my personal email account and any materials from this >> account come with personal disclaimers. >> >> Further I OPT OUT of any and all commercial emailings. > -- Todd S. Glassey This is from my personal email account and any materials from this account come with personal disclaimers. Further I OPT OUT of any and all commercial emailings. _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg