[radext] Fwd: [OPS-DIR] OPS-DIR Review of draft-ietf-radext-ipv6-access-13
Benoit Claise <bclaise@cisco.com> Tue, 04 December 2012 09:56 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3006721F8441 for <radext@ietfa.amsl.com>; Tue, 4 Dec 2012 01:56:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.172
X-Spam-Level:
X-Spam-Status: No, score=-10.172 tagged_above=-999 required=5 tests=[AWL=0.426, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YdEjQkHuyEeU for <radext@ietfa.amsl.com>; Tue, 4 Dec 2012 01:56:21 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 1188D21F842B for <radext@ietf.org>; Tue, 4 Dec 2012 01:56:20 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qB49uJSU004004; Tue, 4 Dec 2012 10:56:19 +0100 (CET)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qB49uJuk013427; Tue, 4 Dec 2012 10:56:19 +0100 (CET)
Message-ID: <50BDC8C3.9090206@cisco.com>
Date: Tue, 04 Dec 2012 10:56:19 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "draft-ietf-radext-ipv6-access@tools.ietf.org" <draft-ietf-radext-ipv6-access@tools.ietf.org>
References: <80A0822C5E9A4440A5117C2F4CD36A640469F0E9@DEMUEXC006.nsn-intra.net>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A640469F0E9@DEMUEXC006.nsn-intra.net>
X-Forwarded-Message-Id: <80A0822C5E9A4440A5117C2F4CD36A640469F0E9@DEMUEXC006.nsn-intra.net>
Content-Type: multipart/alternative; boundary="------------000703050409010608060307"
Cc: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>, "radext@ietf.org" <radext@ietf.org>
Subject: [radext] Fwd: [OPS-DIR] OPS-DIR Review of draft-ietf-radext-ipv6-access-13
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2012 09:56:22 -0000
Hi Authors, Can you please address Mehmet's comments. Regards, Benoit -------- Original Message -------- Subject: [OPS-DIR] OPS-DIR Review of draft-ietf-radext-ipv6-access-13 Date: Tue, 20 Nov 2012 14:38:15 +0100 From: Ersue, Mehmet (NSN - DE/Munich) <mehmet.ersue@nsn.com> To: <ops-dir@ietf.org>, <draft-ietf-radext-ipv6-access@tools.ietf.org> I reviewed the draft "RADIUS attributes for IPv6 Access Networks" ( draft-ietf-radext-ipv6-access-13.txt) for its operational impact. Summary: Intended status: Standards Track Current status: Waiting for AD Go-Ahead The document specifies additional IPv6 RADIUS attributes useful in residential broadband network deployments, which are: assignment of a host IPv6 address and IPv6 DNS server address via DHCPv6; assignment of an IPv6 route announced via router advertisement; assignment of a named IPv6 delegated prefix pool; and assignment of a named IPv6 pool for host DHCPv6 addressing. The document follows the standard method for Radius attribute definition. As such the attributes and their configuration has been sufficiently described. I do not see any blocking issues. The document seems to be ready for publication as Proposed Standard. Minor issues: - Section 4.4. Delegated-IPv6-Prefix-Pool I am not a AAA-NAS expert, however section 4.4. defines the Delegated-IPv6-Prefix-Pool attribute containing the name of an assigned pool that SHOULD be used to select an IPv6 delegated prefix for the user on the NAS. But there is no mention of how the pool itself is defined. A reference to the document where this has been specified would be useful for the reader. - There is one nit error (lines 453/454) which needs to be fixed: ** There are 2 instances of too long lines in the document, the longest one being 3 characters in excess of 72. 453 0+ 0+ 0 0 0+ TBA4 Delegated-IPv6-Prefix-Pool 454 0+ 0+ 0 0 0+ TBA5 Stateful-IPv6-Address-Pool - There is one nit warning: == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Cheers, Mehmet _______________________________________________ OPS-DIR mailing list OPS-DIR@ietf.org https://www.ietf.org/mailman/listinfo/ops-dir
- [radext] Fwd: [OPS-DIR] OPS-DIR Review of draft-i… Benoit Claise
- [radext] Fwd: [OPS-DIR] OPS-DIR Review of draft-i… Wojciech Dec (wdec)
- Re: [radext] Fwd: [OPS-DIR] OPS-DIR Review of dra… Benoit Claise