RFC 6656 on Description of Cisco Systems' Subnet Allocation Option for DHCPv4

rfc-editor@rfc-editor.org Fri, 20 July 2012 17:12 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1972811E8088; Fri, 20 Jul 2012 10:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.25
X-Spam-Level:
X-Spam-Status: No, score=-102.25 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2OFpTFS6qC-T; Fri, 20 Jul 2012 10:12:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 9D97D11E8085; Fri, 20 Jul 2012 10:12:15 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7B414621A1; Fri, 20 Jul 2012 10:12:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6656 on Description of Cisco Systems' Subnet Allocation Option for DHCPv4
From: rfc-editor@rfc-editor.org
Message-Id: <20120720171229.7B414621A1@rfc-editor.org>
Date: Fri, 20 Jul 2012 10:12:29 -0700
Cc: dhcwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 20 Jul 2012 17:12:16 -0000

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

        
        RFC 6656

        Title:      Description of Cisco Systems' Subnet 
                    Allocation Option for DHCPv4 
        Author:     R. Johnson, K. Kinnear,
                    M. Stapp
        Status:     Informational
        Stream:     IETF
        Date:       July 2012
        Mailbox:    raj@cisco.com, 
                    kkinnear@cisco.com, 
                    mjs@cisco.com
        Pages:      24
        Characters: 54971
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-subnet-alloc-13.txt

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

This memo documents a DHCPv4 option that currently exists and was
previously privately defined for the operation and usage of the Cisco
Systems' Subnet Allocation Option for DHCPv4.  The option is passed
between the DHCPv4 Client and the DHCPv4 Server to request dynamic
allocation of a subnet, give specifications of the subnet(s)
allocated, and report usage statistics.  This memo documents the
current usage of the option in agreement with RFC 3942, which
declares that any preexisting usages of option numbers in the range
128-223 should be documented and that the working group will try to
officially assign those numbers to those options.  This document is 
not an Internet Standards Track specification; it is published for 
informational purposes.

This document is a product of the Dynamic Host Configuration Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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
Association Management Solutions, LLC