Classic:

IP over everything

(dog optional)

-----Original Message-----
From: ietf-boun...@ietf.org [mailto:ietf-boun...@ietf.org] On Behalf Of Mark 
Nottingham
Sent: Monday, August 16, 2010 8:05 PM
To: Fred Baker
Cc: wgcha...@ietf.org; ietf@ietf.org
Subject: Re: IETF Logo Wear

That's going to be hard to fit on a t-shirt, Fred.

*ducks*


On 17/08/2010, at 8:34 AM, Fred Baker wrote:

> IEN 111, August 1979. The preface reads:
> 
> This document describes the Internet Protocol.  There have been three 
> previous editions of this specification, and the present text draws 
> heavily from them.  There have been many contributors to this document 
> both in terms of concepts and in terms of text.
> 
>                                                           Jon Postel
>                                                           Editor
> 
> I suspect that, as editor, he would blanch a bit at finding anything there 
> attributed specifically to *him*; he would have said - and on occasion did 
> say - "I was there", but would go on to point out that there were many 
> contributors and many contributions. That said, it is the first instance I 
> can find of the Robustness Principle:
> 
>  The implementation of a protocol must be robust.  Each implementation  
> must expect to interoperate with others created by different  
> individuals.  While the goal of this specification is to be explicit  
> about the protocol there is the possibility of differing  
> interpretations.  In general, an implementation should be conservative  
> in its sending behavior, and liberal in its receiving behavior.  That  
> is, it should be careful to send well-formed datagrams, but should  
> accept any datagram that it can interpret (e.g., not object to  
> technical errors where the meaning is still clear).
> 
> The comment, in various forms, is repeated in IENs 112, 123, 124, 128, and 
> 129, and in RFCs 760, 761, 791, and 793.
> 
> 
> On Aug 16, 2010, at 3:09 PM, Sean Turner wrote:
> 
>> I like:
>> 
>> "Be conservative in what you send and liberal in what you accept"
>>    Jon Postel
>> 
>> I'm sure somebody who has been around longer than me can offer up a 
>> date ;)
>> 
>> spt
>> 
>> 
>> Fred Baker wrote:
>>>     There's no place like ::1
>>> On Aug 16, 2010, at 2:01 PM, Philip Nesser wrote:
>>>> We obviously need an IETF branded one of these:  
>>>> http://www.cafepress.com/+theres_127001_infant_bodysuit,111188172
>>>> 
>>>> 
>>>> --->  Phil
>>>> 
>>>> 
>>>> On Mon, Aug 16, 2010 at 8:26 AM, IETF Administrative Director 
>>>> <i...@ietf.org> wrote:
>>>> All;
>>>> 
>>>> At the request of the community the IAOC and the IETF Trust have 
>>>> approved the establishment of an online store from which the 
>>>> community can buy IETF logo wear.
>>>> 
>>>> The store is at CafePress at:  http://www.cafepress.com/ietf
>>>> 
>>>> The store is maintained by the Internet Society and is expected to 
>>>> generate a very modest income, which will be used to offset IETF 
>>>> operational expenses.
>>>> 
>>>> Suggestions for products or designs may be directed to Steve Conte, 
>>>> co...@isoc.org.
>>>> 
>>>> Shouldn't everyone in your family have an IETF logo wear t-shirt?
>>>> 
>>>> Ray Pelletier
>>>> IAD
>>>> _______________________________________________
>>>> Ietf mailing list
>>>> Ietf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf
>>>> 
>>>> _______________________________________________
>>>> Ietf mailing list
>>>> Ietf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> 


--
Mark Nottingham     http://www.mnot.net/

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Reply via email to