From diameter-admin@frascone.com Sat Jan 1 05:14:45 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05278 for ; Sat, 1 Jan 2005 05:14:45 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 0E9D820494 for ; Sat, 1 Jan 2005 05:14:46 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id B01A620475 for ; Sat, 1 Jan 2005 05:13:22 -0500 (EST) Date: Sat, 01 Jan 2005 05:13:22 -0500 Message-ID: <20050101101322.12683.15977.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 Mon Jan 10 11:32:13 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02371 for ; Mon, 10 Jan 2005 11:32:12 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 2E3CD20277; Mon, 10 Jan 2005 11:32:11 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 8601920260; Mon, 10 Jan 2005 11:32:04 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 759E81FD62 for ; Mon, 10 Jan 2005 11:31:55 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id 487321FCD6 for ; Mon, 10 Jan 2005 11:31:52 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0AB0S5e012194 for ; Mon, 10 Jan 2005 19:00:28 +0800 (SGT) Message-Id: <200501101100.j0AB0S5e012194@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT3A/rUkxvX690fSDWp5WXp36FMAA== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Additions #8 - Trust Model Definition 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: Mon, 10 Jan 2005 19:03:15 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Additions #8 - Trust Model Definition Context: Centralized WTP Management - Introduction (Section 8.3) - Objective Details (Section 8.3.1) - Motivation and Protocol Benefits (Section 8.3.2) - Relation to Problem Statement (Section 8.3.3) - Customer Requirements (Section 8.3.4) Issue: These sub-sections were left blank in v00. Proposed changes: Add text for the sub-sections. The following are proposed; -> Section 8.3 - Introduction Proposed text: Replace current notes with following introduction "The location of the 802.1x authenticator in the centralized WLAN framework raises a number of issues. For example, if the authenticator in 802.11i is relocated from WTP to WLAN controller any potential changes in the trust relationship between WTP and the network infrastructure need to be clarified. If there are changes, the new trust model needs to be defined." ----XXXX---- -> Section 8.3.1 - Objective Details (Left blank in v00) Proposed text: "According to the IEEE 802.11i specifications, the IEEE 802.1X authenticator's role is fixed at the WTP identified by the BSSID. In the centralized WLAN framework however, the IEEE 802.1X authenticator may be relocated to either a centralized WLAN controller or to an alternative entity. So the trust relationship of IEEE 802.11i may be altered with respect to a wireless client. In particular, the entity deciding the BSSID field of a MAC frame will have implications on the authenticator. Such possible changes with regard to the trust relationship need to be studied in relation to the CAPWAP protocol." ----XXXX---- -> Section 8.3.2 - Motivation and Protocol Benefits (Left blank in v00) Proposed text: "Given the fundamental nature of IEEE 802.1X authentication, this objective looks to clarify the possible implications of the centralized WLAN framework on authentication operations. Furthermore, the CAPWAP protocol will benefit from a trusted relationship between authentication entities." ----XXXX---- -> Section 8.3.3 - Relation to Problem Statement (Left blank in v00) Proposed text: Add following new paragraph "This objective is a security consideration relating to changes in IEEE 802.1X authenticator role from traditional deployments to one in the centralized WLAN framework." ----XXXX---- -> Section 8.3.4 - Customer Requirements (Left blank in v00) Proposed text: Add following new paragraph "Since a number of deployments are continually evolving with respect to the IEEE 802.11i security extensions, the trust relationship between authentication entities need to be consistently maintained across both legacy and centralized WLAN architectures. Customers who are in such transition need to be assured that the CAPWAP protocol operates in the context of a trusted relationship. It is for reason that this analysis be made with regard to the location of the authenticator." ----XXXX---- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:32:30 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02400 for ; Mon, 10 Jan 2005 11:32:29 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id E2E0320298; Mon, 10 Jan 2005 11:32:27 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 022C61FD62; Mon, 10 Jan 2005 11:32:11 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 4C2651FD62 for ; Mon, 10 Jan 2005 11:31:57 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id 2423B1FD61 for ; Mon, 10 Jan 2005 11:31:54 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0AAuWJr012099 for ; Mon, 10 Jan 2005 18:56:32 +0800 (SGT) Message-Id: <200501101056.j0AAuWJr012099@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT3A24JFjaVwQfPQlm2htALcXWwHA== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Additions #7 - Centralized WTP Management 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: Mon, 10 Jan 2005 18:59:19 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Additions #7 - Centralized WTP Management Context: Centralized WTP Management - Introduction (Section 7.2) - Objective Details (Section 7.2.1) - Motivation and Protocol Benefits (Section 7.2.2) - Relation to Problem Statement (Section 7.2.3) - Customer Requirements (Section 7.2.4) Issue: These sub-sections were left blank in v00. Proposed changes: Add text for the sub-sections. The following are proposed; -> Section 7.2 - Introduction Proposed text: Add the following paragraph "Large WLAN systems consist of a centralized CAPWAP segment and the wireless medium segment. WTPs, their WLAN controller and the switched or routed network between them constitute the CAPWAP segment. Wireless clients and the air interface constitute the wireless medium segment. This objective deals with system-wide security particularly with those threats arising from the wireless medium segment." ----XXXX---- -> Section 7.2.1 - Objective Details (Left blank in v00) Proposed text: "The emphasis of this objective is on the security threats external to the centralized CAPWAP segment of a WLAN system. The focus is therefore on rogue wireless clients and other illegitimate wireless interferences. There are a number of specific external threats that need to be addressed within the CAPWAP framework. i. PMK Sharing One aspect of this objective relates to recent discussions on PMK sharing in the centralized CAPWAP framework. This objective highlights the need to prevent exploitation of this ambiguity by rogue wireless clients. It is to ensure that there ambiguities arising from the CAPWAP framework are not cause for security breaches. [TBD] Additional external security threats" ----XXXX---- -> Section 7.2.2 - Motivation and Protocol Benefits (Left blank in v00) Proposed text: Add following new paragraph "The external threat to centralized CAPWAP segments becomes increasingly crucial given the low cost of wireless clients. Since it is relatively inexpensive for rogue individuals to mount attacks, it is important that WLAN systems are protected against them. Adequate mechanisms to thwart such external threats will be of tremendous benefit to the WLAN systems controlled and managed by the CAPWAP protocol." ----XXXX---- -> Section 7.2.3 - Relation to Problem Statement (Left blank in v00) Proposed text: Add following new paragraph "This objective is based on the security needs highlighted in the Problem Statement. Specifically, the Problem Statement discusses the effects of the shared wireless medium. This represents the external aspects of the CAPWAP framework from which certain threats can arise. The system-wide security objective addresses such threats in relation to the Problem Statement." ----XXXX---- -> Section 7.2.4 - Customer Requirements (Left blank in v00) Proposed text: Add following new paragraph "As in the CAPWAP Protocol Security objective (7.1), system-wide security aims to strengthen confidence in those deploying large scale WLANs. Realizing this objective will further assure service providers and enterprises that their wireless investment includes adequate protection against various rogue elements." ----XXXX---- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:32:46 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02424 for ; Mon, 10 Jan 2005 11:32:45 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 8B86D1FDF3; Mon, 10 Jan 2005 11:32:43 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 3B75F1FCD6; Mon, 10 Jan 2005 11:32:21 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 255D51FD62 for ; Mon, 10 Jan 2005 11:31:59 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id 03F7B1FCD6 for ; Mon, 10 Jan 2005 11:31:56 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0AAmATD011934 for ; Mon, 10 Jan 2005 18:48:10 +0800 (SGT) Message-Id: <200501101048.j0AAmATD011934@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT3AkMN4ksLHgIvSjWqhgmL3gA1Nw== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Additions #6 - CAPWAP Protocol Security 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: Mon, 10 Jan 2005 18:50:57 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Additions #6 - CAPWAP Protocol Security Context: Centralized WTP Management - Introduction (Section 7.1) - Motivation and Protocol Benefits (Section 7.1.2) - Relation to Problem Statement (Section 7.1.3) - Customer Requirements (Section 7.1.4) Issue: These sub-sections were left blank in v00. Proposed changes: Add text for the sub-sections. The following are proposed; -> Section 7.1 - Introduction Current text: "This objective addresses the security of the protocol." Proposed text: Add new sentences at the end of current introduction "This objective addresses the security of the CAPWAP protocol. Broadly, it addresses the security between WTPs and the WLAN controller. As such, it deals with the threats arising from within the network infrastructure." ----XXXX---- -> Section 7.1.2 - Motivation and Protocol Benefits (Left blank in v00) Proposed text: Add following new paragraphs "Security in itself is beneficial to the protocol. However, it becomes even more crucial in the context of WLAN usage. Since wireless networks are being applied to critical areas of business and enterprise operations, WLAN security takes on added importance. This is why protocol security must be made integral to WLAN control and management. Furthermore, communication networks are at increasing risks due to both physical and logical threats. A secure protocol will ensure that such threats do not adversely affect network operations and performance." ----XXXX---- -> Section 7.1.3 - Relation to Problem Statement (Left blank in v00) Proposed text: Add following new paragraph "The CAPWAP Problem Statement identifies a number of security issues for large scale WLANs. In particular, this objective relates to the threats of rogue WTPs, integrity of protocol exchanges and minimization of system breaches. Protocol security therefore closely follows from the Problem Statement." ----XXXX---- -> Section 7.1.4 - Customer Requirements (Left blank in v00) Proposed text: Add following new paragraph "Customers who deploy WLAN solutions need to be confident of their networks. They need to be assured that their networks address integrity, privacy and reliability. The ultimate users can then in turn be assured that their operations and applications are protected from major security threats. The protocol security objective is therefore of immense importance to WLAN customers." ----XXXX---- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:32:55 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02454 for ; Mon, 10 Jan 2005 11:32:54 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id DD1D41FD61; Mon, 10 Jan 2005 11:32:55 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 96CC6202AA; Mon, 10 Jan 2005 11:32:30 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 25D651FE41 for ; Mon, 10 Jan 2005 11:32:01 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id CB58F1FD61 for ; Mon, 10 Jan 2005 11:31:58 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0AAi1CI011843 for ; Mon, 10 Jan 2005 18:44:01 +0800 (SGT) Message-Id: <200501101044.j0AAi1CI011843@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT3Aa5kuhQYN01jTzCmJCnY8/ktsg== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Additions #5 - Centralized WTP Management 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: Mon, 10 Jan 2005 18:46:48 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Additions #5 - Centralized WTP Management Context: Centralized WTP Management - Introduction (Section 6.5) - Objective Details (Section 6.5.1) - Motivation and Protocol Benefits (Section 6.5.2) - Relation to Problem Statement (Section 6.5.3) - Customer Requirements (Section 6.5.4) Issue: These sub-sections were left blank in v00. Proposed changes: Add text for the sub-sections. The following are proposed; -> Section 6.5 - Introduction Current text: "Large scale WLAN deployments necessitate in centralized control. The CAPWAP protocol interfaces the central control to the numerous WTPs. One aspect of centralized control includes firmware distribution. This objective relates to configuration aspects of the WLAN ." Proposed text: Replace text above with following introduction; "Large scale WLAN deployments necessitate in centralized control to simplify WTP management relating to configuration, firmware distribution, operational parameters and monitoring. The CAPWAP protocol enables the exchange of corresponding control management information as it interfaces the central control to the numerous WTPs." ----XXXX---- -> Section 6.5.1 - Objective Details (Left blank in v00) Proposed text: "This objective deals with the management of WTPs with regard to the following; i. WTP firmware distribution Large WLAN deployments require all constituent WTPs to be enabled with the same firmware within a given operational period The CAPWAP protocol must be capable of determining the appropriate firmware version and ensuring consistency in this version among all WTPs. For example, CAPWAP can include mechanisms to exchange firmware version information between a centralized WLAN controller and its numerous WTPs. ii. WTP operational parameter provisioning Similarly, WTP operational parameters may be provisioned using the CAPWAP protocol. iii. WLAN monitoring WLAN monitoring allows network administrators to check system activity and performance. The CAPWAP protocol can be used to convey such operational information from various WTPs and deliver it to the corresponding WLAN controller." ----XXXX---- -> Section 6.5.2 - Motivation and Protocol Benefits (Left blank in v00) Proposed text: Add following new paragraph "This objective relates to configuration aspects of WLANs. The CAPWAP protocol deals with configuration by enabling the distribution of relevant information throughout the entire WLAN" ----XXXX---- -> Section 6.5.3 - Relation to Problem Statement (Left blank in v00) Proposed text: Add following new paragraph "This objective relates to the problems discussing configuration aspects of large-scale WLANs." ----XXXX---- -> Section 6.5.4 - Customer Requirements (Left blank in v00) Proposed text: Add following new paragraph "Enterprises and service providers demand simplicity and accuracy in the deployment of large scale WLANs. This is expected of all aspects of the deployment including WTP configuration and WLAN monitoring. The [I-D.ietf-capwap-problem-statement] details that the near-sameness of configuration from one WTP to another leads to misconfigurations. This objective will help minimize such errors and in doing so it helps simplify WLAN deployment and operation." ----XXXX---- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:33:21 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02521 for ; Mon, 10 Jan 2005 11:33:21 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id C5631202C8; Mon, 10 Jan 2005 11:33:21 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 8277720466; Mon, 10 Jan 2005 11:33:09 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 54B8820270 for ; Mon, 10 Jan 2005 11:32:07 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id 860521FD61 for ; Mon, 10 Jan 2005 11:32:02 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0AAIO9W011289 for ; Mon, 10 Jan 2005 18:18:24 +0800 (SGT) Message-Id: <200501101018.j0AAIO9W011289@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT2/hoymLOMNyCBSWeIcDq8BPbu0Q== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Additions #3 - Support for Traffic Separation 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: Mon, 10 Jan 2005 18:21:11 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Additions #3 - Support for Traffic Separation Context: Support for Traffic Separation - Objective Details (Section 6.3.1) - Relation to Problem Statement (Section 6.3.3) - Customer Requirements (Section 6.3.4) Issue: These sub-sections were left blank in v00. Proposed change: Add text for the three sub-sections. The following are proposed; Section 6.3.1 - Objective Details Current text: "It is the aim of CAPWAP to simplify the control and management of large scale WLANs. One way of achieving this is to separate control and data aspects within the protocol. This will allow solutions for control and data exchanges to be independently optimized." Proposed text: Add new sentence at end of paragraph "It is the aim of CAPWAP to simplify the control and management of large scale WLANs. One way of achieving this is to separate control and data aspects within the protocol. This will allow solutions for control and data exchanges to be independently optimized. Such flexibility is important for realizing extensible, long-term control mechanisms for wireless networks." ----XXXX---- Section 6.3.3 - Relation to Problem Statement Current text: "Broadly, this objective relates to the challenge of managing complexity in large scale WLANs." Proposed text: Add new sentence at end of paragraph "Broadly, this objective relates to the challenge of managing complexity in large scale WLANs. Traffic separation helps to simplify the CAPWAP solution space and consequently reduces complexity of managing large WLANs." ----XXXX---- Section 6.3.4 - Customer Requirements Current text: "This objective offers simplicity and flexibility in operation. These are important issues for service providers and other enterprises deploying large scale WLANs." Proposed text: Replace current text with following "It is crucial that there be adequate flexibility within WLAN deployments to allow the use of alternative technologies for transporting data and control information. Such flexibility is very important for service providers who must continually adapt their service offerings to remain profitable. Furthermore, as enterprises use their wireless infrastructure to improve productivity, the system must be able to deliver the appropriate benefits." ----XXXX---- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:33:36 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02621 for ; Mon, 10 Jan 2005 11:33:35 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 8839E1FCD6; Mon, 10 Jan 2005 11:33:36 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 318572035C; Mon, 10 Jan 2005 11:33:22 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id DDDAB2026C for ; Mon, 10 Jan 2005 11:32:20 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id 3B88F1FCD6 for ; Mon, 10 Jan 2005 11:32:05 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0A9xSNg010657 for ; Mon, 10 Jan 2005 17:59:28 +0800 (SGT) Message-Id: <200501100959.j0A9xSNg010657@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT2+3UTNoKPr1J7Rfq/nY6I4LDusQ== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Additions #1 - Interconnection Objective 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: Mon, 10 Jan 2005 18:02:15 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Additions #1 - Interconnection Objective Context: Interconnection Objective - Motivation and Protocol Benefits (Section 5.2.2) Interconnection Objective - Relation to Problem Statement (Section 5.2.3) Interconnection Objective - Customer Requirements (Section 5.2.4) Issue: These sub-sections were left blank in v00. Proposed change: Add text for the three sub-sections. The following are proposed; Section 5.2.2 - Motivation and Protocol Benefits "The main aim of the CAPWAP protocol is to achieve interoperability among various WTPs and WLAN controllers. As such, the motivation for this objective is for the protocol to be operable independent of underlying interconnection technologies." Section 5.2.3 - Relation to Problem Statement "The Problem Statement discusses the complexity of configuring larg WLANs. The selection of available interconnection technologies for large scale deployments further intensifies this complexity. This objective avoids part of the complexity by advocating operational independence of the protocol from underlying transport. It plays an important role in addressing [I-D.ietf-capwap-problem-statement]." Section 5.2.4 - Customer Requirements "This architecture objective is derived from wireless service providers who insist on flexibility in the selection of interconnection technologies for WLANs. Some service providers have existing networks with IP, ATM and other transports. The interconnection objective is beneficial in allowing WTPs to be interfaced to the broader network infrastructure by the different interconnection technologies." _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:33:53 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02666 for ; Mon, 10 Jan 2005 11:33:52 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 6F78F1FE41; Mon, 10 Jan 2005 11:33:53 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 7FA482028D; Mon, 10 Jan 2005 11:33:34 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 16E361FCD6 for ; Mon, 10 Jan 2005 11:32:04 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id B6FC71FDF3 for ; Mon, 10 Jan 2005 11:32:00 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0AAZvo5011656 for ; Mon, 10 Jan 2005 18:35:57 +0800 (SGT) Message-Id: <200501101035.j0AAZvo5011656@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT3AI28V/FgIT9gSoiuSYU1jCgybQ== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Additions #4 - STA Admission Control 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: Mon, 10 Jan 2005 18:38:44 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Additions #4 - STA Admission Control Context: STA Admission Control - Title - Introduction (Section 6.4) - Objective Details (Section 6.4.1) - Customer Requirements (Section 6.4.4) Issue: These sub-sections were left blank in v00. Proposed changes: Add text for the sub-sections. The following are proposed; -> Title Current text: "STA Admission Control Objective" Propoposed text: Change title to better reflect CAPWAP needs. Proposed title is "Access Control Objective" ----XXXX---- -> Section 6.4 - Introduction Current text: "STA Admission control deals with client authentication, handoff between WTPs, load balance, QoS etc. Access control in the CAPWAP context must be based on a variety of information. This is because CAPWAP combines both switching and wireless medium segments." Proposed text: Replace text above with following introduction; "Access control in centralized WLANs applies to both wireless clients and also WTPs. For the former, IEEE 802.11 related association and authentication are required while for the latter, specific means of authenticating new WTPs are required. Underlying both these needs is information exchange regarding the switching and wireless medium WLAN segments, security aspects and QoS considerations. Broadly these constitute the factual needs of access control." ----XXXX---- -> Section 6.4.1 - Objective Details Current text: "This objective focuses on access control based on collective information from the switching and wireless medium segments. As such, access to the WLAN is based on both the radio resources, i.e. wireless medium segment and network resources, i.e. Switching segment." Proposed text: Replace with following paragraphs "This objective focuses on the informational needs of WLAN access control and specifically the role of the CAPWAP protocol in transporting this information between WTPs and their WLAN controller. The following are some specific information aspects that need to be transported by the CAPWAP protocol; i. IEEE 802.11 association and authentication The association of wireless clients is distinct for initial and roaming cases. As a result, access control mechanisms requires specific contextual information regarding each case. Additionally, load balancing, QoS, security and congestion in both wireless medium segments and switching segments need to be considered. After IEEE 802.11 association, client authentication requires information relevant to the radio link between wireless clients and the WTP. Furthermore, the location of the IEEE 802.1X authenticator, whether within a centralized WLAN controller or within an alternative entity, presents differences in how authentication information is relayed. The CAPWAP protocol needs to make aware the corresponding information to the appropriate authentication entities. ii. WTP Access Control In addition to controlling access for wireless clients, it is also necessary to control admission of new WTPs. Given the threat of rogue WTPs, it is important for CAPWAP to relay appropriate authentication information between new WTPs and the WLAN controller." ----XXXX---- -> Section 6.3.4 - Customer Requirements (Left blank in v00) Proposed text: Add following new paragraph "Enterprises and service provides need a centralized WLAN controller to perform access control for both wireless clients and WTPs. Since this fundamentally relates to the exchange of relevant information, mangers of WLAN deployments require this objective be realized within a CAPWAP protocol." ----XXXX---- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:34:09 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02705 for ; Mon, 10 Jan 2005 11:34:09 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id B23892028D; Mon, 10 Jan 2005 11:34:09 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id C088C1FD62; Mon, 10 Jan 2005 11:33:48 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id DDD1220260 for ; Mon, 10 Jan 2005 11:32:11 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id 639961FDF3 for ; Mon, 10 Jan 2005 11:32:04 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0AA3lFA010812 for ; Mon, 10 Jan 2005 18:03:47 +0800 (SGT) Message-Id: <200501101003.j0AA3lFA010812@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT2/AHq7SCJJqyaSma7cnJnfl65sw== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Additions #2 - Extensibility Objective 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: Mon, 10 Jan 2005 18:06:34 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Additions #2 - Extensibility Objective Context: Extensibility Objective: Motivation and Protocol Benefits (Section 5.4.2) Relation to Problem Statement (Section 5.4.3) Customer Requirements (Section 5.4.4, Paragraph 1, second sentence) Issue: These sub-sections were left blank in v00. Proposed change: Add text for the three sub-sections. The following are proposed; Section 5.4.2 - Motivation and Protocol Benefits "The main benefit of extensibility is that the CAPWAP protocol will be adaptable to the various developments in IEEE 802.11 It also allows the protocol to be extended to support other wireless technologies." Section 5.4.3 - Relation to Problem Statement "The Problem Statement suggests that WLAN control mechanisms be adaptable to future technology developments. In particular, the CAPWAP protocol must be capable of handling new definitions and extensions of IEEE 802.11 technology." Section 5.4.4 - Customer Requirements Current text: "They require WLAN infrastructure to be able to meet current and future market requirements." Proposed text: "They require WLAN infrastructure to be able to meet current and future market requirements, including support for new wireless technologies and user aplications." _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:34:25 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02737 for ; Mon, 10 Jan 2005 11:34:25 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 5379B2046E; Mon, 10 Jan 2005 11:34:26 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 08AEA2047B; Mon, 10 Jan 2005 11:34:01 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id C449C1FD61 for ; Mon, 10 Jan 2005 11:32:24 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id CBF0020270 for ; Mon, 10 Jan 2005 11:32:09 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0A9o24n010317 for ; Mon, 10 Jan 2005 17:50:02 +0800 (SGT) Message-Id: <200501100950.j0A9o24n010317@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT2+bHz6Rcpb1IDQ3eJJ7JyDBEoIg== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Objectives Issue #4 - Clarification of 'engine-mechanism' 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: Mon, 10 Jan 2005 17:52:50 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Objectives Issue #4 - Clarification of 'engine-mechanism' Context: Centralized WTP Management - Introduction (Section 8.1, Paragraph 1) "The CAPWAP protocol should provide an engine-mechanism to spring WTP auto-configuration and /or software version updates and should support integration with existing network management system. WLAN controller as a management agent is optional." Issue: Sridhar refers to the paragraph above and comments; "The part of this sentence before "and" might need to be rephrased - not clear what is implied." Proposed change: The proposal is to remove this entire section. Centralized management issues will be solely dealt with in Section 6.5. _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:34:43 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02775 for ; Mon, 10 Jan 2005 11:34:42 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id AA69120365; Mon, 10 Jan 2005 11:34:42 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id DE0BD20472; Mon, 10 Jan 2005 11:34:12 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id E9AD520365 for ; Mon, 10 Jan 2005 11:32:21 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id 042531FD61 for ; Mon, 10 Jan 2005 11:32:07 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0A9oFYD010329 for ; Mon, 10 Jan 2005 17:50:15 +0800 (SGT) Message-Id: <200501100950.j0A9oFYD010329@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT2+iudjLj6lZjYS4CYT/jS2nwTJw== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Objectives Issue #5 - Relation of transport mechanisms to centralized management 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: Mon, 10 Jan 2005 17:53:02 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Objectives Issue #5 - Relation of TCP/IP to centralized management Context: Centralized WTP Management - Introduction (Section 8.1, Paragraph 3) "One example of transport mechanism for the CAPWAP protocol is TCP/IP. This will bring more flexibility to the way in which WLAN systems are deployed ." Issue: Sridhar refers to the paragraph above and comments; "Not clear about the relationship of this paragraph with the other parts of this section." Proposed change: The proposal is to remove this entire section. Centralized management issues will be solely dealt with in Section 6.5. _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:34:56 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02797 for ; Mon, 10 Jan 2005 11:34:56 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 41EB720494; Mon, 10 Jan 2005 11:34:57 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id BBEB02047A; Mon, 10 Jan 2005 11:34:27 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 5A5181FD61 for ; Mon, 10 Jan 2005 11:32:27 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id A0C61202A6 for ; Mon, 10 Jan 2005 11:32:11 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0A9hqZN010090 for ; Mon, 10 Jan 2005 17:43:52 +0800 (SGT) Message-Id: <200501100943.j0A9hqZN010090@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT2+MqFNMWtYHjkTjylwuNM388RqQ== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Objectives Issue #3 - Clarification of 'wide network' 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: Mon, 10 Jan 2005 17:46:40 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Objectives Issue #3 - Clarification of 'wide network' Context: Support for Traffic Separation - Motivation and Protocol Benefits (Section 6.3.2, Paragraph 2, last sentence) "This will enable remotely located WTPs to handle data in alternative ways instead of forwarding them across a wide network to the WLAN controller." Issue: Sridhar refers to the sentence above and comments; "Not clear about what is meant here by wide network." Proposed change: Edit the sentence to better present the reason for traffic separation. The proposal is; "This will enable WTPs located in remote locations to handle data in alternative ways instead of forwarding them across a potentially large intermediate network to the WLAN controller." _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:35:14 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02829 for ; Mon, 10 Jan 2005 11:35:13 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id E1F372049C; Mon, 10 Jan 2005 11:35:14 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 0C71A2048B; Mon, 10 Jan 2005 11:34:40 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 3C83D202A6 for ; Mon, 10 Jan 2005 11:32:28 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id 739D1202AA for ; Mon, 10 Jan 2005 11:32:13 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0A9bjTo009885 for ; Mon, 10 Jan 2005 17:37:45 +0800 (SGT) Message-Id: <200501100937.j0A9bjTo009885@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT2+GzX0MKEFJq3Qgykhi66MuFYKw== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Objective Issue #2 - Clarification of 'design types' and 'setup aspects' 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: Mon, 10 Jan 2005 17:40:33 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Objective Issue #2 - Clarification of 'design types' and 'setup aspects' Context: Interoperability Objective - Objective Details (Section 5.1.1, Paragraph 5) "This objective also addresses the need for flexibly configuring WTPs based on their design types and other setup aspects." Issue: Sridhar refers to the sentence above and comments; "'Design Types' and 'other setup aspects' is not very clear - can it be rephrased/elaborated?" Proposed change: Edit the sentence to better describe the flexibility to be achieved by CAPWAP. The following sentence is proposed; "This objective also addresses the need for flexibly configuring WTPs based on the differences in their design, operations and other characteristics." _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:35:28 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02851 for ; Mon, 10 Jan 2005 11:35:27 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id A1DEB2048C; Mon, 10 Jan 2005 11:35:28 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id DD2C120491; Mon, 10 Jan 2005 11:34:50 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 855CB1FDF3 for ; Mon, 10 Jan 2005 11:32:39 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id 3D53D2035E for ; Mon, 10 Jan 2005 11:32:16 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0A9Xl9n009753 for ; Mon, 10 Jan 2005 17:33:47 +0800 (SGT) Message-Id: <200501100933.j0A9Xl9n009753@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT299/PSHEBmid6SAiaprZCyC1a8Q== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Objectives Issue #1 - Difference between 'coexistence' and 'interoperability' 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: Mon, 10 Jan 2005 17:36:34 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Objective Issue #1 - Difference between 'coexistence' and 'interoperability' Context: Interoperability Objective - Objective Details (Section 5.1.1, Paragraph 1) "This objective for the CAPWAP protocol is to ensure that WTPs of both local MAC and split MAC architecture designs are capable of interoperation within a single WLAN." Issue: Sridhar refers to the paragraph above and comments; "Should it be coexistence instead of interoperability?" Proposed change: Include a new paragraph describing relationship of 'coexistence' and 'interoperability' in CAPWAP context. The following is proposed; "Coexistence of different types of WTPs also relates to interoperability. So in addition to enabling WLAN controllers to manage both local MAC and split MAC WTPs, this objective emphasizes that interoperability also be simultaneous. In this manner, a WLAN system can be operated with a mix of WTPs." _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Jan 10 11:35:39 2005 Received: from mail.frascone.com (postfix@frascone.com [204.49.99.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02869 for ; Mon, 10 Jan 2005 11:35:38 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 2D8A42048D; Mon, 10 Jan 2005 11:35:39 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 0FB2520485; Mon, 10 Jan 2005 11:35:02 -0500 (EST) X-Original-To: capwap@frascone.com Delivered-To: capwap@frascone.com Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 78CAF2031A for ; Mon, 10 Jan 2005 11:32:28 -0500 (EST) Received: from mailsrv.psl.com.sg (mailsrv.psl.com.sg [202.14.153.3]) by mail.frascone.com (Postfix) with ESMTP id 67B7D202C3 for ; Mon, 10 Jan 2005 11:32:15 -0500 (EST) Received: from Saravanan ([10.81.113.32]) by mailsrv.psl.com.sg (8.13.1/8.13.1) with ESMTP id j0A9Xl9o009753 for ; Mon, 10 Jan 2005 17:33:49 +0800 (SGT) Message-Id: <200501100933.j0A9Xl9o009753@mailsrv.psl.com.sg> From: "Saravanan Govindan" To: Organization: Panasonic Singapore Laboratories MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT299i1nAgkPbLpTaesLJArNK2/Lw== X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] CAPWAP Objectives Update 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: Mon, 10 Jan 2005 17:36:34 +0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Dear All, Happy New Year! The Objectives draft has received feedback from T. Sridhar so far. He has pointed out various issues that I think need to be discussed in the group. Also, the authors have thought of text for those sections that were left blank in the v00 draft. We would like to discuss these proposals too. I am sending out each issue separately to make for easier discussion. At the same time, please propose other objectives if you feel important points have been left out. In terms of organizations, I have split the proposals into (i) issues raised with existing content; (ii) additions made to various sections - both old and new; and (iii) editorial changes for better readability. Given the short deadline for the Objectives, it would be great to get the WG's feedback and new proposals soon. I look forward to the discussions. Cheers, Saravanan Govindan _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap