<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.ietf.pppext">
    <title>gmane.ietf.pppext</title>
    <link>http://blog.gmane.org/gmane.ietf.pppext</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1229"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1228"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1227"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1226"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1225"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1224"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1223"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1221"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1220"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1219"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1218"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1217"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1216"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1215"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1214"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1213"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1212"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1211"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1210"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.pppext/1209"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1229">
    <title>Re: Advancing PPP RFCs to Standard, updating Security</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1229</link>
    <description>&lt;pre&gt;Given the recent observable history of this group, I'm skeptical that
it has energy to do anything. 

Advancing stuff up the Standards Track is always a worthy goal, and no
doubt our newest AD would prefer WGs doing something rather than
nothing, but is it really worth the effort?

Personally, I don't see the need for this WG anymore. It was left
chartered back when I was AD (even though it had no real work left to
do even then) for the specific reason that the IETF was still getting
PPP (and PPPoE) related drafts sent to the RFC editor that needed
review and needed a WG to say "the WG doesn't want to do that".

Those days seem long gone now...

Thomas

_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Thomas Narten</dc:creator>
    <dc:date>2013-05-22T14:25:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1228">
    <title>Re: Advancing PPP RFCs to Standard, updating Security</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1228</link>
    <description>&lt;pre&gt;Hi,

Thanks for the feedback thus far on security. Further feedback welcome.

I continue to be inclined against having a WG meeting in Berlin.

I may have overstated our AD's interest in advancing PPP standards,
Brian is perhaps closer to neutral on the idea.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3&amp;lt; at &amp;gt;gmail.com


On Sun, May 12, 2013 at 6:01 AM, Donald Eastlake &amp;lt;d3e3e3&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Donald Eastlake</dc:creator>
    <dc:date>2013-05-15T06:59:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1227">
    <title>Re: Advancing PPP RFCs to Standard, updating Security</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1227</link>
    <description>&lt;pre&gt;Likewise. If they don't meet current security standards, any changes we
make are certainly not going to be widely implemented.

Karl


On Mon, May 13, 2013 at 1:33 AM, Glen Zorn &amp;lt;glenzorn&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext
&lt;/pre&gt;</description>
    <dc:creator>Karl Fox</dc:creator>
    <dc:date>2013-05-13T12:54:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1226">
    <title>Re: Advancing PPP RFCs to Standard, updating Security</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1226</link>
    <description>&lt;pre&gt;
 &amp;gt;
I agree.

 &amp;gt;
 &amp;gt; On May 12, 2013, at 3:01 AM, "Donald Eastlake" &amp;lt;d3e3e3&amp;lt; at &amp;gt;gmail.com&amp;gt;
 &amp;gt; wrote:
 &amp;gt;
 &amp;gt;&amp;gt; Hi,
 &amp;gt;&amp;gt;
 &amp;gt;&amp;gt; Our AD is interested in a plan to upgrade appropriate PPP
 &amp;gt;&amp;gt; standards track RFCs to full Standard. A change in state can, under
 &amp;gt;&amp;gt; the right circumstances, be done without a new RFC.
 &amp;gt;&amp;gt;
 &amp;gt;&amp;gt; I think it would be appropriate, as I have suggested before, to
 &amp;gt;&amp;gt; review the PPP security RFCs with a view, in each case, to moving
 &amp;gt;&amp;gt; to Historic those which don't meet modern security standards or to
 &amp;gt;&amp;gt; obsolete them with a new version which does... The later would
 &amp;gt;&amp;gt; require a Charter change.
 &amp;gt;&amp;gt;
 &amp;gt;&amp;gt; To quote from the existing PPPEXT Charter: "The group may,
 &amp;gt;&amp;gt; however, advance existing specifications to the next level in the
 &amp;gt;&amp;gt; standards track, if a need for that comes up. Similarly, the group
 &amp;gt;&amp;gt; may classify existing specifications as Historic where this is
 &amp;gt;&amp;gt; appropriate."
 &amp;gt;&amp;gt;
 &amp;gt;&amp;gt; I'd be interested in any comments. If there is any desire for a
 &amp;gt;&amp;gt; brief meeting in Berlin to discuss this sort of thing, this would
 &amp;gt;&amp;gt; be a good time to request it. (I just noticed that the session
 &amp;gt;&amp;gt; request tool has an option to request a 1/2 hour meeting which I
 &amp;gt;&amp;gt; never noticed before. While WGs have had very short meetings, I
 &amp;gt;&amp;gt; can't recall one scheduled for less than 1 hour...) I suspect such
 &amp;gt;&amp;gt; a meeting at the next IETF Meeting in Berlin is not necessary...
 &amp;gt;&amp;gt;
 &amp;gt;&amp;gt; Thanks, Donald [PPPEXT Chair] ============================= Donald
 &amp;gt;&amp;gt; E. Eastlake 3rd   +1-508-333-2270 (cell) 155 Beaver Street,
 &amp;gt;&amp;gt; Milford, MA 01757 USA d3e3e3&amp;lt; at &amp;gt;gmail.com
 &amp;gt;&amp;gt; _______________________________________________ Pppext mailing
 &amp;gt;&amp;gt; list Pppext&amp;lt; at &amp;gt;ietf.org https://www.ietf.org/mailman/listinfo/pppext
 &amp;gt; _______________________________________________ Pppext mailing list
 &amp;gt; Pppext&amp;lt; at &amp;gt;ietf.org https://www.ietf.org/mailman/listinfo/pppext

_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Glen Zorn</dc:creator>
    <dc:date>2013-05-13T05:33:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1225">
    <title>Re: Advancing PPP RFCs to Standard, updating Security</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1225</link>
    <description>&lt;pre&gt;I see no point in creating new PPP security standards at this point. 

On May 12, 2013, at 3:01 AM, "Donald Eastlake" &amp;lt;d3e3e3&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Bernard Aboba</dc:creator>
    <dc:date>2013-05-12T22:55:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1224">
    <title>Advancing PPP RFCs to Standard, updating Security</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1224</link>
    <description>&lt;pre&gt;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.
While WGs have had very short meetings, I can't recall one scheduled
for less than 1 hour...) I suspect such a meeting at the next IETF
Meeting in Berlin is not necessary...

Thanks,
Donald [PPPEXT Chair]
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3&amp;lt; at &amp;gt;gmail.com
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Donald Eastlake</dc:creator>
    <dc:date>2013-05-12T10:01:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1223">
    <title>Biggest Fake Conference in Computer Science</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1223</link>
    <description>&lt;pre&gt;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 
any reviews) and we were invited to submit the final paper and a 
payment of $500+ fee to present the paper. We decided to use the 
fee for better purposes than making Prof. Hamid Arabnia (Chairman 
of WORLDCOMP) rich. After that, we received few reminders from 
WORLDCOMP to pay the fee but we never responded. 


We MUST say that you should look at the above website if you have any thoughts 
to submit a paper to WORLDCOMP.  DBLP and other indexing agencies have stopped 
indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See 
http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the 
conferences of WORLDCOMP and notice that there is no listing after 2010. See Section 2 of
http://sites.google.com/site/dumpconf for comments from well-known researchers 
about WORLDCOMP. 


The status of your WORLDCOMP papers can be changed from scientific
to other (i.e., junk or non-technical) at any time. Better not to have a paper than 
having it in WORLDCOMP and spoil the resume and peace of mind forever!


Our study revealed that WORLDCOMP is a money making business, 
using University of Georgia mask, for Prof. Hamid Arabnia. He is throwing 
out a small chunk of that money (around 20 dollars per paper published 
in WORLDCOMP’s proceedings) to his puppet (Mr. Ashu Solo or A.M.G. Solo) 
who publicizes WORLDCOMP and also defends it at various forums, using 
fake/anonymous names. The puppet uses fake names and defames other conferences
to divert traffic to WORLDCOMP. He also makes anonymous phone calls and tries to 
threaten the critiques of WORLDCOMP (See Item 7 of Section 5 of above website). 
That is, the puppet does all his best to get a maximum number of papers published 
at WORLDCOMP to get more money into his (and Prof. Hamid Arabnia’s) pockets. 


Monte Carlo Resort (the venue of WORLDCOMP for more than 10 years, until 2012) has 
refused to provide the venue for WORLDCOMP’13 because of the fears of their image 
being tarnished due to WORLDCOMP’s fraudulent activities. That is why WORLDCOMP’13 
is taking place at a different resort. WORLDCOMP will not be held after 2013. 


The draft paper submission deadline is over but still there are no committee 
members, no reviewers, and there is no conference Chairman. The only contact 
details available on WORLDCOMP’s website is just an email address! 

Let us make a direct request to Prof. Hamid arabnia: publish all reviews for 
all the papers (after blocking identifiable details) since 2000 conference. Reveal 
the names and affiliations of all the reviewers (for each year) and how many 
papers each reviewer had reviewed on average. We also request him to look at 
the Open Challenge (Section 6) at https://sites.google.com/site/moneycomp1 


Sorry for posting to multiple lists. Spreading the word is the only way to stop 
this bogus conference. Please forward this message to other mailing lists and people. 


We are shocked with Prof. Hamid Arabnia and his puppet’s activities 
http://worldcomp-fake-bogus.blogspot.com   Search Google using the 
keyword worldcomp fake for additional links.

_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext
&lt;/pre&gt;</description>
    <dc:creator>johnsonhammond1&lt; at &gt;hushmail.com</dc:creator>
    <dc:date>2013-04-27T17:27:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1221">
    <title>Re: Errata classification</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1221</link>
    <description>&lt;pre&gt;Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3&amp;lt; at &amp;gt;gmail.com


On Wed, May 9, 2012 at 6:53 AM, James Carlson &amp;lt;carlsonj&amp;lt; at &amp;gt;workingcode.com&amp;gt; wrote:
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Donald Eastlake</dc:creator>
    <dc:date>2012-05-09T13:44:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1220">
    <title>Re: Errata classification</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1220</link>
    <description>&lt;pre&gt;
At Sun, I worked on an implementation of RFC 2759, and verified the
resulting compatibility with Microsoft RAS.  The erratum is correct.
The password is indeed hashed using UTF-16-LE encoding.  (I suspect, but
cannot prove, that it was originally defined on NT using UCS-2-LE rather
than UTF-16-LE.  But the distinction almost certainly doesn't matter.)

&lt;/pre&gt;</description>
    <dc:creator>James Carlson</dc:creator>
    <dc:date>2012-05-09T10:53:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1219">
    <title>Errata classification</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1219</link>
    <description>&lt;pre&gt;Hi,

The following errata sounds reasonable but could people give me their opinion?

    http://www.rfc-editor.org/errata_search.php?eid=1924

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3&amp;lt; at &amp;gt;gmail.com
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Donald Eastlake</dc:creator>
    <dc:date>2012-05-08T21:53:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1218">
    <title>Re: Future of the PPP WG</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1218</link>
    <description>&lt;pre&gt;Hi Bill,

I don't think your personal opinion of Vernon Schryver is relevant or
appropriate to be posted here.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3&amp;lt; at &amp;gt;gmail.com
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Donald Eastlake</dc:creator>
    <dc:date>2011-10-03T04:30:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1217">
    <title>Re: Future of the PPP WG</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1217</link>
    <description>&lt;pre&gt;Hi,

On Wed, Sep 28, 2011 at 9:48 AM, Vernon Schryver &amp;lt;vjs&amp;lt; at &amp;gt;rhyolite.com&amp;gt; wrote:

Actually, you can't make IANA Consideration criteria for assignment
dependent on approval by a Working Group because IETF Working Groups
are considered transient entities, notwithstanding that some WGs have
been around for a long time.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3&amp;lt; at &amp;gt;gmail.com
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Donald Eastlake</dc:creator>
    <dc:date>2011-10-03T04:29:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1216">
    <title>Re: Future of the PPP WG</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1216</link>
    <description>&lt;pre&gt;It _was_ an odd thing for an individual submission, but I wasn't too
worried about it, as it was proposed in a draft sent to the list.

I went back and looked at my list archives, and found that I'd not even
ever read half the messages about it.  It came out of a series of posts on
the Subject: Re: Reigning in "bad" extensions to PPP.

At the time, I did read the first few messages with each new Subject line:
    proposed draft IANA Considerations
    I-D ACTION:draft-schryver-pppext-iana-00.txt
    IANA PPP considerations
    IANA Considerations for PPP to Proposed Standard

Again, what needs to be changed?


I've an informal personal rule going back to the early '90s against
responding to Schryver's usual provocative rants, and had kill filed him
for some years.  I'd say more of a troll than diabolical.
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>William Allen Simpson</dc:creator>
    <dc:date>2011-10-02T11:14:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1215">
    <title>Re: Future of the PPP WG</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1215</link>
    <description>&lt;pre&gt;

You're not alone, Bill: not much attention was called to it (at least in
pppext).  It was an individual submission (kind of ironic, considering
that the evil it purports to fix is the lack of WG review).  IIRC, I was
unaware of its existence until the announcement of its publication.


Not idiotic at all; the author is not an idiot.  Diabolical, maybe, but
not idiotic.

...
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Glen Zorn</dc:creator>
    <dc:date>2011-10-02T06:44:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1214">
    <title>Re: Future of the PPP WG</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1214</link>
    <description>&lt;pre&gt;Glen, what needs to be changed?  I didn't pay any particular attention
to it at the time, but this really looks like a one-off RFC to update
some kind of IANA considerations.  It doesn't appear to be idiotic.

Anything new will have new IANA considerations.
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>William Allen Simpson</dc:creator>
    <dc:date>2011-09-29T11:18:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1213">
    <title>Re: Future of the PPP WG</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1213</link>
    <description>&lt;pre&gt;

RFC 3818 does nothing but require that IANA demand IETF consensus (not
necessarily consensus in this WG) before assigning new numbers in some
address spaces.  So how would changing RFC 3818 be useful and to whom?
How would replacing RFC 3818 help users and implementors of PPP related
protocols, as opposed to helping people with personal needs to be RFC
authors?

If future necessary work can't get IETF consensus to replace RFC
3818 when the need arises, then its necessarity is not a proper
concern of the IETF.

Changing RFC 3818 would only slightly ease publiccation of ill
considered ideas driven not by technical needs but by misunderstanding,
hurt feelings, or vanity like the majority of PPP related IDs for
the last 10 years.


Vernon Schryver    vjs&amp;lt; at &amp;gt;rhyolite.com
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Vernon Schryver</dc:creator>
    <dc:date>2011-09-28T13:48:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1212">
    <title>Re: Future of the PPP WG</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1212</link>
    <description>&lt;pre&gt;
Please clarify: an update in what way?  The existing document requires
"IETF Consensus" for a certain set of protocol numbers in order to
ensure that any work that's done has meaningful review.  I think this is
a good thing, and certainly should not be considered "obsolete."

In the absence of an IETF PPPEXT WG, I'd expect that any "necessary
work" in these areas would be done in the context of (and likely in
service to) some other working group, with others outside that group
solicited for comment as needed.  "PPPEXT" then becomes as necessary to
the process as would be an "ICMPEXT" group.

If anything, I think RFC 3818 should be strengthened, not abandoned.

&lt;/pre&gt;</description>
    <dc:creator>James Carlson</dc:creator>
    <dc:date>2011-09-28T12:32:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1211">
    <title>Re: Future of the PPP WG</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1211</link>
    <description>&lt;pre&gt;
On Sep 27, 2011, at 9:31 PM, Donald Eastlake wrote:


And a "get-together" of PPP old-far^H^H^Htimers?

- Mark


_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Mark Townsley</dc:creator>
    <dc:date>2011-09-28T06:37:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1210">
    <title>Re: Future of the PPP WG</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1210</link>
    <description>&lt;pre&gt;
Actually, there is one useful thing that this WG could do before its
demise: update or obsolete RFC 3818 so that necessary work can be done
when it (the WG) is gone.

...
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Glen Zorn</dc:creator>
    <dc:date>2011-09-28T04:20:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1209">
    <title>Re: Future of the PPP WG</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1209</link>
    <description>&lt;pre&gt;There will not be a PPPEXT meeting in Taiwan.

Probably next week, I'll review this thread and post my conclusions.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3&amp;lt; at &amp;gt;gmail.com

On Thu, Sep 8, 2011 at 6:24 PM, Donald Eastlake &amp;lt;d3e3e3&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:
_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext

&lt;/pre&gt;</description>
    <dc:creator>Donald Eastlake</dc:creator>
    <dc:date>2011-09-27T19:31:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.pppext/1208">
    <title>Re: Future of the PPP WG</title>
    <link>http://permalink.gmane.org/gmane.ietf.pppext/1208</link>
    <description>&lt;pre&gt;hi,

On Sun, Sep 11, 2011 at 3:13 PM, Glen Zorn &amp;lt;glenzorn&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

+1


Cheers,
Jacni


_______________________________________________
Pppext mailing list
Pppext&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/pppext
&lt;/pre&gt;</description>
    <dc:creator>Jacni Qin</dc:creator>
    <dc:date>2011-09-13T03:55:01</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.ietf.pppext">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.ietf.pppext</link>
  </textinput>
</rdf:RDF>
