Hello Warren
I am happy to review.
Also, being the lead author for the other draft mentioned here
(draft-ietf-opsawg-capwap-alt-tunnel)
I wanted to highlight that the draft needs to be progressed. We would like
to progress that draft. Specifically, can I request a WG last call.
Thanks
Rajesh
On
ink this depends on the
>specific scenarios.
The AC provided information (AR, etc) is on a WLAN basis.
>
>Thanks,
>Jianjie
>
>
>> -邮件原件-
>> 发件人: Rajesh Pazhyannur (rpazhyan) [mailto:rpazh...@cisco.com]
>> 发送时间: 2015年4月14日 4:45
>> 收件人: Youjianjie;
Hello…
Can the authors explain why the problem statement for this cannot be
addressed within the framework of the
"Alternate Tunnel Encapsulation for Data Frames in CAPWAP”. Specifically,
what are the gaps ?
The alternate tunnel draft does allow for different AR to be specified for
different WLAN
gt;> So, my suggestion is to allow draft-ietf-opsawg-capwap-alt-tunnel to
>>>>also support GRE/IP-in-IP modes and have draft-xue focus exclusively
>>>>on L2TP extensions and move it on a fast track. IMO, this is a
>>>>reasonably split. I'm also happy to provi
Hello
I realized there was a typographical error in my response below.
Please see corrections.
Regards
Rajesh
From: Rajesh Pazhyannur mailto:rpazh...@cisco.com>>
Date: Thursday, November 20, 2014 at 12:30 AM
To: "Benoit Claise (bclaise)" mailto:bcla...@cisco.com>>,
"draft-xue-opsawg-capwap-alt-
Hi Benoit
But now I wonder: why do we have two different drafts, as opposed to a single
one?
This is a good question.
Yes, you are correct that draft-ietf-opsawg-capwap-alt-tunnel does not provide
a complete solution and needs something like
draft-ietf-opsawg-capwap-alt-tunnel to complete the
Hello Benoit
Thanks for reviewing the draft.
Overall the comments make sense and I will incorporate the suggested changes.
Some follow up remarks are embedded.
regards
Rajesh
From: Benoit Claise (bclaise)
Sent: Monday, October 27, 2014 1:51 PM
To: draft-ietf-ops
Thanks Benoit for moving it along
regards
Rajesh
From: Benoit Claise (bclaise)
Sent: Monday, October 27, 2014 9:32 AM
To: draft-ietf-opsawg-capwap-hybrid...@tools.ietf.org
Cc: opsawg@ietf.org
Subject: draft-ietf-opsawg-capwap-hybridmac: from AD review
Hello Warren
Thank for your support.
I will post an updated version with comments this week.
regards
Rajesh
From: Warren Kumari [war...@kumari.net]
Sent: Wednesday, August 27, 2014 1:10 PM
To: opsawg@ietf.org; draft-ietf-opsawg-capwap-alt-tun...@tools.iet
Hello Dorothy
Thanks for the comments. Will incorporate them.
Regards
Rajesh
From: Dorothy Stanley [mailto:dstanley1...@gmail.com]
Sent: Friday, May 09, 2014 7:20 PM
To: Rajesh Pazhyannur (rpazhyan)
Cc: Warren Kumari; opsawg@ietf.org;
draft-ietf-opsawg-capwap-hybrid...@tools.ietf.org
Subject
Dan
Thanks for the clarification. You are absolutely right. What I mean by “title”
below was the name of the I-D file.
Regards
Rajesh
From: Romascanu, Dan (Dan) [mailto:droma...@avaya.com]
Sent: Wednesday, April 23, 2014 1:39 AM
To: Rajesh Pazhyannur (rpazhyan); sarik...@ieee.org; Warren
Hello Warren,
I will address the nits and submit a new version.
Thanks for shepherding this through.
Regards
Rajesh
-Original Message-
From: Warren Kumari [mailto:war...@kumari.net]
Sent: Tuesday, April 22, 2014 11:19 AM
To: opsawg@ietf.org; draft-ietf-opsawg-capwap-hybrid...@tools.
Hello Warren
Thanks for shepherding this through.
I will do the needful with regards to creating a new draft.
Regards
Rajesh
-Original Message-
From: OPSAWG [mailto:opsawg-boun...@ietf.org] On Behalf Of Warren Kumari
Sent: Tuesday, April 22, 2014 11:41 AM
To: opsawg@ietf.org; draft-zha
Behcet
The point you raise had been brought up earlier by Dorothy S. and the text was
updated appropriately.
I believe it was difficult to change the title without restarting the
versioning process. As a result, the title still has Hybrid-MAC in the name.
So, besides the title “hybrid” does not
Hello Warren
I am not aware of any IPR related to this document.
Regards
Rajesh
-Original Message-
From: OPSAWG [mailto:opsawg-boun...@ietf.org] On Behalf Of Warren Kumari
Sent: Monday, April 07, 2014 10:55 AM
To: opsawg@ietf.org; draft-zhang-opsawg-capwap-...@tools.ietf.org
Subject: [O
Hello Warren
I am not aware of any IPR regarding this document.
Regards
Rajesh
On Tue, Apr 8, 2014 at 2:41 AM, Warren Kumari
mailto:war...@kumari.net>> wrote:
Dear opsawg WG,
Be not alarmed.
This email was created to satisfy RFC 6702 "Promoting Compliance with
Intellectual Property Rights (I
Hello OPSAWAG chairs,
In the last week's meeting there was a recommendation to make a WGLC for the
following draft--
IEEE 802.11 MAC Profile for CAPWAP:
http://tools.ietf.org/html/draft-ietf-opsawg-capwap-hybridmac
I wanted to know when you would send out the note.
Thanks
Regards
Rajesh
___
ietf-opsawg-capwap-hybridmac-02.
So potentially a new split MAC profile in the case the tunnel termination is
not at the AC.
-Original Message-
From: Björn Smedman [mailto:bjorn.smed...@anyfinetworks.com]
Sent: Tuesday, February 25, 2014 5:23 AM
To: Cao,Zhen
Cc: Rajesh Pazhyannur (rpazhyan); o
4, 2014 5:54 PM
To: Rajesh Pazhyannur (rpazhyan)
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Simplified Alternative to CAPWAP
Hi Rajesh,
On Tue, Feb 25, 2014 at 1:29 AM, Rajesh Pazhyannur (rpazhyan)
mailto:rpazh...@cisco.com>> wrote:
>
> Thanks for the well captured email. Would lik
Hello Bjorn
We see strong benefits to such a protocol from an extensibility [4],
flexibility [5] and security [6] perspective. If there is interest in exploring
this further please let me know
Thanks for the well captured email. Would like to explore more about what you
are suggesting.
I have
Hello
We have a submitted a new version of Alternate Tunnel Encapsulation for Data
Frames in CAPWAP,
http://datatracker.ietf.org/doc/draft-zhang-opsawg-capwap-cds/.
Abstract
In centralized IEEE 802.11 Wireless Local Area Network (WLAN)
architecture, the Access Controller (AC) isn't inte
Behcet
Thanks for your comments.
Please see the latest draft as we have clarified some of the text to improve
readability. I will address the points raised directly as well.
Regards
Rajesh
From: OPSAWG [mailto:opsawg-boun...@ietf.org] On Behalf Of Behcet Sarikaya
Sent: Monday, December 09, 2013
Hello
I have submitted a new version of the draft IEEE 802.11 MAC Profile for CAPWAP,
http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac/ .
Abstract: CAPWAP defines two entities Wireless Transmission Point (WTP) and
Access Controller (AC). CAPWAP also defines two MAC (Medium A
used to negotiate the profile. where each
profile refers to a table containing an
unambigous division of labor between WTP and AC. The IEEE 802.11 MAC
profile message element is used
as follows: the WTP informs the AC of the supported profile(s) and the
AC selects the profile whe
Melinda
Can I get it you by Sun evening ?
Thanks
Rajesh
-Original Message-
From: opsawg-boun...@ietf.org [mailto:opsawg-boun...@ietf.org] On Behalf Of
Melinda Shore
Sent: Thursday, October 31, 2013 1:11 PM
To: opsawg@ietf.org
Subject: [OPSAWG] Slides
If you're on the agenda during T
John
Thanks for reviewing. Some answers provided.
Regards
Rajesh
-Original Message-
From: John Kaippallimalil [mailto:john.kaippallima...@huawei.com]
Sent: Wednesday, October 30, 2013 8:39 PM
To: Rajesh Pazhyannur (rpazhyan); opsawg@ietf.org
Subject: RE: [OPSAWG] Seeking discussion on
all in all, it seemed
easier to define a new element rather than reuse/overload an existing one.
From: Romascanu, Dan (Dan) [mailto:droma...@avaya.com]
Sent: Tuesday, October 29, 2013 8:26 AM
To: Rajesh Pazhyannur (rpazhyan); opsawg@ietf.org
Subject: RE: [OPSAWG] Seeking discussion on "A
Hello
We would like to request some time on the agenda to discuss " IEEE 802.11 MAC
Profile for CAPWAP ",
http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac/.
In the last IETF meeting we had discussion that has resulted in changing the
way the MAC profile capability is specifie
Hello
We have resubmitted a new version of the draft titled "Alternate Tunnel
Encapsulation for Data Frames in CAPWAP",
http://datatracker.ietf.org/doc/draft-zhang-opsawg-capwap-cds/.
The previous version was titled: "Separation of CAPWAP Control and Data Plane:
Scenarios, Requirements and Solu
Dan
Thanks for the comments. Appreciate the review.
Some follow up comments and questions.
Regards
Rajesh
-Original Message-
From: opsawg-boun...@ietf.org [mailto:opsawg-boun...@ietf.org] On Behalf Of
Romascanu, Dan (Dan)
Sent: Monday, October 21, 2013 6:48 AM
To: opsawg@ietf.org
Subjec
Greetings...
We have submitted a new version of the draft (previously titled "Hybrid
MAC-Model for CAPWAP".
While solving the same problem as in the original draft, this takes a different
approach. We introduce a new element IEEE 802.11 MAC Profile. This profile
defines the functional split bet
Hello
First comment/question:
It appears that you are proposing a new MAC mode which is very similar to Split
MAC mode except that it requires
1) Scheduling to *only* at the WTP (instead of allowing it additionally at
AC)
2) Encryption to *only* at the WTP (instead of allowing it addi
Hello Rong
I am not sure I understand your comment. In a way, the proposed approach of
maintaining a control and data channel with the Access Controller (for all
control and station generated management traffic) is consistent with RFC 5416.
Specifically, in a Local MAC mode, the AP/WTP would main
Hello Dapeng
Yes, you are right that we are proposing that all station generated management
messages are encapsulated within a CAPWAP data tunnel. This is, consistent,
with existing behavior when the AP is either in Local MAC or Split MAC mode.
There are two options for the non-management rela
34 matches
Mail list logo
