Subject: [Capwap] FW: [Inquiry #93429] [Fwd: Informational RFC to be:draft-iino-capwap-wicop-02.txt]

From: "Romascanu, Dan (Dan)" <[email-masked]>
Date: Tue, 6 Feb 2007 12:04:42 +0200

The following request to publish draft-iino-capwap-wicop as an
Informational RFC was submitted to the RFC Editor. Please let me know if
there are any issues or comments. 

Dan

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

> > IESG,
> > 
> > This RFC-to-be was submitted to the RFC Editor to be published as
> > Informational: draft-iino-capwap-wicop-02.txt.
> > 
> > Please let us know if this document conflicts with the IETF
> standards
> > process or other work being done in the IETF community.
> > 
> > Four week timeout expires on 20 February 2007.
> > 
> > _________________________________________________________________
> > 
> > NOTE to IESG about:  draft-iino-capwap-wicop-02.txt
> > 
> > This document, submitted to the RFC Editor as an independent 
> > submission by the WG chair, was a partial product of the CAPWAP 
> > working group.
> > Its publication now is intended to be provide historical record of 
> > input to the WG product, and as such the RFC Editor is exercising 
> > minimal editorial control over it.
> > 
> > The RFC Editorial Board raised considerable issue with the
> principle
> > of publishing such a "WG spinoff" document as an independent 
> > submission, rather than as a WG or individual submission.  This led 
> > the RFC
> Editor
> > to request a policy opinion from the IAB, but no such
> policy opinion
> > was provided.
> > 
> > We do not regard publication of this document as an independent 
> > submission to be a precedent.  However, we would REALLY
> like to clear
> > our ISR queue, and so we are proceeding with its publication.
> > 
> > We intend to include the following RFC Editor Note, in
> addition to any
> > note requested by the IESG:
> > 
> > 
> > 	"RFC Editor Note:
> > 
> > 	This document was originally submitted to the CAPWAP Working
> > 	Group.  It is being published now as a historical record of the
> > 	development of CAPWAP ideas; it is not an official Working
> > 	Group product."
> > 
> > ___________________________________________________
> > 
> >                   Wireless LAN Control Protocol (WiCoP)
> > 
> >    The popularity of wireless local area networks (WLANs) has led to
> >    wide spread deployments across different establishments.  It has
> >    also translated in to increasing scale of the WLANs.  Large-scale
> >    deployments made of large numbers of wireless termination points
> >    (WTPs) and covering substantial areas are increasingly common.
> > 
> >    The Wireless LAN Control Protocol (WiCoP) described in this 
> > document
> >    allows for the control and provisioning of large-scale WLANs.  It
> >    enables central management of these networks and realizes the
> >    objectives set forth for the control and provisioning of wireless
> >    access points (CAPWAP).
> > 
> > Sincerely,
> > 
> > Sandy Ginoza - USC/ISI
> > Request for Comments Documents
> > 
> > 
> > 
> > 
> > 
> 
> 

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

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