Re: [radext] FW: New Version Notification for >>draft-xue-radext-key-management-00.txt
Qiong <bingxuere@gmail.com> Mon, 08 April 2013 01:12 UTC
Return-Path: <bingxuere@gmail.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 4586F21F902B for <radext@ietfa.amsl.com>; Sun, 7 Apr 2013 18:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.184
X-Spam-Level:
X-Spam-Status: No, score=-1.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 PilLXpClet0z for <radext@ietfa.amsl.com>; Sun, 7 Apr 2013 18:12:51 -0700 (PDT)
Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) by ietfa.amsl.com (Postfix) with ESMTP id 795DB21F9029 for <radext@ietf.org>; Sun, 7 Apr 2013 18:12:51 -0700 (PDT)
Received: by mail-vc0-f181.google.com with SMTP id ia10so656995vcb.12 for <radext@ietf.org>; Sun, 07 Apr 2013 18:12:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=yODqg/r0qWv+ZhPqvkX1yfv93IDnL1M7e3CY9h4DftA=; b=OQVCO4+Tnd8/LQdj8uAffN+k7VIykmmdnrUaGssNrBFSKUjGoE7AQoIsZs9LpRbC4A UUOONvPpIk5Lw5XxWwogljt/XdgEq7UaBqMMP/7uLPQjkeCJyOIsriGbpWSH78xfP3fH 8wdIQL6Z9HVANoDW2oPt45SnW0uhjSgx0UoKTYMVU7FthYdYA8Z6dzPDs9XdzGlm1aXU DYiG0iMPGe30FbsaQ0zMLyNa5sDJH4gZGsTT9ADjo4GipvlQlCmlW0BYla4cXbF7kFOW 2SFLx8thee1Yk8irAMhwBFI9/Nn5h9ewKLoyLS70SNe7cOeOfoahltqwRU2axLZJRWzh UULQ==
X-Received: by 10.58.96.40 with SMTP id dp8mr14376385veb.41.1365383570842; Sun, 07 Apr 2013 18:12:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.224.133 with HTTP; Sun, 7 Apr 2013 18:12:10 -0700 (PDT)
From: Qiong <bingxuere@gmail.com>
Date: Mon, 08 Apr 2013 09:12:10 +0800
Message-ID: <CAH3bfADDTvhgx4cX2yvjUTnQxpfiaA8Cw3A8cqWXkaJ1wb4Emw@mail.gmail.com>
To: hartmans@painless-security.com, radext@ietf.org, Xueli <xueli@huawei.com>
Content-Type: multipart/alternative; boundary="089e01229c8ab8f6ce04d9cf22d3"
Subject: Re: [radext] FW: New Version Notification for >>draft-xue-radext-key-management-00.txt
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: Mon, 08 Apr 2013 01:12:52 -0000
Hi Sam, We are deploying this use case in our network, where BRAS are doing unified user authentication for both broadband access user and WLAN users. This is for simple user management, authentication, etc. Hope it clarifies. >> >> Xueli> Actually, the issue is when the authenticator is in access >> Xueli> router instead of AC, the PMK should be announced to AC. >> >>What is the use case for putting the authenticator in the access router >>rather than an access point controller? Best wishes Qiong -- ============================================== Qiong Sun China Telecom Beijing Research Institude Open source code: lightweight 4over6: *http://sourceforge.net/projects/laft6/* PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/ * ===============================================