IETF Logo Mail Archive

Re: [radext] #178 (radius-fragmentation): fragments going in both directions - allowed or not?

"radext issue tracker" <trac+radext@trac.tools.ietf.org> Tue, 30 September 2014 06:47 UTC

Return-Path: <trac+radext@trac.tools.ietf.org>
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 4F0761A0235 for <radext@ietfa.amsl.com>; Mon, 29 Sep 2014 23:47:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level:
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] 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 A2SFqtPNpo8D for <radext@ietfa.amsl.com>; Mon, 29 Sep 2014 23:47:42 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25BEC1A0231 for <radext@ietf.org>; Mon, 29 Sep 2014 23:47:42 -0700 (PDT)
Received: from localhost ([::1]:35889 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+radext@trac.tools.ietf.org>) id 1XYrDc-0001AC-Ex; Mon, 29 Sep 2014 23:47:28 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: radext issue tracker <trac+radext@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-radext-radius-fragmentation@tools.ietf.org, alex@um.es, stefan.winter@restena.lu
X-Trac-Project: radext
Date: Tue, 30 Sep 2014 06:47:28 -0000
X-URL: http://tools.ietf.org/radext/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/178#comment:3
Message-ID: <080.8a14d2da60a156e795e3cedd77d089a2@trac.tools.ietf.org>
References: <065.3a956fa45a00049e711dbe6a5fb8d6c9@trac.tools.ietf.org>
X-Trac-Ticket-ID: 178
In-Reply-To: <065.3a956fa45a00049e711dbe6a5fb8d6c9@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-fragmentation@tools.ietf.org, alex@um.es, stefan.winter@restena.lu, radext@ietf.org
X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: aland@networkradius.com, alex@um.es, diego@tid.es, gabilm@um.es, pereniguez@um.es
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/vnoqph-1NnW3XXOzsrdSeMIc4cA
Cc: radext@ietf.org
Subject: Re: [radext] #178 (radius-fragmentation): fragments going in both directions - allowed or not?
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: radext@ietf.org
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: Tue, 30 Sep 2014 06:47:43 -0000

#178: fragments going in both directions - allowed or not?


Comment (by alex@um.es):

 I've changed that paragraph to:
 * Indicate that the exchange of authorization data is not mandatory
 * Add the word MAY to reflect that
 * Add a sentence explicitly forbidding the "other" direction

 [...]
 We can distinguish two phases, which can be omitted if there is no
 authorization data to be sent:

    1.  Pre-authorization.  In this phase, the NAS MAY send a large packet
 with authorization information to the AS before the end user is
 authenticated.  Only the NAS is allowed to send authorization data during
 this phase.

    2.  Post-authorization.  In this phase, the AS MAY send a large packet
 with authorization data to the NAS after the end user has been
 authenticated.  Only the AS is allowed to send authorization data during
 this phase.
 [...]

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |       Owner:  draft-ietf-radext-
  stefan.winter@restena.lu           |  radius-fragmentation@tools.ietf.org
     Type:  defect                   |      Status:  new
 Priority:  major                    |   Milestone:
Component:  radius-fragmentation     |     Version:
 Severity:  Waiting for Shepherd     |  Resolution:
  Writeup                            |
 Keywords:                           |
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/178#comment:3>
radext <http://tools.ietf.org/radext/>

v2.23.0 | Report a Bug | By Email