[dhcwg] [Errata Verified] RFC3736 (3796)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 02 March 2014 10:46 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5EF1A0C46; Sun, 2 Mar 2014 02:46:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 R0-1SXavgMH6; Sun, 2 Mar 2014 02:46:07 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id F2C6A1A0C5A; Sun, 2 Mar 2014 02:46:06 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8BCF27FC3A5; Sun, 2 Mar 2014 02:46:04 -0800 (PST)
To: rdroms.ietf@gmail.com, rdroms@cisco.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140302104604.8BCF27FC3A5@rfc-editor.org>
Date: Sun, 2 Mar 2014 02:46:04 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/KlvaZwaWmvRO2tUw_KxcToaqmB8
Cc: dhcwg@ietf.org, rfc-editor@rfc-editor.org, ted.lemon@nominum.com, iesg@ietf.org
Subject: [dhcwg] [Errata Verified] RFC3736 (3796)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 02 Mar 2014 10:46:08 -0000

The following errata report has been verified for RFC3736,
"Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3736&eid=3796

--------------------------------------
Status: Verified
Type: Technical

Reported by: Ralph Droms <rdroms.ietf@gmail.com>
Date Reported: 2013-11-11
Verified by: Ted Lemon (IESG)

Section: 5.2

Original Text
-------------
   Client message: sent by a DHCP relay agent in a Relay-forward message
                   to carry the client message to a server (section 20)

   Server message: sent by a DHCP server in a Relay-reply message to
                   carry a response message to the relay agent (section
                   20)


Corrected Text
--------------
   Relay Message: sent by a DHCP relay agent in a Relay-forward
                  message to carry the client message to a server or
                  sent by a DHCP server in a Relay-reply message to
                  carry a response message to the relay agent (section
                  20)


Notes
-----
The correct name for the option carries in the Relay-forward message is "Relay Message".  That option is shared by both Relay-forward and Relay-reply messages to carry a DHCPv6 message from or to (respectively) a DHCPv6 client.

I've marked this errata as "technical" because it might have an impact on implementations.

--------------------------------------
RFC3736 (draft-ietf-dhc-dhcpv6-stateless-04)
--------------------------------------
Title               : Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6
Publication Date    : April 2004
Author(s)           : R. Droms
Category            : PROPOSED STANDARD
Source              : Dynamic Host Configuration
Area                : Internet
Stream              : IETF
Verifying Party     : IESG