From diameter-admin@frascone.com Tue Jun 1 05:23:57 2004 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08690 for ; Tue, 1 Jun 2004 05:23:56 -0400 (EDT) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 4D3F020DB1 for ; Tue, 1 Jun 2004 05:10:57 -0400 (EDT) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 5680820D68 for ; Tue, 1 Jun 2004 05:06:34 -0400 (EDT) Date: Tue, 01 Jun 2004 05:06:34 -0400 Message-ID: <20040601090634.4991.96581.Mailman@xavier> Subject: frascone.com mailing list memberships reminder From: mailman-owner@wolverine.cnri.reston.va.us To: capwap-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: diameter-admin@frascone.com Errors-To: diameter-admin@frascone.com X-BeenThere: diameter@frascone.com X-Mailman-Version: 2.0.13 Precedence: bulk X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) This is a reminder, sent out once a month, about your frascone.com mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, capwap-request@frascone.com) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@wolverine. Thanks! Passwords for capwap-archive@lists.ietf.org: List Password // URL ---- -------- capwap@frascone.com xakour http://mail.frascone.com/mailman/options/capwap/capwap-archive%40lists.ietf.org From capwap-admin@frascone.com Tue Jun 1 14:29:18 2004 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04460 for ; Tue, 1 Jun 2004 14:29:17 -0400 (EDT) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id DDBC920993; Tue, 1 Jun 2004 14:16:05 -0400 (EDT) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id E741020902; Tue, 1 Jun 2004 14:16:02 -0400 (EDT) Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 8A67D20901 for ; Tue, 1 Jun 2004 14:15:25 -0400 (EDT) Received: from hermes.jf.intel.com (fmr05.intel.com [134.134.136.6]) by mail.frascone.com (Postfix) with ESMTP id 798F8202A2 for ; Tue, 1 Jun 2004 14:15:22 -0400 (EDT) Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7]) by hermes.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-outer.mc,v 1.15 2004/01/30 18:16:28 root Exp $) with ESMTP id i51ITawQ009229 for ; Tue, 1 Jun 2004 18:29:36 GMT Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by talaria.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-inner.mc,v 1.10 2004/03/01 19:21:36 root Exp $) with SMTP id i51INSEB016608 for ; Tue, 1 Jun 2004 18:24:47 GMT Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs041.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004060111281612956 for ; Tue, 01 Jun 2004 11:28:16 -0700 Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 1 Jun 2004 11:28:16 -0700 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C44806.339D0990" X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Message-ID: <2AF68A477DD44C4EBCBE338C24E7A9EE5C43E2@orsmsx408> Thread-Topic: CAPWAP DT teleconference minutes (05/27/04) Thread-Index: AcRET3CjHjuoyq2gSfKPOB8zv0XqJQDtqVGA From: "Yang, Lily L" To: "Capwap (E-mail)" X-OriginalArrivalTime: 01 Jun 2004 18:28:16.0656 (UTC) FILETIME=[34D47900:01C44806] X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] CAPWAP DT teleconference minutes (05/27/04) Sender: capwap-admin@frascone.com Errors-To: capwap-admin@frascone.com X-BeenThere: capwap@frascone.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: A list for CAPWAP technical discussions List-Unsubscribe: , List-Archive: Date: Tue, 1 Jun 2004 11:28:14 -0700 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) This is a multi-part message in MIME format. ------_=_NextPart_001_01C44806.339D0990 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable May 27, 2004 8-9am PST Attendees (8): Lily, Petros, Emek, Victor, Partha, Inderpreet, Jim, = Peyush The objective of this teleconference was to formulate a working plan to = revise the CAPWAP Taxonomy Draft to v03 in the next few weeks. = Potentially this could be the version that the DT asks for the WG last = call on. The two main work items for v03 are: 1) Address comments received on v02 so far, including comments from = IEEE CAPWAP Ad Hoc Committee (AHC) and others made via IETF CAPWAP = mailing list. 2) Solicit more input from mesh vendors to help us revise the = Distributed Architecture section better than what we currently have, but = it is expected that the Distributed Architecture Section would not = treated as thoroughly as the Centralized Architecture Section.=20 Plan to work on item #1 is: 1) Use the spread sheet from IEEE to collect and track other = comments. Add new columns to the spread sheet so that resolutions or = clarification/feedback can be documented as well. 2) A primary owner is designated from the DT for each comment so = that he/she can take responsibility to understand the issue, clarify = with the comment provider if necessary, and provide recommendation to = the DT and WG on how to address the comment. When in doubt, the owner = should always bring up the issue with the DT and WG in general for = discussion. 3) The DT and WG would be given a chance to go over the = recommendations before the final resolutions are accepted and = incorporated into the draft. Plan to work on item #2 is to first encourage and collect more input = from mesh vendors on the topic in the next 1-2 weeks. Some vendors = already agreed (verbally and informally) to do that. Schedule for v03: need to be discussed by the DT, co-chairs, and the WG. In this conference, we also went over some of the more significant = comments from IEEE Ad Hoc Committee: 1) Comments were made that we need to better describe the = functional interface between AC and WTP in each architecture. The = problem is that we don't have enough raw data to do that, given the fact = that each vendor implements that interface with its proprietary = technology. However, this problem underlines the need for open standard. = It is agreed that we should explicitly state the proprietary nature of = such interface in the reality and the difficulty of describing it in = details. 2) Comments were made that real-time or non-real-time is not well = defined anywhere, which is true. We should state the reality clearly and = honestly. 3) Comments were made about how much advantages and disadvantages = should be pointed out for each architecture variant. The group feels = that Taxonomy document should stay clear of subjective judgments, but = analysis of the technical implications of each architecture is within = the realm of this document. 4) Comments were made regarding the WME/11e entry in the matrix - = it is not clear what the entry tries to address -- whether it should be = what (WME or 11e or both) gets implemented or where (AC or WTP or both) = it gets implemented. The group aggress that it should be the later, not = the former, and if necessary, contributing vendors should be contacted = to clarify this and gather new data for this. 5) Security section: questions were raised whether we should have = more detailed security section. However, it is agreed that we can only = go as far as the vendor input allow us to go. So Inderpreet agrees to = take another look at the vendor inputs for security considerations. 6) Comments were also made regarding the distributed architecture = section and mesh, esp. current development in IEEE .11s group (ESS = Mesh). We agree to expand a bit more on that section, but also = acknowledge the difficulty without enough vendor input. 7) Question was raised regarding Section 4.7 and its relevance to = the document. The group feels that it is indeed important and maybe just = some clarification is needed. WE didn't have enough time to discuss the schedule, so we agree to take = this to the DT mailing list first and get a sense from the DT on when we = can accomplish work item #1 and #2. I will do that separately. Thanks, Lily ------_=_NextPart_001_01C44806.339D0990 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable CAPWAP DT teleconference minutes (05/27/04)

May 27, = 2004 8-9am=20 PST

Attendees (8): Lily, Petros, Emek, Victor, = Partha,=20 Inderpreet, Jim, Peyush

The = objective of=20 this teleconference was to formulate a working plan to revise the CAPWAP Taxonomy = Draft to=20 v03 in the next few weeks. Potentially=20 this could be the=20 version that the DT asks for the WG last=20 call on. The two = main work = items for v03=20 are:

1)      Address comments received on v02 so far, including comments = from=20 IEEE CAPWAP Ad Hoc=20 Committee (AHC) and others made via IETF = CAPWAP mailing=20 list.

2)      Solicit=20 more input from mesh vendors to help us revise the Distributed Architecture section better than = what we=20 currently have, but it is expected = that the=20 Distributed = Architecture Section would = not = treated as=20 thoroughly as the Centralized Architecture Section.

Plan to = work on item #1=20 is:

1)      Use = the spread sheet=20 from IEEE to collect and track other comments. Add new columns to the = spread=20 sheet so that resolutions or clarification/feedback can be documented as = well.

2)      A = primary owner is=20 designated from the DT for each = comment so that=20 he/she can take responsibility to understand the issue, clarify with the = comment=20 provider if necessary, and provide recommendation to the DT and=20 WG on how to address the comment. When in=20 doubt, the owner should always bring up the issue with the DT and WG in general=20 for discussion.

3)      The = DT and WG would=20 be given a chance to go over the recommendations = before the = final=20 resolutions are accepted and incorporated into the = draft.

Plan to = work on item #2=20 is to first encourage and collect more input from mesh vendors on the=20 topic in the next 1-2 weeks. Some = vendors already=20 agreed (verbally and informally) to do that.

Schedule for v03: need to be discussed by the DT, = co-chairs, and=20 the WG.

In this = conference, we=20 also went = over some of the more significant comments from=20 IEEE Ad Hoc Committee:

1)      Comments were=20 made that we need to=20 better describe the functional interface = between AC and=20 WTP in each architecture.=20 The problem is that we = don’t = have enough raw=20 data to do that, given the fact that each vendor implements that = interface with=20 its proprietary technology. However,=20 this problem underlines the need for = open=20 standard. It is agreed that we=20 should explicitly state the proprietary nature of such = interface in=20 the reality and the difficulty of describing it in = details.

2)      Comments=20 were made that real-time or non-real-time is not well defined=20 anywhere, which is true. We should state the reality clearly and = honestly.

3)      Comments were=20 made about how much advantages and = disadvantages=20 should be pointed out for each architecture variant. The = group feels that=20 Taxonomy document should stay clear = of=20 subjective judgments, but analysis of the = technical=20 implications of each=20 architecture is within the realm of this=20 document.

4)      Comments=20 were made regarding the=20 WME/11e entry in the = matrix – it is not clear what the entry tries to = address -- whether it should be what (WME or 11e or both) = gets implemented = or where (AC or=20 WTP or both) it gets implemented. The group aggress that it should = be the later,=20 not the former, and if necessary, contributing vendors should be = contacted to=20 clarify this and gather new data for this.

5)      Security section:=20 questions were raised whether we should have more detailed security = section.=20 However, it is agreed that we can only go as far as the vendor input = allow us to=20 go. So Inderpreet agrees to take another look at the vendor inputs for = security=20 considerations.

6)      Comments=20 were also made regarding the distributed architecture section and mesh, esp. current development in IEEE = .11s group (ESS=20 Mesh). We agree to = expand a bit more=20 on that section, but also acknowledge the difficulty without enough = vendor=20 input.

7)      Question was raised=20 regarding Section 4.7 and its relevance to the document. The group feels that it is indeed important = and maybe just some=20 clarification is needed.

WE=20 didn’t have enough time to discuss the schedule, so we agree to take = this to=20 the DT mailing list first and get a sense from the DT on when we can = accomplish=20 work item #1 and #2. I=20 will do that = separately.

Thanks,

Lily

------_=_NextPart_001_01C44806.339D0990-- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Wed Jun 2 09:54:07 2004 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22188 for ; Wed, 2 Jun 2004 09:54:07 -0400 (EDT) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 6EDB720C1A; Wed, 2 Jun 2004 09:41:05 -0400 (EDT) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 5601520C1B; Wed, 2 Jun 2004 09:41:02 -0400 (EDT) Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 8627E20C1B for ; Wed, 2 Jun 2004 09:40:13 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mail.frascone.com (Postfix) with ESMTP id A0AF920C1A for ; Wed, 2 Jun 2004 09:40:11 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22154; Wed, 2 Jun 2004 09:53:10 -0400 (EDT) Message-Id: <200406021353.JAA22154@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: capwap@frascone.com From: Internet-Drafts@ietf.org X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] I-D ACTION:draft-ietf-capwap-problem-statement-01.txt Sender: capwap-admin@frascone.com Errors-To: capwap-admin@frascone.com X-BeenThere: capwap@frascone.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: A list for CAPWAP technical discussions List-Unsubscribe: , List-Archive: Date: Wed, 02 Jun 2004 09:53:10 -0400 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Control And Provisioning of Wireless Access Points Working Group of the IETF. Title : CAPWAP Problem Statement Author(s) : P. Calhoun, et al. Filename : draft-ietf-capwap-problem-statement-01.txt Pages : 9 Date : 2004-6-1 This document describes the Configuration and Provisioning for Wireless Access Points (CAPWAP) problem statement. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-capwap-problem-statement-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-capwap-problem-statement-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-capwap-problem-statement-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-6-2100802.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-capwap-problem-statement-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-capwap-problem-statement-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-6-2100802.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Thu Jun 17 16:59:31 2004 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15463 for ; Thu, 17 Jun 2004 16:59:30 -0400 (EDT) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 5756F20FC5; Thu, 17 Jun 2004 16:46:06 -0400 (EDT) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 7E1B420FC9; Thu, 17 Jun 2004 16:46:02 -0400 (EDT) Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id D497E20FC9 for ; Thu, 17 Jun 2004 16:45:54 -0400 (EDT) Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56]) by mail.frascone.com (Postfix) with ESMTP id 0560520FC5 for ; Thu, 17 Jun 2004 16:45:53 -0400 (EDT) Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59]) by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i5HKxEN11839; Thu, 17 Jun 2004 16:59:15 -0400 (EDT) Received: from nortelnetworks.com (admin500.ca.nortel.com [47.129.42.72]) by zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NALS96CY; Thu, 17 Jun 2004 16:59:15 -0400 Message-ID: <40D20620.9000500@nortelnetworks.com> X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Kue Wong User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: capwap@frascone.com Cc: kdick@nortelnetworks.com Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Taxonomy Survey Response: Nortel Networks WMN Sender: capwap-admin@frascone.com Errors-To: capwap-admin@frascone.com X-BeenThere: capwap@frascone.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: A list for CAPWAP technical discussions List-Unsubscribe: , List-Archive: Date: Thu, 17 Jun 2004 16:59:12 -0400 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 8bit Following survey response posted to capwap list on behalf of Kevin Dick by Kue Wong. --------------------------------------------------------------------------- Kevin Dick [kdick@nortelnetworks.com] taxonomy responses for Nortel Networks Wireless Mesh Networks (WMN) product ======> CAPWAP Survey Responses (1) Design considerations & requirements: please briefly describe your design principles for this architecture. Response: The design principles for Nortel’s Wireless Mesh Network product are as follows: - enables WLAN deployment and simplified coverage for open areas both indoor and outdoor, - brings “hotspots” together into a Community Area Network (CAN) providing larger coverage area and mobility, - eliminates the need for extensive Ethernet cabling or leased lines through use of wireless links between access points in a mesh configuration, - provides auto-configuration and centralized management capabilities to simplify network operations, - avoids service outages by providing efficient routing using auto-discovery and self-healing algorithms, - provides a highly secure environment for both end users and the network, - scaleable architecture from small enterprise to a large community network, - compliant to existing 802.11 standard protocols and interfaces to ensure universal 802.11 client access, - conformance to FCC requirements on 802.11 indoor and outdoor deployment. (2) WLAN functions supported: Please list the functions supported in this WLAN briefly, but please do not send us the entire data sheet. Examples of WLAN functions includes the STA services, Distributed System Services (as defined by 802.11), radio resource management and control, AP load balancing, mobility support, WLAN network wide security functions (including authentication, encryption for privacy and integrity, etc.) and any others not listed here but deemed important in your design. Response: Supported WLAN functions are: - the STA services open system authentication WPA with TTLS and PEAP support web portal redirect deauthentication - the Distribution System Services (as defined by 802.11) association disassociation distribution and integration services reassociation - mobility support Session persistent Corporate VPN access - WLAN network wide security functions (authentication, encryption for privacy and integrity etc.) fully WPA compliant (3) The functional architecture to implement the functions described above: whether it is by autonomous AP architecture, or "split" architecture. For split architecture, please provide the functional mapping of WLAN functions onto the AP and AC -- with just enough details that help us understand the kinds of functional interface necessary between the two. For distributed architectures, describe how the functionality is distributed across the nodes in the network. Response: - fully autonomous AP architecture (4) The protocol used in between AP and AC, for split architecture; or the protocol used between mesh nodes, for distributed architecture. Response: - does not apply (5) The topological assumptions between AP and AC (is it directly connected, L2 switched, or L3 routed?) -- this also helps us to understand the deployment scenarios. Response: - does not apply (6) Security threat analysis: what kinds of threat introduced by the split architecture, and how that are addressed. Response: - does not apply (7) Pros and Cons of this architecture, esp. in relation to the four problems described in the CAPWAP problem statement. Please keep the analysis at technical instead of marketing level. When referring to the four problems described in CAPWAP, the pros and cons design considerations are as follows: CAPWAP Problem Statement#1: The first problem introduced by large WLAN deployments is that each AP is an IP-addressable device requiring management, monitoring, and control. Response: The advantage of Nortel's architecture over legacy IP network infrastructure deployment is avoiding global IP addressing. This is supported by Intranet and Extranet private IP addressing across system components and users access through the DHCP server. This eliminates the need for global IP addressing for system administration. CAPWAP Problem Statement#2: A second problem introduced by large WLAN deployments is distributing and maintaining a consistent configuration throughout the entire set of access points in the WLAN. Access point configuration consists of both long-term static information, such as addressing and hardware settings, and more dynamic provisioning information, such as individual WLAN settings and security parameters. Large WLAN installations that need to update dyanmic provisioning information in all the APs in the WLAN require a prolonged phase-over time, while each AP is updated and the WLAN does not have a single, consistent, configuration. Response: The basic design requirement is to support in-service upgrade with downloadable configuration capabilities. CAPWAP Problem Statement#3: A third problem introduced by large WLAN deployments is the difficulty in dealing effectively with the dynamic nature of the WLAN medium, itself. Due to the shared nature of the wireless medium, shared with APs in the same WLAN, with APs in other WLANs, and with devices that are not APs at all, parameters controlling the wireless medium on each AP must be monitored frequently and modified in a coordinated fashion to maximize performance for the WLAN to utilize the wireless medium efficiently. This must be coordinated among all the access points, to minimize the interference of one access point with its neighbors. Manually monitoring these metrics and determining a new, optimum configuration for the parameters related to the wireless medium is a task that takes a significant amount of time and effort. Response: Nortel's implementation includes automated configuration and centralized management capabilities to simplify network operations. In addition auto-discovery and self-healing algorithms are used. CAPWAP Problem Statement#4: A fourth problem introduced by large WLAN deployments is securing access to the network and preventing installation of unauthorized access points. Access points are often difficult to physically secure, since their location must often be outside of a locked network closet or server room. Theft of an access point, with its embedded secrets, allows the thief to obtain access to the resources secured by those secrets. Recently, multiple vendors have begun offering proprietary solutions Calhoun, et al. Response: Nortel's solution provides a highly secure environment for both end users and the network including safe-guards against access and misuse of embedded information. Mechanisms include WPA-equivalent authorization, key management, automatic key refresh and encryption to protect user, control and management data. Techniques are embedded in the auto-discovery algorithm to prevent rogue AP intrusions to the NW. _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Wed Jun 30 15:29:50 2004 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09128 for ; Wed, 30 Jun 2004 15:29:50 -0400 (EDT) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id B2098210A4; Wed, 30 Jun 2004 15:16:05 -0400 (EDT) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 4812420492; Wed, 30 Jun 2004 15:16:02 -0400 (EDT) Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 327DD20492 for ; Wed, 30 Jun 2004 15:15:51 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mail.frascone.com (Postfix) with ESMTP id F11AB1FEE8 for ; Wed, 30 Jun 2004 15:15:48 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09093; Wed, 30 Jun 2004 15:29:30 -0400 (EDT) Message-Id: <200406301929.PAA09093@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: capwap@frascone.com From: Internet-Drafts@ietf.org X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] I-D ACTION:draft-ietf-capwap-arch-03.txt Sender: capwap-admin@frascone.com Errors-To: capwap-admin@frascone.com X-BeenThere: capwap@frascone.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: A list for CAPWAP technical discussions List-Unsubscribe: , List-Archive: Date: Wed, 30 Jun 2004 15:29:30 -0400 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Control And Provisioning of Wireless Access Points Working Group of the IETF. Title : Architecture Taxonomy for Control and Provisioning of Wireless Access Points(CAPWAP) Author(s) : L. Yang, et al. Filename : draft-ietf-capwap-arch-03.txt Pages : 96 Date : 2004-6-30 This document provides a taxonomy of the architectures employed in the existing IEEE 802.11 products in the market, by analyzing WLAN (Wireless LAN) functions and services and describing the different variants in distributing these functions and services among the architectural entities. This taxonomy may be utilized by the IEEE 802.11 Working Group as input to their task of defining the Access Point (AP) functional architecture. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-capwap-arch-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-capwap-arch-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-capwap-arch-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-6-30152357.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-capwap-arch-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-capwap-arch-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-6-30152357.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Wed Jun 30 17:08:50 2004 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19791 for ; Wed, 30 Jun 2004 17:08:49 -0400 (EDT) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 3A699210B1; Wed, 30 Jun 2004 16:55:05 -0400 (EDT) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 6D82220B06; Wed, 30 Jun 2004 16:55:02 -0400 (EDT) Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 6818120B06 for ; Wed, 30 Jun 2004 16:54:28 -0400 (EDT) Received: from orsfmr001.jf.intel.com (fmr12.intel.com [134.134.136.15]) by mail.frascone.com (Postfix) with ESMTP id 99B5220AFD for ; Wed, 30 Jun 2004 16:54:26 -0400 (EDT) Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7]) by orsfmr001.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-outer.mc,v 1.15 2004/01/30 18:16:28 root Exp $) with ESMTP id i5UE89Yh013652 for ; Wed, 30 Jun 2004 14:08:23 GMT Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by talaria.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-inner.mc,v 1.10 2004/03/01 19:21:36 root Exp $) with SMTP id i5UL26Pd012677 for ; Wed, 30 Jun 2004 21:02:31 GMT Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56]) by orsmsxvs041.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004063014074730958 for ; Wed, 30 Jun 2004 14:07:47 -0700 Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 30 Jun 2004 14:07:46 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Capwap] I-D ACTION:draft-ietf-capwap-arch-03.txt Message-ID: <2AF68A477DD44C4EBCBE338C24E7A9EE01616819@orsmsx408> Thread-Topic: [Capwap] I-D ACTION:draft-ietf-capwap-arch-03.txt Thread-Index: AcRe2KiREGof7amkTw2B3qvwXg8WhgADVcBQ From: "Yang, Lily L" To: X-OriginalArrivalTime: 30 Jun 2004 21:07:46.0929 (UTC) FILETIME=[4B22FE10:01C45EE6] X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Sender: capwap-admin@frascone.com Errors-To: capwap-admin@frascone.com X-BeenThere: capwap@frascone.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: A list for CAPWAP technical discussions List-Unsubscribe: , List-Archive: Date: Wed, 30 Jun 2004 14:07:44 -0700 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable I sent out an email with change log earlier in the week but didn't see it show up on this mailing list. So here it is again (excuse me if you do see duplicate): --------------------------------- Here is the v03 of CAPWAP Architecture Taxonomy. There are no fundamental or significant changes from v02 to v03. Most changes are minor, of either clarification or editorial nature: 1) Incorporated comments from IEEE 802.11 review committee. The detailed comments and resolutions can be found in the attach excel spread sheet (soon will be posted to www.capwap.org). 2) Received and incorporated two more architecture submissions (from Janusys Networks and Nortel, both on mesh networks), revised section 5 (distributed mesh architecture) accordingly. 3) Incorporated comments received from CAPWAP mailing list and privately made by other IETF reviewers.=20 =20 We would like to request the WG co-chairs to call for WG last call soon, before the Aug IETF meeting. So please review the document and provide feedback promptly. =20 Thanks for all who contributed to this effort! =20 Lily (DT editor) -----Original Message----- From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On Behalf Of Internet-Drafts@ietf.org Sent: Wednesday, June 30, 2004 12:30 PM To: i-d-announce@ietf.org Cc: capwap@frascone.com Subject: [Capwap] I-D ACTION:draft-ietf-capwap-arch-03.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Control And Provisioning of Wireless Access Points Working Group of the IETF. Title : Architecture Taxonomy for Control and Provisioning=20 of Wireless Access Points(CAPWAP) Author(s) : L. Yang, et al. Filename : draft-ietf-capwap-arch-03.txt Pages : 96 Date : 2004-6-30 =09 This document provides a taxonomy of the architectures employed in the existing IEEE 802.11 products in the market, by analyzing WLAN (Wireless LAN) functions and services and describing the different variants in distributing these functions and services among the architectural entities. This taxonomy may be utilized by the IEEE 802.11 Working Group as input to their task of defining the Access Point (AP) functional architecture. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-capwap-arch-03.txt To remove yourself from the I-D Announcement list, send a message to=20 i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. =20 You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20 to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-capwap-arch-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html=20 or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-capwap-arch-03.txt". =09 NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. =09 =09 Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Wed Jun 30 17:37:49 2004 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22081 for ; Wed, 30 Jun 2004 17:37:48 -0400 (EDT) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 9987A20459; Wed, 30 Jun 2004 17:24:05 -0400 (EDT) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 4AD24209BD; Wed, 30 Jun 2004 17:24:02 -0400 (EDT) Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id EBB15209BD for ; Wed, 30 Jun 2004 17:23:30 -0400 (EDT) Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26]) by mail.frascone.com (Postfix) with ESMTP id 921FA20459 for ; Wed, 30 Jun 2004 17:23:28 -0400 (EDT) Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i5ULbB204475; Thu, 1 Jul 2004 00:37:11 +0300 (EET DST) X-Scanned: Thu, 1 Jul 2004 00:36:46 +0300 Nokia Message Protector V1.3.31 2004060815 - RELEASE Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i5ULakcX024405; Thu, 1 Jul 2004 00:36:46 +0300 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks003.ntc.nokia.com 00117gF8; Thu, 01 Jul 2004 00:36:45 EEST Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com [10.241.35.121]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i5ULaiH07619; Thu, 1 Jul 2004 00:36:44 +0300 (EET DST) Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 30 Jun 2004 16:35:55 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: Thread-Topic: CAPWAP Architecture Taxonomy draft 03 available for WG review Thread-Index: AcRe6jir9jmEX148QyeWeDZu4k7Whw== From: To: Cc: , , , X-OriginalArrivalTime: 30 Jun 2004 21:35:55.0915 (UTC) FILETIME=[39D9CDB0:01C45EEA] X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] CAPWAP Architecture Taxonomy draft 03 available for WG review Sender: capwap-admin@frascone.com Errors-To: capwap-admin@frascone.com X-BeenThere: capwap@frascone.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: A list for CAPWAP technical discussions List-Unsubscribe: , List-Archive: Date: Wed, 30 Jun 2004 14:35:54 -0700 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Hi All- There is a new version of the architecture taxonomy draft, = draft-ietf-capwap-arch-03.txt, is available for WG review. Please = submit your review comments and suggestions to the mailing list by = Wednesday, July 7th. This short review is necessary to keep in line = with the CAPWAP milestones. We are targeting a WG last call for this = draft before the IETF meeting in August.=20 The draft can be found at: = http://www.ietf.org/internet-drafts/draft-ietf-capwap-arch-03.txt Thanks to the CAPWAP design team for incorporating the IEEE and WG list = comments.=20 Regards, Dorothy and Mani _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap