On Jul 31, 2009, at 9:40 PM, James M. Polk wrote:
this is a choice between "how can the IETF get money?"
That is something the Trust would have to think about. What we had
been considering was literally licensing a t-shirt company to print
the designs and enabling IETFers to order them. T
On Jul 31, 2009, at 1:23 AM, Simon Josefsson wrote:
I suggest the Trust considers T-shirt designs as code components so
that
the BSD license applies to it. :-)
Do we have to write the license on the shirt, or can we use a URL?
:-)
___
Ietf maili
On Jul 31, 2009, at 12:49 AM, Gregory M. Lebovitz wrote:
Juniper has donated the art for the highly popular IETF74 San
Francisco T-shirt (brown, IPv6 World Tour, "concert" concept) to the
IETF Trust.
Speaking as a Trustee, the Trust thanks Juniper for the donation.
This is a cool design, I agree.
With that said, I think a discussion needs to occur on the
devaluation of the importance of what the shirt means - were it to be
distributed to any/many folks that did not attend an IETF.
There have been several other cool designs from IETFs past, most
notably
On Tue, Jul 28, 2009 at 01:15:20PM -0400, Thomas Narten wrote:
> Can we please drop everything after the comma? (I'm not sure how to
> reword it, since I think the only point that needs to be made is that
> the nomcom as discretion not to publish names, for whatever reason.)
The usual way to say
On 31-Jul-2009, at 07:30, Tobias Markmann wrote:
The protocol that seems to handle such DNS updates seems to be RFC
2136 which is around since 1997. I wonder how far this RFC is
implemented among authoritative DNS servers and whether that RFC is
the right approach to solve the problem of d
Way back in the early days of the IETF, the email address was used for
adding people to the mailing list for the WG. But that was a long
time ago, when many mailing lists weren't so automated. :-)
-David Borman
On Jul 31, 2009, at 9:06 AM, Pekka Savola wrote:
On Fri
hey folks, sorry for my offtopic spam
check this:
http://money.ninemsn.com.au/article.aspx?id=844226
i cant believe at the end closed source eats itself *pmpl*
regards
MarcM
--
Les enfants teribbles - research / deployment
Marc Manthey
Vogelsangerstrasse 97
D - 50823 Köln - Germany
Vogel
I think it's right. nice art, nice colour and wonderful design.
Coko Tracy
---Message original---
De : Richard Barnes
Date : 7/31/2009 12:00:00 PM
A : dcroc...@bbiw.net
Cc : ietf@ietf.org; 74attend...@ietf.org; 75attend...@ietf.org
Sujet : Re: [74attendees] [75attendees] IETF74 T-Shi
It would seem in the open spirit if the IETF to make this a standing
order for t-shirt art, wouldn't it?
On Friday, July 31, 2009, Dave CROCKER wrote:
>
>
> Gregory M. Lebovitz wrote:
>
> I have been asked about this several times this week, so I'd like to clarify
> here for all.
>
> Juniper has
Gregory M. Lebovitz wrote:
I have been asked about this several times this week, so I'd like to
clarify here for all.
Juniper has donated the art for the highly popular IETF74 San Francisco
Greg,
Many thanks!
Especially in light of Bob Hinden's cautionary reference to the Wasa, at the
In general, I don't really understand what problem this draft is trying to
solve. A clearer statement in the abstract or introduction explaining
_why_ a common registry is a good thing would be very useful.
It might also be worth considering separating the Link: header and the
registry into tw
--On Thursday, July 30, 2009 16:09 -0700 Stephan Wenger
wrote:
> Hi Brian,
>
> One can sit in a WG meeting for years, and never incur a
> disclosure obligation under BCP78, correct? Just sitting
> there and not saying/writing/contributing a thing does not
> trigger a disclosure obligation. S
Pekka,
E-mail address are useful data. Anyhow, I would not able to replay to
you without using your address ;-)
and how to know which "John Smith" is the real participant?
+1 for Brian Carpenter
Thanks,
Géza
On Fri, Jul 31, 2009 at 9:06 AM, Pekka Savola wrote:
> On Fri, 31 Jul 2009, Bria
Hi,
I'm currently looking for a convenient solution for the problem of manual
configuration of DNS RRs. The usual setup is that you configure domain and
IP relation in your DNS configuration, in zonefiles or some other kind of
DB, and nearly the same configuration is done in your server application
"Gregory M. Lebovitz" writes:
> I have been asked about this several times this week, so I'd like to
> clarify here for all.
>
> Juniper has donated the art for the highly popular IETF74 San
> Francisco T-shirt (brown, IPv6 World Tour, "concert" concept) to the
> IETF Trust. This was done because
I have been asked about this several times this week, so I'd like to
clarify here for all.
Juniper has donated the art for the highly popular IETF74 San
Francisco T-shirt (brown, IPv6 World Tour, "concert" concept) to the
IETF Trust. This was done because a) many people wanted to buy more
of
I see value in working on a "linked" congestion control scheme (work
consisting in architecting and determining how efficient such scheme
would be compared to current practice/congestion control schemes).
I have a couple of comments/concerns though:
- The BoF presentation considers that the TCP
On Fri, 31 Jul 2009, Brian E Carpenter wrote:
I agree with Alissa that having an explicit privacy policy would be a
good idea, but the fact of participation in an open standards process
certainly cannot be considered a private matter. Exactly the opposite,
in fact.
Indeed, but why do the blue s
19 matches
Mail list logo
