From diameter-admin@frascone.com Mon Nov 1 05:13:11 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 FAA11197 for ; Mon, 1 Nov 2004 05:13:11 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id C3FE31FEE5 for ; Mon, 1 Nov 2004 05:13:11 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id D62921FEEB for ; Mon, 1 Nov 2004 05:12:01 -0500 (EST) Date: Mon, 01 Nov 2004 05:12:01 -0500 Message-ID: <20041101101201.31173.59146.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 Nov 2 17:29:11 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 RAA23836 for ; Tue, 2 Nov 2004 17:29:10 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 37BF31FD39; Tue, 2 Nov 2004 17:29:07 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 7C3C31FD4F; Tue, 2 Nov 2004 17:29:03 -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 42BB81FD4F for ; Tue, 2 Nov 2004 17:28:51 -0500 (EST) Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by mail.frascone.com (Postfix) with ESMTP id 25B991FD39 for ; Tue, 2 Nov 2004 17:28:48 -0500 (EST) Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159]) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id iA2MSle21789; Wed, 3 Nov 2004 00:28:47 +0200 (EET) X-Scanned: Wed, 3 Nov 2004 00:28:06 +0200 Nokia Message Protector V1.3.31 2004060815 - RELEASE Received: (from root@localhost) by esdks004.ntc.nokia.com (8.12.9/8.12.9) id iA2MS6ZP028893; Wed, 3 Nov 2004 00:28:06 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks004.ntc.nokia.com 00BcDlUv; Wed, 03 Nov 2004 00:28:04 EET Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com [10.241.35.122]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id iA2MS1a19885; Wed, 3 Nov 2004 00:28:01 +0200 (EET) Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 2 Nov 2004 16:28:00 -0600 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: Unpublished drafts to be discussed at CAPWAP IETF 61 meeting Thread-Index: AcTBKzP/NnTxmE+6QgK1SScXoRPbYg== From: To: Cc: , , X-OriginalArrivalTime: 02 Nov 2004 22:28:00.0787 (UTC) FILETIME=[360E2E30:01C4C12B] X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Unpublished drafts to be discussed at CAPWAP IETF 61 meeting 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, 2 Nov 2004 14:28:00 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Congratulations all on our new WG! Since the new CAPWAP charter has = been accepted by the IESG, we are now updating the agenda for the IETF = CAPWAP f2f meeting next week. =20 There are 2 items that we need to discuss at IETF 61 that missed the = deadline for the internet draft repository, = draft-zhou-capwap-objectives-00.txt and draft-ietf-capwap-arch-06.txt. = These are both on the www.capwap.org website for review. Formally, = documents that have not been published in the internets-drafts = repository cannot be discussed at IETF f2f meetings unless the WG agrees = to an exception. We need to finalize the editor for the Objectives drafts to meet the Nov = deadline. There are 2 indivdual submissions that should be considered = as a starting point for this milestone. They will both be presented at = the face to face meeting in Washington DC provided there are no = objections to discussing draft-zhou-capwap-objectives-00.txt. In addtition, the final IESG review comments for the taxonomy draft have = been updated as draft-ietf-capwap-arch-06.txt. If there are no = objections by the WG to discuss this draft at the f2f meeting next week, = Lily Yang will present the changes from version 05 to version 06 of the = taxonomy draft. Please review the drafts posted on www.capwap.org and provide comments = to the list and discussion at the meeting, especially for the Objective = drafts that are being proposed. The Objectives Work Item will reflect = WG consensus and will shape the CAPWAP protocol. If there are no objections by the WG, we will discuss = draft-zhou-capwap-objectives-00.txt and draft-ietf-capwap-arch-06.txt = next week at the CAPWAP f2f meeting. Thanks eveybody and see you in Washington. Dorothy & Mani _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Tue Nov 2 18:35:08 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 SAA00914 for ; Tue, 2 Nov 2004 18:35:07 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 29B4D1FCCD; Tue, 2 Nov 2004 18:35:07 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 80E381FD39; Tue, 2 Nov 2004 18:35:03 -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 657A61FD39 for ; Tue, 2 Nov 2004 18:34:09 -0500 (EST) Received: from orsfmr001.jf.intel.com (fmr12.intel.com [134.134.136.15]) by mail.frascone.com (Postfix) with ESMTP id 2E6211FCCD for ; Tue, 2 Nov 2004 18:34:06 -0500 (EST) 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 iA2NYtmU018922 for ; Tue, 2 Nov 2004 23:34:55 GMT Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by talaria.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-inner.mc,v 1.11 2004/07/29 22:51:53 root Exp $) with SMTP id iA2NPu6P023808 for ; Tue, 2 Nov 2004 23:27:02 GMT Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56]) by orsmsxvs040.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004110215340511238 for ; Tue, 02 Nov 2004 15:34:05 -0800 Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 2 Nov 2004 15:34:05 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4C134.70CD30B2" Message-ID: <2AF68A477DD44C4EBCBE338C24E7A9EE0297453F@orsmsx408> Thread-Topic: Draft v06 for CAPWAP Taxonomoy ready for review -- please review ASAP Thread-Index: AcTBGvmIgxO7yvvOQp6csDl+FFN/DgAGTRYA From: "Yang, Lily L" To: X-OriginalArrivalTime: 02 Nov 2004 23:34:05.0254 (UTC) FILETIME=[710FD660:01C4C134] X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Draft v06 for CAPWAP Taxonomoy ready for review -- please review ASAP 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, 2 Nov 2004 15:34:04 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) This is a multi-part message in MIME format. ------_=_NextPart_001_01C4C134.70CD30B2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 Hi, all - =20 IESG review of the CAPWAP Taxonomy draft resulted in a list of comments that must be addressed with a new revision. The original comments from IESG review can be seen here: https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dTag= =3D 11587&rfc_flag=3D0 =20 Here is our proposed draft for v06 to address these comments: http://www.capwap.org/draft-ietf-capwap-arch-06.txt =20 Here is the change log from v05 to v06: http://www.capwap.org/change-log-for-v06-fromv05.txt =20 Please review and provide quick feedback, including nit-picks. We can fold those into the draft before submitting to IETF repository.=20 I plan to submit the draft officially next week after the IETF meeting Monday. I am hoping we can publish this soon as RFC with this revision. So any proof-reading you can do is appreciated. =20 Thanks! Lily Yang (Editor) =20 ------_=_NextPart_001_01C4C134.70CD30B2 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

Hi, all –

 

IESG review of the CAPWAP Taxonomy draft resulted in a list of comments that = must be addressed with a new revision.

The original comments from IESG review can be seen = here:

https://datatracker.ietf.org/publi= c/pidtracker.cgi?command=3Dview_id&dTag=3D11587&rfc_flag=3D0<= o:p>

 

Here is our proposed draft for v06 to address these = comments:

http://www.c= apwap.org/draft-ietf-capwap-arch-06.txt

 

&= nbsp;        Here is the change log from v05 to v06:

http://www.= capwap.org/change-log-for-v06-fromv05.txt

 

Please review and provide quick feedback, including nit-picks. We can fold = those into the draft before submitting to IETF repository. =

I plan to submit the draft officially next week after the IETF meeting = Monday. I am hoping we can publish this soon as RFC with this revision. So any proof-reading you can do is appreciated.

 

Thanks!

Lily Yang (Editor)

 

------_=_NextPart_001_01C4C134.70CD30B2-- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Wed Nov 3 16:16:11 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 QAA20091 for ; Wed, 3 Nov 2004 16:16:09 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 9C8FC1FE3E; Wed, 3 Nov 2004 16:16:05 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 5FB0D1FC6E; Wed, 3 Nov 2004 16:16: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 620191FC6E for ; Wed, 3 Nov 2004 16:15:18 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mail.frascone.com (Postfix) with ESMTP id 72BC31FC63 for ; Wed, 3 Nov 2004 16:15:16 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20050; Wed, 3 Nov 2004 16:15:12 -0500 (EST) Message-Id: <200411032115.QAA20050@ietf.org> From: The IESG To: IETF-Announce@ietf.org Cc: capwap@frascone.com, Mahalingam Mani , Dorothy Gellert X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] WG Action: RECHARTER: Control And Provisioning of Wireless Access Points (capwap) 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, 03 Nov 2004 16:15:12 -0500 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) The Control And Provisioning of Wireless Access Points (capwap) working group in the Operations and Management Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the working group Chairs. Control And Provisioning of Wireless Access Points (capwap) =========================================================== Current Status: Active Working Group Chair(s): Mahalingam Mani Dorothy Gellert Operations and Management Area Director(s): Bert Wijnen David Kessens Operations and Management Area Advisor: Bert Wijnen Technical Advisor(s): Bob O'Hara Mailing Lists: General Discussion: capwap@frascone.com To Subscribe: http://mail.frascone.com/mailman/listinfo/capwap Archive: http://mail.frascone.com/pipermail/capwap/ Description of Working Group: The original CAPWAP WG charter included drafting a problem statement and a taxonomy of architectures. The new charter of the CAPWAP WG proposes building upon the original charter and developing a CAPWAP protocol to provide interoperability among WLAN backend architectures. The intent of the CAPWAP protocol is to facilitate control, management and provisioning of WLAN Termination Points (WTPs) specifying the services, functions and resources relating to 802.11 WLAN Termination Points in order to allow for interoperable implementations of WTPs and ACs. The revised CAPWAP WG will reference two classes of the Centralized WLAN Architecture family, namely the Local MAC and the Split MAC, as described in the CAPWAP Architecture Taxonomy draft. The protocol will define the CAPWAP control plane including the primitives to control data access. An effective Centralized CAPWAP Architecture impacts how WLAN data traffic is managed over the backend network. This implies the abilitiy to control how data is forwarded by negotiating existng data encapsulation mechanisms and specifying data payload formats in order to ensure interoperability between CAPWAP vendors. No other specifications of the CAPWAP data plane are within the scope of this charter. The CAPWAP WG will strive for extensibility in the protocol design to favor future applicability to other access technologies, especially IEEE 802.16. While accommodation of any access technology other than IEEE 802.11 is not required for successful completion, there are clear deployment advantages if a wide range of access technologies are accommodated. In summary, the primary goals of the group will be: 1. Defining a set of Objectives based on the architecture taxonomy work that lists the requirements for an interoperable CAPWAP protocol. In addition, the WG will incorporate requirements derived from the inputs provided by Enterprise and (hotspot) Providers based on the WLAN deployment challenges addressed by CAPWAP architecture. This document will: a. include objectives to address problems described in the CAPWAP Problem statement document b. Describe each objective, its benefit to the protocol and how it satisfies the problem statement. c. Prioritize and classify the objectives into 3 categories: i. Mandatory and Accepted ii. Desirable iii. Rejected d. Undergo review in IEEE 802 as needed This should result in the first WG Last Call for Objectives draft. To avoid requirements bloat and stalemate, the WG has a hard deadline on the Objectives phase. The WG MUST reach WG consensus on the objectives draft by Feb 2005. This is for several reasons: * We must send this for review to IEEE at that time. * We must have a reasonably stable set of objectives so that candidate submissions are aware of the objectives to be met. The 2nd WG Last Call (in April) for the objectives draft is to ensure that the WG has consensus on any changes that may result from IEEE and expert review. So it is not the intention that the WG keeps adding new Objectives after Feb 2005. If the WG cannot reach consensus on the Objectives draft by the May 2005 milestone to the IESG, the WG will close. 2. Evaluating a set of candidate proposals that include existing IETF protocols and any proposals leading to the selection of a protocol on which to base the CAPWAP standard. 3. Developing a CAPWAP protocol standard that meets the Mandatory and Accepted objectives from the Evaluation draft and contains the minimal set of feature needed to control and provision WLAN Access Points. Specifically The CAPWAP protocol document will address the following considerations: a. Architecture b. Operations c. Security d. Network Management e. Scalability f. Performance 4. A MIB Document to support the CAPWAP protocol. In addition, the CAPWAP WG will maintain its Liaison with the IEEE to ensure consistency of its work with the IEEE 802.11 Standard. Deliverables: * Objectives/Criteria Document for CAPWAP protocol * Protocol evaluation and base protocol selection document * CAPWAP Protocol standard * MIB support standard Goals and Milestones: Done Last call for problem statement draft. Done Discuss last call comments for problem statement at IETF 59. Done Last Call for architecture description document. Done Submit problem statement to IESG for publication approval. Done Architecture document to expert review. Done Stable Architecture document for review/sync-up with IEEE 802 Done Discuss results of IEEE 802 review/sync-up Nov 04 Issue first Internet-Draft of CAPWAP Objectives document Feb 05 First WGLC for CAPWAP Objectives Draft Feb 05 Submit CAPWAP Objectives to IEEE/IETF experts review Mar 05 Deadline to submit candidate protocol proposals to the WG Apr 05 Second WGLC for CAPWAP Objectives Draft May 05 Submit CAPWAP Objectives draft to IESG as Informational RFC May 05 Shutdown WG if CAPWAP Objectives have not finalized, otherwise continue with next milestones. Jun 05 Issue first Internet-Draft of CAPWAP Evaluation draft Aug 05 WGLC for CAPWAP Evaluation draft Sep 05 Submit CAPWAP Evaluation draft to IESG as Information RFC Oct 05 Issue first Internet Draft of CAPWAP protocol Nov 05 Issue first Internet-Draft of CAPWAP MIB Dec 05 WGLC for CAPWAP protocol Jan 06 Submit CAPWAP protocol to IESG as Proposed Standard RFC Jan 06 WGLC for CAPWAP MIB Mar 06 Submit CAPWAP MIB to IESG as Proposed Standard RFC _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Wed Nov 3 20:50:08 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 UAA12872 for ; Wed, 3 Nov 2004 20:50:07 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id B9C351FC11; Wed, 3 Nov 2004 20:50:07 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 1534F1FC17; Wed, 3 Nov 2004 20:50: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 71DFA1FC17 for ; Wed, 3 Nov 2004 20:49:37 -0500 (EST) Received: from smtp.foundrynet.com (smtp.foundrynet.com [63.251.100.14]) by mail.frascone.com (Postfix) with ESMTP id C10751FC11 for ; Wed, 3 Nov 2004 20:49:35 -0500 (EST) Received: from email.foundrynet.com (ns100corpdmz.foundrynet.com [63.251.100.1]) by smtp.foundrynet.com (8.12.8/8.12.8/FoundryNetworks) with ESMTP id iA41nXHR000589; Wed, 3 Nov 2004 17:49:34 -0800 Received: from localhost (localhost.localdomain [127.0.0.1]) by email.foundrynet.com (Postfix) with ESMTP id 9C898C24010; Wed, 3 Nov 2004 17:49:33 -0800 (PST) Received: from email.foundrynet.com ([127.0.0.1]) by localhost (email.foundrynet.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02828-01; Wed, 3 Nov 2004 17:49:33 -0800 (PST) Received: from vshinhapc (unknown [192.168.20.56]) by email.foundrynet.com (Postfix) with ESMTP id 44883C2400D; Wed, 3 Nov 2004 17:49:33 -0800 (PST) From: "Vishal Sinha" To: Cc: "Capwap@Frascone. Com" Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Virus-Scanned: by amavisd-new at foundrynet.com X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Urgent: Looking for wireless tech support engineer - Please ignore if you are not interested 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, 3 Nov 2004 17:49:33 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit Technical Support Wireless Day to day Responsibilities: Provides support to customers, resellers and field personnel in resolving company product related issues. Document sequence of events related to resolving customer technical issues Must Have Skills The Customer Support Engineer will provide daily phone consultation with clients as they call to report problems with their software and/or hardware; document client calls in the client management database; ensure client expectations are properly managed, and that issues and needs are resolved to the client's satisfaction in a timely manner. The successful candidate will work as a direct resource for external clients, as well as internal clients to resolve technical problems, provide troubleshooting skills and research for more difficult problems, escalate client problems that require a more complicated solution, maintain call ownership, and see the problem through to resolution. Additionally, they will test new releases for software products before distribution to clients to ensure the product is sound, work with third party vendors regarding client data that is transmitted to them, research and resolve problems that may occur with sending and/or receiving client data, troubleshoot client-reporting issues, contact vendors to clear up the issues, and provide follow-up to clients when issues are resolved. The Successful candidate understands all service offers and the benefits to our clients, works as a direct resource to answer client inquiries, and must have the ability to effectively communicate to both clients and internal personnel while working under pressure and with time constraints. Finally, the successful candidate will be involved in the creation and completion of department and individual goals and fulfilling all services the team promises to clients. The ideal candidate will have experience with 802.11 wireless and encryption protocols such as WEP, WPA, TKIP, and AES experience with authentication protocols such as 802.1X, and Radius, and network management (NMS) experience. The candidate should have experience in the L3 VPN's and tunneling. A firm understanding of 802.11a/b/g radio technology and the security aspects is strongly desired. Education and Work Experience: FNCNE and/or FNCNP is highly preferred. Candidates hired without this certification will be required to complete the FNCNE certification program within six (6) months of hire date. Prefer BS or related discipline. Experience with STP, BGP, OSPF, RIP, MPLS, IPX, AppleTalk. Interested, send me an email @ vsinha@foundrynet.com _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Nov 8 06:05:05 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 GAA21679 for ; Mon, 8 Nov 2004 06:05:04 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 0DD001FE5E; Mon, 8 Nov 2004 06:05:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id B08F81FE46; Mon, 8 Nov 2004 06:05: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 1FBB01FE46 for ; Mon, 8 Nov 2004 06:04:54 -0500 (EST) Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100]) by mail.frascone.com (Postfix) with ESMTP id 4BA811FD39 for ; Mon, 8 Nov 2004 06:04:52 -0500 (EST) Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iA8B31Er021812 for ; Mon, 8 Nov 2004 06:03:01 -0500 (EST) Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iA8B2wEr021764 for ; Mon, 8 Nov 2004 06:02:59 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: Thread-Topic: Monday 11/8/04 meeting agenda - near-final. Thread-Index: AcTFgruCC7i0+bPqTY6Zh3jqLflPYg== X-Priority: 1 Priority: Urgent Importance: high From: "Mani, Mahalingam (Mahalingam)" To: X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Monday 11/8/04 meeting agenda - near-final. 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, 8 Nov 2004 04:04:48 -0700 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable All, The recharter approval came just-in-time for this new CAPWAP WG meeting to be possible. The Objectives discussion has not commenced in WG - but one submission has made it to the repository - though not within -00 deadline. Another is available for perusal. We had been waiting to check on any objections to present either of them. Hearing none - the following agenda is proposed. 1. Agenda bashing (5 min)=20 2. New charter: Plan of Action (15 min.)=20 3. Taxonomy Draft IESG review & resolutions: Lily Yang (10 min.)=20 4. IEEE update on AP Functions AdHoc Committee: Dorothy Stanley (10 min) 5. Inputs to Call for Objectives - Motive & Guideline recap. (10 min).=20 6. Presentation of Objectives draft: Saravanan Govindan (15 min)=20 =20 http://www.ietf.org/internet-drafts/draft-govindan-capwap-objectives-00. txt 7. Presentation of Objectives Draft: (Zhou et al) (15 min)=20 http://www.capwap.org/objs/draft-zhou-capwap-objectives-00.txt 8. Discussion on progressing Objectives work: (10 min) 9. Open Discussion=20 -mani _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Fri Nov 12 10:05: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 KAA09327 for ; Fri, 12 Nov 2004 10:05:06 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 462D61FD57; Fri, 12 Nov 2004 10:05:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id D5B621FCC9; Fri, 12 Nov 2004 10:05: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 29CBB1FCC9 for ; Fri, 12 Nov 2004 10:04:20 -0500 (EST) Received: from hermes.jf.intel.com (fmr05.intel.com [134.134.136.6]) by mail.frascone.com (Postfix) with ESMTP id 447FF1FC64 for ; Fri, 12 Nov 2004 10:04:18 -0500 (EST) Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6]) 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 iACF8iCM031884; Fri, 12 Nov 2004 15:08:44 GMT Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by petasus.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-inner.mc,v 1.11 2004/07/29 22:51:53 root Exp $) with SMTP id iACF875d029389; Fri, 12 Nov 2004 15:08:19 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 M2004111207041318751 ; Fri, 12 Nov 2004 07:04:13 -0800 Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Fri, 12 Nov 2004 07:04:12 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <2AF68A477DD44C4EBCBE338C24E7A9EE02AEF275@orsmsx408> Thread-Topic: Taxonomy v06 ready for review Thread-Index: AcTIyN7arHJKGE6JT9KK3jwIo1Ml7Q== From: "Yang, Lily L" To: Cc: "Russ Housley" , "Walker, Jesse" X-OriginalArrivalTime: 12 Nov 2004 15:04:12.0982 (UTC) FILETIME=[DEC71560:01C4C8C8] X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Taxonomy v06 ready for 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: Fri, 12 Nov 2004 07:04:13 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Hi,=20 At the IETF CAPWAP meeting three days ago, Russ Housley provided alternative text for 4.8.1, regarding PMK sharing issue. Here is the new text from Russ: " If the STA and AC are the parties in the 4-way handshake (defined in [4]), and 802.11i traffic encryption terminates at the WTP, then the PTK (Pairwise Transient Key) has to be transferred from the AC to the WTP. Since the keying material is part of the control and provisioning of the WTPs, a secure encrypted tunnel for control frames is employed to transport the keying material. The centralized model encourages AC implementations to use one PMK for many different WTPs. This practice facilitates speedy transition by a station from one WTP to another WTP that is connected to the same AC without establishing a separate PMK. However, this leaves the station in a difficult position. The station cannot distinguish between a compromised PMK and one that is intentionally being shared. This issue must be resolved. While the resolution is beyond the scope of the CAPWAP working group; however, the resolution must be completed before the CAPWAP working group can complete its protocol development. The venue for this resolution is to be determined by the IEEE 802 and IETF liaisons." A new version of the taxonomy draft which incorporated this new text is available at http://www.capwap.org/draft-ietf-capwap-arch-06.txt Please review by next Wed (Nov 17) as I would like to submit this draft to IETF repository on Thursday for IESG review again. Thanks! Lily _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Fri Nov 12 10:16:06 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 KAA11185 for ; Fri, 12 Nov 2004 10:16:06 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id D00C81FC64; Fri, 12 Nov 2004 10:16:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id E52A11FCC9; Fri, 12 Nov 2004 10:16: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 28E201FCC9 for ; Fri, 12 Nov 2004 10:15:59 -0500 (EST) Received: from AIREMAIL.airespace.com (da001d3897.stl-mo.osd.concentric.net [66.236.111.57]) by mail.frascone.com (Postfix) with ESMTP id 40A131FC64 for ; Fri, 12 Nov 2004 10:15:57 -0500 (EST) 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] Taxonomy v06 ready for review Message-ID: <55749BC69138654EBBC4C50BA4F5561003754C52@AIREMAIL.airespace.com> Thread-Topic: [Capwap] Taxonomy v06 ready for review Thread-Index: AcTIyN7arHJKGE6JT9KK3jwIo1Ml7QAAWvgw From: "Bob O'Hara" To: "Yang, Lily L" , Cc: "Russ Housley" , "Walker, Jesse" 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: Fri, 12 Nov 2004 07:15:43 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Lily, I disagree with the statement near the end of Russ' text that "the resolution must be completed before the CAPWAP working group can complete its protocol development." This is one person's opinion. My opinion is that, since Russ also grants that the solution to this problem is outside the scope of CAPWAP, all that CAPWAP has to do is not to develop a protocol that prevents the problem from being solved. I also don't see how this statement of opinion belongs in the taxonomy document. The description of the problem and the way it is dealt with by the centralized architecture belong in the document, but not the opinion. -Bob =20 -----Original Message----- From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On Behalf Of Yang, Lily L Sent: Friday, November 12, 2004 7:04 AM To: capwap@frascone.com Cc: Russ Housley; Walker, Jesse Subject: [Capwap] Taxonomy v06 ready for review Hi,=20 At the IETF CAPWAP meeting three days ago, Russ Housley provided alternative text for 4.8.1, regarding PMK sharing issue. Here is the new text from Russ: " If the STA and AC are the parties in the 4-way handshake (defined in [4]), and 802.11i traffic encryption terminates at the WTP, then the PTK (Pairwise Transient Key) has to be transferred from the AC to the WTP. Since the keying material is part of the control and provisioning of the WTPs, a secure encrypted tunnel for control frames is employed to transport the keying material. The centralized model encourages AC implementations to use one PMK for many different WTPs. This practice facilitates speedy transition by a station from one WTP to another WTP that is connected to the same AC without establishing a separate PMK. However, this leaves the station in a difficult position. The station cannot distinguish between a compromised PMK and one that is intentionally being shared. This issue must be resolved. While the resolution is beyond the scope of the CAPWAP working group; however, the resolution must be completed before the CAPWAP working group can complete its protocol development. The venue for this resolution is to be determined by the IEEE 802 and IETF liaisons." A new version of the taxonomy draft which incorporated this new text is available at http://www.capwap.org/draft-ietf-capwap-arch-06.txt Please review by next Wed (Nov 17) as I would like to submit this draft to IETF repository on Thursday for IESG review again. Thanks! Lily _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Fri Nov 12 10:37: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 KAA13201 for ; Fri, 12 Nov 2004 10:37:06 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 0E99E1FCD1; Fri, 12 Nov 2004 10:37:07 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 6E96E1FCD3; Fri, 12 Nov 2004 10:37:03 -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 9E19A1FCD3 for ; Fri, 12 Nov 2004 10:36:51 -0500 (EST) Received: from caduceus.jf.intel.com (fmr06.intel.com [134.134.136.7]) by mail.frascone.com (Postfix) with ESMTP id C82CC1FCD1 for ; Fri, 12 Nov 2004 10:36:49 -0500 (EST) Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6]) by caduceus.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 iACFahxq015906; Fri, 12 Nov 2004 15:36:44 GMT Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by petasus.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-inner.mc,v 1.11 2004/07/29 22:51:53 root Exp $) with SMTP id iACFee5f016092; Fri, 12 Nov 2004 15:40:49 GMT Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs040.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004111207364612928 ; Fri, 12 Nov 2004 07:36:46 -0800 Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Fri, 12 Nov 2004 07:36:46 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.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] Taxonomy v06 ready for review Message-ID: <2AF68A477DD44C4EBCBE338C24E7A9EE02AEF29B@orsmsx408> Thread-Topic: [Capwap] Taxonomy v06 ready for review Thread-Index: AcTIy6P+9jd5MmhUQICk75EeDZsomAAAEP5w From: "Yang, Lily L" To: "Russ Housley" , "Bob O'Hara" , Cc: "Walker, Jesse" X-OriginalArrivalTime: 12 Nov 2004 15:36:46.0834 (UTC) FILETIME=[6B5D3D20:01C4C8CD] 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: Fri, 12 Nov 2004 07:36:45 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Russ -- Does it have to be a strict dependency on this external unknown entity? Is it acceptable if CAPWAP works around the problem before the solution to the root of the problem is fixed somewhere else? In that case, CAPWAP may not have to wait for the final solution coming from an external entity, as long as CAPWAP also allows integration of such a final solution. It is best if we can structure it so that we can make progress at CAPWAP without being subject to external dependency like this. Bottom line: we need to fix the problem -- either by a permanent fix coming from outside, or a temporary workaround. IMHO, both should be acceptable.=20 Lily -----Original Message----- From: Russ Housley [mailto:housley@vigilsec.com]=20 Sent: Friday, November 12, 2004 7:24 AM To: Bob O'Hara; Yang, Lily L; capwap@frascone.com Cc: Walker, Jesse Subject: RE: [Capwap] Taxonomy v06 ready for review Bob: How do we tell the reader about the dependency? I am certainly willing to=20 accept any words that do so. Russ At 10:15 AM 11/12/2004, Bob O'Hara wrote: >Lily, > >I disagree with the statement near the end of Russ' text that "the >resolution must be completed before the CAPWAP working group can >complete its protocol development." This is one person's opinion. My >opinion is that, since Russ also grants that the solution to this >problem is outside the scope of CAPWAP, all that CAPWAP has to do is not >to develop a protocol that prevents the problem from being solved. > >I also don't see how this statement of opinion belongs in the taxonomy >document. The description of the problem and the way it is dealt with >by the centralized architecture belong in the document, but not the >opinion. > > -Bob > > >-----Original Message----- >From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On >Behalf Of Yang, Lily L >Sent: Friday, November 12, 2004 7:04 AM >To: capwap@frascone.com >Cc: Russ Housley; Walker, Jesse >Subject: [Capwap] Taxonomy v06 ready for review > > >Hi, >At the IETF CAPWAP meeting three days ago, Russ Housley provided >alternative text for 4.8.1, regarding PMK sharing issue. Here is the new >text from Russ: > > " If the STA and AC are the parties in the 4-way handshake (defined in > [4]), and 802.11i traffic encryption terminates at the WTP, then the > PTK (Pairwise Transient Key) has to be transferred from the AC to the > WTP. Since the keying material is part of the control and > provisioning of the WTPs, a secure encrypted tunnel for control > frames is employed to transport the keying material. > > The centralized model encourages AC implementations to use one PMK > for many different WTPs. This practice facilitates speedy transition > by a station from one WTP to another WTP that is connected to the > same AC without establishing a separate PMK. However, this leaves > the station in a difficult position. The station cannot distinguish > between a compromised PMK and one that is intentionally being shared. > This issue must be resolved. While the resolution is beyond the > scope of the CAPWAP working group; however, the resolution must be > completed before the CAPWAP working group can complete its protocol > development. The venue for this resolution is to be determined by > the IEEE 802 and IETF liaisons." > >A new version of the taxonomy draft which incorporated this new text is >available at http://www.capwap.org/draft-ietf-capwap-arch-06.txt >Please review by next Wed (Nov 17) as I would like to submit this draft >to IETF repository on Thursday for IESG review again. > >Thanks! > >Lily >_______________________________________________ >Capwap mailing list >Capwap@frascone.com >http://mail.frascone.com/mailman/listinfo/capwap _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Fri Nov 12 11:09:06 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 LAA15844 for ; Fri, 12 Nov 2004 11:09:06 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 536631FC64; Fri, 12 Nov 2004 11:09:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 447621FCD3; Fri, 12 Nov 2004 11:09:03 -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 7A2EE1FCD3 for ; Fri, 12 Nov 2004 11:08:03 -0500 (EST) Received: from AIREMAIL.airespace.com (da001d3897.stl-mo.osd.concentric.net [66.236.111.57]) by mail.frascone.com (Postfix) with ESMTP id 79FBB1FC64 for ; Fri, 12 Nov 2004 11:08:00 -0500 (EST) 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] Taxonomy v06 ready for review Message-ID: <55749BC69138654EBBC4C50BA4F5561003754C65@AIREMAIL.airespace.com> Thread-Topic: [Capwap] Taxonomy v06 ready for review Thread-Index: AcTIy6KjtiJOMIXNRM2nJf6BO8EaSgAAjnOA From: "Bob O'Hara" To: "Russ Housley" , "Yang, Lily L" , Cc: "Walker, Jesse" 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: Fri, 12 Nov 2004 08:07:58 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Russ,=20 I think that stating the problem, as you have so eloquently done, is sufficient for the taxonomy draft, along with stating that it is not solved. The Objectives draft should include an objective of the to be developed protocol(s) that the solution to the problem must not be excluded by the protocol that is developed. =20 The protocol document should have a restatement of the problem and a description of what limitations, if any, the protocol places on how the problem might be solved. Possibly, the protocol document will reference another document where the solution to the problem is described. Does that make sense? -Bob =20 -----Original Message----- From: Russ Housley [mailto:housley@vigilsec.com]=20 Sent: Friday, November 12, 2004 7:24 AM To: Bob O'Hara; Yang, Lily L; capwap@frascone.com Cc: Walker, Jesse Subject: RE: [Capwap] Taxonomy v06 ready for review Bob: How do we tell the reader about the dependency? I am certainly willing to=20 accept any words that do so. Russ At 10:15 AM 11/12/2004, Bob O'Hara wrote: >Lily, > >I disagree with the statement near the end of Russ' text that "the >resolution must be completed before the CAPWAP working group can >complete its protocol development." This is one person's opinion. My >opinion is that, since Russ also grants that the solution to this >problem is outside the scope of CAPWAP, all that CAPWAP has to do is not >to develop a protocol that prevents the problem from being solved. > >I also don't see how this statement of opinion belongs in the taxonomy >document. The description of the problem and the way it is dealt with >by the centralized architecture belong in the document, but not the >opinion. > > -Bob > > >-----Original Message----- >From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On >Behalf Of Yang, Lily L >Sent: Friday, November 12, 2004 7:04 AM >To: capwap@frascone.com >Cc: Russ Housley; Walker, Jesse >Subject: [Capwap] Taxonomy v06 ready for review > > >Hi, >At the IETF CAPWAP meeting three days ago, Russ Housley provided >alternative text for 4.8.1, regarding PMK sharing issue. Here is the new >text from Russ: > > " If the STA and AC are the parties in the 4-way handshake (defined in > [4]), and 802.11i traffic encryption terminates at the WTP, then the > PTK (Pairwise Transient Key) has to be transferred from the AC to the > WTP. Since the keying material is part of the control and > provisioning of the WTPs, a secure encrypted tunnel for control > frames is employed to transport the keying material. > > The centralized model encourages AC implementations to use one PMK > for many different WTPs. This practice facilitates speedy transition > by a station from one WTP to another WTP that is connected to the > same AC without establishing a separate PMK. However, this leaves > the station in a difficult position. The station cannot distinguish > between a compromised PMK and one that is intentionally being shared. > This issue must be resolved. While the resolution is beyond the > scope of the CAPWAP working group; however, the resolution must be > completed before the CAPWAP working group can complete its protocol > development. The venue for this resolution is to be determined by > the IEEE 802 and IETF liaisons." > >A new version of the taxonomy draft which incorporated this new text is >available at http://www.capwap.org/draft-ietf-capwap-arch-06.txt >Please review by next Wed (Nov 17) as I would like to submit this draft >to IETF repository on Thursday for IESG review again. > >Thanks! > >Lily >_______________________________________________ >Capwap mailing list >Capwap@frascone.com >http://mail.frascone.com/mailman/listinfo/capwap _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Fri Nov 12 11:38: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 LAA18385 for ; Fri, 12 Nov 2004 11:38:06 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id CB7EE1FC64; Fri, 12 Nov 2004 11:38:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 2F4501FCD1; Fri, 12 Nov 2004 11:38:03 -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 4DD701FCD1 for ; Fri, 12 Nov 2004 11:37:15 -0500 (EST) Received: from tierw.net.avaya.com (tierw.net.avaya.com [198.152.13.100]) by mail.frascone.com (Postfix) with ESMTP id 7FF361FC64 for ; Fri, 12 Nov 2004 11:37:13 -0500 (EST) Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iACGSt2m024251 for ; Fri, 12 Nov 2004 11:28:55 -0500 (EST) Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iACGS82m023006 for ; Fri, 12 Nov 2004 11:28:27 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4C8D5.BF8A38B4" Message-ID: Thread-Topic: CAPWAP session presentations Thread-Index: AcTI1b9AStUWkQvQSk+oGM9XyR3kog== X-Priority: 1 Priority: Urgent Importance: high From: "Mani, Mahalingam (Mahalingam)" To: X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] CAPWAP session presentations 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: Fri, 12 Nov 2004 09:36:24 -0700 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) This is a multi-part message in MIME format. ------_=_NextPart_001_01C4C8D5.BF8A38B4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The presentations and minutes of the IETF61 CAPWAP session can be found at =20 www.capwap.org/ietf61 =20 [The CAPWAP website is hosted by Dave Frascone - thanks Dave]. =20 thanks, -mani =20 ------_=_NextPart_001_01C4C8D5.BF8A38B4 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The presentations and minutes of the IETF61 CAPWAP = session can be found at

 

www.capwap.org/ietf61

 

[The CAPWAP website is hosted by Dave Frascone = – thanks Dave].

 

thanks,

-mani

 

------_=_NextPart_001_01C4C8D5.BF8A38B4-- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Fri Nov 12 11:38:21 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 LAA18412 for ; Fri, 12 Nov 2004 11:38:18 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 0996C1FCD1; Fri, 12 Nov 2004 11:38:20 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 3F0301FD5C; Fri, 12 Nov 2004 11:38:08 -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 ABECD1FCD1 for ; Fri, 12 Nov 2004 11:37:57 -0500 (EST) Received: from alageremail2.agere.com (alageremail2.agere.com [192.19.192.110]) by mail.frascone.com (Postfix) with ESMTP id E0CAE1FC64 for ; Fri, 12 Nov 2004 11:37:55 -0500 (EST) Received: from alerelay.agere.com (alerelay.agere.com [135.14.190.33]) by alageremail2.agere.com (8.11.7+Sun/8.10.2) with ESMTP id iACGbq619774; Fri, 12 Nov 2004 11:37:52 -0500 (EST) Received: from palex2kf01.ags.agere.com (palex2kf01.agere.com [128.94.210.80]) by alerelay.agere.com (8.11.6+Sun/8.11.6) with ESMTP id iACGbpr29937; Fri, 12 Nov 2004 11:37:51 -0500 (EST) Received: from PAUEX2KF01.ags.agere.com ([135.14.186.42]) by palex2kf01.ags.agere.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 12 Nov 2004 11:37:51 -0500 Received: from agere.com ([135.149.86.132]) by PAUEX2KF01.ags.agere.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 12 Nov 2004 11:37:51 -0500 Message-ID: <4194E6DE.6060405@agere.com> From: Dorothy Stanley User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Bob O'Hara" , "Yang, Lily L" , Russ Housley Cc: capwap@frascone.com, "Walker, Jesse" Subject: Re: [Capwap] Taxonomy v06 ready for review References: <55749BC69138654EBBC4C50BA4F5561003754C52@AIREMAIL.airespace.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Nov 2004 16:37:51.0309 (UTC) FILETIME=[F38FBFD0:01C4C8D5] 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: Fri, 12 Nov 2004 10:37:50 -0600 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: 7bit (a) Is the taxonomy draft the right place to be discussing dependencies of the capwap protocol/workplan? The objectives draft currently being developed seems to be a more appropriate place, since that is where the protocol objectives/requirements and presumably any dependencies will be discussed. So I'd suggest leaving just the description of the situation in the taxonomy draft, and including a statement of dependencies (if any) in the objectives draft. (b) Is a dependency required, and what is the nature of the dependency? That is, must a method be identified to enable a station to distinguish between a compromised PMK and one that is intentionally being shared, prior to completion of the CAPWAP protocol? Must the method be standardized? Right now, the CAPWAP milestones show a first draft of the CAPWAP protocol to be avalable Oct 05, with completion in March of 06. While having a standardized method in parallel is desirable, to be sure, it introduces a schedule dependency. Is it sufficient to have a method identified and in the process of being standardized, together with credible evidence that the proposed CAPWAP protocol does not prevent the proposed solution? Dorothy Bob O'Hara wrote: >Lily, > >I disagree with the statement near the end of Russ' text that "the >resolution must be completed before the CAPWAP working group can >complete its protocol development." This is one person's opinion. My >opinion is that, since Russ also grants that the solution to this >problem is outside the scope of CAPWAP, all that CAPWAP has to do is not >to develop a protocol that prevents the problem from being solved. > >I also don't see how this statement of opinion belongs in the taxonomy >document. The description of the problem and the way it is dealt with >by the centralized architecture belong in the document, but not the >opinion. > > -Bob > > >-----Original Message----- >From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On >Behalf Of Yang, Lily L >Sent: Friday, November 12, 2004 7:04 AM >To: capwap@frascone.com >Cc: Russ Housley; Walker, Jesse >Subject: [Capwap] Taxonomy v06 ready for review > > >Hi, >At the IETF CAPWAP meeting three days ago, Russ Housley provided >alternative text for 4.8.1, regarding PMK sharing issue. Here is the new >text from Russ: > > " If the STA and AC are the parties in the 4-way handshake (defined in > [4]), and 802.11i traffic encryption terminates at the WTP, then the > PTK (Pairwise Transient Key) has to be transferred from the AC to the > WTP. Since the keying material is part of the control and > provisioning of the WTPs, a secure encrypted tunnel for control > frames is employed to transport the keying material. > > The centralized model encourages AC implementations to use one PMK > for many different WTPs. This practice facilitates speedy transition > by a station from one WTP to another WTP that is connected to the > same AC without establishing a separate PMK. However, this leaves > the station in a difficult position. The station cannot distinguish > between a compromised PMK and one that is intentionally being shared. > This issue must be resolved. While the resolution is beyond the > scope of the CAPWAP working group; however, the resolution must be > completed before the CAPWAP working group can complete its protocol > development. The venue for this resolution is to be determined by > the IEEE 802 and IETF liaisons." > >A new version of the taxonomy draft which incorporated this new text is >available at http://www.capwap.org/draft-ietf-capwap-arch-06.txt >Please review by next Wed (Nov 17) as I would like to submit this draft >to IETF repository on Thursday for IESG review again. > >Thanks! > >Lily >_______________________________________________ >Capwap mailing list >Capwap@frascone.com >http://mail.frascone.com/mailman/listinfo/capwap >_______________________________________________ >Capwap mailing list >Capwap@frascone.com >http://mail.frascone.com/mailman/listinfo/capwap > > -- ---------------- Dorothy Stanley Agere Systems 2000 North Naperville Rd. Naperville, IL 60566 630-979-1572 (Phone, Fax) 630-222-6753 (Cell) _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Fri Nov 12 11:44:05 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 LAA18755 for ; Fri, 12 Nov 2004 11:44:05 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 86DBA1FC64; Fri, 12 Nov 2004 11:44:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 06CD31FCCE; Fri, 12 Nov 2004 11:44:03 -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 43B9F1FCCE for ; Fri, 12 Nov 2004 11:43:42 -0500 (EST) Received: from AIREMAIL.airespace.com (da001d3897.stl-mo.osd.concentric.net [66.236.111.57]) by mail.frascone.com (Postfix) with ESMTP id 4D9531FC64 for ; Fri, 12 Nov 2004 11:43:39 -0500 (EST) 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] Taxonomy v06 ready for review Message-ID: <55749BC69138654EBBC4C50BA4F55610036D5F88@AIREMAIL.airespace.com> Thread-Topic: [Capwap] Taxonomy v06 ready for review Thread-Index: AcTIy6KjtiJOMIXNRM2nJf6BO8EaSgAAjnOAAAIxC1A= From: "Pat R. Calhoun" To: "Bob O'Hara" , "Russ Housley" , "Yang, Lily L" , Cc: "Walker, Jesse" 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: Fri, 12 Nov 2004 08:43:39 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Perhaps we can address this in the objectives by stating that the protocol must be capable of handling whatever the outcome is. Basically, by pushing this functinality into the AC, it becomes transparent to the WTP and then becomes purely an implementation detail on the AC. PatC=20 -----Original Message----- From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On Behalf Of Bob O'Hara Sent: Friday, November 12, 2004 8:08 AM To: Russ Housley; Yang, Lily L; capwap@frascone.com Cc: Walker, Jesse Subject: RE: [Capwap] Taxonomy v06 ready for review Russ,=20 I think that stating the problem, as you have so eloquently done, is sufficient for the taxonomy draft, along with stating that it is not solved. The Objectives draft should include an objective of the to be developed protocol(s) that the solution to the problem must not be excluded by the protocol that is developed. =20 The protocol document should have a restatement of the problem and a description of what limitations, if any, the protocol places on how the problem might be solved. Possibly, the protocol document will reference another document where the solution to the problem is described. Does that make sense? -Bob =20 -----Original Message----- From: Russ Housley [mailto:housley@vigilsec.com] Sent: Friday, November 12, 2004 7:24 AM To: Bob O'Hara; Yang, Lily L; capwap@frascone.com Cc: Walker, Jesse Subject: RE: [Capwap] Taxonomy v06 ready for review Bob: How do we tell the reader about the dependency? I am certainly willing to=20 accept any words that do so. Russ At 10:15 AM 11/12/2004, Bob O'Hara wrote: >Lily, > >I disagree with the statement near the end of Russ' text that "the >resolution must be completed before the CAPWAP working group can >complete its protocol development." This is one person's opinion. My >opinion is that, since Russ also grants that the solution to this >problem is outside the scope of CAPWAP, all that CAPWAP has to do is not >to develop a protocol that prevents the problem from being solved. > >I also don't see how this statement of opinion belongs in the taxonomy >document. The description of the problem and the way it is dealt with >by the centralized architecture belong in the document, but not the >opinion. > > -Bob > > >-----Original Message----- >From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On >Behalf Of Yang, Lily L >Sent: Friday, November 12, 2004 7:04 AM >To: capwap@frascone.com >Cc: Russ Housley; Walker, Jesse >Subject: [Capwap] Taxonomy v06 ready for review > > >Hi, >At the IETF CAPWAP meeting three days ago, Russ Housley provided >alternative text for 4.8.1, regarding PMK sharing issue. Here is the new >text from Russ: > > " If the STA and AC are the parties in the 4-way handshake (defined in > [4]), and 802.11i traffic encryption terminates at the WTP, then the > PTK (Pairwise Transient Key) has to be transferred from the AC to the > WTP. Since the keying material is part of the control and > provisioning of the WTPs, a secure encrypted tunnel for control > frames is employed to transport the keying material. > > The centralized model encourages AC implementations to use one PMK > for many different WTPs. This practice facilitates speedy transition > by a station from one WTP to another WTP that is connected to the > same AC without establishing a separate PMK. However, this leaves > the station in a difficult position. The station cannot distinguish > between a compromised PMK and one that is intentionally being shared. > This issue must be resolved. While the resolution is beyond the > scope of the CAPWAP working group; however, the resolution must be > completed before the CAPWAP working group can complete its protocol > development. The venue for this resolution is to be determined by > the IEEE 802 and IETF liaisons." > >A new version of the taxonomy draft which incorporated this new text is >available at http://www.capwap.org/draft-ietf-capwap-arch-06.txt >Please review by next Wed (Nov 17) as I would like to submit this draft >to IETF repository on Thursday for IESG review again. > >Thanks! > >Lily >_______________________________________________ >Capwap mailing list >Capwap@frascone.com >http://mail.frascone.com/mailman/listinfo/capwap _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Fri Nov 12 11:53:06 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 LAA19778 for ; Fri, 12 Nov 2004 11:53:05 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id E5E191FC64; Fri, 12 Nov 2004 11:53:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id EC0361FCD1; Fri, 12 Nov 2004 11:53: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 C14FB1FCD1 for ; Fri, 12 Nov 2004 11:52:28 -0500 (EST) Received: from tierw.net.avaya.com (tierw.net.avaya.com [198.152.13.100]) by mail.frascone.com (Postfix) with ESMTP id C68601FC64 for ; Fri, 12 Nov 2004 11:52:26 -0500 (EST) Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iACGi92m015778 for ; Fri, 12 Nov 2004 11:44:09 -0500 (EST) Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iACGh22m014133 for ; Fri, 12 Nov 2004 11:43:20 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.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] Taxonomy v06 ready for review Message-ID: Thread-Topic: [Capwap] Taxonomy v06 ready for review Thread-Index: AcTI1iuJISQvQIj2S7GE37ECAiXmJwAAQY0A From: "Mani, Mahalingam (Mahalingam)" To: "Dorothy Stanley" , "Bob O'Hara" , "Yang, Lily L" , "Russ Housley" Cc: , "Walker, Jesse" 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: Fri, 12 Nov 2004 09:51:18 -0700 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable I tend to agree with Dorothy's suggestion on the stipulation being called out in Objectives draft (inasmuch as there is now going to be one) rather than in a taxonomy draft which has discovered the problem but does not do anything by stipulating how protocol should be developed - being informational document. However, the text can be suggestive of the need to resolve this to remove a hurdle when a protocol development happens. I think that is as well the sentiment of Russ (though I will let him confirm that) - that it not slip through the cracks - though it is too significant an issue for such a thing to happen. -mani -----Original Message----- From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On Behalf Of Dorothy Stanley Sent: Friday, November 12, 2004 8:38 AM To: Bob O'Hara; Yang, Lily L; Russ Housley Cc: capwap@frascone.com; Walker, Jesse Subject: Re: [Capwap] Taxonomy v06 ready for review (a) Is the taxonomy draft the right place to be discussing dependencies of the capwap protocol/workplan? The objectives draft currently being=20 developed seems to be a more appropriate place, since that is where the protocol objectives/requirements and presumably any dependencies will be discussed. So I'd suggest leaving just the description of the situation in the=20 taxonomy draft, and including a statement of dependencies (if any) in the objectives draft. (b) Is a dependency required, and what is the nature of the dependency? That is, must a method be identified to enable a station to distinguish between a compromised PMK and one that is intentionally=20 being shared, prior to completion of the CAPWAP protocol? Must the method be standardized? Right now, the CAPWAP milestones show a first draft of the CAPWAP=20 protocol to be avalable Oct 05, with completion in March of 06. While having a standardized method in=20 parallel is desirable, to be sure, it introduces a schedule dependency. Is it sufficient to have a method=20 identified and in the process of being standardized, together with credible evidence=20 that the proposed CAPWAP protocol does not prevent the proposed solution? Dorothy Bob O'Hara wrote: >Lily, > >I disagree with the statement near the end of Russ' text that "the >resolution must be completed before the CAPWAP working group can >complete its protocol development." This is one person's opinion. My >opinion is that, since Russ also grants that the solution to this >problem is outside the scope of CAPWAP, all that CAPWAP has to do is not >to develop a protocol that prevents the problem from being solved. > >I also don't see how this statement of opinion belongs in the taxonomy >document. The description of the problem and the way it is dealt with >by the centralized architecture belong in the document, but not the >opinion. > > -Bob >=20 > >-----Original Message----- >From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On >Behalf Of Yang, Lily L >Sent: Friday, November 12, 2004 7:04 AM >To: capwap@frascone.com >Cc: Russ Housley; Walker, Jesse >Subject: [Capwap] Taxonomy v06 ready for review > > >Hi,=20 >At the IETF CAPWAP meeting three days ago, Russ Housley provided >alternative text for 4.8.1, regarding PMK sharing issue. Here is the new >text from Russ: > > " If the STA and AC are the parties in the 4-way handshake (defined in > [4]), and 802.11i traffic encryption terminates at the WTP, then the > PTK (Pairwise Transient Key) has to be transferred from the AC to the > WTP. Since the keying material is part of the control and > provisioning of the WTPs, a secure encrypted tunnel for control > frames is employed to transport the keying material. > > The centralized model encourages AC implementations to use one PMK > for many different WTPs. This practice facilitates speedy transition > by a station from one WTP to another WTP that is connected to the > same AC without establishing a separate PMK. However, this leaves > the station in a difficult position. The station cannot distinguish > between a compromised PMK and one that is intentionally being shared. > This issue must be resolved. While the resolution is beyond the > scope of the CAPWAP working group; however, the resolution must be > completed before the CAPWAP working group can complete its protocol > development. The venue for this resolution is to be determined by > the IEEE 802 and IETF liaisons." > >A new version of the taxonomy draft which incorporated this new text is >available at http://www.capwap.org/draft-ietf-capwap-arch-06.txt >Please review by next Wed (Nov 17) as I would like to submit this draft >to IETF repository on Thursday for IESG review again. > >Thanks! > >Lily >_______________________________________________ >Capwap mailing list >Capwap@frascone.com >http://mail.frascone.com/mailman/listinfo/capwap >_______________________________________________ >Capwap mailing list >Capwap@frascone.com >http://mail.frascone.com/mailman/listinfo/capwap > =20 > --=20 ---------------- Dorothy Stanley Agere Systems 2000 North Naperville Rd.=20 Naperville, IL 60566 630-979-1572 (Phone, Fax) 630-222-6753 (Cell) _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Fri Nov 12 12:40: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 MAA23963 for ; Fri, 12 Nov 2004 12:40:06 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 5D4341FCD1; Fri, 12 Nov 2004 12:40:07 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id BF87A1FCD2; Fri, 12 Nov 2004 12:40:03 -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 447211FCD2 for ; Fri, 12 Nov 2004 12:39:40 -0500 (EST) Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100]) by mail.frascone.com (Postfix) with ESMTP id 585591FCD1 for ; Fri, 12 Nov 2004 12:39:37 -0500 (EST) Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iACHbjEr016303 for ; Fri, 12 Nov 2004 12:37:45 -0500 (EST) Received: from nj7460avexu2.global.avaya.com (h198-152-6-52.avaya.com [198.152.6.52]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iACHadEr015115 for ; Fri, 12 Nov 2004 12:36:57 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4C8DE.5D566BFA" Subject: RE: [Capwap] Taxonomy v06 ready for review Message-ID: <5844A41F4E146044A2E8356C63285880071235F3@nj7460avexu2.global.avaya.com> Thread-Topic: [Capwap] Taxonomy v06 ready for review Thread-Index: AcTIyN7arHJKGE6JT9KK3jwIo1Ml7QAFCIHA From: "Sadot, Emek (Emek)" To: "Yang, Lily L" , Cc: "Russ Housley" , "Walker, Jesse" 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: Fri, 12 Nov 2004 12:38:04 -0500 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) This is a multi-part message in MIME format. ------_=_NextPart_001_01C4C8DE.5D566BFA Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Lily, Russ, Sharing/caching PMK method can span across multiple ACs in the same BESS and still offers faster transaction from one WTP to another. Suggest rewording: 'This practice facilitates speedy transition by a station from one WTP to another WTP that is connected to the same or different AC in the same ESS without establishing a separate PMK' Emek -----Original Message----- From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On Behalf Of Yang, Lily L Sent: Friday, November 12, 2004 10:04 AM To: capwap@frascone.com Cc: Russ Housley; Walker, Jesse Subject: [Capwap] Taxonomy v06 ready for review Hi,=20 At the IETF CAPWAP meeting three days ago, Russ Housley provided alternative text for 4.8.1, regarding PMK sharing issue. Here is the new text from Russ: " If the STA and AC are the parties in the 4-way handshake (defined in [4]), and 802.11i traffic encryption terminates at the WTP, then the PTK (Pairwise Transient Key) has to be transferred from the AC to the WTP. Since the keying material is part of the control and provisioning of the WTPs, a secure encrypted tunnel for control frames is employed to transport the keying material. The centralized model encourages AC implementations to use one PMK for many different WTPs. This practice facilitates speedy transition by a station from one WTP to another WTP that is connected to the same AC without establishing a separate PMK. However, this leaves the station in a difficult position. The station cannot distinguish between a compromised PMK and one that is intentionally being shared. This issue must be resolved. While the resolution is beyond the scope of the CAPWAP working group; however, the resolution must be completed before the CAPWAP working group can complete its protocol development. The venue for this resolution is to be determined by the IEEE 802 and IETF liaisons." A new version of the taxonomy draft which incorporated this new text is available at http://www.capwap.org/draft-ietf-capwap-arch-06.txt Please review by next Wed (Nov 17) as I would like to submit this draft to IETF repository on Thursday for IESG review again. Thanks! Lily _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap ------_=_NextPart_001_01C4C8DE.5D566BFA Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable RE: [Capwap] Taxonomy v06 ready for review

Lily, Russ,

Sharing/caching PMK method can span across multiple ACs in the same = BESS and still offers faster transaction from one WTP to = another.

Suggest rewording: 'This practice facilitates speedy transition by = a station from one WTP to another WTP that is connected to the = same or different = AC in the same ESS without establishing a separate = PMK'

Emek

-----Original Message-----

From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.co= m] On Behalf Of Yang, Lily L

Sent: Friday, November 12, 2004 10:04 AM

To: capwap@frascone.com

Cc: Russ Housley; Walker, Jesse

Subject: [Capwap] Taxonomy v06 ready for review

Hi,

At = the IETF CAPWAP meeting three days ago, Russ Housley = provided

alternative text for 4.8.1, regarding PMK sharing issue. Here is = the new

text from Russ:

 "  If the STA and AC are the parties in the 4-way = handshake (defined in

   [4]), and 802.11i traffic encryption terminates at the = WTP, then the

   PTK (Pairwise Transient Key) has to be transferred = from the AC to the

   WTP.  Since the keying material is part of the = control and

   provisioning of the WTPs, a secure encrypted tunnel = for control

   frames is employed to transport the keying = material.

   The centralized model encourages AC implementations to = use one PMK

   for many different WTPs.  This practice = facilitates speedy transition

   by a station from one WTP to another WTP that is = connected to the

   same AC without establishing a separate PMK.  = However, this leaves

   the station in a difficult position.  The station = cannot distinguish

   between a compromised PMK and one that is = intentionally being shared.

   This issue must be resolved.  While the = resolution is beyond the

   scope of the CAPWAP working group; however, the = resolution must be

   completed before the CAPWAP working group can complete = its protocol

   development.  The venue for this resolution is to = be determined by

   the  IEEE 802 and IETF = liaisons."

A = new version of the taxonomy draft which incorporated this new text = is

available at http://www.c= apwap.org/draft-ietf-capwap-arch-06.txt

Please review by next Wed (Nov 17) as I would like to submit this = draft

to = IETF repository on Thursday for IESG review again.

Thanks!

Lily

_______________________________________________

Capwap mailing list

Capwap@frascone.com

http://mail.fra= scone.com/mailman/listinfo/capwap

------_=_NextPart_001_01C4C8DE.5D566BFA-- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Nov 15 12:30:09 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 MAA12952 for ; Mon, 15 Nov 2004 12:30:06 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 013861FC68; Mon, 15 Nov 2004 12:30:07 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 0D9EE1FC70; Mon, 15 Nov 2004 12:30:03 -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 3E4FA1FC70 for ; Mon, 15 Nov 2004 12:29:11 -0500 (EST) Received: from AIREMAIL.airespace.com (da001d3897.stl-mo.osd.concentric.net [66.236.111.57]) by mail.frascone.com (Postfix) with ESMTP id 1A52A1FC68 for ; Mon, 15 Nov 2004 12:29:08 -0500 (EST) 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] Taxonomy v06 ready for review Message-ID: <55749BC69138654EBBC4C50BA4F5561003754E0D@AIREMAIL.airespace.com> Thread-Topic: [Capwap] Taxonomy v06 ready for review Thread-Index: AcTLMPrMZIClF6QwRiWqnm3IlcBmbgACArsQ From: "Bob O'Hara" To: "Russ Housley" , "Yang, Lily L" , Cc: "Walker, Jesse" 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: Mon, 15 Nov 2004 09:28:36 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Russ, I like it. We will need to make sure that the issue moves forward to the objectives draft and, ultimately, to the protocol draft(s). -Bob =20 -----Original Message----- From: Russ Housley [mailto:housley@vigilsec.com]=20 Sent: Monday, November 15, 2004 10:31 AM To: Bob O'Hara; Yang, Lily L; capwap@frascone.com Cc: Walker, Jesse Subject: RE: [Capwap] Taxonomy v06 ready for review Bob: This makes sense to me. How about replacing the paragraph with: The centralized model encourages AC implementations to use one PMK for many different WTPs. This practice facilitates speedy transition by a station from one WTP to another WTP that is connected to the same AC without establishing a separate PMK. However, this leaves the station in a difficult position. The station cannot distinguish between a compromised PMK and one that is intentionally being shared. This issue must be resolved, but the resolution is beyond the scope of the CAPWAP working group. The venue for this resolution is to be determined by the IEEE 802 and IETF liaisons. Russ At 11:07 AM 11/12/2004, Bob O'Hara wrote: >Russ, > >I think that stating the problem, as you have so eloquently done, is >sufficient for the taxonomy draft, along with stating that it is not >solved. The Objectives draft should include an objective of the to be >developed protocol(s) that the solution to the problem must not be >excluded by the protocol that is developed. > >The protocol document should have a restatement of the problem and a >description of what limitations, if any, the protocol places on how the >problem might be solved. Possibly, the protocol document will reference >another document where the solution to the problem is described. > >Does that make sense? > > -Bob > > >-----Original Message----- >From: Russ Housley [mailto:housley@vigilsec.com] >Sent: Friday, November 12, 2004 7:24 AM >To: Bob O'Hara; Yang, Lily L; capwap@frascone.com >Cc: Walker, Jesse >Subject: RE: [Capwap] Taxonomy v06 ready for review > > >Bob: > >How do we tell the reader about the dependency? I am certainly willing >to >accept any words that do so. > >Russ > > >At 10:15 AM 11/12/2004, Bob O'Hara wrote: > >Lily, > > > >I disagree with the statement near the end of Russ' text that "the > >resolution must be completed before the CAPWAP working group can > >complete its protocol development." This is one person's opinion. My > >opinion is that, since Russ also grants that the solution to this > >problem is outside the scope of CAPWAP, all that CAPWAP has to do is >not > >to develop a protocol that prevents the problem from being solved. > > > >I also don't see how this statement of opinion belongs in the taxonomy > >document. The description of the problem and the way it is dealt with > >by the centralized architecture belong in the document, but not the > >opinion. > > > > -Bob > > > > > >-----Original Message----- > >From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On > >Behalf Of Yang, Lily L > >Sent: Friday, November 12, 2004 7:04 AM > >To: capwap@frascone.com > >Cc: Russ Housley; Walker, Jesse > >Subject: [Capwap] Taxonomy v06 ready for review > > > > > >Hi, > >At the IETF CAPWAP meeting three days ago, Russ Housley provided > >alternative text for 4.8.1, regarding PMK sharing issue. Here is the >new > >text from Russ: > > > > " If the STA and AC are the parties in the 4-way handshake (defined >in > > [4]), and 802.11i traffic encryption terminates at the WTP, then >the > > PTK (Pairwise Transient Key) has to be transferred from the AC to >the > > WTP. Since the keying material is part of the control and > > provisioning of the WTPs, a secure encrypted tunnel for control > > frames is employed to transport the keying material. > > > > The centralized model encourages AC implementations to use one PMK > > for many different WTPs. This practice facilitates speedy >transition > > by a station from one WTP to another WTP that is connected to the > > same AC without establishing a separate PMK. However, this leaves > > the station in a difficult position. The station cannot >distinguish > > between a compromised PMK and one that is intentionally being >shared. > > This issue must be resolved. While the resolution is beyond the > > scope of the CAPWAP working group; however, the resolution must be > > completed before the CAPWAP working group can complete its protocol > > development. The venue for this resolution is to be determined by > > the IEEE 802 and IETF liaisons." > > > >A new version of the taxonomy draft which incorporated this new text is > >available at http://www.capwap.org/draft-ietf-capwap-arch-06.txt > >Please review by next Wed (Nov 17) as I would like to submit this draft > >to IETF repository on Thursday for IESG review again. > > > >Thanks! > > > >Lily > >_______________________________________________ > >Capwap mailing list > >Capwap@frascone.com > >http://mail.frascone.com/mailman/listinfo/capwap _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Mon Nov 15 17:44:13 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 RAA21129 for ; Mon, 15 Nov 2004 17:44:08 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 7FAB31FC68; Mon, 15 Nov 2004 17:44:07 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 8CBF31FD40; Mon, 15 Nov 2004 17:44:03 -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 64EF71FD40 for ; Mon, 15 Nov 2004 17:43:57 -0500 (EST) Received: from AIREMAIL.airespace.com (da001d3897.stl-mo.osd.concentric.net [66.236.111.57]) by mail.frascone.com (Postfix) with ESMTP id C1E751FC68 for ; Mon, 15 Nov 2004 17:43:53 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4CB64.8ED7162F" Subject: RE: [Capwap] Taxonomy v06 ready for review Message-ID: <55749BC69138654EBBC4C50BA4F55610035951E2@AIREMAIL.airespace.com> Thread-Topic: [Capwap] Taxonomy v06 ready for review Thread-Index: AcTLMPrMZIClF6QwRiWqnm3IlcBmbgACArsQAArfJaY= From: "Pat R. Calhoun" To: "Bob O'Hara" , "Russ Housley" , "Yang, Lily L" , Cc: "Walker, Jesse" 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: Mon, 15 Nov 2004 14:43:21 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) This is a multi-part message in MIME format. ------_=_NextPart_001_01C4CB64.8ED7162F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I like the new text as well PatC -----Original Message----- From: capwap-admin@frascone.com on behalf of Bob O'Hara Sent: Mon 11/15/2004 9:28 AM To: Russ Housley; Yang, Lily L; capwap@frascone.com Cc: Walker, Jesse Subject: RE: [Capwap] Taxonomy v06 ready for review =20 Russ, I like it. We will need to make sure that the issue moves forward to the objectives draft and, ultimately, to the protocol draft(s). -Bob =20 -----Original Message----- From: Russ Housley [mailto:housley@vigilsec.com]=20 Sent: Monday, November 15, 2004 10:31 AM To: Bob O'Hara; Yang, Lily L; capwap@frascone.com Cc: Walker, Jesse Subject: RE: [Capwap] Taxonomy v06 ready for review Bob: This makes sense to me. How about replacing the paragraph with: The centralized model encourages AC implementations to use one PMK for many different WTPs. This practice facilitates speedy transition by a station from one WTP to another WTP that is connected to the same AC without establishing a separate PMK. However, this leaves the station in a difficult position. The station cannot distinguish between a compromised PMK and one that is intentionally being shared. This issue must be resolved, but the resolution is beyond the scope of the CAPWAP working group. The venue for this resolution is to be determined by the IEEE 802 and IETF liaisons. Russ At 11:07 AM 11/12/2004, Bob O'Hara wrote: >Russ, > >I think that stating the problem, as you have so eloquently done, is >sufficient for the taxonomy draft, along with stating that it is not >solved. The Objectives draft should include an objective of the to be >developed protocol(s) that the solution to the problem must not be >excluded by the protocol that is developed. > >The protocol document should have a restatement of the problem and a >description of what limitations, if any, the protocol places on how the >problem might be solved. Possibly, the protocol document will reference >another document where the solution to the problem is described. > >Does that make sense? > > -Bob > > >-----Original Message----- >From: Russ Housley [mailto:housley@vigilsec.com] >Sent: Friday, November 12, 2004 7:24 AM >To: Bob O'Hara; Yang, Lily L; capwap@frascone.com >Cc: Walker, Jesse >Subject: RE: [Capwap] Taxonomy v06 ready for review > > >Bob: > >How do we tell the reader about the dependency? I am certainly willing >to >accept any words that do so. > >Russ > > >At 10:15 AM 11/12/2004, Bob O'Hara wrote: > >Lily, > > > >I disagree with the statement near the end of Russ' text that "the > >resolution must be completed before the CAPWAP working group can > >complete its protocol development." This is one person's opinion. My > >opinion is that, since Russ also grants that the solution to this > >problem is outside the scope of CAPWAP, all that CAPWAP has to do is >not > >to develop a protocol that prevents the problem from being solved. > > > >I also don't see how this statement of opinion belongs in the taxonomy > >document. The description of the problem and the way it is dealt with > >by the centralized architecture belong in the document, but not the > >opinion. > > > > -Bob > > > > > >-----Original Message----- > >From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com] On > >Behalf Of Yang, Lily L > >Sent: Friday, November 12, 2004 7:04 AM > >To: capwap@frascone.com > >Cc: Russ Housley; Walker, Jesse > >Subject: [Capwap] Taxonomy v06 ready for review > > > > > >Hi, > >At the IETF CAPWAP meeting three days ago, Russ Housley provided > >alternative text for 4.8.1, regarding PMK sharing issue. Here is the >new > >text from Russ: > > > > " If the STA and AC are the parties in the 4-way handshake (defined >in > > [4]), and 802.11i traffic encryption terminates at the WTP, then >the > > PTK (Pairwise Transient Key) has to be transferred from the AC to >the > > WTP. Since the keying material is part of the control and > > provisioning of the WTPs, a secure encrypted tunnel for control > > frames is employed to transport the keying material. > > > > The centralized model encourages AC implementations to use one PMK > > for many different WTPs. This practice facilitates speedy >transition > > by a station from one WTP to another WTP that is connected to the > > same AC without establishing a separate PMK. However, this leaves > > the station in a difficult position. The station cannot >distinguish > > between a compromised PMK and one that is intentionally being >shared. > > This issue must be resolved. While the resolution is beyond the > > scope of the CAPWAP working group; however, the resolution must be > > completed before the CAPWAP working group can complete its protocol > > development. The venue for this resolution is to be determined by > > the IEEE 802 and IETF liaisons." > > > >A new version of the taxonomy draft which incorporated this new text is > >available at http://www.capwap.org/draft-ietf-capwap-arch-06.txt > >Please review by next Wed (Nov 17) as I would like to submit this draft > >to IETF repository on Thursday for IESG review again. > > > >Thanks! > > > >Lily > >_______________________________________________ > >Capwap mailing list > >Capwap@frascone.com > >http://mail.frascone.com/mailman/listinfo/capwap _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap ------_=_NextPart_001_01C4CB64.8ED7162F Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [Capwap] Taxonomy v06 ready for review

I like the new text as well

PatC


-----Original Message-----
From: capwap-admin@frascone.com on behalf of Bob O'Hara
Sent: Mon 11/15/2004 9:28 AM
To: Russ Housley; Yang, Lily L; capwap@frascone.com
Cc: Walker, Jesse
Subject: RE: [Capwap] Taxonomy v06 ready for review

Russ,

I like it.  We will need to make sure that the issue moves forward = to
the objectives draft and, ultimately, to the protocol draft(s).

 -Bob


-----Original Message-----
From: Russ Housley [mailto:housley@vigilsec.com]
= Sent: Monday, November 15, 2004 10:31 AM
To: Bob O'Hara; Yang, Lily L; capwap@frascone.com
Cc: Walker, Jesse
Subject: RE: [Capwap] Taxonomy v06 ready for review


Bob:

This makes sense to me.  How about replacing the paragraph = with:

    The centralized model encourages AC implementations = to use one PMK
    for many different WTPs.  This practice = facilitates speedy
transition
    by a station from one WTP to another WTP that is = connected to the
    same AC without establishing a separate PMK.  = However, this leaves
    the station in a difficult position.  The = station cannot distinguish
    between a compromised PMK and one that is = intentionally being
shared.
    This issue must be resolved, but the resolution is = beyond the scope
of
    the CAPWAP working group.  The venue for this = resolution is to be
    determined by the  IEEE 802 and IETF = liaisons.

Russ

At 11:07 AM 11/12/2004, Bob O'Hara wrote:
>Russ,
>
>I think that stating the problem, as you have so eloquently done, = is
>sufficient for the taxonomy draft, along with stating that it is = not
>solved.  The Objectives draft should include an objective of = the to be
>developed protocol(s) that the solution to the problem must not = be
>excluded by the protocol that is developed.
>
>The protocol document should have a restatement of the problem and = a
>description of what limitations, if any, the protocol places on how = the
>problem might be solved.  Possibly, the protocol document = will
reference
>another document where the solution to the problem is described.
>
>Does that make sense?
>
>  -Bob
>
>
>-----Original Message-----
>From: Russ Housley [mailto:housley@vigilsec.com]
= >Sent: Friday, November 12, 2004 7:24 AM
>To: Bob O'Hara; Yang, Lily L; capwap@frascone.com
>Cc: Walker, Jesse
>Subject: RE: [Capwap] Taxonomy v06 ready for review
>
>
>Bob:
>
>How do we tell the reader about the dependency?  I am certainly = willing
>to
>accept any words that do so.
>
>Russ
>
>
>At 10:15 AM 11/12/2004, Bob O'Hara wrote:
> >Lily,
> >
> >I disagree with the statement near the end of Russ' text that = "the
> >resolution must be completed before the CAPWAP working group = can
> >complete its protocol development."  This is one = person's opinion.
My
> >opinion is that, since Russ also grants that the solution to = this
> >problem is outside the scope of CAPWAP, all that CAPWAP has to = do is
>not
> >to develop a protocol that prevents the problem from being = solved.
> >
> >I also don't see how this statement of opinion belongs in = the
taxonomy
> >document.  The description of the problem and the way it = is dealt
with
> >by the centralized architecture belong in the document, but not = the
> >opinion.
> >
> >  -Bob
> >
> >
> >-----Original Message-----
> >From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.co= m] On
> >Behalf Of Yang, Lily L
> >Sent: Friday, November 12, 2004 7:04 AM
> >To: capwap@frascone.com
> >Cc: Russ Housley; Walker, Jesse
> >Subject: [Capwap] Taxonomy v06 ready for review
> >
> >
> >Hi,
> >At the IETF CAPWAP meeting three days ago, Russ Housley = provided
> >alternative text for 4.8.1, regarding PMK sharing issue. Here = is the
>new
> >text from Russ:
> >
> >  "  If the STA and AC are the parties in the = 4-way handshake
(defined
>in
> >    [4]), and 802.11i traffic encryption = terminates at the WTP, then
>the
> >    PTK (Pairwise Transient Key) has to be = transferred from the AC to
>the
> >    WTP.  Since the keying material is part = of the control and
> >    provisioning of the WTPs, a secure encrypted = tunnel for control
> >    frames is employed to transport the keying = material.
> >
> >    The centralized model encourages AC = implementations to use one
PMK
> >    for many different WTPs.  This practice = facilitates speedy
>transition
> >    by a station from one WTP to another WTP = that is connected to the
> >    same AC without establishing a separate = PMK.  However, this
leaves
> >    the station in a difficult position.  = The station cannot
>distinguish
> >    between a compromised PMK and one that is = intentionally being
>shared.
> >    This issue must be resolved.  While the = resolution is beyond the
> >    scope of the CAPWAP working group; however, = the resolution must
be
> >    completed before the CAPWAP working group = can complete its
protocol
> >    development.  The venue for this = resolution is to be determined
by
> >    the  IEEE 802 and IETF = liaisons."
> >
> >A new version of the taxonomy draft which incorporated this new = text
is
> >available at http://www.c= apwap.org/draft-ietf-capwap-arch-06.txt
> >Please review by next Wed (Nov 17) as I would like to submit = this
draft
> >to IETF repository on Thursday for IESG review again.
> >
> >Thanks!
> >
> >Lily
> >_______________________________________________
> >Capwap mailing list
> >Capwap@frascone.com
> >http://mail.fra= scone.com/mailman/listinfo/capwap

_______________________________________________
Capwap mailing list
Capwap@frascone.com
http://mail.fra= scone.com/mailman/listinfo/capwap

------_=_NextPart_001_01C4CB64.8ED7162F-- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Tue Nov 16 10:37:12 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 KAA10736 for ; Tue, 16 Nov 2004 10:37:11 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 6E9751FCC8; Tue, 16 Nov 2004 10:37:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id C47841FC79; Tue, 16 Nov 2004 10:37: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 02ECB1FC79 for ; Tue, 16 Nov 2004 10:36:19 -0500 (EST) Received: from orsfmr005.jf.intel.com (fmr20.intel.com [134.134.136.19]) by mail.frascone.com (Postfix) with ESMTP id 562C61FC0E for ; Tue, 16 Nov 2004 10:36:16 -0500 (EST) Received: from orsfmr100.jf.intel.com (orsfmr100.jf.intel.com [10.7.209.16]) by orsfmr005.jf.intel.com (8.12.10/8.12.10/d: major-outer.mc,v 1.1 2004/09/17 17:50:56 root Exp $) with ESMTP id iAGFaFDh023690; Tue, 16 Nov 2004 15:36:15 GMT Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by orsfmr100.jf.intel.com (8.12.10/8.12.10/d: major-inner.mc,v 1.2 2004/09/17 18:05:01 root Exp $) with SMTP id iAGFa45C032061; Tue, 16 Nov 2004 15:36:15 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 M2004111607361206851 ; Tue, 16 Nov 2004 07:36:12 -0800 Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 16 Nov 2004 07:36:13 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <2AF68A477DD44C4EBCBE338C24E7A9EE02B7F94D@orsmsx408> Thread-Topic: concluding taxonomy draft v06 -- plan to submit tomorrow Thread-Index: AcTLMQQKkOHkkz3ZQ725aTlH3xAfVwAVofcwABpeTNA= From: "Yang, Lily L" To: Cc: "Russ Housley" , "Walker, Jesse" X-OriginalArrivalTime: 16 Nov 2004 15:36:13.0073 (UTC) FILETIME=[00E4B810:01C4CBF2] X-Scanned-By: MIMEDefang 2.44 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] concluding taxonomy draft v06 -- plan to submit tomorrow 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, 16 Nov 2004 07:36:07 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Ok. I updated the taxonomy draft to reflect the most recent consensus on this issue. Check out the new text at=20 http://www.capwap.org/draft-ietf-capwap-arch-06.txt The change log at: http://www.capwap.org/change-log-for-v06-fromv05.txt Now section 5.8.1 reads: If the STA and AC are the parties in the 4-way handshake (defined in [4]), and 802.11i traffic encryption terminates at the WTP, then the PTK (Pairwise Transient Key) has to be transferred from the AC to the WTP. Since the keying material is part of the control and provisioning of the WTPs, a secure encrypted tunnel for control frames is employed to transport the keying material. The centralized model encourages AC implementations to use one PMK for many different WTPs. This practice facilitates speedy transition by a station from one WTP to another WTP that is connected to the same AC without establishing a separate PMK. However, this leaves the station in a difficult position. The station cannot distinguish between a compromised PMK and one that is intentionally being shared. This issue must be resolved, but the resolution is beyond the scope of the CAPWAP working group. The venue for this resolution is to be determined by the IEEE 802 and IETF liaisons. If no other objection, I plan to submit this version to IETF repository tomorrow. Thanks! Lily _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Wed Nov 17 05:07:06 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 FAA07484 for ; Wed, 17 Nov 2004 05:07:06 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 6F3B01FC78; Wed, 17 Nov 2004 05:07:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id A6C8C1FCBA; Wed, 17 Nov 2004 05:07: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 644A51FCBA for ; Wed, 17 Nov 2004 05:06:11 -0500 (EST) Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27]) by mail.frascone.com (Postfix) with ESMTP id 17EDA1FC78 for ; Wed, 17 Nov 2004 05:06:08 -0500 (EST) Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id iAHA62E21209; Wed, 17 Nov 2004 12:06:03 +0200 (EET) X-Scanned: Wed, 17 Nov 2004 12:04:53 +0200 Nokia Message Protector V1.3.31 2004060815 - RELEASE Received: (from root@localhost) by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iAHA4rlg016570; Wed, 17 Nov 2004 12:04:53 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks001.ntc.nokia.com 0057mfd2; Wed, 17 Nov 2004 12:04:51 EET 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 iAHA2Ya19754; Wed, 17 Nov 2004 12:02:34 +0200 (EET) Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 17 Nov 2004 04:02:34 -0600 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 Subject: RE: [Capwap] concluding taxonomy draft v06 -- plan to submit tomorrow Message-ID: Thread-Topic: concluding taxonomy draft v06 -- plan to submit tomorrow Thread-Index: AcTLMQQKkOHkkz3ZQ725aTlH3xAfVwAVofcwABpeTNAAAOe0MA== From: To: , Cc: , X-OriginalArrivalTime: 17 Nov 2004 10:02:34.0006 (UTC) FILETIME=[8F034360:01C4CC8C] 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, 17 Nov 2004 02:02:32 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Ok with me. -Dorothy > -----Original Message----- > From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com]On > Behalf Of ext Yang, Lily L > Sent: Tuesday, November 16, 2004 7:36 AM > To: capwap@frascone.com > Cc: Russ Housley; Walker, Jesse > Subject: [Capwap] concluding taxonomy draft v06 -- plan to submit > tomorrow >=20 >=20 > Ok. I updated the taxonomy draft to reflect the most recent=20 > consensus on > this issue. Check out the new text at=20 > http://www.capwap.org/draft-ietf-capwap-arch-06.txt > The change log at: > http://www.capwap.org/change-log-for-v06-fromv05.txt >=20 > Now section 5.8.1 reads: >=20 > If the STA and AC are the parties in the 4-way handshake=20 > (defined in > [4]), and 802.11i traffic encryption terminates at the=20 > WTP, then the > PTK (Pairwise Transient Key) has to be transferred from=20 > the AC to the > WTP. Since the keying material is part of the control and > provisioning of the WTPs, a secure encrypted tunnel for control > frames is employed to transport the keying material. >=20 > The centralized model encourages AC implementations to use one PMK > for many different WTPs. This practice facilitates speedy=20 > transition > by a station from one WTP to another WTP that is connected to the > same AC without establishing a separate PMK. However, this leaves > the station in a difficult position. The station cannot=20 > distinguish > between a compromised PMK and one that is intentionally=20 > being shared. > This issue must be resolved, but the resolution is beyond the scope > of the CAPWAP working group. The venue for this=20 > resolution is to be > determined by the IEEE 802 and IETF liaisons. >=20 > If no other objection, I plan to submit this version to IETF=20 > repository > tomorrow. >=20 > Thanks! > Lily >=20 >=20 > _______________________________________________ > Capwap mailing list > Capwap@frascone.com > http://mail.frascone.com/mailman/listinfo/capwap >=20 _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Wed Nov 17 07:30:08 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 HAA21821 for ; Wed, 17 Nov 2004 07:30:07 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 811101FC78; Wed, 17 Nov 2004 07:30:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id B68401FD53; Wed, 17 Nov 2004 07:30: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 867E71FD53 for ; Wed, 17 Nov 2004 07:29:22 -0500 (EST) Received: from AIREMAIL.airespace.com (da001d3897.stl-mo.osd.concentric.net [66.236.111.57]) by mail.frascone.com (Postfix) with ESMTP id 7CE581FC78 for ; Wed, 17 Nov 2004 07:29:19 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4CCA1.04C947B7" Subject: RE: [Capwap] concluding taxonomy draft v06 -- plan to submit tomorrow Message-ID: <55749BC69138654EBBC4C50BA4F5561003595259@AIREMAIL.airespace.com> Thread-Topic: concluding taxonomy draft v06 -- plan to submit tomorrow Thread-Index: AcTLMQQKkOHkkz3ZQ725aTlH3xAfVwAVofcwABpeTNAAAOe0MAArFujy From: "Pat R. Calhoun" To: , , Cc: , 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, 17 Nov 2004 04:28:52 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) This is a multi-part message in MIME format. ------_=_NextPart_001_01C4CCA1.04C947B7 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Works for me too PatC -----Original Message----- From: capwap-admin@frascone.com on behalf of Dorothy.Gellert@nokia.com Sent: Wed 11/17/2004 2:02 AM To: lily.l.yang@intel.com; capwap@frascone.com Cc: housley@vigilsec.com; jesse.walker@intel.com Subject: RE: [Capwap] concluding taxonomy draft v06 -- plan to submit = tomorrow =20 Ok with me. -Dorothy > -----Original Message----- > From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com]On > Behalf Of ext Yang, Lily L > Sent: Tuesday, November 16, 2004 7:36 AM > To: capwap@frascone.com > Cc: Russ Housley; Walker, Jesse > Subject: [Capwap] concluding taxonomy draft v06 -- plan to submit > tomorrow >=20 >=20 > Ok. I updated the taxonomy draft to reflect the most recent=20 > consensus on > this issue. Check out the new text at=20 > http://www.capwap.org/draft-ietf-capwap-arch-06.txt > The change log at: > http://www.capwap.org/change-log-for-v06-fromv05.txt >=20 > Now section 5.8.1 reads: >=20 > If the STA and AC are the parties in the 4-way handshake=20 > (defined in > [4]), and 802.11i traffic encryption terminates at the=20 > WTP, then the > PTK (Pairwise Transient Key) has to be transferred from=20 > the AC to the > WTP. Since the keying material is part of the control and > provisioning of the WTPs, a secure encrypted tunnel for control > frames is employed to transport the keying material. >=20 > The centralized model encourages AC implementations to use one PMK > for many different WTPs. This practice facilitates speedy=20 > transition > by a station from one WTP to another WTP that is connected to the > same AC without establishing a separate PMK. However, this leaves > the station in a difficult position. The station cannot=20 > distinguish > between a compromised PMK and one that is intentionally=20 > being shared. > This issue must be resolved, but the resolution is beyond the scope > of the CAPWAP working group. The venue for this=20 > resolution is to be > determined by the IEEE 802 and IETF liaisons. >=20 > If no other objection, I plan to submit this version to IETF=20 > repository > tomorrow. >=20 > Thanks! > Lily >=20 >=20 > _______________________________________________ > Capwap mailing list > Capwap@frascone.com > http://mail.frascone.com/mailman/listinfo/capwap >=20 _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap ------_=_NextPart_001_01C4CCA1.04C947B7 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [Capwap] concluding taxonomy draft v06 -- plan to submit = tomorrow

Works for me too

PatC

-----Original Message-----
From: capwap-admin@frascone.com on behalf of = Dorothy.Gellert@nokia.com
Sent: Wed 11/17/2004 2:02 AM
To: lily.l.yang@intel.com; capwap@frascone.com
Cc: housley@vigilsec.com; jesse.walker@intel.com
Subject: RE: [Capwap] concluding taxonomy draft v06 -- plan to submit = tomorrow

Ok with me.

-Dorothy


> -----Original Message-----
> From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.co= m]On
> Behalf Of ext Yang, Lily L
> Sent: Tuesday, November 16, 2004 7:36 AM
> To: capwap@frascone.com
> Cc: Russ Housley; Walker, Jesse
> Subject: [Capwap] concluding taxonomy draft v06 -- plan to = submit
> tomorrow
>
>
> Ok. I updated the taxonomy draft to reflect the most recent
> consensus on
> this issue. Check out the new text at
> http://www.c= apwap.org/draft-ietf-capwap-arch-06.txt
> The change log at:
> http://www.= capwap.org/change-log-for-v06-fromv05.txt
>
> Now section 5.8.1 reads:
>
>    If the STA and AC are the parties in the 4-way = handshake
> (defined in
>    [4]), and 802.11i traffic encryption terminates = at the
> WTP, then the
>    PTK (Pairwise Transient Key) has to be = transferred from
> the AC to the
>    WTP.  Since the keying material is part of = the control and
>    provisioning of the WTPs, a secure encrypted = tunnel for control
>    frames is employed to transport the keying = material.
>
>    The centralized model encourages AC = implementations to use one PMK
>    for many different WTPs.  This practice = facilitates speedy
> transition
>    by a station from one WTP to another WTP that is = connected to the
>    same AC without establishing a separate = PMK.  However, this leaves
>    the station in a difficult position.  The = station cannot
> distinguish
>    between a compromised PMK and one that is = intentionally
> being shared.
>    This issue must be resolved, but the resolution = is beyond the scope
>    of the CAPWAP working group.  The venue for = this
> resolution is to be
>    determined by the  IEEE 802 and IETF = liaisons.
>
> If no other objection, I plan to submit this version to IETF
> repository
> tomorrow.
>
> Thanks!
> Lily
>
>
> _______________________________________________
> Capwap mailing list
> Capwap@frascone.com
> http://mail.fra= scone.com/mailman/listinfo/capwap
>
_______________________________________________
Capwap mailing list
Capwap@frascone.com
http://mail.fra= scone.com/mailman/listinfo/capwap

------_=_NextPart_001_01C4CCA1.04C947B7-- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Thu Nov 18 15:15:08 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 PAA01412 for ; Thu, 18 Nov 2004 15:15:08 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id C153E1FD47; Thu, 18 Nov 2004 15:15:07 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 994331FD4D; Thu, 18 Nov 2004 15:15:03 -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 A41B61FD4D for ; Thu, 18 Nov 2004 15:14:15 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mail.frascone.com (Postfix) with ESMTP id 597211FD47 for ; Thu, 18 Nov 2004 15:14:12 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01143; Thu, 18 Nov 2004 15:14:09 -0500 (EST) Message-Id: <200411182014.PAA01143@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-06.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: Thu, 18 Nov 2004 15:14:09 -0500 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-06.txt Pages : 44 Date : 2004-11-18 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-capwap-arch-06.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-06.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-06.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-11-18141727.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-capwap-arch-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-capwap-arch-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-11-18141727.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 Nov 18 18:33:09 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 SAA03614 for ; Thu, 18 Nov 2004 18:33:08 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 98B3E1FD62; Thu, 18 Nov 2004 18:33:07 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 118F51FD63; Thu, 18 Nov 2004 18:33: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 5ABCF1FD63 for ; Thu, 18 Nov 2004 18:32:31 -0500 (EST) Received: from tierw.net.avaya.com (tierw.net.avaya.com [198.152.13.100]) by mail.frascone.com (Postfix) with ESMTP id 591AF1FD62 for ; Thu, 18 Nov 2004 18:32:28 -0500 (EST) Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iAINO5lN009924 for ; Thu, 18 Nov 2004 18:24:05 -0500 (EST) Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iAINJHlN004357 for ; Thu, 18 Nov 2004 18:20:24 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4CDC5.CAE5E272" Message-ID: Thread-Topic: Taxonomy draft-06 revision and readying for IESG. Thread-Index: AcTNxcmY9cITDytcTJya9c/JRdY7Kg== X-Priority: 1 Priority: Urgent Importance: high From: "Mani, Mahalingam (Mahalingam)" To: X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Taxonomy draft-06 revision and readying for IESG. 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, 18 Nov 2004 16:24:46 -0700 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) This is a multi-part message in MIME format. ------_=_NextPart_001_01C4CDC5.CAE5E272 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All: =20 The draft-ietf-capwap-arch-06.txt is now in repository incorporating responses to IESG review comments; they are already well discussed in the WG list. The changes have been well delineated in the list by the Editor(s). =20 We believe the WG is OK with this new revision (that basically addresses IESG review comments and reflects WG position and consensus) and so unless anyone objects within the next four days, then we'll send this revision to IESG on Monday the 22nd Nov 2004. If anyone absolutely needs more time to review (and is committed to indeed review), then do speak up. =20 Thanks, -mani -Dorothy =3D=3D=3D=3D Mahalingam Mani ------_=_NextPart_001_01C4CDC5.CAE5E272 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All:

 

The draft-ietf-capwap-arch-06.txt is now in = repository incorporating responses to IESG review comments; they are already well discussed in the WG list. The changes have been well delineated in the = list by the Editor(s).

 

We believe the WG is OK with this new revision (that basically addresses IESG review comments and reflects WG position and = consensus) and so unless anyone objects within the next four days, then we'll send = this revision to IESG on Monday the 22nd Nov 2004. If anyone = absolutely needs more time to review (and is committed to indeed review), then do = speak up.

 

Thanks,

-mani

-Dorothy

=3D=3D=3D=3D

Mahalingam Mani

------_=_NextPart_001_01C4CDC5.CAE5E272-- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Tue Nov 23 16:01: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 QAA28668 for ; Tue, 23 Nov 2004 16:01:07 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 7103B1FCB8; Tue, 23 Nov 2004 16:01:07 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 7CFFC1FD45; Tue, 23 Nov 2004 16:01:03 -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 9BEBE1FD45 for ; Tue, 23 Nov 2004 16:00:07 -0500 (EST) Received: from caduceus.jf.intel.com (fmr06.intel.com [134.134.136.7]) by mail.frascone.com (Postfix) with ESMTP id E9DAE1FCB8 for ; Tue, 23 Nov 2004 16:00:05 -0500 (EST) Received: from orsfmr100.jf.intel.com (orsfmr100.jf.intel.com [10.7.209.16]) by caduceus.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 iANL0BO3020464 for ; Tue, 23 Nov 2004 21:00:11 GMT Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by orsfmr100.jf.intel.com (8.12.10/8.12.10/d: major-inner.mc,v 1.2 2004/09/17 18:05:01 root Exp $) with SMTP id iANL00Ht032717 for ; Tue, 23 Nov 2004 21:00:04 GMT Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs040.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004112313000427597 for ; Tue, 23 Nov 2004 13:00:04 -0800 Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 23 Nov 2004 13:00:03 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <2AF68A477DD44C4EBCBE338C24E7A9EE02CC56D0@orsmsx408> Thread-Topic: Objective contribution from Zhou et al. Thread-Index: AcTRn2ai44Ta2Z3nSqiRzQ5AWOd7IQ== From: "Yang, Lily L" To: X-OriginalArrivalTime: 23 Nov 2004 21:00:04.0108 (UTC) FILETIME=[67959CC0:01C4D19F] X-Scanned-By: MIMEDefang 2.44 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Objective contribution from Zhou et al. 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, 23 Nov 2004 13:00:02 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Hi,=20 The individual contribution on CAPWAP Objectives by Zhou et al. is now officially submitted and accepted into the IETF repository: http://www.ietf.org/internet-drafts/draft-zhou-capwap-objectives-00.txt As agreed in the IETF meeting at Washington DC, the team is actively working with the other group from Panasonic that submitted draft-govindan-capwap-objectives-00.txt to merge the two drafts together. The merged version of Objectives draft will be available in the very near future. We encourage everyone on the list to voice their opinions on the subject of CAPWAP Objectives and/or comments on the two individual drafts so that we can incorporate them into the merged draft as well. Thanks, Lily _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Tue Nov 23 17:39: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 RAA14796 for ; Tue, 23 Nov 2004 17:39:06 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id BA3761FCB8; Tue, 23 Nov 2004 17:39:07 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 657C41FD45; Tue, 23 Nov 2004 17:39:03 -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 503B01FD45 for ; Tue, 23 Nov 2004 17:38:42 -0500 (EST) Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100]) by mail.frascone.com (Postfix) with ESMTP id 7F4811FCB8 for ; Tue, 23 Nov 2004 17:38:40 -0500 (EST) Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iANMaaZ4006047 for ; Tue, 23 Nov 2004 17:36:37 -0500 (EST) Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iANMY3Z4003111 for ; Tue, 23 Nov 2004 17:34:36 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4D1AC.CCBC5CCC" Message-ID: Thread-Topic: the short lastcall on draft-ietf-capwap-arch-06.txt ended Thread-Index: AcTRrMpTa2RgAVyQRcuJeVHn6dmKog== X-Priority: 1 Priority: Urgent Importance: high From: "Mani, Mahalingam (Mahalingam)" To: X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] the short lastcall on draft-ietf-capwap-arch-06.txt ended 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, 23 Nov 2004 15:35:57 -0700 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) This is a multi-part message in MIME format. ------_=_NextPart_001_01C4D1AC.CCBC5CCC Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The short last-call for draft-ietf-capwap-arch-06.txt ended yesterday. We will be re-submitting for IESG review and Consideration for publication as informational RFC. =20 -Mani, Dorothy ------_=_NextPart_001_01C4D1AC.CCBC5CCC Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The short last-call for draft-ietf-capwap-arch-06.txt = ended yesterday. We will be re-submitting for IESG review = and

Consideration for publication as informational = RFC.

 

-Mani, Dorothy

------_=_NextPart_001_01C4D1AC.CCBC5CCC-- _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Tue Nov 23 18:27:05 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 SAA19724 for ; Tue, 23 Nov 2004 18:27:04 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id B063E1FDF3; Tue, 23 Nov 2004 18:27:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 45B3F1FD47; Tue, 23 Nov 2004 18:27:03 -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 746DD1FD47 for ; Tue, 23 Nov 2004 18:26:24 -0500 (EST) Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by mail.frascone.com (Postfix) with ESMTP id D619E1FCB8 for ; Tue, 23 Nov 2004 18:26:22 -0500 (EST) Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1CWjtr-0005lu-KI; Tue, 23 Nov 2004 18:16:43 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Cc: Internet Architecture Board , RFC Editor , capwap mailing list , capwap chair , capwap chair Message-Id: X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Subject: [Capwap] Document Action: 'Architecture Taxonomy for Control and Provisioning of Wireless Access Points(CAPWAP)' to Informational RFC 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, 23 Nov 2004 18:16:43 -0500 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) The IESG has approved the following document: - 'Architecture Taxonomy for Control and Provisioning of Wireless Access Points(CAPWAP) ' as an Informational RFC This document is the product of the Control And Provisioning of Wireless Access Points Working Group. The IESG contact persons are Bert Wijnen and David Kessens. Technical Summary 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. Working Group Summary The working group has consensus to publish this document as an Informational RFC. The document was also submitted to IEEE 802.11 for review and feedback has been incorporated. Protocol Quality Bert wijnen has reviewed this document for the IESG. _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap From capwap-admin@frascone.com Tue Nov 23 22:02:10 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 WAA06390 for ; Tue, 23 Nov 2004 22:02:09 -0500 (EST) Received: from localhost (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id EDB121FCB8; Tue, 23 Nov 2004 22:02:06 -0500 (EST) Received: from xavier (xavier [127.0.0.1]) by mail.frascone.com (Postfix) with ESMTP id 5BC991FD4C; Tue, 23 Nov 2004 22:02:03 -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 B73CD1FD4C for ; Tue, 23 Nov 2004 22:01:55 -0500 (EST) Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21]) by mail.frascone.com (Postfix) with ESMTP id C239E1FCB8 for ; Tue, 23 Nov 2004 22:01:53 -0500 (EST) Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id iAO31mv02041; Wed, 24 Nov 2004 05:01:50 +0200 (EET) X-Scanned: Wed, 24 Nov 2004 05:03:12 +0200 Nokia Message Protector V1.3.31 2004060815 - RELEASE Received: (from root@localhost) by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iAO33ChX000977; Wed, 24 Nov 2004 05:03:12 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks001.ntc.nokia.com 008EcvAs; Wed, 24 Nov 2004 05:03:11 EET Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com [10.241.35.122]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id iAO2jea18865; Wed, 24 Nov 2004 04:45:40 +0200 (EET) Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 23 Nov 2004 20:45:15 -0600 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 Subject: RE: [Capwap] Objective contribution from Zhou et al. Message-ID: Thread-Topic: Objective contribution from Zhou et al. Thread-Index: AcTRn2ai44Ta2Z3nSqiRzQ5AWOd7IQAKi4Fg From: To: , Cc: , , , , , , X-OriginalArrivalTime: 24 Nov 2004 02:45:15.0491 (UTC) FILETIME=[A087DB30:01C4D1CF] 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: Tue, 23 Nov 2004 18:45:13 -0800 X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com) Content-Transfer-Encoding: quoted-printable Hi Lily- I think you may have misunderstood the action item at the last IETF = meeting. Mani and I have asked the authors of both drafts to agree upon = an editor and combine the drafts going forward. We need to have a = single point of contact with the editor since the Objectives draft is a = critical milestone in our WG. =20 If the authors of the 2 Objectives drafts can not come to an agreement, = then we will have to appoint an editor going forward. Since both of = these drafts have so much in common, I hope that the authors can also = agree to nominate an editor. =20 Keep in mind the editor of the Objectives draft will have to be = available and willing to put in the time required to meet the milestones = dates. =20 Let me or Mani know if anyone has further questions. BTW, the Zhou draft does not include an author contact list, so I = apologize if this email does not go directly to all the authors of the = zhou draft! Thanks, Dorothy > -----Original Message----- > From: capwap-admin@frascone.com [mailto:capwap-admin@frascone.com]On > Behalf Of ext Yang, Lily L > Sent: Tuesday, November 23, 2004 1:00 PM > To: capwap@frascone.com > Subject: [Capwap] Objective contribution from Zhou et al. >=20 >=20 > Hi,=20 > The individual contribution on CAPWAP Objectives by Zhou et al. is now > officially submitted and accepted into the IETF repository: > http://www.ietf.org/internet-drafts/draft-zhou-capwap-objectiv es-00.txt As agreed in the IETF meeting at Washington DC, the team is actively working with the other group from Panasonic that submitted draft-govindan-capwap-objectives-00.txt to merge the two drafts together. The merged version of Objectives draft will be available in the very near future. We encourage everyone on the list to voice their opinions on the subject of CAPWAP Objectives and/or comments on the two individual drafts so that we can incorporate them into the merged draft as well. Thanks, Lily _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap _______________________________________________ Capwap mailing list Capwap@frascone.com http://mail.frascone.com/mailman/listinfo/capwap