While reading through this ID: A Uniform Resource Identifier for Geographic
Locations ('geo' URI), I found several minor issues.
Section 2. Introduction
[use of WGS84 reference system]
I wonder if it might be more forward thinking to allow for the optional
specification of the reference
The IETF Trust is considering applying to the U.S. Library of Congress
to obtain an International Standard Serial Number (ISSN) for the RFC
Series and would like community input to inform its decision. The Trust
may take up this matter on June 11th.
An ISSN is applied to serials - print or
Great idea, and I don't see a downside.
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Ray Pelletier [EMAIL PROTECTED]
Date: Wed, 21 May 2008 13:52:09
To:IETF Discussion ietf@ietf.org, IAOC [EMAIL PROTECTED], The IESG [EMAIL
PROTECTED],RFC Editor [EMAIL PROTECTED],
On 5/21/08 2:06 PM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Great idea, and I don't see a downside.
The only possible disadvantage I can see is if they're then
cataloged as a serial rather than having individual call numbers
and individual catalog entries, but since the Library of Congress
Hi,
The Trust has analyzed the advantages, and you included the advantages
in your post.
Has the Trust also analyzed any potential disadvantages? Can you tell
us those as well?
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL
Hi -
From: Melinda Shore [EMAIL PROTECTED]
To: IETF Discussion ietf@ietf.org
Sent: Wednesday, May 21, 2008 11:16 AM
Subject: Re: ISSN for RFC Series under Consideration
...
The only possible disadvantage I can see is if they're then
cataloged as a serial rather than having individual call
On 5/21/08 at 1:52 PM -0400, Ray Pelletier wrote:
The Trust believes there are advantages to indentifying the RFC
Series with an ISSN.
OK, maybe I'm getting suspicious in my (still slowly) advancing years:
Nowhere in the message did I see words like, The Trust has consulted
with
salutcomment vas-tu,la famille aussi?rentre vite dans le site:
www.bicoeur.com inscris toi sur ((butineo)) c'est une bannière jaunetu recevras un code pour appeler et envoyer des sms gratuitement dans le monde entier
___
IETF mailing list
Pete Resnick wrote:
On 5/21/08 at 1:52 PM -0400, Ray Pelletier wrote:
The Trust believes there are advantages to indentifying the RFC
Series with an ISSN.
OK, maybe I'm getting suspicious in my (still slowly) advancing years:
Nowhere in the message did I see words like, The
On 5/21/08 2:19 PM, Randy Presuhn [EMAIL PROTECTED] wrote:
What would it take to get them cataloged individually?
Interest in having them cataloged individually. I believe LC
catalogs everything it receives. I've been out of librarianship
long enough not to know how they receive
On 5/21/08 at 2:36 PM -0400, Ray Pelletier wrote:
The Trust did consult with lawyers, old-crusty-IETFers, RFC Editor,
and found no disadvantages to indentifying the RFC Series with an
ISSN.
[...]
We've done our due diligence, but we respect the community and the
process, and seek its guidance.
Mostly sounds fine, with one small glitch.
At 1:52 PM -0400 5/21/08, Ray Pelletier wrote:
According to the Library of Congress, www.loc.gov/issn/, for serials
available only in online versions, the ISSN should appear on the title
screen or home page and/or in the masthead or other areas where
Naw. The ISSN has to be on the document itself. As you point out,
this isn't something to be done with Internet Drafts, so it falls
naturally to the RFC Editor, not to the individual authors.
Steve
On May 22, 2008, at 3:14 AM, Paul Hoffman wrote:
Mostly sounds fine, with one small
On Wed, May 21, 2008 at 12:14:35PM -0700,
Paul Hoffman [EMAIL PROTECTED] wrote
a message of 23 lines which said:
The value of adding ISSN: 12345678
ISSN: 12345678? I hope we will eat our own dog food and use RFC
3044.
___
IETF mailing list
Steve Crocker wrote:
Naw. The ISSN has to be on the document itself. As you point out,
this isn't something to be done with Internet Drafts, so it falls
naturally to the RFC Editor, not to the individual authors.
The benefit of the new number requires that folk know about it, which
I think there is a bigger issue with encumbering the people of the US for
paying for creating an indexing system for the IETF to prevent the
Chair/Trust from doing its job.
I suggest that this is another stupid idea from the Trust to keep them from
actually answering the question as to what
On 5/21/08 3:36 PM, Dave Crocker [EMAIL PROTECTED] wrote:
The benefit of the new number requires that folk know about it,
I actually don't think that's the case. I mean, I think
it should be on the documents (otherwise there's some small
point to having one, but not a lot) but I think it's real
Ray Pelletier wrote:
...
The Trust believes there are advantages to indentifying the RFC Series
with an ISSN. Among them,
1. Make reference to the series compact and globally unique;
...
More compact than urn:ietf:rfc:?
BR, Julian
___
IETF
Yes, this seems like a good idea and I don't see why anyone would have
to do any work other than the RFC Editor. Are the tools we use really so
brittle that adding a line with ISSN - or urn:ISSN:-
or whatever somewhere in the upper left corner of the first page of an
RFC will break
On Wed May 21 20:49:19 2008, Eastlake III Donald-LDE008 wrote:
Yes, this seems like a good idea and I don't see why anyone would
have
to do any work other than the RFC Editor. Are the tools we use
really so
brittle that adding a line with ISSN - or
urn:ISSN:-
or
The following is an explanation of how to accomplish setting up a path of
communication between two RNET Hosts. Some of you may have already figured this
out... now you have the definitive answer.Consider this; You have two RNET
Hosts, host A and host B. Both hosts wish to communicate with
+1 no brainer
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Pete Resnick
Sent: Wednesday, May 21, 2008 3:06 PM
To: Ray Pelletier
Cc: Working Group Chairs; IAB; IETF Discussion; IAOC; The IESG; RFC
Editor
Subject: Re: [IAOC] ISSN for RFC
On 2008-05-22 07:20, Julian Reschke wrote:
Ray Pelletier wrote:
...
The Trust believes there are advantages to indentifying the RFC Series
with an ISSN. Among them,
1. Make reference to the series compact and globally unique;
...
More compact than urn:ietf:rfc:?
Possibly not, but
So we have reinvented STUN?
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Chad Giffin [EMAIL PROTECTED]
Date: Wed, 21 May 2008 17:09:54
To:ietf@ietf.org
Cc:[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Random Network Endpoint Technology (RNET)
The following is an
On 5/21/08 5:39 PM, Brian E Carpenter [EMAIL PROTECTED] wrote:
Possibly not, but there is still a crusty old world of academic
publications with traditional reference styles out there, and an ISSN
will make it much more straightforward to cite RFCs in peer-reviewed
publications. +1 that it's a
On 5/21/08 5:49 PM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
So we have reinvented STUN?
This is probably closer to Paul Francis's NUTSS stuff without
the cool crankback and especially without resolving the location
problem.
Melinda
___
IETF
The practical benefit I see here is getting the Library of
Congress (and who knows? maybe the British Library, etc.)
to catalog the series as a series, but again I'm unclear on
the practical benefit, since RFCs are incredibly easy to find
*as* RFCs; that is to say, by the information by which the
At Wed, 21 May 2008 17:52:55 -0400,
Melinda Shore wrote:
On 5/21/08 5:39 PM, Brian E Carpenter [EMAIL PROTECTED] wrote:
Possibly not, but there is still a crusty old world of academic
publications with traditional reference styles out there, and an ISSN
will make it much more
So? The rules of academic citation are broken. Take a look at their idiotic
criteria for citing web pages.
Unfortunately the folk who designed the reference manager for office 2008 made
the mistake of taking them seriously. It is not possible to cite urls for
articles as a result.
Sent
I agree with Melinda here. I can't remember ever seeing anything
like an ISBN or an ISSN used as a citation in an academic paper.
Correct, but I have seen a wide variety of ways to cite RFCs
and tying them all back to an ISSN number would be a step forward
IMHO. In any case: at worst,
On May 21, 2008, at 4:49 PM, [EMAIL PROTECTED] wrote:
So we have reinvented STUN?
No, we've moved the state of STUN into each of the routers between the
two hosts, and have to hope we don't have a route flap somewhere.
It's sort of like RSVP.
--
Dean
thanks for the comments, Matt. Responses below:
Matt Mathis wrote:
I reviewed draft-ietf-sipping-overload-reqs-02 at the request of the
transport
area directors. Note that my area of expertise is TCP, congestion control
and
bulk data transport. I am not a SIP expert, and have not been
Lisa,
Could you let us see your summary of the discussion about
(not) documenting the X-headers? I haven't seen any further
comments since Dave's message below, and it appears that the
IESG is ballotting on the document now.
Regards
Brian
On 2008-04-08 06:34, Dave Crocker wrote:
Pete
Excerpts from Melinda Shore at 17:55:57 -0400 on Wed 21 May 2008:
On 5/21/08 5:49 PM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
So we have reinvented STUN?
This is probably closer to Paul Francis's NUTSS stuff without
the cool crankback and especially without resolving the location
While I cannot comment specifically about RFC style, I can say (from my
study of the use of language globally) that there are several conventions in
use for numerical notation using the numerals 0-9, depending on usage.
- The point/period/full stop may be used to separate whole numbers from
72nd IETF Meeting
Dublin, Ireland
July 27-August 1, 2008
Host: Alcatel-Lucent
Registration numbers for Dublin are currently exceeding Paris!
Be sure to make your hotel reservation, there are a limited number of
rooms at the Citywest Hotel. More information on the hotel and how to make
your
36 matches
Mail list logo
