IETF Logo Mail Archive

Re: [89attendees] When does the IETF network officially come up?

"Ali C. Begen (abegen)" <abegen@cisco.com> Sun, 02 March 2014 07:57 UTC

Return-Path: <abegen@cisco.com>
X-Original-To: 89attendees@ietfa.amsl.com
Delivered-To: 89attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDA631A0C13 for <89attendees@ietfa.amsl.com>; Sat, 1 Mar 2014 23:57:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Level:
X-Spam-Status: No, score=-15.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIwDHtodGSyE for <89attendees@ietfa.amsl.com>; Sat, 1 Mar 2014 23:56:57 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id A67481A0C0D for <89attendees@ietf.org>; Sat, 1 Mar 2014 23:56:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=995; q=dns/txt; s=iport; t=1393747015; x=1394956615; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=vkyYHsvcLBfj5vMK5r88NkIQegawQTyvJkoPajzuAOU=; b=K9Zk8F1JGaj2N2ofRSO9weaA+YzlR/tHS9JbdM3LqhvxLl5SRKxRlqSO vw734QMuPHC6y4/tHtsNRXGIBVi7E2HLeLJRCnstQla9v4VtTQkqxZEHX m9W+u+UyV+XzOKWjqPtMqz2mbnis1JKAG582LZ+JjGQo1TWzr7IeOXxjU 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAAbkElOtJV2b/2dsb2JhbABXA4JlITtXwSGBEhZ0giUBAQEDAUkwEAIBCBguMiUCBA4Fh3EIActYF44mIxAHEYMTgRQEmDySK4Mtgio
X-IronPort-AV: E=Sophos;i="4.97,571,1389744000"; d="scan'208";a="307441707"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-2.cisco.com with ESMTP; 02 Mar 2014 07:56:46 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s227ukqJ011012 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 2 Mar 2014 07:56:46 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Sun, 2 Mar 2014 01:56:45 -0600
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: Dave Oran <daveoran@orandom.net>
Thread-Topic: [89attendees] When does the IETF network officially come up?
Thread-Index: Ac81PqhBFgFPbBl7T+SLgUBoKoqZcgANzEKAAACrzwAAAGvjAP//qVUegABqzICAAAOrgIAAo9YAgAAagoCAAANpgIAAcIAA
Date: Sun, 2 Mar 2014 07:56:44 +0000
Message-ID: <2495F7E9-9723-41C5-9E14-0E558DA76429@cisco.com>
References: <884C5283-E928-478B-922A-9B9347A41EDB@cisco.com> <CACbUdyqLQFT8y+w0mMynceLrYFyXpT7oPZYZnApJGOcYHk+Q9g@mail.gmail.com> <6C1E7012-198E-41B5-BC0A-0D89307CB6A8@isoc.org> <9AD8EDB5-DA02-4956-9AB4-FF965CFA714E@isc.org> <9B214294-5B21-43A5-9E1F-08B6630323F1@cisco.com> <p06240602cf3790386cf9@dhcp-5432.meeting.ietf.org> <7108CB28-3F79-4265-8FC3-8076FC918416@cisco.com> <CACB24MuG23BN4RP-Lq5z5fnub44m9SqPTWZs0dVhMse=0ovZ8Q@mail.gmail.com> <EDFFFBDE-24CE-45E0-8226-767042EC8BC8@orandom.net> <0F397CED-CD57-4C5E-B55B-5A0D9D737C69@orandom.net>
In-Reply-To: <0F397CED-CD57-4C5E-B55B-5A0D9D737C69@orandom.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.250.188]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <5E7DA3BFA08B2945B80D57E0C8B5F717@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/89attendees/NltwZXSg9sCluCb817VL9RYGmNw
Cc: Richard Barnes <richard.barnes@gmail.com>, Colin Doyle <cdoyle@verilan.com>, Ray Pelletier <rpelletier@isoc.org>, attendees <89attendees@ietf.org>, Randall Gellens <randy@qti.qualcomm.com>, Jim Martin <jrmii@isc.org>
Subject: Re: [89attendees] When does the IETF network officially come up?
X-BeenThere: 89attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 89 attendees that have opted in to the list." <89attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/89attendees>, <mailto:89attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/89attendees/>
List-Post: <mailto:89attendees@ietf.org>
List-Help: <mailto:89attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/89attendees>, <mailto:89attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Mar 2014 07:57:04 -0000

Did you check the wireless signal information? Could it be too much noise somewhere around your room? Cannot say anything about the wired connection.


On Mar 2, 2014, at 3:14 AM, David R Oran <daveoran@orandom.net> wrote:

> 
> On Mar 2, 2014, at 1:01 AM, David R Oran <daveoran@orandom.net> wrote:
> 
>> My room on the 4th floor has now also gone to s…
>> Can’t stay associated with the AP for more than 10 seconds at a time.
>> In some cases this is too little time to even get a DHCP IPv4 address.
>> 
> And when I do ping times go between 200ms and 5 Seconds, with loss of 37%. Thats on the ietf SSID
> 
> --- www.ietf.org ping statistics ---
> 125 packets transmitted, 78 packets received, 37.6% packet loss
> round-trip min/avg/max/stddev = 140.323/1480.633/5322.551/1536.355 ms
> 
> Time to have the NOC folks do the ritual totentanz with the hotel an BT people? Seems this is beginning to look it might be one of the problematic venues...

v2.8.7 | Report a Bug | By Email