IETF Logo Mail Archive

Re: [radext] draft-cullen-radextra-status-realm-00

Alexander Clouter <alex+ietf@coremem.com> Mon, 02 January 2023 19:57 UTC

Return-Path: <alex+ietf@coremem.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C058C14CEE0 for <radext@ietfa.amsl.com>; Mon, 2 Jan 2023 11:57:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=coremem.com header.b=dpnixz0I; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=W6Kjlqsu
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 vqW5x-FHWvSM for <radext@ietfa.amsl.com>; Mon, 2 Jan 2023 11:57:06 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 D2319C14F74F for <radext@ietf.org>; Mon, 2 Jan 2023 11:57:06 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id A33893200413 for <radext@ietf.org>; Mon, 2 Jan 2023 14:57:05 -0500 (EST)
Received: from imap46 ([10.202.2.96]) by compute5.internal (MEProxy); Mon, 02 Jan 2023 14:57:05 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coremem.com; h= cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1672689425; x=1672775825; bh=nFNj56htTr CAbxCdx5IS6LIBIspxtdPi4SyiFZPt/Cs=; b=dpnixz0I7fYNcklg8rIZnCLjVL oT3J6pwaC+PK1492IaMgeTc/nlP6IVhleKbiPnmHI1oSFwA6ZEVglJFTmXq0/53c gjd9FjNATKXWJNQOk0pQeb4pURL88XP/muP213rtZy+8FgFPVMOY8TxcT3W7vC0V 2kZkk0MTSkNs70m2bda9nXvU6vG/1B0Nuac4aBfUdOEJdEk9D6QgAWyTVaDgsgb7 wfSBJYz6YV7DdUUhDw7HgI+XidrRUVcs9yTQ/eNRXuVjroErbmf0jo3d1vV9sgIq ndLFydDxdviw48NScSPXDjcvnjv8dH5m8k/PK64u/z54SxF33tDyT8tUluCA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1672689425; x=1672775825; bh=nFNj56htTrCAbxCdx5IS6LIBIspx tdPi4SyiFZPt/Cs=; b=W6KjlqsuTaHYhCWkvhezW3IFG6i8+Prz8iKpTj8U/rHi sFPhSSpHj3Swe4cwVZUomUYuiDI91Xu0D5vgwv6DC9JCrjxdcpWKFgKFEwhhQAPt OgMuSdI/AVqTVaIkZp2NK77tSU9vWzS5UyqpvRGnKMm5FE9QB74b85tLiC7+cW+n meAyvrlj0HTNTuw2eo2PJZJIZrWLZvVoJERLf1rukkGVCAhfM273/BKOorXjEOkE 2upAlHlzOuBODNLko42BbiBwto1QzYsGfOLMO3CHvB7hzDqBQGgx6+A+s6CSZs6Y aStci63S0xpG4ZH3Ckbqkgmd0SOP9OmHanb+gOKSDQ==
X-ME-Sender: <xms:ETezY32AxHkNymkP6z3_ZlymWWHZxahOe4McSqf4j6SFLIt36-wgdA> <xme:ETezY2EfTYWG4sYnP04gMdPA2B8wsApZvOua4ygWwdxa3B2jo4DcZfFZ2uegyGdTD yj46VDQYwY7UT306A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrjedvgddufedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedftehlvgigrghnuggvrhcuvehlohhuthgvrhdfuceorghl vgigodhivghtfhestghorhgvmhgvmhdrtghomheqnecuggftrfgrthhtvghrnhepvdetje fhhefggeelueelfeetieekgfevhfehkeehvedvkeeufeekieeifffhvdegnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvgigodhivghtfh estghorhgvmhgvmhdrtghomh
X-ME-Proxy: <xmx:ETezY37a0w5bKAmfEidUQhk2ecYXkU0jNWA6c4C1mJs-YExirROXuA> <xmx:ETezY82njJsUNBnyMH4CW0sRv5U23G3jbjFc0a-E0ZLsWhJ-5r_OmQ> <xmx:ETezY6Fk5Uyx9zUmKiuh50Fn1KEdxYppuq8dMYjaWFuGeM74uccGaw> <xmx:ETezY-Sdg3-RVoorrr6IUsQrd5LXFveWXgoi-VP6elTCVfWr7mYPVw>
Feedback-ID: ie3614602:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id E11B32A20080; Mon, 2 Jan 2023 14:57:04 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.7.0-alpha0-1185-g841157300a-fm-20221208.002-g84115730
Mime-Version: 1.0
Message-Id: <3dbeb1b1-b8ab-4752-b768-65f1a8734754@app.fastmail.com>
In-Reply-To: <F8D81167-DEB1-4257-9DD2-D7F270B89E7F@deployingradius.com>
References: <BB2CA78D-4C7B-4A5D-A1D5-F09993636373@gmail.com> <747e85f4-71c5-4b45-aded-0bb73f1b334c@app.fastmail.com> <f184470f-6395-468a-a908-7c39dde7d363@app.fastmail.com> <F8D81167-DEB1-4257-9DD2-D7F270B89E7F@deployingradius.com>
Date: Mon, 02 Jan 2023 19:56:44 +0000
From: Alexander Clouter <alex+ietf@coremem.com>
To: radext@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/9qwakTlx0WnZtY0HKYowbc7tluA>
Subject: Re: [radext] draft-cullen-radextra-status-realm-00
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jan 2023 19:57:11 -0000

On Mon, 2 Jan 2023, at 19:00, Alan DeKok wrote:
>> 
>> Actually dwelling on it, probably best to scratch the timestamp as each system clock will be out of sync; we can just build tooling based on incrementing Max-Hop-Count (a la traceroute-esque).
>
>   What would work is a time delta.  i.e. "reply time - request time" at each stage.

I did think maybe on the outbound path proxies could add their timestamp and then on the inbound response include their timestamp there...that could work.

As a consequence you would also be able to pick out systems with hugely out of sync clocks too, though not sure of the practical use of this.

v2.34.0 | Report a Bug | By Email | System Status