[dhcwg] RFC 9243 on A YANG Data Model for DHCPv6 Configuration

rfc-editor@rfc-editor.org Tue, 21 June 2022 22:23 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D01D5C14F721; Tue, 21 Jun 2022 15:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.66
X-Spam-Level:
X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uhfy9TGERcwA; Tue, 21 Jun 2022 15:23:24 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0EEEC14F72E; Tue, 21 Jun 2022 15:23:22 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 811881BA4906; Tue, 21 Jun 2022 15:23:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dhcwg@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20220621222322.811881BA4906@rfcpa.amsl.com>
Date: Tue, 21 Jun 2022 15:23:22 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/B_aFuYGfnenXfj-0KSqJCcQDpqg>
Subject: [dhcwg] =?utf-8?q?RFC_9243_on_A_YANG_Data_Model_for_DHCPv6_Confi?= =?utf-8?q?guration?=
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2022 22:23:27 -0000

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

        
        RFC 9243

        Title:      A YANG Data Model for 
                    DHCPv6 Configuration 
        Author:     I. Farrer, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2022
        Mailbox:    ian.farrer@telekom.de
        Pages:      92
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-dhcpv6-yang-25.txt

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

        DOI:        10.17487/RFC9243

This document describes YANG data models for the configuration and
management of Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
(RFC 8415) servers, relays, and clients.

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

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  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