From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb1-f181.google.com (mail-yb1-f181.google.com [209.85.219.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id B65223B29D for ; Tue, 30 Apr 2024 13:12:26 -0400 (EDT) Received: by mail-yb1-f181.google.com with SMTP id 3f1490d57ef6-de6074a464aso1838736276.0 for ; Tue, 30 Apr 2024 10:12:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714497146; x=1715101946; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=f8dc9S9BNVKgRcHxnnmd8zRwpMw817sIKJHc5sz2+BU=; b=kIhUaxf/rbX7ZrEcACHl6MJDZYiGLawxuZbJD2rwmw1XCmaEE8NU3bdfuCeDaptu3v L24rRT2iOq1blKWvl5HX3A+NkoPESG3SyhaULnvvcwuKuX7kIj/wLtnjZbHkh45ZZ/uS k4ZHhW5FbpIDPFfiijq4sf5HtJCZt1dl+xzmfdve8R6FlI2YUmF5uDEzkenjNoPBWXQ/ O0LJYzUx5P75JWrRGwjYmewnafSTH2RQuTVyBlsMaj3fdQOyvf2BLQeAALS69/ChNnM1 CNnRLSALzNCZReG1QTXLIcl/eT9YeDdSVCVSfyNFvoNb1yRQDZzhqEoiUKOzXcRKULRD x7dQ== X-Gm-Message-State: AOJu0YwGjtW2neQrFf+O6413SfmE5rdphuPJyDQ9zOuMxTvT+23akJDA jb9lfH4DhwhiTWqXzZ/1x6AxM4LSf75p1bBQPVQ1BY5oufBpnd7eb2KqVckM5dRpwlSEwjvDnWq jn5dLjf2OXW0clPpmcu7RJP8uHLQ= X-Google-Smtp-Source: AGHT+IG783p638l/ODMrv1IM9X9RCXqWUHU/bu7ZHS5MuVl0VfI1cI0l40tCGSRdF5Lqo4YmBcEKDkjdV0xwp4ZDe/A= X-Received: by 2002:a25:900b:0:b0:de4:604c:41b0 with SMTP id s11-20020a25900b000000b00de4604c41b0mr243470ybl.32.1714497146171; Tue, 30 Apr 2024 10:12:26 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: J Pan Date: Tue, 30 Apr 2024 10:12:14 -0700 Message-ID: To: =?UTF-8?Q?David_Fern=C3=A1ndez?= Cc: starlink Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [Starlink] Time Synchronization in Satellite Networks X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2024 17:12:26 -0000 accurate timing is useful for starlink itself, e.g., https://patents.justia.com/patent/11924821 and its users---hopefully starlink can allow its dish to advertise the time besides location to lan -- J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pa= n On Tue, Apr 30, 2024 at 1:47=E2=80=AFAM David Fern=C3=A1ndez via Starlink wrote: > > Dear Hesham, > > May I ask for what reason do you need the satellites to be synchronized i= n time? What application is requiring this? Earth observation? Then, go for= GNSS-based time synchronization, as done by EO satellites in LEO: https://= navi.ion.org/content/69/3/navi.531 > > "GNSS signals could even be used for reliable navigation in lunar orbit",= so also for time synchronization: https://www.nasa.gov/missions/tech-demon= stration/nasa-navigation-tech-shows-timing-really-is-everything > > It seems that as long as your device can have a GNSS receiver, that's the= best way to keep it time-synchronized. Is there anything preventing the us= e of GNSS on your intended application? > > https://lists.bufferbloat.net/pipermail/starlink/2024-March/002605.html > > Regards, > > David > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink