From pppext-bounces@ietf.org Fri Sep 09 07:48:35 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDhMx-0007mA-4u; Fri, 09 Sep 2005 07:48:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDVqa-0000L4-3k for pppext@megatron.ietf.org; Thu, 08 Sep 2005 19:30:24 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05258 for ; Thu, 8 Sep 2005 19:30:20 -0400 (EDT) Received: from rt.icann.org ([192.0.34.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDVu1-0006qh-25 for pppext@ietf.org; Thu, 08 Sep 2005 19:33:59 -0400 Received: from rt.icann.org (localhost.icann.org [127.0.0.1]) by rt.icann.org (8.13.1/8.13.1) with ESMTP id j88NUBK5037585 for ; Thu, 8 Sep 2005 16:30:11 -0700 (PDT) (envelope-from www@rt.icann.org) Received: (from www@localhost) by rt.icann.org (8.13.1/8.13.1/Submit) id j88NUBV2037584; Thu, 8 Sep 2005 16:30:11 -0700 (PDT) (envelope-from www) Date: Thu, 8 Sep 2005 16:30:11 -0700 (PDT) From: "Michelle Cotton via RT" In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.icann.org RT-Ticket: rt.icann.org #3528 Managed-by: RT 3.2.2 (http://www.bestpractical.com/rt/) RT-Originator: michelle.cotton@icann.org Cc: pppext@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 X-Mailman-Approved-At: Fri, 09 Sep 2005 07:48:33 -0400 Subject: [Pppext] [rt.icann.org #3528] FW: General Request for Assignments (ppp-numbers) X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Reply-To: iana-prot-param@icann.org List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org Attn: PPPEXT Working Group The IANA has received the below request for a PPP ECP configuration option type. The registry can be found at the following: http://www.iana.org/assignments/ppp-numbers We are forwarding this to the working group for an expert review as this was suggested by our IANA official PPP expert. Can we please have the WG Chair respond to the IANA on what the consensus is and how the IANA should move forward? Thank you, Michelle Cotton IANA > > -----Original Message----- > From: Mohamedali.sfaxi@unil.ch [mailto:Mohamedali.sfaxi@unil.ch] > Sent: Wednesday, August 03, 2005 4:46 AM > To: iana@iana.org; Mohamedali.sfaxi@unil.ch > Subject: General Request for Assignments > > Contact Name : > Mohamed Ali SFAXI > > Contact Email : > Mohamedali.sfaxi@unil.ch > > Type of Assignment : > BB84 Quantum key distribution (QKD) > > Registry : > PPP ECP configuration option type > > Description : > The ECP (in PPP) gives the possibility to select the encryption algorithm > and its parameters. This ensures the confidentiality and the integrity of > the PPP frame. The weakness of this use resides in the way of generating and > exchanging the encryption key. In fact, for all the encryption algorithms > the secret key is assumed to be already shared between the communicating > parties. Using QKD, the two linked nodes exchange the secret key and > because of the use of the quantum technologies, this exchange is > unconditional secure. > > Additional Info : > BB84 : Bennet, C; Brassard, G (1984). IEEE International Conference on > Computers, Systems,and Signal Processing. IEEE Press, LOS ALAMITOS Mayers, D > (1998). "Unconditionnal Security in Quantum Cryptography". J. Assoc.Comput. > Math. 48, 351 > > > > _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Fri Sep 09 08:02:01 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDhZx-000237-Fp; Fri, 09 Sep 2005 08:02:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDhZu-00022o-8b for pppext@megatron.ietf.org; Fri, 09 Sep 2005 08:01:58 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27017 for ; Fri, 9 Sep 2005 08:01:55 -0400 (EDT) Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDhdN-0007og-Rq for pppext@ietf.org; Fri, 09 Sep 2005 08:05:38 -0400 Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id j89C1kDB025526 for ; Fri, 9 Sep 2005 06:01:46 -0600 (MDT) Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143]) by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL, v2.2) with ESMTP id j89C1jUj024867 for ; Fri, 9 Sep 2005 08:01:45 -0400 (EDT) Received: from phorcys.East.Sun.COM (localhost [127.0.0.1]) by phorcys.East.Sun.COM (8.13.4+Sun/8.13.4) with ESMTP id j89C1jqS010507 for ; Fri, 9 Sep 2005 08:01:45 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.East.Sun.COM (8.13.4+Sun/8.13.4/Submit) id j89C1j4d010504; Fri, 9 Sep 2005 08:01:45 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17185.31145.738118.436622@gargle.gargle.HOWL> Date: Fri, 9 Sep 2005 08:01:45 -0400 From: James Carlson To: pppext@ietf.org Subject: Re: [Pppext] [rt.icann.org #3528] FW: General Request for Assignments (ppp-numbers) In-Reply-To: Michelle Cotton via RT's message of 8 September 2005 16:30:11 References: X-Mailer: VM 7.01 under Emacs 21.3.1 X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: 7bit X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org Michelle Cotton via RT writes: > The IANA has received the below request for a PPP ECP configuration > option type. The registry can be found at the following: > http://www.iana.org/assignments/ppp-numbers Unfortunately, Vern's RFC 3818 doesn't cover ECP assignments, so it appears we're still stuck with expert review. That means we need to discuss it here and report consensus back. > > parties. Using QKD, the two linked nodes exchange the secret key and > > because of the use of the quantum technologies, this exchange is > > unconditional secure. I read through BB84, and it appears to be a key-exchange protocol, not an encryption algorithm. Also, it appears to work only with direct access to physical media and not with the regular bit stream that PPP itself requires. Thus, I suspect it may not be really appropriate as an ECP option, though I suppose it may open up a possibly interesting discussion about whether we *should* talk about key distribution as an ECP option. (Whether of the ordinary algorithmic sort, or the more hand-wavy x-files area-51 "quantum" sort.) -- James Carlson, KISS Network Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Fri Sep 09 09:54:16 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDjKa-0001Ff-HM; Fri, 09 Sep 2005 09:54:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDjKY-0001Ee-00 for pppext@megatron.ietf.org; Fri, 09 Sep 2005 09:54:14 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02316 for ; Fri, 9 Sep 2005 09:54:12 -0400 (EDT) Received: from calcite.rhyolite.com ([192.188.61.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDjO7-0002MG-Fb for pppext@ietf.org; Fri, 09 Sep 2005 09:57:56 -0400 Received: from calcite.rhyolite.com (localhost [127.0.0.1]) by calcite.rhyolite.com (8.13.4/8.13.4) with ESMTP id j89Drr4v026817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) env-from ; Fri, 9 Sep 2005 07:53:53 -0600 (MDT) Received: (from vjs@localhost) by calcite.rhyolite.com (8.13.4/8.13.4/Submit) id j89Drrxb026816; Fri, 9 Sep 2005 07:53:53 -0600 (MDT) Date: Fri, 9 Sep 2005 07:53:53 -0600 (MDT) From: Vernon Schryver Message-Id: <200509091353.j89Drrxb026816@calcite.rhyolite.com> To: pppext@ietf.org Subject: Re: [Pppext] [rt.icann.org #3528] FW: General Request for Assignments (ppp-numbers) In-Reply-To: <17185.31145.738118.436622@gargle.gargle.HOWL> X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Cc: iana-prot-param@icann.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org > From: James Carlson > Unfortunately, Vern's RFC 3818 doesn't cover ECP assignments, so it > appears we're still stuck with expert review. That means we need to > discuss it here and report consensus back. My now vague recollections are that 3818 does not mention ECP because a similar document was advanced specifically for ECP. I can't seem to find it in the RFC index. > I read through BB84, and it appears to be a key-exchange protocol, not > an encryption algorithm. Also, it appears to work only with direct > access to physical media and not with the regular bit stream that PPP > itself requires. Thus, I suspect it may not be really appropriate as > an ECP option, though I suppose it may open up a possibly interesting > discussion about whether we *should* talk about key distribution as an > ECP option. (Whether of the ordinary algorithmic sort, or the more > hand-wavy x-files area-51 "quantum" sort.) Where did you read about BB84 for PPP? My first thought when I read the message from Michelle Cotton was that someone is playing a practical joke on the IANA. It is possible that someone sane seriously wants to do PPP with quantum cryptography, but I'd like to see an I-D or at least something more substantial than the short note from Mohamed Ali. There have been some serious quantum cryptography efforts that I'd not call hand-wavy x-files area-51, but they've all been a little "academic" as opposed to "industrial." Before the IANA fires up a registry, there must be an IETF protocol that would use it. So where is the I-D? Vernon Schryver vjs@rhyolite.com _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Wed Sep 14 10:45:39 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFYW3-0003D8-2d; Wed, 14 Sep 2005 10:45:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFYW0-0003Cq-MW for pppext@megatron.ietf.org; Wed, 14 Sep 2005 10:45:36 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14886 for ; Wed, 14 Sep 2005 10:45:32 -0400 (EDT) Received: from nwkea-mail-2.sun.com ([192.18.42.14]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EFYaY-0003kq-MJ for pppext@ietf.org; Wed, 14 Sep 2005 10:50:21 -0400 Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id j8EEjUHT006359 for ; Wed, 14 Sep 2005 07:45:30 -0700 (PDT) Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143]) by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL, v2.2) with ESMTP id j8EEjTUn003375 for ; Wed, 14 Sep 2005 10:45:29 -0400 (EDT) Received: from phorcys.East.Sun.COM (localhost [127.0.0.1]) by phorcys.East.Sun.COM (8.13.4+Sun/8.13.4) with ESMTP id j8EEjStQ024166; Wed, 14 Sep 2005 10:45:28 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.East.Sun.COM (8.13.4+Sun/8.13.4/Submit) id j8EEjS6W024163; Wed, 14 Sep 2005 10:45:28 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17192.14216.816941.262818@gargle.gargle.HOWL> Date: Wed, 14 Sep 2005 10:45:28 -0400 From: James Carlson To: Vernon Schryver Subject: Re: [Pppext] [rt.icann.org #3528] FW: General Request for Assignments (ppp-numbers) In-Reply-To: Vernon Schryver's message of 9 September 2005 07:53:53 References: <17185.31145.738118.436622@gargle.gargle.HOWL> <200509091353.j89Drrxb026816@calcite.rhyolite.com> X-Mailer: VM 7.01 under Emacs 21.3.1 X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit Cc: pppext@ietf.org, iana-prot-param@icann.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org Vernon Schryver writes: > > Unfortunately, Vern's RFC 3818 doesn't cover ECP assignments, so it > > appears we're still stuck with expert review. That means we need to > > discuss it here and report consensus back. > > My now vague recollections are that 3818 does not mention ECP because > a similar document was advanced specifically for ECP. I can't seem > to find it in the RFC index. Nor could I. > > I read through BB84, and it appears to be a key-exchange protocol, not > > an encryption algorithm. Also, it appears to work only with direct > > access to physical media and not with the regular bit stream that PPP > > itself requires. Thus, I suspect it may not be really appropriate as > > an ECP option, though I suppose it may open up a possibly interesting > > discussion about whether we *should* talk about key distribution as an > > ECP option. (Whether of the ordinary algorithmic sort, or the more > > hand-wavy x-files area-51 "quantum" sort.) > > Where did you read about BB84 for PPP? I just read about BB84, not its use with PPP, but it seems fairly clear to me that since BB84 needs access to a physical layer transport between peers, it's not *just* an ECP option. > My first thought when I read the message from Michelle Cotton was that > someone is playing a practical joke on the IANA. It is possible that > someone sane seriously wants to do PPP with quantum cryptography, but > I'd like to see an I-D or at least something more substantial than the > short note from Mohamed Ali. I agree. It seemed dubious to me. > There have been some serious quantum cryptography efforts that I'd not > call hand-wavy x-files area-51, but they've all been a little "academic" > as opposed to "industrial." Before the IANA fires up a registry, there > must be an IETF protocol that would use it. So where is the I-D? So, let's have a hum of agreement. Anyone disagree that we should ask to see the I-D published before the code point is assigned? -- James Carlson, KISS Network Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Wed Sep 14 13:35:27 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFbAN-00055y-NW; Wed, 14 Sep 2005 13:35:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFbAJ-00054F-0L for pppext@megatron.ietf.org; Wed, 14 Sep 2005 13:35:25 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22879 for ; Wed, 14 Sep 2005 13:35:21 -0400 (EDT) Received: from hoemail1.lucent.com ([192.11.226.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EFbEv-0008Hh-Ii for pppext@ietf.org; Wed, 14 Sep 2005 13:40:11 -0400 Received: from horh1.emsr.lucent.com (h135-112-138-211.lucent.com [135.112.138.211]) by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j8EHZ61A000422; Wed, 14 Sep 2005 12:35:06 -0500 (CDT) Received: from new-wopr.eng.ascend.com (new-wopr.eng.ascend.com [135.140.53.19]) by horh1.emsr.lucent.com (8.12.11/8.12.11) with ESMTP id j8EHZ1hq022749; Wed, 14 Sep 2005 12:35:05 -0500 (CDT) Received: from cliff.eng.ascend.com (cliff.eng.ascend.com [135.140.53.169]) by new-wopr.eng.ascend.com (8.11.6+Sun/8.10.2) with ESMTP id j8EHZ0b26275; Wed, 14 Sep 2005 10:35:00 -0700 (PDT) Received: from igoyret-t23 (dhcp-135-140-27-179 [135.140.27.179]) by cliff.eng.ascend.com (8.13.1/8.13.1) with SMTP id j8EHYwSd013668; Wed, 14 Sep 2005 10:34:59 -0700 Message-Id: <200509141734.j8EHYwSd013668@cliff.eng.ascend.com> X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 Date: Wed, 14 Sep 2005 10:31:58 -0700 To: James Carlson From: Ignacio Goyret Subject: Re: [Pppext] [rt.icann.org #3528] FW: General Request for Assignments(ppp-numbers) In-Reply-To: <17192.14216.816941.262818@gargle.gargle.HOWL> References: <17185.31145.738118.436622@gargle.gargle.HOWL> <200509091353.j89Drrxb026816@calcite.rhyolite.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 1.9 (+) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Cc: pppext@ietf.org, iana-prot-param@icann.org, Vernon Schryver X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org At 10:45 9/14/2005 -0400, James Carlson wrote: >> There have been some serious quantum cryptography efforts that I'd not >> call hand-wavy x-files area-51, but they've all been a little "academic" >> as opposed to "industrial." Before the IANA fires up a registry, there >> must be an IETF protocol that would use it. So where is the I-D? > >So, let's have a hum of agreement. Anyone disagree that we should ask >to see the I-D published before the code point is assigned? Agreed. Let's see the I-D first. _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Thu Sep 15 08:05:08 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFsUG-0007BA-T8; Thu, 15 Sep 2005 08:05:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFsUE-0007A3-Jn for pppext@megatron.ietf.org; Thu, 15 Sep 2005 08:05:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06369 for ; Thu, 15 Sep 2005 08:05:05 -0400 (EDT) Received: from zproxy.gmail.com ([64.233.162.199]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EFsZ1-0006y7-EU for pppext@ietf.org; Thu, 15 Sep 2005 08:10:04 -0400 Received: by zproxy.gmail.com with SMTP id l1so244609nzf for ; Thu, 15 Sep 2005 05:04:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cNVX4jwhw2DHSVr2Tg/chCtCHPuQj+0FjjSWO9yvxTARLNH1u3dr63XqA8uns0NczlVor1kguTm8EcwFnAyoPPjdikEl6FXrWYselO/4lrNuCcltNNpt3cNe/lakEuDLKXF8t8xvk06CNt8oyAwQXoWYCgHXd5kRKSa5krxoezg= Received: by 10.54.124.19 with SMTP id w19mr341877wrc; Thu, 15 Sep 2005 05:04:53 -0700 (PDT) Received: by 10.54.79.3 with HTTP; Thu, 15 Sep 2005 05:04:56 -0700 (PDT) Message-ID: Date: Thu, 15 Sep 2005 05:04:56 -0700 From: Clint Chaplin To: James Carlson Subject: Re: [Pppext] [rt.icann.org #3528] FW: General Request for Assignments (ppp-numbers) In-Reply-To: <17192.14216.816941.262818@gargle.gargle.HOWL> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17185.31145.738118.436622@gargle.gargle.HOWL> <200509091353.j89Drrxb026816@calcite.rhyolite.com> <17192.14216.816941.262818@gargle.gargle.HOWL> X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: quoted-printable Cc: pppext@ietf.org, iana-prot-param@icann.org, Vernon Schryver X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: clint.chaplin@gmail.com List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org Rotary Engine. >=20 > So, let's have a hum of agreement. Anyone disagree that we should ask > to see the I-D published before the code point is assigned? >=20 --=20 Clint (JOATMON) Chaplin Wireless Security Technologist Wireless Standards Manager _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Thu Sep 15 08:21:03 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFsjf-0003f1-Cd; Thu, 15 Sep 2005 08:21:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFsjd-0003ew-JT for pppext@megatron.ietf.org; Thu, 15 Sep 2005 08:21:01 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07143 for ; Thu, 15 Sep 2005 08:20:57 -0400 (EDT) Received: from nwkea-mail-1.sun.com ([192.18.42.13]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EFsoK-0007Np-1J for pppext@ietf.org; Thu, 15 Sep 2005 08:25:57 -0400 Received: from eastmail2bur.East.Sun.COM ([129.148.13.40]) by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id j8FCKp2B017691 for ; Thu, 15 Sep 2005 05:20:52 -0700 (PDT) Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143]) by eastmail2bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL, v2.2) with ESMTP id j8FCKpWD016200 for ; Thu, 15 Sep 2005 08:20:51 -0400 (EDT) Received: from phorcys.East.Sun.COM (localhost [127.0.0.1]) by phorcys.East.Sun.COM (8.13.4+Sun/8.13.4) with ESMTP id j8FCKpr2028038; Thu, 15 Sep 2005 08:20:51 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.East.Sun.COM (8.13.4+Sun/8.13.4/Submit) id j8FCKp2c028035; Thu, 15 Sep 2005 08:20:51 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17193.26403.210920.790452@gargle.gargle.HOWL> Date: Thu, 15 Sep 2005 08:20:51 -0400 From: James Carlson To: iana-prot-param@icann.org Subject: Re: [Pppext] [rt.icann.org #3528] FW: General Request for Assignments (ppp-numbers) In-Reply-To: Clint Chaplin's message of 15 September 2005 05:04:56 References: <17185.31145.738118.436622@gargle.gargle.HOWL> <200509091353.j89Drrxb026816@calcite.rhyolite.com> <17192.14216.816941.262818@gargle.gargle.HOWL> X-Mailer: VM 7.01 under Emacs 21.3.1 X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 7bit Cc: pppext@ietf.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org OK, that's sufficient. I'm going to call that agreement. ;-} IANA: please notify the submitter that the PPPEXT Working Group would like to see an Internet Draft published before we agree to the allocation of a code point within the PPP ECP option space for this new keying mechanism. -- James Carlson, KISS Network Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext