Re: [68ATTENDEES] standards track wireless network

[Jim Martin <[e-mail]>]

	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"  
> <[e-mail]>
> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>> 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[
>> ] [e-mail]      http://www.sandelman.ottawa.on.ca/mcr/ | 
>> device
>> driver[
>> ] panic("Just another Debian GNU/Linux using, kernel hacking,  
>> security guy");
>> [
>>
>>
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.6 (GNU/Linux)
>> Comment: Finger me for keys
>>
>> iQEVAwUBRgfNKoCLcPvd0N1lAQJn9AgAuVgEirNvCjIOLjbmRlpuDu1VtpTInAZ4
>> fRN4C28UuQIADoQ9qLsICi6gZFaDSrWkXzWGku9PV2otcRxw0jzjnL53ShbRnvxl
>> qFAo4HWu8dFWOMBuVXo2zCVfZKSUusbb0PpDRJwyThjm+TSG9zYMk/1GAgjy2E8J
>> 7l3eCnGEFxJtMbC7+b5tZn6DyLjvz442Tj3bQjjQ3U6HOGlyV08kpCP2yi59X/BG
>> KQeYnQE/HUPRzVAH4FmEU9KXlRNisGswTpluJCkbw3JfDRDa16X9/2qEa7HImIt3
>> p+0yonpinRIAgl+rSoQJYzKDMDWQSI+26O9YlKDcPBPfPkf+iSdwvQ==
>> =9p17
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> 68ATTENDEES mailing list
>> [e-mail]
>> https://www1.ietf.org/mailman/listinfo/68attendees
>
> -- 
> Jonne Soininen
> Nokia
>
> Tel: [phone]
> E-mail: [e-mail]
>
>
>
> _______________________________________________
> 68ATTENDEES mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/68attendees


_______________________________________________
68ATTENDEES mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/68attendees