From owner-ietf-radius@livingston.com Wed Sep 13 17:14:44 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA17708 for ; Wed, 13 Sep 2000 17:14:43 -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 OAA19187; Wed, 13 Sep 2000 14:07:24 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/1.0) id NAA19001 for ietf-radius-outgoing; Wed, 13 Sep 2000 13:59:53 -0700 (PDT) X-Authentication-Warning: server.livingston.com: majordom set sender to owner-ietf-radius@livingston.com using -f Message-ID: <001d01c01db8$0f0270a0$dc4745ab@cisco.com> From: "Murtaza S. Chiba" To: Subject: (radius) Server initiated disconnect Date: Wed, 13 Sep 2000 13:23:12 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Murtaza S. Chiba" Content-Transfer-Encoding: 7bit Hi, This might have been discussed before so I apologize in advance. Basically, I know that Ascend (now Lucent) uses server initiated message to disconnect users. What I would like to know if this is a standard practice used by many vendors? If so what are the ports used to send these requests on? Thanks, Murtaza - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon Sep 18 11:49:12 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11939 for ; Mon, 18 Sep 2000 11:49:11 -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 IAA08437; Mon, 18 Sep 2000 08:41:20 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/1.0) id IAA00067 for ietf-radius-outgoing; Mon, 18 Sep 2000 08:40:58 -0700 (PDT) X-Authentication-Warning: server.livingston.com: majordom set sender to owner-ietf-radius@livingston.com using -f Message-Id: <4.3.2.7.2.20000918112436.00d6e9d0@ZBL6C008.corpeast.baynetworks.com> X-Sender: dmitton@ZBL6C008.corpeast.baynetworks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 18 Sep 2000 11:36:32 -0400 To: "Murtaza S. Chiba" , ietf-radius From: "David Mitton" Subject: Re: (radius) Server initiated disconnect In-Reply-To: <001d01c01db8$0f0270a0$dc4745ab@cisco.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" Hello Murtaza, This has not been discussed before here, as its outside of the RFC's described functions. I, personally, don't know any other vendors that implement this (other than us, and I don't know if that code is in general distribution). I think you asked the wrong question. The sending port does not matter, the NAS receiving port does. Ascend defaults to 1700 (according to the manual I'm looking at), but it's configurable. (See: Configuring the MAX TNT for RADIUS client requests, Specifying the UDP port) I don't know our default, it's probably 1645. Dave. At 9/13/00 01:23 PM -0600, Murtaza S. Chiba wrote: >Hi, > This might have been discussed before so I apologize in advance. > Basically, I know that Ascend (now Lucent) uses server initiated message >to disconnect users. What I would like to know if this is a standard >practice used by many vendors? > If so what are the ports used to send these requests on? > >Thanks, >Murtaza > >- >To unsubscribe, email 'majordomo@livingston.com' with >'unsubscribe ietf-radius' in the body of the message. --------------------------------------------------------------- David Mitton ESN: 248-4570 Advisor, Nortel Networks 978-288-4570 Direct ServiceWare, IP Mobility 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 Mon Sep 18 20:34:18 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA22036 for ; Mon, 18 Sep 2000 20:34:17 -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 RAA16605; Mon, 18 Sep 2000 17:26:56 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/1.0) id RAA26182 for ietf-radius-outgoing; Mon, 18 Sep 2000 17:30:37 -0700 (PDT) X-Authentication-Warning: server.livingston.com: majordom set sender to owner-ietf-radius@livingston.com using -f Message-ID: <39C6B2BE.1619EFF2@cisco.com> Date: Mon, 18 Sep 2000 17:26:38 -0700 From: Murtaza Chiba Organization: Cisco Systems, Inc. X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: David Mitton CC: ietf-radius Subject: Re: (radius) Server initiated disconnect References: <4.3.2.7.2.20000918112436.00d6e9d0@ZBL6C008.corpeast.baynetworks.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Murtaza Chiba Content-Transfer-Encoding: 7bit Hi David, Apart from Nortel, I know that we at Cisco also use it. At Cisco it is known as PoD (Packet of Disconnect). I have heard that 3Com uses a similar packet exchange and is referred to as the resource reclaim message. I was a bit ambiguous about which port I meant and you are right I meant the destination port, not the source port. I was curious if this was widely used, since the Merit servers also include an example client with their freeware distribution. If a lot more vendors are using this feature then I would be willing to document the practices. Maybe the Extended Practices draft would be a good place to detail it in? Thanks, Murtaza David Mitton wrote: > > Hello Murtaza, > > This has not been discussed before here, as its outside of the > RFC's described functions. > I, personally, don't know any other vendors that implement this > (other than us, and I don't know if that code is in general distribution). > > I think you asked the wrong question. The sending port does not > matter, the NAS receiving port does. Ascend defaults to 1700 (according to > the manual I'm looking at), but it's configurable. (See: Configuring the > MAX TNT for RADIUS client requests, Specifying the UDP port) > > I don't know our default, it's probably 1645. > > Dave. > > At 9/13/00 01:23 PM -0600, Murtaza S. Chiba wrote: > >Hi, > > This might have been discussed before so I apologize in advance. > > Basically, I know that Ascend (now Lucent) uses server initiated message > >to disconnect users. What I would like to know if this is a standard > >practice used by many vendors? > > If so what are the ports used to send these requests on? > > > >Thanks, > >Murtaza > > > >- > >To unsubscribe, email 'majordomo@livingston.com' with > >'unsubscribe ietf-radius' in the body of the message. > > --------------------------------------------------------------- > David Mitton ESN: 248-4570 > Advisor, Nortel Networks 978-288-4570 Direct > ServiceWare, IP Mobility 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 Sep 22 17:13:29 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA26579 for ; Fri, 22 Sep 2000 17:13:29 -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 OAA12679; Fri, 22 Sep 2000 14:05:52 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/1.0) id NAA10819 for ietf-radius-outgoing; Fri, 22 Sep 2000 13:59:15 -0700 (PDT) X-Authentication-Warning: server.livingston.com: majordom set sender to owner-ietf-radius@livingston.com using -f Message-Id: <4.3.2.7.2.20000922112157.00d69ab0@ZBL6C008.corpeast.baynetworks.com> X-Sender: dmitton@ZBL6C008.corpeast.baynetworks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 22 Sep 2000 11:35:19 -0400 To: Murtaza Chiba , "David Mitton" From: "David Mitton" Subject: Re: (radius) Server initiated disconnect Cc: ietf-radius In-Reply-To: <39C6B2BE.1619EFF2@cisco.com> References: <4.3.2.7.2.20000918112436.00d6e9d0@ZBL6C008.corpeast.baynetworks.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" Well, Murtaza, the NASreq Extended RADIUS Practices, RFC2882, is not intended to be a protocol reference document. It was an Informational snapshot of general practices and does not include sufficient detailed field or message exchange information for implementation. Also a particular vendor made it quite clear that he didn't want his products described by name or version number, and I have removed most of the attribution from the original draft document. As useful as it may be, the RADIUS WG (RIP) has never taken up documenting "practices" vs. the standard. And some vendors see no benefit in cooperating. That's not to say that it couldn't be done elsewhere, just not as a WG item. Dave. At 9/18/00 05:26 PM -0700, Murtaza Chiba wrote: >Hi David, > Apart from Nortel, I know that we at Cisco also use it. At Cisco > it is >known as PoD (Packet of Disconnect). I have heard that 3Com uses a >similar packet exchange and is referred to as the resource reclaim >message. > I was a bit ambiguous about which port I meant and you are right I >meant the destination port, not the source port. > I was curious if this was widely used, since the Merit servers also >include an example client with their freeware distribution. > If a lot more vendors are using this feature then I would be > willing to >document the practices. Maybe the Extended Practices draft would be a >good place to detail it in? > >Thanks, >Murtaza > >David Mitton wrote: > > > > Hello Murtaza, > > > > This has not been discussed before here, as its outside of the > > RFC's described functions. > > I, personally, don't know any other vendors that implement this > > (other than us, and I don't know if that code is in general distribution). > > > > I think you asked the wrong question. The sending port does not > > matter, the NAS receiving port does. Ascend defaults to 1700 (according to > > the manual I'm looking at), but it's configurable. (See: Configuring the > > MAX TNT for RADIUS client requests, Specifying the UDP port) > > > > I don't know our default, it's probably 1645. > > > > Dave. > > > > At 9/13/00 01:23 PM -0600, Murtaza S. Chiba wrote: > > >Hi, > > > This might have been discussed before so I apologize in advance. > > > Basically, I know that Ascend (now Lucent) uses server initiated > message > > >to disconnect users. What I would like to know if this is a standard > > >practice used by many vendors? > > > If so what are the ports used to send these requests on? > > > > > >Thanks, > > >Murtaza > > > > > >- > > >To unsubscribe, email 'majordomo@livingston.com' with > > >'unsubscribe ietf-radius' in the body of the message. > > > > --------------------------------------------------------------- > > David Mitton ESN: 248-4570 > > Advisor, Nortel Networks 978-288-4570 Direct > > ServiceWare, IP Mobility 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. --------------------------------------------------------------- David Mitton ESN: 248-4570 Advisor, Nortel Networks 978-288-4570 Direct ServiceWare, IP Mobility 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 Mon Sep 25 04:03:19 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA28505 for ; Mon, 25 Sep 2000 04:03:19 -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 AAA27665; Mon, 25 Sep 2000 00:55:32 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/1.0) id AAA23329 for ietf-radius-outgoing; Mon, 25 Sep 2000 00:54:55 -0700 (PDT) X-Authentication-Warning: server.livingston.com: majordom set sender to owner-ietf-radius@livingston.com using -f Message-ID: From: Klausberger Walter To: "'David Mitton'" , Murtaza Chiba Cc: ietf-radius Subject: AW: (radius) Server initiated disconnect Date: Mon, 25 Sep 2000 09:52:41 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-MIME-Autoconverted: from quoted-printable to 8bit by server.livingston.com id AAA23324 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Klausberger Walter X-MIME-Autoconverted: from 8bit to quoted-printable by bast.livingston.com id AAA27665 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA28505 Hi, We intend to implement a similar feature in our NAS, but I don't want to invent something totally new. Especially if there are already some implementations in the field. Thus, to document the practices would be a really good idea and I would be glad if Murtaza could do it in some way. with best regards Walter --------------------------------------------------------------- Walter Klausberger System Architecture Team Siemens AG Austria Phone: +43(5)1707-42683 Fax: +43(5)1707-55951 email: walter.klausberger@siemens.at -----Ursprüngliche Nachricht----- Von: David Mitton [mailto:dmitton@nortelnetworks.com] Gesendet am: Freitag, 22. September 2000 17:35 An: Murtaza Chiba; David Mitton Cc: ietf-radius Betreff: Re: (radius) Server initiated disconnect Well, Murtaza, the NASreq Extended RADIUS Practices, RFC2882, is not intended to be a protocol reference document. It was an Informational snapshot of general practices and does not include sufficient detailed field or message exchange information for implementation. Also a particular vendor made it quite clear that he didn't want his products described by name or version number, and I have removed most of the attribution from the original draft document. As useful as it may be, the RADIUS WG (RIP) has never taken up documenting "practices" vs. the standard. And some vendors see no benefit in cooperating. That's not to say that it couldn't be done elsewhere, just not as a WG item. Dave. At 9/18/00 05:26 PM -0700, Murtaza Chiba wrote: >Hi David, > Apart from Nortel, I know that we at Cisco also use it. At Cisco > it is >known as PoD (Packet of Disconnect). I have heard that 3Com uses a >similar packet exchange and is referred to as the resource reclaim >message. > I was a bit ambiguous about which port I meant and you are right I >meant the destination port, not the source port. > I was curious if this was widely used, since the Merit servers also >include an example client with their freeware distribution. > If a lot more vendors are using this feature then I would be > willing to >document the practices. Maybe the Extended Practices draft would be a >good place to detail it in? > >Thanks, >Murtaza > >David Mitton wrote: > > > > Hello Murtaza, > > > > This has not been discussed before here, as its outside of the > > RFC's described functions. > > I, personally, don't know any other vendors that implement this > > (other than us, and I don't know if that code is in general distribution). > > > > I think you asked the wrong question. The sending port does not > > matter, the NAS receiving port does. Ascend defaults to 1700 (according to > > the manual I'm looking at), but it's configurable. (See: Configuring the > > MAX TNT for RADIUS client requests, Specifying the UDP port) > > > > I don't know our default, it's probably 1645. > > > > Dave. > > > > At 9/13/00 01:23 PM -0600, Murtaza S. Chiba wrote: > > >Hi, > > > This might have been discussed before so I apologize in advance. > > > Basically, I know that Ascend (now Lucent) uses server initiated > message > > >to disconnect users. What I would like to know if this is a standard > > >practice used by many vendors? > > > If so what are the ports used to send these requests on? > > > > > >Thanks, > > >Murtaza > > > > > >- > > >To unsubscribe, email 'majordomo@livingston.com' with > > >'unsubscribe ietf-radius' in the body of the message. > > > > --------------------------------------------------------------- > > David Mitton ESN: 248-4570 > > Advisor, Nortel Networks 978-288-4570 Direct > > ServiceWare, IP Mobility 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. --------------------------------------------------------------- David Mitton ESN: 248-4570 Advisor, Nortel Networks 978-288-4570 Direct ServiceWare, IP Mobility 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.