IETF Logo Mail Archive

[hackathon] IETF Hackathon Project Proposal Inquiry

内田祥喜 <6yo17shi@gmail.com> Wed, 13 March 2024 15:55 UTC

Return-Path: <6yo17shi@gmail.com>
X-Original-To: hackathon@ietfa.amsl.com
Delivered-To: hackathon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 943F9C14F6AD for <hackathon@ietfa.amsl.com>; Wed, 13 Mar 2024 08:55:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X7cw09gyMxF3 for <hackathon@ietfa.amsl.com>; Wed, 13 Mar 2024 08:55:51 -0700 (PDT)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A76FC14F5E8 for <hackathon@ietf.org>; Wed, 13 Mar 2024 08:50:47 -0700 (PDT)
Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-5686677bda1so1951492a12.0 for <hackathon@ietf.org>; Wed, 13 Mar 2024 08:50:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710345045; x=1710949845; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=biu7JytyEBFY9Xi2OZODkBt2T2kY6mHrtGYHg9zNQeM=; b=bkpyS46AxVmkXbrtuvGNu/XzBhhe1c73D6NdxkfYXnT44XyBNyXNOZfyHMwr6bUlpY cnKU2zOqmppqyEd62zSdq8FJ+i+ofKzAmzlQ2CLeap2cY/Ym9C5Oo0tEhUXjOcyYP02S f5KPIcMYNcLqPLaYt8FJcw2mnpMi+aezCPpM5IodgRBbNc/qzRTMpaOXBFuo0jUwCAua 5OwczC8koSZKyOk6BG9R3rjjeDc96IZslVAK+jP8YQE3mj+SeItOt+IAy1fPhrikfdsw e+ZF3pyMPrEWqvnruY6EeLIJxWO7/earpjkhNHgmyR6Anb+WnSDXzPDjiT6s/hjBjcoJ 65qw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710345045; x=1710949845; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=biu7JytyEBFY9Xi2OZODkBt2T2kY6mHrtGYHg9zNQeM=; b=qnZJZXFuF6RMCaf1Ye67zxIRkDXNvHJH3toj+cQQktEf+eYcatANoMlzp12+zlbRrc oZkMrwkcoioucpLVZ3rU8ec6I0QX8XezSJeliBaUoAUW4T1eHdJOQhKNnmqA/mXwF6ul /aQ63PEr+Zq0ZW7brpWICXaMd0ZsK2RylzpqSN6wbgVcDXB3wzr8rHzdNzAgjKQhSwoI Zr7qT0gy5VGyrARwDUsXo632sKV9vEcpG7N8Ci8gBRnHWfzeADbqdhf1nR+B7WaXX5nA IZPePHYWjt39w15N9x+i6DJKVyq/h6GBV2bEhrYiEEzgpaOm3YYtM7xJO6OfCD72KBeE wZUg==
X-Gm-Message-State: AOJu0Yw+SP0ntta2Sy6veS+gTZ9oabiKLkZywnIZDIjauwzXEW0wDLjr 1xXxSd3RK2vXxXbNoJrw34pAd1YgZMBWIVPmANepFZ1KA+jHilYn7NJoUwnM2GSG4oR0zuA5lJj CJiRrkCtMOzAd23tZqR3vhw284g+zKC2/DSI=
X-Google-Smtp-Source: AGHT+IG8moGap8K76UzbDsTJWarKEc2ZQl0y6ZY4bKBsZTjjCxIkZYgDRbXJo3UUOGikIuLXnm2ktRz5EqIFi3NzoE0=
X-Received: by 2002:a17:906:3595:b0:a46:6151:4ca1 with SMTP id o21-20020a170906359500b00a4661514ca1mr1540594ejb.22.1710345045060; Wed, 13 Mar 2024 08:50:45 -0700 (PDT)
MIME-Version: 1.0
From: 内田祥喜 <6yo17shi@gmail.com>
Date: Thu, 14 Mar 2024 00:50:33 +0900
Message-ID: <CAGfXTyue8p+wHXcCx5gVD471ES4Ets9kOyVou5pOzORQB-rf0w@mail.gmail.com>
To: hackathon@ietf.org
Content-Type: multipart/alternative; boundary="000000000000dab21506138cbc51"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hackathon/xVzNkPGGE6dErSvb0USKJWzehAc>
Subject: [hackathon] IETF Hackathon Project Proposal Inquiry
X-BeenThere: hackathon@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussion regarding past, present, and future IETF hackathons." <hackathon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hackathon>, <mailto:hackathon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hackathon/>
List-Post: <mailto:hackathon@ietf.org>
List-Help: <mailto:hackathon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hackathon>, <mailto:hackathon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2024 15:55:51 -0000

Dear IETF Hackathon Organizers,

I'm Yoshiki Uchida from Keio University in Japan. I have something I'd like
to do at the IETF Hackathon. Our project, entitled the Dynamic Orbital
Communication Adjustment Protocol (DOCAP), is designed to significantly
improve the efficiency and reliability of communications in space by
dynamically adjusting communication margins. This adjustment is based on
real-time and predictive velocity and acceleration data of satellites and
spacecraft.

The core of our proposal involves the development of a novel protocol that
utilizes heartbeat messages for the dynamic adjustment of communication
parameters in orbital communication systems. This would entail the
formulation of a new message format to convey essential velocity and
acceleration data, alongside a mechanism for calculating dynamic
communication margins.

Before we proceed with our detailed proposal, we seek to confirm a few
critical points with you:
1. Given that our concept is original and currently lacks a formal draft or
pre-existing specification within the IETF document repository, would our
project be considered appropriate for submission to the IETF Hackathon?
2. Are projects that introduce entirely new concepts, as opposed to
building upon existing drafts, welcome at the Hackathon?

Our primary aim is to contribute a fresh perspective to the challenges of
space communication.

Thank you very much for considering our inquiry.

Best regards,
Yoshiki Uchida
6yo17shi@gmail.com
(uchiyoshi@sfc.wide.ad.jp)

v2.23.0 | Report a Bug | By Email