Re: [68ATTENDEES] standards track wireless network

Hi,

Those documents already exist (both venue and network). I'm taking note
about the comments, as new items such as smoke-free considerations are
coming into the list, and plan to convert them to ION:

http://tools.ietf.org/id/draft-palet-ietf-meeting-network-requirements-00.tx
t
http://tools.ietf.org/id/draft-palet-ietf-meeting-venue-selection-criteria-0
4.txt

Regards,
Jordi

> De: Tony Hansen <tony@att.com>
> Responder a: <68attendees-bounces@ietf.org>
> Fecha: Tue, 27 Mar 2007 14:39:55 -0400
> Para: <68attendees@ietf.org>
> CC: "Soininen Jonne (Nokia-NET/Espoo)" <Jonne.Soininen@nokia.com>
> Asunto: Re: [68ATTENDEES] standards track wireless network
> 
> Instead of making it an RFC, it seems perfect fodder for an ION.
> 
> Tony Hansen
> tony@att.com
> 
> Jim Martin wrote:
>>     Actually, this is just /mostly/ right :-)
>> 
>>     There is in fact a document regarding the modern network, but rather
>> than in ID format, it's a set of requirements. We (the volunteer crew)
>> developed this to aid in the process of generating an RFP for the
>> network contractor, and then later as a mechanism to help generate
>> quantifiable "scoring" during the evaluation of the resultant proposals.
>> 
>>     What we don't have is a document which takes those requirements and
>> adds in the hard-won best current practices. We've spoken of generating
>> this document many many times, but due to the considerations you've
>> mentioned, we've just never gotten to the actual /writing/ part.
>> 
>>     - Jim
>> 
>> On Mar 27, 2007, at 12:49 PM, Soininen Jonne (Nokia-NET/Espoo) wrote:
>> 
>>> Hi,
>>> 
>>> There used to be a document (which has not been updated) on the
>>> requirement
>>> of the "terminal room" for the IETF. The draft was mostly about the
>>> network
>>> anyways.
>>> 
>>> The updating of the document stopped, because the requirements where
>>> increasing faster than the people could type and the information in the
>>> document would have been out-dated before it reached RFC. Perhaps the
>>> requirements have become more stable and writing the document might be
>>> possible.
>>> 
>>> In addition, there is another difficulty to write the document: Some
>>> of the
>>> requirements are not easily documentable in portable format. For
>>> instance,
>>> the WLAN network requirements should say that you should forget
>>> everything
>>> you have learned about setting up WLAN networks and ask the people who
>>> has
>>> done this before what actually works and what doesn't in this kind of
>>> environment. Though, it is useful in IETF context, it might not be that
>>> useful outside of it.
>>> 
>>> I think the main reason for not documenting the networking experiences is
>>> actually time. People are pretty burned out after the meeting. Even they
>>> have said before the meeting that they will document everything, after
>>> the
>>> meeting the this promise is often forgotten (been there, done that).
>>> 
>>> These are no excuses not to do the documentation. Somebody just has to
>>> write
>>> it... ;)
>>> 
>>> Cheers,
>>> 
>>> Jonne.
>>> 
>>> 
>>> On 3/26/07 4:39 PM, "ext Michael Richardson" <mcr@sandelman.ottawa.on.ca>
>>> wrote:
>>> 
>> 
>> At one point, the IETF NOC teams were going to write up their
>> experiences.  It would be lovely if the Python (or other conferences)
>> could just say to their hotels:
>>       "please make sure that your network is RFC50xx compliant"
>> 
>> --
>> ]            Bear: "Me, I'm just the shape of a bear."          |
>> firewalls
>> [
>> ]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net
>> architect[
>> ] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device
>> driver[
>> ] panic("Just another Debian GNU/Linux using, kernel hacking,
>> security guy");
>> [
>> 
>> 
>> 
>>>> 
> _______________________________________________
> 68ATTENDEES mailing list
> 68ATTENDEES@ietf.org
> https://www1.ietf.org/mailman/listinfo/68attendees
>>> 
>>> --Jonne Soininen
>>> Nokia
>>> 
>>> Tel: +358 40 527 46 34
>>> E-mail: jonne.soininen@nokia.com
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> 68ATTENDEES mailing list
>>> 68ATTENDEES@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/68attendees
> 
>> _______________________________________________
>> 68ATTENDEES mailing list
>> 68ATTENDEES@ietf.org
>> https://www1.ietf.org/mailman/listinfo/68attendees
> 
> _______________________________________________
> 68ATTENDEES mailing list
> 68ATTENDEES@ietf.org
> https://www1.ietf.org/mailman/listinfo/68attendees

**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

_______________________________________________
68ATTENDEES mailing list
68ATTENDEES@ietf.org
https://www1.ietf.org/mailman/listinfo/68attendees