IETF Logo Mail Archive

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

Alan DeKok <aland@deployingradius.com> Mon, 02 January 2023 19:00 UTC

Return-Path: <aland@deployingradius.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 F0D1BC14CE57 for <radext@ietfa.amsl.com>; Mon, 2 Jan 2023 11:00:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 dXHwr4r52OpJ for <radext@ietfa.amsl.com>; Mon, 2 Jan 2023 11:00:14 -0800 (PST)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (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 83C03C14CF0D for <radext@ietf.org>; Mon, 2 Jan 2023 11:00:13 -0800 (PST)
Received: from smtpclient.apple (135-23-95-173.cpe.pppoe.ca [135.23.95.173]) by mail.networkradius.com (Postfix) with ESMTPSA id 42504257; Mon, 2 Jan 2023 19:00:09 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <f184470f-6395-468a-a908-7c39dde7d363@app.fastmail.com>
Date: Mon, 02 Jan 2023 14:00:07 -0500
Cc: radext@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: Alexander Clouter <alex+ietf@coremem.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/-IhgIftyRRm-PmBpxFPS5ysTKWU>
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:00:19 -0000

On Jan 2, 2023, at 1:02 PM, Alexander Clouter <alex+ietf@coremem.com> wrote:
> 
> On Sun, 1 Jan 2023, at 17:53, Alexander Clouter wrote:
>> Finally I would love to see a timestamp (at least millisecond resolution) sub-attribute be packed into 'Server-Information' so we can find the slow hops and an optional 'retry' sub-attribute counter so we can discover the lossy hops.
> 
> 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.

  Alan DeKok.

v2.23.0 | Report a Bug | By Email