Return-Path: <adamsobieski@hotmail.com>
X-Original-To: p2prg@ietfa.amsl.com
Delivered-To: p2prg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
 with ESMTP id EFDD721F887C for <p2prg@ietfa.amsl.com>;
 Sun, 16 Dec 2012 11:07:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level: 
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[AWL=0.260,
 BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I6U101JPu4nE for
 <p2prg@ietfa.amsl.com>; Sun, 16 Dec 2012 11:07:49 -0800 (PST)
Received: from snt0-omc4-s5.snt0.hotmail.com (snt0-omc4-s5.snt0.hotmail.com
 [65.55.90.208]) by ietfa.amsl.com (Postfix) with ESMTP id 0A7CC21F887A for
 <p2prg@irtf.org>; Sun, 16 Dec 2012 11:07:48 -0800 (PST)
Received: from SNT002-W162 ([65.55.90.199]) by snt0-omc4-s5.snt0.hotmail.com
 with Microsoft SMTPSVC(6.0.3790.4675); Sun, 16 Dec 2012 11:07:47 -0800
X-EIP: [VX2ZGfSjWkCG0O0CbZM0LHLgmvQj35r1]
X-Originating-Email: [adamsobieski@hotmail.com]
Message-ID: <SNT002-W1625EE3D9C025F17A2F916DC5330@phx.gbl>
Content-Type: multipart/alternative;
 boundary="_4f20fd17-5ebc-407f-a3b2-59d4d0c74f4b_"
From: Adam Sobieski <adamsobieski@hotmail.com>
To: "p2prg@irtf.org" <p2prg@irtf.org>
Date: Sun, 16 Dec 2012 19:07:47 +0000
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Dec 2012 19:07:47.0753 (UTC)
 FILETIME=[A2F12990:01CDDBC0]
Subject: [p2prg] NNTP 2.0
X-BeenThere: p2prg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Peer-to-Peer Research Group <p2prg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/p2prg>,
 <mailto:p2prg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/p2prg>
List-Post: <mailto:p2prg@irtf.org>
List-Help: <mailto:p2prg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/p2prg>,
 <mailto:p2prg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 19:07:50 -0000

--_4f20fd17-5ebc-407f-a3b2-59d4d0c74f4b_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Internet Research Task Force=2C
Peer-to-Peer Research Group=2C

Greetings.  In October of 2006=2C the IETF released RFC 3977 (http://tools.=
ietf.org/html/rfc3977) which updated the NNTP protocol=2C codifying many of=
 the additions made over the years since the 1986 RFC 977 (http://tools.iet=
f.org/html/rfc977).  Topically to peer-to-peer research and development=2C =
it is possible that an entirely decentralized and distributed forum system =
could be both researched and developed=2C abstractly referred to as NNTP 2.=
0 herein=2C achieving all of the 1986 and 2006 design goals=2C scaled to cu=
rrent Internet usage=2C utilizing 2012 state-of-the-art computer science in=
cluding with regard to distributed computing=2C distributed databases=2C an=
d peer-to-peer technologies.

Metadata models for messages=2C e.g. blog article metadata models=2C can be=
 applicable to updating both email and NNTP computer networking protocols. =
 Beyond searchable subject strings and text content=2C then=2C could be use=
r-specified folksonomic keywords=2C categories=2C and other metadata.  Meta=
data models can enhance the searchability of blogs=2C mailing lists=2C and =
forums.  Additionally=2C as with blogs=2C NNTP 2.0 could utilize pinging co=
nfigurably by users for each of their messages and per individual messages.=
  Hyperlinks can interconnect the HTTP-based Web and NNTP 2.0 forum content=
.

PKI and digital signatures enhance scenarios with the distributed storage o=
f user-generated content.  Additionally=2C just as NNTPS utilizes TLS=2C TL=
S can enhance a peer-to-peer NNTP 2.0.
=20
A distributed forum system would contain multiple forums=2C each forum woul=
d contain multiple threads=2C and each thread would contain multiple messag=
es.  Forum messages=2C with enhanced metadata=2C digitally signed by users=
=2C can be interrelated by typed links where a forum message could be in re=
sponse to a number of other messages from various threads in various forums=
 on the distributed system enhancing content discovery and navigation.  NNT=
P 2.0 would add to the features available with NNTP.

With the aforementioned blog-based pings=2C configurable by users=2C Web-ba=
sed search engine technology could be interoperable with a distributed=2C d=
ecentralized=2C peer-to-peer NNTP 2.0 system.  NNTP 2.0 could=2C additional=
ly=2C include distributed search technologies also enhanced by the aforemen=
tioned metadata models.



Kind regards=2C

Adam Sobieski 		 	   		  =

--_4f20fd17-5ebc-407f-a3b2-59d4d0c74f4b_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>Internet Research Task Force=2C<=
br/>
Peer-to-Peer Research Group=2C<br/>
<br/>
Greetings.  In October of 2006=2C the IETF released RFC 3977 (<a href=3D"ht=
tp://tools.ietf.org/html/rfc3977">http://tools.ietf.org/html/rfc3977</a>) w=
hich updated the NNTP protocol=2C codifying many of the additions made over=
 the years since the 1986 RFC 977 (<a href=3D"http://tools.ietf.org/html/rf=
c977">http://tools.ietf.org/html/rfc977</a>).  Topically to peer-to-peer re=
search and development=2C it is possible that an entirely decentralized and=
 distributed forum system could be both researched and developed=2C abstrac=
tly referred to as NNTP 2.0 herein=2C achieving all of the 1986 and 2006 de=
sign goals=2C scaled to current Internet usage=2C utilizing 2012 state-of-t=
he-art computer science including with regard to distributed computing=2C d=
istributed databases=2C and peer-to-peer technologies.<BR>
<br/>
Metadata models for messages=2C e.g. blog article metadata models=2C can be=
 applicable to updating both email and NNTP computer networking protocols. =
 Beyond searchable subject strings and text content=2C then=2C could be use=
r-specified folksonomic keywords=2C categories=2C and other metadata.  Meta=
data models can enhance the searchability of blogs=2C mailing lists=2C and =
forums.  Additionally=2C as with blogs=2C NNTP 2.0 could utilize pinging co=
nfigurably by users for each of their messages and per individual messages.=
  Hyperlinks can interconnect the HTTP-based Web and NNTP 2.0 forum content=
.<BR>
<br/>
PKI and digital signatures enhance scenarios with the distributed storage o=
f user-generated content.  Additionally=2C just as NNTPS utilizes TLS=2C TL=
S can enhance a peer-to-peer NNTP 2.0.<BR>
<br/>=20
A distributed forum system would contain multiple forums=2C each forum woul=
d contain multiple threads=2C and each thread would contain multiple messag=
es.  Forum messages=2C with enhanced metadata=2C digitally signed by users=
=2C can be interrelated by typed links where a forum message could be in re=
sponse to a number of other messages from various threads in various forums=
 on the distributed system enhancing content discovery and navigation.  NNT=
P 2.0 would add to the features available with NNTP.<BR>
<br/>
With the aforementioned blog-based pings=2C configurable by users=2C Web-ba=
sed search engine technology could be interoperable with a distributed=2C d=
ecentralized=2C peer-to-peer NNTP 2.0 system.  NNTP 2.0 could=2C additional=
ly=2C include distributed search technologies also enhanced by the aforemen=
tioned metadata models.<BR>
<br/>
<br/>
<br/>
Kind regards=2C<br/>
<br/>
Adam Sobieski 		 	   		  </div></body>
</html>=

--_4f20fd17-5ebc-407f-a3b2-59d4d0c74f4b_--
