
From lars.eggert@nokia.com  Fri May  7 07:44:38 2010
Return-Path: <lars.eggert@nokia.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB34F3A691E for <homegate@core3.amsl.com>; Fri,  7 May 2010 07:44:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.065
X-Spam-Level: 
X-Spam-Status: No, score=-5.065 tagged_above=-999 required=5 tests=[AWL=-1.066, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M9NniwV4ptfR for <homegate@core3.amsl.com>; Fri,  7 May 2010 07:44:38 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 87E6A3A67B5 for <homegate@ietf.org>; Fri,  7 May 2010 07:44:34 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o47EiKik006821 for <homegate@ietf.org>; Fri, 7 May 2010 09:44:21 -0500
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 7 May 2010 17:44:19 +0300
Received: from mgw-sa02.ext.nokia.com ([147.243.1.48]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Fri, 7 May 2010 17:44:19 +0300
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-sa02.ext.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o47EiIvE020679 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <homegate@ietf.org>; Fri, 7 May 2010 17:44:18 +0300
From: Lars Eggert <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96 at fit.nokia.com
Content-Type: multipart/signed; boundary=Apple-Mail-92-730967398; protocol="application/pkcs7-signature"; micalg=sha1
Date: Fri, 7 May 2010 17:43:38 +0300
Message-Id: <0278F321-9CF7-4F07-AF11-1ADAE82ECFB9@nokia.com>
To: homegate@ietf.org
Mime-Version: 1.0 (Apple Message framework v1078)
X-Mailer: Apple Mail (2.1078)
X-OriginalArrivalTime: 07 May 2010 14:44:19.0699 (UTC) FILETIME=[C6860C30:01CAEDF3]
X-Nokia-AV: Clean
Subject: [homegate] wanted: your old/spare NAT home router
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Lars Eggert <lars.eggert@nokia.com>, Markku Kojo <kojo@cs.helsinki.fi>, Seppo Hatonen <shatonen@cs.helsinki.fi>
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 May 2010 14:44:39 -0000

--Apple-Mail-92-730967398
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

for a measurement study done together with Markku Kojo's team at the =
University of Helsinki, we're looking to collect as many different NAT =
home routers as possible. If you have an old clunker or otherwise unused =
box lying around somewhere, please contact me off-list. I'll cover =
shipping via DHL. Feel free to forward this email as you see fit.

The boxes will find a permanent home at the University of Helsinki. =
Study results will be published openly. The intent is that this =
collection become a resource for the community to be shared for future =
studies.=20

Thanks,
Lars=

--Apple-Mail-92-730967398
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGbDCCAyUw
ggKOoAMCAQICEAdjk36sXKbnVn15S0/qUp0wDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDYxNTExMjYxNFoXDTEwMDYxNTExMjYx
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA7mR8A+Pn0/FsUkMX6Pyjw+FL3IFcJk8GaKV5VJ40TMI0Wh8oq20cqA9X
uqnVDW9WztKwH+o+msJenLwWpprbpJm4TImYGbnUJxYyN8gb81aiX1Bw2xCpJ5z3H2+8DsReJLuY
Rdl4bVvaIxLIL4odmfsRwzPyNkOK8LRtfl6OPcaDOlFWzbikULfIVGGu7BqK4lxQSpYwwpZkOMOB
6nnBSfUOtBEmqO+qZG/nL/JxWFV5vxQgg4XHbsMMTxFf6+ji18BD09BUIfDLTuJoCzFmQhrM9vLT
VuRhHWSL20LoafGjXv6mPt3i9IGJHpVb2dMQUgOgRyWHTKiUJVU/rUTdWwIDAQABo14wXDAqBgUr
ZQEEAQQhMB8CAQAwGjAYAgEEBBNMMnVNeWZmQk5VYk5KSmNkWjJzMCAGA1UdEQQZMBeBFWxhcnMu
ZWdnZXJ0QG5va2lhLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBADUx+67n98wt
I1vydB90HeSZP4Y64VCxxb0NxGGFvfc2+JdVKeHJ/xT+l+ygYKsWNwJJprkPi4WZ5G0crkq4VK1H
5drEJIztpSPVfWI05vPidaaGuuuCR+6MvJMtOTEYEvc/6eovBnkrzRf9x5x5EyuJXAWTeuBADg80
QI3vQ1tZMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTAT
BgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUg
Q29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIG
A1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25h
bC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjEL
MAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNV
BAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUA
A4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAK
MNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7
n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAw
QwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJl
ZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRl
TGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9M
Ibj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg
T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAxAwggMMAgEBMHYw
YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAq
BgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAHY5N+rFym51Z9eUtP
6lKdMAkGBSsOAwIaBQCgggFvMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF
MQ8XDTEwMDUwNzE0NDM0N1owIwYJKoZIhvcNAQkEMRYEFNX/caU5+kjbUgavNsoTpnqKuQbZMIGF
BgkrBgEEAYI3EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGlu
ZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBD
QQIQB2OTfqxcpudWfXlLT+pSnTCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw
IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVy
c29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQB2OTfqxcpudWfXlLT+pSnTANBgkqhkiG9w0BAQEF
AASCAQDPLr8K9OPt5XgYODIKiGQS/pVcJVVhkHrPfn+2kO/ISs+aIg5jcDzehHu/wyfwsCIlCjJg
60N8LfjUb+IH5lQTGS5F8BCSnVWnJ/z6aD4vQ3PtyBNtOFRW9E7RQLrwerRzikPuNZLRwBO8eHZY
4Tq5swhwQ4UH88hNwb7O90QuLL0PpVxYWtYIk0TISBUDVMu4oLUNIgAh8haJxdXwAjVhGUG+zPnX
e76loEVMLn1gcGbqmJLrP6vgf15jbU+OGxkU8lfPF0TzV+rsjExfhtM6sJxW9XHcFDT9IDOc3o8M
A5scj5q+xr3wPL9zSndmKwASD5ApWjzQSJSrlRsHqy/kAAAAAAAA

--Apple-Mail-92-730967398--

From dwing@cisco.com  Fri May  7 08:02:51 2010
Return-Path: <dwing@cisco.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 451233A6B69 for <homegate@core3.amsl.com>; Fri,  7 May 2010 08:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.114
X-Spam-Level: 
X-Spam-Status: No, score=-9.114 tagged_above=-999 required=5 tests=[AWL=-1.115, BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D9xd68ORp1RT for <homegate@core3.amsl.com>; Fri,  7 May 2010 08:02:49 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 842D13A6B3C for <homegate@ietf.org>; Fri,  7 May 2010 08:02:28 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAJAEfI40urR7H+/2dsb2JhbACHXYEUiGuMO3GlNplbhRUEg0I
X-IronPort-AV: E=Sophos;i="4.52,348,1270425600"; d="scan'208";a="323996890"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 07 May 2010 15:02:16 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o47F2GpT021050 for <homegate@ietf.org>; Fri, 7 May 2010 15:02:16 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <homegate@ietf.org>
Date: Fri, 7 May 2010 08:02:15 -0700
Message-ID: <022e01caedf6$4840e270$38a66b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acrt9kfyOxGVfZhLQm2PNWwUaSAsHA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Subject: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 May 2010 15:02:51 -0000

As we continue to design PCP (port control protocol), a worry is restart
avalanches caused by a metropolitan-wide power outage/restoration event.
However, restart avalanche concerns are not unique to PCP; restart avalanches
are also a problem for DHCP servers, DNS servers (as devices query for things
like pool.ntp.org), NTP servers, SIP proxies, XMPP servers, and so on.

The restart avalanche problem has been discussed before in the context of VoIP
devices in PacketCable.  Text exists in Section 7.4.3.5 of PacketCable's NCS
specification, titled "Fighting the Restart Avalanche",
http://www.cablelabs.com/specifications/PKT-SP-NCS1.5-I03-070412.pdf and in
Section 4.4.6 of RFC3435, titled "Fighting the Restart Avalanche",
http://tools.ietf.org/html/rfc3435#section-4.4.6


I would prefer that HOMEGATE describe the problem and require the customer
premise router's coldstart initialization be randomly delayed.  The
alternative is that each protocol include a similar mechanism (waste of code,
testing, etc.) and the risk is a device will include both its own delay and a
per-protocol delay, adding unnecessary delay to coldstart initialization.

Thoughts?

-d

(Thanks to Flemming Andreasen for the citations to the PacketCable specs.)


From marc.blanchet@viagenie.ca  Fri May  7 08:06:25 2010
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9CB3B3A6851 for <homegate@core3.amsl.com>; Fri,  7 May 2010 08:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level: 
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=-0.930,  BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ezChzsPb2ZkM for <homegate@core3.amsl.com>; Fri,  7 May 2010 08:06:24 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by core3.amsl.com (Postfix) with ESMTP id 0863A3A6957 for <homegate@ietf.org>; Fri,  7 May 2010 08:06:24 -0700 (PDT)
Received: from mbl.lan (modemcable144.164-201-24.mc.videotron.ca [24.201.164.144]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 612F620D1B for <homegate@ietf.org>; Fri,  7 May 2010 11:06:11 -0400 (EDT)
Message-ID: <4BE42C62.30305@viagenie.ca>
Date: Fri, 07 May 2010 11:06:10 -0400
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: homegate@ietf.org
References: <022e01caedf6$4840e270$38a66b80@cisco.com>
In-Reply-To: <022e01caedf6$4840e270$38a66b80@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 May 2010 15:06:25 -0000

FYI, IPv6 Neighbor discovery also has that anti-restart avalanche 
mechanism. RFC4861.

Marc.

Le 10-05-07 11:02, Dan Wing a écrit :
> As we continue to design PCP (port control protocol), a worry is restart
> avalanches caused by a metropolitan-wide power outage/restoration event.
> However, restart avalanche concerns are not unique to PCP; restart avalanches
> are also a problem for DHCP servers, DNS servers (as devices query for things
> like pool.ntp.org), NTP servers, SIP proxies, XMPP servers, and so on.
>
> The restart avalanche problem has been discussed before in the context of VoIP
> devices in PacketCable.  Text exists in Section 7.4.3.5 of PacketCable's NCS
> specification, titled "Fighting the Restart Avalanche",
> http://www.cablelabs.com/specifications/PKT-SP-NCS1.5-I03-070412.pdf and in
> Section 4.4.6 of RFC3435, titled "Fighting the Restart Avalanche",
> http://tools.ietf.org/html/rfc3435#section-4.4.6
>
>
> I would prefer that HOMEGATE describe the problem and require the customer
> premise router's coldstart initialization be randomly delayed.  The
> alternative is that each protocol include a similar mechanism (waste of code,
> testing, etc.) and the risk is a device will include both its own delay and a
> per-protocol delay, adding unnecessary delay to coldstart initialization.
>
> Thoughts?
>
> -d
>
> (Thanks to Flemming Andreasen for the citations to the PacketCable specs.)
>
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate


-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN news service: http://reeves.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca


From swmike@swm.pp.se  Fri May  7 09:17:32 2010
Return-Path: <swmike@swm.pp.se>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1A1E3A6A7F for <homegate@core3.amsl.com>; Fri,  7 May 2010 09:17:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.433
X-Spam-Level: 
X-Spam-Status: No, score=-4.433 tagged_above=-999 required=5 tests=[AWL=-0.784, BAYES_50=0.001, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cC9IFQXG2O2n for <homegate@core3.amsl.com>; Fri,  7 May 2010 09:17:31 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by core3.amsl.com (Postfix) with ESMTP id DA1C53A6A70 for <homegate@ietf.org>; Fri,  7 May 2010 09:17:24 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 584A89E; Fri,  7 May 2010 18:17:07 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 56E8C9A; Fri,  7 May 2010 18:17:07 +0200 (CEST)
Date: Fri, 7 May 2010 18:17:07 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dan Wing <dwing@cisco.com>
In-Reply-To: <022e01caedf6$4840e270$38a66b80@cisco.com>
Message-ID: <alpine.DEB.1.10.1005071759040.3685@uplift.swm.pp.se>
References: <022e01caedf6$4840e270$38a66b80@cisco.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: homegate@ietf.org
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 May 2010 16:17:32 -0000

On Fri, 7 May 2010, Dan Wing wrote:

> I would prefer that HOMEGATE describe the problem and require the customer
> premise router's coldstart initialization be randomly delayed.

Is that really the best way to solve this (if you by this means minutes of 
backoff instead of tens of seconds?)

I'd rather see more intelligent backoff if the initial request failed, 
because we don't want to delay customer getting their access restored when 
they cold-reboot (or initial-startup) on purpose.

Quite a substantial part of the population power-off their equipment when 
they don't use it (to save power and to protect against power-surges etc).

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From dwing@cisco.com  Fri May  7 09:51:31 2010
Return-Path: <dwing@cisco.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44E043A6881 for <homegate@core3.amsl.com>; Fri,  7 May 2010 09:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.037
X-Spam-Level: 
X-Spam-Status: No, score=-9.037 tagged_above=-999 required=5 tests=[AWL=-1.038, BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t50nySCk4NND for <homegate@core3.amsl.com>; Fri,  7 May 2010 09:51:30 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 0337E3A6805 for <homegate@ietf.org>; Fri,  7 May 2010 09:51:30 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al0IANPh40urR7Hu/2dsb2JhbACHXYEUlShxpguZTYJQgkUEg0I
X-IronPort-AV: E=Sophos;i="4.52,349,1270425600"; d="scan'208";a="126411531"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 07 May 2010 16:51:17 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o47GpH6N009938; Fri, 7 May 2010 16:51:17 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Mikael Abrahamsson'" <swmike@swm.pp.se>
References: <022e01caedf6$4840e270$38a66b80@cisco.com> <alpine.DEB.1.10.1005071759040.3685@uplift.swm.pp.se>
Date: Fri, 7 May 2010 09:51:17 -0700
Message-ID: <02bc01caee05$83436640$38a66b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcruAMB4UXL+y+yqThidqEBrZj46rwAACj7Q
In-Reply-To: <alpine.DEB.1.10.1005071759040.3685@uplift.swm.pp.se>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Cc: homegate@ietf.org
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 May 2010 16:51:31 -0000

> > I would prefer that HOMEGATE describe the problem and 
> > require the customer
> > premise router's coldstart initialization be randomly delayed.
> 
> Is that really the best way to solve this (if you by this 
> means minutes of backoff instead of tens of seconds?)
>
> I'd rather see more intelligent backoff if the initial 
> request failed, because we don't want to delay customer 
> getting their access restored when they cold-reboot (or 
> initial-startup) on purpose.

I am purposefully not discussing the duration of the delay,
or if the delay is fixed or based on some 
random_value*exponential backoff.

Rather, I am first trying to see if HOMEGATE feels restart 
avalanche is something in HOMEGATE's scope.

> Quite a substantial part of the population power-off their 
> equipment when they don't use it (to save power and to 
> protect against power-surges etc).

That can be accomodated by 'the detection of a local 
user activity' which short-cuts the delay.  Anything that
differentiates an unattended device from an attended
device would be sufficient.  For examples: pressing and 
holding the 'power-on' button or some other button, or 
detecting it was the physical power switch being toggled
(versus mains power being restored).

One idea to avoid restart delay is for the network to
signal the CP router (e.g., using DHCP) that the network
is (or is not) currently experiencing a restart avalanche 
and the CP router should delay (or should not delay) its 
initialization.  This would allow the DHCP server to 
protect the rest of the network elements from the 
avalanche restart.  It is just one idea.

But rather than details such as that, I would like to 
first understand if HOMEGATE wants to include restart 
avalanche into its scope.

-d


From paul.hoffman@vpnc.org  Fri May  7 10:05:23 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D5A43A67E5 for <homegate@core3.amsl.com>; Fri,  7 May 2010 10:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.929
X-Spam-Level: 
X-Spam-Status: No, score=-0.929 tagged_above=-999 required=5 tests=[AWL=-1.483, BAYES_50=0.001, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9RtZ920nw2E for <homegate@core3.amsl.com>; Fri,  7 May 2010 10:05:22 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id B784F3A65A6 for <homegate@ietf.org>; Fri,  7 May 2010 10:05:22 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o47H4MFt045203 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 May 2010 10:04:24 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p062408c0c809f6cd6098@[10.20.30.158]>
In-Reply-To: <02bc01caee05$83436640$38a66b80@cisco.com>
References: <022e01caedf6$4840e270$38a66b80@cisco.com> <alpine.DEB.1.10.1005071759040.3685@uplift.swm.pp.se> <02bc01caee05$83436640$38a66b80@cisco.com>
Date: Fri, 7 May 2010 10:04:20 -0700
To: "Dan Wing" <dwing@cisco.com>, "'Mikael Abrahamsson'" <swmike@swm.pp.se>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: homegate@ietf.org
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 May 2010 17:05:23 -0000

At 9:51 AM -0700 5/7/10, Dan Wing wrote:
> > > I would prefer that HOMEGATE describe the problem and
> > > require the customer
>> > premise router's coldstart initialization be randomly delayed.
>>
>> Is that really the best way to solve this (if you by this
>> means minutes of backoff instead of tens of seconds?)
>>
>> I'd rather see more intelligent backoff if the initial
>> request failed, because we don't want to delay customer
>> getting their access restored when they cold-reboot (or
>> initial-startup) on purpose.
>
>I am purposefully not discussing the duration of the delay,
>or if the delay is fixed or based on some
>random_value*exponential backoff.
>
>Rather, I am first trying to see if HOMEGATE feels restart
>avalanche is something in HOMEGATE's scope.

It would only be in scope if it was the gateway that was the one doing the restart. If it is a server behind a gateway that is initiating the restart, the gateway should not participate in avalanche prevention. That is, I would *not* want a gateway to say "I just started up, and now I see a request from something behind me, and I know that request is on my do-not-avalanche list, so I'm going to delay that by a random amount".

Having said that, I would like to see a generic model for intelligent backoff that could be used in protocols, including those that are used in gateways. Once that is established, listing which protocols that gateways themselves use that should observe that model should be in scope here.

> > Quite a substantial part of the population power-off their
>> equipment when they don't use it (to save power and to
>> protect against power-surges etc).
>
>That can be accomodated by 'the detection of a local
>user activity' which short-cuts the delay.  Anything that
>differentiates an unattended device from an attended
>device would be sufficient.  For examples: pressing and
>holding the 'power-on' button or some other button, or
>detecting it was the physical power switch being toggled
>(versus mains power being restored).
>
>One idea to avoid restart delay is for the network to
>signal the CP router (e.g., using DHCP) that the network
>is (or is not) currently experiencing a restart avalanche
>and the CP router should delay (or should not delay) its
>initialization.  This would allow the DHCP server to
>protect the rest of the network elements from the
>avalanche restart.  It is just one idea.

...and a good one. There could also be a generic, trusted, ultra-low-overhead service on a network that the gateway or host behind the gateway could ask either before it does something, or when it gets an anomalous result (a "try again later" response, no reply when it really expects one, and so on). This could also protect a DHCP server if done correctly.

--Paul Hoffman, Director
--VPN Consortium

From fred@cisco.com  Fri May  7 13:58:33 2010
Return-Path: <fred@cisco.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D63513A695B for <homegate@core3.amsl.com>; Fri,  7 May 2010 13:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.065
X-Spam-Level: 
X-Spam-Status: No, score=-109.065 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_05=-1.11, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iN0yl1qlnHcJ for <homegate@core3.amsl.com>; Fri,  7 May 2010 13:58:32 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 9A5873A69D3 for <homegate@ietf.org>; Fri,  7 May 2010 13:58:32 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.52,350,1270425600"; d="scan'208";a="109199538"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 07 May 2010 20:58:20 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o47KwDEm026532; Fri, 7 May 2010 20:58:14 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Fri, 07 May 2010 13:58:19 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Fri, 07 May 2010 13:58:19 -0700
Mime-Version: 1.0 (Apple Message framework v1078)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <alpine.DEB.1.10.1005071759040.3685@uplift.swm.pp.se>
Date: Fri, 7 May 2010 13:58:08 -0700
Message-Id: <605D7502-E9F8-4737-A3F9-72C16A32A391@cisco.com>
References: <022e01caedf6$4840e270$38a66b80@cisco.com> <alpine.DEB.1.10.1005071759040.3685@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1078)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: homegate@ietf.org
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 May 2010 20:58:33 -0000

randomization is a good thing, and exponential backoffs are a proven =
thing. Personally, I would recommend having, on the Nth request, the =
thing wait a random number of milliseconds between 2^(N-1) and 2^N =
seconds between retries.

On May 7, 2010, at 9:17 AM, Mikael Abrahamsson wrote:

> On Fri, 7 May 2010, Dan Wing wrote:
>=20
>> I would prefer that HOMEGATE describe the problem and require the =
customer
>> premise router's coldstart initialization be randomly delayed.
>=20
> Is that really the best way to solve this (if you by this means =
minutes of backoff instead of tens of seconds?)
>=20
> I'd rather see more intelligent backoff if the initial request failed, =
because we don't want to delay customer getting their access restored =
when they cold-reboot (or initial-startup) on purpose.
>=20
> Quite a substantial part of the population power-off their equipment =
when they don't use it (to save power and to protect against =
power-surges etc).
>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate

http://www.ipinc.net/IPv4.GIF


From rdroms.ietf@gmail.com  Fri May  7 15:21:44 2010
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FAAE3A6994 for <homegate@core3.amsl.com>; Fri,  7 May 2010 15:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.342
X-Spam-Level: 
X-Spam-Status: No, score=-2.342 tagged_above=-999 required=5 tests=[AWL=0.257,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ApwUr2Wl8fhF for <homegate@core3.amsl.com>; Fri,  7 May 2010 15:21:39 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id B86543A6869 for <homegate@ietf.org>; Fri,  7 May 2010 15:21:38 -0700 (PDT)
Received: by gyh4 with SMTP id 4so957087gyh.31 for <homegate@ietf.org>; Fri, 07 May 2010 15:21:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=MUQOL3rKJlEbzbFAb9GimVHq9uk6BAB/c48gfAcZhVU=; b=fGxaBmO1ODVwQRTYg3LaWUiHa/iJmyxo2KmfNLGjU+BEJmWWlrZSp7R0L8fctC72Xe 1O4X6IIsRIUfTzapSOefwbGt5JMP1pqoFk2DrWjuPYZuDhNp3LG8EeNFtgO0z7WAV6AJ LA3oOn2xubBDcEW+GQ/isSM2TDEusBgEL5NAs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=i55hTVuk5FQyVGlOgwzXgB7tD9eLvyB7i0U0/BiYnOkU+BnrLWP7Bui6E5FQwI15QT N/WoMMpGdMWjtYu6rzYvDL6p2OCqXdd7ncd9RGhL55Vh9Mk+R/+tHtR6rki3f8LG3nx7 s9mhxUBc8ZcXs+yNRhRpG4hxQT7cThCACE484=
Received: by 10.231.191.145 with SMTP id dm17mr325182ibb.17.1273270883596; Fri, 07 May 2010 15:21:23 -0700 (PDT)
Received: from bxb-rdroms-8711.cisco.com (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id bk12sm877305ibb.20.2010.05.07.15.21.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 07 May 2010 15:21:22 -0700 (PDT)
Message-Id: <665BE908-5BDE-46E2-B815-401D4FD97668@gmail.com>
From: Ralph Droms <rdroms.ietf@gmail.com>
To: Dan Wing <dwing@cisco.com>
In-Reply-To: <022e01caedf6$4840e270$38a66b80@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 7 May 2010 18:21:19 -0400
References: <022e01caedf6$4840e270$38a66b80@cisco.com>
X-Mailer: Apple Mail (2.936)
Cc: homegate@ietf.org
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 May 2010 22:21:44 -0000

I agree in principle...

...but a couple of devils in the details include:

* is the same initial short and randomized delay appropriate for all  
protocols?
* how would the delay interact with existing randomized delays; e.g.,  
in DHCP and ND

- Ralph

On May 7, 2010, at 11:02 AM 5/7/10, Dan Wing wrote:

> As we continue to design PCP (port control protocol), a worry is  
> restart
> avalanches caused by a metropolitan-wide power outage/restoration  
> event.
> However, restart avalanche concerns are not unique to PCP; restart  
> avalanches
> are also a problem for DHCP servers, DNS servers (as devices query  
> for things
> like pool.ntp.org), NTP servers, SIP proxies, XMPP servers, and so on.
>
> The restart avalanche problem has been discussed before in the  
> context of VoIP
> devices in PacketCable.  Text exists in Section 7.4.3.5 of  
> PacketCable's NCS
> specification, titled "Fighting the Restart Avalanche",
> http://www.cablelabs.com/specifications/PKT-SP-NCS1.5-I03-070412.pdf  
> and in
> Section 4.4.6 of RFC3435, titled "Fighting the Restart Avalanche",
> http://tools.ietf.org/html/rfc3435#section-4.4.6
>
>
> I would prefer that HOMEGATE describe the problem and require the  
> customer
> premise router's coldstart initialization be randomly delayed.  The
> alternative is that each protocol include a similar mechanism (waste  
> of code,
> testing, etc.) and the risk is a device will include both its own  
> delay and a
> per-protocol delay, adding unnecessary delay to coldstart  
> initialization.
>
> Thoughts?
>
> -d
>
> (Thanks to Flemming Andreasen for the citations to the PacketCable  
> specs.)
>
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate


From rdroms.ietf@gmail.com  Fri May  7 15:25:06 2010
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99B203A6869 for <homegate@core3.amsl.com>; Fri,  7 May 2010 15:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level: 
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V3mT2oJfMkpx for <homegate@core3.amsl.com>; Fri,  7 May 2010 15:25:04 -0700 (PDT)
Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by core3.amsl.com (Postfix) with ESMTP id 34D363A67A1 for <homegate@ietf.org>; Fri,  7 May 2010 15:25:04 -0700 (PDT)
Received: by qyk11 with SMTP id 11so2252441qyk.13 for <homegate@ietf.org>; Fri, 07 May 2010 15:24:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=bbMIUg+YUIphoGuX71l7UfNPtL6VDxrVKasOo/kGDUc=; b=eHbk5PlhQNWhWgCODj/7niF3Wspof21nrRDu2x8le/FRQRs1Ms3oXZmC/L9C5nqSbr H9W+J9VryJkvlna0qeG48HGGkwQl0yN2sInJHdqm+DFteWbuZIWToSF0xLJD0QIxvtAU 8/jX/txVPw5+KONpzcSoqIQ5m6MhWwuHd5b10=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=Aa0kqOdSgZa+EkX8Iabm1jBl66fvhvKOrgC1L7yd9v5jyJhCoHQ4RXVWh0xOTtwSCQ wUbvSlc4ijSwEtQ+oH0tfQ7Gk37iF9RzEmFJvEX6mg4F7EEI+FVAdXMXXur/dcoCi47I kfefauJeDsCQHjAABmPejWIv4HjJABF62RJNQ=
Received: by 10.229.220.202 with SMTP id hz10mr458714qcb.23.1273271088307; Fri, 07 May 2010 15:24:48 -0700 (PDT)
Received: from bxb-rdroms-8711.cisco.com (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id g19sm1465794qcq.11.2010.05.07.15.24.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 07 May 2010 15:24:47 -0700 (PDT)
Message-Id: <DC4EAD37-8C90-4713-A091-EFE5CD4D12BE@gmail.com>
From: Ralph Droms <rdroms.ietf@gmail.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <605D7502-E9F8-4737-A3F9-72C16A32A391@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 7 May 2010 18:24:45 -0400
References: <022e01caedf6$4840e270$38a66b80@cisco.com> <alpine.DEB.1.10.1005071759040.3685@uplift.swm.pp.se> <605D7502-E9F8-4737-A3F9-72C16A32A391@cisco.com>
X-Mailer: Apple Mail (2.936)
Cc: homegate@ietf.org
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 May 2010 22:25:06 -0000

Considering the multitude of protocols involved and the lack of  
clarity about what constitutes "failure" and "retry", I think the only  
sensible system-wide delay would be to wait some short delay before  
starting the normal initialization.  Perhaps delay a number of seconds  
chosen from a random distribution between 0 and 10 seconds?  Then let  
all the specific protocols such as DHCP and ND start up with their own  
initial delays and exponential backoffs.

- Ralph

On May 7, 2010, at 4:58 PM 5/7/10, Fred Baker wrote:

> randomization is a good thing, and exponential backoffs are a proven  
> thing. Personally, I would recommend having, on the Nth request, the  
> thing wait a random number of milliseconds between 2^(N-1) and 2^N  
> seconds between retries.
>
> On May 7, 2010, at 9:17 AM, Mikael Abrahamsson wrote:
>
>> On Fri, 7 May 2010, Dan Wing wrote:
>>
>>> I would prefer that HOMEGATE describe the problem and require the  
>>> customer
>>> premise router's coldstart initialization be randomly delayed.
>>
>> Is that really the best way to solve this (if you by this means  
>> minutes of backoff instead of tens of seconds?)
>>
>> I'd rather see more intelligent backoff if the initial request  
>> failed, because we don't want to delay customer getting their  
>> access restored when they cold-reboot (or initial-startup) on  
>> purpose.
>>
>> Quite a substantial part of the population power-off their  
>> equipment when they don't use it (to save power and to protect  
>> against power-surges etc).
>>
>> -- 
>> Mikael Abrahamsson    email: swmike@swm.pp.se
>> _______________________________________________
>> homegate mailing list
>> homegate@ietf.org
>> https://www.ietf.org/mailman/listinfo/homegate
>
> http://www.ipinc.net/IPv4.GIF
>
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate


From shemant@cisco.com  Fri May  7 19:55:04 2010
Return-Path: <shemant@cisco.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 427363A6810 for <homegate@core3.amsl.com>; Fri,  7 May 2010 19:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_20=-0.74, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0cfPaVBQzoJ7 for <homegate@core3.amsl.com>; Fri,  7 May 2010 19:55:03 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id EE8F13A6808 for <homegate@ietf.org>; Fri,  7 May 2010 19:55:02 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJ5v5EutJV2b/2dsb2JhbACeG3GkXZkohRUEg0I
X-IronPort-AV: E=Sophos;i="4.52,352,1270425600"; d="scan'208";a="109286023"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rtp-iport-2.cisco.com with ESMTP; 08 May 2010 02:54:50 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id o482soMm016879;  Sat, 8 May 2010 02:54:50 GMT
Received: from xmb-rcd-114.cisco.com ([72.163.62.156]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 7 May 2010 21:54:50 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 7 May 2010 21:54:47 -0500
Message-ID: <AF742F21C1FCEE4DAB7F4842ABDC511C01865A50@XMB-RCD-114.cisco.com>
In-Reply-To: <DC4EAD37-8C90-4713-A091-EFE5CD4D12BE@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [homegate] restart avalanche
Thread-Index: AcruNCT1JiSpHbvkSHKO0bDzCELpDQAJBv7g
References: <022e01caedf6$4840e270$38a66b80@cisco.com><alpine.DEB.1.10.1005071759040.3685@uplift.swm.pp.se><605D7502-E9F8-4737-A3F9-72C16A32A391@cisco.com> <DC4EAD37-8C90-4713-A091-EFE5CD4D12BE@gmail.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ralph Droms" <rdroms.ietf@gmail.com>, "Fred Baker (fred)" <fred@cisco.com>
X-OriginalArrivalTime: 08 May 2010 02:54:50.0310 (UTC) FILETIME=[D39A8660:01CAEE59]
Cc: homegate@ietf.org
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 May 2010 02:55:04 -0000

I agree with Ralph.  Further, one should not only look at RFC 4861 but
also RFC 4862.  I think there is little or no interaction of ND with
DHCPv6 because DHCPv6 travels over the link-local address. The home
gateway has to create a link-local address and then send a NS(DAD) for
the link-local before the router can send any DHCPv6 message.  See
section 5.4.2 of RFC 4862 than recommends the randomized delay in
sending of the first NS. DHCPv6 has its own initial.  I don't see a
restart avalanche problem.  The protocols that are involved with the
home gateway initialization have randomized delay and start built into
them.

Hemant

-----Original Message-----
From: homegate-bounces@ietf.org [mailto:homegate-bounces@ietf.org] On
Behalf Of Ralph Droms
Sent: Friday, May 07, 2010 6:25 PM
To: Fred Baker (fred)
Cc: homegate@ietf.org
Subject: Re: [homegate] restart avalanche

Considering the multitude of protocols involved and the lack of =20
clarity about what constitutes "failure" and "retry", I think the only =20
sensible system-wide delay would be to wait some short delay before =20
starting the normal initialization.  Perhaps delay a number of seconds =20
chosen from a random distribution between 0 and 10 seconds?  Then let =20
all the specific protocols such as DHCP and ND start up with their own =20
initial delays and exponential backoffs.

- Ralph


From frnkblk@iname.com  Fri May  7 21:11:57 2010
Return-Path: <frnkblk@iname.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 809A13A6869 for <homegate@core3.amsl.com>; Fri,  7 May 2010 21:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.501
X-Spam-Level: 
X-Spam-Status: No, score=0.501 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FROM_LOCAL_NOVOWEL=0.5]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QyvDtPRdPjoq for <homegate@core3.amsl.com>; Fri,  7 May 2010 21:11:55 -0700 (PDT)
Received: from premieronline.net (smtp1-1.premieronline.net [96.31.0.21]) by core3.amsl.com (Postfix) with ESMTP id 961BE3A6863 for <homegate@ietf.org>; Fri,  7 May 2010 21:11:55 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=199.120.69.26; 
Received: from FrankBulkLapto (unverified [199.120.69.26])  by premieronline.net (SurgeMail 4.3h) with ESMTP id 11635740-1729245  for multiple; Fri, 07 May 2010 23:11:36 -0500
From: "Frank Bulk" <frnkblk@iname.com>
To: "'Dan Wing'" <dwing@cisco.com>, <homegate@ietf.org>
References: <022e01caedf6$4840e270$38a66b80@cisco.com>
In-Reply-To: <022e01caedf6$4840e270$38a66b80@cisco.com>
Date: Fri, 7 May 2010 23:11:22 -0500
Message-ID: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAAD+GPMxayzKTIyIgZjR0SpPAQAAAAA=@iname.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acrt9kfyOxGVfZhLQm2PNWwUaSAsHAAbSWKQ
Content-Language: en-us
X-Authenticated-User: fbulk@premieronline.net 
X-SpamDetect: : 0.000000 
X-Info: aspam skipped due to (useraccess)
X-IP-stats: Incoming Outgoing Last 0, First 426, in=5625775, out=28864, spam=0 Known=true ip=199.120.69.26
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: frnkblk@iname.com
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 May 2010 04:11:57 -0000

There's four different access technologies and only one of them possibly
faces this restart avalanche issue for 'homegate':
a) xDSL: if a homegate device is attached to a DSL modem, modems will take
varying lengths of time to sync based on brand/model DSL modem (as each
modem boots up), line conditions, back end PPP processes (if any), and DHCP.
So the homegate device attached to the DSL modem will have an inherent
random dely
b) DOCSIS: much the same as (a).  With ~200 CMs, we see that it takes up to
15 minutes for all the cable modems to get connected.  
c) BWA: much the same as (a)
d) FTTH: if the ONT is battery-backed, the 'homegate' device would be on as
quickly as the power returns.  This is the only situation where I can see
restart avalanche control having substantive value.

Unless we're looking to use restart avalanche control to delay start up by
several minutes, I believe the other processes mention in (a) and (b) will
act as the random delay mechanism.  Rather than build delay in 'homegate',
affecting every user's experience, I'd encourage better mechanisms in the
service provider environment to deal with the "avalanches".

Frank

-----Original Message-----
From: homegate-bounces@ietf.org [mailto:homegate-bounces@ietf.org] On Behalf
Of Dan Wing
Sent: Friday, May 07, 2010 10:02 AM
To: homegate@ietf.org
Subject: [homegate] restart avalanche

As we continue to design PCP (port control protocol), a worry is restart
avalanches caused by a metropolitan-wide power outage/restoration event.
However, restart avalanche concerns are not unique to PCP; restart
avalanches
are also a problem for DHCP servers, DNS servers (as devices query for
things
like pool.ntp.org), NTP servers, SIP proxies, XMPP servers, and so on.

The restart avalanche problem has been discussed before in the context of
VoIP
devices in PacketCable.  Text exists in Section 7.4.3.5 of PacketCable's NCS
specification, titled "Fighting the Restart Avalanche",
http://www.cablelabs.com/specifications/PKT-SP-NCS1.5-I03-070412.pdf and in
Section 4.4.6 of RFC3435, titled "Fighting the Restart Avalanche",
http://tools.ietf.org/html/rfc3435#section-4.4.6


I would prefer that HOMEGATE describe the problem and require the customer
premise router's coldstart initialization be randomly delayed.  The
alternative is that each protocol include a similar mechanism (waste of
code,
testing, etc.) and the risk is a device will include both its own delay and
a
per-protocol delay, adding unnecessary delay to coldstart initialization.

Thoughts?

-d

(Thanks to Flemming Andreasen for the citations to the PacketCable specs.)

_______________________________________________
homegate mailing list
homegate@ietf.org
https://www.ietf.org/mailman/listinfo/homegate


From swmike@swm.pp.se  Fri May  7 21:52:46 2010
Return-Path: <swmike@swm.pp.se>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DE9E3A6833 for <homegate@core3.amsl.com>; Fri,  7 May 2010 21:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level: 
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[AWL=-0.863, BAYES_50=0.001, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EsF96sP4Bsal for <homegate@core3.amsl.com>; Fri,  7 May 2010 21:52:45 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by core3.amsl.com (Postfix) with ESMTP id 6F3EF3A6405 for <homegate@ietf.org>; Fri,  7 May 2010 21:52:45 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 3FAD79F; Sat,  8 May 2010 06:52:29 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 3DB999E for <homegate@ietf.org>; Sat,  8 May 2010 06:52:29 +0200 (CEST)
Date: Sat, 8 May 2010 06:52:29 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: homegate@ietf.org
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAAD+GPMxayzKTIyIgZjR0SpPAQAAAAA=@iname.com>
Message-ID: <alpine.DEB.1.10.1005080645230.3685@uplift.swm.pp.se>
References: <022e01caedf6$4840e270$38a66b80@cisco.com> <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAAD+GPMxayzKTIyIgZjR0SpPAQAAAAA=@iname.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 May 2010 04:52:46 -0000

On Fri, 7 May 2010, Frank Bulk wrote:

> There's four different access technologies and only one of them possibly
> faces this restart avalanche issue for 'homegate':
> a) xDSL: if a homegate device is attached to a DSL modem, modems will take
> varying lengths of time to sync based on brand/model DSL modem (as each
> modem boots up), line conditions, back end PPP processes (if any), and DHCP.
> So the homegate device attached to the DSL modem will have an inherent
> random dely

Millions of devices will pound RADIUS backend systems if PPPoX and 
authentication is used, some kind of backoff here is definitely needed. 
When you have millions of devices this is definitely an avalance (I've 
seen this myself in a production network and the BRAS didn't have any 
ratelimiting features so it was hard to mitigate).

> Unless we're looking to use restart avalanche control to delay start up 
> by several minutes, I believe the other processes mention in (a) and (b) 
> will act as the random delay mechanism.  Rather than build delay in 
> 'homegate', affecting every user's experience, I'd encourage better 
> mechanisms in the service provider environment to deal with the 
> "avalanches".

I think the recommendation should be that any mechanism that talks to the 
provider network should have some kind of backoff if the initial query 
isn't answered. I believe DHCP already does this, I don't know about PPP 
establishment requests.

I tend to agree that this should be handled in the network as well, but 
all protocols should have backoff in case of non-response, nothing should 
run on a simple interval timer without backoff.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From frnkblk@iname.com  Sat May  8 10:19:37 2010
Return-Path: <frnkblk@iname.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8889A3A68BC for <homegate@core3.amsl.com>; Sat,  8 May 2010 10:19:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.658
X-Spam-Level: 
X-Spam-Status: No, score=0.658 tagged_above=-999 required=5 tests=[AWL=-0.157,  BAYES_50=0.001, FROM_LOCAL_NOVOWEL=0.5, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nrVqCyLNHyiC for <homegate@core3.amsl.com>; Sat,  8 May 2010 10:19:36 -0700 (PDT)
Received: from premieronline.net (smtp1-2.premieronline.net [96.31.0.22]) by core3.amsl.com (Postfix) with ESMTP id ADEB53A68AE for <homegate@ietf.org>; Sat,  8 May 2010 10:19:35 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=199.120.69.26; 
Received: from FrankBulkLapto (unverified [199.120.69.26])  by premieronline.net (SurgeMail 4.3h) with ESMTP id 11650574-1729245  for multiple; Sat, 08 May 2010 12:19:13 -0500
From: "Frank Bulk" <frnkblk@iname.com>
To: "'Mikael Abrahamsson'" <swmike@swm.pp.se>, <homegate@ietf.org>
References: <022e01caedf6$4840e270$38a66b80@cisco.com>	<!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAAD+GPMxayzKTIyIgZjR0SpPAQAAAAA=@iname.com> <alpine.DEB.1.10.1005080645230.3685@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.1.10.1005080645230.3685@uplift.swm.pp.se>
Date: Sat, 8 May 2010 12:18:54 -0500
Message-ID: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAABg+XdlpqR+R43a5RB3yO5PAQAAAAA=@iname.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acruaku35bvv1oIjQKOgGdF1QoJWDwAZ3btQ
Content-Language: en-us
X-Authenticated-User: fbulk@premieronline.net 
X-SpamDetect: : 0.000000 
X-Info: aspam skipped due to (useraccess)
X-IP-stats: Incoming Outgoing Last 0, First 427, in=5632420, out=28904, spam=0 Known=true ip=199.120.69.26
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: frnkblk@iname.com
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 May 2010 17:19:38 -0000

The number of events where *millions* of devices point a RADIUS backend
systems nearly simultaneously are few -- I don't think that's worth
designing for.  And if they happened, it would be very unlikely that they
were caused by a power outage, but more likely by some kind of connectivity
failure between the CPE and system at the core, and that would be restart
avalanche control as much as reconnect avalanche control.

And just to be clear, where are we looking for avalanche control?  PPPoA/E?
IPv6 RA? DHCP? DNS?

I'm following the general outlines of the concern, but I think we had better
flesh out the real life scenarios before adding in random startup delays for
something at layer 2/3/4/7 that will frustrate customers 99% of the time for
an event that happens less than 0.01% of power on events.

Frank

-----Original Message-----
From: homegate-bounces@ietf.org [mailto:homegate-bounces@ietf.org] On Behalf
Of Mikael Abrahamsson
Sent: Friday, May 07, 2010 11:52 PM
To: homegate@ietf.org
Subject: Re: [homegate] restart avalanche

On Fri, 7 May 2010, Frank Bulk wrote:

> There's four different access technologies and only one of them possibly
> faces this restart avalanche issue for 'homegate':
> a) xDSL: if a homegate device is attached to a DSL modem, modems will take
> varying lengths of time to sync based on brand/model DSL modem (as each
> modem boots up), line conditions, back end PPP processes (if any), and
DHCP.
> So the homegate device attached to the DSL modem will have an inherent
> random dely

Millions of devices will pound RADIUS backend systems if PPPoX and 
authentication is used, some kind of backoff here is definitely needed. 
When you have millions of devices this is definitely an avalance (I've 
seen this myself in a production network and the BRAS didn't have any 
ratelimiting features so it was hard to mitigate).

> Unless we're looking to use restart avalanche control to delay start up 
> by several minutes, I believe the other processes mention in (a) and (b) 
> will act as the random delay mechanism.  Rather than build delay in 
> 'homegate', affecting every user's experience, I'd encourage better 
> mechanisms in the service provider environment to deal with the 
> "avalanches".

I think the recommendation should be that any mechanism that talks to the 
provider network should have some kind of backoff if the initial query 
isn't answered. I believe DHCP already does this, I don't know about PPP 
establishment requests.

I tend to agree that this should be handled in the network as well, but 
all protocols should have backoff in case of non-response, nothing should 
run on a simple interval timer without backoff.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se
_______________________________________________
homegate mailing list
homegate@ietf.org
https://www.ietf.org/mailman/listinfo/homegate


From swmike@swm.pp.se  Sat May  8 10:34:28 2010
Return-Path: <swmike@swm.pp.se>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AD0E3A67FC for <homegate@core3.amsl.com>; Sat,  8 May 2010 10:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.119
X-Spam-Level: 
X-Spam-Status: No, score=-4.119 tagged_above=-999 required=5 tests=[AWL=-0.785, BAYES_50=0.001, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LO7oTKeRXVqA for <homegate@core3.amsl.com>; Sat,  8 May 2010 10:34:27 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by core3.amsl.com (Postfix) with ESMTP id EE6EE28C0D7 for <homegate@ietf.org>; Sat,  8 May 2010 10:34:17 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 34A089F; Sat,  8 May 2010 19:34:01 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 317A29E for <homegate@ietf.org>; Sat,  8 May 2010 19:34:01 +0200 (CEST)
Date: Sat, 8 May 2010 19:34:01 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: homegate@ietf.org
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAABg+XdlpqR+R43a5RB3yO5PAQAAAAA=@iname.com>
Message-ID: <alpine.DEB.1.10.1005081931050.3685@uplift.swm.pp.se>
References: <022e01caedf6$4840e270$38a66b80@cisco.com> <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAAD+GPMxayzKTIyIgZjR0SpPAQAAAAA=@iname.com> <alpine.DEB.1.10.1005080645230.3685@uplift.swm.pp.se> <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAABg+XdlpqR+R43a5RB3yO5PAQAAAAA=@iname.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 May 2010 17:34:28 -0000

On Sat, 8 May 2010, Frank Bulk wrote:

> The number of events where *millions* of devices point a RADIUS backend
> systems nearly simultaneously are few -- I don't think that's worth
> designing for.  And if they happened, it would be very unlikely that they
> were caused by a power outage, but more likely by some kind of connectivity
> failure between the CPE and system at the core, and that would be restart
> avalanche control as much as reconnect avalanche control.

In this case it was a connectivity event, but the same reasoning is true 
for a widespread power event (which are rare but they obviously happen).

> And just to be clear, where are we looking for avalanche control?  PPPoA/E?
> IPv6 RA? DHCP? DNS?

All of the above, and more. All protocols where the device talks to the 
network, NTP as well (wasn't there a CPE that kept asking NTP once per 
minute even if it didn't get any response, that meant quite a lot of 
traffic with millions of devices). There should be a general guideline 
that all these mechanism use a sensible backoff algorithm.

> I'm following the general outlines of the concern, but I think we had better
> flesh out the real life scenarios before adding in random startup delays for
> something at layer 2/3/4/7 that will frustrate customers 99% of the time for
> an event that happens less than 0.01% of power on events.

I don't want a startup delay, I want backoff.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From jason_livingood@cable.comcast.com  Mon May 10 06:49:26 2010
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FF563A6948 for <homegate@core3.amsl.com>; Mon, 10 May 2010 06:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.626
X-Spam-Level: ***
X-Spam-Status: No, score=3.626 tagged_above=-999 required=5 tests=[AWL=-1.975,  BAYES_50=0.001, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Beos-JuWkZVZ for <homegate@core3.amsl.com>; Mon, 10 May 2010 06:49:24 -0700 (PDT)
Received: from paoakoavas10.cable.comcast.com (paoakoavas10.cable.comcast.com [208.17.35.59]) by core3.amsl.com (Postfix) with ESMTP id F07163A694F for <homegate@ietf.org>; Mon, 10 May 2010 06:49:22 -0700 (PDT)
Received: from ([24.40.15.92]) by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH7.81184159; Mon, 10 May 2010 09:48:51 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PACDCEXCSMTP03.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 10 May 2010 09:48:50 -0400
Received: from 147.191.227.151 ([147.191.227.151]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.152]) with Microsoft Exchange Server HTTP-DAV ; Mon, 10 May 2010 13:48:49 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 10 May 2010 09:48:59 -0400
From: Jason Livingood <jason_livingood@cable.comcast.com>
To: "homegate@ietf.org" <homegate@ietf.org>
Message-ID: <C80D870B.234B3%jason_livingood@cable.comcast.com>
Thread-Topic: Next Steps: Workshop & IETF 78 (Feedback Requested)
Thread-Index: AcrwR4p4qb6YePeCDUKYRswaa/uXOQ==
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3356329740_3940369"
X-OriginalArrivalTime: 10 May 2010 13:48:50.0560 (UTC) FILETIME=[85710000:01CAF047]
Subject: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 May 2010 13:49:26 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3356329740_3940369
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

We=B9ve been discussing next steps as IETF 78 approaches.  It looks likely
that we will submit a request to hold a second, relatively brief BoF at IET=
F
78.  This is likely to be one hour in length, covering the following topics
(feel free to send feedback):
-  Review of Goals of BoF
-  Review of Draft Charter (at
http://trac.tools.ietf.org/area/tsv/trac/wiki/HOMEGATE)
-  Discussion of Any Concerns from Other SDOs / Potential Overlap
-  Final Discussion of Charter & How/Whether to Proceed with Homegate

This leads us to the next question, which concerns the workshop we=B9d
planned.  When we initially scheduled the workshop we believed that other
SDOs had concerns regarding potential overlap with the proposed IETF
homegate effort.  As a result, the workshop was intended to explore what
each of these other SDOs was doing in terms of focus, and to work through
any concerns regarding overlap and so on.  A primary question we have now i=
s
whether such a workshop discussion is still useful.

If the concerns have been assuaged and the interest is now low in the
workshop, no need to hold it.  If we did hold the workshop, none of the
dates were clear winners but here are some of the ones with better indicate=
d
attendance:
- June 22/23 (Western Europe)
- July 13/14 (Eastern U.S.)
- July 14/15 (Eastern U.S.)

Your feedback is requested on the utility of the cross-SDO workshop, as wel=
l
as our plan/agenda for a second BoF.

Regards
Jason



--B_3356329740_3940369
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Next Steps: Workshop &amp; IETF 78 (Feedback Requested)</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>We&#8217;ve been discussing next steps as IETF 78 approaches. &nbsp;It loo=
ks likely that we will submit a request to hold a second, relatively brief B=
oF at IETF 78. &nbsp;This is likely to be one hour in length, covering the f=
ollowing topics (feel free to send feedback):<BR>
- &nbsp;Review of Goals of BoF<BR>
- &nbsp;Review of Draft Charter (at <a href=3D"http://trac.tools.ietf.org/are=
a/tsv/trac/wiki/HOMEGATE">http://trac.tools.ietf.org/area/tsv/trac/wiki/HOME=
GATE</a>)<BR>
- &nbsp;Discussion of Any Concerns from Other SDOs / Potential Overlap<BR>
- &nbsp;Final Discussion of Charter &amp; How/Whether to Proceed with Homeg=
ate <BR>
<BR>
This leads us to the next question, which concerns the workshop we&#8217;d =
planned. &nbsp;When we initially scheduled the workshop we believed that oth=
er SDOs had concerns regarding potential overlap with the proposed IETF home=
gate effort. &nbsp;As a result, the workshop was intended to explore what ea=
ch of these other SDOs was doing in terms of focus, and to work through any =
concerns regarding overlap and so on. &nbsp;A primary question we have now i=
s whether such a workshop discussion is still useful. <BR>
<BR>
If the concerns have been assuaged and the interest is now low in the works=
hop, no need to hold it. &nbsp;If we did hold the workshop, none of the date=
s were clear winners but here are some of the ones with better indicated att=
endance:<BR>
- June 22/23 (Western Europe)<BR>
- July 13/14 (Eastern U.S.)<BR>
- July 14/15 (Eastern U.S.)<BR>
<BR>
Your feedback is requested on the utility of the cross-SDO workshop, as wel=
l as our plan/agenda for a second BoF.<BR>
<BR>
Regards<BR>
Jason<BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3356329740_3940369--


From jason_livingood@cable.comcast.com  Mon May 10 06:56:09 2010
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E19F3A6964 for <homegate@core3.amsl.com>; Mon, 10 May 2010 06:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.973
X-Spam-Level: 
X-Spam-Status: No, score=-0.973 tagged_above=-999 required=5 tests=[AWL=2.823,  BAYES_50=0.001, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GGDfXrkQ16sI for <homegate@core3.amsl.com>; Mon, 10 May 2010 06:56:07 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 0BC833A68A7 for <homegate@ietf.org>; Mon, 10 May 2010 06:55:56 -0700 (PDT)
Received: from ([24.40.15.118]) by pacdcimo01.cable.comcast.com with ESMTP  id 5503620.79454143; Mon, 10 May 2010 09:55:12 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PACDCEXCSMTP04.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 10 May 2010 09:55:13 -0400
Received: from 147.191.227.151 ([147.191.227.151]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.152]) with Microsoft Exchange Server HTTP-DAV ; Mon, 10 May 2010 13:55:12 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 10 May 2010 09:55:23 -0400
From: Jason Livingood <jason_livingood@cable.comcast.com>
To: Dan Wing <dwing@cisco.com>, <homegate@ietf.org>
Message-ID: <C80D888B.234B7%jason_livingood@cable.comcast.com>
Thread-Topic: [homegate] restart avalanche
Thread-Index: Acrt9kfyOxGVfZhLQm2PNWwUaSAsHACUidpJ
In-Reply-To: <022e01caedf6$4840e270$38a66b80@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 10 May 2010 13:55:13.0113 (UTC) FILETIME=[6975F490:01CAF048]
Subject: Re: [homegate] restart avalanche
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 May 2010 13:56:09 -0000

Seems like an interesting question and one that's prompted some discussion
on the list so far.  I think though, given the lower order questions I just
posted to the list, I should defer to the advising ADs on the question of
scope/interest.

Jason


On 5/7/10 11:02 AM, "Dan Wing" <dwing@cisco.com> wrote:

> As we continue to design PCP (port control protocol), a worry is restart
> avalanches caused by a metropolitan-wide power outage/restoration event.
> However, restart avalanche concerns are not unique to PCP; restart avalanches
> are also a problem for DHCP servers, DNS servers (as devices query for things
> like pool.ntp.org), NTP servers, SIP proxies, XMPP servers, and so on.
> 
> The restart avalanche problem has been discussed before in the context of VoIP
> devices in PacketCable.  Text exists in Section 7.4.3.5 of PacketCable's NCS
> specification, titled "Fighting the Restart Avalanche",
> http://www.cablelabs.com/specifications/PKT-SP-NCS1.5-I03-070412.pdf and in
> Section 4.4.6 of RFC3435, titled "Fighting the Restart Avalanche",
> http://tools.ietf.org/html/rfc3435#section-4.4.6
> 
> 
> I would prefer that HOMEGATE describe the problem and require the customer
> premise router's coldstart initialization be randomly delayed.  The
> alternative is that each protocol include a similar mechanism (waste of code,
> testing, etc.) and the risk is a device will include both its own delay and a
> per-protocol delay, adding unnecessary delay to coldstart initialization.
> 
> Thoughts?
> 
> -d
> 
> (Thanks to Flemming Andreasen for the citations to the PacketCable specs.)
> 


From paul.hoffman@vpnc.org  Mon May 10 08:16:34 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B3CDA3A69FC for <homegate@core3.amsl.com>; Mon, 10 May 2010 08:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.811
X-Spam-Level: 
X-Spam-Status: No, score=-0.811 tagged_above=-999 required=5 tests=[AWL=-1.365, BAYES_50=0.001, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZrwWH1zJ-A1D for <homegate@core3.amsl.com>; Mon, 10 May 2010 08:16:32 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 311573A6BE7 for <homegate@ietf.org>; Mon, 10 May 2010 08:15:29 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o4AFF52h070113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 May 2010 08:15:07 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624080fc80dd2f9213b@[10.20.30.158]>
In-Reply-To: <C80D870B.234B3%jason_livingood@cable.comcast.com>
References: <C80D870B.234B3%jason_livingood@cable.comcast.com>
Date: Mon, 10 May 2010 08:15:06 -0700
To: Jason Livingood <jason_livingood@cable.comcast.com>, "homegate@ietf.org" <homegate@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 May 2010 15:16:34 -0000

At 9:48 AM -0400 5/10/10, Jason Livingood wrote:
>This leads us to the next question, which concerns the workshop we'd planned.  When we initially scheduled the workshop we believed that other SDOs had concerns regarding potential overlap with the proposed IETF homegate effort.  As a result, the workshop was intended to explore what each of these other SDOs was doing in terms of focus, and to work through any concerns regarding overlap and so on.  A primary question we have now is whether such a workshop discussion is still useful.

For those of us who are not active in those other SDOs, it would be useful to know what concerns *they* have with the formation of this WG. If people in those SDOs could send concerns, unofficially, to the list, we can get a better sense of whether or not a face-to-face meeting, a day-long telecon, or any meeting at all, is needed.

--Paul Hoffman, Director
--VPN Consortium

From jason_livingood@cable.comcast.com  Tue May 11 05:59:26 2010
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D458F3A6AEE for <homegate@core3.amsl.com>; Tue, 11 May 2010 05:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.918
X-Spam-Level: 
X-Spam-Status: No, score=-3.918 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, RCVD_IN_SORBS_WEB=0.619, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ibPo62r0Nhl for <homegate@core3.amsl.com>; Tue, 11 May 2010 05:59:26 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 0795F3A6BB6 for <homegate@ietf.org>; Tue, 11 May 2010 05:58:38 -0700 (PDT)
Received: from ([10.52.116.30]) by pacdcimo01.cable.comcast.com with ESMTP  id 5503620.79568892; Tue, 11 May 2010 08:58:25 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 11 May 2010 08:58:25 -0400
Received: from 207.228.237.150 ([207.228.237.150]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.152]) with Microsoft Exchange Server HTTP-DAV ; Tue, 11 May 2010 12:58:24 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Tue, 11 May 2010 08:58:41 -0400
From: Jason Livingood <jason_livingood@cable.comcast.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "homegate@ietf.org" <homegate@ietf.org>
Message-ID: <C80ECCC1.23636%jason_livingood@cable.comcast.com>
Thread-Topic: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
Thread-Index: AcrxCa4EKYKFl6rKq0mONXxZmVF4zQ==
In-Reply-To: <p0624080fc80dd2f9213b@[10.20.30.158]>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 11 May 2010 12:58:25.0127 (UTC) FILETIME=[A48E4F70:01CAF109]
Subject: Re: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 May 2010 12:59:26 -0000

On 5/10/10 11:15 AM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:
> 
> For those of us who are not active in those other SDOs, it would be useful to
> know what concerns *they* have with the formation of this WG. If people in
> those SDOs could send concerns, unofficially, to the list, we can get a better
> sense of whether or not a face-to-face meeting, a day-long telecon, or any
> meeting at all, is needed.

Agree.  And if we don't see much interest raised on the list, we'll have to
conclude we don't need such a meeting of course.

J


From mbaugher@cisco.com  Tue May 11 06:56:47 2010
Return-Path: <mbaugher@cisco.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D0893A6816 for <homegate@core3.amsl.com>; Tue, 11 May 2010 06:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.299
X-Spam-Level: 
X-Spam-Status: No, score=-9.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AEk4i4g0Eyfi for <homegate@core3.amsl.com>; Tue, 11 May 2010 06:56:46 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id CE2CD3A6841 for <homegate@ietf.org>; Tue, 11 May 2010 06:56:41 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAEf/6EurR7Hu/2dsb2JhbACeK3GhWplhgmCCMASDQA
X-IronPort-AV: E=Sophos;i="4.53,207,1272844800"; d="scan'208";a="324925088"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 11 May 2010 13:56:31 +0000
Received: from sjc-mbaugher-8712.cisco.com (sjc-mbaugher-8712.cisco.com [10.19.93.35]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o4BDuVNd021375; Tue, 11 May 2010 13:56:31 GMT
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: Mark Baugher <mbaugher@cisco.com>
In-Reply-To: <C80ECCC1.23636%jason_livingood@cable.comcast.com>
Date: Tue, 11 May 2010 06:56:30 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <89C14FC9-6659-4A66-8044-3A5D81A8A146@cisco.com>
References: <C80ECCC1.23636%jason_livingood@cable.comcast.com>
To: Jason Livingood <jason_livingood@cable.comcast.com>
X-Mailer: Apple Mail (2.1078)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 May 2010 13:56:47 -0000

On May 11, 2010, at 5:58 AM, Jason Livingood wrote:

> On 5/10/10 11:15 AM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:
>>=20
>> For those of us who are not active in those other SDOs, it would be =
useful to
>> know what concerns *they* have with the formation of this WG. If =
people in
>> those SDOs could send concerns, unofficially, to the list, we can get =
a better
>> sense of whether or not a face-to-face meeting, a day-long telecon, =
or any
>> meeting at all, is needed.
>=20
> Agree.  And if we don't see much interest raised on the list, we'll =
have to
> conclude we don't need such a meeting of course.

It's hard for me to say because I don't recall exactly why we chose to =
invite SDO representatives in the first place.  The idea made sense to =
me because homegate has an interface to the home network and the IETF as =
an organization has little experience in that realm.  As an =
organization, we know our way around the service provider interface =
better than network services to home devices.  So a combination of SDOs =
and vendors like Apple that develop standards for home networks provide =
can provide needed background information to many of us and their talks =
should also provide a common frame of reference for their entire group.  =
That's what I thought the reasons were for their original intent.  True?

Personally, I have heard enough presentations about UPnP, Bonjour, DLNA, =
IGRS, etc. that I don't have that much interest.  But I am interested in =
what homegate is going to do differently from some of these other =
initiatives and where these technologies have a bearing on what homegate =
is going to do.

Mark

>=20
> J
>=20
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate


From ichiroumakino@gmail.com  Tue May 11 07:05:47 2010
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6BED63A6949 for <homegate@core3.amsl.com>; Tue, 11 May 2010 07:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.667
X-Spam-Level: 
X-Spam-Status: No, score=-0.667 tagged_above=-999 required=5 tests=[AWL=-0.668, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCN2pd8uUK4i for <homegate@core3.amsl.com>; Tue, 11 May 2010 07:05:46 -0700 (PDT)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id 4834F28C15D for <homegate@ietf.org>; Tue, 11 May 2010 07:04:46 -0700 (PDT)
Received: by ewy8 with SMTP id 8so1259887ewy.28 for <homegate@ietf.org>; Tue, 11 May 2010 07:04:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=E0AvFZxrFWFu5tPMdzxPc5hrNbXpudIIEjj60rG256w=; b=DwVc95HRq3Vq7zo7SOJIbfkbG0Z5aLigCH5Uf7vsy0g4eyMPYIoEJa9LkXJIs4zoSw PdmSGcX+lmDO5sa/fVfAgvR8O6ypA6nlOgr+QQTCLqji6wVpRabtLGqcSe8BxZzXY2eS huKQdD3CZ/LqqitOnh+OcoHgXwpuDglKM3Ok4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=CDDdeogHBQHFWUP+cbF4dxVuKwLLMeyezLEpbqpRSMFfwBSgw+1RKmWsT4GP6jORTH 9qZJAxPzrVH6utQPpxS+FBBLr1Enks02XIOk7B9Q3WrulpN0q3AaXfQy5Uiiu3yhToEy jFN3y3/RwjlKUOCi0gjZ0TfSv+9TkKGw9jXaE=
Received: by 10.213.37.203 with SMTP id y11mr2387314ebd.61.1273586672080; Tue, 11 May 2010 07:04:32 -0700 (PDT)
Received: from dhcp-10-55-89-162.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id 15sm3125050ewy.12.2010.05.11.07.04.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 11 May 2010 07:04:29 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <89C14FC9-6659-4A66-8044-3A5D81A8A146@cisco.com>
Date: Tue, 11 May 2010 16:04:27 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE10AD20-D0D3-4760-90C8-57C80D5903E9@employees.org>
References: <C80ECCC1.23636%jason_livingood@cable.comcast.com> <89C14FC9-6659-4A66-8044-3A5D81A8A146@cisco.com>
To: Jason Livingood <jason_livingood@cable.comcast.com>
X-Mailer: Apple Mail (2.1078)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, homegate@ietf.org
Subject: Re: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 May 2010 14:05:47 -0000

Mark,

>>> For those of us who are not active in those other SDOs, it would be =
useful to
>>> know what concerns *they* have with the formation of this WG. If =
people in
>>> those SDOs could send concerns, unofficially, to the list, we can =
get a better
>>> sense of whether or not a face-to-face meeting, a day-long telecon, =
or any
>>> meeting at all, is needed.
>>=20
>> Agree.  And if we don't see much interest raised on the list, we'll =
have to
>> conclude we don't need such a meeting of course.
>=20
> It's hard for me to say because I don't recall exactly why we chose to =
invite SDO representatives in the first place.  The idea made sense to =
me because homegate has an interface to the home network and the IETF as =
an organization has little experience in that realm.  As an =
organization, we know our way around the service provider interface =
better than network services to home devices.  So a combination of SDOs =
and vendors like Apple that develop standards for home networks provide =
can provide needed background information to many of us and their talks =
should also provide a common frame of reference for their entire group.  =
That's what I thought the reasons were for their original intent.  True?
>=20
> Personally, I have heard enough presentations about UPnP, Bonjour, =
DLNA, IGRS, etc. that I don't have that much interest.  But I am =
interested in what homegate is going to do differently from some of =
these other initiatives and where these technologies have a bearing on =
what homegate is going to do.

with my BBF hat on (co-author of TR-124i2) my only concern would be if =
homegate would specify something which would conflict with that =
document. of lesser concern would be if homegate spent time specifying =
overlapping requirements. even though that appears to be a waste of =
time.

from purely an IPv6 perspective the "IPv6 CE router requirements" draft =
represents multiple SDO's involvement (CableLabs, BBF, IETF). and can =
perhaps be looked at as part summary of TR-124i2 / DOCSIS 3.0.

I think it would be easier to relate to homegate if we knew what we =
wanted it to do.
did we reach any consensus on the 'issues list' we discussed previously?

cheers,
Ole=

From jason_livingood@cable.comcast.com  Fri May 14 08:38:31 2010
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A29783A6B37 for <homegate@core3.amsl.com>; Fri, 14 May 2010 08:38:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.858
X-Spam-Level: 
X-Spam-Status: No, score=-0.858 tagged_above=-999 required=5 tests=[AWL=2.623,  BAYES_50=0.001, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Db2bEju-kCuV for <homegate@core3.amsl.com>; Fri, 14 May 2010 08:38:30 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 273443A6B22 for <homegate@ietf.org>; Fri, 14 May 2010 08:38:30 -0700 (PDT)
Received: from ([10.52.116.30]) by pacdcimo01.cable.comcast.com with ESMTP  id 5503620.79945426; Fri, 14 May 2010 11:38:16 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 14 May 2010 11:38:15 -0400
Received: from 147.191.227.151 ([147.191.227.151]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.152]) with Microsoft Exchange Server HTTP-DAV ; Fri, 14 May 2010 15:38:15 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Fri, 14 May 2010 11:38:10 -0400
From: Jason Livingood <jason_livingood@cable.comcast.com>
To: Ole Troan <otroan@employees.org>
Message-ID: <C812E6A2.23B70%jason_livingood@cable.comcast.com>
Thread-Topic: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
Thread-Index: Acrze3TTMK4dVH5CU0O8VCjf3PmY/g==
In-Reply-To: <FE10AD20-D0D3-4760-90C8-57C80D5903E9@employees.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 14 May 2010 15:38:15.0998 (UTC) FILETIME=[786655E0:01CAF37B]
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, homegate@ietf.org
Subject: Re: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2010 15:38:31 -0000

> I think it would be easier to relate to homegate if we knew what we wanted it
> to do.
> did we reach any consensus on the 'issues list' we discussed previously?

What issues list is that?

Here is our current draft charter and objectives.  Is it more clear from
this what we intend?  If there is still uncertainty, please say so and
please be as specific in your feedback as possible.

http://trac.tools.ietf.org/area/tsv/trac/wiki/HOMEGATE

PROPOSED CHARTER - PLEASE REVIEW / UPDATE
Title: Broadband Home Gateway [HomeGate]

Proposed Charter: Access to broadband Internet services use networking
technology of one form or another within the home, small office/home office
(SOHO) or small to medium business (SMB) as the demarcation between the
local network and the Internet. These technologies almost always involve a
single entity - which is not purely a router - called a "home gateway".
This entity connects a local user or users to various LAN services,
providing some basic level of security.  The majority of Internet users
employ home gateways for this purpose.

However, many serious, long-term problems face users of home gateways today.
At the root of many of these problems is the fact that device manufacturers,
and/or the organizations that specify requirements for such devices, are not
certain which IETF standards and best current practices should be supported,
and when/why that support is needed.  As a result of this, millions of
devices are being deployed every year, which do not work with important IETF
protocols, standards, and best practices that are central to the future of
the Internet. 

One of the problems in this area appears to be that home gateway vendors are
unclear which RFCs are important, or current, and why they are important and
in what context they matter. Thus, the primary objective of the group is
document a baseline of requirements derived from "core" RFCs which must be
supported. A secondary objective is to list desired-but-optional, or
"advanced", requirements from the same RFCs as well as other, non-core RFCs.
The context and reasoning behind each document which is included should be
summarized as well, in order to improve comprehension of why a given
document has been included.  These things will help improve compatibilities
with and capabilities for use of the Internet of today.  This will include a
focus in areas such as DNS proxy behavior, congestion mechanisms support,
and security. 

A secondary problem is compatibility with and capability for the use of the
Internet of tomorrow.  New security needs related to DNS are motivating a
move to DNSSEC.  However, many if not most home gateways cannot handle
DNSSEC, which is expected to be a major problem that could significantly
impede the deployment of DNSSEC globally. Support for IPv6 is also lacking
to a great degree and there is no clear understanding of how such devices
should support IPv6.

This working group will not develop new Internet protocols, but may create
different requirements in the context of home gateways. If the Working Group
believes that new protocols are needed, it will refer the problem to the
IESG for further work in existing or new Working Groups.

Proposed Deliverables and Priorities: The Working Group would work to
improve the network experience that a user of a home gateway gets when using
the Internet. This means specifying the requirements from different RFCs
should be supported in home gateways. This will touch on standards such as:
* IPv6
* DNSSEC RFCs and BCPs
* ECN
* RED (or other queue management)
* DNS Proxy BCPs
* Security-Related BCPs
* Other TBD

The group will create a BCP-level document for home gateways that only
support IPv4, and a second BCP-level document for home gateways that only
support both IPv4 and IPv6.

The group shall prioritize work as follows:
1. IPv4-related topics
2. IPv6-related topics
3. DNS-related topics (DNSSEC, DNS Proxies, etc.)
4. ECN-related topics (congestion and queue management)
5. Security-related topics

Contributors: ISPs and home gateway developers / vendors

Who Uses the Work: Home gateway developers / vendors, ISPs 


From mohamed.boucadair@orange-ftgroup.com  Tue May 18 08:29:56 2010
Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9EAEC3A692D for <homegate@core3.amsl.com>; Tue, 18 May 2010 08:29:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.259
X-Spam-Level: 
X-Spam-Status: No, score=-1.259 tagged_above=-999 required=5 tests=[AWL=-0.926, BAYES_50=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yevtXNWMBZRi for <homegate@core3.amsl.com>; Tue, 18 May 2010 08:29:55 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by core3.amsl.com (Postfix) with ESMTP id 4C86F3A6A30 for <homegate@ietf.org>; Tue, 18 May 2010 08:28:22 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 65E532DC36B; Tue, 18 May 2010 17:28:13 +0200 (CEST)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 4BE5B4C01B; Tue, 18 May 2010 17:28:13 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Tue, 18 May 2010 17:28:12 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: Jason Livingood <jason_livingood@cable.comcast.com>
Date: Tue, 18 May 2010 17:28:12 +0200
Thread-Topic: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
Thread-Index: Acrze3TTMK4dVH5CU0O8VCjf3PmY/gDIeFBg
Message-ID: <28922_1274196493_4BF2B20D_28922_2840_1_94C682931C08B048B7A8645303FDC9F30F129CB660@PUEXCB1B.nanterre.francetelecom.fr>
References: <FE10AD20-D0D3-4760-90C8-57C80D5903E9@employees.org> <C812E6A2.23B70%jason_livingood@cable.comcast.com>
In-Reply-To: <C812E6A2.23B70%jason_livingood@cable.comcast.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.5.18.145115
Cc: Reinaldo Penno <rpenno@juniper.net>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2010 15:29:56 -0000

Dear Jason,

Dan has asked in this ML if there in an interest to include avalanche resta=
rt concerns to the scope of the homegate. In the context of the ongoing PCP=
 spec, we have proposed the use of DHCP as a means to delay sending PCP mes=
sages during massive reboot: http://tools.ietf.org/html/draft-bpw-softwire-=
pcp-dhcp-01#section-3.3.

We think this solution can be generalised and instead of defining a solutio=
n per-service/application/protocol, a generic solution can be documented in=
 a single place.=20

Based on the previous discussion on that topic, is there any conclusion to =
include/exclude such topic to the proposed charter?

Cheers,
Med=20

-----Message d'origine-----
De : homegate-bounces@ietf.org [mailto:homegate-bounces@ietf.org] De la par=
t de Jason Livingood
Envoy=E9 : vendredi 14 mai 2010 17:38
=C0 : Ole Troan
Cc : Paul Hoffman; homegate@ietf.org
Objet : Re: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)


> I think it would be easier to relate to homegate if we knew what we wante=
d it
> to do.
> did we reach any consensus on the 'issues list' we discussed previously?

What issues list is that?

Here is our current draft charter and objectives.  Is it more clear from
this what we intend?  If there is still uncertainty, please say so and
please be as specific in your feedback as possible.

http://trac.tools.ietf.org/area/tsv/trac/wiki/HOMEGATE

PROPOSED CHARTER - PLEASE REVIEW / UPDATE
Title: Broadband Home Gateway [HomeGate]

Proposed Charter: Access to broadband Internet services use networking
technology of one form or another within the home, small office/home office
(SOHO) or small to medium business (SMB) as the demarcation between the
local network and the Internet. These technologies almost always involve a
single entity - which is not purely a router - called a "home gateway".
This entity connects a local user or users to various LAN services,
providing some basic level of security.  The majority of Internet users
employ home gateways for this purpose.

However, many serious, long-term problems face users of home gateways today.
At the root of many of these problems is the fact that device manufacturers,
and/or the organizations that specify requirements for such devices, are not
certain which IETF standards and best current practices should be supported,
and when/why that support is needed.  As a result of this, millions of
devices are being deployed every year, which do not work with important IETF
protocols, standards, and best practices that are central to the future of
the Internet.=20

One of the problems in this area appears to be that home gateway vendors are
unclear which RFCs are important, or current, and why they are important and
in what context they matter. Thus, the primary objective of the group is
document a baseline of requirements derived from "core" RFCs which must be
supported. A secondary objective is to list desired-but-optional, or
"advanced", requirements from the same RFCs as well as other, non-core RFCs.
The context and reasoning behind each document which is included should be
summarized as well, in order to improve comprehension of why a given
document has been included.  These things will help improve compatibilities
with and capabilities for use of the Internet of today.  This will include a
focus in areas such as DNS proxy behavior, congestion mechanisms support,
and security.=20

A secondary problem is compatibility with and capability for the use of the
Internet of tomorrow.  New security needs related to DNS are motivating a
move to DNSSEC.  However, many if not most home gateways cannot handle
DNSSEC, which is expected to be a major problem that could significantly
impede the deployment of DNSSEC globally. Support for IPv6 is also lacking
to a great degree and there is no clear understanding of how such devices
should support IPv6.

This working group will not develop new Internet protocols, but may create
different requirements in the context of home gateways. If the Working Group
believes that new protocols are needed, it will refer the problem to the
IESG for further work in existing or new Working Groups.

Proposed Deliverables and Priorities: The Working Group would work to
improve the network experience that a user of a home gateway gets when using
the Internet. This means specifying the requirements from different RFCs
should be supported in home gateways. This will touch on standards such as:
* IPv6
* DNSSEC RFCs and BCPs
* ECN
* RED (or other queue management)
* DNS Proxy BCPs
* Security-Related BCPs
* Other TBD

The group will create a BCP-level document for home gateways that only
support IPv4, and a second BCP-level document for home gateways that only
support both IPv4 and IPv6.

The group shall prioritize work as follows:
1. IPv4-related topics
2. IPv6-related topics
3. DNS-related topics (DNSSEC, DNS Proxies, etc.)
4. ECN-related topics (congestion and queue management)
5. Security-related topics

Contributors: ISPs and home gateway developers / vendors

Who Uses the Work: Home gateway developers / vendors, ISPs=20

_______________________________________________
homegate mailing list
homegate@ietf.org
https://www.ietf.org/mailman/listinfo/homegate

*********************************
This message and any attachments (the "message") are confidential and inten=
ded solely for the addressees.=20
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.=20
France Telecom Group shall not be liable for the message if altered, change=
d or falsified.
If you are not the intended addressee of this message, please cancel it imm=
ediately and inform the sender.
********************************


From iljitsch@muada.com  Tue May 18 08:38:19 2010
Return-Path: <iljitsch@muada.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C982A28C18C for <homegate@core3.amsl.com>; Tue, 18 May 2010 08:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.647
X-Spam-Level: 
X-Spam-Status: No, score=-0.647 tagged_above=-999 required=5 tests=[AWL=-0.463, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ejk6rUG5hKyq for <homegate@core3.amsl.com>; Tue, 18 May 2010 08:38:19 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 79DDC3A6A20 for <homegate@ietf.org>; Tue, 18 May 2010 08:37:20 -0700 (PDT)
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.229]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o4IFYcNT033224 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 May 2010 17:34:38 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <28922_1274196493_4BF2B20D_28922_2840_1_94C682931C08B048B7A8645303FDC9F30F129CB660@PUEXCB1B.nanterre.francetelecom.fr>
Date: Tue, 18 May 2010 17:36:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1CB1075F-8C7C-4C8F-8FCB-F264A0A6E718@muada.com>
References: <FE10AD20-D0D3-4760-90C8-57C80D5903E9@employees.org> <C812E6A2.23B70%jason_livingood@cable.comcast.com> <28922_1274196493_4BF2B20D_28922_2840_1_94C682931C08B048B7A8645303FDC9F30F129CB660@PUEXCB1B.nanterre.francetelecom.fr>
To: <mohamed.boucadair@orange-ftgroup.com>
X-Mailer: Apple Mail (2.1078)
Cc: "homegate@ietf.org" <homegate@ietf.org>, Reinaldo Penno <rpenno@juniper.net>
Subject: Re: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2010 15:38:19 -0000

On 18 mei 2010, at 17:28, <mohamed.boucadair@orange-ftgroup.com> wrote:

> Dan has asked in this ML if there in an interest to include avalanche =
restart concerns to the scope of the homegate. In the context of the =
ongoing PCP spec, we have proposed the use of DHCP as a means to delay =
sending PCP messages during massive reboot

I don't think DHCP is a good choice here. First of all, DHCP isn't a =
good choice for pretty much anything because there are separate versions =
for IPv4 and IPv6 and within DHCPv6 there are stateful and stateless =
variants and DHCPv6 deployment is _far_ from universal.

But more to the point: DHCP uses multicast. Multicast uses and =
inordinate amount of capacity on wifi networks, and under many =
circumstances also more than unicast on switched ethernet. There are =
ways to work around this, but first creating a problem and then solving =
it seems inelegant compared to not creating it in the first place.


From mohamed.boucadair@orange-ftgroup.com  Tue May 18 09:35:14 2010
Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6F963A6C5D for <homegate@core3.amsl.com>; Tue, 18 May 2010 09:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.362
X-Spam-Level: 
X-Spam-Status: No, score=-1.362 tagged_above=-999 required=5 tests=[AWL=-0.714, BAYES_50=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K3MAYRj-u58K for <homegate@core3.amsl.com>; Tue, 18 May 2010 09:35:14 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by core3.amsl.com (Postfix) with ESMTP id 88E5B3A6C8D for <homegate@ietf.org>; Tue, 18 May 2010 09:29:47 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id C7FF73246A6; Tue, 18 May 2010 18:29:38 +0200 (CEST)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id AD581238066; Tue, 18 May 2010 18:29:38 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Tue, 18 May 2010 18:29:38 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 18 May 2010 18:26:39 +0200
Thread-Topic: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)
Thread-Index: Acr2n/+q7INJTdS1RoSE9N+h3886hAABuUT4
Message-ID: <13118_1274200178_4BF2C072_13118_7341_1_94C682931C08B048B7A8645303FDC9F30F12CC4326@PUEXCB1B.nanterre.francetelecom.fr>
References: <FE10AD20-D0D3-4760-90C8-57C80D5903E9@employees.org> <C812E6A2.23B70%jason_livingood@cable.comcast.com> <28922_1274196493_4BF2B20D_28922_2840_1_94C682931C08B048B7A8645303FDC9F30F129CB660@PUEXCB1B.nanterre.francetelecom.fr>, <1CB1075F-8C7C-4C8F-8FCB-F264A0A6E718@muada.com>
In-Reply-To: <1CB1075F-8C7C-4C8F-8FCB-F264A0A6E718@muada.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.5.18.155115
Cc: "homegate@ietf.org" <homegate@ietf.org>, Reinaldo Penno <rpenno@juniper.net>
Subject: [homegate] RE : Next Steps: Workshop & IETF 78 (Feedback Requested)
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2010 16:35:14 -0000

Dear Iljitsh,

DHCP is privided here as an example of solution candidate. I won't argue ag=
ainst what you have just said.=20

At this stage, what we asked for is to agree (or not) on the the problem to=
 be solved. Is it something of interest of this initiative or not?

Please don't focus on the solution but on the problem to be solved.

Cheers,
Med

________________________________________
De : Iljitsch van Beijnum [iljitsch@muada.com]
Date d'envoi : mardi 18 mai 2010 17:36
=C0 : BOUCADAIR Mohamed NCPI/NAD/TIP
Cc : Jason Livingood; Reinaldo Penno; homegate@ietf.org
Objet : Re: [homegate] Next Steps: Workshop & IETF 78 (Feedback Requested)

On 18 mei 2010, at 17:28, <mohamed.boucadair@orange-ftgroup.com> wrote:

> Dan has asked in this ML if there in an interest to include avalanche res=
tart concerns to the scope of the homegate. In the context of the ongoing P=
CP spec, we have proposed the use of DHCP as a means to delay sending PCP m=
essages during massive reboot

I don't think DHCP is a good choice here. First of all, DHCP isn't a good c=
hoice for pretty much anything because there are separate versions for IPv4=
 and IPv6 and within DHCPv6 there are stateful and stateless variants and D=
HCPv6 deployment is _far_ from universal.

But more to the point: DHCP uses multicast. Multicast uses and inordinate a=
mount of capacity on wifi networks, and under many circumstances also more =
than unicast on switched ethernet. There are ways to work around this, but =
first creating a problem and then solving it seems inelegant compared to no=
t creating it in the first place.


*********************************
This message and any attachments (the "message") are confidential and inten=
ded solely for the addressees.=20
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.=20
France Telecom Group shall not be liable for the message if altered, change=
d or falsified.
If you are not the intended addressee of this message, please cancel it imm=
ediately and inform the sender.
********************************


From iljitsch@muada.com  Tue May 18 09:50:40 2010
Return-Path: <iljitsch@muada.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E6553A6A8F for <homegate@core3.amsl.com>; Tue, 18 May 2010 09:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.323
X-Spam-Level: 
X-Spam-Status: No, score=-0.323 tagged_above=-999 required=5 tests=[AWL=-0.324, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ARzCtczxKUYb for <homegate@core3.amsl.com>; Tue, 18 May 2010 09:50:39 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id CD5543A68CD for <homegate@ietf.org>; Tue, 18 May 2010 09:48:48 -0700 (PDT)
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.229]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o4IGk5Ce033616 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 May 2010 18:46:07 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <13118_1274200178_4BF2C072_13118_7341_1_94C682931C08B048B7A8645303FDC9F30F12CC4326@PUEXCB1B.nanterre.francetelecom.fr>
Date: Tue, 18 May 2010 18:48:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1D453F8-1CC3-4D06-AFA9-A5DBF42381A0@muada.com>
References: <FE10AD20-D0D3-4760-90C8-57C80D5903E9@employees.org> <C812E6A2.23B70%jason_livingood@cable.comcast.com> <28922_1274196493_4BF2B20D_28922_2840_1_94C682931C08B048B7A8645303FDC9F30F129CB660@PUEXCB1B.nanterre.francetelecom.fr>, <1CB1075F-8C7C-4C8F-8FCB-F264A0A6E718@muada.com> <13118_1274200178_4BF2C072_13118_7341_1_94C682931C08B048B7A8645303FDC9F30F12CC4326@PUEXCB1B.nanterre.francetelecom.fr>
To: <mohamed.boucadair@orange-ftgroup.com>
X-Mailer: Apple Mail (2.1078)
Cc: "homegate@ietf.org" <homegate@ietf.org>, Reinaldo Penno <rpenno@juniper.net>
Subject: Re: [homegate] RE : Next Steps: Workshop & IETF 78 (Feedback Requested)
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2010 16:50:40 -0000

On 18 mei 2010, at 18:26, <mohamed.boucadair@orange-ftgroup.com> wrote:

> At this stage, what we asked for is to agree (or not) on the the =
problem to be solved. Is it something of interest of this initiative or =
not?

> Please don't focus on the solution but on the problem to be solved.

I think to some degree the problem is unsolvable, as you need to =
reinitialize a whole bunch of stuff after an outage whether you like it =
or not.

So I think it's important that mostly vendors but also protocol =
designers to some degree should focus on making provisioning systems etc =
high performance and robust so they can handle large numbers of requests =
without entering in some kind of congestion collapse. We already apply =
exponential backoffs in many protocols for exactly this reason.

However, there are some things that can be done. For instance, Apple's =
iPhone (I'm sure many other devices do the same thing, but I just happen =
to know this example) does an ARP request for the default gateway when =
wifi connectivity has changed. If there is an ARP reply (possibly after =
checking some parameters) then the device will continue to use its =
current DHCP lease, if there is no ARP reply it will initiate a new DHCP =
request.

A home gateway could do something similar: after an outage, it could ARP =
or ping the ISP's router and only reinitialize everything if that =
request fails. Of course this does require that the DHCP server state at =
the ISP survives a power failure, and the lease times must be =
sufficiently long.

Another thing that would probably be useful is to make sure that when =
layer X isn't working, layers X+1 ... X+N aren't trying to =
reconnect/rediscover, just making things worse.=

From jason_livingood@cable.comcast.com  Mon May 31 08:23:41 2010
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 449713A6886 for <homegate@core3.amsl.com>; Mon, 31 May 2010 08:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.931
X-Spam-Level: ****
X-Spam-Status: No, score=4.931 tagged_above=-999 required=5 tests=[BAYES_80=2,  HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y6tlhiwrEUqc for <homegate@core3.amsl.com>; Mon, 31 May 2010 08:23:40 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by core3.amsl.com (Postfix) with ESMTP id 649773A6836 for <homegate@ietf.org>; Mon, 31 May 2010 08:23:40 -0700 (PDT)
Received: from ([147.191.124.14]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.470541;  Mon, 31 May 2010 09:26:06 -0600
Received: from PAOAKEXCSMTP02.cable.comcast.com (10.52.116.31) by COPDCEXHUB03.cable.comcast.com (147.191.124.14) with Microsoft SMTP Server id 14.0.694.0; Mon, 31 May 2010 09:23:26 -0600
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 31 May 2010 11:23:24 -0400
Received: from 68.81.100.147 ([68.81.100.147]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.152]) with Microsoft Exchange Server HTTP-DAV ; Mon, 31 May 2010 15:23:24 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 31 May 2010 11:23:21 -0400
From: Jason Livingood <jason_livingood@cable.comcast.com>
To: "homegate@ietf.org" <homegate@ietf.org>
Message-ID: <C8294CA9.24E36%jason_livingood@cable.comcast.com>
Thread-Topic: Update on Workshop Status & IETF 78 Plans
Thread-Index: AcrxCa4EKYKFl6rKq0mONXxZmVF4zQPy4Xyc
In-Reply-To: <C80ECCC1.23636%jason_livingood@cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 31 May 2010 15:23:24.0814 (UTC) FILETIME=[363C32E0:01CB00D5]
Subject: [homegate] Update on Workshop Status & IETF 78 Plans
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 May 2010 15:23:41 -0000

Based on the feedback from the advising Area Directors and co-chairs of the
continuing homegate effort, we have determined there is insufficient
interest in and content to justify a 2-day face to face meeting prior to
IETF 78.

However we do believe there is value in an abbreviated, virtual meeting
(WebEx, etc.) prior to IETF 78.  To support this we're proposing several
possible dates, and there is a draft agenda below.  Please give us your
feedback on the agenda and please also vote on dates at

As for IETF 78, we have requested a second BoF (not yet approved).  I will
send the draft agenda for the BoF under separate cover.  We received
guidance to make that agenda short and focused.

DRAFT VIRTUAL WORKSHOP TIMES AND AGENDA (and presenters)

Times listed are **UTC** (so adjust to your local time zone)
Duration: 6 Hours (with 2 breaks)
Start Time: 1:00pm GMT, 10:00am EDT, 7:00am PDT
End Time: 7:00pm GMT, 4:00pm EDT, 1:00pm PDT

1300 - 1315     Agenda bashing
1315 =AD 1330     Overview of IETF=B9s thinking in this space
1330 - 1345     Use cases: ISP-purchased + Subscriber-purchased devices
1345 - 1405     View from HGI - Duncan Bees
1405 - 1425     View from BBF - Heather Kirksey / Barbara Stark  / Ole Tran
1425 - 1445     View from Cablelabs/eRouter - Jean-Francois Mule
1445 - 1455     Break #1
1455 - 1505     View from UPnP Forum - Mark Baugher
1505 - 1525     View from IEEE 802.1 AVB - Michael Johas Teener
1525 - 1645     View from DLNA
1645 - 1700     Break #2
1700 - 1715     View from device vendor 1: Apple
1715 - 1730     View from device vendor 2: Cisco
1730 - 1745     View from device vendor 2: NetGear
1745 - 1845     Discussion of IETF focus, how to proceed
1845 - 1900     Wrap-up / Next Steps

Jason



From jason_livingood@cable.comcast.com  Mon May 31 08:24:04 2010
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 997AA3A6781 for <homegate@core3.amsl.com>; Mon, 31 May 2010 08:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.63
X-Spam-Level: ****
X-Spam-Status: No, score=4.63 tagged_above=-999 required=5 tests=[AWL=0.301, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Br4xDE7cO3oR for <homegate@core3.amsl.com>; Mon, 31 May 2010 08:24:01 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by core3.amsl.com (Postfix) with ESMTP id 1790A3A6861 for <homegate@ietf.org>; Mon, 31 May 2010 08:24:01 -0700 (PDT)
Received: from ([147.191.124.13]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.470553;  Mon, 31 May 2010 09:26:25 -0600
Received: from PAOAKEXCSMTP01.cable.comcast.com (10.52.116.30) by copdcexhub02.cable.comcast.com (147.191.124.13) with Microsoft SMTP Server id 14.0.694.0; Mon, 31 May 2010 09:23:44 -0600
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 31 May 2010 11:23:42 -0400
Received: from 68.81.100.147 ([68.81.100.147]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.152]) with Microsoft Exchange Server HTTP-DAV ; Mon, 31 May 2010 15:23:42 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 31 May 2010 11:23:39 -0400
From: Jason Livingood <jason_livingood@cable.comcast.com>
To: "homegate@ietf.org" <homegate@ietf.org>
Message-ID: <C8294CBB.24E36%jason_livingood@cable.comcast.com>
Thread-Topic: Draft BoF Agenda @ IETF 78
Thread-Index: AcrxCb9N2qdlmTFwjkWT7tcaQu80uQPxnm3dAAFBa/s=
In-Reply-To: <C829444E.24E27%jason_livingood@cable.comcast.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="B_3358149820_3298102"
X-OriginalArrivalTime: 31 May 2010 15:23:42.0680 (UTC) FILETIME=[40E25580:01CB00D5]
Subject: [homegate] Draft BoF Agenda @ IETF 78
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 May 2010 15:24:04 -0000

--B_3358149820_3298102
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

As noted in my previous email, here is a summary of the BoF request we have
sent for IETF 78.

1 - Expected Attendance: 75 People
2 - Number of sessions: 1
3 - Length of sessions: 1 Hour
4 =AD Agenda:
(Assume start of BoF is 0:00 for simplicity)
0:00 =AD 0:05     Blue Sheets, Agenda Bashing
0:05 =AD 0:10     Review of Goals of BoF
0:10 =AD 0:30     Review of Charter
0:30 =AD 0:45     Discussion of Concerns from Other SDOs / Potential Overlap
0:45 =AD 1:00     Final Discussion of Charter & How/Whether to Proceed with
Homegate

Regards
Jason


--B_3358149820_3298102
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Draft BoF Agenda @ IETF 78</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>As noted in my previous email, here is a summary of the BoF request we hav=
e sent for IETF 78.<BR>
<BR>
1 - Expected Attendance: <B>75 People</B> <BR>
2 - Number of sessions: <B>1<BR>
</B>3 - Length of sessions: <B>1 Hour<BR>
</B>4 &#8211; Agenda:<BR>
<B>(Assume start of BoF is 0:00 for simplicity)<BR>
0:00 &#8211; 0:05 &nbsp;&nbsp;&nbsp;&nbsp;Blue Sheets, Agenda Bashing<BR>
0:05 &#8211; 0:10 &nbsp;&nbsp;&nbsp;&nbsp;Review of Goals of BoF<BR>
0:10 &#8211; 0:30 &nbsp;&nbsp;&nbsp;&nbsp;Review of Charter<BR>
0:30 &#8211; 0:45 &nbsp;&nbsp;&nbsp;&nbsp;Discussion of Concerns from Other=
 SDOs / Potential Overlap<BR>
0:45 &#8211; 1:00 &nbsp;&nbsp;&nbsp;&nbsp;Final Discussion of Charter &amp;=
 How/Whether to Proceed with Homegate<BR>
<BR>
</B>Regards<BR>
Jason<B><BR>
</B></SPAN></FONT>
</BODY>
</HTML>


--B_3358149820_3298102--

From jason_livingood@cable.comcast.com  Mon May 31 08:47:02 2010
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C5FC93A67E9 for <homegate@core3.amsl.com>; Mon, 31 May 2010 08:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.781
X-Spam-Level: ***
X-Spam-Status: No, score=3.781 tagged_above=-999 required=5 tests=[AWL=0.849,  BAYES_50=0.001, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HyMjy457Dpux for <homegate@core3.amsl.com>; Mon, 31 May 2010 08:47:01 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by core3.amsl.com (Postfix) with ESMTP id 705F93A67A1 for <homegate@ietf.org>; Mon, 31 May 2010 08:47:01 -0700 (PDT)
Received: from ([147.191.124.13]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.470991;  Mon, 31 May 2010 09:49:27 -0600
Received: from PAOAKEXCSMTP01.cable.comcast.com (10.52.116.30) by copdcexhub02.cable.comcast.com (147.191.124.13) with Microsoft SMTP Server id 14.0.694.0; Mon, 31 May 2010 09:46:47 -0600
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 31 May 2010 11:46:46 -0400
Received: from 68.81.100.147 ([68.81.100.147]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.152]) with Microsoft Exchange Server HTTP-DAV ; Mon, 31 May 2010 15:46:46 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 31 May 2010 11:46:44 -0400
From: Jason Livingood <jason_livingood@cable.comcast.com>
To: "homegate@ietf.org" <homegate@ietf.org>
Message-ID: <C8295224.24E41%jason_livingood@cable.comcast.com>
Thread-Topic: [homegate] Doodle Poll - Virtual Workshop Date
Thread-Index: AcrxCa4EKYKFl6rKq0mONXxZmVF4zQPy4XycAADREIw=
In-Reply-To: <C8294CA9.24E36%jason_livingood@cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 31 May 2010 15:46:46.0160 (UTC) FILETIME=[7980A100:01CB00D8]
Subject: Re: [homegate] Doodle Poll - Virtual Workshop Date
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 May 2010 15:47:02 -0000

We have noted the proposed times below.  Please vote via Doodle poll on the
possible dates at:

http://www.doodle.com/6segkyrseasfz5it

Thanks
Jason

On 5/31/10 11:23 AM, "Jason Livingood" <jason_livingood@cable.comcast.com>
wrote:

> Based on the feedback from the advising Area Directors and co-chairs of t=
he
> continuing homegate effort, we have determined there is insufficient
> interest in and content to justify a 2-day face to face meeting prior to
> IETF 78.
>=20
> However we do believe there is value in an abbreviated, virtual meeting
> (WebEx, etc.) prior to IETF 78.  To support this we're proposing several
> possible dates, and there is a draft agenda below.  Please give us your
> feedback on the agenda and please also vote on dates at
>=20
> As for IETF 78, we have requested a second BoF (not yet approved).  I wil=
l
> send the draft agenda for the BoF under separate cover.  We received
> guidance to make that agenda short and focused.
>=20
> DRAFT VIRTUAL WORKSHOP TIMES AND AGENDA (and presenters)
>=20
> Times listed are **UTC** (so adjust to your local time zone)
> Duration: 6 Hours (with 2 breaks)
> Start Time: 1:00pm GMT, 10:00am EDT, 7:00am PDT
> End Time: 7:00pm GMT, 4:00pm EDT, 1:00pm PDT
>=20
> 1300 - 1315     Agenda bashing
> 1315 =AD 1330     Overview of IETF=B9s thinking in this space
> 1330 - 1345     Use cases: ISP-purchased + Subscriber-purchased devices
> 1345 - 1405     View from HGI - Duncan Bees
> 1405 - 1425     View from BBF - Heather Kirksey / Barbara Stark  / Ole Tr=
an
> 1425 - 1445     View from Cablelabs/eRouter - Jean-Francois Mule
> 1445 - 1455     Break #1
> 1455 - 1505     View from UPnP Forum - Mark Baugher
> 1505 - 1525     View from IEEE 802.1 AVB - Michael Johas Teener
> 1525 - 1645     View from DLNA
> 1645 - 1700     Break #2
> 1700 - 1715     View from device vendor 1: Apple
> 1715 - 1730     View from device vendor 2: Cisco
> 1730 - 1745     View from device vendor 2: NetGear
> 1745 - 1845     Discussion of IETF focus, how to proceed
> 1845 - 1900     Wrap-up / Next Steps
>=20
> Jason


From palm@broadcom.com  Mon May 31 10:21:08 2010
Return-Path: <palm@broadcom.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F5823A6A5B for <homegate@core3.amsl.com>; Mon, 31 May 2010 10:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ISx6WNbp4xZt for <homegate@core3.amsl.com>; Mon, 31 May 2010 10:21:07 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id F3C023A6A5A for <homegate@ietf.org>; Mon, 31 May 2010 10:21:06 -0700 (PDT)
Received: from [10.9.200.131] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 31 May 2010 10:20:43 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from mail-irva-12.broadcom.com (10.11.16.101) by IRVEXCHHUB01.corp.ad.broadcom.com (10.9.200.131) with Microsoft SMTP Server id 8.2.247.2; Mon, 31 May 2010 10:20:43 -0700
Received: from [10.9.252.27] (svpn-10-9-252-27.broadcom.com [10.9.252.27]) by mail-irva-12.broadcom.com (Postfix) with ESMTP id 03F6869CA8; Mon, 31 May 2010 10:20:42 -0700 (PDT)
Message-ID: <4C03EFEA.1040609@broadcom.com>
Date: Mon, 31 May 2010 10:20:42 -0700
From: "Stephen [kiwin] PALM" <palm@broadcom.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "Jason Livingood" <jason_livingood@cable.comcast.com>
References: <C8295224.24E41%jason_livingood@cable.comcast.com>
In-Reply-To: <C8295224.24E41%jason_livingood@cable.comcast.com>
X-WSS-ID: 601D306131G142374845-01-01
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] Doodle Poll - Virtual Workshop Date
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 May 2010 17:21:08 -0000

The doodle poll times seem to be off by an hour.  -kiwin

Jason Livingood wrote:
> We have noted the proposed times below.  Please vote via Doodle poll on=
 the
> possible dates at:
>=20
> http://www.doodle.com/6segkyrseasfz5it
>=20
> Thanks
> Jason
>=20
> On 5/31/10 11:23 AM, "Jason Livingood" <jason_livingood@cable.comcast.c=
om>
> wrote:
>=20
>> Based on the feedback from the advising Area Directors and co-chairs o=
f the
>> continuing homegate effort, we have determined there is insufficient
>> interest in and content to justify a 2-day face to face meeting prior =
to
>> IETF 78.
>>
>> However we do believe there is value in an abbreviated, virtual meetin=
g
>> (WebEx, etc.) prior to IETF 78.  To support this we're proposing sever=
al
>> possible dates, and there is a draft agenda below.  Please give us you=
r
>> feedback on the agenda and please also vote on dates at
>>
>> As for IETF 78, we have requested a second BoF (not yet approved).  I =
will
>> send the draft agenda for the BoF under separate cover.  We received
>> guidance to make that agenda short and focused.
>>
>> DRAFT VIRTUAL WORKSHOP TIMES AND AGENDA (and presenters)
>>
>> Times listed are **UTC** (so adjust to your local time zone)
>> Duration: 6 Hours (with 2 breaks)
>> Start Time: 1:00pm GMT, 10:00am EDT, 7:00am PDT
>> End Time: 7:00pm GMT, 4:00pm EDT, 1:00pm PDT
>>
>> 1300 - 1315     Agenda bashing
>> 1315 =AD 1330     Overview of IETF=B9s thinking in this space
>> 1330 - 1345     Use cases: ISP-purchased + Subscriber-purchased device=
s
>> 1345 - 1405     View from HGI - Duncan Bees
>> 1405 - 1425     View from BBF - Heather Kirksey / Barbara Stark  / Ole=
 Tran
>> 1425 - 1445     View from Cablelabs/eRouter - Jean-Francois Mule
>> 1445 - 1455     Break #1
>> 1455 - 1505     View from UPnP Forum - Mark Baugher
>> 1505 - 1525     View from IEEE 802.1 AVB - Michael Johas Teener
>> 1525 - 1645     View from DLNA
>> 1645 - 1700     Break #2
>> 1700 - 1715     View from device vendor 1: Apple
>> 1715 - 1730     View from device vendor 2: Cisco
>> 1730 - 1745     View from device vendor 2: NetGear
>> 1745 - 1845     Discussion of IETF focus, how to proceed
>> 1845 - 1900     Wrap-up / Next Steps
>>
>> Jason
>=20
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate
>=20

--=20
Stephen [kiwin] Palm   Ph.D.                          E:  palm@kiwin.com
Technical Director                                    T: +1-949-926-PALM
Broadcom Broadband Communications Group               F: +1-949-926-7256
Irvine, California                               W: http://www.kiwin.com
Secondary email accounts:  stephenpalm@alumni.uci.edu  palm@broadcom.com
s.palm@ieee.org  palm@itu.ch  spalm@cs.cmu.edu  palm@ics.t.u-tokyo.ac.jp


