If only there were some uniform resource locator system, whereby we could use a
string to both identify and locate such a document, and include such a string
*in* our specifications.
A pipe dream, I know...
On 09/05/2011, at 10:41 AM, Steven Bellovin wrote:
On May 8, 2011, at 7:44 58PM,
And since we are tripping back through memory lane, Jon Postel and I
co-authored RFC 980 which tells you how to order protocol documents,
including the collections we made at SRI. Not sure I remember the
price for these books, but to quote from the RFC itself:
For hardcopy distribution from
Ole Jacobsen wrote:
We had a special line printer for this purpose and a machine called a
burster, something I have not seen or heard about in about 25 years.
If you refer to the machine that separates the sheets into individual
pages when fed listing paper (continuous, but not on a roll,
Hi,
Today if you're an IEEE type, and you wonder where to find RFC 793, or
you're wondering what RFC 793 is about, and you look it up in IEEE
Xplore, the online library that all electrical engineers use, and that
their employers have site subscriptions for, you'll find ... nothing.
Yes, you
Agreeing with John here re: it's just a bug.
IEEE Xplore regularly does deals (read: free) to add publishers to the
digital library. It is part of the network effect from their perspective: if
you are more likely to get a hit using their service, you are more likely to
use the service.
We
SM:
s much as I would like to use the IESG as a scapegoat, the reality is that
IETF working groups also work briskly to on impediments. Section 4 mentions
that the rules that prohibit references to documents at lower maturity
levels are a major cause of stagnation in the advancement of
glassey [tglas...@earthlink.net]
Hmmm. Does the IETF publication license allow this? the commercial
resale of its documents?
There is no copyright notice on RFC 793, but it was published after
1976, so the question would revolve around the implicit license
involved in publishing RFCs at the
--
Terre natale !
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
On 09.05.2011 16:34, Russ Housley wrote:
...
My person experience with advancing documents is that downrefs are a
significant hindrance. As you point out, procedures have been adopted to
permit downrefs, but they are not sufficient. We often see Last Call repeated
just to resolve a downref
Hi Julian,
Julian Reschke wrote:
On 09.05.2011 16:34, Russ Housley wrote:
...
My person experience with advancing documents is that downrefs are a
significant hindrance. As you point out, procedures have been
adopted to permit downrefs, but they are not sufficient. We often
see Last
On 09.05.2011 18:10, Alexey Melnikov wrote:
Hi Julian,
Julian Reschke wrote:
On 09.05.2011 16:34, Russ Housley wrote:
...
My person experience with advancing documents is that downrefs are a
significant hindrance. As you point out, procedures have been adopted
to permit downrefs, but they
Bob,
What you presumably remember, but others reading this may not,
was just how many comments Jon made about the impossibility of
preventing fools from throwing their money away.
John Klensin,
Indeed, I do remember. ;-)
Bob Braden.
___
Ietf
On May 9, 2011, at 6:51 AM, Eric Burger wrote:
Agreeing with John here re: it's just a bug.
IEEE Xplore regularly does deals (read: free) to add publishers to the
digital library. It is part of the network effect from their perspective: if
you are more likely to get a hit using their
Hi Russ,
At 07:34 09-05-2011, Russ Housley wrote:
My person experience with advancing documents is that downrefs are a
significant
Thanks for sharing that.
hindrance. As you point out, procedures have been adopted to
permit downrefs, but they are not sufficient. We often see Last
Call
On 05/09/2011 07:51, Worley, Dale R (Dale) wrote:
Companies sell tap water in bottles at prices higher than those of
gasoline...
Fortunately gasoline is catching up fast. :)
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth
Subject: [www.ietf.org/rt #37575] transcript of IETF-80 tech plenary discussion?
From: Wanda Lo via RT age...@ietf.org
Date: Mon, 09 May 2011 10:28:23 -0700
To: jeff.hod...@kingsmountain.com
Hi Jeff,
http://www.ietf.org/proceedings/80/minutes/plenaryt.txt
The minutes are based on Renee's
In article 516ebea6-e089-4952-ae33-de799e375...@mnot.net you write:
If only there were some uniform resource locator system, whereby we
could use a string to both identify and locate such a document, and
include such a string *in* our specifications.
It exists, it's called a DOI. I don't
A simpler and more pragmatic approach is to include a statement in the
boilerplate of every RFC that says, RFCs are available free of charge online
from ...
The copyright rules would prohibit anyone from removing this statement. If
someone pays $47 for a copy and then reads this statement, he
+1
The elegance and simplicity of this is quite nice.
d/
--
Dave Crocker
bbiw.net
Steve Crocker st...@shinkuro.com wrote:
A simpler and more pragmatic approach is to include a statement in the
boilerplate of every RFC that says, RFCs are available free of charge online
from ... The copyright
--On Monday, May 09, 2011 23:41 + John Levine
jo...@iecc.com wrote:
In article 516ebea6-e089-4952-ae33-de799e375...@mnot.net you
write:
If only there were some uniform resource locator system,
whereby we could use a string to both identify and locate
such a document, and include such a
This reminds me of what a colleague once said about government-run lotteries:
A tax on people who are bad at math. In this case the fools don't seem to be
throwing all that many dollars away (at least not per document).
Ross
-Original Message-
From: ietf-boun...@ietf.org
On Mon, 9 May 2011, Steve Crocker wrote:
A simpler and more pragmatic approach is to include a statement in the boilerplate of
every RFC that says, RFCs are available free of charge online from ...
The copyright rules would prohibit anyone from removing this statement. If
someone pays $47
On 09.05.2011 19:07, SM wrote:
...
For what it is worth, the draft was intended for publication as an
Internet Standard (STD 71). As I see it, the problem here is that
Intended status: Standards Track is assumed to be Proposed Standard.
As the Document Shepherd runs a draft through Id-nits, he
On 10.05.2011 03:44, John C Klensin wrote:
John,
Depends on where you look. DOIs are popular in some
communities, URNs in others, and, of course, some communities
have not discovered either. For most purposes, DOIs and URNs
can be considered functionally equivalent, but one of the
differences
The IESG has approved the following document:
- 'Export of Structured Data in IPFIX'
(draft-ietf-ipfix-structured-data-06.txt) as a Proposed Standard
This document is the product of the IP Flow Information Export Working
Group.
The IESG contact persons are Dan Romascanu and Ron Bonica.
A URL
The IESG has approved the following document:
- 'Protocol Support for High Availability of IKEv2/IPsec'
(draft-ietf-ipsecme-ipsecha-protocol-06.txt) as a Proposed Standard
This document is the product of the IP Security Maintenance and
Extensions Working Group.
The IESG contact persons are
The IESG has approved the following document:
- 'The ERP Local Domain Name DHCPv6 Option'
(draft-ietf-hokey-ldn-discovery-10.txt) as a Proposed Standard
This document is the product of the Handover Keying Working Group.
The IESG contact persons are Stephen Farrell and Sean Turner.
A URL of
The IESG has received a request from the isms WG (isms) to consider the
following document:
- 'Transport Layer Security (TLS) Transport Model for the Simple Network
Management Protocol (SNMP) '
RFC 5953 as a Draft Standard
Two issues were raised during the first Last Call: 1) references
A new Request for Comments is now available in online RFC libraries.
RFC 6232
Title: Purge Originator Identification TLV for
IS-IS
Author: F. Wei, Y. Qin,
Z. Li, T. Li,
J. Dong
A new Request for Comments is now available in online RFC libraries.
RFC 6233
Title: IS-IS Registry Extension for Purges
Author: T. Li, L. Ginsberg
Status: Standards Track
Stream: IETF
Date: May 2011
30 matches
Mail list logo
