Date:Wed, 19 Jul 2006 03:06:10 +0200
From:Henrik Levkowetz [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
| Ok. So I'm not sure what you propose here - should we not require
| rsync and ftp mirroring capability, or should we ask for it, and not
| specify
Ok. So I'm not sure what you propose here - should we not require
rsync and ftp mirroring capability, or should we ask for it, and not
specify chapter and verse regarding version etc.? I'd certainly be
very unhappy completely abandoning the rsync capability.
IMO, the SOW should have some
Starting from Europe, San Diego seems to be no harder to reach
than any other major US city. The SPF route from Geneva
has two hops (e.g. via EWR or JFK).
I agree that major hub airports are a little easier to reach,
but maybe that's why we can get meeting space more easily
in non-hub cities?
Speaking only for myself, I have always read the words
Further recourse is available... at the beginning of
section 6.5.3 of RFC 2026 to mean that an appeal to the
ISOC Board can only follow rejection of an appeal by both
the IESG and IAB.
I think this is essentially right. That is, it makes
Folks interested in the topic of minutes may want to go find a copy of
(the expired) draft-meyer-agendas-and-minutes-00.txt
And if they think this is a good direction to go, encourage the
authors to update the document and push it forward through the system.
Thomas
Brian E Carpenter wrote:
Starting from Europe, San Diego seems to be no harder to reach
than any other major US city. The SPF route from Geneva
has two hops (e.g. via EWR or JFK).
I agree that major hub airports are a little easier to reach,
but maybe that's why we can get meeting space
Let me relate my *EXPERIENCE* with some interim meetings (lemonade). [I
suppose data is the closest we have to 'working code.'] Meeting held in
Dallas: 9 participants. Meeting held in Vancouver: 10 participants.
Meeting held in London: 14 participants. Meeting held in Beijing: 21
Clint Chaplin wrote:
One data point: IEEE 802 is in San Diego this week, and I've met at
least one attendee who flew through LAX to get here; that is, he took
LAX - SAN as his last leg.
the flight is so short, one can feel guilty taking it. however the effort to
rent a car from an airport,
I use ftp all the time to access the RFCs. I use direct web URLs all the
time to access the RFCs. I *occasionally* use rfc-editor.org's web
interface. I agree with Henrik.
Tony Hansen
[EMAIL PROTECTED]
Henrik Levkowetz wrote:
It may be that the level of detail specification
Dave,
A few points:
If a non-hub venue offers dramatic net price savings, fabulous facilities, or
some other strong justification, it makes sense to go there.
Otherwise, a non-hum city forces virtually the entire set of attendees to:
1. Experience an extra flight, each way, with its
Dave,
Actually, airline hubs increase the risk of depending on a single airline, since most hubs (at least in the US) are dominated by a single airline, such as Northwest in Minneapolisand Detroit, US Airways in Philly and Pittsburgh, American in Dallas, Delta in Altanta and Salt Lake City,
On Wed Jul 19 14:53:59 2006, Dave Crocker wrote:
1. Since we know that The London metropolitan area has excellent
Internet
connectivity and bandwidth, the problems you experienced must have
been due to
the particular meeting site and not the region.
Indeed. The meeting site had confused Full
Dave Crocker wrote:
Clint Chaplin wrote:
One data point: IEEE 802 is in San Diego this week, and I've met at
least one attendee who flew through LAX to get here; that is, he took
LAX - SAN as his last leg.
the flight is so short, one can feel guilty taking it. however the effort to
I did this the last time we where in San Diego. The only thing to be
concerned about is at least United operated small planes with not to
good frequency (at least then) and tends to fill up on Saturday
afternoon and Sunday morning (I noticed).
Then going from International to domestic at
Hi Thomas,
on 2006-07-19 14:33 Thomas Narten said the following:
IMO, the SOW should have some wording that requires/implies that
information available via web pages must also be provided in a
mirror-friendly way. The principle is that that the info can be easily
be replicated on mirror
Eliot Lear wrote:
Minneapolis *is* a hub for Northwest.
4. More generally, secondary venues have less total airline seating capacity
and
the concentration of our 1200-1400 attendees flying in and out close together
usually has a noticeable impact on their flights.
This is unlikely to
On 19-jul-2006, at 15:45, Dave Crocker wrote:
I agree that major hub airports are a little easier to reach,
but maybe that's why we can get meeting space more easily
in non-hub cities?
If a non-hub venue offers dramatic net price savings, fabulous
facilities, or
some other strong
Dave Crocker wrote:
Clint Chaplin wrote:
One data point: IEEE 802 is in San Diego this week, and I've met at
least one attendee who flew through LAX to get here; that is, he took
LAX - SAN as his last leg.
the flight is so short, one can feel guilty taking it. however the effort to
rent a
On 7/19/06 1:47 PM, Iljitsch van Beijnum [EMAIL PROTECTED] wrote:
All in all, San Diego seems like a pretty bad choice for a meeting
place: it's even hard to get to from inside the US, and it's as far
as you can get from Europe without leaving the continental US.
I'm not crazy about it either,
The limitation on lack of eating and drinking places near the venue is
because of the choice of the particular hotel. IEEE is in the Hyatt
on the waterfront, and Old Town is well within walking distace, with
lots of restaurant choices.
On 7/19/06, Andy Bierman [EMAIL PROTECTED] wrote:
Dave
Another data point; San Diego is hosting Comic-Con this weekend:
they're expecting on the order of 100,000 attendees.
On 7/19/06, Eliot Lear [EMAIL PROTECTED] wrote:
Dave,
A few points:
If a non-hub venue offers dramatic net price savings, fabulous facilities, or
some other strong
This is my understanding.
However this rises a problem in cases like RFC 3683. Because in this
case (this what the IESG claims) the delay for appealing the RFC 3863
text is over. This is why I spoke of RFC 3863 application, the same
as there is usually a text and a running code. In a BCP
Hi,
in response to the first TSVAREA meeting in Montreal, we have set up
a corresponding area-wide mailing list.
The purpose of the TSVAREA meeting (and the associated mailing list)
is to inform about and discuss important issues, developments and
work within the transport area. The area
Point 2 is exactly my point. Places which should have the best
connectivity (tons of international interconnect and PSTN connectivity)
can still be defeated by stupid firewall tricks and no host with
international PSTN conference services.
Conversely, places that North Americans might consider
The IESG has approved the following document:
- 'Registration of media type audio/mobile-xmf '
draft-kosonen-mobile-xmf-mediatype-01.txt as an Informational RFC
This document has been reviewed in the IETF but is not the product of an
IETF Working Group.
The IESG contact person is Ted
The IESG has received a request from an individual submitter to consider the
following document:
- 'Document Shepherding From Working Group Last Call to IESG Approval '
draft-ietf-proto-wgchair-doc-shepherding-07.txt as an Informational RFC
The IESG plans to make a decision in the next few
A new Request for Comments is now available in online RFC libraries.
RFC 4568
Title: Session Description Protocol (SDP) Security
Descriptions for Media Streams
Author: F. Andreasen, M. Baugher,
D. Wing
A new Request for Comments is now available in online RFC libraries.
RFC 4536
Title: The application/smil and application/smil+xml Media
Types
Author: P. Hoschka
Status: Informational
Date: July 2006
A new Request for Comments is now available in online RFC libraries.
RFC 4569
Title: Internet Assigned Number Authority (IANA)
Registration of the Message Media Feature
Tag
Author: G. Camarillo
Status:
A new Request for Comments is now available in online RFC libraries.
RFC 4566
Title: SDP: Session Description Protocol
Author: M. Handley, V. Jacobson,
C. Perkins
Status: Standards Track
Date: July 2006
A new Request for Comments is now available in online RFC libraries.
RFC 4573
Title: MIME Type Registration for RTP
Payload Format for H.224
Author: R. Even, A. Lochbaum
Status: Standards Track
Date: July
A new Request for Comments is now available in online RFC libraries.
RFC 4571
Title: Framing Real-time Transport Protocol (RTP)
and RTP Control Protocol (RTCP) Packets
over Connection-Oriented Transport
Author:
A new Request for Comments is now available in online RFC libraries.
RFC 4586
Title: Extended RTP Profile for Real-time
Transport Control Protocol (RTCP)-Based Feedback:
Results of the Timing Rule Simulations
33 matches
Mail list logo
