IETF Logo Mail Archive

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

Alexander Clouter <alex+ietf@coremem.com> Mon, 02 January 2023 18:02 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 F374AC1524BD for <radext@ietfa.amsl.com>; Mon, 2 Jan 2023 10:02:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 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, HTML_MESSAGE=0.001, 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=nPZfgGmN; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=mPF0dEsH
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 aBoaw174W8MY for <radext@ietfa.amsl.com>; Mon, 2 Jan 2023 10:02:48 -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 AD4F5C1524BC for <radext@ietf.org>; Mon, 2 Jan 2023 10:02:48 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 60CCD32002E2 for <radext@ietf.org>; Mon, 2 Jan 2023 13:02:47 -0500 (EST)
Received: from imap46 ([10.202.2.96]) by compute5.internal (MEProxy); Mon, 02 Jan 2023 13:02:47 -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=1672682566; x=1672768966; bh=pQOpabM9yp KKkRrGcKmuLl9tDku3b6i74irqo1VDpNw=; b=nPZfgGmN4qHA8H/QpdCgFPbp3M 6UsopRqkTwJWd/qZcTqkt9Y2hcwPZYqENgCVlEOSnr0RHtbkDSZNtEU14WKaZgJh 8RTykhNk4I2IX6RfH7eJ+5WcXvDoHFpRody9dgYaeZBJ/XOeqDiHELCFc02hk1Iw mb1tGpMc6YoTWcnBTwRvztkz5QX6lWZbq6t6yIi8jpWe6Cyi0OsccdHpN8ciL4Yo 8bt2w9eCSm6GqgZrzNrZPMowgJpaUhz9exBQYCAPriSby+D0HFgDQhIlxBOz/lPt pSb4gh3N3YgUeLGsN4wFSlxyD0tCRowdbPDruvslgwiItbIwrQiOfz1Pdq0Q==
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=1672682566; x=1672768966; bh=pQOpabM9ypKKkRrGcKmuLl9tDku3 b6i74irqo1VDpNw=; b=mPF0dEsHAv4FB1Pt2wH5pdX47SVlF985axg1uEUYUa6t 0yIR/l6ABqADC8TsMnElPu7J5BZc6FkioYrygyXqx7CrJRgar3uSNS9rjbNR0Oub VEzCTDG6v5bLeygm3iU7ctVo6MbOZmUz5mDHKLca2dOTYdV5yENrVUI0szhC2znU Tr1B8lSg/bvWRAMCm0a3z7+siwbdZRriKmoDIoSelDLmEznZrXRwxNRHcBoQZRJU AAAchqKLaOKKbEeQlzmMoUfuBy4N7WFevNadNkr1J/dcB2nTHLXD4+venB9BxqXc RkzH06R6mbqVsliIxypuD/nkxS9GwyAN8XPJVDGu5Q==
X-ME-Sender: <xms:RhyzY6jTHam3M0CnOs5EUUyYqbBZWenqIJu8fRfH-DcuMYV8zH-WnA> <xme:RhyzY7AqsuRzFI0emxMNhKU8d1sUQim6jYr9a0n7IY6ryKUyA7nQour_H_kqNOsHh -Dd1X5MZaSleSaaRw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrjedvgdduuddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedftehlvgigrghnuggvrhcuvehlohhuthgvrhdfuceorghl vgigodhivghtfhestghorhgvmhgvmhdrtghomheqnecuggftrfgrthhtvghrnhepheekhe duveeggeevueffgfejudfhteejtdeuffefieeffeevffeuffekieevvedvnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvgigodhivghtfh estghorhgvmhgvmhdrtghomh
X-ME-Proxy: <xmx:RhyzYyGl1mPpYsuFmbr5zieFkQYWI8xZhtk_TvCG46S5bSN68_Kr-w> <xmx:RhyzYzRhD3hq0KyXQEG81ptOMvsk0HIRc7xCvbyTMtvAqT179bhleQ> <xmx:RhyzY3zfFOB6RA1_6pK_yURbqSAuJK4hGszQiKrTHI_DTTwzThEAzA> <xmx:RhyzY28L5s4sefv6KDxCpl2oNrfKaWhNhaemC_4aiA62Mzc4DrEn3w>
Feedback-ID: ie3614602:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id AB06A2A20080; Mon, 2 Jan 2023 13:02:46 -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: <f184470f-6395-468a-a908-7c39dde7d363@app.fastmail.com>
In-Reply-To: <747e85f4-71c5-4b45-aded-0bb73f1b334c@app.fastmail.com>
References: <BB2CA78D-4C7B-4A5D-A1D5-F09993636373@gmail.com> <747e85f4-71c5-4b45-aded-0bb73f1b334c@app.fastmail.com>
Date: Mon, 02 Jan 2023 18:02:26 +0000
From: Alexander Clouter <alex+ietf@coremem.com>
To: radext@ietf.org
Content-Type: multipart/alternative; boundary="3c85c353f8644dd6a27250346d149fc4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/uMyu1VJDJhTaab2RoEQyetXNZjQ>
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 18:02:54 -0000

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).

Thanks

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