Re: [radext] Gathering opinions on draft-xue-radext-key-management

Xueli <xueli@huawei.com> Wed, 09 July 2014 02:12 UTC

Return-Path: <xueli@huawei.com>
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 26F6D1A0202 for <radext@ietfa.amsl.com>; Tue, 8 Jul 2014 19:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 KR0dR-DrvEjf for <radext@ietfa.amsl.com>; Tue, 8 Jul 2014 19:12:12 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B65C11A0294 for <radext@ietf.org>; Tue, 8 Jul 2014 19:12:11 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJT67296; Wed, 09 Jul 2014 02:12:09 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 9 Jul 2014 03:12:08 +0100
Received: from NKGEML504-MBX.china.huawei.com ([169.254.7.247]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Wed, 9 Jul 2014 10:12:03 +0800
From: Xueli <xueli@huawei.com>
To: Sam Hartman <hartmans@painless-security.com>
Thread-Topic: [radext] Gathering opinions on draft-xue-radext-key-management
Thread-Index: Ac+aU1q4YvahpQSJTAKpJucCQYvthQAURi7UAB2J9sA=
Date: Wed, 9 Jul 2014 02:12:02 +0000
Message-ID: <01FE63842C181246BBE4CF183BD159B448FD331C@nkgeml504-mbx.china.huawei.com>
References: <01FE63842C181246BBE4CF183BD159B448FD2EA1@nkgeml504-mbx.china.huawei.com> <tslvbr85aa0.fsf@mit.edu>
In-Reply-To: <tslvbr85aa0.fsf@mit.edu>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.97.86]
Content-Type: multipart/alternative; boundary="_000_01FE63842C181246BBE4CF183BD159B448FD331Cnkgeml504mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/TU937xaiV-5_IgumaospOumPN0c
Cc: "radext@ietf.org" <radext@ietf.org>, Jouni Korhonen <jouni.nospam@gmail.com>, Stefan Winter <stefan.winter@restena.lu>
Subject: Re: [radext] Gathering opinions on draft-xue-radext-key-management
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: Wed, 09 Jul 2014 02:12:14 -0000

Hi Sam



I appreciate it.. Make sense to me..

Thanks

Regards

Li



>I would request that you:

>

>* Approach this as an architectural issue at the RFC 5247 level rather

>  than a RADIUS issue

>

>* Focus on clearly describing the scenario and having a discussion with

>  the IETF community about whether this scenario is reasonable.

>

>* Discuss with the IETF community about whether a solution to this

>  scenario is desirable.

>

>This is a much bigger change than one RADIUS attribute.

>