IETF Logo Mail Archive

Re: [Dime] RAR Message with possible ReAuth-Reqiest_type

Glen Zorn <glenzorn@gmail.com> Sat, 23 November 2013 08:27 UTC

Return-Path: <glenzorn@gmail.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3EA91AE0DF for <dime@ietfa.amsl.com>; Sat, 23 Nov 2013 00:27:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 Iz5SqBD4O7aC for <dime@ietfa.amsl.com>; Sat, 23 Nov 2013 00:27:04 -0800 (PST)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 05C671AE025 for <dime@ietf.org>; Sat, 23 Nov 2013 00:27:03 -0800 (PST)
Received: by mail-pb0-f53.google.com with SMTP id ma3so2455247pbc.26 for <dime@ietf.org>; Sat, 23 Nov 2013 00:26:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=YZZNKNXG9Px+v1otzjlpLQtMJNE8nKEoL2u1sPV3eUs=; b=IzcoOoejsdEf5gy/IncP54l5BFhuJqKl+udDllJqrPWEdu2e8FzPcZPLMVXO+wWjrj Zl08STbEq3LTWGkogsqkxLzvMzBXF5W3lmKu98Jbl2OPdNG7NgIe+/FwzzQp7NNR/JyD WcUlP/pH7WCVmzljFeqDNDS+pbKgzYT3vtAIgy1LvlPJsM4cTQpjljKSEo93UfIRH1OK FsF5NUSgu2Dc9q/p0nv3BZwDn/uG5p32OEB5O1XRe85qMZ32dr5IBvWbP0ckR+FQRoUW 071QGANkGYfeb2wa72jygEaFpno5fiP+4gKQonqpNbQCViNR5NcRFrQ3itDoZNom3MjL bGqg==
X-Received: by 10.66.102.66 with SMTP id fm2mr16405156pab.94.1385195216723; Sat, 23 Nov 2013 00:26:56 -0800 (PST)
Received: from [192.168.0.104] (ppp-171-96-88-15.revip8.asianet.co.th. [171.96.88.15]) by mx.google.com with ESMTPSA id oa3sm25356569pbb.15.2013.11.23.00.26.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 23 Nov 2013 00:26:56 -0800 (PST)
Message-ID: <529066CB.8050505@gmail.com>
Date: Sat, 23 Nov 2013 15:26:51 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Satyanarayana Danda (sdanda)" <sdanda@cisco.com>
References: <E06F3B652F60A4409C49D8E840BEEC921E46790E@xmb-rcd-x14.cisco.com>
In-Reply-To: <E06F3B652F60A4409C49D8E840BEEC921E46790E@xmb-rcd-x14.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "dime@ietf.org" <dime@ietf.org>
Subject: Re: [Dime] RAR Message with possible ReAuth-Reqiest_type
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Nov 2013 08:27:06 -0000

On 11/23/2013 03:06 PM, Satyanarayana Danda (sdanda) wrote:

> Hi folks,
>
> I am looking for a case where *Re-Auth-Request* is sent to NAS with
> subscriber credentials captured via web Portal (web-logon) case.
>
>  From RFC 6733, we do have two options set in *ReAuth-Request-Type* AVP
> of the action expected. From my use-case standpoint, I would like to inform
>
> NAS to take *AUTHENTICATE_ONLY* action by sending AA-Request for
> credential validation.
>
> Since this is not specified as part of this RFC, do you see this needs
> to be addressed?
>
> Please let me know in case you want more details on the use-case.

I would like more details.  In particular, why do you believe that 
authorization in unnecessary?

>
> Thanks
>
> Satya
>
>
>       <snip>
>
>
>       Re-Auth-Request-Type AVP
>
>
>
>     The Re-Auth-Request-Type AVP (AVP Code 285) is of type Enumerated and
>
>     is included in application-specific auth answers to inform the client
>
>     of the action expected upon expiration of the Authorization-Lifetime.
>
>
>
>     If the answer message contains an Authorization-Lifetime AVP with a
>
>     positive value, the Re-Auth-Request-Type AVP MUST be present in an
>
>     answer message.  The following values are defined:
>
>
>
>     AUTHORIZE_ONLY 0
>
>
>
>        An authorization only re-auth is expected upon expiration of the
>
>        Authorization-Lifetime.  This is the default value if the AVP is
>
>        not present in answer messages that include the Authorization-
>
>        Lifetime.
>
>
>
>     AUTHORIZE_AUTHENTICATE 1
>
>
>
>        An authentication and authorization re-auth is expected upon
>
>        expiration of the Authorization-Lifetime.
>
> </snip>
>
>
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime
>

v2.23.0 | Report a Bug | By Email