RFC 7969 on Customizing DHCP Configuration on the Basis of Network Topology

rfc-editor@rfc-editor.org Thu, 20 October 2016 00:16 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 0CE231293EB; Wed, 19 Oct 2016 17:16:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.033
X-Spam-Level:
X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id piWrekE7Kvup; Wed, 19 Oct 2016 17:16:22 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8736A1294AD; Wed, 19 Oct 2016 17:16:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4597DB80141; Wed, 19 Oct 2016 17:16:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7969 on Customizing DHCP Configuration on the Basis of Network Topology
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161020001622.4597DB80141@rfc-editor.org>
Date: Wed, 19 Oct 2016 17:16:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/CjtGHz-LZR0OfpUaMwAbrwh09PI>
Cc: drafts-update-ref@iana.org, dhcwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 20 Oct 2016 00:16:24 -0000

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

        
        RFC 7969

        Title:      Customizing DHCP Configuration on the 
                    Basis of Network Topology 
        Author:     T. Lemon, T. Mrugalski
        Status:     Informational
        Stream:     IETF
        Date:       October 2016
        Mailbox:    ted.lemon@nominum.com, 
                    tomasz.mrugalski@gmail.com
        Pages:      20
        Characters: 46674
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-topo-conf-09.txt

        URL:        https://www.rfc-editor.org/info/rfc7969

        DOI:        http://dx.doi.org/10.17487/RFC7969

DHCP servers have evolved over the years to provide significant
functionality beyond that described in the DHCP base specifications.
One aspect of this functionality is support for context-specific
configuration information.  This memo describes some such features
and explains their operation.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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