Re: [68ATTENDEES] standards track wireless network

Tony Hansen <tony@att.com> Tue, 27 March 2007 18:39 UTC

Return-path: <68attendees-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWGZu-000881-DU; Tue, 27 Mar 2007 14:39:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWGZs-00086n-NY for 68attendees@ietf.org; Tue, 27 Mar 2007 14:39:28 -0400
Received: from mail121.messagelabs.com ([216.82.241.195]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HWGZq-0001xY-CE for 68attendees@ietf.org; Tue, 27 Mar 2007 14:39:28 -0400
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-11.tower-121.messagelabs.com!1175020765!9225066!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 3957 invoked from network); 27 Mar 2007 18:39:25 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4) by server-11.tower-121.messagelabs.com with SMTP; 27 Mar 2007 18:39:25 -0000
Received: from attrh.att.com (localhost [127.0.0.1]) by attrh3i.attrh.att.com (8.13.8/8.13.8) with ESMTP id l2RIdPGl014711 for <68attendees@ietf.org>; Tue, 27 Mar 2007 14:39:25 -0400 (EDT)
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by attrh3i.attrh.att.com (8.13.8/8.13.8) with ESMTP id l2RIdL0r014693 for <68attendees@ietf.org>; Tue, 27 Mar 2007 14:39:21 -0400 (EDT)
Received: from [135.210.108.132] (unknown[135.210.108.132](misconfigured sender)) by maillennium.att.com (mailgw1) with ESMTP id <20070327183920gw10010gpqe> (Authid: tony); Tue, 27 Mar 2007 18:39:20 +0000
Message-ID: <460964FB.5070208@att.com>
Date: Tue, 27 Mar 2007 14:39:55 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: 68attendees@ietf.org
Subject: Re: [68ATTENDEES] standards track wireless network
References: <C22ED162.3C275%Jonne.Soininen@nokia.com> <E45C5654-5516-47E8-AD90-0D2EDFC57C9B@daedelus.com>
In-Reply-To: <E45C5654-5516-47E8-AD90-0D2EDFC57C9B@daedelus.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: "Soininen Jonne \(Nokia-NET/Espoo\)" <Jonne.Soininen@nokia.com>
X-BeenThere: 68attendees@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Mailing list for IETF 68 attendees." <68attendees.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/68attendees>, <mailto:68attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/68attendees>
List-Post: <mailto:68attendees@ietf.org>
List-Help: <mailto:68attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/68attendees>, <mailto:68attendees-request@ietf.org?subject=subscribe>
Errors-To: 68attendees-bounces@ietf.org

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