IETF Logo Mail Archive

Re: [Call-home] bof at vancouver?

Eliot Lear <lear@cisco.com> Sun, 09 October 2005 11:41 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOZYD-0002wF-CA; Sun, 09 Oct 2005 07:41:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOZYB-0002vz-GX for call-home@megatron.ietf.org; Sun, 09 Oct 2005 07:41:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10895 for <call-home@ietf.org>; Sun, 9 Oct 2005 07:41:06 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EOZhr-0000fc-FM for call-home@ietf.org; Sun, 09 Oct 2005 07:51:08 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 09 Oct 2005 04:40:55 -0700
X-IronPort-AV: i="3.97,190,1125903600"; d="scan'208"; a="664533437:sNHT22763700"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j99Beq4u018440; Sun, 9 Oct 2005 04:40:52 -0700 (PDT)
Received: from [212.254.247.3] (ams-clip-vpn-dhcp61.cisco.com [10.61.64.61]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j99BpsAj025657; Sun, 9 Oct 2005 04:51:55 -0700
Message-ID: <434901C2.50106@cisco.com>
Date: Sun, 09 Oct 2005 13:40:50 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: j.schoenwaelder@iu-bremen.de
Subject: Re: [Call-home] bof at vancouver?
References: <4348EA06.6080900@cisco.com> <20051009113509.GB2123@boskop.local>
In-Reply-To: <20051009113509.GB2123@boskop.local>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=387; t=1128858715; x=1129290915; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=lear@cisco.com; z=Subject:Re=3A=20[Call-home]=20bof=20at=20vancouver?| From:Eliot=20Lear=20<lear@cisco.com>| Date:Sun,=2009=20Oct=202005=2013=3A40=3A50=20+0200| Content-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowed| Content-Transfer-Encoding:7bit; b=TQt0DE2iFeR2XJxww4zg/DL7vjrsTClN7rxK4kvYmrqg1cWXr8odabjN07RKP1ollEV9/Wg2 jvcvVGPmu1AwLKGTnC0cqf59Iaqi14c52W1NcHp7IUDxWebjhzlIdGgDJFr6RZG4JOieHOg32ov Iw9Qc7Otd+tVCd1sKBKoO014=
Authentication-Results: imail.cisco.com; header.From=lear@cisco.com; dkim=pass ( message from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Cc: call-home@ietf.org
X-BeenThere: call-home@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion of issues relating to &quot; call home&quot; functionality and firewall traversal" <call-home.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/call-home>, <mailto:call-home-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/call-home>
List-Post: <mailto:call-home@ietf.org>
List-Help: <mailto:call-home-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/call-home>, <mailto:call-home-request@ietf.org?subject=subscribe>
Sender: call-home-bounces@ietf.org
Errors-To: call-home-bounces@ietf.org

Juergen,
> Bert also offered the option to use some time in the ops area meeting.
> Is this option off the table now?
> 

I think so, but for the record I am fine with either option.  Perhaps 
others would like to express an opinion.  One issue that was raised was 
whether the other groups would have sufficient visibility to call-home 
if it's in the ops-area group.  BoFs, on the other hand, seem to have a 
lot more formality tied to them.  Again, I'm fine with either option.

Eliot

_______________________________________________
Call-home mailing list
Call-home@ietf.org
https://www1.ietf.org/mailman/listinfo/call-home

v2.23.0 | Report a Bug | By Email