From owner-radiusext@ops.ietf.org Mon Jan 10 12:49:04 2011 Return-Path: X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 074CF3A6765 for ; Mon, 10 Jan 2011 12:49:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.473 X-Spam-Level: X-Spam-Status: No, score=-103.473 tagged_above=-999 required=5 tests=[AWL=0.964, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id raLc1t2SXoV4 for ; Mon, 10 Jan 2011 12:48:03 -0800 (PST) Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 18B543A672E for ; Mon, 10 Jan 2011 12:48:00 -0800 (PST) Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PcOe9-000NEE-Hd for radiusext-data0@psg.com; Mon, 10 Jan 2011 20:47:21 +0000 Received: from mail.ietf.org ([2001:1890:1112:1::20]) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PcOe6-000NDr-Pr for radiusext@ops.ietf.org; Mon, 10 Jan 2011 20:47:19 +0000 Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9FD73A66B4 for ; Mon, 10 Jan 2011 12:45:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xtnPS634iToM; Mon, 10 Jan 2011 12:45:01 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9C433A6405; Mon, 10 Jan 2011 12:45:01 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Cc: radiusext@ops.ietf.org Subject: I-D Action:draft-ietf-radext-ipv6-access-03.txt X-Test-IDTracker: no X-IETF-IDTracker: 3.10 Message-ID: <20110110204501.5529.90484.idtracker@localhost> Date: Mon, 10 Jan 2011 12:45:01 -0800 Sender: owner-radiusext@ops.ietf.org Precedence: bulk List-ID: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the RADIUS EXTensions Working Group of the IETF. Title : RADIUS attributes for IPv6 Access Networks Author(s) : B. Lourdelet, et al. Filename : draft-ietf-radext-ipv6-access-03.txt Pages : 14 Date : 2011-01-10 This document specifies IPv6 RADIUS attributes, which complement those of RFC3162, and are intended to be used in residential broadband networks, where specific user configuration information is expected to be passed as part of the AAA process between a NAS and an AAA server. The attributes cover the assignment or reporting of the following; a specific host IPv6 address; a recursive DNS IPv6 server address; a specific IPv6 route announced to a host; a named IPv6 delegated prefix pool to be used for assignments to an accessing host. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-radext-ipv6-access-03.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-radext-ipv6-access-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-01-10123459.I-D@ietf.org> --NextPart-- -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-radiusext@ops.ietf.org Wed Jan 12 16:54:45 2011 Return-Path: X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B80C93A67FB for ; Wed, 12 Jan 2011 16:54:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.149 X-Spam-Level: X-Spam-Status: No, score=-104.149 tagged_above=-999 required=5 tests=[AWL=-0.551, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjuBJi56RnQ1 for ; Wed, 12 Jan 2011 16:54:40 -0800 (PST) Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 5FF133A67EC for ; Wed, 12 Jan 2011 16:54:39 -0800 (PST) Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PdBRH-0001II-HK for radiusext-data0@psg.com; Thu, 13 Jan 2011 00:53:19 +0000 Received: from g6t0184.atlanta.hp.com ([15.193.32.61]) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PdBR5-0001Hn-1d for radiusext@ops.ietf.org; Thu, 13 Jan 2011 00:53:07 +0000 Received: from G5W0603.americas.hpqcorp.net (g5w0603.americas.hpqcorp.net [16.228.9.186]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g6t0184.atlanta.hp.com (Postfix) with ESMTPS id 9E748D34E; Thu, 13 Jan 2011 00:53:01 +0000 (UTC) Received: from G6W0173.americas.hpqcorp.net (16.230.33.182) by G5W0603.americas.hpqcorp.net (16.228.9.186) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 13 Jan 2011 00:51:21 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G6W0173.americas.hpqcorp.net ([16.230.33.182]) with mapi; Thu, 13 Jan 2011 00:51:20 +0000 From: "Sanchez, Mauricio (HP Networking)" To: "radiusext@ops.ietf.org" CC: "Bernard Aboba (Bernard_Aboba@hotmail.com)" Date: Thu, 13 Jan 2011 00:46:55 +0000 Subject: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round) Thread-Topic: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round) Thread-Index: AcuyuykLx3yJZs1XTq2UohstnTZ92Q== Message-ID: <9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194@GVW0671EXC.americas.hpqcorp.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194GVW0671EXCame_" MIME-Version: 1.0 Sender: owner-radiusext@ops.ietf.org Precedence: bulk List-ID: --_000_9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194GVW0671EXCame_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable This is an announcement of RADEXT WG second last call on "RADIUS attributes= for IPv6 Access Networks", prior to sending the document to the IESG for p= ublication as a proposed standard RFC. The first last call did not garner= any comments, whether positive or negative. If you read the draft and hav= e no issues, please state this as so on the mailing list. The document is available for inspection here: http://tools.ietf.org/wg/radext/draft-ietf-radext-ipv6-access/ This RADEXT WG last call will last until January 26, 2011. If you have co= mments on the document, please file using TRAC system. See below for summa= ry of instructions. Thanks, MS 1. To submit an issue in TRAC, you first need to login to the RADEXT = WG site on the tools server: http://tools.ietf.org/wg/radext/trac/login 2. If you don't already have a login ID, you can obtain one by naviga= ting to this site: http://trac.tools.ietf.org/newlogin 3. Once you have obtained an account, and have logged in, you can fil= e an issue by navigating to the ticket entry form: http://trac.tools.ietf.= org/wg/radext/trac/newticket 4. When opening an issue: a. The Type: field should be set to "defect" for an issue with the cu= rrent document text, or "enhancement" for a proposed addition of functional= ity (such as an additional requirement). b. The Priority: field is set based on the severity of the Issue. Fo= r example, editorial issues are typically "minor" or "trivial". c. The Milestone: field should be set to milestone1 (useless, I know)= . d. The Component: field should be set to the document you are filing t= he issue on. e. The Version: field should be set to "1.0". f. The Severity: field should be set to based on the status of the d= ocument (e.g. "In WG Last Call" for a document in WG last call) g. The Keywords: and CC: fields can be left blank unless inspiration= seizes you. h. The Assign To: field is generally filled in with the email address = of the editor. 5. Typically it won't be necessary to enclose a file with the ticket,= but if you need to, select "I have files to attach to this ticket". 6. If you want to preview your Issue, click on the "Preview" button. = When you're ready to submit the issue, click on the "Create Ticket" button= . 7. If you want to update an issue, go to the "View Tickets" page: htt= p://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the ticket # you = want to update, and then modify the ticket fields as required --_000_9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194GVW0671EXCame_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

This is an announcement of RADEXT WG second last call on "RADIUS attribut= es for IPv6 Access Networks", prior to sending the document to the IES= G for publication as a proposed standard RFC.   The first last ca= ll did not garner any comments, whether positive or negative.  If you = read the draft and have no issues, please state this as so on the mailing l= ist. 

The document is available for inspection here:<= /p>

http://tools.ietf.org/wg/ra= dext/draft-ietf-radext-ipv6-access/

This RADEXT WG last call will last until Jan= uary 26, 2011.   If you have comments on the document, please fil= e using TRAC system.  See below for summary of instructions.

Thanks,
MS

 <= /o:p>

1.  =      To submit an issue in TRAC, you first need to logi= n to the RADEXT WG site on the tools server:  http://tools.ietf.org/wg/radext/trac/login

2.       If you don’t alread= y have a login ID, you can obtain one by navigating to this site: &nbs= p; http://trac.tools.ietf.o= rg/newlogin

3.       Once you have= obtained an account, and have logged in, you can file an issue by navigati= ng to the  ticket entry form: http://trac.tools.ietf.org/wg/radext/trac/newticket=

4.       When opening an issue:
a.       The Type: field should be set = to “defect” for an issue with the current document text, or = 220;enhancement” for a proposed addition of functionality (such as an= additional requirement).
b.      The Priority= : field is set based on the severity of the Issue.   For example,= editorial issues are typically “minor” or “trivial”= ;.
c.       The Milestone: field should b= e set to milestone1 (useless, I know).
d.     = The Component: field should be set to the document you are filing the issu= e on. 
e.      The Version: field should = be set to “1.0”.
f.      &nbs= p; The Severity: field should be set to based on the status of the document= (e.g. “In WG Last Call” for a document in WG last call)
g.&= nbsp;       The Keywords: and CC: fields can = be left blank unless inspiration seizes you.
h.    =   The Assign To: field is generally filled in with the email address o= f the editor.

5.       Typically it w= on’t be necessary to enclose a file with the ticket, but if you need = to, select “I have files to attach to this ticket”.

6.&= nbsp;      If you want to preview your Issue, clic= k on the “Preview” button.  When you’re ready to sub= mit the issue, click on the “Create Ticket” button.

7.&= nbsp;      If you want to update an issue, go to t= he "View Tickets" page: http://trac.tools.ietf.org/wg/radext/trac/report/1  Click on the ticket # you want to update, and then modify the ticke= t fields as required

 <= /o:p>

= --_000_9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194GVW0671EXCame_-- -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-radiusext@ops.ietf.org Thu Jan 13 01:43:20 2011 Return-Path: X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 324913A6AC5 for ; Thu, 13 Jan 2011 01:43:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.586 X-Spam-Level: X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nHV2eL7c4mBn for ; Thu, 13 Jan 2011 01:43:18 -0800 (PST) Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id A88813A69E5 for ; Thu, 13 Jan 2011 01:43:18 -0800 (PST) Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PdJhA-0002Qr-FW for radiusext-data0@psg.com; Thu, 13 Jan 2011 09:42:16 +0000 Received: from zinfandel.tools.ietf.org ([2001:1890:1112:1::2a]) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PdJh7-0002QY-SV for radiusext@ops.ietf.org; Thu, 13 Jan 2011 09:42:14 +0000 Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from ) id 1PdJh6-0002pi-2b; Thu, 13 Jan 2011 01:42:12 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.11.7 Cc: radiusext@ops.ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.11.7, by Edgewall Software To: aland@deployingradius.com X-Trac-Project: radext Date: Thu, 13 Jan 2011 09:42:12 -0000 Reply-To: radiusext@ops.ietf.org X-URL: http://tools.ietf.org/radext/ Subject: [radext] ipv6-access #62 (new): Use of "Address" X-Trac-Ticket-URL: https://wiki.tools.ietf.org/wg/radext/trac/ticket/62 Message-ID: <066.17eef1017064d45f1c34a9e0e44ff3f1@tools.ietf.org> X-Trac-Ticket-ID: 62 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: aland@deployingradius.com, radiusext@ops.ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false Sender: owner-radiusext@ops.ietf.org Precedence: bulk List-ID: #62: Use of "Address" Section 3.1 and 3.1: ... Address The Address field contains a 128-bit IPv6 address. I suggest using "IPv6 Address", as "address" is defined in RFC2865 as being for Ipv4 addressess. -- ---------------------------------------+------------------------------------ Reporter: aland@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: ipv6-access | Version: Severity: In WG Last Call | Keywords: ---------------------------------------+------------------------------------ Ticket URL: radext -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-radiusext@ops.ietf.org Thu Jan 13 01:43:29 2011 Return-Path: X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 75F643A6AC5 for ; Thu, 13 Jan 2011 01:43:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.582 X-Spam-Level: X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iAzaCjdX7bGK for ; Thu, 13 Jan 2011 01:43:28 -0800 (PST) Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 5717D3A69E5 for ; Thu, 13 Jan 2011 01:43:28 -0800 (PST) Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PdJhZ-0002S6-8A for radiusext-data0@psg.com; Thu, 13 Jan 2011 09:42:41 +0000 Received: from liberty.deployingradius.com ([88.191.76.128]) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PdJhW-0002Rq-OM for radiusext@ops.ietf.org; Thu, 13 Jan 2011 09:42:38 +0000 Message-ID: <4D2EC90B.6010206@deployingradius.com> Date: Thu, 13 Jan 2011 10:42:35 +0100 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: "Sanchez, Mauricio (HP Networking)" CC: "radiusext@ops.ietf.org" , "Bernard Aboba (Bernard_Aboba@hotmail.com)" Subject: Re: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round) References: <9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194@GVW0671EXC.americas.hpqcorp.net> In-Reply-To: <9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194@GVW0671EXC.americas.hpqcorp.net> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-radiusext@ops.ietf.org Precedence: bulk List-ID: Sanchez, Mauricio (HP Networking) wrote: > This is an announcement of RADEXT WG second last call on "RADIUS > attributes for IPv6 Access Networks", prior to sending the document to > the IESG for publication as a proposed standard RFC. The first last > call did not garner any comments, whether positive or negative. If you > read the draft and have no issues, please state this as so on the > mailing list. Section 2.2: ... Existing IETF Radius attributes convey DNS as 32- bit IPv4 addresses and cannot support a 128-bit IPv6 address. I'm unaware of any IETF specification which transports DNS server addresses in RADIUS. Is there a reference for this? Section 3.1 and 3.1: ... Address The Address field contains a 128-bit IPv6 address. I suggest using "IPv6 Address", as "address" is defined in RFC2865 as being for Ipv4 addresses. But this isn't critical, and can be left as-is. Other than that, I'm OK with the document. I've also opened tickets in trac. Alan DeKok. -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-radiusext@ops.ietf.org Thu Jan 13 01:43:41 2011 Return-Path: X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 818343A6AC5 for ; Thu, 13 Jan 2011 01:43:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.586 X-Spam-Level: X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f9kA1dqBfT6i for ; Thu, 13 Jan 2011 01:43:40 -0800 (PST) Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8645A3A69E5 for ; Thu, 13 Jan 2011 01:43:40 -0800 (PST) Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PdJg9-0002Mk-Tk for radiusext-data0@psg.com; Thu, 13 Jan 2011 09:41:13 +0000 Received: from zinfandel.tools.ietf.org ([2001:1890:1112:1::2a]) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PdJg7-0002MU-54 for radiusext@ops.ietf.org; Thu, 13 Jan 2011 09:41:11 +0000 Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from ) id 1PdJg2-0001P4-Sn; Thu, 13 Jan 2011 01:41:07 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.11.7 Cc: radiusext@ops.ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.11.7, by Edgewall Software To: aland@deployingradius.com X-Trac-Project: radext Date: Thu, 13 Jan 2011 09:41:06 -0000 Reply-To: radiusext@ops.ietf.org X-URL: http://tools.ietf.org/radext/ Subject: [radext] ipv6-access #61 (new): DNS attribute for IPv4? X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/61 Message-ID: <066.cc2411f6b119d81f73eec60b018d6670@tools.ietf.org> X-Trac-Ticket-ID: 61 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: aland@deployingradius.com, radiusext@ops.ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false Sender: owner-radiusext@ops.ietf.org Precedence: bulk List-ID: #61: DNS attribute for IPv4? Section 2.2: ... Existing IETF Radius attributes convey DNS as 32- bit IPv4 addresses and cannot support a 128-bit IPv6 address. I'm unaware of any IETF specification which transports DNS server addresses in RADIUS. Is there a reference for this? -- ---------------------------------------+------------------------------------ Reporter: aland@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: ipv6-access | Version: Severity: In WG Last Call | Keywords: ---------------------------------------+------------------------------------ Ticket URL: radext -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-radiusext@ops.ietf.org Thu Jan 13 10:14:30 2011 Return-Path: X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34F6D3A6A57 for ; Thu, 13 Jan 2011 10:14:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFtK1apTGegF for ; Thu, 13 Jan 2011 10:14:29 -0800 (PST) Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 28BCE3A683D for ; Thu, 13 Jan 2011 10:14:29 -0800 (PST) Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PdRfl-00058O-Sm for radiusext-data0@psg.com; Thu, 13 Jan 2011 18:13:21 +0000 Received: from remote.iea-software.com ([70.89.142.196] helo=aspen.internal.iea-software.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PdRfj-000584-14 for radiusext@ops.ietf.org; Thu, 13 Jan 2011 18:13:19 +0000 Received: from SMURF (unverified [10.0.3.195]) by aspen.internal.iea-software.com (Rockliffe SMTPRA 7.0.6) with ESMTP id ; Thu, 13 Jan 2011 10:13:17 -0800 Date: Thu, 13 Jan 2011 10:13:12 -0800 (Pacific Standard Time) From: Peter Deacon To: "Sanchez, Mauricio (HP Networking)" cc: "radiusext@ops.ietf.org" Subject: Re: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round) In-Reply-To: <9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194@GVW0671EXC.americas.hpqcorp.net> Message-ID: References: <9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194@GVW0671EXC.americas.hpqcorp.net> User-Agent: Alpine 2.00 (WNT 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="308460330-4360-1294942393=:6308" Sender: owner-radiusext@ops.ietf.org Precedence: bulk List-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --308460330-4360-1294942393=:6308 Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 13 Jan 2011, Sanchez, Mauricio (HP Networking) wrote: > This is an announcement of RADEXT WG second last call on "RADIUS attributes for > IPv6 Access Networks", prior to sending the document to the IESG for publication > as a proposed standard RFC.   The first last call did not garner any comments, > whether positive or negative.  If you read the draft and have no issues, please > state this as so on the mailing list. Looks good, noticed one minor problem. In 3.3 description the reserved field is missing. Recommend adding (RFC3162 text) Reserved This field, which is reserved and MUST be present, is always set to zero regards, Peter --308460330-4360-1294942393=:6308-- -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-radiusext@ops.ietf.org Wed Jan 26 00:10:47 2011 Return-Path: X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0526A3A6951 for ; Wed, 26 Jan 2011 00:10:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.549 X-Spam-Level: X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ptACJWMlDjc1 for ; Wed, 26 Jan 2011 00:10:45 -0800 (PST) Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 39D653A6969 for ; Wed, 26 Jan 2011 00:10:45 -0800 (PST) Received: from majordom by psg.com with local (Exim 4.73 (FreeBSD)) (envelope-from ) id 1Pi0S4-000FQP-Jy for radiusext-data0@psg.com; Wed, 26 Jan 2011 08:10:04 +0000 Received: from nj300815-nj-outbound.net.avaya.com ([135.11.29.16] helo=p-us1-iereast-outbound-tmp.us1.avaya.com) by psg.com with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1Pi0S1-000FPf-LF for radiusext@ops.ietf.org; Wed, 26 Jan 2011 08:10:01 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEALtkP03GmAcF/2dsb2JhbACkdnOjKAKZGoVPBJAK X-IronPort-AV: E=Sophos;i="4.60,379,1291611600"; d="scan'208";a="56087036" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 26 Jan 2011 03:07:57 -0500 X-IronPort-AV: E=Sophos;i="4.60,379,1291611600"; d="scan'208";a="574832875" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 26 Jan 2011 03:07:56 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: FW: Informational RFC to be: Date: Wed, 26 Jan 2011 09:07:42 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Informational RFC to be: Thread-Index: Acu8BK7NmNDPP3jaTfygXfWO/AmDMwBKxtGQ From: "Romascanu, Dan (Dan)" To: "radext mailing list" Sender: owner-radiusext@ops.ietf.org Precedence: bulk List-ID: Hi, See the announcement below and pay attention to the IESG note.=20 Dan -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG Sent: Monday, January 24, 2011 10:20 PM To: RFC Editor; rfc-ise@rfc-editor.org Cc: iana@iana.org; The IESG; ietf-announce@ietf.org Subject: Re: Informational RFC to be: The IESG has no problem with the publication of 'Cisco Vendor Specific RADIUS Attributes for the Delivery of Keying Material' as an Informational RFC. The IESG would also like the RFC-Editor to review the comments in the datatracker (http://datatracker.ietf.org/doc/draft-zorn-radius-keywrap/) related to this document and determine whether or not they merit incorporation into the document. Comments may exist in both the ballot and the comment log. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-zorn-radius-keywrap/ The process for such documents is described at http://www.rfc-editor.org/indsubs.html Thank you, The IESG Secretary Technical Summary This document defines a set of vendor specific RADIUS Attributes designed to allow both the secure transmission of cryptographic keying material and strong authentication of any RADIUS message. These attributes have been allocated from the Cisco vendor specific space and have been implemented by multiple vendors. Working Group Summary This document is not the result of any IETF Working Group. It is an Independent Stream submission to the RFC Editor. Protocol Quality =20 Note to RFC Editor 1. Please include the IESG note below if the document is published as an RFC.=20 2. In the Abstract section s/This attributes/These attributes/ IESG Note The IESG has concluded that this work is related to IETF work done in the RADEXT WG, but this relationship does not prevent publishing. The IESG recommends that the RADEXT WG proceeds with the=20 work for an interoperable modern key wrap solution using attributes from the standard space as part of its charter.=20 _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: Envelope-to: radiusext-data0@psg.com Delivery-date: Wed, 26 Jan 2011 08:11:07 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: FW: Informational RFC to be: Date: Wed, 26 Jan 2011 09:07:42 +0100 Message-ID: Thread-Topic: Informational RFC to be: Thread-Index: Acu8BK7NmNDPP3jaTfygXfWO/AmDMwBKxtGQ From: "Romascanu, Dan (Dan)" To: "radext mailing list" Hi, See the announcement below and pay attention to the IESG note.=20 Dan -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG Sent: Monday, January 24, 2011 10:20 PM To: RFC Editor; rfc-ise@rfc-editor.org Cc: iana@iana.org; The IESG; ietf-announce@ietf.org Subject: Re: Informational RFC to be: The IESG has no problem with the publication of 'Cisco Vendor Specific RADIUS Attributes for the Delivery of Keying Material' as an Informational RFC. The IESG would also like the RFC-Editor to review the comments in the datatracker (http://datatracker.ietf.org/doc/draft-zorn-radius-keywrap/) related to this document and determine whether or not they merit incorporation into the document. Comments may exist in both the ballot and the comment log. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-zorn-radius-keywrap/ The process for such documents is described at http://www.rfc-editor.org/indsubs.html Thank you, The IESG Secretary Technical Summary This document defines a set of vendor specific RADIUS Attributes designed to allow both the secure transmission of cryptographic keying material and strong authentication of any RADIUS message. These attributes have been allocated from the Cisco vendor specific space and have been implemented by multiple vendors. Working Group Summary This document is not the result of any IETF Working Group. It is an Independent Stream submission to the RFC Editor. Protocol Quality =20 Note to RFC Editor 1. Please include the IESG note below if the document is published as an RFC.=20 2. In the Abstract section s/This attributes/These attributes/ IESG Note The IESG has concluded that this work is related to IETF work done in the RADEXT WG, but this relationship does not prevent publishing. The IESG recommends that the RADEXT WG proceeds with the=20 work for an interoperable modern key wrap solution using attributes from the standard space as part of its charter.=20 _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: Envelope-to: radiusext-data0@psg.com Delivery-date: Thu, 13 Jan 2011 18:14:16 +0000 Date: Thu, 13 Jan 2011 10:13:12 -0800 (Pacific Standard Time) From: Peter Deacon To: "Sanchez, Mauricio (HP Networking)" cc: "radiusext@ops.ietf.org" Subject: Re: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round) Message-ID: User-Agent: Alpine 2.00 (WNT 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="308460330-4360-1294942393=:6308" This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --308460330-4360-1294942393=:6308 Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 13 Jan 2011, Sanchez, Mauricio (HP Networking) wrote: > This is an announcement of RADEXT WG second last call on "RADIUS attributes for > IPv6 Access Networks", prior to sending the document to the IESG for publication > as a proposed standard RFC.   The first last call did not garner any comments, > whether positive or negative.  If you read the draft and have no issues, please > state this as so on the mailing list. Looks good, noticed one minor problem. In 3.3 description the reserved field is missing. Recommend adding (RFC3162 text) Reserved This field, which is reserved and MUST be present, is always set to zero regards, Peter --308460330-4360-1294942393=:6308-- -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: Envelope-to: radiusext-data0@psg.com Delivery-date: Thu, 13 Jan 2011 09:42:48 +0000 Message-ID: <4D2EC90B.6010206@deployingradius.com> Date: Thu, 13 Jan 2011 10:42:35 +0100 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: "Sanchez, Mauricio (HP Networking)" CC: "radiusext@ops.ietf.org" , "Bernard Aboba (Bernard_Aboba@hotmail.com)" Subject: Re: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sanchez, Mauricio (HP Networking) wrote: > This is an announcement of RADEXT WG second last call on "RADIUS > attributes for IPv6 Access Networks", prior to sending the document to > the IESG for publication as a proposed standard RFC. The first last > call did not garner any comments, whether positive or negative. If you > read the draft and have no issues, please state this as so on the > mailing list. Section 2.2: ... Existing IETF Radius attributes convey DNS as 32- bit IPv4 addresses and cannot support a 128-bit IPv6 address. I'm unaware of any IETF specification which transports DNS server addresses in RADIUS. Is there a reference for this? Section 3.1 and 3.1: ... Address The Address field contains a 128-bit IPv6 address. I suggest using "IPv6 Address", as "address" is defined in RFC2865 as being for Ipv4 addresses. But this isn't critical, and can be left as-is. Other than that, I'm OK with the document. I've also opened tickets in trac. Alan DeKok. -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: Envelope-to: radiusext-data0@psg.com Delivery-date: Thu, 13 Jan 2011 09:42:21 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" Cc: radiusext@ops.ietf.org Auto-Submitted: auto-generated To: aland@deployingradius.com Date: Thu, 13 Jan 2011 09:42:12 -0000 Reply-To: radiusext@ops.ietf.org Subject: [radext] ipv6-access #62 (new): Use of "Address" Message-ID: <066.17eef1017064d45f1c34a9e0e44ff3f1@tools.ietf.org> #62: Use of "Address" Section 3.1 and 3.1: ... Address The Address field contains a 128-bit IPv6 address. I suggest using "IPv6 Address", as "address" is defined in RFC2865 as being for Ipv4 addressess. -- ---------------------------------------+------------------------------------ Reporter: aland@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: ipv6-access | Version: Severity: In WG Last Call | Keywords: ---------------------------------------+------------------------------------ Ticket URL: radext -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: Envelope-to: radiusext-data0@psg.com Delivery-date: Thu, 13 Jan 2011 09:41:59 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" Cc: radiusext@ops.ietf.org Auto-Submitted: auto-generated To: aland@deployingradius.com Date: Thu, 13 Jan 2011 09:41:06 -0000 Reply-To: radiusext@ops.ietf.org Subject: [radext] ipv6-access #61 (new): DNS attribute for IPv4? Message-ID: <066.cc2411f6b119d81f73eec60b018d6670@tools.ietf.org> #61: DNS attribute for IPv4? Section 2.2: ... Existing IETF Radius attributes convey DNS as 32- bit IPv4 addresses and cannot support a 128-bit IPv6 address. I'm unaware of any IETF specification which transports DNS server addresses in RADIUS. Is there a reference for this? -- ---------------------------------------+------------------------------------ Reporter: aland@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: ipv6-access | Version: Severity: In WG Last Call | Keywords: ---------------------------------------+------------------------------------ Ticket URL: radext -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: Envelope-to: radiusext-data0@psg.com Delivery-date: Thu, 13 Jan 2011 00:54:23 +0000 From: "Sanchez, Mauricio (HP Networking)" To: "radiusext@ops.ietf.org" CC: "Bernard Aboba (Bernard_Aboba@hotmail.com)" Date: Thu, 13 Jan 2011 00:46:55 +0000 Subject: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round) Thread-Topic: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round) Thread-Index: AcuyuykLx3yJZs1XTq2UohstnTZ92Q== Message-ID: <9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194@GVW0671EXC.americas.hpqcorp.net> Accept-Language: en-US Content-Language: en-US acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194GVW0671EXCame_" MIME-Version: 1.0 --_000_9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194GVW0671EXCame_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable This is an announcement of RADEXT WG second last call on "RADIUS attributes= for IPv6 Access Networks", prior to sending the document to the IESG for p= ublication as a proposed standard RFC. The first last call did not garner= any comments, whether positive or negative. If you read the draft and hav= e no issues, please state this as so on the mailing list. The document is available for inspection here: http://tools.ietf.org/wg/radext/draft-ietf-radext-ipv6-access/ This RADEXT WG last call will last until January 26, 2011. If you have co= mments on the document, please file using TRAC system. See below for summa= ry of instructions. Thanks, MS 1. To submit an issue in TRAC, you first need to login to the RADEXT = WG site on the tools server: http://tools.ietf.org/wg/radext/trac/login 2. If you don't already have a login ID, you can obtain one by naviga= ting to this site: http://trac.tools.ietf.org/newlogin 3. Once you have obtained an account, and have logged in, you can fil= e an issue by navigating to the ticket entry form: http://trac.tools.ietf.= org/wg/radext/trac/newticket 4. When opening an issue: a. The Type: field should be set to "defect" for an issue with the cu= rrent document text, or "enhancement" for a proposed addition of functional= ity (such as an additional requirement). b. The Priority: field is set based on the severity of the Issue. Fo= r example, editorial issues are typically "minor" or "trivial". c. The Milestone: field should be set to milestone1 (useless, I know)= . d. The Component: field should be set to the document you are filing t= he issue on. e. The Version: field should be set to "1.0". f. The Severity: field should be set to based on the status of the d= ocument (e.g. "In WG Last Call" for a document in WG last call) g. The Keywords: and CC: fields can be left blank unless inspiration= seizes you. h. The Assign To: field is generally filled in with the email address = of the editor. 5. Typically it won't be necessary to enclose a file with the ticket,= but if you need to, select "I have files to attach to this ticket". 6. If you want to preview your Issue, click on the "Preview" button. = When you're ready to submit the issue, click on the "Create Ticket" button= . 7. If you want to update an issue, go to the "View Tickets" page: htt= p://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the ticket # you = want to update, and then modify the ticket fields as required --_000_9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194GVW0671EXCame_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

This is an announcement of RADEXT WG second last call on "RADIUS attribut= es for IPv6 Access Networks", prior to sending the document to the IES= G for publication as a proposed standard RFC.   The first last ca= ll did not garner any comments, whether positive or negative.  If you = read the draft and have no issues, please state this as so on the mailing l= ist. 

The document is available for inspection here:<= /p>

http://tools.ietf.org/wg/ra= dext/draft-ietf-radext-ipv6-access/

This RADEXT WG last call will last until Jan= uary 26, 2011.   If you have comments on the document, please fil= e using TRAC system.  See below for summary of instructions.

Thanks,
MS

 <= /o:p>

1.  =      To submit an issue in TRAC, you first need to logi= n to the RADEXT WG site on the tools server:  http://tools.ietf.org/wg/radext/trac/login

2.       If you don’t alread= y have a login ID, you can obtain one by navigating to this site: &nbs= p; http://trac.tools.ietf.o= rg/newlogin

3.       Once you have= obtained an account, and have logged in, you can file an issue by navigati= ng to the  ticket entry form: http://trac.tools.ietf.org/wg/radext/trac/newticket=

4.       When opening an issue:
a.       The Type: field should be set = to “defect” for an issue with the current document text, or = 220;enhancement” for a proposed addition of functionality (such as an= additional requirement).
b.      The Priority= : field is set based on the severity of the Issue.   For example,= editorial issues are typically “minor” or “trivial”= ;.
c.       The Milestone: field should b= e set to milestone1 (useless, I know).
d.     = The Component: field should be set to the document you are filing the issu= e on. 
e.      The Version: field should = be set to “1.0”.
f.      &nbs= p; The Severity: field should be set to based on the status of the document= (e.g. “In WG Last Call” for a document in WG last call)
g.&= nbsp;       The Keywords: and CC: fields can = be left blank unless inspiration seizes you.
h.    =   The Assign To: field is generally filled in with the email address o= f the editor.

5.       Typically it w= on’t be necessary to enclose a file with the ticket, but if you need = to, select “I have files to attach to this ticket”.

6.&= nbsp;      If you want to preview your Issue, clic= k on the “Preview” button.  When you’re ready to sub= mit the issue, click on the “Create Ticket” button.

7.&= nbsp;      If you want to update an issue, go to t= he "View Tickets" page: http://trac.tools.ietf.org/wg/radext/trac/report/1  Click on the ticket # you want to update, and then modify the ticke= t fields as required

 <= /o:p>

= --_000_9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194GVW0671EXCame_-- -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: Envelope-to: radiusext-data0@psg.com Delivery-date: Mon, 10 Jan 2011 20:48:19 +0000 MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Cc: radiusext@ops.ietf.org Subject: I-D Action:draft-ietf-radext-ipv6-access-03.txt Message-ID: <20110110204501.5529.90484.idtracker@localhost> Date: Mon, 10 Jan 2011 12:45:01 -0800 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the RADIUS EXTensions Working Group of the IETF. Title : RADIUS attributes for IPv6 Access Networks Author(s) : B. Lourdelet, et al. Filename : draft-ietf-radext-ipv6-access-03.txt Pages : 14 Date : 2011-01-10 This document specifies IPv6 RADIUS attributes, which complement those of RFC3162, and are intended to be used in residential broadband networks, where specific user configuration information is expected to be passed as part of the AAA process between a NAS and an AAA server. The attributes cover the assignment or reporting of the following; a specific host IPv6 address; a recursive DNS IPv6 server address; a specific IPv6 route announced to a host; a named IPv6 delegated prefix pool to be used for assignments to an accessing host. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-radext-ipv6-access-03.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-radext-ipv6-access-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-01-10123459.I-D@ietf.org> --NextPart-- -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: