Re: [radext] Adoption call for draft-hartman-radext-bigger-packets

Peter Deacon <peterd@iea-software.com> Mon, 24 March 2014 17:09 UTC

Return-Path: <peterd@iea-software.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35FA51A0254 for <radext@ietfa.amsl.com>; Mon, 24 Mar 2014 10:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 X4h-0TozY4Ke for <radext@ietfa.amsl.com>; Mon, 24 Mar 2014 10:09:11 -0700 (PDT)
Received: from aspen.internal.iea-software.com (remote.iea-software.com [70.89.142.196]) by ietfa.amsl.com (Postfix) with ESMTP id D5B3A1A024C for <radext@ietf.org>; Mon, 24 Mar 2014 10:09:10 -0700 (PDT)
Received: from SMURF.peterd.ws (unverified [10.0.3.195]) by aspen.internal.iea-software.com (Rockliffe SMTPRA 7.0.6) with ESMTP id <B0005923908@aspen.internal.iea-software.com>; Mon, 24 Mar 2014 10:09:09 -0700
Date: Mon, 24 Mar 2014 10:09:25 -0700 (Pacific Daylight Time)
From: Peter Deacon <peterd@iea-software.com>
To: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <53306157.7060309@deployingradius.com>
Message-ID: <alpine.WNT.2.11.1403240955120.12912@SMURF>
References: <907DC0B0-6E00-4179-BE37-17C89810A9EC@gmail.com> <alpine.WNT.2.11.1403240855250.12912@SMURF> <53306157.7060309@deployingradius.com>
User-Agent: Alpine 2.11 (WNT 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/xiow94HCp7DrwQyZjH55NdlteHk
Cc: "radext@ietf.org" <radext@ietf.org>, Jouni Korhonen <jouni.nospam@gmail.com>, "radext-chairs@tools.ietf.org" <radext-chairs@tools.ietf.org>
Subject: Re: [radext] Adoption call for draft-hartman-radext-bigger-packets
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 24 Mar 2014 17:09:13 -0000

On Mon, 24 Mar 2014, Alan DeKok wrote:

> Peter Deacon wrote:
>> I do not support adoption at this time.  Seeing value in continuing to
>> support UDP/DTLS no bridge is available for CoA and Accounting.  Noting
>> also did not support rational in Alex's draft for ignoring this issue
>> for reasons explained in detail earlier on this list.

>  That is unnecessary, for reasons explained in detail earlier on this list.

There is no defined mechanism for coalescing accounting sessions. 
Multi-Session-Id is inter-session rather than intra-session.

Binding CoA to authorization is not something we can support seeing value 
in maintaining autonomy to manage admitted sessions separately from 
authorization.

>> If systems are to start transmitting more than max size I prefer a less
>> permissive environment where some indication of support is required up
>> front prior to transmitting larger messages.  It can be a manual setting
>> or an automatic "discovery" yet would prefer something "MUST" be indicated.

>  The draft discusses negotiation of large packets, which seems to 
> address the above concerns.

A list of optional procedures are defined.  What I don't see is where it 
says one of them must be followed or an implementation must not assume 
support for larger packets.

regards,
Peter