Re: draft-ietf-ipv6-ra-flags-option edits
Jari Arkko <jari.arkko@piuha.net> Mon, 17 September 2007 16:23 UTC
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IXJNj-0001XG-Tu; Mon, 17 Sep 2007 12:23:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IXJNi-0001X8-3f for ipv6@ietf.org; Mon, 17 Sep 2007 12:23:30 -0400
Received: from p130.piuha.net ([193.234.218.130]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXJNh-0002HQ-DR for ipv6@ietf.org; Mon, 17 Sep 2007 12:23:30 -0400
Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 12102198690; Mon, 17 Sep 2007 19:23:28 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id A2A3519865D; Mon, 17 Sep 2007 19:23:27 +0300 (EEST)
Message-ID: <46EEAA00.5050505@piuha.net>
Date: Mon, 17 Sep 2007 19:23:28 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.13 (X11/20070824)
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <E1ITF7O-0001cl-LP@ietf.org> <46DFFE97.70801@innovationslab.net> <46DFFFBA.8050509@piuha.net> <46E94FF7.8040101@innovationslab.net>
In-Reply-To: <46E94FF7.8040101@innovationslab.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: Bob Hinden <bob.hinden@nokia.com>, IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ra-flags-option edits
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org
I did not see any complaints, so given that Brian's new version is in the directories I will proceed with the approval. Thanks, Jari Brian Haberman kirjoitti: > All, > The IESG reviewed the RA flags option draft and provided several > comments. In order to address those comments, I proposed the > following OLD/NEW edits to the document. I will submit a revised > version of the document to the ID editor soon. If you have issues > with the proposed changes, please let me know quickly. > > > > OLD: > Length = 1; The length MUST be checked when processing the option > in order to allow for future expansion of this option if the need > arises. > > NEW: > Length - The length MUST be checked when processing the option > in order to allow for future expansion of this option. An > implementation of this specification MUST set the Length to 1, > MUST ignore any unrecognized data, and MUST be able to recognize > the specified length in order to skip over unrecognized bits. > > > OLD: > During the construction/transmission, this option: > > o MUST only occur in Router Advertisement messages > > o MUST be the first option immediately following the Router > Advertisement message header > > o MUST only occur once in the Router Advertisement message. > > NEW: > During the construction/transmission, this option: > > o MUST only occur in Router Advertisement messages > > o MUST occur prior to any additional options associated with any > flags set in this option > > o MUST only occur once in the Router Advertisement message > > o MUST NOT be added to a Router Advertisement message if no flags > in the option are set > > o MUST have all unused flags set to zero. > > > OLD: > Upon reception, a receiver processing NDP messages containing this > option: > > o MUST ignore the option if it occurs in a message other than a > Router Advertisement > > o MUST ignore the option if it is not the first option in the Router > Advertisement > > o MUST ignore all instances of the option except the first one > encountered in the Router Advertisement message > > NEW: > Upon reception, a receiver processing NDP messages containing this > option: > > o MUST ignore the option if it occurs in a message other than a > Router Advertisement > > o MUST ignore all instances of the option except the first one > encountered in the Router Advertisement message > > o MUST ignore the option if the Length is less than 1 > > o MUST ignore any unknown flag bits. > > > OLD: > The bit fields within the option are numbered from left to right from > 8 to 55 and follow the numbering of the flag bits in the RA option > described in Figure 1. Flag bits 0 to 7 are found in the Router > Advertisement message header defined in [1] > > NEW: > The bit fields within the option are numbered from left to right from > 8 to 55 (starting at bit offset 16 in the option) and follow the > numbering of the flag bits in the RA option described in Figure 1. > Flag bits 0 to 7 are found in the Router Advertisement message header > defined in [1] > > > OLD: > The assignment of new RA flags in the RA option header and for the > bits defined in the RA extension option defined in this document > require standards action or IESG approval. > > > NEW: > The assignment of new RA flags in the RA option header and for the > bits defined in the RA extension option defined in this document > require standards action or IESG approval [RFC2434]. > > > Regards, > Brian > > > -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- draft-ietf-ipv6-ra-flags-option edits Brian Haberman
- Re: draft-ietf-ipv6-ra-flags-option edits Jari Arkko