[LINK] The RFC process

stephen at melbpc.org.au stephen at melbpc.org.au
Mon Apr 13 02:37:20 AEST 2009

Interesting rfc's (27) this fortnight maybe


Eg: http://tools.ietf.org/html/rfc5514  (snip)

                     IPv6 over Social Networks

   There is a lack of IPv6 utilization in early 2009; this is partly
   linked to the fact that the number of IPv6 nodes is rather low.  This
   document proposes to vastly increase the number of IPv6 hosts by
   transforming all Social Networking platforms into IPv6 networks.

   This will immediately add millions of IPv6 hosts to the existing IPv6
   Internet.  This document includes sections on addressing and
   transport of IPv6 over a Social Network.  A working prototype has
   been developed.

1.  Introduction

   While the IPv6 protocols are well-known for years, not every host
   uses IPv6 (at least in March 2009), and most network users are not
   aware of what IPv6 is or are even afraid by IPv6 because it is

   On the other hand, Social Networks (like Facebook, LinkedIn, etc.)
   are well-known by users and the usage of those networks is huge.

   This document describes how to leverage Social Networks in order to
   make more people aware of IPv6 and to add several thousands of IPv6
   routers to the Internet.

2.  Architecture

   With IPv6 over Social Network (IPoSN):

   o  Every user is a router with at least one loopback interface;

   o  Every friend or connection between users will be used as a point-
      to-point link.

   On social networks users want to have multiple friends, partners, or
   relations with other users. Therefore, it can be expected that there
   is a heavily meshed network among these users. This will provide for
   good IPv6 connectivity because each user (IPoSN router) will be IPv6
   connected to all his/her friends (IPoSN neighbor routers).." (snip)


This RFC  .. non-ASCII email addresses .. thinking about it how can the
net claim to be global, if it wants ASCII email headers? This net would
be ubiquitous if everyone with Chinese & Japanese (etc etc) ISP account
names, enjoy email with their own 'real' names? Seems a digital divide?

 http://tools.ietf.org/html/rfc5504  (snip)

Traditional mail systems handle only ASCII characters in SMTP envelope
and mail header fields. The Email Address internationalization (UTF8SMTP)
extension allows UTF-8 characters in SMTP envelope & mail header fields. 

To avoid rejecting internationalized email messages when a server in the
delivery path does not support the UTF8SMTP extension, some sort of
converting mechanism is required.  This document describes ..." Otoh?

And, here's the Official 40th Year RFC, RFC Announcement :)


Network Working Group                                         RFC Editor
Request for Comments: 5540                                       USC/ISI
Category: Informational                                     7 April 2009

                            40 Years of RFCs

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.


   This RFC marks the 40th anniversary of the RFC document series.

1.  RFCs and Jon Postel

   Forty years ago today, the first Request for Comments document, RFC
   1, was published at UCLA [RFC1].  This was the first of a series that
   currently contains more than 5400 documents (roughly 160,000 pages)
   on computer networking in general and on the Internet protocols in
   particular.  The RFC series emerged from the US government-funded
   research efforts that created the ARPANET and later the Internet.
   When the IETF was formed in the mid-1980s, RFCs became the primary
   publication vehicle for IETF standards, and thus became centered on
   the vendor and user communities.

   For the first 29 years, Jon Postel [Postel] was *the* RFC Editor,
   until his untimely death in October 1998.  Postel, with substantial
   help from Joyce K. Reynolds, was responsible for the collection,
   editing, online publication, and archiving of the RFC documents.
   From 1978 until 1998, Postel was a research scientist at the USC
   Information Sciences Institute (USC/ISI) in Marina del Rey,
   California.  Postel was also the original IANA as well as Director of
   the Computer Networks Division at ISI.

   Upon the occasion of the 30th anniversary of RFC 1 and as a tribute
   to the massive contribution of Jon Postel, the RFC Editor published
   RFC 2555 [RFC2555] on April 7, 1999.  This RFC contained
   recollections from three networking pioneers: Steve Crocker who wrote
   RFC 1, Vint Cerf whose long-range vision continues to guide us, and
   Jake Feinler who played a key role in the middle years of the RFC


   Ten more years have now passed, and we have reached the 40th
   anniversary of the RFC series.  The series has more than doubled in
   size during the last ten years, and it is expected to continue far
   into the future.  All the good things said in RFC 2555 still hold
   true ten years later.

   We should, however, note some changes that have occurred over the
   past ten years.

   o  After Jon passed away, Joyce Reynolds and Bob Braden put together
      a small organization at USC/ISI to continue the RFC Editor
      function.  This was motivated by a desire to honor Postel by
      continuing his remarkable effort and to provide a service to the
      Internet community.

   o  Funding of the RFC Editor, which had been supported by the US
      government until 1998, was taken over by the Internet Society.
      During 1998-2006, ISOC funded the RFC Editor under a series of
      annual contracts and extensions.  ISOC put the function out for
      competitive bid for 2007 (USC/ISI was selected to provide RFC
      Editor services from 2007-2009), and the contract will be put out
      to bid again for post-2009.

      During 2009 there will be a significant transition for the RFC
      Editor function, as some new organization or set of organizations
      takes over this service that has been performed at USC/ISI
      continuously since 1978.

   o  Many improvements have increased the efficiency and transparency
      of the RFC editorial process [RFCed09].

   o  The RFC Editor formed an RFC Editorial Board, a group of people
      with broad and deep knowledge of the Internet and networking.  One
      of its major functions is to assist the RFC Editor by reviewing
      RFCs in the Independent Submission stream.

   o  An email list, rfc-interest at rfc-editor.org, was created to obtain
      community input on the RFC Editor functions.

RFC Editor                   Informational                      [Page 2]
RFC 5540                    40th Anniversary                7 April 2009

2.  Security Considerations

   This document does not raise any security issues.

3.  Acknowledgments

   It has been an honor for USC/ISI to serve the community during the
   past 31 years.

4.  Informative References

   [Postel]  "Remembering Jonathan B. Postel",

   [RFCed09] Braden, R., Ginoza, S., and A. Hagens, "The RFC Editor
             Function at ISI", <http://www.rfc-editor.org/
             RFCeditor.at.ISI.pdf>, January 2009.

   [RFC1]    Crocker, S., "Host Software", RFC 1, April 1969.

   [RFC2555] RFC Editor, et al., "30 Years of RFCs", RFC 2555, April

Author's Address

   RFC Editor


> > * How the Internet Got Its Rules
> >
> > By S.D. CROCKER  Published: April 7, 2009
> > http://www.nytimes.com/2009/04/07/opinion/07crocker.html?ref=internet
> >
> > First Request for Comment: http://tools.ietf.org/html/rfc1
> >
> >
> > TODAY is an important date in the history of the Internet: the 40th
> > anniversary of what is known as the "Request for Comments".


Message sent using MelbPC WebMail Server

More information about the Link mailing list