Re: [radext] Ben Campbell's Discuss on draft-ietf-radext-coa-proxy-05: (with DISCUSS and COMMENT)

Alan DeKok <aland@freeradius.org> Wed, 15 August 2018 15:24 UTC

Return-Path: <aland@freeradius.org>
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 1B88E130DDA; Wed, 15 Aug 2018 08:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Txg_qTzEw6_Y; Wed, 15 Aug 2018 08:24:24 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) by ietfa.amsl.com (Postfix) with ESMTP id 49708130DCD; Wed, 15 Aug 2018 08:24:24 -0700 (PDT)
Received: from [192.168.20.38] (CPEf4cc55220745-CM64777ddff610.cpe.net.cable.rogers.com [173.32.191.82]) by mail.networkradius.com (Postfix) with ESMTPSA id A228E2C6; Wed, 15 Aug 2018 15:24:22 +0000 (UTC)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_F2E1C6B8-2B04-41D9-83BA-9CF953AF4F0F"; protocol="application/pgp-signature"; micalg=pgp-sha256
X-Pgp-Agent: GPGMail
From: Alan DeKok <aland@freeradius.org>
In-Reply-To: <22938F82-F957-4356-AC12-5DECE2926260@nostrum.com>
Date: Wed, 15 Aug 2018 11:24:20 -0400
Cc: Winter Stefan <stefan.winter@restena.lu>, radext@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-radext-coa-proxy@ietf.org, radext-chairs@ietf.org
Message-Id: <92D694EE-B9AF-4DE9-85AF-78334E9CD8C8@freeradius.org>
References: <153430309790.27225.13672171828804687460.idtracker@ietfa.amsl.com> <4D83C0DB-8A53-408D-9CDE-D4B11D27DD30@freeradius.org> <22938F82-F957-4356-AC12-5DECE2926260@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/6jNpOYjJOqeGNkQtw-K82X9zZdY>
Subject: Re: [radext] Ben Campbell's Discuss on draft-ietf-radext-coa-proxy-05: (with DISCUSS and COMMENT)
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.27
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: Wed, 15 Aug 2018 15:24:26 -0000

On Aug 15, 2018, at 10:46 AM, Ben Campbell <ben@nostrum.com> wrote:
> Yes, but as you allude to below, this document depends on 5176. Given that it is an extension to 5176,  I’d say that it effectively incorporates 5176 by reference.

  Which means what?  That this document is really part of 5176, and that the caveats given in Section 1.1 should be applied, even though they don't apply to this document?

  I'm not sure I follow that logic.  "IF A then B" means that if A is false, then B is also false.

>> Can we have a standards track document which depends on an informational document?
> 
> There’s the problem. According to RFC 2026, we cannot. The IESG can make exceptions under specific circumstances (see RFCs 3967 and 4897). The point of my DISCUSS is to force discussion of whether it is appropriate to make an exception for this draft.

  We already have RFC 5080 (proposed standard) which updates RFC 2866 (informational).

  Even more strongly, RFC 5080 points out errors in both the spec *and* in implementations.

  Which means that RFC 5080 took the opposite decision of 5176.  It marked existing implementations as non-compliant.  The reasons for that decision are historical.

> My initial thoughts is that it is not appropriate to do so. This draft is a relatively small extension to 5176. It might be different if this draft incidentally depended on 5176, but in this case the informational RFC is the entire foundation of this draft.
> 
> If it’s important to make this draft standards track, then we should look into promoting 5176 to standards track.

  Along with RFC 2866 (RADIUS accounting), RFC 2867, RFC 2868, RC 5997, RFC 6613 (TCP transport), RFC 6614 (TLS transport), and RFC 7360 (DTLS transport).  And probably more.  All of those documents are informational.  There have been discussions over the years about making them all standards track.

  However, the sad truth is that the RADIUS WG is essentially dead at this point.  There is little interest in revisiting 20 year-old specs, just to have them promoted to standards track.  And even if they were made standards track, the consensus has been that little of the content would change.

  As for this document, the WG was in favour of making it standards track, and it had support from the previous AD.  Exceptions have been made in the past in similar circumstances.

  I'm arguing this point simply because I'm not convinced by the counter-arguments.

  Alan DeKok.