From owner-ietf-radius@livingston.com Thu May 4 09:32:56 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05858 for ; Thu, 4 May 2000 09:32:55 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id GAA02711; Thu, 4 May 2000 06:28:15 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id GAA29522 for ietf-radius-outgoing; Thu, 4 May 2000 06:25:33 -0700 (PDT) Message-ID: <392A357CE6FFD111AC3E00A0C99848B003694D40@hdsmsx31.hd.intel.com> From: "Shriver, John" To: "'ietf-radius@livingston.com'" Cc: "Shriver, John" Subject: (radius) comments on Date: Thu, 4 May 2000 06:24:05 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Shriver, John" (Please keep me in the CC: list, I'm not on the list. Enough lists!) When draft-ietf-radius-eap-xx.txt was merged into draft-ietf-radius-ext-00.txt, in the section on EAP-Message, the drawing and text describing what part of the EAP packet goes into the AVP was not included. Thus, there is now no discussion of what part of the EAP packet goes into "String". Also, "String" is a very misleading name for the data portion of this AVP, since it's really a packet. I'd say that "Packet", or "Message" would be a better name. Finally, we should discuss who owns the Identifier field of the encapsulated EAP packet. I presume that the EAP Authenticator (PPP Authenticator) has the last say, since these are the unique identifiers for its retransmissions. I would suggest that the text should read as follows, which avoids mentioning PPP to prevent any conflict with IEEE 802.1x's use of EAP and RADIUS: A summary of the EAP-Message attribute format is shown below. The fields are transmitted from left to right. 0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Message... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type 79 for EAP-Message. Length >= 3 Message The Message field contains EAP packets, as defined in [3]. The Message field MUST start with the Code field of the EAP packet, and will include all the data. The Message field MUST NOT include any PPP data-link padding that had been part of the EAP packet when received by the RADIUS authenticator. If multiple EAP-Message attributes are present in a received RADIUS packet their values MUST be concatenated; this allows EAP packets longer than 253 octets to be passed by RADIUS. Similarly, EAP packets longer than 253 octets MUST be fragmented into multiple EAP-Message attributes before transmission over RADIUS. The Identifier field of the EAP packet is the responsibility of the EAP authenticator, not the RADIUS server. The EAP authenticator MUST ensure that the Identifier field has a different value from the previous one sent, since the RADIUS server may not have used a unique value. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Thu May 4 09:35:21 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05891 for ; Thu, 4 May 2000 09:35:21 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id GAA02944; Thu, 4 May 2000 06:31:09 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id GAA29727 for ietf-radius-outgoing; Thu, 4 May 2000 06:31:59 -0700 (PDT) Message-ID: <392A357CE6FFD111AC3E00A0C99848B003694D42@hdsmsx31.hd.intel.com> From: "Shriver, John" To: "'ietf-radius@livingston.com'" Subject: (radius) comments are on draft-ietf-radius-ext-07.txt Date: Thu, 4 May 2000 06:30:37 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Shriver, John" The comments I just sent are on draft-ietf-radius-ext-07.txt. Forgot to finish the subject line... - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Thu May 4 11:16:16 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08003 for ; Thu, 4 May 2000 11:16:15 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id IAA10258; Thu, 4 May 2000 08:12:00 -0700 (PDT) Received: by server.livingston.com (8.9.3/8.9.3/0.5) id IAA05972 for ietf-radius-outgoing; Thu, 4 May 2000 08:11:06 -0700 (PDT) Message-Id: <4.2.2.20000504105852.00d6dda0@ZBL6C008.corpeast.baynetworks.com> X-Sender: dmitton@ZBL6C008.corpeast.baynetworks.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 04 May 2000 11:01:34 -0400 To: "'ietf-radius@livingston.com'" From: "David Mitton" Subject: Re: (radius) comments are on draft-ietf-radius-ext-07.txt In-Reply-To: <392A357CE6FFD111AC3E00A0C99848B003694D42@hdsmsx31.hd.intel .com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "David Mitton" I'm curious how many RADIUS servers have implementations of EAP support out there? And how many are compatible with Windows 2000? I guess the follow up question is, if not, then what clients do you support? Dave. --------------------------------------------------------------- David Mitton ESN: 248-4570 Advisor, Nortel Networks 978-288-4570 Direct Carrier Packet Solutions, Preside 978-288-3030 FAX Billerica, MA 01821 dmitton@nortelnetworks.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri May 5 21:18:43 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02159 for ; Fri, 5 May 2000 21:18:42 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id SAA22034; Fri, 5 May 2000 18:14:18 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id SAA24555 for ietf-radius-outgoing; Fri, 5 May 2000 18:12:41 -0700 (PDT) From: "Bernard Aboba" To: "'David Mitton'" , Cc: , Subject: RE: (radius) comments are on draft-ietf-radius-ext-07.txt Date: Fri, 5 May 2000 18:13:48 -0700 Message-ID: <009101bfb6f8$56a8a220$428939cc@ntdev.microsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <4.2.2.20000504105852.00d6dda0@ZBL6C008.corpeast.baynetworks.com> X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Bernard Aboba" Content-Transfer-Encoding: 7bit In general, it's probably time to do an assessment of EAP implementations for draft standards submission. We should probably do the EAP/RADIUS assessment as part of that. -----Original Message----- From: owner-ietf-radius@livingston.com [mailto:owner-ietf-radius@livingston.com]On Behalf Of David Mitton Sent: Thursday, May 04, 2000 8:02 AM To: 'ietf-radius@livingston.com' Subject: Re: (radius) comments are on draft-ietf-radius-ext-07.txt I'm curious how many RADIUS servers have implementations of EAP support out there? And how many are compatible with Windows 2000? I guess the follow up question is, if not, then what clients do you support? Dave. --------------------------------------------------------------- David Mitton ESN: 248-4570 Advisor, Nortel Networks 978-288-4570 Direct Carrier Packet Solutions, Preside 978-288-3030 FAX Billerica, MA 01821 dmitton@nortelnetworks.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon May 8 14:33:32 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14607 for ; Mon, 8 May 2000 14:33:31 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA12817; Mon, 8 May 2000 11:24:00 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id LAA03295 for ietf-radius-outgoing; Mon, 8 May 2000 11:21:31 -0700 (PDT) Message-Id: <200005081809.OAA14083@ietf.org> To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: ietf-radius@livingston.com From: The IESG Subject: (radius) Protocol Action: Remote Authentication Dial In User Service (RADIUS) to Draft Standard Date: Mon, 08 May 2000 14:09:30 -0400 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: The IESG The IESG has approved the Internet-Draft 'Remote Authentication Dial In User Service (RADIUS)' as a Draft Standard, replacing RFC2138. This document is the product of the Remote Authentication Dial-In User Service Working Group. The IESG contact persons are Bert Wijnen and Randy Bush. Technical Summary This document describes a widely deployed protocol for carrying user authentication, authorization, and configuration information between a network access server which desires to authenticate its links and a usually shared authentication server. Working Group Summary Working group review had no significant technical dissent. Protocol Quality The document was reviewed by Randy Bush. Note to RFC Editor: The IESG requests the following text be added as an IESG Note: This protocol is widely implemented and used. Experience has shown that it can suffer degraded performance and lost data when used in large scale systems, in part because it does not include provisions for congestion control. Readers of this document may find it beneficial to track the progress of the IETF's AAA working group, which may develop a successor protocol that better addresses the scaling and congestion control issues. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon May 8 14:40:00 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14802 for ; Mon, 8 May 2000 14:39:59 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA13121; Mon, 8 May 2000 11:34:37 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id LAA04173 for ietf-radius-outgoing; Mon, 8 May 2000 11:34:15 -0700 (PDT) Message-Id: <200005081826.OAA14348@ietf.org> To: IETF-Announce: ; Cc: RFC Editor , iana@iana.org Cc: Internet Architecture Board Cc: ietf-radius@livingston.com From: The IESG Subject: (radius) Document Action: RADIUS Accounting to Informational Date: Mon, 08 May 2000 14:26:24 -0400 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: The IESG The IESG has approved the Internet-Draft 'RADIUS Accounting' as an Informational RFC. This document replaces RFC2139, This document is the product of the Remote Authentication Dial-In User Service Working Group. The IESG contact persons are Bert Wijnen and Randy Bush. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon May 8 14:42:36 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14882 for ; Mon, 8 May 2000 14:42:35 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA13123; Mon, 8 May 2000 11:34:37 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id LAA04180 for ietf-radius-outgoing; Mon, 8 May 2000 11:34:17 -0700 (PDT) Message-Id: <200005081826.OAA14357@ietf.org> To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: ietf-radius@livingston.com From: The IESG Subject: (radius) Document Action: RADIUS Extensions to Informational Date: Mon, 08 May 2000 14:26:30 -0400 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: The IESG The IESG has approved the Internet-Draft 'RADIUS Extensions' as an Informational RFC. This document is the product of the Remote Authentication Dial-In User Service Working Group. The IESG contact persons are Bert Wijnen and Randy Bush. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon May 8 15:04:48 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15668 for ; Mon, 8 May 2000 15:04:48 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA13835; Mon, 8 May 2000 11:55:20 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id LAA05556 for ietf-radius-outgoing; Mon, 8 May 2000 11:53:33 -0700 (PDT) Message-Id: <200005081837.OAA14758@ietf.org> To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: ietf-radius@livingston.com From: The IESG Subject: (radius) Document Action: RADIUS Attributes for Tunnel Protocol Support to Informational Date: Mon, 08 May 2000 14:37:26 -0400 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: The IESG The IESG has approved the Internet-Draft 'RADIUS Attributes for Tunnel Protocol Support' as an Informational RFC. This document is the product of the Remote Authentication Dial-In User Service Working Group. The IESG contact persons are Bert Wijnen and Randy Bush. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon May 8 15:08:02 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15667 for ; Mon, 8 May 2000 15:04:48 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA13839; Mon, 8 May 2000 11:55:24 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id LAA05568 for ietf-radius-outgoing; Mon, 8 May 2000 11:53:37 -0700 (PDT) Message-Id: <200005081837.OAA14768@ietf.org> To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: ietf-radius@livingston.com From: The IESG Subject: (radius) Document Action: RADIUS Accounting Modifications for Tunnel Protocol Support to Informational Date: Mon, 08 May 2000 14:37:33 -0400 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: The IESG The IESG has approved the Internet-Draft 'RADIUS Accounting Modifications for Tunnel Protocol Support' as an Informational RFC. This document is the product of the Remote Authentication Dial-In User Service Working Group. The IESG contact persons are Bert Wijnen and Randy Bush. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri May 26 10:36:13 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16601 for ; Fri, 26 May 2000 10:36:12 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id HAA09479; Fri, 26 May 2000 07:31:13 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id HAA22328 for ietf-radius-outgoing; Fri, 26 May 2000 07:27:36 -0700 (PDT) From: "Darran Potter" To: "Ietf-Radius@Livingston.Com" Subject: (radius) IPv6 Date: Fri, 26 May 2000 15:20:59 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Darran Potter" Content-Transfer-Encoding: 7bit I havent seen anything on IPv6 since a mail from Carl Rigney last year stating that it was not part of the Radius scope at that time. Have there been any updates to this position? ______________________________ Darran Potter - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri May 26 14:31:58 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22598 for ; Fri, 26 May 2000 14:31:57 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA13665; Fri, 26 May 2000 11:27:12 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id LAA03648 for ietf-radius-outgoing; Fri, 26 May 2000 11:26:01 -0700 (PDT) From: "Bernard Aboba" To: "'Darran Potter'" , "'Ietf-Radius@Livingston.Com'" Subject: RE: (radius) IPv6 Date: Fri, 26 May 2000 11:30:57 -0700 Message-ID: <002601bfc740$8975db20$428939cc@ntdev.microsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4131.1600 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Bernard Aboba" Content-Transfer-Encoding: 7bit Not that I'm aware of. There are two separate issues -- IPv6 transport and ability of RADIUS to carry IPv6 attributes. In terms of the latter, I'm curious as to what changes are necessary. The PPP over IPv6CP draft specifies a way to transmit the interface identifier using IPv6CP. So we'd need a RADIUS attribute for that. I've also thought that a prefix AVP is needed, so as to tell the NAS what to send in a router advertisement. Then there AVPs like NAS-IPAddress that need to be updated to 128-bit addresses from 32-bit addresses. And then there is the MIB which is IPv4 centric. Is this the extent of the changes that would be needed? -----Original Message----- From: owner-ietf-radius@livingston.com [mailto:owner-ietf-radius@livingston.com]On Behalf Of Darran Potter Sent: Friday, May 26, 2000 7:21 AM To: Ietf-Radius@Livingston.Com Subject: (radius) IPv6 I havent seen anything on IPv6 since a mail from Carl Rigney last year stating that it was not part of the Radius scope at that time. Have there been any updates to this position? ______________________________ Darran Potter - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri May 26 16:38:17 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25152 for ; Fri, 26 May 2000 16:38:16 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id NAA15427; Fri, 26 May 2000 13:32:19 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id NAA08964 for ietf-radius-outgoing; Fri, 26 May 2000 13:31:09 -0700 (PDT) Date: Fri, 26 May 2000 13:31:07 -0700 (PDT) From: Carl Rigney Message-Id: <200005262031.NAA08957@server.livingston.com> To: ietf-radius@livingston.com Subject: RE: (radius) IPv6 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Carl Rigney > Then there AVPs like NAS-IPAddress that need to be updated > to 128-bit addresses from 32-bit addresses. I thought IPv6 was downplaying using IP addresses to identify things? So NAS-Identifier should probably be used instead of adding a NAS-IP6-Address attribute. (Of course, if someone wants to use their IPv6 address as their NAS-Identifier, that works.) Any other changes needed besides the ones Bernard mentioned? It's reasonable to do a RADIUS for IPv6 draft. Anyone want to volunteer? I'm willing to write that draft (although if someone else really wants to and has the time, I'd be glad to foist that off), but I'd rather not deal with the MIBs, are the MIB authors willing to do IPv6 flavors of the MIBs? -- Carl Rigney RADIUS WG Chair cdr@livingston.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri May 26 18:50:21 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27246 for ; Fri, 26 May 2000 18:50:20 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id PAA16965; Fri, 26 May 2000 15:45:37 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id PAA13825 for ietf-radius-outgoing; Fri, 26 May 2000 15:45:45 -0700 (PDT) From: "Glen Zorn" To: "Carl Rigney" , Subject: RE: (radius) IPv6 Date: Fri, 26 May 2000 15:28:22 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <200005262031.NAA08957@server.livingston.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Glen Zorn" Content-Transfer-Encoding: 7bit ... > It's reasonable to do a RADIUS for IPv6 draft. Anyone want to > volunteer? I'm willing to write that draft (although if someone else > really wants to and has the time, I'd be glad to foist that off), but > I'd rather not deal with the MIBs, are the MIB authors willing to do > IPv6 flavors of the MIBs? We're just waiting for the IPv6MIB Design Team to finish their work. > > -- > Carl Rigney > RADIUS WG Chair > cdr@livingston.com > - > To unsubscribe, email 'majordomo@livingston.com' with > 'unsubscribe ietf-radius' in the body of the message. > > - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Sat May 27 11:43:06 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19136 for ; Sat, 27 May 2000 11:43:06 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id IAA21427; Sat, 27 May 2000 08:38:24 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id IAA29750 for ietf-radius-outgoing; Sat, 27 May 2000 08:36:20 -0700 (PDT) From: "Bernard Aboba" To: "'Carl Rigney'" , Subject: RE: (radius) IPv6 Date: Sat, 27 May 2000 08:41:43 -0700 Message-ID: <000601bfc7f2$0feb11a0$428939cc@ntdev.microsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <200005262031.NAA08957@server.livingston.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4131.1600 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Bernard Aboba" Content-Transfer-Encoding: 7bit >I thought IPv6 was downplaying using IP addresses to identify things? IPv6 addresses are larger and therefore more unwieldy to type in by hand, but that doesn't mean that they aren't to be used in protocols. >So NAS-Identifier should probably be used instead of adding a >NAS-IP6-Address attribute. I'd make the NAS-IP6-Attribute available and wouldn't change the spec language. >It's reasonable to do a RADIUS for IPv6 draft. Anyone want to >volunteer? I'll volunteer. >Are the MIB authors willing to do IPv6 flavors of the MIBs? Once the IPv6 spec is done, yes. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue May 30 05:30:35 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22323 for ; Tue, 30 May 2000 05:30:34 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id CAA07228; Tue, 30 May 2000 02:25:36 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id CAA19884 for ietf-radius-outgoing; Tue, 30 May 2000 02:25:01 -0700 (PDT) From: "Darran Potter" To: "'Ietf-Radius@Livingston.Com'" Subject: RE: (radius) IPv6 Date: Tue, 30 May 2000 10:18:06 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <002601bfc740$8975db20$428939cc@ntdev.microsoft.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Darran Potter" Content-Transfer-Encoding: 7bit Thanks for the responses... really just wanted to check I hadnt missed anything. Darran -----Original Message----- From: Bernard Aboba [mailto:aboba@internaut.com] Sent: 26 May 2000 19:31 To: 'Darran Potter'; 'Ietf-Radius@Livingston.Com' Subject: RE: (radius) IPv6 Not that I'm aware of. There are two separate issues -- IPv6 transport and ability of RADIUS to carry IPv6 attributes. In terms of the latter, I'm curious as to what changes are necessary. The PPP over IPv6CP draft specifies a way to transmit the interface identifier using IPv6CP. So we'd need a RADIUS attribute for that. I've also thought that a prefix AVP is needed, so as to tell the NAS what to send in a router advertisement. Then there AVPs like NAS-IPAddress that need to be updated to 128-bit addresses from 32-bit addresses. And then there is the MIB which is IPv4 centric. Is this the extent of the changes that would be needed? -----Original Message----- From: owner-ietf-radius@livingston.com [mailto:owner-ietf-radius@livingston.com]On Behalf Of Darran Potter Sent: Friday, May 26, 2000 7:21 AM To: Ietf-Radius@Livingston.Com Subject: (radius) IPv6 I havent seen anything on IPv6 since a mail from Carl Rigney last year stating that it was not part of the Radius scope at that time. Have there been any updates to this position? ______________________________ Darran Potter - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue May 30 10:36:38 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29896 for ; Tue, 30 May 2000 10:36:38 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id HAA09830; Tue, 30 May 2000 07:30:29 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id HAA24651 for ietf-radius-outgoing; Tue, 30 May 2000 07:31:32 -0700 (PDT) Message-Id: <4.3.1.2.20000530101747.00a8e960@ZBL6C008.corpeast.baynetworks.com> X-Sender: dmitton@ZBL6C008.corpeast.baynetworks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Tue, 30 May 2000 10:21:07 -0400 To: Bernard Aboba , "'Carl Rigney'" , ietf-radius From: "David Mitton" Subject: RE: (radius) IPv6 In-Reply-To: <000601bfc7f2$0feb11a0$428939cc@ntdev.microsoft.com> References: <200005262031.NAA08957@server.livingston.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "David Mitton" For attributes of the type "ipaddr", is it reasonable to propose length sensitive processing/upgrading? Instead of creating duplicate attribute (and using more constrainted code space) That is ipaddr attributes of length = 6 are IPv4, attributes of length = x+2 are IPv6. (set x appropriately) Dave. At 08:41 AM 5/27/00 -0700, Bernard Aboba wrote: > >I thought IPv6 was downplaying using IP addresses to identify things? > >IPv6 addresses are larger and therefore more unwieldy to >type in by hand, but that doesn't mean that they aren't to >be used in protocols. > > >So NAS-Identifier should probably be used instead of adding a > >NAS-IP6-Address attribute. > >I'd make the NAS-IP6-Attribute available and wouldn't change >the spec language. > > >It's reasonable to do a RADIUS for IPv6 draft. Anyone want to > >volunteer? > >I'll volunteer. > > >Are the MIB authors willing to do IPv6 flavors of the MIBs? > >Once the IPv6 spec is done, yes. >- >To unsubscribe, email 'majordomo@livingston.com' with >'unsubscribe ietf-radius' in the body of the message. --------------------------------------------------------------- David Mitton ESN: 248-4570 Consulting Engineer, Nortel Networks 978-288-4570 Direct Carrier Packet Solutions, Preside 978-288-3030 FAX Billerica, MA 01821 dmitton@nortelnetworks.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue May 30 14:15:26 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06142 for ; Tue, 30 May 2000 14:15:25 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA15012; Tue, 30 May 2000 11:05:20 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id LAA05569 for ietf-radius-outgoing; Tue, 30 May 2000 11:06:35 -0700 (PDT) Date: Tue, 30 May 2000 11:06:31 -0700 (PDT) From: Carl Rigney Message-Id: <200005301806.LAA05559@server.livingston.com> To: aboba@internaut.com, cdr@livingston.com, dmitton@nortelnetworks.com, ietf-radius@livingston.com Subject: RE: (radius) IPv6 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Carl Rigney I'd rather add attributes with a new type, since there are only a handful of those, than break all existing RADIUS servers by adding the concept of length sensitive processing. -- Carl Rigney - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed May 31 00:59:24 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18439 for ; Wed, 31 May 2000 00:59:23 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id VAA23447; Tue, 30 May 2000 21:54:36 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id VAA06655 for ietf-radius-outgoing; Tue, 30 May 2000 21:54:28 -0700 (PDT) Date: Tue, 30 May 2000 21:54:25 -0700 (PDT) From: Carl Rigney Message-Id: <200005310454.VAA06649@server.livingston.com> To: bwijnen@lucent.com Subject: RE: (radius) IPv6 Cc: ietf-radius@livingston.com Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Carl Rigney We've got 10 months left to move the standards track drafts to their final fates, so we should able to complete a IPv6 document before then. -- Carl - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed May 31 01:07:36 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18829 for ; Wed, 31 May 2000 01:07:35 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id WAA23687; Tue, 30 May 2000 22:02:50 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id WAA06949 for ietf-radius-outgoing; Tue, 30 May 2000 22:03:25 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Carl Rigney Cc: bwijnen@lucent.com, ietf-radius@livingston.com Subject: RE: (radius) IPv6 References: <200005310454.VAA06649@server.livingston.com> Message-Id: Date: Tue, 30 May 2000 22:02:35 -0700 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Randy Bush Content-Transfer-Encoding: 7bit > We've got 10 months left to move the standards track drafts to their final > fates, so we should able to complete a IPv6 document before then. we? the radius wg is closed. just waiting for the rfcs to drop to make it final. randy - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed May 31 19:40:37 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27442 for ; Wed, 31 May 2000 19:40:36 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id QAA10713; Wed, 31 May 2000 16:35:47 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id QAA17672 for ietf-radius-outgoing; Wed, 31 May 2000 16:34:20 -0700 (PDT) Message-Id: <4.2.2.20000531182910.00db77d0@ZBL6C008.corpeast.baynetworks.com> X-Sender: dmitton@ZBL6C008.corpeast.baynetworks.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 31 May 2000 18:44:12 -0400 To: Carl Rigney , aboba@internaut.com, cdr@livingston.com, "David Mitton" , ietf-radius@livingston.com From: "David Mitton" Subject: RE: (radius) IPv6 In-Reply-To: <200005301806.LAA05559@server.livingston.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "David Mitton" At 11:06 AM 5/30/00 -0700, Carl Rigney wrote: >I'd rather add attributes with a new type, since there are only a handful of >those, than break all existing RADIUS servers by adding the concept of length >sensitive processing. > >-- >Carl Rigney While I think that's a fair enough decision.... ... I'm concerned about the concept of non-six byte ipaddr attributes "breaking" existing servers. While they may not understand the value, I would hope that; a) they would check the length and realize the attribute value received is not-as-expected for the data type (by their implementation timeframe) b) ignore the attribute value c) perhaps flag or log the problem d) not reject the whole message (though they might per earlier interpretations of the RADIUS message processing rules) None of these consequences would be really unusual, as operationally the client and server must converge on a mutually understood set of attributes anyways. Going a step further, I think primarily NAS-IP-Address would be client generated. (and Framed-IP-Address if the address was user or NAS chosen) Most other ipaddr values would be in a server return profile to start with. Older servers would not be able to encode these values, and therefore would not interoperate with a hypothetical IPv6 RADIUS-speaking NAS. So I guess that's sort of a rationale for new attributes. However if they are anything other than ASCII\\\\\ UTF-8 strings there is something new here to be implemented anyways. Dave. --------------------------------------------------------------- David Mitton ESN: 248-4570 Advisor, Nortel Networks 978-288-4570 Direct Carrier Packet Solutions, IP Mobility 978-288-???? FAX Billerica, MA 01821 dmitton@nortelnetworks.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message.