http://blog.gmane.org/gmane.ietf.pppext hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.ietf.pppext/1224 <pre>Hi, Our AD is interested in a plan to upgrade appropriate PPP standards track RFCs to full Standard. A change in state can, under the right circumstances, be done without a new RFC. I think it would be appropriate, as I have suggested before, to review the PPP security RFCs with a view, in each case, to moving to Historic those which don't meet modern security standards or to obsolete them with a new version which does... The later would require a Charter change. To quote from the existing PPPEXT Charter: "The group may, however, advance existing specifications to the next level in the standards track, if a need for that comes up. Similarly, the group may classify existing specifications as Historic where this is appropriate." I'd be interested in any comments. If there is any desire for a brief meeting in Berlin to discuss this sort of thing, this would be a good time to request it. (I just noticed that the session request tool has an option to request a 1/2 hour meeting which I never noticed before. Wh</pre> Donald Eastlake 2013-05-12T10:01:00 http://comments.gmane.org/gmane.ietf.pppext/1223 <pre>Biggest Fake Conference in Computer Science We are researchers from different parts of the world and conducted a study on the world’s biggest bogus computer science conference WORLDCOMP ( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia from University of Georgia, USA. We submitted a fake paper to WORLDCOMP 2011 and again (the same paper with a modified title) to WORLDCOMP 2012. This paper had numerous fundamental mistakes. Sample statements from that paper include: (1). Binary logic is fuzzy logic and vice versa (2). Pascal developed fuzzy logic (3). Object oriented languages do not exhibit any polymorphism or inheritance (4). TCP and IP are synonyms and are part of OSI model (5). Distributed systems deal with only one computer (6). Laptop is an example for a super computer (7). Operating system is an example for computer hardware Also, our paper did not express any conceptual meaning. However, it was accepted both the times without any modifications (and without</pre> johnsonhammond1< at >hushmail.com 2013-04-27T17:27:59 http://comments.gmane.org/gmane.ietf.pppext/1186 <pre>Hi, In case you were unaware, I am now the Chair of PPPEXT. Generally, there has been little activity in this WG for some years. Although I believe it serves a useful purpose in examining PPP proposals, possibly that purpose could be served by just continuing the mailing list. In any case, it seems likely that, if the situation continues unchanged, the WG will be dissolved sometime early next year. In the process of producing RFC 6361, it became very apparent that the PPP security RFCs, such as they are, meet few, if any, modern IETF security guidelines. I believe that there should be an update of PPP security or, if an effort to update them fails for some reason, then at least old / inadequate / unimplemented PPP security RFCs should be declared historic. My suggestion is that PPPEXT re-Charter to include a goal such as the above and I'm willing to try drafting a new Charter but welcome suggestions and comments on all this. One question is, should PPPEXT have a 1 hour meeting at the November IETF meeti</pre> Donald Eastlake 2011-09-08T22:24:24 http://comments.gmane.org/gmane.ietf.pppext/1179 <pre>Preparing to watch some IETF meetings, I belatedly noticed this. Because it is now an independent submission, it wasn't sent to the pppext list. -------- Original Message -------- Subject: I-D Action: draft-ietf-pppext-trill-protocol-08.txt Date: Tue, 14 Jun 2011 15:07:01 -0700 From: internet-drafts&lt; at &gt;ietf.org Reply-To: internet-drafts&lt; at &gt;ietf.org To: i-d-announce&lt; at &gt;ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : PPP TRILL Protocol Control Protocol Author(s) : James Carlson Donald Eastlake Filename : draft-ietf-pppext-trill-protocol-08.txt Pages : 11 Date : 2011-06-14 The Point-to-Point Protocol (PPP) defines a Link Control Protocol (LCP) and a method for negotiating the use of multi-protocol traffic over point-to-point links. This document describes PPP support for the Transparent Interconnection of Lots of Links (TRILL) Protocol, allowing direct communication betw</pre> William Allen Simpson 2011-07-25T15:11:55 http://comments.gmane.org/gmane.ietf.pppext/1164 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Point-to-Point Protocol Extensions Working Group of the IETF. Title : PPP TRILL Protocol Control Protocol Author(s) : James Carlson Filename : draft-ietf-pppext-trill-protocol-07.txt Pages : 7 Date : 2011-06-03 The Point-to-Point Protocol (PPP) defines a Link Control Protocol (LCP) and a method for negotiating the use of multi-protocol traffic over point-to-point links. This document describes PPP support for Transparent Interconnection of Lots of Links (TRILL) Protocol, allowing direct communication between Routing Bridges (RBridges) via PPP links. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pppext-trill-protocol-07.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/d</pre> internet-drafts< at >ietf.org 2011-06-03T19:45:15 http://comments.gmane.org/gmane.ietf.pppext/1144 <pre>As part of IETF review, the Routing ADs are looking over draft-ietf-pppext-trill-protocol-06. Not too surprising to me -- given that I still think it's far out of scope -- the text concerning IS-IS System IDs is causing trouble in that review. See this thread: http://www.ietf.org/mail-archive/web/rtg-dir/current/threads.html#01533 I wish I could leave the worms safely in the can, but it's looking like that might not be one of the options. Instead of the reference to Bill Simpson's draft, Stewart Bryant suggested replacement text like this: ISO/IEC 10589 states that it is the responsibility of the routeing domain administrative authority to enforce the uniqueness of the system ID. In cases where a zero configuration system is supplied the system manufacturer MUST install a suitable unique identifier at manufacturing time. One way to achieve this is for the manufacturer to use a unique IEEE MAC address following the allocation procedures normally used in the manufacture of an Ethernet int</pre> James Carlson 2011-05-31T17:05:07 http://comments.gmane.org/gmane.ietf.pppext/1136 <pre>Hi All While working with ML-PPP over some time, I have come across some problems which I think should be solved at the protocol level. Please review the abstract below and let me know your valuable opinions: As per existing RFC, following are the key characteristics of LCP negotiation for multi-link parameters: • MRRU option is considered as mandatory option for a link to join a MC/ML-PPP bundle • Endpoint discriminator is optional and can be used to identify different PPP peers • Short-sequence number as an option is negotiated as part of LCP although same value has to be negotiated on all the links Problem that current protocol creates is that it allows a scope for bundle level parameters to be negotiated with different values on different links. This leads to an implementation ambiguity about which values to be chosen for the bundle. Some of the ways applications can implement this choice are: - Choose the negotiated value from t</pre> Vineet kumar Garg 2011-05-26T09:21:45 http://comments.gmane.org/gmane.ietf.pppext/1134 <pre> The IESG has received a request from the Point-to-Point Protocol Extensions WG (pppext) to consider the following document: - 'PPP TRILL Protocol Control Protocol' &lt;draft-ietf-pppext-trill-protocol-06.txt&gt; as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf&lt; at &gt;ietf.org mailing lists by 2011-06-08. Exceptionally, comments may be sent to iesg&lt; at &gt;ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The Point-to-Point Protocol (PPP) defines a Link Control Protocol (LCP) and a method for negotiating the use of multi-protocol traffic over point-to-point links. This document describes PPP support for Transparent Interconnection of Lots of Links (TRILL) Protocol, allowing direct communication between Routing Bridges (RBridges) via PPP links. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf</pre> The IESG 2011-05-25T16:13:57 http://comments.gmane.org/gmane.ietf.pppext/1128 <pre>I have reviewed this draft. I think it is basically in good shape, but needs to make a few things more explicit &amp; correct small issues. For what it is worth, I'm happy with the resolution of the system ID issue; it really needs to be out of scope and dealt in ISIS WG, if they think its an issue. I'm expecting a new draft version. Then I can start an IETF Last Call. Also, for the record, as James is both the WG chair and the author, I have reviewed the discussion in the mailing list and believe that the Working Group has consensus to move the document forward. Section 2.1: Can you clarify what this actually means. It was not clear (to this reader, at least). Is this where the configuration options would be, if some were defined? But if so, what does LCP code numbers have to do with it? Section 2.2: Please add a reference to the document and Section where these fields are defined. TRILL version of IS-IS, I presume. Please provide a reference to the RFC that specifies the IS-IS payload used </pre> Jari Arkko 2011-05-24T10:23:59 http://comments.gmane.org/gmane.ietf.pppext/1122 <pre>New "Intended status", updated with various minor changes, such as Radia's request for a bit more detail of Magic Numbers. Also tossed in a MUST to SHOULD change for Don, and made the probability comparison more explicit. Ready to roll. http://tools.ietf.org/rfcdiff?url2=draft-simpson-isis-ppp-unique-01.txt === A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Generation of Unique IS-IS System Identifiers Author(s) : William Allen Simpson Filename : draft-simpson-isis-ppp-unique-01.txt Pages : 8 Date : 2011-05-18 The IS-IS routing protocol (Intermediate System to Intermediate System, ISO 10589) requires unique System Identifiers at the link layer. A common practice has been to use an existing IEEE 802 MAC link-layer interface identifier. When no unique MAC is available, this document specifies automatic generation of identifiers. It is fully interoperable with systems that do not support t</pre> William Allen Simpson 2011-05-18T14:22:29 http://comments.gmane.org/gmane.ietf.pppext/1121 <pre>Another update of this draft. Among the changes, the draft now says that it intends "Informational" rather than "Experimental" status, and it has switched to use vendor-specific options rather than a distinct IPCP Option number. While I continue to believe that this is not the right layer at which to do this negotiation, and thus it's still an architectural error, the move to a vendor option alleviates many of my concerns. I think we're just down to the use of the IETF as a vanity press. Perhaps if it must go forward, we can agree on some disclaimer text explaining that it's not the product of this working group and that there are serious reservations concerning its use. </pre> James Carlson 2011-05-17T11:34:25 http://comments.gmane.org/gmane.ietf.pppext/1113 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Point-to-Point Protocol Extensions Working Group of the IETF. Title : PPP TRILL Protocol Control Protocol Author(s) : James Carlson Filename : draft-ietf-pppext-trill-protocol-04.txt Pages : 7 Date : 2011-05-09 The Point-to-Point Protocol (PPP) defines a Link Control Protocol (LCP) and a method for negotiating the use of multi-protocol traffic over point-to-point links. This document describes PPP support for Transparent Interconnection of Lots of Links (TRILL) Protocol, allowing direct communication between Routing Bridges (RBridges) via PPP links. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pppext-trill-protocol-04.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/d</pre> internet-drafts< at >ietf.org 2011-05-09T16:02:27 http://comments.gmane.org/gmane.ietf.pppext/1107 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Point-to-Point Protocol Extensions Working Group of the IETF. Title : PPP TRILL Protocol Control Protocol Author(s) : J. Carlson Filename : draft-ietf-pppext-trill-protocol-03.txt Pages : 6 Date : 2011-03-30 The Point-to-Point Protocol (PPP) [1] defines a Link Control Protocol (LCP) and a method for negotiating the use of multi-protocol traffic over point-to-point links. This document describes support for Transparent Interconnection of Lots of Links (TRILL) Protocol, allowing direct communication between Routing Bridges (RBridges) via PPP links. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pppext-trill-protocol-03.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically re</pre> Internet-Drafts< at >ietf.org 2011-03-30T19:45:02 http://comments.gmane.org/gmane.ietf.pppext/1103 <pre>Includes changes discussed, with changebars. The internet-draft (sans c) does not include the changebars. === INTERNET-DRAFT W A Simpson DayDreamer Intended status: Standards Track 29 March 2011 Generation of Unique IS-IS System Identifiers | draft-simpson-isis-ppp-unique-00c | Abstract The IS-IS routing protocol (Intermediate System to Intermediate System, ISO 10589) requires unique System Identifiers at the link layer. A common practice has been to use an existing IEEE 802 MAC | link-layer interface identifier. When no unique MAC is available, this document specifies automatic generation of identifiers. It is fully interoperable with systems that do not support this extension. Additionally, the extension automatically resolves conflicts between System Identifi</pre> William Allen Simpson 2011-03-30T02:49:13 http://comments.gmane.org/gmane.ietf.pppext/1095 <pre>Sadly, I wasn't paying attention, and didn't notice there was another IETF meeting coming up. So, they won't let me post this draft today. Here it is anyway for your perusal, just in case anybody is interested! === INTERNET-DRAFT W A Simpson DayDreamer Intended status: Standards Track 17 March 2011 Generation of Unique IS-IS System Identifiers draft-simpson-isis-ppp-unique-00b Abstract The IS-IS routing protocol (Intermediate System to Intermediate System, ISO 10589) requires unique System Identifiers at the link layer. A common practice has been to use an existing IEEE 802 MAC link-layer address. When no unique MAC address is available, this document specifies automatic generation of identifiers. It is fully interoperable with systems that do not support this extension. Additionally, the extension au</pre> William Allen Simpson 2011-03-17T19:24:17 http://comments.gmane.org/gmane.ietf.pppext/1093 <pre>Two new drafts were posted for IPv6CP extensions. The announcements are attached. You can see diffs from the previous version by looking here: http://tools.ietf.org/html/draft-hu-pppext-ipv6cp-requirements-01 http://tools.ietf.org/html/draft-hu-pppext-ipv6cp-extensions-01 </pre> James Carlson 2011-03-14T21:31:29 http://comments.gmane.org/gmane.ietf.pppext/1092 <pre>I see nothing particularly new here -- just a rehash of the existing ability to negotiate NCPs when and where desired -- but since it describes PPP mechanisms directly, I'm forwarding it along to the list. </pre> James Carlson 2011-03-08T15:30:33 http://comments.gmane.org/gmane.ietf.pppext/1091 <pre>This message was somehow lost in the ether. I've contacted ietf-action to see if they can dig up any information. In any event, sorry, Anoop, for the inadvertent delay. </pre> James Carlson 2011-02-07T16:15:57 http://comments.gmane.org/gmane.ietf.pppext/1081 <pre> 3. An implementation that has only PPP links might have no previously configured Media Access Control (MAC) that can function as an IS-IS System ID. In this case, the System ID is formed by adding a randomly generated 14-bit leading number (in place of an OUI) to the link's unique LCP Magic Number. The Magic Number MUST be unique for all links and all known link peers. This pseudo-MAC MUST have both the "locally-assigned" and "broadcast/multicast" (group) bits set to 1; that is, the least significant two bits of the most significant octet are both set to 1. ... Operational Considerations Although the probability of conflict with another IS-IS System ID is minuscule, each implementation MUST have a configuration option to override the System ID. _______________________________________________ Pppext mailing list Pppext&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/pppext </pre> William Allen Simpson 2011-01-27T11:03:45 http://comments.gmane.org/gmane.ietf.pppext/1059 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Point-to-Point Protocol Extensions Working Group of the IETF. Title : PPP TRILL Protocol Control Protocol Author(s) : J. Carlson Filename : draft-ietf-pppext-trill-protocol-02.txt Pages : 6 Date : 2011-01-06 The Point-to-Point Protocol (PPP) [1] defines a Link Control Protocol (LCP) and a method for negotiating the use of multi-protocol traffic over point-to-point links. This document describes support for Transparent Interconnection of Lots of Links (TRILL) Protocol, allowing direct communication between Routing Bridges (RBridges) via PPP links. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pppext-trill-protocol-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically re</pre> Internet-Drafts< at >ietf.org 2011-01-06T15:45:01 http://comments.gmane.org/gmane.ietf.pppext/1055 <pre>Hi, I've received a comment about the last figure in Section 2.3 of draft-ietf-trill-rbridge-protocol-16.txt. This figure shows a very high level generic view of a TRILL Data frame being sent over PPP. However, there is a possible problem with that figure. The general form of a TRILL Data frame is Link Header TRILL Header Encapsulated data frame in Ethernet format Link Trailer If the link is Ethernet, the Link Header is an Ethernet Header (destination MAC, source MAC, possible VLAN tag, Ethertype) and the Link Trailer is an Ethernet Trailer, that is, an FCS covering the entire frame. If the link is PPP, then we should have a PPP Header, which is fine and is shown in the figure, but is there a "PPP Trailer"? The figure shows an "Ethernet FCS" which may be wrongly labeled. If there is an FCS there, calculated as Ethernet does, how much of the frame does it cover? In particular, does it cover the PPP Header, in which case I think it should be labeled "PPP FCS"? Or should the convention in PPP be to </pre> Donald Eastlake 2011-01-03T17:27:20 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.ietf.pppext