IETF Logo Mail Archive

Re: [fun] status of the homenet effort

Robert Raszuk <robert@raszuk.net> Fri, 01 July 2011 11:45 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: fun@ietfa.amsl.com
Delivered-To: fun@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 406EC21F8647 for <fun@ietfa.amsl.com>; Fri, 1 Jul 2011 04:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e3-aFSQyKUNA for <fun@ietfa.amsl.com>; Fri, 1 Jul 2011 04:45:54 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id C959321F8637 for <fun@ietf.org>; Fri, 1 Jul 2011 04:45:54 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMIAOSyDU6rRDoI/2dsb2JhbABSmG2Oc3erS54DhjIEkjKEdos9
X-IronPort-AV: E=Sophos;i="4.65,457,1304294400"; d="scan'208";a="351325769"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-3.cisco.com with ESMTP; 01 Jul 2011 11:45:54 +0000
Received: from [192.168.1.51] (ams-raszuk-2-87113.cisco.com [10.55.99.78]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p61Bjrj6027245 for <fun@ietf.org>; Fri, 1 Jul 2011 11:45:54 GMT
Message-ID: <4E0DB36D.60303@raszuk.net>
Date: Fri, 01 Jul 2011 13:45:49 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: fun@ietf.org
References: <CA31F3ED.4AB6%jason.weil@twcable.com>
In-Reply-To: <CA31F3ED.4AB6%jason.weil@twcable.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [fun] status of the homenet effort
X-BeenThere: fun@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: "FUture home Networking \(FUN\)" <fun.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fun>, <mailto:fun-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fun>
List-Post: <mailto:fun@ietf.org>
List-Help: <mailto:fun-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fun>, <mailto:fun-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 11:45:55 -0000

While rereading the proposed charter I have two questions ..

1. Is documentation or new tools specification development for home 
network troubleshooting either manual or automated in or outside of 
charter ? How about diagnostics in reachability to internal subnets or 
different hosts on the internet ?

2. How about multihoming with seamless switchover ?

I think those will make home networking a bit easier ?

---

Example for 1: What happens if I can ping/trace a destination, browse 
it's web site just fine, but my cgi script dies ? And I have a real case 
like this which honestly I am not sure how to troubleshoot. Server side 
reports no errors at all in the log. MTU is low as it can be.

/* Well I found the solution but will not say it on this list as I am 
afraid Jari and Mark will unsubscribe me ;-) */

Cheers,
R.

v2.23.0 | Report a Bug | By Email