Re: [radext] #153: Section 2.8 Access-Info
Bernard Aboba <bernard_aboba@hotmail.com> Sun, 09 June 2013 14:30 UTC
Return-Path: <bernard_aboba@hotmail.com>
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 1C64821F9695 for <radext@ietfa.amsl.com>; Sun, 9 Jun 2013 07:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level:
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wkwfTkgiUQue for <radext@ietfa.amsl.com>; Sun, 9 Jun 2013 07:30:24 -0700 (PDT)
Received: from blu0-omc2-s14.blu0.hotmail.com (blu0-omc2-s14.blu0.hotmail.com [65.55.111.89]) by ietfa.amsl.com (Postfix) with ESMTP id F32E821F9344 for <radext@ietf.org>; Sun, 9 Jun 2013 07:30:23 -0700 (PDT)
Received: from BLU404-EAS231 ([65.55.111.71]) by blu0-omc2-s14.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 9 Jun 2013 07:30:23 -0700
X-TMN: [6Z0RwtMM/Ks9p3ZMnFOdTA/qtoQmwlgV]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU404-EAS231C316F9C8F0B313F78316939B0@phx.gbl>
Content-Type: multipart/related; boundary="_267cd97d-5178-4e70-9c97-c40880093970_"
References: <066.e99973544c7878635851fd28a6cf5689@trac.tools.ietf.org> <27657_1370418838_51AEEE96_27657_5798_1_6B7134B31289DC4FAF731D844122B36E1FB0BA@PEXCVZYM13.corporate.adroot.infra.ftgroup> <BLU169-W12706042E244DCC236F92B0939B0@phx.gbl> <28638_1370769510_51B44866_28638_19542_1_6B7134B31289DC4FAF731D844122B36E1FEC37@PEXCVZYM13.corporate.adroot.infra.ftgroup>
From: Bernard Aboba <bernard_aboba@hotmail.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <28638_1370769510_51B44866_28638_19542_1_6B7134B31289DC4FAF731D844122B36E1FEC37@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Date: Sun, 09 Jun 2013 07:30:21 -0700
To: "lionel.morand@orange.com" <lionel.morand@orange.com>
X-OriginalArrivalTime: 09 Jun 2013 14:30:23.0067 (UTC) FILETIME=[E039E2B0:01CE651D]
Cc: "radext@ietf.org" <radext@ietf.org>, "draft-ietf-radext-ieee802ext@tools.ietf.org" <draft-ietf-radext-ieee802ext@tools.ietf.org>
Subject: Re: [radext] #153: Section 2.8 Access-Info
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 09 Jun 2013 14:30:31 -0000
Unless anyone objects, I will remove it. On Jun 9, 2013, at 2:18 AM, lionel.morand@orange.com wrote: > I had the same concern. Not sure that this info in the Access-Challenge makes sense. > > Lionel > > De : Bernard Aboba [mailto:bernard_aboba@hotmail.com] > Envoyé : dimanche 9 juin 2013 02:52 > À : MORAND Lionel OLNC/OLN; radext@ietf.org; draft-ietf-radext-ieee802ext@tools.ietf.org > Objet : RE: [radext] #153: Section 2.8 Access-Info > > > Lionel said: > > > I'm not sure to understand this point. > > > > As per section 10.1 in 802.1X, the access status indication is consecutive to an authentication procedure in any case. > > So my assumption is that this status is valid for the duration of the session. If any change is required, you need to restart a session. > > Except if I have missed something... > > [BA] The document allows the Access-Info Attribute in an Access-Challenge packet. That doesn't seem compatible with "if any change is required you need to restart a session", because the value in an Access-Challenge could be different from that in an Access-Accept or Access-Reject. Does inclusion in an Access-Challenge really make sense? > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext
_______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext
- [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info Joseph Salowey (jsalowey)
- Re: [radext] #153: Section 2.8 Access-Info lionel.morand
- Re: [radext] #153: Section 2.8 Access-Info Bernard Aboba
- Re: [radext] #153: Section 2.8 Access-Info lionel.morand
- Re: [radext] #153: Section 2.8 Access-Info Bernard Aboba
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info Joseph Salowey (jsalowey)
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info Bernard Aboba
- Re: [radext] #153: Section 2.8 Access-Info Joseph Salowey (jsalowey)
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info Joseph Salowey (jsalowey)
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker