From owner-ietf-radius@portmasters.com Thu Jan 31 15:18:19 2002 Received: from linux2.portmasters.com (root@ns2.jakes.org [216.138.104.67]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10910 for ; Thu, 31 Jan 2002 15:18:18 -0500 (EST) Received: (from majordomo@localhost) by linux2.portmasters.com (8.11.1/8.11.1) id g0VJvbR31367 for ietf-radius-outgoing; Thu, 31 Jan 2002 13:57:37 -0600 X-Authentication-Warning: linux2.portmasters.com: majordomo set sender to owner-ietf-radius@portmasters.com using -f From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: ietf-radius@portmasters.com Subject: (radius) draft-chiba-radius-dynamic-disconnect-00.txt Message-Id: Date: Thu, 31 Jan 2002 12:13:31 -0800 Sender: owner-ietf-radius@portmasters.com Precedence: bulk Reply-To: Randy Bush Content-Transfer-Encoding: 7bit This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-chiba-radius-dynamic-disconnect-00.txt. does anyone have issues with this? randy - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@portmasters.com Thu Jan 31 17:39:04 2002 Received: from linux2.portmasters.com (root@ns2.jakes.org [216.138.104.67]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14651 for ; Thu, 31 Jan 2002 17:38:58 -0500 (EST) Received: (from majordomo@localhost) by linux2.portmasters.com (8.11.1/8.11.1) id g0VML8n02896 for ietf-radius-outgoing; Thu, 31 Jan 2002 16:21:08 -0600 X-Authentication-Warning: linux2.portmasters.com: majordomo set sender to owner-ietf-radius@portmasters.com using -f From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bernard Aboba Cc: ietf-radius@portmasters.com Subject: Re: (radius) draft-chiba-radius-dynamic-disconnect-00.txt References: Message-Id: Date: Thu, 31 Jan 2002 14:36:40 -0800 Sender: owner-ietf-radius@portmasters.com Precedence: bulk Reply-To: Randy Bush Content-Transfer-Encoding: 7bit > Here's the quote from section 6.2 of RFC 2865: > > "Packet Type Coes have a range from 1 to 254, of which 1-5, 11-13 have > been allocated. Because a new Packet Type has considerable impact on > interoperability, a new Packet Type Code requires Standards Action, and > should be allocated starting at 14." thank you! randy - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@portmasters.com Thu Jan 31 20:37:17 2002 Received: from linux2.portmasters.com (root@ns2.jakes.org [216.138.104.67]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17138 for ; Thu, 31 Jan 2002 20:37:13 -0500 (EST) Received: (from majordomo@localhost) by linux2.portmasters.com (8.11.1/8.11.1) id g111JP705855 for ietf-radius-outgoing; Thu, 31 Jan 2002 19:19:25 -0600 X-Authentication-Warning: linux2.portmasters.com: majordomo set sender to owner-ietf-radius@portmasters.com using -f From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: ietf-radius@portmasters.com Cc: mchiba@cisco.com, gdommety@cisco.com, meklund@cisco.com, david@mitton.com Subject: (radius) Re: draft-chiba-radius-dynamic-disconnect-00.txt References: Message-Id: Date: Thu, 31 Jan 2002 17:35:01 -0800 Sender: owner-ietf-radius@portmasters.com Precedence: bulk Reply-To: Randy Bush Content-Transfer-Encoding: 7bit > Here's the quote from section 6.2 of RFC 2865: > > "Packet Type Coes have a range from 1 to 254, of which 1-5, 11-13 have > been allocated. Because a new Packet Type has considerable impact on > interoperability, a new Packet Type Code requires Standards Action, and > should be allocated starting at 14." given the above, what do the authors wish to do with this document? and, if the authors were to propose this as a standards action, would anyone on this list think that technical objections might be raised? randy - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe ietf-radius' in the body of the message.