IETF Logo Mail Archive

Re: [radext] Review of draft-ietf-radext-bigger-packets-02.txt

Alejandro Perez Mendez <alex@um.es> Thu, 26 February 2015 18:13 UTC

Return-Path: <alex@um.es>
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 569521AC3A0 for <radext@ietfa.amsl.com>; Thu, 26 Feb 2015 10:13:36 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 pQ9n4DPEKqpl for <radext@ietfa.amsl.com>; Thu, 26 Feb 2015 10:13:35 -0800 (PST)
Received: from xenon22.um.es (xenon22.um.es [155.54.212.162]) by ietfa.amsl.com (Postfix) with ESMTP id C8C061AC398 for <radext@ietf.org>; Thu, 26 Feb 2015 10:13:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by xenon22.um.es (Postfix) with ESMTP id BBC4243CB; Thu, 26 Feb 2015 19:13:31 +0100 (CET)
X-Virus-Scanned: by antispam in UMU at xenon22.um.es
Received: from xenon22.um.es ([127.0.0.1]) by localhost (xenon22.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id BSNRgp5xkGvg; Thu, 26 Feb 2015 19:13:31 +0100 (CET)
Received: from [10.42.0.179] (84.121.18.25.dyn.user.ono.com [84.121.18.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: alex) by xenon22.um.es (Postfix) with ESMTPSA id 62165B0F; Thu, 26 Feb 2015 19:13:29 +0100 (CET)
Message-ID: <54EF6249.1010600@um.es>
Date: Thu, 26 Feb 2015 19:13:29 +0100
From: Alejandro Perez Mendez <alex@um.es>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Sam Hartman <hartmans@painless-security.com>
References: <54EF26A3.6040502@um.es> <CFC9B8C6-3DF9-4A77-9EBD-DB72A75F2EA0@deployingradius.com> <54EF5F97.1060905@um.es> <tslegpc7djd.fsf@mit.edu>
In-Reply-To: <tslegpc7djd.fsf@mit.edu>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/radext/RXUQCZcCI69bu5Tc5Hg8Qt1cUGw>
Cc: "radext@ietf.org" <radext@ietf.org>, Alan DeKok <aland@deployingradius.com>
Subject: Re: [radext] Review of draft-ietf-radext-bigger-packets-02.txt
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: Thu, 26 Feb 2015 18:13:36 -0000

El 26/02/15 a las 19:06, Sam Hartman escribió:
>>>>>> "Alejandro" == Alejandro Perez Mendez <alex@um.es> writes:
>      Alejandro> Hi Alan,
>
>      Alejandro> thanks for the explanation. It is now clear. It serves to
>      Alejandro> build a unique key in the form of (ID,
>      Alejandro> Original-Packet-Code) which is used by the Client to
>      Alejandro> match it with the corresponding request, as ID by itself
>      Alejandro> cannot do it (is the Client allowed to create parallel
>      Alejandro> Access-Requests and Accounting-Requests with the same
>      Alejandro> ID?)
>
>  From my edit buffer:
>
>        <t>A Protocol-Error packet MUST contain a Original-Packet-Code
>        attribute,
>        along with an Error-Cause attribute.  Other attributes MAY be
>        included if desired.  The Original-Packet-Code contains the code
>        from the reque\
>        st that generated the protocol error so that clients can
>        disambiguate requests \
>        with different codes and the same ID.
>
> Is that sufficient?

It is for me.

v2.23.0 | Report a Bug | By Email