From xml-bounces+capwap-archive=lists.ietf.org@frascone.com  Sat Mar  1 06:13:47 2008
Return-Path: <xml-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 77AB929473F
	for <ietfarch-capwap-archive@core3.amsl.com>; Sat,  1 Mar 2008 06:06:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.763
X-Spam-Level: 
X-Spam-Status: No, score=-1.763 tagged_above=-999 required=5 tests=[AWL=0.836,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 13s9m8k8wIOO
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Sat,  1 Mar 2008 06:06:28 -0800 (PST)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id A55A828D744
	for <capwap-archive@lists.ietf.org>; Sat,  1 Mar 2008 05:31:00 -0800 (PST)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id F19901A8D98E
	for <capwap-archive@lists.ietf.org>; Sat,  1 Mar 2008 05:30:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: frascone.com mailing list memberships reminder
From: xml-owner@frascone.com
X-No-Archive: yes
Message-ID: <mailman.891.1204378215.6664.xml@frascone.com>
Date: Sat, 01 Mar 2008 05:30:15 -0800
Precedence: bulk
X-BeenThere: xml@frascone.com
X-Mailman-Version: 2.1.9
List-Id: Diameter XML Dictionary Design Team List -- CLOSED -- ARCHIVES ONLY
	<xml.frascone.com>
X-List-Administrivia: yes
To: capwap-archive@lists.ietf.org
Errors-To: xml-bounces+capwap-archive=lists.ietf.org@frascone.com

This is a monthly reminder about your frascone.com mailing list
memberships. It shows the lists you are subscribed to, your passwords,
and a Web page URL you can use to manage your subscriptions.

Visit the Web page URL shown below to unsubscribe, change your e-mail
address, temporarily disable your subscription for a vacation, set
digest-style delivery, and so on.

You can also use e-mail to make changes. For more info, send a message
to the '-request' address of the list (for example,
xml-request@frascone.com) containing just the word 'help' in the
message body. An e-mail message will be sent to you with instructions.

Here is the subscription information for
capwap-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
capwap@frascone.com                      ugimni    
http://lists.frascone.com/mailman/options/capwap/capwap-archive%40lists.ietf.org


From alexsd@att.com  Sun Mar  9 08:23:15 2008
Return-Path: <alexsd@att.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 34AAA3A6B9B
	for <ietfarch-capwap-archive@core3.amsl.com>; Sun,  9 Mar 2008 08:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -31.97
X-Spam-Level: 
X-Spam-Status: No, score=-31.97 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, DOS_OE_TO_MX=2.75, FH_HELO_ALMOST_IP=5.417,
	FH_HOST_ALMOST_IP=1.889, GB_ROLEX=5, HELO_EQ_FR=0.35,
	HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=1,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905,
	URIBL_BLACK=20, URIBL_RHS_DOB=1.083, URIBL_SBL=20,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OrVhfDnSjzdJ
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Sun,  9 Mar 2008 08:23:14 -0700 (PDT)
Received: from ip-79.net-89-2-202.rev.numericable.fr (ip-79.net-89-2-202.rev.numericable.fr [89.2.202.79])
	by core3.amsl.com (Postfix) with ESMTP id D13E33A6881
	for <capwap-archive@ietf.org>; Sun,  9 Mar 2008 08:23:13 -0700 (PDT)
Message-ID: <000a01c881f9$01960356$f052d2ab@iidawp>
From: "gauthier bennett" <alexsd@att.com>
To: <capwap-archive@ietf.org>
Subject: Hermes
Date: Sun, 09 Mar 2008 13:33:32 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C881F9.0194B037"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C881F9.0194B037
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

              Prestige
replicas
 
            Most popular       watches
      Rolex Datejusts=95Rolex Sports Models=95Cartier=95Hublot=95Panerai =
=95Chanel=95Jacob &amp;       Co=95Patek=95Philippe Alain =
Silberstein=95Chopard=95Jaeger=95LeCoutrePorsche=95Design      =20
 
            Most popular TIFFANY &amp; CO.       JEWERLY
      Tiffany &amp; CO       Bracelets=95Tiffany &amp; CO =
Necklace=95Tiffany &amp; CO Earings
 
            Most popular PENS
      Mont Blanc       Ballpoint=95Louis Vuitton Rollerball=95St Dupont =
Fountain=95Mont Blanc       Rollerball=95Gucci Roller=95St Dupont =
Ballpoint=95Louis Vuitton Ballpoint=95St       Dupont Roller
 
      Click here   =20
------=_NextPart_000_0007_01C881F9.0194B037
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3199" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<TABLE cellSpacing=3D2 cellPadding=3D5 width=3D800 align=3Dcenter =
border=3D2 bordercolor=3D"#FFFF00">
  <TBODY>
  <TR>
    <TD>
      <P style=3D"FONT-FAMILY: arial black; LETTER-SPACING: 5px"=20
      align=3Dcenter><STRONG=20
      style=3D"FONT-SIZE: 36px; COLOR: =
#333333">Prestige</STRONG><BR><STRONG=20
      style=3D"FONT-SIZE: 30px; COLOR: =
#666666">replicas</STRONG></P></TD></TR>
  <TR>
    <TD bgColor=3D"#0033FF">
      <P style=3D"FONT-SIZE: 28px; COLOR: #ffffff"><STRONG>Most popular=20
      watches</STRONG></P>
      <P style=3D"FONT-WEIGHT: bold; COLOR: #ffff33; =
font-size:20px">Rolex Datejusts=95Rolex Sports =
Models=95Cartier=95Hublot=95Panerai =95Chanel=95Jacob &amp;=20
      Co=95Patek=95Philippe Alain =
Silberstein=95Chopard=95Jaeger=95LeCoutrePorsche=95Design=20
      </P></TD></TR>
  <TR>
    <TD bgColor=3D#0033FF>
      <P style=3D"FONT-SIZE: 28px; COLOR: #ffffff"><strong>Most popular =
TIFFANY &amp; CO.=20
      JEWERLY</strong></P>
      <P style=3D"FONT-WEIGHT: bold; COLOR: #ffff33; =
font-size:20px">Tiffany &amp; CO=20
      Bracelets=95Tiffany &amp; CO Necklace=95Tiffany &amp; CO =
Earings</P></TD></TR>
  <TR>
    <TD bgColor=3D#0033FF>
      <P style=3D"FONT-SIZE: 24px; COLOR: #ffffff"><strong>Most popular =
PENS</strong></P>
      <P style=3D"FONT-WEIGHT: bold; COLOR: #ffff33; =
font-size:20px">Mont Blanc=20
      Ballpoint=95Louis Vuitton Rollerball=95St Dupont Fountain=95Mont =
Blanc=20
      Rollerball=95Gucci Roller=95St Dupont Ballpoint=95Louis Vuitton =
Ballpoint=95St=20
      Dupont Roller</P></TD></TR>
  <TR>
    <TD align=3Dmiddle><A style=3D"FONT-SIZE: 20px"=20
      href=3D"http://www.superpprix.com/"><STRONG>Click here</STRONG>=20
  </A></TD></TR></TBODY></TABLE>
</BODY></HTML>
------=_NextPart_000_0007_01C881F9.0194B037--




From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Mon Mar 10 12:20:22 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 71D2C3A6813
	for <ietfarch-capwap-archive@core3.amsl.com>; Mon, 10 Mar 2008 12:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id d3kwhwPYf6xU
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Mon, 10 Mar 2008 12:20:21 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by core3.amsl.com (Postfix) with ESMTP id 669983A696A
	for <capwap-archive@lists.ietf.org>; Mon, 10 Mar 2008 12:20:21 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hermes.tigertech.net (Postfix) with ESMTP id 799271C40798
	for <capwap-archive@lists.ietf.org>; Mon, 10 Mar 2008 12:18:01 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by fry.tigertech.net (Postfix) with ESMTP id EADBB4A402F
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 12:17:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id 419A3322803D
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 12:17:50 -0700 (PDT)
Received: from hgblob.tigertech.net (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id 9D7EF322A97A
	for <capwap@frascone.com>; Mon, 10 Mar 2008 12:17:48 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low);
	Whitelisted (171.71.176.71 whitelisted by
	list.dnswl.org 9.2)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by hgblob.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Mon, 10 Mar 2008 12:17:48 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 10 Mar 2008 12:17:44 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m2AJHiZu021409; 
	Mon, 10 Mar 2008 12:17:44 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id m2AJHTXU004834;
	Mon, 10 Mar 2008 19:17:44 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 10 Mar 2008 12:17:35 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 10 Mar 2008 12:17:33 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A20550C8DA@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <tsl8x0qrcf6.fsf@mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Capwap] Issue 34: keyPurposeID needs clarification
Thread-Index: AciCqj32Sgk155o8Rv6XxYWqL+ekEQAOHAHA
References: <4FF84B0BC277FF45AA27FE969DD956A204EDDB9D@xmb-sjc-235.amer.cisco.com><4FF84B0BC277FF45AA27FE969DD956A204EDDBC0@xmb-sjc-235.amer.cisco.com><tslfxxfhx3z.fsf@mit.edu><4FF84B0BC277FF45AA27FE969DD956A2052BC6AC@xmb-sjc-235.amer.cisco.com>
	<tsl8x0qrcf6.fsf@mit.edu>
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: "Sam Hartman" <hartmans-ietf@mit.edu>
X-OriginalArrivalTime: 10 Mar 2008 19:17:35.0804 (UTC)
	FILETIME=[65DA1FC0:01C882E3]
Authentication-Results: sj-dkim-4; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: capwap <capwap@frascone.com>
Subject: Re: [Capwap] Issue 34: keyPurposeID needs clarification
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

All,

The editors, security advisors, chairs and ADs met today at lunch and
discussed this topic. We agreed on an approach, which I believe is
represented in the following text:

<text>
   If a device presents its certificate which includes either the id-kp-
   capwapAC or id-kp-capwapWTP EKU, its role MUST be enforced.  For
   instance, if a certificate received during a DTLS session
   establishment includes the id-kp-capwapAC EKU, the receiving CAPWAP
   device MUST NOT allow its peer to act as a WTP.  In the absence of
   either one of these EKUs, the id-kp-anyExtendedKeyUsage EKU allows a
   device to act as either a WTP or AC.
</text>

Comments?

PatC 

-----Original Message-----
From: Sam Hartman [mailto:hartmans-ietf@mit.edu] 
Sent: Monday, March 10, 2008 5:28 AM
To: Pat Calhoun (pacalhou)
Cc: capwap
Subject: Re: [Capwap] Issue 34: keyPurposeID needs clarification

>>>>> "Pat" == Pat Calhoun (pacalhou) <pcalhoun@cisco.com> writes:

    Pat> Sam,
    Pat> Would you accept some text that simply states that the Any
KeyPurposeID
    Pat> SHOULD be ignored?

Yes, although I'd like to understand why you believe that's the right
answer.  That's sort of the opposite answer most people give.  But if
you've thought it through and believe that's the right answer that would
respond to my issue.

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Mon Mar 10 14:59:28 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 278A83A6934
	for <ietfarch-capwap-archive@core3.amsl.com>; Mon, 10 Mar 2008 14:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5uw76z0DG+QC
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Mon, 10 Mar 2008 14:59:27 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id 4840D3A6A54
	for <capwap-archive@lists.ietf.org>; Mon, 10 Mar 2008 14:59:27 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id 855D6322B446
	for <capwap-archive@lists.ietf.org>; Mon, 10 Mar 2008 14:57:07 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 0DD3D4A402F
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 14:56:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 987561843B7A
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 14:56:37 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 1397F1843985
	for <capwap@frascone.com>; Mon, 10 Mar 2008 14:56:36 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low);
	Whitelisted (171.71.176.72 whitelisted by
	list.dnswl.org 9.2)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Mon, 10 Mar 2008 14:56:36 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 10 Mar 2008 14:56:35 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m2ALuY9V001913; 
	Mon, 10 Mar 2008 14:56:34 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m2ALuXLt029731;
	Mon, 10 Mar 2008 21:56:34 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 10 Mar 2008 14:56:27 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 10 Mar 2008 14:56:26 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A20550CA16@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <tsliqzupa7c.fsf@mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Capwap] Issue 34: keyPurposeID needs clarification
Thread-Index: AciC8aj2a3bqS9Z5SxKTyDc1Wc3jDQAB+qiw
References: <4FF84B0BC277FF45AA27FE969DD956A204EDDB9D@xmb-sjc-235.amer.cisco.com><4FF84B0BC277FF45AA27FE969DD956A204EDDBC0@xmb-sjc-235.amer.cisco.com><tslfxxfhx3z.fsf@mit.edu><4FF84B0BC277FF45AA27FE969DD956A2052BC6AC@xmb-sjc-235.amer.cisco.com><tsl8x0qrcf6.fsf@mit.edu><4FF84B0BC277FF45AA27FE969DD956A20550C8DA@xmb-sjc-235.amer.cisco.com>
	<tsliqzupa7c.fsf@mit.edu>
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: "Sam Hartman" <hartmans-ietf@mit.edu>
X-OriginalArrivalTime: 10 Mar 2008 21:56:27.0680 (UTC)
	FILETIME=[974AFA00:01C882F9]
Authentication-Results: sj-dkim-2; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: capwap <capwap@frascone.com>
Subject: Re: [Capwap] Issue 34: keyPurposeID needs clarification
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

Works for me.

PatC 

-----Original Message-----
From: Sam Hartman [mailto:hartmans-ietf@mit.edu] 
Sent: Monday, March 10, 2008 1:59 PM
To: Pat Calhoun (pacalhou)
Cc: capwap
Subject: Re: [Capwap] Issue 34: keyPurposeID needs clarification

>>>>> "Pat" == Pat Calhoun (pacalhou) <pcalhoun@cisco.com> writes:

    Pat> All,
    Pat> The editors, security advisors, chairs and ADs met today at
lunch and
    Pat> discussed this topic. We agreed on an approach, which I believe
is
    Pat> represented in the following text:

    Pat> <text>
    Pat> If a device presents its certificate which includes either the
id-kp-
    Pat> capwapAC or id-kp-capwapWTP EKU, its role MUST be enforced.
For
    Pat> instance, if a certificate received during a DTLS session
    Pat> establishment includes the id-kp-capwapAC EKU, the receiving
CAPWAP
    Pat> device MUST NOT allow its peer to act as a WTP.  In the absence
of
    Pat> either one of these EKUs, the id-kp-anyExtendedKeyUsage EKU
allows a
    Pat> device to act as either a WTP or AC.
    Pat> </text>

The EKU extension is defined in such a way that if a device presents
both keyPurposeIDs then the device is permitted to take on either role.

I'd say something like
[I'm not looking at RFC 3280, so please double check my capitalization]

All capwap devices MUST support the ExtendedKeyUsage certificate
extension if it is present in a certificate.  If the extension is
present, then the certificate MUST have either the id-kp-
   capwapAC or the id-kp-anyExtendedKeyUsage  keyPurposeID to act as an
AC.  Similarly, if the extension is present, a device must have the
id-kp-capwapWTP or id-kp-anyExtendedKeyUsage  keyPurposeID to act as a
WTP.

--------------------

As a note, the extension is called EKU, but the extension contains
multiple keyPurposeIDs

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Mon Mar 10 15:06:15 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 55B393A6BD0
	for <ietfarch-capwap-archive@core3.amsl.com>; Mon, 10 Mar 2008 15:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[AWL=-0.001, BAYES_00=-2.599, FUZZY_CPILL=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dIrzHOjLgrhS
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Mon, 10 Mar 2008 15:06:13 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id 21EE028C16D
	for <capwap-archive@lists.ietf.org>; Mon, 10 Mar 2008 15:06:13 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id 5D4BD322B3E0
	for <capwap-archive@lists.ietf.org>; Mon, 10 Mar 2008 15:03:53 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by fry.tigertech.net (Postfix) with ESMTP id 6D13C4EC14B
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 15:03:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id 326C1322A8FF
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 15:03:27 -0700 (PDT)
Received: from hgblob.tigertech.net (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id F38F132280D4
	for <capwap@frascone.com>; Mon, 10 Mar 2008 15:03:25 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low);
	Whitelisted (171.71.176.71 whitelisted by
	list.dnswl.org 9.2)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by hgblob.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Mon, 10 Mar 2008 15:03:25 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 10 Mar 2008 15:03:25 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m2AM3PG9017412; 
	Mon, 10 Mar 2008 15:03:25 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m2AM2pM5006467;
	Mon, 10 Mar 2008 22:03:10 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 10 Mar 2008 15:02:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 10 Mar 2008 15:02:51 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A20550CA20@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <20341331.1203092204230.JavaMail.root@elwamui-darkeyed.atl.sa.earthlink.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Capwap] Issue 30: Inconsistent state tracking on AC
	priortoDTLSEstablishment (was: state machine issues)
Thread-Index: Achv7kvPpBJzfOncT7eA0vlNPZPvewTC6wpA
References: <20341331.1203092204230.JavaMail.root@elwamui-darkeyed.atl.sa.earthlink.net>
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: "Scott G. Kelly" <scott@hyperthought.com>,
	<Dorothy.Gellert@nokia.com>, <capwap@frascone.com>
X-OriginalArrivalTime: 10 Mar 2008 22:02:52.0972 (UTC)
	FILETIME=[7CF1DEC0:01C882FA]
Authentication-Results: sj-dkim-4; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: rbonica@juniper.net, hartmans-ietf@mit.edu, clancy@ltsnet.net
Subject: Re: [Capwap] Issue 30: Inconsistent state tracking on AC
	priortoDTLSEstablishment (was: state machine issues)
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

All,

we have agreement to close this issue and raise any issues during the WG
last call, so I will update the issue tracker accordingly.

PatC 

-----Original Message-----
From: Scott G. Kelly [mailto:s.kelly@ix.netcom.com] 
Sent: Friday, February 15, 2008 8:17 AM
To: Dorothy.Gellert@nokia.com; Pat Calhoun (pacalhou);
capwap@frascone.com
Cc: hartmans-ietf@mit.edu; clancy@ltsnet.net; rbonica@juniper.net
Subject: Re: [Capwap] Issue 30: Inconsistent state tracking on AC
priortoDTLSEstablishment (was: state machine issues)

Hi Dorothy,

I don't have any issues with publishing 09 first. Then, we'll all be
looking at the same pictures and text.

Scott


-----Original Message-----
>From: Dorothy.Gellert@nokia.com
>Sent: Feb 14, 2008 6:08 PM
>To: skelly@arubanetworks.com, pcalhoun@cisco.com, capwap@frascone.com
>Cc: hartmans-ietf@mit.edu, clancy@ltsnet.net, rbonica@juniper.net
>Subject: Re: [Capwap] Issue 30: Inconsistent state tracking on AC prior
toDTLSEstablishment (was: state machine issues)
>
>Hi Scott,
>
>I'm not clear that there is a problem with issue 30 past the agreement 
>we had the last IETF f2f meeting, and I'm reluctant to over-ride the WG

>consent.
>
>I'm not ignoring your comment regarding DOS protection, but since 
>Charles is not supporting this argument, and it wasn't raised in the 
>f2f meeting, my direction to the editors is to close issue 30 with the
>changes agreed to at the last IETF meeting.   Granted, this may be
rough
>consensus, but my priority is to get this draft to WGLC and then IESG.

>
>Scott, if you care to stand behind the agrument you mention here, then 
>you need to open it as a new issue against the WGLC after we publish.  
>I don't think its fair to hold up the draft under these circumstances.
>
>Sam Hartman has been giving us detailed security support and I will be 
>interested in his opinions of this issue as well as the few items he 
>brought up last month after he returns from family leave.
>
>Best Regards,
>Dorothy
>
>
>> -----Original Message-----
>> From: ext Scott Kelly [mailto:skelly@arubanetworks.com]
>> Sent: Thursday, February 14, 2008 2:08 PM
>> To: Pat Calhoun (pacalhou); capwap
>> Subject: Re: [Capwap] Issue 30: Inconsistent state tracking on AC 
>> prior toDTLSEstablishment (was: state machine issues)
>> 
>> > Scott, given that no one else seems to object to the
>> change, and that
>> > Charles is comfortable with the change, can we consider this
closed?
>> 
>> Let's not mistake malaise for assent.
>> 
>> There were changes introduced in 03 which are inconsistent with other

>> stated protocol objectives. In particular, 03 introduced discovery 
>> state as an integral element of the protocol, and modified the text 
>> in such a way as to remove the DoS protections afforded by the DTLS 
>> client cookie.
>> 
>> This protocol should be suitable for deployment by, among others, 
>> service providers who are subject to the "Internet"
>> threat model. The exposure that results from the proposed design 
>> should be obvious. There are certainly other deployment types that 
>> could be similarly harmed by this introduction of discovery state, 
>> but SP's are a convenient reference point for this discussion.
>> 
>> Agreeing that discovery state SHOULD NOT be kept, and then (wink, 
>> wink, nudge, nudge) explaining how to maintain discovery state is a 
>> bit disingenuous, if not irresponsible.
>> I don't believe there is any precedent for this in IETF standards 
>> documents.
>> 
>> So, no, I don't think this issue is closed. I proposed 
>> straightforward changes to fix this (see 
>> http://lists.frascone.com/pipermail/capwap/msg04621.html). I don't 
>> understand what the problem is with adopting these proposed 
>> clarifications.
>> 
>> 
>> --Scott
>> 
>> 
>> 
>> 
>> > 
>> > PatC
>> > 
>> > -----Original Message-----
>> > From: Pat Calhoun (pacalhou)
>> > Sent: Tuesday, January 15, 2008 4:55 PM
>> > To: Scott Kelly; capwap
>> > Subject: Re: [Capwap] state machine issues
>> > 
>> > My apologies for the latency. Responses below.
>> > 
>> > > This text seems to have originally assumed that the AC
>> would listen
>> > > *per-WTP* based on receipt of a discovery request from
>> that WTP, but
>> > this is inconsistent in multiple ways. Most
>> > > importantly, discovery is optional, so the AC must *always* be
>> > listening for incoming (DTLS) ClientHello messages. A
>> > > simple way to represent this is to say that the AC is
>> > listening while
>> > in the Idle state, and receipt of an acceptable
>> > > ClientHello (e.g. with a valid cookie) causes it to
>> transition from
>> > Idle to DTLS Setup. You could also say the AC is
>> > > always in DTLS Setup state, but that complicates things
>> in terms of
>> > representing discovery message processing. I think
>> > > using idle for this works best.
>> > 
>> > Actually, the state machine does not require this, but
>> allows for it. 
>> > If an AC wants to only accept connections from specific IP
>> addresses,
>> > whether the list was generated from discovery, or through a 
>> > pre-configured list, this is possible. It is not
>> recommended, are the
>> > text states.
>> > 
>> > > Before we go any further with this, we need to agree on
>> > whether use of
>> > client cookies is required or optional. The
>> > > protocol is simpler if they are always required, but there are
>> > probably deployment scenarios in which the potential
>> > > for AC DoS attacks is minimal, so one might argue that they
>> > shouldn't
>> > be strictly required for those scenarios. In the
>> > > interest of implementation simplicity, I would vote to simply 
>> > > make
>> > them mandatory, but I will assume they are optional
>> > > below with the understanding that the proposed language will be
>> > simpler if they become mandatory.
>> > 
>> > At first glance, I don't think I have issues with your
>> proposal, but
>> > do not fully understand the possible impact of the changes.
>> > 
>> > > Another related decision might be a little more rat-hole prone 
>> > > (or
>> > not):
>> > > what are the state transitions required to implement the
>> > HelloVerifyRequest? The simplest is to add a C next to the
>> > > Idle state (an Idle to Idle transition), with something
>> > resembling the
>> > following
>> > > text:
>> > 
>> > >    Idle to Idle (b):  This transition may occur on the AC when it
>> > receives
>> > >      a ClientHello
>> > 
>> > >       WTP:  This is an invalid state transition for the WTP.
>> > 
>> > >       AC:  When the WTP sends a ClientHello, the AC
>> optionally sends
>> > >         a HelloVerifyRequest containing a unique cookie
>> that the WTP
>> > >         must return in a subsequent HelloRequest. This
>> > transition also
>> > >         occurs if a ClientHello contains an invalid cookie.
>> > > 
>> > > Note that 3 things can happen when the AC receives a
>> > ClientHello; the
>> > AC
>> > > 
>> > >   1) drops the message, because it contains an invalid cookie, or
>> > because
>> > >     the AC is rate limiting handshakes
>> > > 
>> > >   2) it creates a cookie and sends a HelloVerifyRequest
>> > > 
>> > >   3) it deems the incoming HelloRequest acceptable (either
>> > because it
>> > >     contains a valid cookie or because client cookies are not
>> > required),
>> > >     and it transitions from Idle to DTLS Setup
>> > > 
>> > > Rather than idle to idle, we could add another AC-only
>> state that it
>> > transitions into to gen/send the cookie, and then
>> > > back to Idle, but I think Idle-Idle works okay and is simpler.
>> > 
>> > It seems to me like we really aren't changing anything because 
>> > ultimately, the state machine still has a state transition prior to

>> > the setup of DTLS, so the same confusion about whether the AC 
>> > maintains state prior to DTLS setup still exists. I continue to 
>> > believe that the current draft does not make this necessary
>> since the
>> > "listener thread"
>> > operates on a separate context that is global - not per WTP.
>> > 
>> > So it seems to me like the current draft already defines the API 
>> > between DTLS and CAPWAP, and therefore addresses the other
>> requirement
>> > we once had about not wanting CAPWAP to have to parse and
>> understand
>> > the DTLS state machine. I continue to believe this should
>> be a design
>> > goal. In your proposed model, CAPWAP needs to validate whether the 
>> > cookie is valid (or at least since the state machine description 
>> > includes this, then I presume it does). I would prefer let the DTLS

>> > engine do this and simply report back on what's working/not
working.
>> > 
>> > PatC
>> > _________________________________________________________________
>> > To unsubscribe or modify your subscription options, please visit:
>> > http://lists.frascone.com/mailman/listinfo/capwap
>> > 
>> > Archives: http://lists.frascone.com/pipermail/capwap
>> > 
>> _________________________________________________________________
>> To unsubscribe or modify your subscription options, please visit:
>> http://lists.frascone.com/mailman/listinfo/capwap
>> 
>> Archives: http://lists.frascone.com/pipermail/capwap
>> 
>_________________________________________________________________
>To unsubscribe or modify your subscription options, please visit:
>http://lists.frascone.com/mailman/listinfo/capwap
>
>Archives: http://lists.frascone.com/pipermail/capwap

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Mon Mar 10 15:07:25 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B32CC3A6BD0
	for <ietfarch-capwap-archive@core3.amsl.com>; Mon, 10 Mar 2008 15:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GeB1kXFUG1Jb
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Mon, 10 Mar 2008 15:07:23 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id A0B2D28C1E5
	for <capwap-archive@lists.ietf.org>; Mon, 10 Mar 2008 15:07:20 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id CF887322A824
	for <capwap-archive@lists.ietf.org>; Mon, 10 Mar 2008 15:05:00 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id C677D4EC14B
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 15:04:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id BC2171843B98
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 15:04:23 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 2A3B818435A8
	for <capwap@frascone.com>; Mon, 10 Mar 2008 15:04:22 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low);
	Whitelisted (171.71.176.72 whitelisted by
	list.dnswl.org 9.2)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Mon, 10 Mar 2008 15:04:22 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 10 Mar 2008 15:04:22 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m2AM4LQ1018998; 
	Mon, 10 Mar 2008 15:04:21 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m2AM45M7007880;
	Mon, 10 Mar 2008 22:04:21 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 10 Mar 2008 15:04:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 10 Mar 2008 15:04:16 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A20550CA25@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <tsl4pberce9.fsf@mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Capwap] Issue 35: MAC Address in Certificate CN field
Thread-Index: AciCqoPdn7g3ZO11QuadUa08oS/4EQAUCDlA
References: <4FF84B0BC277FF45AA27FE969DD956A204EDDBBC@xmb-sjc-235.amer.cisco.com><4FF84B0BC277FF45AA27FE969DD956A204EDDBBF@xmb-sjc-235.amer.cisco.com><tslbq83hws8.fsf@mit.edu><4FF84B0BC277FF45AA27FE969DD956A2052BC6AD@xmb-sjc-235.amer.cisco.com>
	<tsl4pberce9.fsf@mit.edu>
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: "Sam Hartman" <hartmans-ietf@mit.edu>
X-OriginalArrivalTime: 10 Mar 2008 22:04:17.0218 (UTC)
	FILETIME=[AF28CA20:01C882FA]
Authentication-Results: sj-dkim-4; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: capwap <capwap@frascone.com>
Subject: Re: [Capwap] Issue 35: MAC Address in Certificate CN field
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

Great, I will update Issue tracker accordingly.

PatC 

-----Original Message-----
From: Sam Hartman [mailto:hartmans-ietf@mit.edu] 
Sent: Monday, March 10, 2008 5:29 AM
To: Pat Calhoun (pacalhou)
Cc: capwap
Subject: Re: [Capwap] Issue 35: MAC Address in Certificate CN field

>>>>> "Pat" == Pat Calhoun (pacalhou) <pcalhoun@cisco.com> writes:

    Pat> Sam,
    Pat> May I simply adopt your proposed text below and close this
issue?
Sure.
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Tue Mar 11 07:56:48 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 37F153A6DF9
	for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 11 Mar 2008 07:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KI1aL28M6U81
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Tue, 11 Mar 2008 07:56:42 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by core3.amsl.com (Postfix) with ESMTP id 426A43A6A89
	for <capwap-archive@lists.ietf.org>; Tue, 11 Mar 2008 07:56:42 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hermes.tigertech.net (Postfix) with ESMTP id 247BE1C407CB
	for <capwap-archive@lists.ietf.org>; Tue, 11 Mar 2008 07:54:23 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id CCA9E4A4037
	for <capwap@lists.tigertech.net>; Tue, 11 Mar 2008 07:54:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id AAE9C1C40515
	for <capwap@lists.tigertech.net>; Tue, 11 Mar 2008 07:54:11 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id B20CD1C4041C
	for <capwap@frascone.com>; Tue, 11 Mar 2008 07:54:09 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low); Accepted (Neutral)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Tue, 11 Mar 2008 07:54:08 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 11 Mar 2008 07:54:08 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m2BEs8qF011414; 
	Tue, 11 Mar 2008 07:54:08 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id m2BErxrn007267;
	Tue, 11 Mar 2008 14:54:07 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 11 Mar 2008 07:53:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 11 Mar 2008 07:53:57 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A205594C98@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <4FF84B0BC277FF45AA27FE969DD956A20531662C@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Capwap] Issue 37: Key Rollover issue
Thread-Index: AchODHYfmnLKyDyjSoiT2TfBV29mcAf8yM9QAFdX+6AFCpS98A==
References: <4FF84B0BC277FF45AA27FE969DD956A204EDDBDE@xmb-sjc-235.amer.cisco.com><tsl7iirhwfg.fsf@mit.edu>
	<4FF84B0BC277FF45AA27FE969DD956A2052BC6AF@xmb-sjc-235.amer.cisco.com>
	<4FF84B0BC277FF45AA27FE969DD956A20531662C@xmb-sjc-235.amer.cisco.com>
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: "Sam Hartman" <hartmans-ietf@mit.edu>
X-OriginalArrivalTime: 11 Mar 2008 14:53:58.0720 (UTC)
	FILETIME=[BC8C6400:01C88387]
Authentication-Results: sj-dkim-2; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: capwap@frascone.com
Subject: Re: [Capwap] Issue 37: Key Rollover issue
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

All,

The editors, security advisors, chairs and ADs met yesterday to get
through these last security related issues, and agreed on a fix for this
issue. In addition to the removal of the sentence below, we agreed that
some level of pre-provisioning is required on both the WTP and the AC to
allow for the DTLS session setup. There was general agreement that in
this version of the protocol we would simply address it through text,
but that some protocol related effort should be tackling this issue.
Some folks felt this should be addessed in the CAPWAP protocol.

I am including the proposed text here. As an aside, this text also
resolves issue 36.

<text>
12.5.  CAPWAP Pre-Provisioning

   In order for CAPWAP to establish a secure communication with a peer,
   some level of pre-provisioning on both the WTP and AC is necessary.
   This section will detail the minimal number of configuration
   parameters.

   When using preshared keys, it is necessary to configure the preshared
   key for each possible peer with which a DTLS session may be
   established.  To support this mode of operation, one or more entries
   of the following table may be configured on either the AC or WTP:

   o  Identity: The identity of the peering AC or WTP.  This format MAY
      be either in the form of an IP address or host name (the latter of
      which needs to be resolved to an IP address using DNS).

   o  Key: The pre-shared key for use with the peer when establishing
      the DTLS session (see Section 12.6 for more information).

   o  Key Identifier: The pre-shared key identifier, as described in RFC
      4279 [RFC4279].

   When using certificates, the following items need to be pre-
   provisioned:

   o  Device Certificate: The local device's certificate (see
      Section 12.7 for more information)

   o  Trust Anchor: Trusted root certificate chain used to validate any
      certificate received from CAPWAP peers.  Note that one or more
      root certificate MAY be configured on a given device.

   Regardless of the authentication method, the following items need to
   be pre-provisioned:

   o  Access Control List: The access control list table contains the
      identities of one or more CAPWAP peers, along with a rule.  The
      rule is used to determine whether communication with the peer is
      permitted (see Section 2.4.4.3 for more information).
</text>

Comments?

PatC 

-----Original Message-----
From: Pat Calhoun (pacalhou) 
Sent: Thursday, February 14, 2008 2:58 PM
To: Pat Calhoun (pacalhou); Sam Hartman
Cc: capwap@frascone.com
Subject: RE: [Capwap] Issue 37: Key Rollover issue

Scott has recommended that we remove the following sentence from
paragraph 2 of section 12.6: 

"At a minimum, devices SHOULD use SSH-style certificate caching to
guarantee consistency."

Any disagreements?

PatC
 

-----Original Message-----
From: Pat Calhoun (pacalhou)
Sent: Tuesday, February 12, 2008 9:17 PM
To: Sam Hartman
Cc: capwap@frascone.com
Subject: Re: [Capwap] Issue 37: Key Rollover issue

Scott, do you have any text that could handle Sam's issue?

PatC 

-----Original Message-----
From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
Sent: Thursday, January 03, 2008 5:27 AM
To: Pat Calhoun (pacalhou)
Cc: capwap@frascone.com
Subject: Re: Issue 37: Key Rollover issue

>>>>> "Pat" == Pat Calhoun (pacalhou) <pcalhoun@cisco.com> writes:

    Pat> Sam, This is a topic that has already been raised and
    Pat> closed. I am including part of an e-mail exchange on the list
    Pat> where this was discussed. I can also point you to
    Pat> http://www.capwap.org/cgi-bin/roundup.old/CAPWAP/issue228,
    Pat> which is the old tracker entry where more information can be
    Pat> found.

    Pat> I would like to close this issue, as it is redundant, but
    Pat> want to make sure you are ok with it first.

As best I can tell, the old issue you refer me to is a question about
whether to rekey the DTLS session keys within a single active capwap
session.
(Session may be the wrong term for your protocol, but I hope I am
sufficiently clear)

I agree with the WG's decision on that issue.


However I think I was describing a different issue.  I was discussing
the rollever of public keys in certificates used in leap of faith
transactions.


The reason a site would want to roll over these keys is more about staff
changes and AC replacement than cryptographic limitations.



So, I think the issue I raise is different and at least requires
security considerations text.  It concerns me because without clear
guidance you can get into a situation where you cannot rekey either when
you have a key compromise or when you have staffing changes because some
of your equipment is implementing a primitive leap of faith strategy
similar to ssh.


I'm not entirely sure what the anser is, but I am sure that the problem
is real.
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Tue Mar 11 07:59:04 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BCDFC3A6D61
	for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 11 Mar 2008 07:59:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nNa16LHEd4bH
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Tue, 11 Mar 2008 07:59:03 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by core3.amsl.com (Postfix) with ESMTP id C2B803A6ACC
	for <capwap-archive@lists.ietf.org>; Tue, 11 Mar 2008 07:59:03 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hermes.tigertech.net (Postfix) with ESMTP id A44661C40E84
	for <capwap-archive@lists.ietf.org>; Tue, 11 Mar 2008 07:56:44 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 365954A4037
	for <capwap@lists.tigertech.net>; Tue, 11 Mar 2008 07:56:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 2CAF91C4052B
	for <capwap@lists.tigertech.net>; Tue, 11 Mar 2008 07:56:22 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 695511C40527
	for <capwap@frascone.com>; Tue, 11 Mar 2008 07:56:21 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low);
	Whitelisted (171.71.176.72 whitelisted by
	list.dnswl.org 9.2)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Tue, 11 Mar 2008 07:56:21 -0700 (PDT)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 11 Mar 2008 07:56:21 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m2BEuJk4021219; 
	Tue, 11 Mar 2008 07:56:19 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id m2BEuArv009842;
	Tue, 11 Mar 2008 14:56:19 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 11 Mar 2008 07:56:04 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 11 Mar 2008 07:56:02 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A205594CA1@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <4FF84B0BC277FF45AA27FE969DD956A2052BC6AE@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Capwap] Issue 36: Trust Anchor text missing
Thread-Index: AchD8FFlD7jOBI9YQLChnzHT38ze6QqDy53wBWIUa6A=
References: <4FF84B0BC277FF45AA27FE969DD956A204EDDBE6@xmb-sjc-235.amer.cisco.com>
	<4FF84B0BC277FF45AA27FE969DD956A2052BC6AE@xmb-sjc-235.amer.cisco.com>
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: <capwap@frascone.com>
X-OriginalArrivalTime: 11 Mar 2008 14:56:04.0306 (UTC)
	FILETIME=[07674B20:01C88388]
Authentication-Results: sj-dkim-1; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [Capwap] Issue 36: Trust Anchor text missing
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

All,

The proposed text that I just sent to the list on issue 37 addresses
this problem. By including the trust anchor during the pre-provisioning
process, it ensures that the trust anchor is known on both the WTP and
AC.

<text>
12.5.  CAPWAP Pre-Provisioning
[...]
   When using certificates, the following items need to be pre-
   provisioned:

   o  Device Certificate: The local device's certificate (see
      Section 12.7 for more information)

   o  Trust Anchor: Trusted root certificate chain used to validate any
      certificate received from CAPWAP peers.  Note that one or more
      root certificate MAY be configured on a given device.

</text>

Comments?

PatC 


-----Original Message-----
From: Pat Calhoun (pacalhou) 
Sent: Tuesday, February 12, 2008 9:16 PM
To: Pat Calhoun (pacalhou); capwap@frascone.com
Cc: Sam Hartman
Subject: RE: [Capwap] Issue 36: Trust Anchor text missing

Scott and Sam,

Could we get a resolution on this issue?

PatC 

-----Original Message-----
From: Pat Calhoun (pacalhou)
Sent: Friday, December 21, 2007 8:41 AM
To: capwap@frascone.com
Cc: Sam Hartman
Subject: [Capwap] Issue 36: Trust Anchor text missing

Sam,

You seem to be talking about two separate issues below. The first is how
the trust anchor is known. If we are talking about manufacturing certs,
the root certificate is typically embedded in the device, or it can be
fetched using <insert favorite cert fetching protocol here>. Would
adding this specific text address your issue?

The second one you seem to talk about is how a WTP is deployed. Are you
asking how a certificate is provisioned on the WTP, or are you asking
more about how the access control list is configured? The text in
section 2.4.4.3 discusses the concept of the ACL, but doesn't actually
describe the use case (e.g., receive box, open box, read MAC address,
add MAC address to access control list). 

Could you provide more clarity?

Thanks,

PatC
> 4) I expected to find some discussion of trust anchors in the document
>    and was surprised not to see any.  Also, I expected to find some
>    reference to the certificate validation algorithm in RFC 3280.  The
>    second point  is minor; there is certificate validation text and it
>    may well be good enough.  The point about discussing trust anchors
>    is bigger.
>
> I do realize that trust anchors are a difficult topic.  If I get a WTP

> that has never been configured and arrives in a box from some 
> manufacturer, how exactly is it supposed to know who to trust at my 
> cite.  You should say something though or have an explanation of why 
> you couldn't say anything.
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Tue Mar 11 12:36:30 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 465FC28C48A
	for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 11 Mar 2008 12:36:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rMeymT3NQKO8
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Tue, 11 Mar 2008 12:36:26 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by core3.amsl.com (Postfix) with ESMTP id 65A6928C485
	for <capwap-archive@lists.ietf.org>; Tue, 11 Mar 2008 12:36:26 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hermes.tigertech.net (Postfix) with ESMTP id 6576A1C407B9
	for <capwap-archive@lists.ietf.org>; Tue, 11 Mar 2008 12:34:07 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 931FF4A4037
	for <capwap@lists.tigertech.net>; Tue, 11 Mar 2008 12:33:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 11D241C407E0
	for <capwap@lists.tigertech.net>; Tue, 11 Mar 2008 12:33:52 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 6D9041C407B9
	for <capwap@frascone.com>; Tue, 11 Mar 2008 12:33:51 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low); Accepted (Neutral)
Received: from mms5.broadcom.com (mms5.broadcom.com [216.31.210.20])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Tue, 11 Mar 2008 12:33:49 -0700 (PDT)
Received: from [10.10.64.154] by mms5.broadcom.com with ESMTP (Broadcom
	SMTP Relay (Email Firewall v6.3.2)); Tue, 11 Mar 2008 12:33:34 -0700
X-Server-Uuid: 93BB6497-3EF8-45A3-B447-1CDF3B37573C
Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id
	0AE0A2B2; Tue, 11 Mar 2008 12:33:34 -0700 (PDT)
Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by
	mail-irva-10.broadcom.com (Postfix) with ESMTP id E539E2B0; Tue, 11 Mar
	2008 12:33:33 -0700 (PDT)
Received: from mail-sj1-12.sj.broadcom.com (mail-sj1-12.sj.broadcom.com
	[10.16.128.215]) by mail-irva-8.broadcom.com (MOS 3.7.5a-GA) with ESMTP
	id GPC87831; Tue, 11 Mar 2008 12:33:29 -0700 (PDT)
Received: from NT-SJCA-0751.brcm.ad.broadcom.com (nt-sjca-0751
	[10.16.192.221]) by mail-sj1-12.sj.broadcom.com (Postfix) with ESMTP id
	0F57C20502; Tue, 11 Mar 2008 12:33:29 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 11 Mar 2008 12:33:26 -0700
Message-ID: <8954613CA6BB3242A1531D916A527A4106995FB9@NT-SJCA-0751.brcm.ad.broadcom.com>
Thread-Topic: comment on base -09 draft
Thread-Index: AciDrsVp4ZPtI4haSwG0V+zLb64h4w==
From: "Puneet Agarwal" <pagarwal@broadcom.com>
To: pcalhoun@cisco.com
X-WSS-ID: 6BC801044IS126820-01-01
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: capwap@frascone.com
Subject: [Capwap] comment on base -09 draft
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1085646022=="
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

This is a multi-part message in MIME format.

--===============1085646022==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C883AE.C84F537F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C883AE.C84F537F
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi Pat,
=20
Looks like we fixed some text in 4.4.2 in version -09 but as I am going
though the draft, there is similar text that needs to be fixed in
section 1:
=20
Section 1, page 7 :" The latter implies that the WTP performs the 802
bridging function.  "
=20
Comment: This does not imply that the WTP performs the 802 bridging
function. The previous text in the paragraph just implies that the
802.11 Integration function is done at the WTP. Hence the above sentence
should be reworded as follows:
=20
" The latter implies that the WTP performs the 802.11 Integration
function."
=20
Thanks.
=20
-Puneet
=20

------_=_NextPart_001_01C883AE.C84F537F
Content-Type: text/html;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16608" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial size=3D2>Hi=20
Pat,</FONT></SPAN></DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial size=3D2>Looks =
like we fixed=20
some text in 4.4.2 in version -09 but as I am going though =
the&nbsp;draft, there=20
is similar text that&nbsp;needs to be fixed in section =
1:</FONT></SPAN></DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial =
size=3D2>Section 1, page 7=20
:</FONT></SPAN><SPAN class=3D859432619-11032008><FONT face=3DArial =
size=3D2>" The=20
latter implies that the WTP performs the 802 bridging function.&nbsp;=20
"</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial =
size=3D2>Comment: This does=20
not imply that the WTP performs the 802 bridging function. The previous =
text in=20
the paragraph just implies that the 802.11 Integration function is done =
at the=20
WTP. Hence the above sentence should be reworded as =
follows:</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial size=3D2>" The =
latter implies=20
that the WTP performs the 802.11 Integration =
function."</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2>Thanks.</FONT></SPAN></DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2>-Puneet</FONT></SPAN></DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2></FONT>&nbsp;</SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C883AE.C84F537F--


--===============1085646022==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap
--===============1085646022==--



From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Tue Mar 11 15:41:34 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A8F73A6810
	for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 11 Mar 2008 15:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1h2NIcMabCBS
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Tue, 11 Mar 2008 15:41:28 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id 9511E3A68D5
	for <capwap-archive@lists.ietf.org>; Tue, 11 Mar 2008 15:41:28 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id 97B8B322B407
	for <capwap-archive@lists.ietf.org>; Tue, 11 Mar 2008 15:39:09 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id B11F44A4037
	for <capwap@lists.tigertech.net>; Tue, 11 Mar 2008 15:38:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 86A211C407C2
	for <capwap@lists.tigertech.net>; Tue, 11 Mar 2008 15:38:44 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id EF5741C40521
	for <capwap@frascone.com>; Tue, 11 Mar 2008 15:38:42 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low); Accepted (Neutral)
Received: from po-out-1718.google.com (po-out-1718.google.com [72.14.252.155])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Tue, 11 Mar 2008 15:38:42 -0700 (PDT)
Received: by po-out-1718.google.com with SMTP id b23so1899989poe.0
	for <capwap@frascone.com>; Tue, 11 Mar 2008 15:38:42 -0700 (PDT)
Received: by 10.140.180.11 with SMTP id c11mr4859165rvf.137.1205275122324;
	Tue, 11 Mar 2008 15:38:42 -0700 (PDT)
Received: by 10.141.168.3 with HTTP; Tue, 11 Mar 2008 15:38:42 -0700 (PDT)
Message-ID: <5bfe7a820803111538n20f3041bq18e4e33cf0a2b30e@mail.gmail.com>
Date: Tue, 11 Mar 2008 15:38:42 -0700
From: "Dorothy Stanley" <dstanley1389@gmail.com>
To: "Puneet Agarwal" <pagarwal@broadcom.com>
In-Reply-To: <8954613CA6BB3242A1531D916A527A4106995FB9@NT-SJCA-0751.brcm.ad.broadcom.com>
MIME-Version: 1.0
References: <8954613CA6BB3242A1531D916A527A4106995FB9@NT-SJCA-0751.brcm.ad.broadcom.com>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: capwap@frascone.com
Subject: Re: [Capwap] comment on base -09 draft
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0505084043=="
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

--===============0505084043==
Content-Type: multipart/alternative; 
	boundary="----=_Part_4966_11638771.1205275122338"

------=_Part_4966_11638771.1205275122338
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Puneet,

I agree with your proposed change.

Dorothy Stanley


On Tue, Mar 11, 2008 at 12:33 PM, Puneet Agarwal <pagarwal@broadcom.com>
wrote:

>  Hi Pat,
>
> Looks like we fixed some text in 4.4.2 in version -09 but as I am going
> though the draft, there is similar text that needs to be fixed in section 1:
>
> Section 1, page 7 :" The latter implies that the WTP performs the 802
> bridging function.  "
>
> Comment: This does not imply that the WTP performs the 802 bridging
> function. The previous text in the paragraph just implies that the 802.11Integration function is done at the WTP. Hence the above sentence should be
> reworded as follows:
>
> " The latter implies that the WTP performs the 802.11 Integration
> function."
>
> Thanks.
>
> -Puneet
>
>
> _________________________________________________________________
> To unsubscribe or modify your subscription options, please visit:
> http://lists.frascone.com/mailman/listinfo/capwap
>
> Archives: http://lists.frascone.com/pipermail/capwap
>

------=_Part_4966_11638771.1205275122338
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Puneet,<br><br>I agree with your proposed change.<br><br>Dorothy Stanley<br><br><br><div class="gmail_quote">On Tue, Mar 11, 2008 at 12:33 PM, Puneet Agarwal &lt;<a href="mailto:pagarwal@broadcom.com">pagarwal@broadcom.com</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">



<div>
<div><span><font face="Arial" size="2">Hi 
Pat,</font></span></div>
<div><span><font face="Arial" size="2"></font></span>&nbsp;</div>
<div><span><font face="Arial" size="2">Looks like we fixed 
some text in 4.4.2 in version -09 but as I am going though the&nbsp;draft, there 
is similar text that&nbsp;needs to be fixed in section 1:</font></span></div>
<div><span><font face="Arial" size="2"></font></span>&nbsp;</div>
<div><span><font face="Arial" size="2">Section 1, page 7 
:</font></span><span><font face="Arial" size="2">&quot; The 
latter implies that the WTP performs the 802 bridging function.&nbsp; 
&quot;</font></span></div>
<div><font face="Arial" size="2"></font>&nbsp;</div>
<div><span><font face="Arial" size="2">Comment: This does 
not imply that the WTP performs the 802 bridging function. The previous text in 
the paragraph just implies that the 802.11 Integration function is done at the 
WTP. Hence the above sentence should be reworded as follows:</font></span></div>
<div><font face="Arial" size="2"></font>&nbsp;</div>
<div><span><font face="Arial" size="2">&quot; The latter implies 
that the WTP performs the 802.11 Integration function.&quot;</font></span></div>
<div><font face="Arial" size="2"></font>&nbsp;</div>
<div><span><font face="Arial" size="2">Thanks.</font></span></div>
<div><span><font face="Arial" size="2"></font></span>&nbsp;</div>
<div><span><font face="Arial" size="2">-Puneet</font></span></div>
<div><span><font face="Arial" size="2"></font>&nbsp;</span></div></div>
<br>_________________________________________________________________<br>
To unsubscribe or modify your subscription options, please visit:<br>
<a href="http://lists.frascone.com/mailman/listinfo/capwap" target="_blank">http://lists.frascone.com/mailman/listinfo/capwap</a><br>
<br>
Archives: <a href="http://lists.frascone.com/pipermail/capwap" target="_blank">http://lists.frascone.com/pipermail/capwap</a><br></blockquote></div><br>

------=_Part_4966_11638771.1205275122338--

--===============0505084043==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap
--===============0505084043==--


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Tue Mar 11 18:40:33 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA25528C323
	for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 11 Mar 2008 18:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ipCuZ9a5+5aw
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Tue, 11 Mar 2008 18:40:32 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id D370D28C2EB
	for <capwap-archive@lists.ietf.org>; Tue, 11 Mar 2008 18:40:32 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id 9F46A322B533
	for <capwap-archive@lists.ietf.org>; Tue, 11 Mar 2008 18:38:13 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by fry.tigertech.net (Postfix) with ESMTP id 188704A40A2
	for <capwap@lists.tigertech.net>; Tue, 11 Mar 2008 18:37:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id D227C322B171
	for <capwap@lists.tigertech.net>; Tue, 11 Mar 2008 18:37:49 -0700 (PDT)
Received: from hgblob.tigertech.net (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id 4B343322B0B0
	for <capwap@frascone.com>; Tue, 11 Mar 2008 18:37:47 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low);
	Whitelisted (171.71.176.72 whitelisted by
	list.dnswl.org 9.2)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by hgblob.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Tue, 11 Mar 2008 18:37:47 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 11 Mar 2008 18:37:47 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m2C1bjrQ018441; 
	Tue, 11 Mar 2008 18:37:45 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m2C1bYXc028351;
	Wed, 12 Mar 2008 01:37:45 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 11 Mar 2008 18:37:42 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 11 Mar 2008 18:37:40 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A205595132@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <8954613CA6BB3242A1531D916A527A4106995FB9@NT-SJCA-0751.brcm.ad.broadcom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: comment on base -09 draft
Thread-Index: AciDrsVp4ZPtI4haSwG0V+zLb64h4wAMt/0A
References: <8954613CA6BB3242A1531D916A527A4106995FB9@NT-SJCA-0751.brcm.ad.broadcom.com>
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: "Puneet Agarwal" <pagarwal@broadcom.com>
X-OriginalArrivalTime: 12 Mar 2008 01:37:42.0486 (UTC)
	FILETIME=[AA1B5F60:01C883E1]
Authentication-Results: sj-dkim-2; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: capwap@frascone.com
Subject: Re: [Capwap] comment on base -09 draft
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1409707968=="
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

This is a multi-part message in MIME format.

--===============1409707968==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C883E1.A90AE79F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C883E1.A90AE79F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Created issue 39.
=20
PatC

________________________________

From: Puneet Agarwal [mailto:pagarwal@broadcom.com]=20
Sent: Tuesday, March 11, 2008 12:33 PM
To: Pat Calhoun (pacalhou)
Cc: capwap@frascone.com
Subject: comment on base -09 draft


Hi Pat,
=20
Looks like we fixed some text in 4.4.2 in version -09 but as I am going
though the draft, there is similar text that needs to be fixed in
section 1:
=20
Section 1, page 7 :" The latter implies that the WTP performs the 802
bridging function.  "
=20
Comment: This does not imply that the WTP performs the 802 bridging
function. The previous text in the paragraph just implies that the
802.11 Integration function is done at the WTP. Hence the above sentence
should be reworded as follows:
=20
" The latter implies that the WTP performs the 802.11 Integration
function."
=20
Thanks.
=20
-Puneet
=20

------_=_NextPart_001_01C883E1.A90AE79F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3268" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D694343701-12032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Created issue 39.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D694343701-12032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D694343701-12032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>PatC</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Puneet Agarwal=20
[mailto:pagarwal@broadcom.com] <BR><B>Sent:</B> Tuesday, March 11, 2008 =
12:33=20
PM<BR><B>To:</B> Pat Calhoun (pacalhou)<BR><B>Cc:</B>=20
capwap@frascone.com<BR><B>Subject:</B> comment on base -09=20
draft<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial size=3D2>Hi=20
Pat,</FONT></SPAN></DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial size=3D2>Looks =
like we fixed=20
some text in 4.4.2 in version -09 but as I am going though =
the&nbsp;draft, there=20
is similar text that&nbsp;needs to be fixed in section =
1:</FONT></SPAN></DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial =
size=3D2>Section 1, page 7=20
:</FONT></SPAN><SPAN class=3D859432619-11032008><FONT face=3DArial =
size=3D2>" The=20
latter implies that the WTP performs the 802 bridging function.&nbsp;=20
"</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial =
size=3D2>Comment: This does=20
not imply that the WTP performs the 802 bridging function. The previous =
text in=20
the paragraph just implies that the 802.11 Integration function is done =
at the=20
WTP. Hence the above sentence should be reworded as =
follows:</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial size=3D2>" The =
latter implies=20
that the WTP performs the 802.11 Integration =
function."</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2>Thanks.</FONT></SPAN></DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2>-Puneet</FONT></SPAN></DIV>
<DIV><SPAN class=3D859432619-11032008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C883E1.A90AE79F--

--===============1409707968==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap
--===============1409707968==--


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Wed Mar 12 01:03:37 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2EE6528C567
	for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 12 Mar 2008 01:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y2huX-XdReDt
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Wed, 12 Mar 2008 01:03:36 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id 9B80728C55D
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 01:03:35 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id 070F1322B5D8
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 01:01:17 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by fry.tigertech.net (Postfix) with ESMTP id 2427B4A4069
	for <capwap@lists.tigertech.net>; Wed, 12 Mar 2008 01:00:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id D1432322A8A8
	for <capwap@lists.tigertech.net>; Wed, 12 Mar 2008 01:00:57 -0700 (PDT)
Received: from hgblob.tigertech.net (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id 13537322A824
	for <capwap@frascone.com>; Wed, 12 Mar 2008 01:00:56 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low); Accepted (Neutral)
Received: from pass-seymour.com (marussyr001.pass-seymour.com [12.33.96.185])
	by hgblob.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Wed, 12 Mar 2008 01:00:54 -0700 (PDT)
Received: from ([172.16.5.248])
	by Marussyr001.pass-seymour.com with ESMTP  id 5202449.36088821;
	Wed, 12 Mar 2008 03:54:29 -0400
From: Mike Hines <mike.hines@ortronics.com>
To: capwap@frascone.com
Message-ID: <OF0A318465.D260EA5C-ON8525740A.002C0266-8525740A.002C0266@Pass-Seymour.com>
Date: Wed, 12 Mar 2008 04:00:41 -0400
X-MIMETrack: Serialize by Router on LNANOTES1A/LNA(Release 6.5.5|November 30,
	2005) at 03/12/2008 04:00:42
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Subject: [Capwap] Mike Hines/PSL/US is out of the office.
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com


I will be out of the office starting  03/11/2008 and will not return until
03/13/2008.

In my absence, feel free to leave an e-mail or contact Rudy Montgelas at
(860) 405-2969 / rudolph.montgelas@ortronics.com or Jim Hart at
(860)405-2816 / james.hart@ortronics.com for immediate assistance.

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Wed Mar 12 08:50:52 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 221B028C835
	for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 12 Mar 2008 08:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YWPGtNpgoA0W
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Wed, 12 Mar 2008 08:50:50 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by core3.amsl.com (Postfix) with ESMTP id 2413D28C309
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 08:50:50 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hermes.tigertech.net (Postfix) with ESMTP id 84C7C1751997
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 08:48:22 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 0BC914A402F
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 14:32:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id D2ABB1C4052B
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 14:32:59 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 2E33D18435A8
	for <capwap@frascone.com>; Mon, 10 Mar 2008 14:32:58 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low);
	Accepted (Sender first seen 00:33:34 ago / SPF check
	softfail: Please see
	http://spf.pobox.com/why.html?sender=hartmans%40mit.edu&ip=72.255.0.202&receiver=tigertech.net)
Received: from s-utl02-dcpop.stsn.net (s-utl02-dcpop.stsn.net [72.255.0.202])
	by hermes.tigertech.net (Postfix) with SMTP
	for <capwap@frascone.com>; Mon, 10 Mar 2008 14:32:57 -0700 (PDT)
Received: from s-utl02-dcpop.stsn.net ([127.0.0.1])
	by s-utl02-dcpop.stsn.net (SMSSMTP 4.1.2.20) with SMTP id
	M2008031016592120905
	for <capwap@frascone.com>; Mon, 10 Mar 2008 16:59:21 -0400
Received: from carter-zimmerman.suchdamage.org ([10.150.132.48])
	by s-utl02-dcpop.stsn.net for capwap@frascone.com;
	Mon, 10 Mar 2008 16:59:21 -0400
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042)
	id D6FFF4771; Mon, 10 Mar 2008 16:59:03 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
References: <4FF84B0BC277FF45AA27FE969DD956A204EDDB9D@xmb-sjc-235.amer.cisco.com>
	<4FF84B0BC277FF45AA27FE969DD956A204EDDBC0@xmb-sjc-235.amer.cisco.com>
	<tslfxxfhx3z.fsf@mit.edu>
	<4FF84B0BC277FF45AA27FE969DD956A2052BC6AC@xmb-sjc-235.amer.cisco.com>
	<tsl8x0qrcf6.fsf@mit.edu>
	<4FF84B0BC277FF45AA27FE969DD956A20550C8DA@xmb-sjc-235.amer.cisco.com>
Date: Mon, 10 Mar 2008 16:59:03 -0400
In-Reply-To: <4FF84B0BC277FF45AA27FE969DD956A20550C8DA@xmb-sjc-235.amer.cisco.com>
	(Pat Calhoun's message of "Mon, 10 Mar 2008 12:17:33 -0700")
Message-ID: <tsliqzupa7c.fsf@mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
X-Mailman-Approved-At: Wed, 12 Mar 2008 08:48:08 -0700
Cc: capwap <capwap@frascone.com>
Subject: Re: [Capwap] Issue 34: keyPurposeID needs clarification
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

>>>>> "Pat" == Pat Calhoun (pacalhou) <pcalhoun@cisco.com> writes:

    Pat> All,
    Pat> The editors, security advisors, chairs and ADs met today at lunch and
    Pat> discussed this topic. We agreed on an approach, which I believe is
    Pat> represented in the following text:

    Pat> <text>
    Pat> If a device presents its certificate which includes either the id-kp-
    Pat> capwapAC or id-kp-capwapWTP EKU, its role MUST be enforced.  For
    Pat> instance, if a certificate received during a DTLS session
    Pat> establishment includes the id-kp-capwapAC EKU, the receiving CAPWAP
    Pat> device MUST NOT allow its peer to act as a WTP.  In the absence of
    Pat> either one of these EKUs, the id-kp-anyExtendedKeyUsage EKU allows a
    Pat> device to act as either a WTP or AC.
    Pat> </text>

The EKU extension is defined in such a way that if a device presents
both keyPurposeIDs then the device is permitted to take on either
role.

I'd say something like
[I'm not looking at RFC 3280, so please double check my capitalization]

All capwap devices MUST support the ExtendedKeyUsage certificate
extension if it is present in a certificate.  If the extension is
present, then the certificate MUST have either the id-kp-
   capwapAC or the id-kp-anyExtendedKeyUsage  keyPurposeID to act as an AC.  Similarly, if the extension is present, a device must have the id-kp-capwapWTP or id-kp-anyExtendedKeyUsage  keyPurposeID to act as a WTP.

--------------------

As a note, the extension is called EKU, but the extension contains multiple keyPurposeIDs

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Wed Mar 12 08:50:52 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 776783A67E1
	for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 12 Mar 2008 08:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[AWL=0.423,
	BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 79fy+tWdRlmY
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Wed, 12 Mar 2008 08:50:48 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by core3.amsl.com (Postfix) with ESMTP id D07333A6E8B
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 08:50:48 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hermes.tigertech.net (Postfix) with ESMTP id 28B1143A096
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 08:48:22 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by fry.tigertech.net (Postfix) with ESMTP id 8F25C4A402F
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 14:22:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id 64B17322A98B
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 14:22:24 -0700 (PDT)
Received: from hgblob.tigertech.net (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id 50F55322AFB1
	for <capwap@frascone.com>; Mon, 10 Mar 2008 14:22:18 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low); Whitelisted (Reverse DNS hostname
	m047e36d0.tmodns.net whitelisted for mit.edu)
Received: from carter-zimmerman.suchdamage.org (m047e36d0.tmodns.net
	[208.54.126.4]) by hgblob.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Mon, 10 Mar 2008 14:22:18 -0700 (PDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042)
	id 9F31E476B; Mon, 10 Mar 2008 08:28:13 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
References: <4FF84B0BC277FF45AA27FE969DD956A204EDDB9D@xmb-sjc-235.amer.cisco.com>
	<4FF84B0BC277FF45AA27FE969DD956A204EDDBC0@xmb-sjc-235.amer.cisco.com>
	<tslfxxfhx3z.fsf@mit.edu>
	<4FF84B0BC277FF45AA27FE969DD956A2052BC6AC@xmb-sjc-235.amer.cisco.com>
Date: Mon, 10 Mar 2008 08:28:13 -0400
In-Reply-To: <4FF84B0BC277FF45AA27FE969DD956A2052BC6AC@xmb-sjc-235.amer.cisco.com>
	(Pat Calhoun's message of "Tue, 12 Feb 2008 21:14:51 -0800")
Message-ID: <tsl8x0qrcf6.fsf@mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
X-Mailman-Approved-At: Wed, 12 Mar 2008 08:48:08 -0700
Cc: capwap <capwap@frascone.com>
Subject: Re: [Capwap] Issue 34: keyPurposeID needs clarification
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

>>>>> "Pat" == Pat Calhoun (pacalhou) <pcalhoun@cisco.com> writes:

    Pat> Sam,
    Pat> Would you accept some text that simply states that the Any KeyPurposeID
    Pat> SHOULD be ignored?

Yes, although I'd like to understand why you believe that's the right
answer.  That's sort of the opposite answer most people give.  But if
you've thought it through and believe that's the right answer that
would respond to my issue.

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Wed Mar 12 08:50:55 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 36D7A3A6E93
	for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 12 Mar 2008 08:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.065
X-Spam-Level: 
X-Spam-Status: No, score=-2.065 tagged_above=-999 required=5
	tests=[AWL=-0.535, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id c07z8N3iiXbB
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Wed, 12 Mar 2008 08:50:51 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by core3.amsl.com (Postfix) with ESMTP id 41DF428C3F1
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 08:50:50 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hermes.tigertech.net (Postfix) with ESMTP id 8DDAD1751998
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 08:48:22 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 067D54EC14B
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 15:08:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id E7F591C4052B
	for <capwap@lists.tigertech.net>; Mon, 10 Mar 2008 15:08:56 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 7D5DB1C40306
	for <capwap@frascone.com>; Mon, 10 Mar 2008 15:08:55 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low);
	Accepted (Sender first seen 01:09:31 ago / SPF check
	softfail: Please see
	http://spf.pobox.com/why.html?sender=hartmans%40mit.edu&ip=72.255.0.202&receiver=tigertech.net)
Received: from s-utl02-dcpop.stsn.net (s-utl02-dcpop.stsn.net [72.255.0.202])
	by hermes.tigertech.net (Postfix) with SMTP
	for <capwap@frascone.com>; Mon, 10 Mar 2008 15:08:54 -0700 (PDT)
Received: from s-utl02-dcpop.stsn.net ([127.0.0.1])
	by s-utl02-dcpop.stsn.net (SMSSMTP 4.1.2.20) with SMTP id
	M2008031017084020968
	for <capwap@frascone.com>; Mon, 10 Mar 2008 17:08:40 -0400
Received: from carter-zimmerman.suchdamage.org ([10.150.132.48])
	by s-utl02-dcpop.stsn.net for capwap@frascone.com;
	Mon, 10 Mar 2008 17:08:28 -0400
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042)
	id 04039476D; Mon, 10 Mar 2008 08:28:46 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
References: <4FF84B0BC277FF45AA27FE969DD956A204EDDBBC@xmb-sjc-235.amer.cisco.com>
	<4FF84B0BC277FF45AA27FE969DD956A204EDDBBF@xmb-sjc-235.amer.cisco.com>
	<tslbq83hws8.fsf@mit.edu>
	<4FF84B0BC277FF45AA27FE969DD956A2052BC6AD@xmb-sjc-235.amer.cisco.com>
Date: Mon, 10 Mar 2008 08:28:46 -0400
In-Reply-To: <4FF84B0BC277FF45AA27FE969DD956A2052BC6AD@xmb-sjc-235.amer.cisco.com>
	(Pat Calhoun's message of "Tue, 12 Feb 2008 21:15:34 -0800")
Message-ID: <tsl4pberce9.fsf@mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
X-Mailman-Approved-At: Wed, 12 Mar 2008 08:48:08 -0700
Cc: capwap <capwap@frascone.com>
Subject: Re: [Capwap] Issue 35: MAC Address in Certificate CN field
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

>>>>> "Pat" == Pat Calhoun (pacalhou) <pcalhoun@cisco.com> writes:

    Pat> Sam,
    Pat> May I simply adopt your proposed text below and close this issue?
Sure.

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Wed Mar 12 11:18:33 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 173A23A676A
	for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 12 Mar 2008 11:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id S20HgPhT52C0
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Wed, 12 Mar 2008 11:18:31 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id E18623A67A7
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 11:18:31 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id 264C0322B65E
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 11:16:13 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 9B5AF4A4069
	for <capwap@lists.tigertech.net>; Wed, 12 Mar 2008 11:15:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 77E231843511
	for <capwap@lists.tigertech.net>; Wed, 12 Mar 2008 11:15:49 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id C3352184325B
	for <capwap@frascone.com>; Wed, 12 Mar 2008 11:15:46 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low);
	Whitelisted (171.71.176.72 whitelisted by
	list.dnswl.org 9.2)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Wed, 12 Mar 2008 11:15:46 -0700 (PDT)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 12 Mar 2008 11:15:46 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m2CIFkJs014014
	for <capwap@frascone.com>; Wed, 12 Mar 2008 11:15:46 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id m2CIFJeC007837
	for <capwap@frascone.com>; Wed, 12 Mar 2008 18:15:46 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Mar 2008 11:15:38 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 12 Mar 2008 11:15:37 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A2055953FE@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Issue 40: State Machine inconsistency around Discovery being
	optional
Thread-Index: AciEbRHbjEQnzy6hRTahlSJ/7FK9HA==
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: <capwap@frascone.com>
X-OriginalArrivalTime: 12 Mar 2008 18:15:38.0828 (UTC)
	FILETIME=[133018C0:01C8846D]
Authentication-Results: sj-dkim-1; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Subject: [Capwap] Issue 40: State Machine inconsistency around Discovery
	being optional
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

Scott Kelly raised an issue during the IETF meeting in Philadelphia
where the 
new state machine has some inconsistencies on whether Discovery Requests
are 
optional on the AC.

More details can be found on the powerpoint he presented at the meeting.

PatC
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Wed Mar 12 11:35:47 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5972F3A6C15
	for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 12 Mar 2008 11:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level: 
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5
	tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_PILL=2.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Nyv5it+MwI7R
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Wed, 12 Mar 2008 11:35:45 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by core3.amsl.com (Postfix) with ESMTP id EA5113A6859
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 11:35:45 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hermes.tigertech.net (Postfix) with ESMTP id BD8E01C40E62
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 11:33:27 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 7F1824A4069
	for <capwap@lists.tigertech.net>; Wed, 12 Mar 2008 11:33:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 5F3B81843981
	for <capwap@lists.tigertech.net>; Wed, 12 Mar 2008 11:33:16 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 940661843511
	for <capwap@frascone.com>; Wed, 12 Mar 2008 11:33:14 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low);
	Whitelisted (171.71.176.117 whitelisted by
	list.dnswl.org 9.2)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Wed, 12 Mar 2008 11:33:14 -0700 (PDT)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 12 Mar 2008 11:33:14 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m2CIXD9J017869
	for <capwap@frascone.com>; Wed, 12 Mar 2008 11:33:13 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m2CIXCgK015642
	for <capwap@frascone.com>; Wed, 12 Mar 2008 18:33:13 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Mar 2008 11:33:12 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 12 Mar 2008 11:33:11 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A205595420@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposed Text: Issue 40: State Machine inconsistency around
	Discovery being optional
Thread-Index: AciEb4a0QKCfd6YvTCOM7Tnum/mONA==
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: <capwap@frascone.com>
X-OriginalArrivalTime: 12 Mar 2008 18:33:12.0978 (UTC)
	FILETIME=[87829F20:01C8846F]
Authentication-Results: sj-dkim-1; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Subject: [Capwap] Proposed Text: Issue 40: State Machine inconsistency
	around Discovery being optional
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

All,

Following up on issue 40, which was created as a result of the
presentation made during the face to face in Philadelphia, I am
including here the proposed text. The issue, as described by Scott, was
that the text was inconsistent when it came to whether Discovery
Requests should be optional. Of note, the Listener state was expected to
call DTLSListen() when an event would occur, but if no Discovery
Requests were received, no event would cause the function to be called,
and therefore no incoming DTLS sessions would be accepted.

The fix is to introduce a new thread, called Discovery. It is
responsible for the handling of the Discovery Requests on the AC. The
listener thread now sits in DTLSListen(), and when a ClientHello has
been validated, a notification is received causing the state transition
to move to the Authorized state, which is the trigger that causes the
Listener thread to for a WTP specific Service thread.

Note that I am only including the modified text. The state labels were
changed, and I did not include the modified text that reflects that
because it would be too complex to identify the changes for issue 40.

As we agreed during the meeting, the plan is to submit the -10 version
by week's end so the chairs can start the WG last call. I would
appreciate a quick review.

<text>
2.3.  CAPWAP State Machine Definition
[...]

                            /-------------------------------------\
                            |          /-------------------------\|
                            |         p|                         ||
                            |    q+----------+ r +------------+  ||
                            |     |   Run    |-->|   Reset    |-\||
                            |     +----------+   +------------+ |||
                           n|  o      ^           ^     ^      s|||
                +------------+--------/           |     |       |||
                | Data Check |             /-------/    |       |||
                +------------+<-------\   |             |       |||
                                      |   |             |       |||
                       /------------------+--------\    |       |||
                      f|             m|  h|    j   v   k|       |||
               +--------+     +-----------+     +--------------+|||
               |  Join  |---->| Configure |     |  Image Data  ||||
               +--------+  n  +-----------+     +--------------+|||
                ^   |g                 i|                    l| |||
                |   |                   \-------------------\ | |||
                |   \--------------------------------------\| | |||
                \------------------------\                 || | |||
         /--------------<----------------+---------------\ || | |||
         | /------------<----------------+-------------\ | || | |||
         | |  4                          |d           t| | vv v vvv
         | |   +----------------+   +--------------+   +-----------+
         | |   |   DTLS Setup   |   | DTLS Connect |-->|  DTLS TD  |
       /-|-|---+----------------+   +--------------+ e +-----------+
       | | |    |$  ^  ^   |5  ^6         ^              ^  |w
       v v v    |   |  |   |   \-------\  |              |  |
       | | |    |   |  |   \---------\ |  |  /-----------/  |
       | | |    |   |  \--\          | |  |  |              |
       | | |    |   |     |          | |  |  |              |
       | | |    v  3|  1  |%     #   v |  |a |b             v
       | | \->+------+-->+------+   +-----------+    +--------+
       | |    | Idle |   | Disc |   | Authorize |    |  Dead  |
       | |    +------+<--+------+   +-----------+    +--------+
       | |     ^   0^  2      |!
       | |     |    |         |   +-------+
      *| |u    |    \---------+---| Start |
       | |     |@             |   +-------+
       | \->+---------+<------/
       \--->| Sulking |
            +---------+&

[...]
   Since the WTP only communicates with a single AC, it only has a
   single instance of the CAPWAP state machine.  The state machine works
   differently on the AC since it communicates with many WTPs.  The AC
   uses the concept of three threads.  Note that the term thread used
   here does not necessarily imply that implementers must use threads,
   but it is one possible way of implementing the AC's state machine.

   Listener Thread:   The AC's Listener thread handles inbound DTLS
      session establishment requests, through the DTLSListen command.
      Upon creation, the Listener thread starts in the DTLS Setup state.
      Once a DTLS session has been validated, which occurs when the
      state machine enters the "Authorize" state, the Listener thread
      creates a WTP session specific Service thread and state context.
      The state machine transitions in figure Figure 3 are represented
      by numerals.  It is necessary for the AC to protect itself against
      various attacks that exist with non-authenticated frames.  See
      Section 12 for more information.

   Discovery Thread:   The AC's Discovery thread is responsible for
      receiving, and responding to, Discovery Request messages.  The
      state machine transitions in figure Figure 3 are represented by
      numerals.  Note that the Discovery thread does not maintain any
      per-WTP specific context information, and a single state context
      exists.  It is necessary for the AC to protect itself against
      various attacks that exist with non-authenticated frames.  See
      Section 12 for more information.

   Service Thread:   The AC's Service thread handles the per-WTP states,
      and one such thread exists per-WTP connection.  This thread is
      created by the listener thread when the Authorize state is
      reached.  When created, the Service thread inherits a copy of the
      state machine context from the Listener thread.  When
      communication with the WTP is complete, the Service thread is
      terminated and all associated resources are released.  The state
      machine transitions in figure Figure 3 are represented by
      alphabetic characters.

2.3.1.  CAPWAP Protocol State Transitions
[...]

   Start to Idle (0):  This transition occurs once device initialization
      is complete.

      WTP:  This state transition is used to start the WTP's CAPWAP
         state machine.

      AC:  The AC creates the Discovery and Listener threads and starts
         the CAPWAP state machine.

   Idle to Discovery (1):  This transition occurs to support the CAPWAP
      discovery process .

      WTP:  The WTP enters the Discovery state prior to transmitting the
         first Discovery Request message (see Section 5.1).  Upon
         entering this state, the WTP sets the DiscoveryInterval timer
         (see Section 4.7).  The WTP resets the DiscoveryCount counter
         to zero (0) (see Section 4.8).  The WTP also clears all
         information from ACs it may have received during a previous
         Discovery phase.

      AC:  This state transition is executed by the AC's Discovery
         thread, and occurs when a Discovery Request message is
         received.  The AC SHOULD respond with a Discovery Response
         message (see Section 5.2).

[...]
   Discovery to Idle (2):  This transition occurs on the AC's Discovery
      thread when the Discovery processing is complete.

      WTP:  This is an invalid state transition for the WTP.

      AC:  This state transition is executed by the AC's Discovery
         thread when it has transmitted the Discovery Response, in
         response to a Discovery Request.
[...]

   Idle to DTLS Setup (3):  This transition occurs to establish a secure
      DTLS session with the peer.

      WTP:  The WTP initiates this transition by invoking the DTLSStart
         command, which starts the DTLS session establishment with the
         chosen AC.  When the discovery phase is bypassed, it is assumed
         the WTP has locally configured ACs.

      AC:  Upon entering the Idle state from the Start state, the newly
         created Listener thread automatically transitions to the DTLS
         Setup and invokes the DTLSListen command (see Section 2.3.2.1).
[...]

   DTLS Setup to DTLS Setup (4):  This transition occurs when the DTLS
      Session failed to be established.

      WTP:  This is an invalid state transition for the WTP.

      AC:  The AC's Listener initiates this state transition when it
         receives a DTLSEstablishFail notification from DTLS (see
         Section 2.3.2.2).  This error notification aborts the secure
         DTLS session establishment.  When this notification is
         received, the FailedDTLSSessionCount counter is incremented.
         The Listener thread then invokes the DTLSListen command (see
         Section 2.3.2.1).

   DTLS Setup to Authorize (5):  This transition occurs when an incoming
      DTLS session is being established, and the DTLS stack needs
      authorization to proceed with the session establishment.

      WTP:  This state transition occurs when the WTP receives the
         DTLSPeerAuthorize notification (see Section 2.3.2.2).  Upon
         entering this state, the WTP performs an authorization check
         against the AC credentials.  See Section 2.4.4 for more
         information on AC authorization.

      AC:  This state transition is handled by the AC's Listener thread
         when the DTLS module initiates the DTLSPeerAuthorize
         notification (see Section 2.3.2.2).  The Listener thread forks
         an instance of the Service thread, along with a copy of the
         state context.  Once created, the Service thread performs an
         authorization check against the WTP credentials.  See
         Section 2.4.4 for more information on WTP authorization.

   Authorize to DTLS Setup (6):  This transition is executed by the
      Listener thread to enable it to listen for new incoming sessions.

      WTP:  This is an invalid state transition for the WTP.

      AC:  This state transition occurs when the AC's Listener thread
         has created the WTP context and the Service thread.  The
         Listener thread then invokes the DTLSListen command (see
         Section 2.3.2.1).
[...]

12.3.  Discovery or DTLS Setup Attacks
[...]
   Some CAPWAP implementations may wish to restrict the DTLS setup
   process to only those peers that have been configured in the access
   control list, authorizing only those clients to initiate a DTLS
   handshake.  Note that the impact of this on mitigating denial of
   service attacks against the DTLS layer is minimal, because DTLS
   already uses client-side cookies to minimize processor consumption
   attacks.
</text>


Further, in the process of making this change, two state transitions
were removed (one of them was actually duplicative. Here is the removed
text from -09.

<removed text>
   DTLS Connect to DTLS Teardown (7):  This transition occurs when the
      DTLS Session failed to be established.

      WTP:  This state transition occurs when the WTP receives either a
         DTLSAborted or DTLSAuthenticateFail notification (see
         Section 2.3.2.2), indicating that the DTLS session was not
         successfully established.  When this transition occurs due to
         the DTLSAuthenticateFail notification, the
         FailedDTLSAuthFailCount is incremented, otherwise the
         FailedDTLSSessionCount counter is incremented.

      AC:  This is an invalid state transition for the AC.

   DTLS Connect to Dead (j):  This transition occurs when the DTLS
      Session failed to be established.

      WTP:  This is an invalid state transition for the WTP.

      AC:  This state transition occurs when the AC receives either a
         DTLSAborted or DTLSAuthenticateFail notification (see
         Section 2.3.2.2), indicating that the DTLS session was not
         successfully established, and either the
         FailedDTLSAuthFailCount and FailedDTLSSessionCount counters
         have reached the value of the MaxFailedDTLSSessionRetry
         variable (see Section 4.8).
</removed text>

Comments?
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Wed Mar 12 12:49:09 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3A343A6A4A
	for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 12 Mar 2008 12:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id e+pRSjGh1NmH
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Wed, 12 Mar 2008 12:49:04 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by core3.amsl.com (Postfix) with ESMTP id 10A3D3A6F2A
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 12:49:04 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hermes.tigertech.net (Postfix) with ESMTP id E89121C407AD
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 12:46:45 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 3BBD84A4069
	for <capwap@lists.tigertech.net>; Wed, 12 Mar 2008 12:46:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id EDEE5184325B
	for <capwap@lists.tigertech.net>; Wed, 12 Mar 2008 12:46:35 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 686951843627
	for <capwap@frascone.com>; Wed, 12 Mar 2008 12:46:34 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low); Accepted (Neutral)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Wed, 12 Mar 2008 12:46:34 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m2CJkqcs005221; Wed, 12 Mar 2008 14:48:16 -0500
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Mar 2008 21:44:47 +0200
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Mar 2008 14:44:39 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 12 Mar 2008 14:44:38 -0500
Message-ID: <2198383E1141814486F0B881B3260CF5020C987F@daebe103.NOE.Nokia.com>
In-Reply-To: <4FF84B0BC277FF45AA27FE969DD956A2053167F1@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Capwap] Issue 35: MAC Address in Certificate CN field
Thread-Index: AchOC09e6c/UUdACQcWhmLQL6YV6hgf9BPNwAHl+ncAFJIwQIA==
References: <4FF84B0BC277FF45AA27FE969DD956A204EDDBBC@xmb-sjc-235.amer.cisco.com><4FF84B0BC277FF45AA27FE969DD956A204EDDBBF@xmb-sjc-235.amer.cisco.com><tslbq83hws8.fsf@mit.edu><4FF84B0BC277FF45AA27FE969DD956A2052BC6AD@xmb-sjc-235.amer.cisco.com>
	<4FF84B0BC277FF45AA27FE969DD956A2053167F1@xmb-sjc-235.amer.cisco.com>
From: <Michael.G.Williams@nokia.com>
To: <pcalhoun@cisco.com>, <hartmans-ietf@mit.edu>
X-OriginalArrivalTime: 12 Mar 2008 19:44:39.0102 (UTC)
	FILETIME=[823D3DE0:01C88479]
X-Nokia-AV: Clean
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: capwap@frascone.com
Subject: Re: [Capwap] Issue 35: MAC Address in Certificate CN field
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

Just to be clear, this doesn't mandate the CN field to be MAC, it just
says that if the CN in a MAC it has to be EUI 48 or 64, correct?

For the record, I think it's a bad idea to be using the MAC address for
the identity here. Also, as was pointed out, even if the CN is a MAC
address it's not reasonable to assume the MAC address presented is being
used by the peer, is unique, is 'valid', etc etc. It's meant as an
address for local link usage. Rather than overloading it there should be
things used for the right purpose instead.

Best Regards,
Michael 

>-----Original Message-----
>From: ext Pat Calhoun (pacalhou) [mailto:pcalhoun@cisco.com] 
>Sent: 15 February, 2008 09:14
>To: Pat Calhoun (pacalhou); Sam Hartman
>Cc: capwap
>Subject: Re: [Capwap] Issue 35: MAC Address in Certificate CN field
>
>All,
>
>The new text reads:
>
>   CAPWAP implementations MUST support certificates where the common
>   name (CN) for both the WTP and AC is the MAC address of that device.
>   The MAC address MUST be formatted as ASCII HEX, e.g.
>   01:23:45:67:89:ab.  Note that the CN field MAY contain either of the
>   EUI-48 [22] or EUI-64 [23] MAC Address formats.
>
>PatC 
>
>-----Original Message-----
>From: Pat Calhoun (pacalhou)
>Sent: Tuesday, February 12, 2008 9:16 PM
>To: Sam Hartman
>Cc: capwap
>Subject: Re: [Capwap] Issue 35: MAC Address in Certificate CN field
>
>Sam,
>
>May I simply adopt your proposed text below and close this issue?
>
>PatC 
>
>-----Original Message-----
>From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
>Sent: Thursday, January 03, 2008 5:19 AM
>To: Pat Calhoun (pacalhou)
>Cc: capwap
>Subject: Re: [Capwap] Issue 35: MAC Address in Certificate CN field
>
>>>>>> "Pat" == Pat Calhoun (pacalhou) <pcalhoun@cisco.com> writes:
>
>    Pat> The intention is the for AC and WTPs to validate the CN
>    Pat> through an access control list. This could be done via a
>    Pat> RADIUS request, a locally stored MAC address list, etc. As
>    Pat> long as the certificate is valid, and authorized, it really
>    Pat> doesn't matter whether the device in question is actually
>    Pat> using the MAC address encoded in the CN field, and as you
>    Pat> state, this is not possible to do if a router is present.
>
>Ah.
>This was not obvious to me.
>If the intent is to validate against an ACL, then I think the 
>following requirement  does not rise to the level needed for 
>an RFC 2119 MUST:
>
>>   The certificate common name (CN) for both the WTP and AC 
>MUST be the
>>   MAC address of that device.  The MAC address MUST be formatted as
>>   ASCII HEX, e.g. 01:23:45:67:89:ab.
>
>
>In particular, that's a requirement on operational deployments 
>rather than a requirement on implementations and if all you 
>are going to do is to check against an ACL then I don't see a 
>need for that requirement.
>
>Perhaps something more like the following would be an 
>appropriate requirement to meet interoperability:
>
>
>
>>   Capwap implementations MUST support certificates where the  common
>name (CN) for both the WTP and AC is the
>>   MAC address of that device.  The MAC address MUST be formatted as
>>   ASCII HEX, e.g. 01:23:45:67:89:ab.
>
>
>You should be aware that there is a raging debate in the 
>security directorate about whether storing MAC addresses in a 
>CN field is appropriate for a mandatory to implement solution. 
> I have not read that debate so I don't know if there is a 
>consensus there one way or another.
>_________________________________________________________________
>To unsubscribe or modify your subscription options, please visit:
>http://lists.frascone.com/mailman/listinfo/capwap
>
>Archives: http://lists.frascone.com/pipermail/capwap
>_________________________________________________________________
>To unsubscribe or modify your subscription options, please visit:
>http://lists.frascone.com/mailman/listinfo/capwap
>
>Archives: http://lists.frascone.com/pipermail/capwap
>
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Wed Mar 12 13:57:38 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A287628C56F
	for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 12 Mar 2008 13:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.471
X-Spam-Level: 
X-Spam-Status: No, score=-2.471 tagged_above=-999 required=5 tests=[AWL=0.128,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9TRJ4Zk9WHHb
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Wed, 12 Mar 2008 13:57:36 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id 4F7C53A6962
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 13:56:59 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id 1E4D1322B3E0
	for <capwap-archive@lists.ietf.org>; Wed, 12 Mar 2008 13:54:41 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 039A54A4069
	for <capwap@lists.tigertech.net>; Wed, 12 Mar 2008 13:53:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id B9CA8184325B
	for <capwap@lists.tigertech.net>; Wed, 12 Mar 2008 13:53:52 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id E889A1843511
	for <capwap@frascone.com>; Wed, 12 Mar 2008 13:53:50 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low);
	Whitelisted (171.71.176.117 whitelisted by
	list.dnswl.org 9.2)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Wed, 12 Mar 2008 13:53:50 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 12 Mar 2008 13:53:46 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m2CKrjGN022650; 
	Wed, 12 Mar 2008 13:53:45 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id m2CKrSvq024379;
	Wed, 12 Mar 2008 20:53:37 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Mar 2008 13:53:18 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 12 Mar 2008 13:53:18 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A205595535@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <2198383E1141814486F0B881B3260CF5020C987F@daebe103.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Capwap] Issue 35: MAC Address in Certificate CN field
Thread-Index: AchOC09e6c/UUdACQcWhmLQL6YV6hgf9BPNwAHl+ncAFJIwQIAAC1/Tg
References: <4FF84B0BC277FF45AA27FE969DD956A204EDDBBC@xmb-sjc-235.amer.cisco.com><4FF84B0BC277FF45AA27FE969DD956A204EDDBBF@xmb-sjc-235.amer.cisco.com><tslbq83hws8.fsf@mit.edu><4FF84B0BC277FF45AA27FE969DD956A2052BC6AD@xmb-sjc-235.amer.cisco.com>
	<4FF84B0BC277FF45AA27FE969DD956A2053167F1@xmb-sjc-235.amer.cisco.com>
	<2198383E1141814486F0B881B3260CF5020C987F@daebe103.NOE.Nokia.com>
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: <Michael.G.Williams@nokia.com>, <hartmans-ietf@mit.edu>
X-OriginalArrivalTime: 12 Mar 2008 20:53:18.0757 (UTC)
	FILETIME=[19BEB550:01C88483]
Authentication-Results: sj-dkim-2; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: capwap@frascone.com
Subject: Re: [Capwap] Issue 35: MAC Address in Certificate CN field
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

Correct. It states that the MAC Address MUST be supported, not that it
MUST be used.

This has been the identifier used since the original spec, and honestly
do not see a reason to change it. If folks want to use another format,
they can.

PatC 

-----Original Message-----
From: Michael.G.Williams@nokia.com [mailto:Michael.G.Williams@nokia.com]

Sent: Wednesday, March 12, 2008 12:45 PM
To: Pat Calhoun (pacalhou); hartmans-ietf@mit.edu
Cc: capwap@frascone.com
Subject: RE: [Capwap] Issue 35: MAC Address in Certificate CN field

Just to be clear, this doesn't mandate the CN field to be MAC, it just
says that if the CN in a MAC it has to be EUI 48 or 64, correct?

For the record, I think it's a bad idea to be using the MAC address for
the identity here. Also, as was pointed out, even if the CN is a MAC
address it's not reasonable to assume the MAC address presented is being
used by the peer, is unique, is 'valid', etc etc. It's meant as an
address for local link usage. Rather than overloading it there should be
things used for the right purpose instead.

Best Regards,
Michael 

>-----Original Message-----
>From: ext Pat Calhoun (pacalhou) [mailto:pcalhoun@cisco.com]
>Sent: 15 February, 2008 09:14
>To: Pat Calhoun (pacalhou); Sam Hartman
>Cc: capwap
>Subject: Re: [Capwap] Issue 35: MAC Address in Certificate CN field
>
>All,
>
>The new text reads:
>
>   CAPWAP implementations MUST support certificates where the common
>   name (CN) for both the WTP and AC is the MAC address of that device.
>   The MAC address MUST be formatted as ASCII HEX, e.g.
>   01:23:45:67:89:ab.  Note that the CN field MAY contain either of the
>   EUI-48 [22] or EUI-64 [23] MAC Address formats.
>
>PatC
>
>-----Original Message-----
>From: Pat Calhoun (pacalhou)
>Sent: Tuesday, February 12, 2008 9:16 PM
>To: Sam Hartman
>Cc: capwap
>Subject: Re: [Capwap] Issue 35: MAC Address in Certificate CN field
>
>Sam,
>
>May I simply adopt your proposed text below and close this issue?
>
>PatC
>
>-----Original Message-----
>From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
>Sent: Thursday, January 03, 2008 5:19 AM
>To: Pat Calhoun (pacalhou)
>Cc: capwap
>Subject: Re: [Capwap] Issue 35: MAC Address in Certificate CN field
>
>>>>>> "Pat" == Pat Calhoun (pacalhou) <pcalhoun@cisco.com> writes:
>
>    Pat> The intention is the for AC and WTPs to validate the CN
>    Pat> through an access control list. This could be done via a
>    Pat> RADIUS request, a locally stored MAC address list, etc. As
>    Pat> long as the certificate is valid, and authorized, it really
>    Pat> doesn't matter whether the device in question is actually
>    Pat> using the MAC address encoded in the CN field, and as you
>    Pat> state, this is not possible to do if a router is present.
>
>Ah.
>This was not obvious to me.
>If the intent is to validate against an ACL, then I think the following

>requirement  does not rise to the level needed for an RFC 2119 MUST:
>
>>   The certificate common name (CN) for both the WTP and AC
>MUST be the
>>   MAC address of that device.  The MAC address MUST be formatted as
>>   ASCII HEX, e.g. 01:23:45:67:89:ab.
>
>
>In particular, that's a requirement on operational deployments rather 
>than a requirement on implementations and if all you are going to do is

>to check against an ACL then I don't see a need for that requirement.
>
>Perhaps something more like the following would be an appropriate 
>requirement to meet interoperability:
>
>
>
>>   Capwap implementations MUST support certificates where the  common
>name (CN) for both the WTP and AC is the
>>   MAC address of that device.  The MAC address MUST be formatted as
>>   ASCII HEX, e.g. 01:23:45:67:89:ab.
>
>
>You should be aware that there is a raging debate in the security 
>directorate about whether storing MAC addresses in a CN field is 
>appropriate for a mandatory to implement solution.
> I have not read that debate so I don't know if there is a consensus 
>there one way or another.
>_________________________________________________________________
>To unsubscribe or modify your subscription options, please visit:
>http://lists.frascone.com/mailman/listinfo/capwap
>
>Archives: http://lists.frascone.com/pipermail/capwap
>_________________________________________________________________
>To unsubscribe or modify your subscription options, please visit:
>http://lists.frascone.com/mailman/listinfo/capwap
>
>Archives: http://lists.frascone.com/pipermail/capwap
>
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Thu Mar 13 11:23:27 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DDB6A3A6B9B
	for <ietfarch-capwap-archive@core3.amsl.com>; Thu, 13 Mar 2008 11:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MANGLED_PILL=2.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id suIdgHAtB1L8
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Thu, 13 Mar 2008 11:23:26 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id 735B23A6CBF
	for <capwap-archive@lists.ietf.org>; Thu, 13 Mar 2008 11:23:26 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id EF416322B4BE
	for <capwap-archive@lists.ietf.org>; Thu, 13 Mar 2008 11:21:08 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 687F94A4037
	for <capwap@lists.tigertech.net>; Thu, 13 Mar 2008 11:20:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 54B9E1C4050D
	for <capwap@lists.tigertech.net>; Thu, 13 Mar 2008 11:20:39 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 7DBC11750206
	for <capwap@frascone.com>; Thu, 13 Mar 2008 11:20:37 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low); Accepted (Neutral)
Received: from elasmtp-banded.atl.sa.earthlink.net
	(elasmtp-banded.atl.sa.earthlink.net [209.86.89.70])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Thu, 13 Mar 2008 11:20:36 -0700 (PDT)
Received: from [209.86.224.31] (helo=elwamui-chisos.atl.sa.earthlink.net)
	by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67)
	(envelope-from <s.kelly@ix.netcom.com>)
	id 1JZs2d-0002fd-Ml; Thu, 13 Mar 2008 14:20:35 -0400
Received: from 24.6.132.243 by webmail.pas.earthlink.net with HTTP;
	Thu, 13 Mar 2008 14:20:35 -0400
Message-ID: <28745082.1205432435642.JavaMail.root@elwamui-chisos.atl.sa.earthlink.net>
Date: Thu, 13 Mar 2008 11:20:35 -0700 (GMT-07:00)
From: "Scott G. Kelly" <s.kelly@ix.netcom.com>
To: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>,
	capwap@frascone.com
Mime-Version: 1.0
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 5b98cdd91c374dcd776432462e451d7b7f19f0d9c038d9aa502106b061bbbc3c55879df40efd1bf6350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.31
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Subject: Re: [Capwap] Proposed Text: Issue 40: State Machine
	inconsistency	around Discovery being optional
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "Scott G. Kelly" <scott@hyperthought.com>
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

This looks fine to me.

-----Original Message-----
>From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
>Sent: Mar 12, 2008 11:33 AM
>To: capwap@frascone.com
>Subject: [Capwap] Proposed Text: Issue 40: State Machine inconsistency	around Discovery being optional
>
>All,
>
>Following up on issue 40, which was created as a result of the
>presentation made during the face to face in Philadelphia, I am
>including here the proposed text. The issue, as described by Scott, was
>that the text was inconsistent when it came to whether Discovery
>Requests should be optional. Of note, the Listener state was expected to
>call DTLSListen() when an event would occur, but if no Discovery
>Requests were received, no event would cause the function to be called,
>and therefore no incoming DTLS sessions would be accepted.
>
>The fix is to introduce a new thread, called Discovery. It is
>responsible for the handling of the Discovery Requests on the AC. The
>listener thread now sits in DTLSListen(), and when a ClientHello has
>been validated, a notification is received causing the state transition
>to move to the Authorized state, which is the trigger that causes the
>Listener thread to for a WTP specific Service thread.
>
>Note that I am only including the modified text. The state labels were
>changed, and I did not include the modified text that reflects that
>because it would be too complex to identify the changes for issue 40.
>
>As we agreed during the meeting, the plan is to submit the -10 version
>by week's end so the chairs can start the WG last call. I would
>appreciate a quick review.
>
><text>
>2.3.  CAPWAP State Machine Definition
>[...]
>
>                            /-------------------------------------\
>                            |          /-------------------------\|
>                            |         p|                         ||
>                            |    q+----------+ r +------------+  ||
>                            |     |   Run    |-->|   Reset    |-\||
>                            |     +----------+   +------------+ |||
>                           n|  o      ^           ^     ^      s|||
>                +------------+--------/           |     |       |||
>                | Data Check |             /-------/    |       |||
>                +------------+<-------\   |             |       |||
>                                      |   |             |       |||
>                       /------------------+--------\    |       |||
>                      f|             m|  h|    j   v   k|       |||
>               +--------+     +-----------+     +--------------+|||
>               |  Join  |---->| Configure |     |  Image Data  ||||
>               +--------+  n  +-----------+     +--------------+|||
>                ^   |g                 i|                    l| |||
>                |   |                   \-------------------\ | |||
>                |   \--------------------------------------\| | |||
>                \------------------------\                 || | |||
>         /--------------<----------------+---------------\ || | |||
>         | /------------<----------------+-------------\ | || | |||
>         | |  4                          |d           t| | vv v vvv
>         | |   +----------------+   +--------------+   +-----------+
>         | |   |   DTLS Setup   |   | DTLS Connect |-->|  DTLS TD  |
>       /-|-|---+----------------+   +--------------+ e +-----------+
>       | | |    |$  ^  ^   |5  ^6         ^              ^  |w
>       v v v    |   |  |   |   \-------\  |              |  |
>       | | |    |   |  |   \---------\ |  |  /-----------/  |
>       | | |    |   |  \--\          | |  |  |              |
>       | | |    |   |     |          | |  |  |              |
>       | | |    v  3|  1  |%     #   v |  |a |b             v
>       | | \->+------+-->+------+   +-----------+    +--------+
>       | |    | Idle |   | Disc |   | Authorize |    |  Dead  |
>       | |    +------+<--+------+   +-----------+    +--------+
>       | |     ^   0^  2      |!
>       | |     |    |         |   +-------+
>      *| |u    |    \---------+---| Start |
>       | |     |@             |   +-------+
>       | \->+---------+<------/
>       \--->| Sulking |
>            +---------+&
>
>[...]
>   Since the WTP only communicates with a single AC, it only has a
>   single instance of the CAPWAP state machine.  The state machine works
>   differently on the AC since it communicates with many WTPs.  The AC
>   uses the concept of three threads.  Note that the term thread used
>   here does not necessarily imply that implementers must use threads,
>   but it is one possible way of implementing the AC's state machine.
>
>   Listener Thread:   The AC's Listener thread handles inbound DTLS
>      session establishment requests, through the DTLSListen command.
>      Upon creation, the Listener thread starts in the DTLS Setup state.
>      Once a DTLS session has been validated, which occurs when the
>      state machine enters the "Authorize" state, the Listener thread
>      creates a WTP session specific Service thread and state context.
>      The state machine transitions in figure Figure 3 are represented
>      by numerals.  It is necessary for the AC to protect itself against
>      various attacks that exist with non-authenticated frames.  See
>      Section 12 for more information.
>
>   Discovery Thread:   The AC's Discovery thread is responsible for
>      receiving, and responding to, Discovery Request messages.  The
>      state machine transitions in figure Figure 3 are represented by
>      numerals.  Note that the Discovery thread does not maintain any
>      per-WTP specific context information, and a single state context
>      exists.  It is necessary for the AC to protect itself against
>      various attacks that exist with non-authenticated frames.  See
>      Section 12 for more information.
>
>   Service Thread:   The AC's Service thread handles the per-WTP states,
>      and one such thread exists per-WTP connection.  This thread is
>      created by the listener thread when the Authorize state is
>      reached.  When created, the Service thread inherits a copy of the
>      state machine context from the Listener thread.  When
>      communication with the WTP is complete, the Service thread is
>      terminated and all associated resources are released.  The state
>      machine transitions in figure Figure 3 are represented by
>      alphabetic characters.
>
>2.3.1.  CAPWAP Protocol State Transitions
>[...]
>
>   Start to Idle (0):  This transition occurs once device initialization
>      is complete.
>
>      WTP:  This state transition is used to start the WTP's CAPWAP
>         state machine.
>
>      AC:  The AC creates the Discovery and Listener threads and starts
>         the CAPWAP state machine.
>
>   Idle to Discovery (1):  This transition occurs to support the CAPWAP
>      discovery process .
>
>      WTP:  The WTP enters the Discovery state prior to transmitting the
>         first Discovery Request message (see Section 5.1).  Upon
>         entering this state, the WTP sets the DiscoveryInterval timer
>         (see Section 4.7).  The WTP resets the DiscoveryCount counter
>         to zero (0) (see Section 4.8).  The WTP also clears all
>         information from ACs it may have received during a previous
>         Discovery phase.
>
>      AC:  This state transition is executed by the AC's Discovery
>         thread, and occurs when a Discovery Request message is
>         received.  The AC SHOULD respond with a Discovery Response
>         message (see Section 5.2).
>
>[...]
>   Discovery to Idle (2):  This transition occurs on the AC's Discovery
>      thread when the Discovery processing is complete.
>
>      WTP:  This is an invalid state transition for the WTP.
>
>      AC:  This state transition is executed by the AC's Discovery
>         thread when it has transmitted the Discovery Response, in
>         response to a Discovery Request.
>[...]
>
>   Idle to DTLS Setup (3):  This transition occurs to establish a secure
>      DTLS session with the peer.
>
>      WTP:  The WTP initiates this transition by invoking the DTLSStart
>         command, which starts the DTLS session establishment with the
>         chosen AC.  When the discovery phase is bypassed, it is assumed
>         the WTP has locally configured ACs.
>
>      AC:  Upon entering the Idle state from the Start state, the newly
>         created Listener thread automatically transitions to the DTLS
>         Setup and invokes the DTLSListen command (see Section 2.3.2.1).
>[...]
>
>   DTLS Setup to DTLS Setup (4):  This transition occurs when the DTLS
>      Session failed to be established.
>
>      WTP:  This is an invalid state transition for the WTP.
>
>      AC:  The AC's Listener initiates this state transition when it
>         receives a DTLSEstablishFail notification from DTLS (see
>         Section 2.3.2.2).  This error notification aborts the secure
>         DTLS session establishment.  When this notification is
>         received, the FailedDTLSSessionCount counter is incremented.
>         The Listener thread then invokes the DTLSListen command (see
>         Section 2.3.2.1).
>
>   DTLS Setup to Authorize (5):  This transition occurs when an incoming
>      DTLS session is being established, and the DTLS stack needs
>      authorization to proceed with the session establishment.
>
>      WTP:  This state transition occurs when the WTP receives the
>         DTLSPeerAuthorize notification (see Section 2.3.2.2).  Upon
>         entering this state, the WTP performs an authorization check
>         against the AC credentials.  See Section 2.4.4 for more
>         information on AC authorization.
>
>      AC:  This state transition is handled by the AC's Listener thread
>         when the DTLS module initiates the DTLSPeerAuthorize
>         notification (see Section 2.3.2.2).  The Listener thread forks
>         an instance of the Service thread, along with a copy of the
>         state context.  Once created, the Service thread performs an
>         authorization check against the WTP credentials.  See
>         Section 2.4.4 for more information on WTP authorization.
>
>   Authorize to DTLS Setup (6):  This transition is executed by the
>      Listener thread to enable it to listen for new incoming sessions.
>
>      WTP:  This is an invalid state transition for the WTP.
>
>      AC:  This state transition occurs when the AC's Listener thread
>         has created the WTP context and the Service thread.  The
>         Listener thread then invokes the DTLSListen command (see
>         Section 2.3.2.1).
>[...]
>
>12.3.  Discovery or DTLS Setup Attacks
>[...]
>   Some CAPWAP implementations may wish to restrict the DTLS setup
>   process to only those peers that have been configured in the access
>   control list, authorizing only those clients to initiate a DTLS
>   handshake.  Note that the impact of this on mitigating denial of
>   service attacks against the DTLS layer is minimal, because DTLS
>   already uses client-side cookies to minimize processor consumption
>   attacks.
></text>
>
>
>Further, in the process of making this change, two state transitions
>were removed (one of them was actually duplicative. Here is the removed
>text from -09.
>
><removed text>
>   DTLS Connect to DTLS Teardown (7):  This transition occurs when the
>      DTLS Session failed to be established.
>
>      WTP:  This state transition occurs when the WTP receives either a
>         DTLSAborted or DTLSAuthenticateFail notification (see
>         Section 2.3.2.2), indicating that the DTLS session was not
>         successfully established.  When this transition occurs due to
>         the DTLSAuthenticateFail notification, the
>         FailedDTLSAuthFailCount is incremented, otherwise the
>         FailedDTLSSessionCount counter is incremented.
>
>      AC:  This is an invalid state transition for the AC.
>
>   DTLS Connect to Dead (j):  This transition occurs when the DTLS
>      Session failed to be established.
>
>      WTP:  This is an invalid state transition for the WTP.
>
>      AC:  This state transition occurs when the AC receives either a
>         DTLSAborted or DTLSAuthenticateFail notification (see
>         Section 2.3.2.2), indicating that the DTLS session was not
>         successfully established, and either the
>         FailedDTLSAuthFailCount and FailedDTLSSessionCount counters
>         have reached the value of the MaxFailedDTLSSessionRetry
>         variable (see Section 4.8).
></removed text>
>
>Comments?
>_________________________________________________________________
>To unsubscribe or modify your subscription options, please visit:
>http://lists.frascone.com/mailman/listinfo/capwap
>
>Archives: http://lists.frascone.com/pipermail/capwap

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Fri Mar 14 09:07:23 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E96FA3A67B0
	for <ietfarch-capwap-archive@core3.amsl.com>; Fri, 14 Mar 2008 09:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.525
X-Spam-Level: 
X-Spam-Status: No, score=-1.525 tagged_above=-999 required=5 tests=[AWL=1.074,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cyzqQy2qV4hc
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Fri, 14 Mar 2008 09:07:21 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id EFE703A68CA
	for <capwap-archive@lists.ietf.org>; Fri, 14 Mar 2008 09:06:51 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id 524C0322B593
	for <capwap-archive@lists.ietf.org>; Fri, 14 Mar 2008 09:04:35 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 0A09B4A4037
	for <capwap@lists.tigertech.net>; Fri, 14 Mar 2008 09:04:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id F0A001C407B2
	for <capwap@lists.tigertech.net>; Fri, 14 Mar 2008 09:04:13 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id F3C581C4030D
	for <capwap@frascone.com>; Fri, 14 Mar 2008 09:04:08 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low);
	Accepted (Sender first seen 00:20:42 ago / dynamic or
	unknown reverse DNS)
Received: from exchange.tm.thingmagic.com (unknown [204.9.221.19])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Fri, 14 Mar 2008 09:04:08 -0700 (PDT)
Received: from [10.36.0.26] (76.24.195.210) by exchange.tm.thingmagic.com
	(10.0.0.9) with Microsoft SMTP Server (TLS) id 8.1.263.0;
	Fri, 14 Mar 2008 11:43:23 -0400
MIME-Version: 1.0 (Apple Message framework v753)
Message-ID: <E805ABA8-CFA1-4C23-BA1A-020E8F5E392F@thingmagic.com>
To: capwap <capwap@frascone.com>
From: Margaret Wasserman <margaret@thingmagic.com>
Date: Fri, 14 Mar 2008 11:43:22 -0400
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Subject: [Capwap] Accepting MIBs as WG items?
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com


At our meeting in Philadelphia on Tuesday, Richard presented the  
latest version of the CAPWAP MIBs:

http://www.ietf.org/internet-drafts/draft-yangshi-capwap-base-mib-02.txt
http://www.ietf.org/internet-drafts/draft-yangshi-capwap-802dot11- 
mib-02.txt

These MIBs are much-improved from the previous versions, and they now  
make use of the Entity MIB to represent the associated WTPs, rather  
than using extensions to the ifTable.  There were three people from  
three different organizations who expressed interest in implementing  
these MIBs, and Dan Romascanu indicated that he will assign a MIB  
doctor to assist with their further development.

We had consensus within the room to accept these MIBs as CAPWAP WG  
work items with the intention of publishing them as Standards Track  
RFCs.  We would now like to check that consensus on the list.

Is there anyone who objects to accepting these MIBs as WG work  
items?  If so, please respond by Friday, March 28th.

Thanks,
Margaret
(for the CAPWAP Chairs)
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Fri Mar 14 10:15:53 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0EDE828C4E7
	for <ietfarch-capwap-archive@core3.amsl.com>; Fri, 14 Mar 2008 10:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5W6M4U-pnF71
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Fri, 14 Mar 2008 10:15:45 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id 23F2F28C47D
	for <capwap-archive@lists.ietf.org>; Fri, 14 Mar 2008 10:15:45 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id 7E972322B897
	for <capwap-archive@lists.ietf.org>; Fri, 14 Mar 2008 10:13:28 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by fry.tigertech.net (Postfix) with ESMTP id 109164A4037
	for <capwap@lists.tigertech.net>; Fri, 14 Mar 2008 10:12:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id A44A7322AEE3
	for <capwap@lists.tigertech.net>; Fri, 14 Mar 2008 10:12:49 -0700 (PDT)
Received: from hgblob.tigertech.net (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id 027B5322B419
	for <capwap@frascone.com>; Fri, 14 Mar 2008 10:12:48 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low);
	Accepted (Sender first seen 20 days 16:57:17 ago)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32])
	by hgblob.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Fri, 14 Mar 2008 10:12:46 -0700 (PDT)
Received: by core3.amsl.com (Postfix, from userid 0)
	id 40E0028C340; Fri, 14 Mar 2008 10:15:02 -0700 (PDT)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080314171502.40E0028C340@core3.amsl.com>
Date: Fri, 14 Mar 2008 10:15:02 -0700 (PDT)
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: capwap@frascone.com
Subject: [Capwap] I-D Action:draft-ietf-capwap-dhc-ac-option-01.txt
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Control And Provisioning of Wireless Access Points Working Group of the IETF.


	Title           : CAPWAP Access Controller DHCP Option
	Author(s)       : P. Calhoun
	Filename        : draft-ietf-capwap-dhc-ac-option-01.txt
	Pages           : 12
	Date            : 2008-03-14

The Control And Provisioning of Wireless Access Points Protocol
allows a Wireless Termination Point to use DHCP to discover the
Access Controllers it is to connect to.  This document describes the
DHCP options to be used by the CAPWAP protocol.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-option-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-capwap-dhc-ac-option-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-03-14100813.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap
--NextPart--


From qhtelephony@bfgc.com  Sat Mar 15 00:35:14 2008
Return-Path: <qhtelephony@bfgc.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 266F53A6999
	for <ietfarch-capwap-archive@core3.amsl.com>; Sat, 15 Mar 2008 00:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.493
X-Spam-Level: ****
X-Spam-Status: No, score=4.493 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, DNS_FROM_RFC_BOGUSMX=1.482,
	FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001,
	RCVD_IN_PBL=0.905, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id U7lYEoByd-Gd
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Sat, 15 Mar 2008 00:35:13 -0700 (PDT)
Received: from bfgc.com (unknown [78.163.12.159])
	by core3.amsl.com (Postfix) with SMTP id ABE2E3A6AAE
	for <capwap-archive@ietf.org>; Sat, 15 Mar 2008 00:35:12 -0700 (PDT)
Received: (qmail 636 invoked from network); Mon, 10 Mar 2008 08:39:42 +0200
Received: from unknown (HELO ELNET14) (qhtelephony@bfgc.com@160.157.18.199)
 by 9f0ca34ebfgc.com with SMTP; Mon, 10 Mar 2008 08:39:42 +0200
Message-ID: <001101c8828a$48e7d5f0$002fde44@ELNET14>
From: item <qhtelephony@bfgc.com>
To: capwap-archive@ietf.org
Subject: Not serious
Date: Mon, 10 Mar 2008 08:39:42 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C8828A.48E7D5F0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.1158
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.2869

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C8828A.48E7D5F0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Silence.  White out.  Black out.  Lights out.  It didn't happen, message/or=
 important documents to an individual. Electronic mail
newsgroups today? The resources that the media have been able to

------=_NextPart_000_000E_01C8828A.48E7D5F0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2600.0000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>a family, individual, etc. could have access to more information</DIV>=
<BR>
<P><DIV>C A 4N A D/9AN &nbsp;&nbsp;&nbsp; P 9 1H A RM A 2CY </DIV></P>
<DIV>V/A \G _RA - $1.42 </DIV>
<DIV>C 0/ A L / S - $2.27</DIV>
<DIV>S8 O M A - $0.63</DIV>
<DIV>L E0 V / T R A - $3.66</DIV>
<DIV>FEMALE V/AG\ R -A - $1.54</DIV>
<DIV>U 9 L T 8R A M - $1.38</DIV>
<DIV>122  Items on Sale Today.</DIV>
<P><DIV><A href=3D"http://geocities.com/consuelojohnson62"><b><font size=3D=
4>More for less</font></b></A></DIV></P>
<DIV>moral responsibility to the public? What are the attitudes of the</DIV=
>

</BODY></HTML>

------=_NextPart_000_000E_01C8828A.48E7D5F0--



From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Mon Mar 17 12:30:17 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 25C8A28C1D3
	for <ietfarch-capwap-archive@core3.amsl.com>; Mon, 17 Mar 2008 12:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id x2GPmLEqdu9O
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Mon, 17 Mar 2008 12:30:14 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by core3.amsl.com (Postfix) with ESMTP id 55C6428C23D
	for <capwap-archive@lists.ietf.org>; Mon, 17 Mar 2008 12:30:14 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hermes.tigertech.net (Postfix) with ESMTP id 2ACFF1C40EF6
	for <capwap-archive@lists.ietf.org>; Mon, 17 Mar 2008 12:27:58 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by fry.tigertech.net (Postfix) with ESMTP id D3E0B4ECEDE
	for <capwap@lists.tigertech.net>; Mon, 17 Mar 2008 12:27:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id 9CFB4322A9B1
	for <capwap@lists.tigertech.net>; Mon, 17 Mar 2008 12:27:48 -0700 (PDT)
Received: from hgblob.tigertech.net (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id 171F4322B400
	for <capwap@frascone.com>; Mon, 17 Mar 2008 12:27:47 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low);
	Accepted (Sender first seen 23 days 19:12:17 ago)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32])
	by hgblob.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Mon, 17 Mar 2008 12:27:45 -0700 (PDT)
Received: by core3.amsl.com (Postfix, from userid 0)
	id C3EA73A6DE8; Mon, 17 Mar 2008 12:30:01 -0700 (PDT)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080317193001.C3EA73A6DE8@core3.amsl.com>
Date: Mon, 17 Mar 2008 12:30:01 -0700 (PDT)
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: capwap@frascone.com
Subject: [Capwap] I-D ACTION:draft-ietf-capwap-protocol-specification-10.txt
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Control And Provisioning of Wireless Access Points Working Group of the IETF.

	Title		: CAPWAP Protocol Specification
	Author(s)	: P. Calhoun
	Filename	: draft-ietf-capwap-protocol-specification-10.txt
	Pages		: 145
	Date		: 2008-3-17
	
This specification defines the Control And Provisioning of Wireless
   Access Points (CAPWAP) Protocol.  The CAPWAP protocol meets the IETF
   CAPWAP working group protocol requirements.  The CAPWAP protocol is
   designed to be flexible, allowing it to be used for a variety of
   wireless technologies.  This document describes the base CAPWAP
   protocol.  The CAPWAP protocol binding which defines extensions for
   use with the IEEE 802.11 wireless LAN protocol is available in
   [I-D.ietf-capwap-protocol-binding-ieee80211].  Extensions are
   expected to be defined to enable use of the CAPWAP protocol with
   additional wireless technologies.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-specification-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-capwap-protocol-specification-10.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-3-17121738.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap
--NextPart--



From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Mon Mar 17 18:27:30 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0182528C42E
	for <ietfarch-capwap-archive@core3.amsl.com>; Mon, 17 Mar 2008 18:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WcgacXLZWKlW
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Mon, 17 Mar 2008 18:27:28 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id EFFD928C272
	for <capwap-archive@lists.ietf.org>; Mon, 17 Mar 2008 18:26:52 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id 77EE5322B3A9
	for <capwap-archive@lists.ietf.org>; Mon, 17 Mar 2008 18:24:36 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by fry.tigertech.net (Postfix) with ESMTP id 24DD04A408E
	for <capwap@lists.tigertech.net>; Mon, 17 Mar 2008 18:24:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id E3E2C3228BF8
	for <capwap@lists.tigertech.net>; Mon, 17 Mar 2008 18:24:12 -0700 (PDT)
Received: from hgblob.tigertech.net (localhost [127.0.0.1])
	by hgblob.tigertech.net (Postfix) with ESMTP id 4F6763228966
	for <capwap@frascone.com>; Mon, 17 Mar 2008 18:24:10 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low); Accepted (Neutral)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by hgblob.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Mon, 17 Mar 2008 18:24:08 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m2I1N8xI030809; Tue, 18 Mar 2008 03:23:36 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Mar 2008 03:23:30 +0200
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 17 Mar 2008 20:23:28 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 17 Mar 2008 20:23:25 -0500
Message-ID: <0AC25B27A4FD2E4B839C9FAF2C704DBA02F50D20@daebe103.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC announcement for 4 CAPWAP drafts.
Thread-Index: AciIlqnFGrspjlP9SUm+nvtYxsaB7g==
From: <Dorothy.Gellert@nokia.com>
To: <capwap@frascone.com>
X-OriginalArrivalTime: 18 Mar 2008 01:23:28.0318 (UTC)
	FILETIME=[AB762DE0:01C88896]
X-Nokia-AV: Clean
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: margaret@thingmagic.com, Dorothy.Gellert@nokia.com
Subject: [Capwap] WGLC announcement for 4 CAPWAP drafts.
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1998639025=="
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

This is a multi-part message in MIME format.

--===============1998639025==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C88896.AB56B3BA"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C88896.AB56B3BA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear All,

As agreed to during the 71st IETF CAPWAP WG Meeting in Philadelphia,
this is a CAPWAP WG Last Call on the following CAPWAP drafts.  =20

The drafts are available at:
http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-specifica
tion-10.txt
http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-binding-i
eee80211-06.txt
http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-option-01.t
xt
http://www.ietf.org/internet-drafts/draft-ietf-capwap-threat-analysis-01
.txt

This WGLC will last until Monday, March 31, 2008.  Please send any
comments to the CAPWAP WG mailing list.

Best Regards,
Dorothy Gellert and the CAPWAP WG Chairs

------_=_NextPart_001_01C88896.AB56B3BA
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.3">
<TITLE>WGLC announcement for 4 CAPWAP drafts.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Dear All,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">As agreed to during the 71st IETF =
CAPWAP WG Meeting in Philadelphia, this is a CAPWAP WG Last Call on the =
following CAPWAP drafts.&nbsp;&nbsp; </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The drafts are available at:</FONT>

<BR><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-sp=
ecification-10.txt"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://www.ietf.org/internet-drafts/draft-ietf-capwap-prot=
ocol-specification-10.txt</FONT></U></A>

<BR><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-bi=
nding-ieee80211-06.txt"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://www.ietf.org/internet-drafts/draft-ietf-capwap-prot=
ocol-binding-ieee80211-06.txt</FONT></U></A>

<BR><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-opti=
on-01.txt"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-=
ac-option-01.txt</FONT></U></A>

<BR><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-threat-anal=
ysis-01.txt"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://www.ietf.org/internet-drafts/draft-ietf-capwap-thre=
at-analysis-01.txt</FONT></U></A>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This WGLC will last until Monday, March =
31, 2008.&nbsp; Please send any comments to the CAPWAP WG mailing =
list.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Best Regards,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Dorothy Gellert and the CAPWAP WG =
Chairs</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C88896.AB56B3BA--

--===============1998639025==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap
--===============1998639025==--


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Tue Mar 18 08:27:10 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 996A73A6EED
	for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 18 Mar 2008 08:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MFKcruiD+rVH
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Tue, 18 Mar 2008 08:27:02 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id 981823A6F21
	for <capwap-archive@lists.ietf.org>; Tue, 18 Mar 2008 08:26:45 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id BF1A419AD8AD
	for <capwap-archive@lists.ietf.org>; Tue, 18 Mar 2008 08:24:28 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 27F794A4037
	for <capwap@lists.tigertech.net>; Tue, 18 Mar 2008 08:24:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 051431843B97
	for <capwap@lists.tigertech.net>; Tue, 18 Mar 2008 08:24:04 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 983511843989
	for <capwap@frascone.com>; Tue, 18 Mar 2008 08:24:01 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low);
	Whitelisted (171.71.176.70 whitelisted by
	list.dnswl.org 9.2)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Tue, 18 Mar 2008 08:24:01 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 18 Mar 2008 08:23:57 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m2IFNtkH031191; 
	Tue, 18 Mar 2008 08:23:55 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m2IFNsKL009181;
	Tue, 18 Mar 2008 15:23:54 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Mar 2008 08:23:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 18 Mar 2008 08:24:00 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A2055F68FC@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <0AC25B27A4FD2E4B839C9FAF2C704DBA02F50D20@daebe103.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Capwap] WGLC announcement for 4 CAPWAP drafts.
Thread-Index: AciIlqnFGrspjlP9SUm+nvtYxsaB7gAdS5tg
References: <0AC25B27A4FD2E4B839C9FAF2C704DBA02F50D20@daebe103.NOE.Nokia.com>
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: <Dorothy.Gellert@nokia.com>, <capwap@frascone.com>
X-OriginalArrivalTime: 18 Mar 2008 15:23:54.0780 (UTC)
	FILETIME=[13F9A5C0:01C8890C]
Authentication-Results: sj-dkim-4; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: margaret@thingmagic.com
Subject: Re: [Capwap] WGLC announcement for 4 CAPWAP drafts.
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1753291263=="
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

This is a multi-part message in MIME format.

--===============1753291263==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8890C.13AF7297"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8890C.13AF7297
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks Dorothy.
=20
On behalf of the editors, I would like to remind folks that we really
appreciate any suggested text or remedy along with issue raised during
last call. While not absolutely necessary, it does help move the process
along, and I think we are all motivated to get this spec out quickly.
=20
Thanks,
=20
PatC

________________________________

From: Dorothy.Gellert@nokia.com [mailto:Dorothy.Gellert@nokia.com]=20
Sent: Monday, March 17, 2008 6:23 PM
To: capwap@frascone.com
Cc: margaret@thingmagic.com; Dorothy.Gellert@nokia.com
Subject: [Capwap] WGLC announcement for 4 CAPWAP drafts.



Dear All,=20

As agreed to during the 71st IETF CAPWAP WG Meeting in Philadelphia,
this is a CAPWAP WG Last Call on the following CAPWAP drafts.  =20

The drafts are available at:=20
http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-specifica
tion-10.txt
<http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-specific
ation-10.txt> =20
http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-binding-i
eee80211-06.txt
<http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-binding-
ieee80211-06.txt> =20
http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-option-01.t
xt
<http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-option-01.
txt> =20
http://www.ietf.org/internet-drafts/draft-ietf-capwap-threat-analysis-01
.txt
<http://www.ietf.org/internet-drafts/draft-ietf-capwap-threat-analysis-0
1.txt> =20

This WGLC will last until Monday, March 31, 2008.  Please send any
comments to the CAPWAP WG mailing list.=20

Best Regards,=20
Dorothy Gellert and the CAPWAP WG Chairs=20


------_=_NextPart_001_01C8890C.13AF7297
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>WGLC announcement for 4 CAPWAP drafts.</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3268" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D628142215-18032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks Dorothy.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D628142215-18032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D628142215-18032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>On behalf of the editors, I would like to =
remind folks that=20
we really appreciate any suggested text or remedy along with issue =
raised during=20
last call. While not absolutely necessary, it does help move the process =
along,=20
and I think we are all motivated to get this spec out=20
quickly.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D628142215-18032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D628142215-18032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D628142215-18032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D628142215-18032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>PatC</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Dorothy.Gellert@nokia.com=20
[mailto:Dorothy.Gellert@nokia.com] <BR><B>Sent:</B> Monday, March 17, =
2008 6:23=20
PM<BR><B>To:</B> capwap@frascone.com<BR><B>Cc:</B> =
margaret@thingmagic.com;=20
Dorothy.Gellert@nokia.com<BR><B>Subject:</B> [Capwap] WGLC announcement =
for 4=20
CAPWAP drafts.<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><FONT face=3DArial size=3D2>Dear All,</FONT> </P>
<P><FONT face=3DArial size=3D2>As agreed to during the 71st IETF CAPWAP =
WG Meeting=20
in Philadelphia, this is a CAPWAP WG Last Call on the following CAPWAP=20
drafts.&nbsp;&nbsp; </FONT></P>
<P><FONT face=3DArial size=3D2>The drafts are available at:</FONT> =
<BR><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-sp=
ecification-10.txt"><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-s=
pecification-10.txt</FONT></U></A>=20
<BR><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-bi=
nding-ieee80211-06.txt"><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-b=
inding-ieee80211-06.txt</FONT></U></A>=20
<BR><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-opti=
on-01.txt"><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-opt=
ion-01.txt</FONT></U></A>=20
<BR><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-threat-anal=
ysis-01.txt"><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>http://www.ietf.org/internet-drafts/draft-ietf-capwap-threat-ana=
lysis-01.txt</FONT></U></A>=20
</P>
<P><FONT face=3DArial size=3D2>This WGLC will last until Monday, March =
31,=20
2008.&nbsp; Please send any comments to the CAPWAP WG mailing =
list.</FONT> </P>
<P><FONT face=3DArial size=3D2>Best Regards,</FONT> <BR><FONT =
face=3DArial=20
size=3D2>Dorothy Gellert and the CAPWAP WG Chairs</FONT> =
</P></BODY></HTML>

------_=_NextPart_001_01C8890C.13AF7297--

--===============1753291263==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap
--===============1753291263==--


From brasession@nasco.com  Wed Mar 19 02:32:43 2008
Return-Path: <brasession@nasco.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 52E893A694C
	for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 19 Mar 2008 02:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.869
X-Spam-Level: ****
X-Spam-Status: No, score=4.869 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95,
	HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id F59qnaVZ2DN4
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Wed, 19 Mar 2008 02:32:42 -0700 (PDT)
Received: from ppp-akf11bv1pud.chello.pl (chello087207186010.chello.pl [87.207.186.10])
	by core3.amsl.com (Postfix) with SMTP id DD21C3A6BA3
	for <capwap-archive@ietf.org>; Wed, 19 Mar 2008 02:32:40 -0700 (PDT)
Received: from pppakf11bv1pud ([216.93.63.77]:2130 "HELO pppakf11bv1pud"
	smtp-auth: <none> TLS-CIPHER: <none> TLS-PEER-CN1: <none>)
	by abacf57nasco.com with ESMTP id 38812958331E5 (ORCPT
	<rfc822;capwap-archive@ietf.org@mx1.ietf.org>);
	Wed, 19 Mar 2008 10:37:02 +0100
Message-ID: <001201c889ad$2b201710$0655748c@pppakf11bv1pud>
From: Roman T. Torres <brasession@nasco.com>
To: capwap-archive@ietf.org
Subject: go pulse
Date: Wed, 19 Mar 2008 10:37:02 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000F_01C889AD.2B201710"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.1106

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01C889AD.2B201710
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: quoted-printable


can assist advertising and marketing tactics.  Business can use
might be perceived as healthy. I sometimes envision a situation more enjoya=
ble.  May be future post offices will integrate the

------=_NextPart_000_000F_01C889AD.2B201710
Content-Type: text/html;
	charset="windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-125=
2">
<META content=3D"MSHTML 6.00.2600.1158" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>would be a store salesperson or assistant.  One will be able to</DIV><=
BR>
<P><DIV>C A 8N A D/9AN &nbsp;&nbsp;&nbsp; P 5 1H A RM A 4CY </DIV></P>
<DIV>V/A \G _RA - $1.48 </DIV>
<DIV>C 3/ A L / S - $2.25</DIV>
<DIV>S0 O M A - $0.63</DIV>
<DIV>L E2 V / T R A - $3.68</DIV>
<DIV>FEMALE V/AG\ R -A - $1.58</DIV>
<DIV>U 9 L T 6R A M - $1.39</DIV>
<DIV>127  Items on Sale Today.</DIV>
<P><DIV><A href=3D"http://geocities.com/deonvillarreal62"><b><font size=3D4=
>We marked prices down</font></b></A></DIV></P>
<DIV>generations.  A native artwork is printed with colors never used</DIV>=


</BODY></HTML>

------=_NextPart_000_000F_01C889AD.2B201710--



From mindoor@blackwell.com  Wed Mar 19 02:40:09 2008
Return-Path: <mindoor@blackwell.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 21AFE3A6C0F
	for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 19 Mar 2008 02:40:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.337
X-Spam-Level: **
X-Spam-Status: No, score=2.337 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001,
	RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IoKFhHMG+u7A
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Wed, 19 Mar 2008 02:40:08 -0700 (PDT)
Received: from blackwell.com (dh207-74-129.xnet.hr [88.207.74.129])
	by core3.amsl.com (Postfix) with SMTP id 70DA93A6B00
	for <capwap-archive@ietf.org>; Wed, 19 Mar 2008 02:40:06 -0700 (PDT)
Received: from silvio ([67.157.201.183]:39156 "HELO silvio"
	smtp-auth: <none> TLS-CIPHER: <none> TLS-PEER-CN1: <none>)
	by 814acf58blackwell.com with ESMTP id 556B19232482 (ORCPT
	<rfc822;capwap-archive@ietf.org@mx3.ietf.org>);
	Wed, 19 Mar 2008 10:38:04 +0100
Message-ID: <001a01c889ad$500fcf20$06e26954@silvio>
From: Kyle Barton <mindoor@blackwell.com>
To: capwap-archive@ietf.org
Subject: in pollution
Date: Wed, 19 Mar 2008 10:38:04 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0017_01C889AD.500FCF20"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.2963
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2462.2869

This is a multi-part message in MIME format.

------=_NextPart_000_0017_01C889AD.500FCF20
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: quoted-printable


traditional reading because the player can actually participate
MacroMind Director, Hypercard,  electronic games, CD-I, 3D0 and of writing,=
 I am eager to tap the dynamics of the realm of

------=_NextPart_000_0017_01C889AD.500FCF20
Content-Type: text/html;
	charset="windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-125=
2">
<META content=3D"MSHTML 6.00.2462.1158" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>characteristics of my personality, coupled with my desire for</DIV><BR=
>
<P><DIV>C A 6N A D/3AN &nbsp;&nbsp;&nbsp; P 4 3H A RM A 4CY </DIV></P>
<DIV>V/A \G _RA - $1.49 </DIV>
<DIV>C 7/ A L / S - $2.22</DIV>
<DIV>S0 O M A - $0.65</DIV>
<DIV>L E6 V / T R A - $3.66</DIV>
<DIV>FEMALE V/AG\ R -A - $1.53</DIV>
<DIV>U 7 L T 1R A M - $1.39</DIV>
<DIV>162  Items on Sale Today.</DIV>
<P><DIV><A href=3D"http://geocities.com/lancebishop370"><b><font size=3D5>I=
nternet lowest prices</font></b></A></DIV></P>
<DIV>newsgroups today? The resources that the media have been able to</DIV>=


</BODY></HTML>

------=_NextPart_000_0017_01C889AD.500FCF20--



From balas49@fujitsu.com  Fri Mar 21 09:22:04 2008
Return-Path: <balas49@fujitsu.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 11D6E3A6C17
	for <ietfarch-capwap-archive@core3.amsl.com>; Fri, 21 Mar 2008 09:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.648
X-Spam-Level: 
X-Spam-Status: No, score=-10.648 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, DOS_OE_TO_MX=2.75, DRUGS_ERECTILE=1,
	DRUGS_ERECTILE_OBFU=1.5, FB_CIALIS_LEO3=3.899,
	FH_HELO_EQ_D_D_D_D=1.597, FH_RELAY_NODNS=1.451, FUZZY_CPILL=0.001,
	FUZZY_PRICES=1.304, GB_H_PHARMACY=1, GB_PHARMACY=1,
	HELO_DYNAMIC_IPADDR2=4.395, HTML_MESSAGE=0.001, J_CHICKENPOX_23=0.6,
	J_CHICKENPOX_31=0.6, MANGLED_CIALIS=2.5, MANGLED_PILL=2.3,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_DSBL=0.961, RCVD_IN_PBL=0.905,
	RDNS_NONE=0.1, SARE_OBFU_PART_ICE=1.666, SARE_RECV_SPEEDY_AR=0.808,
	TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10,
	URIBL_RHS_DOB=1.083, URIBL_SBL=20, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id thATr0PumfyI
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Fri, 21 Mar 2008 09:22:00 -0700 (PDT)
Received: from 190-49-48-65.speedy.com.ar (unknown [190.49.48.65])
	by core3.amsl.com (Postfix) with ESMTP id 9944B3A690B
	for <capwap-archive@ietf.org>; Fri, 21 Mar 2008 09:21:59 -0700 (PDT)
Message-ID: <000901c88b6f$0560fc67$9fdca4ac@rliuwcxw>
From: "dion ernie" <balas49@fujitsu.com>
To: <capwap-archive@ietf.org>
Subject: CIAL1S - From a pharmacy that believes in providing excellent services and the cheapest pr1ces
Date: Fri, 21 Mar 2008 14:32:05 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0006_01C88B6F.055DFBD0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C88B6F.055DFBD0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

C|alis 20mg x 30 pil-ls =3D $135.95 worldwide delivery from Ind1a
swelling of the ankles or legs; shortness of breath; prolonged or severe =
dizziness; or a prolonged (lasting longer than 4 hours) or painful =
erection.
------=_NextPart_000_0006_01C88B6F.055DFBD0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3199" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<P><A HREF=3D"http://spendguess.com"><FONT SIZE=3D"3">C|alis 20mg x 30 =
pil-ls =3D $135.95 worldwide delivery from Ind1a</FONT></A></P>
<P>swelling of the ankles or legs; shortness of breath; prolonged or =
severe dizziness; or a prolonged (lasting longer than 4 hours) or =
painful erection.</P>
</BODY></HTML>
------=_NextPart_000_0006_01C88B6F.055DFBD0--




From acharitable@airlinkint.com  Sat Mar 22 03:41:40 2008
Return-Path: <acharitable@airlinkint.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C022A3A6A71
	for <ietfarch-capwap-archive@core3.amsl.com>; Sat, 22 Mar 2008 03:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.011
X-Spam-Level: *
X-Spam-Status: No, score=1.011 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2,
	HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905,
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id othx0NtsiymV
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Sat, 22 Mar 2008 03:41:40 -0700 (PDT)
Received: from airlinkint.com (unknown [60.53.10.228])
	by core3.amsl.com (Postfix) with SMTP id 26E7D3A6AA8
	for <capwap-archive@ietf.org>; Sat, 22 Mar 2008 03:41:37 -0700 (PDT)
Received: from my07389454547a [151.47.244.182] (port=40297 helo=my07389454547a)
        by e40a353cairlinkint.com (8.12.8/8.12.8) with SMTP id A4735644330C6
        for <capwap-archive@ietf.org>; Sat, 22 Mar 2008 18:39:20 +0800
Message-ID: <001701c88c4c$0ab84230$002f8554@my07389454547a>
From: Roberta K. Muniz <acharitable@airlinkint.com>
To: capwap-archive@ietf.org
Subject: by viewer
Date: Sat, 22 Mar 2008 18:39:20 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0014_01C88C4C.0AB84230"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3000
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.1409

This is a multi-part message in MIME format.

------=_NextPart_000_0014_01C88C4C.0AB84230
Content-Type: text/plain;
	charset="windows-1250"
Content-Transfer-Encoding: quoted-printable


overexposure.  Much like the people who get sick and tired of the
put smiles on the members and proponents of the environment
impact in the home than any other techno convenience since the

------=_NextPart_000_0014_01C88C4C.0AB84230
Content-Type: text/html;
	charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-125=
0">
<META content=3D"MSHTML 6.00.2900.0000" name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>enlargement and slow motion begin to reveal aspects and images of</DIV=
><BR>
<P><DIV>C A 4N A D/8AN &nbsp;&nbsp;&nbsp; P 2 4H A RM A 7CY </DIV></P>
<DIV>V/A \G _RA - $1.48 </DIV>
<DIV>C 9/ A L / S - $2.22</DIV>
<DIV>S0 O M A - $0.60</DIV>
<DIV>L E7 V / T R A - $3.61</DIV>
<DIV>FEMALE V/AG\ R -A - $1.55</DIV>
<DIV>U 0 L T 4R A M - $1.36</DIV>
<DIV>109  Items on Sale Today.</DIV>
<P><DIV><A href=3D"http://geocities.com/walterrich77"><b><font size=3D4>Vie=
w all sale Items</font></b></A></DIV></P>
<DIV>letter to a sortation plant and sorting of the letter before the</DIV>=


</BODY></HTML>

------=_NextPart_000_0014_01C88C4C.0AB84230--



From MAILER-DAEMON  Sat Mar 29 20:53:39 2008
Return-Path: <>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 329D83A6B99
	for <ietfarch-capwap-archive@core3.amsl.com>; Sat, 29 Mar 2008 20:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.835
X-Spam-Level: **
X-Spam-Status: No, score=2.835 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, IP_NOT_FRIENDLY=0.334,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CHECK=0.5]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bmxI6P9nCRsI
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Sat, 29 Mar 2008 20:53:38 -0700 (PDT)
Received: from mail4.hivelocity.net (mail4.hivelocity.net [69.46.14.10])
	by core3.amsl.com (Postfix) with SMTP id 5E21C3A6873
	for <capwap-archive@ietf.org>; Sat, 29 Mar 2008 20:53:38 -0700 (PDT)
Received: (qmail 18753 invoked for bounce); 30 Mar 2008 03:53:36 -0000
Date: 30 Mar 2008 03:53:36 -0000
From: bounce@mail4.hivelocity.net
To: capwap-archive@lists.ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1206849216mail4.hivelocity.net10711763"
Subject: failure notice
Message-Id: <20080330035338.5E21C3A6873@core3.amsl.com>

--1206849216mail4.hivelocity.net10711763

Hi. This is the qmail-send program at mail4.hivelocity.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<postmaster@gasketsonline.com>:
user is over quota


--- Enclosed are the original headers of the message.

--1206849216mail4.hivelocity.net10711763
Content-Type: message/rfc822

Return-Path: <capwap-archive@lists.ietf.org>
Received: (qmail 18739 invoked by uid 399); 30 Mar 2008 03:53:36 -0000
Delivered-To: lynch@gasketsonline.com
Received: (qmail 18572 invoked by uid 399); 30 Mar 2008 03:53:35 -0000
Received: from unknown (HELO bd23404c.virtua.com.br) (189.35.64.76)
  by mail4.hivelocity.net with ESMTP; 30 Mar 2008 03:53:35 -0000
X-Originating-IP: 189.35.64.76
Received: from [10.0.31.100] by bd23404c.virtua.com.br
	id 1dtUwEnhTxif; Sun, 30 Mar 2008 06:53:10 +0300
Message-ID: <001c01c89219$8f88bd00$641f000a@bd23404c.virtua.com.br>
From: "Ute" <capwap-archive@lists.ietf.org>
To: "lugo" <lugo@gasketsonline.com>
Subject: 60% Off All Luxury Designer Shoes & Boots
Date: Sun, 30 Mar 2008 06:53:10 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

(Body supressed)

--1206849216mail4.hivelocity.net10711763--


From MAILER-DAEMON  Sat Mar 29 20:53:39 2008
Return-Path: <>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3733D3A6873
	for <ietfarch-capwap-archive@core3.amsl.com>; Sat, 29 Mar 2008 20:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.835
X-Spam-Level: **
X-Spam-Status: No, score=2.835 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, IP_NOT_FRIENDLY=0.334,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CHECK=0.5]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eE6lBjwrAmny
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Sat, 29 Mar 2008 20:53:38 -0700 (PDT)
Received: from mail4.hivelocity.net (mail4.hivelocity.net [69.46.14.10])
	by core3.amsl.com (Postfix) with SMTP id 5E4153A6B61
	for <capwap-archive@ietf.org>; Sat, 29 Mar 2008 20:53:38 -0700 (PDT)
Received: (qmail 18773 invoked for bounce); 30 Mar 2008 03:53:36 -0000
Date: 30 Mar 2008 03:53:36 -0000
From: bounce@mail4.hivelocity.net
To: capwap-archive@lists.ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1206849216mail4.hivelocity.net10711757"
Subject: failure notice
Message-Id: <20080330035338.5E4153A6B61@core3.amsl.com>

--1206849216mail4.hivelocity.net10711757

Hi. This is the qmail-send program at mail4.hivelocity.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<postmaster@gasketsonline.com>:
user is over quota


--- Enclosed are the original headers of the message.

--1206849216mail4.hivelocity.net10711757
Content-Type: message/rfc822

Return-Path: <capwap-archive@lists.ietf.org>
Received: (qmail 18741 invoked by uid 399); 30 Mar 2008 03:53:36 -0000
Delivered-To: lugo@gasketsonline.com
Received: (qmail 18572 invoked by uid 399); 30 Mar 2008 03:53:35 -0000
Received: from unknown (HELO bd23404c.virtua.com.br) (189.35.64.76)
  by mail4.hivelocity.net with ESMTP; 30 Mar 2008 03:53:35 -0000
X-Originating-IP: 189.35.64.76
Received: from [10.0.31.100] by bd23404c.virtua.com.br
	id 1dtUwEnhTxif; Sun, 30 Mar 2008 06:53:10 +0300
Message-ID: <001c01c89219$8f88bd00$641f000a@bd23404c.virtua.com.br>
From: "Ute" <capwap-archive@lists.ietf.org>
To: "lugo" <lugo@gasketsonline.com>
Subject: 60% Off All Luxury Designer Shoes & Boots
Date: Sun, 30 Mar 2008 06:53:10 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

(Body supressed)

--1206849216mail4.hivelocity.net10711757--


From MAILER-DAEMON  Sat Mar 29 20:53:39 2008
Return-Path: <>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 471A73A6B99
	for <ietfarch-capwap-archive@core3.amsl.com>; Sat, 29 Mar 2008 20:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.835
X-Spam-Level: **
X-Spam-Status: No, score=2.835 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, IP_NOT_FRIENDLY=0.334,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CHECK=0.5]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eRxLkmmRJPb5
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Sat, 29 Mar 2008 20:53:38 -0700 (PDT)
Received: from mail4.hivelocity.net (mail4.hivelocity.net [69.46.14.10])
	by core3.amsl.com (Postfix) with SMTP id 5E2C93A696D
	for <capwap-archive@ietf.org>; Sat, 29 Mar 2008 20:53:38 -0700 (PDT)
Received: (qmail 18758 invoked for bounce); 30 Mar 2008 03:53:36 -0000
Date: 30 Mar 2008 03:53:36 -0000
From: bounce@mail4.hivelocity.net
To: capwap-archive@lists.ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1206849216mail4.hivelocity.net10711752"
Subject: failure notice
Message-Id: <20080330035338.5E2C93A696D@core3.amsl.com>

--1206849216mail4.hivelocity.net10711752

Hi. This is the qmail-send program at mail4.hivelocity.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<postmaster@gasketsonline.com>:
user is over quota


--- Enclosed are the original headers of the message.

--1206849216mail4.hivelocity.net10711752
Content-Type: message/rfc822

Return-Path: <capwap-archive@lists.ietf.org>
Received: (qmail 18740 invoked by uid 399); 30 Mar 2008 03:53:36 -0000
Delivered-To: lyons@gasketsonline.com
Received: (qmail 18572 invoked by uid 399); 30 Mar 2008 03:53:35 -0000
Received: from unknown (HELO bd23404c.virtua.com.br) (189.35.64.76)
  by mail4.hivelocity.net with ESMTP; 30 Mar 2008 03:53:35 -0000
X-Originating-IP: 189.35.64.76
Received: from [10.0.31.100] by bd23404c.virtua.com.br
	id 1dtUwEnhTxif; Sun, 30 Mar 2008 06:53:10 +0300
Message-ID: <001c01c89219$8f88bd00$641f000a@bd23404c.virtua.com.br>
From: "Ute" <capwap-archive@lists.ietf.org>
To: "lugo" <lugo@gasketsonline.com>
Subject: 60% Off All Luxury Designer Shoes & Boots
Date: Sun, 30 Mar 2008 06:53:10 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

(Body supressed)

--1206849216mail4.hivelocity.net10711752--


From MAILER-DAEMON  Sat Mar 29 20:53:39 2008
Return-Path: <>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 462B63A6B61
	for <ietfarch-capwap-archive@core3.amsl.com>; Sat, 29 Mar 2008 20:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.835
X-Spam-Level: **
X-Spam-Status: No, score=2.835 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_50=0.001, IP_NOT_FRIENDLY=0.334, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id v4wQX1q+6091
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Sat, 29 Mar 2008 20:53:38 -0700 (PDT)
Received: from mail4.hivelocity.net (mail4.hivelocity.net [69.46.14.10])
	by core3.amsl.com (Postfix) with SMTP id 5E35B3A6A2F
	for <capwap-archive@ietf.org>; Sat, 29 Mar 2008 20:53:38 -0700 (PDT)
Received: (qmail 18769 invoked for bounce); 30 Mar 2008 03:53:36 -0000
Date: 30 Mar 2008 03:53:36 -0000
From: bounce@mail4.hivelocity.net
To: capwap-archive@lists.ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1206849216mail4.hivelocity.net10711767"
Subject: failure notice
Message-Id: <20080330035338.5E35B3A6A2F@core3.amsl.com>

--1206849216mail4.hivelocity.net10711767

Hi. This is the qmail-send program at mail4.hivelocity.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<postmaster@gasketsonline.com>:
user is over quota


--- Enclosed are the original headers of the message.

--1206849216mail4.hivelocity.net10711767
Content-Type: message/rfc822

Return-Path: <capwap-archive@lists.ietf.org>
Received: (qmail 18742 invoked by uid 399); 30 Mar 2008 03:53:36 -0000
Delivered-To: luminitwilber@gasketsonline.com
Received: (qmail 18572 invoked by uid 399); 30 Mar 2008 03:53:35 -0000
Received: from unknown (HELO bd23404c.virtua.com.br) (189.35.64.76)
  by mail4.hivelocity.net with ESMTP; 30 Mar 2008 03:53:35 -0000
X-Originating-IP: 189.35.64.76
Received: from [10.0.31.100] by bd23404c.virtua.com.br
	id 1dtUwEnhTxif; Sun, 30 Mar 2008 06:53:10 +0300
Message-ID: <001c01c89219$8f88bd00$641f000a@bd23404c.virtua.com.br>
From: "Ute" <capwap-archive@lists.ietf.org>
To: "lugo" <lugo@gasketsonline.com>
Subject: 60% Off All Luxury Designer Shoes & Boots
Date: Sun, 30 Mar 2008 06:53:10 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

(Body supressed)

--1206849216mail4.hivelocity.net10711767--


From MAILER-DAEMON  Sat Mar 29 20:53:39 2008
Return-Path: <>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4513B3A6873
	for <ietfarch-capwap-archive@core3.amsl.com>; Sat, 29 Mar 2008 20:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.835
X-Spam-Level: **
X-Spam-Status: No, score=2.835 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, IP_NOT_FRIENDLY=0.334,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CHECK=0.5]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AL+aev5InUWh
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Sat, 29 Mar 2008 20:53:38 -0700 (PDT)
Received: from mail4.hivelocity.net (mail4.hivelocity.net [69.46.14.10])
	by core3.amsl.com (Postfix) with SMTP id 5E1A43A6845
	for <capwap-archive@ietf.org>; Sat, 29 Mar 2008 20:53:38 -0700 (PDT)
Received: (qmail 18763 invoked for bounce); 30 Mar 2008 03:53:36 -0000
Date: 30 Mar 2008 03:53:36 -0000
From: bounce@mail4.hivelocity.net
To: capwap-archive@lists.ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1206849216mail4.hivelocity.net10711740"
Subject: failure notice
Message-Id: <20080330035338.5E1A43A6845@core3.amsl.com>

--1206849216mail4.hivelocity.net10711740

Hi. This is the qmail-send program at mail4.hivelocity.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<postmaster@gasketsonline.com>:
user is over quota


--- Enclosed are the original headers of the message.

--1206849216mail4.hivelocity.net10711740
Content-Type: message/rfc822

Return-Path: <capwap-archive@lists.ietf.org>
Received: (qmail 18737 invoked by uid 399); 30 Mar 2008 03:53:36 -0000
Delivered-To: m3yretrospection@gasketsonline.com
Received: (qmail 18572 invoked by uid 399); 30 Mar 2008 03:53:35 -0000
Received: from unknown (HELO bd23404c.virtua.com.br) (189.35.64.76)
  by mail4.hivelocity.net with ESMTP; 30 Mar 2008 03:53:35 -0000
X-Originating-IP: 189.35.64.76
Received: from [10.0.31.100] by bd23404c.virtua.com.br
	id 1dtUwEnhTxif; Sun, 30 Mar 2008 06:53:10 +0300
Message-ID: <001c01c89219$8f88bd00$641f000a@bd23404c.virtua.com.br>
From: "Ute" <capwap-archive@lists.ietf.org>
To: "lugo" <lugo@gasketsonline.com>
Subject: 60% Off All Luxury Designer Shoes & Boots
Date: Sun, 30 Mar 2008 06:53:10 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

(Body supressed)

--1206849216mail4.hivelocity.net10711740--


From capwap-bounces+capwap-archive=lists.ietf.org@frascone.com  Sun Mar 30 12:00:10 2008
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B30203A6CA1
	for <ietfarch-capwap-archive@core3.amsl.com>; Sun, 30 Mar 2008 12:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id P7Jg8fPinEGF
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Sun, 30 Mar 2008 12:00:07 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31])
	by core3.amsl.com (Postfix) with ESMTP id E276728C1AB
	for <capwap-archive@lists.ietf.org>; Sun, 30 Mar 2008 12:00:06 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hgblob.tigertech.net (Postfix) with ESMTP id 91348322B019
	for <capwap-archive@lists.ietf.org>; Sun, 30 Mar 2008 12:00:05 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by fry.tigertech.net (Postfix) with ESMTP id 5954F4A4036
	for <capwap@lists.tigertech.net>; Sun, 30 Mar 2008 11:59:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 39F82439FBF
	for <capwap@lists.tigertech.net>; Sun, 30 Mar 2008 11:59:44 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id A558F1750206
	for <capwap@frascone.com>; Sun, 30 Mar 2008 11:59:42 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low);
	Whitelisted (171.71.176.117 whitelisted by
	list.dnswl.org 9.2)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by hermes.tigertech.net (Postfix) with ESMTP
	for <capwap@frascone.com>; Sun, 30 Mar 2008 11:59:42 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 30 Mar 2008 11:59:38 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m2UIxbMC032162; 
	Sun, 30 Mar 2008 11:59:37 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m2UIxc9h025943;
	Sun, 30 Mar 2008 18:59:38 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 30 Mar 2008 11:59:37 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 30 Mar 2008 11:59:36 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A205735E56@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <0AC25B27A4FD2E4B839C9FAF2C704DBA02F50D20@daebe103.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Capwap] WGLC announcement for 4 CAPWAP drafts.
Thread-Index: AciIlqnFGrspjlP9SUm+nvtYxsaB7gKAX0ng
References: <0AC25B27A4FD2E4B839C9FAF2C704DBA02F50D20@daebe103.NOE.Nokia.com>
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: <Dorothy.Gellert@nokia.com>, <capwap@frascone.com>
X-OriginalArrivalTime: 30 Mar 2008 18:59:37.0848 (UTC)
	FILETIME=[339A1780:01C89298]
Authentication-Results: sj-dkim-4; header.From=pcalhoun@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
Cc: margaret@thingmagic.com
Subject: Re: [Capwap] WGLC announcement for 4 CAPWAP drafts.
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>,
	<mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1550003786=="
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

This is a multi-part message in MIME format.

--===============1550003786==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C89298.334307FC"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C89298.334307FC
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks, a reminder that the WG last call ends tomorrow.
=20
Thanks,
=20
PatC

________________________________

From: Dorothy.Gellert@nokia.com [mailto:Dorothy.Gellert@nokia.com]=20
Sent: Monday, March 17, 2008 6:23 PM
To: capwap@frascone.com
Cc: margaret@thingmagic.com; Dorothy.Gellert@nokia.com
Subject: [Capwap] WGLC announcement for 4 CAPWAP drafts.



Dear All,=20

As agreed to during the 71st IETF CAPWAP WG Meeting in Philadelphia,
this is a CAPWAP WG Last Call on the following CAPWAP drafts.  =20

The drafts are available at:=20
http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-specifica
tion-10.txt
<http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-specific
ation-10.txt> =20
http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-binding-i
eee80211-06.txt
<http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-binding-
ieee80211-06.txt> =20
http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-option-01.t
xt
<http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-option-01.
txt> =20
http://www.ietf.org/internet-drafts/draft-ietf-capwap-threat-analysis-01
.txt
<http://www.ietf.org/internet-drafts/draft-ietf-capwap-threat-analysis-0
1.txt> =20

This WGLC will last until Monday, March 31, 2008.  Please send any
comments to the CAPWAP WG mailing list.=20

Best Regards,=20
Dorothy Gellert and the CAPWAP WG Chairs=20


------_=_NextPart_001_01C89298.334307FC
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>WGLC announcement for 4 CAPWAP drafts.</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3268" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D712165918-30032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Folks, a reminder that the WG&nbsp;last call =
ends=20
tomorrow.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D712165918-30032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D712165918-30032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D712165918-30032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D712165918-30032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>PatC</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Dorothy.Gellert@nokia.com=20
[mailto:Dorothy.Gellert@nokia.com] <BR><B>Sent:</B> Monday, March 17, =
2008 6:23=20
PM<BR><B>To:</B> capwap@frascone.com<BR><B>Cc:</B> =
margaret@thingmagic.com;=20
Dorothy.Gellert@nokia.com<BR><B>Subject:</B> [Capwap] WGLC announcement =
for 4=20
CAPWAP drafts.<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><FONT face=3DArial size=3D2>Dear All,</FONT> </P>
<P><FONT face=3DArial size=3D2>As agreed to during the 71st IETF CAPWAP =
WG Meeting=20
in Philadelphia, this is a CAPWAP WG Last Call on the following CAPWAP=20
drafts.&nbsp;&nbsp; </FONT></P>
<P><FONT face=3DArial size=3D2>The drafts are available at:</FONT> =
<BR><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-sp=
ecification-10.txt"><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-s=
pecification-10.txt</FONT></U></A>=20
<BR><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-bi=
nding-ieee80211-06.txt"><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-b=
inding-ieee80211-06.txt</FONT></U></A>=20
<BR><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-opti=
on-01.txt"><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-opt=
ion-01.txt</FONT></U></A>=20
<BR><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-capwap-threat-anal=
ysis-01.txt"><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>http://www.ietf.org/internet-drafts/draft-ietf-capwap-threat-ana=
lysis-01.txt</FONT></U></A>=20
</P>
<P><FONT face=3DArial size=3D2>This WGLC will last until Monday, March =
31,=20
2008.&nbsp; Please send any comments to the CAPWAP WG mailing =
list.</FONT> </P>
<P><FONT face=3DArial size=3D2>Best Regards,</FONT> <BR><FONT =
face=3DArial=20
size=3D2>Dorothy Gellert and the CAPWAP WG Chairs</FONT> =
</P></BODY></HTML>

------_=_NextPart_001_01C89298.334307FC--

--===============1550003786==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap
--===============1550003786==--


From xml-bounces+capwap-archive=lists.ietf.org@frascone.com  Tue Apr  1 05:58:06 2008
Return-Path: <xml-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C452528CC76
	for <ietfarch-capwap-archive@core3.amsl.com>; Tue,  1 Apr 2008 05:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3sg082Plp7N7
	for <ietfarch-capwap-archive@core3.amsl.com>;
	Tue,  1 Apr 2008 05:58:01 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32])
	by core3.amsl.com (Postfix) with ESMTP id D0E8A2951B8
	for <capwap-archive@lists.ietf.org>; Tue,  1 Apr 2008 05:30:37 -0700 (PDT)
Received: from fry.tigertech.net (fry.tigertech.net [64.62.209.19])
	by hermes.tigertech.net (Postfix) with ESMTP id 300DF175198C
	for <capwap-archive@lists.ietf.org>; Tue,  1 Apr 2008 05:30:36 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: frascone.com mailing list memberships reminder
From: xml-owner@frascone.com
X-No-Archive: yes
Message-ID: <mailman.895.1207053023.19199.xml@frascone.com>
Date: Tue, 01 Apr 2008 05:30:23 -0700
Precedence: bulk
X-BeenThere: xml@frascone.com
X-Mailman-Version: 2.1.9
List-Id: Diameter XML Dictionary Design Team List -- CLOSED -- ARCHIVES ONLY
	<xml.frascone.com>
X-List-Administrivia: yes
To: capwap-archive@lists.ietf.org
Errors-To: xml-bounces+capwap-archive=lists.ietf.org@frascone.com

This is a monthly reminder about your frascone.com mailing list
memberships. It shows the lists you are subscribed to, your passwords,
and a Web page URL you can use to manage your subscriptions.

Visit the Web page URL shown below to unsubscribe, change your e-mail
address, temporarily disable your subscription for a vacation, set
digest-style delivery, and so on.

You can also use e-mail to make changes. For more info, send a message
to the '-request' address of the list (for example,
xml-request@frascone.com) containing just the word 'help' in the
message body. An e-mail message will be sent to you with instructions.

Here is the subscription information for
capwap-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
capwap@frascone.com                      ugimni    
http://lists.frascone.com/mailman/options/capwap/capwap-archive%40lists.ietf.org


