Re: [Softwires] I-D Action: draft-ietf-softwire-map-radius-03.txt
"Fuyu (Eleven)" <eleven.fuyu@huawei.com> Sat, 27 December 2014 06:58 UTC
Return-Path: <eleven.fuyu@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79B0B1A212A for <softwires@ietfa.amsl.com>; Fri, 26 Dec 2014 22:58:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 8rw6OG7STpx7 for <softwires@ietfa.amsl.com>; Fri, 26 Dec 2014 22:58:55 -0800 (PST)
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 9BE8C1A3B9B for <softwires@ietf.org>; Fri, 26 Dec 2014 22:58:54 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNJ10072; Sat, 27 Dec 2014 06:58:53 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 27 Dec 2014 06:58:52 +0000
Received: from NKGEML505-MBX.china.huawei.com ([169.254.1.204]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Sat, 27 Dec 2014 14:58:46 +0800
From: "Fuyu (Eleven)" <eleven.fuyu@huawei.com>
To: Ross Chandler <ross@eircom.net>
Thread-Topic: [Softwires] I-D Action: draft-ietf-softwire-map-radius-03.txt
Thread-Index: AQHQHihpJNifZgmbG0amxnPFyV+o5pyho7rg
Date: Sat, 27 Dec 2014 06:58:45 +0000
Message-ID: <EF6A204047BD994A860EE26D5F23BF5881554176@nkgeml505-mbx.china.huawei.com>
References: <45B77C58-E086-408E-AEB1-1D07EDAD8762@eircom.net>
In-Reply-To: <45B77C58-E086-408E-AEB1-1D07EDAD8762@eircom.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.25]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/t7AKXSlZVHu8kXuop6rjWn2AJTI
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-map-radius-03.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Dec 2014 06:58:56 -0000
Hi Ross， Thank you for your comments. In the existing operational practice, the User-name attribute can be filled by MAC address or interface-id or vlan id or all of them. It depends on the operational implementation by different vendor. So I think this sentence may be updated by " When BNG receives the SOLICIT, it SHOULD initiates radius Access-Request message, in which the User-Name attribute (1) MAY be filled by the MAP CE MAC address or interface-id or both". Thanks Cheers Yu -----Original Message----- From: Softwires [mailto:softwires-bounces@ietf.org] On Behalf Of Ross Chandler Sent: Tuesday, December 23, 2014 4:47 AM To: softwires@ietf.org Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-map-radius-03.txt Hello, Section 3 says “When BNG receives the SOLICIT, it SHOULD initiates radius Access-Request message, in which the User-Name attribute (1) SHOULD be filled by the MAP CE MAC address” Does this not conflict with the existing operational practise of inserting interface-id (e.g. DSLAM or PON line) in the User-Name attribute? BR Ross _______________________________________________ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires
- [Softwires] I-D Action: draft-ietf-softwire-map-r… internet-drafts
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Ross Chandler
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Fuyu (Eleven)
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Ross Chandler