RFC 5417 on Control And Provisioning of Wireless Access Points (CAPWAP) Access Controller DHCP Option

rfc-editor@rfc-editor.org Fri, 06 March 2009 00:56 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30D5D28C1F9 for <ietf-announce@core3.amsl.com>; Thu, 5 Mar 2009 16:56:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.847
X-Spam-Level:
X-Spam-Status: No, score=-16.847 tagged_above=-999 required=5 tests=[AWL=0.152, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 qOT9z8n8BEnO for <ietf-announce@core3.amsl.com>; Thu, 5 Mar 2009 16:56:31 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id E889028C1F0 for <ietf-announce@ietf.org>; Thu, 5 Mar 2009 16:56:30 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 873CF24055F; Thu, 5 Mar 2009 16:55:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5417 on Control And Provisioning of Wireless Access Points (CAPWAP) Access Controller DHCP Option
From: rfc-editor@rfc-editor.org
Message-Id: <20090306005529.873CF24055F@bosco.isi.edu>
Date: Thu, 05 Mar 2009 16:55:29 -0800
Cc: capwap@frascone.com, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 00:56:32 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5417

        Title:      Control And Provisioning of Wireless 
                    Access Points (CAPWAP) Access Controller DHCP 
                    Option 
        Author:     P. Calhoun
        Status:     Standards Track
        Date:       March 2009
        Mailbox:    pcalhoun@cisco.com
        Pages:      6
        Characters: 11551
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-capwap-dhc-ac-option-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5417.txt

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

This document is a product of the Control And Provisioning of Wireless Access Points Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute