From pppext-bounces@ietf.org Fri Sep 07 16:28:28 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ITkOh-0003iS-4X; Fri, 07 Sep 2007 16:25:47 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ITkOf-0003Qj-4U for pppext@ietf.org; Fri, 07 Sep 2007 16:25:45 -0400 Received: from sca-ea-mail-2.sun.com ([192.18.43.25]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ITkOe-0007RM-KO for pppext@ietf.org; Fri, 07 Sep 2007 16:25:45 -0400 Received: from dm-east-02.east.sun.com ([129.148.13.5]) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l87KPhWt019649 for ; Fri, 7 Sep 2007 20:25:43 GMT Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143]) by dm-east-02.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id l87KPhsq059344 for ; Fri, 7 Sep 2007 16:25:43 -0400 (EDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l87KIDK5136479 for ; Fri, 7 Sep 2007 16:18:13 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l87KIB8g136476; Fri, 7 Sep 2007 16:18:11 -0400 (EDT) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="xhdeLebPED" Content-Transfer-Encoding: 7bit Message-ID: <18145.45571.689958.417678@gargle.gargle.HOWL> Date: Fri, 7 Sep 2007 16:18:11 -0400 From: James Carlson To: pppext@ietf.org X-Mailer: VM 7.01 under Emacs 21.3.1 X-Spam-Score: 0.0 (/) X-Scan-Signature: d16ce744298aacf98517bc7c108bd198 Subject: [Pppext] Fwd: Nomcom 2007-8: Nominations Close on Sep 10, 2007 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: , Errors-To: pppext-bounces@ietf.org --xhdeLebPED Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit If you have nominations or comments, please let nomcom know. --xhdeLebPED Content-Type: message/rfc822 Content-Description: forwarded message Content-Transfer-Encoding: 7bit MIME-version: 1.0 Content-Length: 1032 Content-type: text/plain; format=flowed; charset=ISO-8859-15 Return-path: Received: from mail-amer.sun.com [192.18.108.187] by phorcys.east.sun.com with IMAP (fetchmail-6.3.8) for (single-drop); Fri, 07 Sep 2007 15:53:59 -0400 (EDT) Received: from fe-amer-10.sun.com ([192.18.108.184]) by amer4-mail1.central.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0JO000EINKK2VO70@amer4-mail1.central.sun.com> for carlsonj@amer4-mail1.Central.Sun.COM; Fri, 07 Sep 2007 13:52:51 -0600 (MDT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JO000G01KIYP600@mail-amer.sun.com> for carlsonj@amer4-mail1.Central.Sun.COM (ORCPT james.d.carlson@sun.com); Fri, 07 Sep 2007 13:52:50 -0600 (MDT) Received: from phys-amer4-1.central.sun.com ([129.147.157.48]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTP id <0JO000LCOKK2X58Z@mail-amer.sun.com> for carlsonj@amer4-mail1.Central.Sun.COM (ORCPT james.d.carlson@sun.com); Fri, 07 Sep 2007 13:52:50 -0600 (MDT) Received: from dm-east-02.east.sun.com ([129.148.13.5]) by amer4-mail1.central.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0JO000EIFKK2VO70@amer4-mail1.central.sun.com> for carlsonj@amer4-mail1.Central.Sun.COM (ORCPT james.d.carlson@sun.com); Fri, 07 Sep 2007 13:52:50 -0600 (MDT) Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by dm-east-02.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id l87Jqnho049944 for ; Fri, 07 Sep 2007 15:52:49 -0400 (EDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l87Jqmkb017702; Fri, 07 Sep 2007 12:52:48 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JO000F07KJY7U00@brm-avmta-1.central.sun.com>; Fri, 07 Sep 2007 13:52:46 -0600 (MDT) Received: from sca-ea-mail-1.sun.com ([192.18.43.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JO000AUWKJXJR50@brm-avmta-1.central.sun.com>; Fri, 07 Sep 2007 13:52:45 -0600 (MDT) Received: from relay14i.sun.com (ip124.net129179-4.block1.us.syntegra.com [129.179.4.124]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l87JmNdt002179; Fri, 07 Sep 2007 19:52:44 +0000 (GMT) Received: from mmp12es.sun.com ([160.41.209.22] [160.41.209.22]) by relay14i.sun.com with ESMTP id BT-MMP-293078; Fri, 07 Sep 2007 19:52:44 +0000 (Z) Received: from relay12i.sun.com (relay12i.sun.com [129.179.4.122]) by mmp12es.sun.com with ESMTP id BT-MMP-161471; Fri, 07 Sep 2007 19:52:44 +0000 (Z) Received: from megatron.ietf.org ([156.154.16.145] [156.154.16.145]) by relay1i.sun.com with ESMTP id BT-MMP-1361636; Fri, 07 Sep 2007 19:52:44 +0000 (Z) Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ITjsb-0006ns-IT; Fri, 07 Sep 2007 15:52:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ITjsY-0006Ua-3P; Fri, 07 Sep 2007 15:52:34 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ITjsW-00027j-QH; Fri, 07 Sep 2007 15:52:34 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l87JqT0H017541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 07 Sep 2007 12:52:30 -0700 Received: from [10.50.69.196] (qconnect-10-50-69-196.qualcomm.com [10.50.69.196]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l87JqSO1025798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 07 Sep 2007 12:52:29 -0700 Errors-to: wgchairs-bounces@ietf.org Message-id: <46E1AC01.3050800@qualcomm.com> Precedence: list X-BeenThere: wgchairs@ietf.org X-PMX-Version: 5.2.0.264296 X-Spam-Score: -4.0 (----) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 X-Mailman-Version: 2.1.5 List-Post: List-Subscribe: , List-Unsubscribe: , List-Help: List-Id: Working Group Chairs User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) Original-recipient: rfc822;james.d.carlson@sun.com X-DCC-carlson-at-sun-Metrics: phorcys 1019; Body=1 Fuz1=1 Fuz2=1 From: Lakshminath Dondeti Sender: wgchairs-bounces@ietf.org To: ietf-announce@ietf.org, wgchairs@ietf.org, IESG IESG , IAB IAB Cc: Subject: Nomcom 2007-8: Nominations Close on Sep 10, 2007 Date: Fri, 07 Sep 2007 12:52:33 -0700 WGchairs, IESG and IAB members Please forward this request to the lists you manage and request feedback and nominations. All, Here is the link to nominate: https://tools.ietf.org/group/nomcom/07/nominate You may also send nominations or comments via email to nomcom07@ietf.org or ldondeti@qualcomm.com. We have received very few nominations (1, 2, 2, 2, 3, 4, 8, 8, 19) and even fewer accepted (1-2 people in each area, IAB acceptances is 4 at last count). I request the community to provide feedback on the incumbents (send email or send notes via the web page). 1) If you think that the incumbent is doing a good job a) provide feedback AND b) nominate similar people just in case there is strong negative feedback on the incumbent 2) If you think the incumbent can do somethings better a) provide feedback AND b) nominate someone who you think might do better Candidates, if time commitment is the only issue, please indicate that to the nomcom and accept the nominations. thanks, Lakshminath --xhdeLebPED Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext --xhdeLebPED-- From pppext-bounces@ietf.org Tue Sep 11 21:18:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVGpM-00069i-S4; Tue, 11 Sep 2007 21:15:36 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVGpL-00063R-2v for pppext@ietf.org; Tue, 11 Sep 2007 21:15:35 -0400 Received: from gate.alliedtelesyn.co.nz ([202.49.72.33]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IVGpK-0006WX-BL for pppext@ietf.org; Tue, 11 Sep 2007 21:15:35 -0400 Received: (qmail 13305 invoked from network); 12 Sep 2007 01:15:32 -0000 Received: from mmarshal2-dx.alliedtelesyn.co.nz (HELO mailmarshall.alliedtelesyn.co.nz) (10.32.18.41) by gate-int.alliedtelesyn.co.nz with SMTP; 12 Sep 2007 01:15:32 -0000 Received: from aslan.alliedtelesyn.co.nz (Not Verified[10.32.18.53]) by mailmarshall.alliedtelesyn.co.nz with MailMarshal (v6, 2, 0, 2977) id ; Wed, 12 Sep 2007 13:15:21 +1200 Received: from CHCDOM1-MTA by aslan.alliedtelesyn.co.nz with Novell_GroupWise; Wed, 12 Sep 2007 13:15:20 +1200 Message-Id: <46E7E648.4A01.00D7.0@alliedtelesis.co.nz> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Date: Wed, 12 Sep 2007 13:14:48 +1200 From: "matt harris" To: References: <46C9D571020000D70001C90A@aslan.alliedtelesyn.co.nz> <46E7E648020000D70001E926@aslan.alliedtelesyn.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Subject: [Pppext] RFC for LLDP control protocol? 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: , Errors-To: pppext-bounces@ietf.org Hi, Does anyone know if PPP DLL Protocol numbers have been assigned for the Link Layer Discovery Protocol (LLDP) data and control protocols for PPP? There is nothing in http://www.iana.org/assignments/ppp-number and RFC3818 says the IETF PPP Extensions working group decides by consensus new values in the PPP DLL protocol numbers address space. LLDP is the IEEE standards based (802.1ab) version of the Cisco Discovery Protocol. Various PPP RFCs are in the bibliography of 802.1ab but there doesn't appear to be a link in the other direction, that I can find. I know of at least one vendor claiming to support LLDPCP and need to know the Protocol numbers to achieve interoperability. Unfortunately I don't have one of the vendor's boxes or I could sniff the packets to see what they are using. thanks in advance, Matt Harris Allied Telesis Labs Christchurch New Zealand www.alliedtelesis.com NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesis Labs Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesis Labs. _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Wed Sep 12 09:49:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVSXw-0007sV-6u; Wed, 12 Sep 2007 09:46:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVSXv-0007q3-Es for pppext@ietf.org; Wed, 12 Sep 2007 09:46:23 -0400 Received: from sca-ea-mail-1.sun.com ([192.18.43.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IVSXr-0007Mb-Kl for pppext@ietf.org; Wed, 12 Sep 2007 09:46:23 -0400 Received: from dm-east-02.east.sun.com ([129.148.13.5]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l8CDkGvA003835 for ; Wed, 12 Sep 2007 13:46:16 GMT Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143]) by dm-east-02.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id l8CDkGuc045781 for ; Wed, 12 Sep 2007 09:46:16 -0400 (EDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l8CDVBMQ110791; Wed, 12 Sep 2007 09:31:11 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l8CDVAmE110788; Wed, 12 Sep 2007 09:31:10 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18151.59934.549615.201024@gargle.gargle.HOWL> Date: Wed, 12 Sep 2007 09:31:10 -0400 From: James Carlson To: matt harris Subject: Re: [Pppext] RFC for LLDP control protocol? In-Reply-To: <46E7E648.4A01.00D7.0@alliedtelesis.co.nz> References: <46C9D571020000D70001C90A@aslan.alliedtelesyn.co.nz> <46E7E648020000D70001E926@aslan.alliedtelesyn.co.nz> <46E7E648.4A01.00D7.0@alliedtelesis.co.nz> X-Mailer: VM 7.01 under Emacs 21.3.1 X-Spam-Score: -1.0 (-) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d 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: , Errors-To: pppext-bounces@ietf.org matt harris writes: > Does anyone know if PPP DLL Protocol numbers have been assigned for the > Link Layer Discovery Protocol (LLDP) data and control protocols for PPP? No, there isn't one. But why exactly would you do that? As best I can tell, LLDP (802.1AB) would mostly duplicate what PPP negotiation itself already does. I could understand why you'd want that if you were running bridging over PPP (RFC 3518), but then you'd probably run it using the assigned Ethertype of LLDP over the bridge link. > There is nothing in http://www.iana.org/assignments/ppp-number and > RFC3818 says the IETF PPP Extensions working group decides by consensus > new values in the PPP DLL protocol numbers address space. That's correct, and it means that publishing an RFC is _required_ in order to allocate a new number. Other allocations are just not valid. The only exception to this is RFC 2153, which allows for vendor extensions. Consenting peers using a vendor extension could (at least in theory) negotiate the use of a non-standard protocol without running into interoperability problems. > I know of at least one vendor claiming to support LLDPCP and need to > know the Protocol numbers to achieve interoperability. Unfortunately I > don't have one of the vendor's boxes or I could sniff the packets to see > what they are using. That one vendor seems to be HP. You should probably contact them directly and ask what they're intending for interoperability, as it appears to be their invention, and isn't described in any open document I can locate. -- James Carlson, Solaris Networking 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