Re: [dhcwg] [Editorial Errata Reported] RFC3633 (3736)

"Leaf Yeh" <leaf.yeh.sdo@gmail.com> Tue, 01 October 2013 15:40 UTC

Return-Path: <leaf.yeh.sdo@gmail.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 88FBF21E8226 for <dhcwg@ietfa.amsl.com>; Tue, 1 Oct 2013 08:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.933
X-Spam-Level:
X-Spam-Status: No, score=-0.933 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_RECV_IP_219128=1.666]
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 wTnMnY0UbutI for <dhcwg@ietfa.amsl.com>; Tue, 1 Oct 2013 08:40:53 -0700 (PDT)
Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id C179321E805F for <dhcwg@ietf.org>; Tue, 1 Oct 2013 08:40:10 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id uo5so7303729pbc.37 for <dhcwg@ietf.org>; Tue, 01 Oct 2013 08:40:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=AL1ZAYKFsnONgTs4xj22FQPGWbALNNDZSlO6TddzIzE=; b=f76Y/DyagRt8X+f36FoC9HVp0i8LSUstf+77pSo7XhkTHre9kDFCwaiyihUFmb/wbM FxGmnZa4RmsbKVqUmvsfJeEmwTAWpa5LxN400OKBWLMa2X64Ew68jDExGEm4dx6ULJxW olgt2JLn2F4G7gdWcgeB5j/7LB68VJE3Au2RUEVIITUlnmm6pC2tZDc9nfLPcyVV3VSX /nS8FceenbPEv7ZN9VASJ6APx8SJRtnVGWG5XL3YtUdaWcxf1hzlnICQyxVeQHwdohyn IRPAIWnPk6IoX6vnVIozyLesvRC/yp8QOwLTEoqc/Bx6RKr44nTdHWVkmunyZ1VX+Ubl pTdg==
X-Received: by 10.66.136.71 with SMTP id py7mr34314770pab.2.1380642009910; Tue, 01 Oct 2013 08:40:09 -0700 (PDT)
Received: from PC ([219.133.129.162]) by mx.google.com with ESMTPSA id nj9sm7507387pbc.13.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 01 Oct 2013 08:40:09 -0700 (PDT)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: <ot@cisco.com>, <rdroms@cisco.com>, <brian@innovationslab.net>, <ted.lemon@nominum.com>, <volz@cisco.com>, <tomasz.mrugalski@gmail.com>
References: <20130925114309.5568A8E016@rfc-editor.org>
In-Reply-To: <20130925114309.5568A8E016@rfc-editor.org>
Date: Tue, 1 Oct 2013 23:39:57 +0800
Message-ID: <524aecd9.69d4440a.25d9.ffffba17@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac655WHQ37xNcEnsQKOEhd5I+BQ0SwAL54XA
Content-Language: zh-cn
Cc: dhcwg@ietf.org, alexandru.petrescu@gmail.com
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3633 (3736)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 01 Oct 2013 15:40:54 -0000

Frankly speaking, I prefer the original text. This copy revision sound
unnecessary.

I suppose only the 1st router (called the Provider Edge router) in the
provider network needs to add the routing information (or routes) for
delegated prefixes, the other routers (through which the requesting router
may forward traffic) could get these routes from the routing protocol
employed in the ISP network.


Best Regards,
Leaf



-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
RFC Errata System
Sent: Wednesday, September 25, 2013 7:43 PM
To: ot@cisco.com; rdroms@cisco.com; brian@innovationslab.net;
ted.lemon@nominum.com; volz@cisco.com; tomasz.mrugalski@gmail.com
Cc: dhcwg@ietf.org; alexandru.petrescu@gmail.com; rfc-editor@rfc-editor.org
Subject: [dhcwg] [Editorial Errata Reported] RFC3633 (3736)

The following errata report has been submitted for RFC3633,
"IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version
6".

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

--------------------------------------
Type: Editorial
Reported by: Alexandru Petrescu (w/ text from R.  Droms)
<alexandru.petrescu@gmail.com>

Section: 14

Original Text
-------------
If a delegating router communicates with a requesting router through a relay
agent, the delegating router may need a protocol or other out-of-band
communication to add routing information for delegated prefixes into the
provider edge router.

Corrected Text
--------------
If a delegating router communicates with a requesting router through a relay
agent, the delegating router may need a protocol or other out-of-band
communication to add routing information for delegated prefixes into any
router through which the requesting router may forward traffic.

Notes
-----
This is a terminology correction.  See discussion on the email list DHCWG of
the DHC WG of IETF, 24 September 2013,
http://www.ietf.org/mail-archive/web/dhcwg/current/msg14709.html

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please use
"Reply All" to discuss whether it should be verified or rejected. When a
decision is reached, the verifying party (IESG) can log in to change the
status and edit the report, if necessary. 

--------------------------------------
RFC3633 (draft-ietf-dhc-dhcpv6-opt-prefix-delegation-05)
--------------------------------------
Title               : IPv6 Prefix Options for Dynamic Host Configuration
Protocol (DHCP) version 6
Publication Date    : December 2003
Author(s)           : O. Troan, R. Droms
Category            : PROPOSED STANDARD
Source              : Dynamic Host Configuration
Area                : Internet
Stream              : IETF
Verifying Party     : IESG
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg