[Capwap] 答复: Capwap Digest, Vol 54, Issue 2
"rishyang@gmail.com" <rishyang@gmail.com> Thu, 17 March 2011 13:29 UTC
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B39F3A695E for <ietfarch-capwap-archive@core3.amsl.com>; Thu, 17 Mar 2011 06:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.947
X-Spam-Level:
X-Spam-Status: No, score=-0.947 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_32=0.6, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gqGmAbmAt8yc for <ietfarch-capwap-archive@core3.amsl.com>; Thu, 17 Mar 2011 06:29:33 -0700 (PDT)
Received: from lists.out.tigertech.net (lists.out.tigertech.net [74.114.88.30]) by core3.amsl.com (Postfix) with ESMTP id 43B093A67FA for <capwap-archive@lists.ietf.org>; Thu, 17 Mar 2011 06:29:33 -0700 (PDT)
Received: from zoidberg.tigertech.net (localhost [127.0.0.1]) by zoidberg.tigertech.net (Postfix) with ESMTP id 6D29AEDC046 for <capwap-archive@lists.ietf.org>; Thu, 17 Mar 2011 06:31:01 -0700 (PDT)
Received: from mx4.tigertech.net (mx4.tigertech.net [74.114.88.34]) by lists.tigertech.net (Postfix) with ESMTP id BC527E24105 for <capwap@lists.tigertech.net>; Thu, 17 Mar 2011 06:30:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.tigertech.net (Postfix) with ESMTP id B78ADE47204 for <capwap@frascone.com>; Thu, 17 Mar 2011 06:30:54 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hypnotoad.tigertech.net
Received: from mx4.tigertech.net (localhost [127.0.0.1]) by mx4.tigertech.net (Postfix) with ESMTP id 0E5B7E47202 for <capwap@frascone.com>; Thu, 17 Mar 2011 06:30:54 -0700 (PDT)
X-TigerTech-Content-Filter: Whitelisted
X-TigerTech-Spam-Status: Level 0 (High) (P0); Whitelisted TTSSA (rishyang@gmail.com whitelisted)
Received: from mail-wy0-f173.google.com (mail-wy0-f173.google.com [74.125.82.173]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx4.tigertech.net (Postfix) with ESMTPS for <capwap@frascone.com>; Thu, 17 Mar 2011 06:30:53 -0700 (PDT)
Received: by wyb42 with SMTP id 42so2777654wyb.32 for <capwap@frascone.com>; Thu, 17 Mar 2011 06:30:52 -0700 (PDT)
Received: by 10.216.230.153 with SMTP id j25mr907753weq.22.1300368651999; Thu, 17 Mar 2011 06:30:51 -0700 (PDT)
Received: from lhrnms-0055-fe.pr.nmsg.s.nokia.com (em1x-48.lhr.messaging.nokia.com [131.228.18.48]) by mx.google.com with ESMTPS id u9sm656465wbg.17.2011.03.17.06.30.49 (version=SSLv3 cipher=OTHER); Thu, 17 Mar 2011 06:30:50 -0700 (PDT)
Message-ID: <4d820d0a.8937e30a.7e03.33b5@mx.google.com>
Date: Thu, 17 Mar 2011 13:27:39 +0000
From: "rishyang@gmail.com" <rishyang@gmail.com>
To: "capwap@frascone.com" <capwap@frascone.com>
MIME-Version: 1.0
X-Priority: 3
Subject: [Capwap] 答复: Capwap Digest, Vol 54, Issue 2
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: rishyang@gmail.com
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Post: <mailto:capwap@frascone.com>
X-Tigertech-Mailman-Hint: 636170776170
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=subscribe>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com
从我的诺基亚手机发送 -----原始邮件----- 自:capwap-request@frascone.com 发送时间: 2011/03/17 18:17:01 至:capwap@frascone.com 主题: Capwap Digest, Vol 54, Issue 2 Send Capwap mailing list submissions to capwap@frascone.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.frascone.com/mailman/listinfo/capwap or, via email, send a message with subject or body 'help' to capwap-request@frascone.com You can reach the person managing the list at capwap-owner@frascone.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Capwap digest..." Today's Topics: 1. Re: Capwap Digest, Vol 54, Issue 1 (Yong Zhang) ---------------------------------------------------------------------- Message: 1 Date: Wed, 16 Mar 2011 07:38:28 -0700 From: Yong Zhang <yozhang@gmail.com> Subject: Re: [Capwap] Capwap Digest, Vol 54, Issue 1 To: capwap@frascone.com Cc: capwap-request@frascone.com Message-ID: <AANLkTikNnBZrrwZSmRWE8DF2wvc+Q1CLsQsFv+uxRpL7@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi, Liu, I have had same question before. The answer I got from Pat was that you only can put one add/del/update WLAN ME in one WLAN config request message. Although this was not written in the spec, you had better not make your wlan config messages too complicated. Your AC can send them, but other vendors' WTP maybe can not decode them correctly. Yong On Wed, Mar 16, 2011 at 3:17 AM, <capwap-request@frascone.com> wrote: > Send Capwap mailing list submissions to > ? ? ? ?capwap@frascone.com > > To subscribe or unsubscribe via the World Wide Web, visit > ? ? ? ?http://lists.frascone.com/mailman/listinfo/capwap > or, via email, send a message with subject or body 'help' to > ? ? ? ?capwap-request@frascone.com > > You can reach the person managing the list at > ? ? ? ?capwap-owner@frascone.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Capwap digest..." > > > Today's Topics: > > ? 1. How many massage elements in one "wlan configuration ? ? ?request > ? ? ?" ? (liusong8080) > ? 2. How many Add(or del/update) WLAN massage elements in ONE > ? ? ?"wlan configuration request " ? (liusong8080) > ? 3. Re: How many Add(or del/update) WLAN massage elements in ONE > ? ? ?"wlan configuration request " ? (Kiran Ashokan) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 16 Mar 2011 17:37:29 +0800 > From: liusong8080 <liusong8080@gmail.com> > Subject: [Capwap] How many massage elements in one "wlan configuration > ? ? ? ?request " ? > To: Capwap@frascone.com > Message-ID: > ? ? ? ?<AANLkTimHCY2ACUAw-mHdM_HaG4BJsftzF4WmtgigQc2T@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > > ? I got a uncertain ?question in rfc5416.txt about the number of > massage elements in one ?"wlan configuration request ". > > ? In the rfc5416.txt described like this: > ? For instance, a WTP that is capable of supporting up to 16 Service > Set Identifiers > ? (SSIDs), could accept up to 16 IEEE 802.11 WLAN Configuration Request > ? messages that include the Add WLAN message element. > > ? My question is how many Add(or del/update) WLAN massage elements > in ONE "wlan configuration request " ? > > > Good luck! > Your LiuSong > IN XI'AN city of China. > > > ------------------------------ > > Message: 2 > Date: Wed, 16 Mar 2011 17:47:10 +0800 > From: liusong8080 <liusong8080@gmail.com> > Subject: [Capwap] How many Add(or del/update) WLAN massage elements in > ? ? ? ?ONE "wlan configuration request " ? > To: Capwap@frascone.com > Message-ID: > ? ? ? ?<AANLkTikaF0RW0FnE1bT=22g9QRJptw1UE+uo3H3i71f9@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > > ? I got a uncertain ?question in rfc5416.txt about the number of > massage elements in one ?"wlan configuration request ". > > ? In the rfc5416.txt described like this: > > ? "For instance, a WTP that is capable of supporting up to 16 Service > Set Identifiers > ? (SSIDs), could accept up to 16 IEEE 802.11 WLAN Configuration Request > ? messages that include the Add WLAN message element. " > > ? My question is how many Add(or del/update) WLAN massage elements > in ONE "wlan configuration request " ? > > Good luck! > Your LiuSong > IN XI'AN city of China. > > > ------------------------------ > > Message: 3 > Date: Wed, 16 Mar 2011 15:35:30 +0530 > From: Kiran Ashokan <kiran.ashokan@gmail.com> > Subject: Re: [Capwap] How many Add(or del/update) WLAN massage > ? ? ? ?elements in ONE "wlan configuration request " ? > To: liusong8080 <liusong8080@gmail.com> > Cc: Capwap@frascone.com > Message-ID: > ? ? ? ?<AANLkTimeEdgENPRtFn9FHWbE88Rsfg7jXEt-a=ZWNQbR@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Liu, > > You could use multiple "Add WLAN" in a single "WLAN Configuration Request" > The Radio ID/WLAN ID field could be used to differentiate each of the > Service Set Identifier that you would be looking for. > > Hope this helps. > > - Kiran > > > On 16 March 2011 15:17, liusong8080 <liusong8080@gmail.com> wrote: > >> Hi, >> >> ? I got a uncertain ?question in rfc5416.txt about the number of >> massage elements in one ?"wlan configuration request ". >> >> ? In the rfc5416.txt described like this: >> >> ? "For instance, a WTP that is capable of supporting up to 16 Service >> Set Identifiers >> ? (SSIDs), could accept up to 16 IEEE 802.11 WLAN Configuration Request >> ? messages that include the Add WLAN message element. " >> >> ? My question is how many Add(or del/update) WLAN massage elements >> in ONE "wlan configuration request " ? >> >> Good luck! >> Your LiuSong >> IN XI'AN city of China. >> _________________________________________________________________ >> To unsubscribe or modify your subscription options, please visit: >> http://lists.frascone.com/mailman/listinfo/capwap >> >> Archives: http://lists.frascone.com/pipermail/capwap >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://lists.frascone.com/pipermail/capwap/attachments/20110316/1c4be781/attachment.htm > > ------------------------------ > > _________________________________________________________________ > To unsubscribe or modify your subscription options, please visit: > http://lists.frascone.com/mailman/listinfo/capwap > > Archives: http://lists.frascone.com/pipermail/capwap > > End of Capwap Digest, Vol 54, Issue 1 > ************************************* > ------------------------------ _________________________________________________________________ To unsubscribe or modify your subscription options, please visit: http://lists.frascone.com/mailman/listinfo/capwap Archives: http://lists.frascone.com/pipermail/capwap End of Capwap Digest, Vol 54, Issue 2 ************************************* _________________________________________________________________ To unsubscribe or modify your subscription options, please visit: http://lists.frascone.com/mailman/listinfo/capwap Archives: http://lists.frascone.com/pipermail/capwap
- [Capwap] 答复: Capwap Digest, Vol 54, Issue 2 rishyang@gmail.com