IETF Logo Mail Archive

RE: [Call-home] BoF at IETF64

"Romascanu, Dan \(Dan\)" <dromasca@avaya.com> Wed, 26 October 2005 09:54 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUhzZ-0003Hq-OS; Wed, 26 Oct 2005 05:54:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUhzX-0003Hi-J8 for call-home@megatron.ietf.org; Wed, 26 Oct 2005 05:54:43 -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 FAA08095 for <call-home@ietf.org>; Wed, 26 Oct 2005 05:54:27 -0400 (EDT)
Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUiCf-0003TV-AI for call-home@ietf.org; Wed, 26 Oct 2005 06:08:18 -0400
Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j9Q9egBM012541 for <call-home@ietf.org>; Wed, 26 Oct 2005 05:40:42 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j9Q9eeBM012515 for <call-home@ietf.org>; Wed, 26 Oct 2005 05:40:41 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Call-home] BoF at IETF64
Date: Wed, 26 Oct 2005 11:54:34 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F095C74C3@is0004avexu1.global.avaya.com>
Thread-Topic: [Call-home] BoF at IETF64
Thread-Index: AcXaEiDW4o3tiv+UTk6ZoGPxRriwhQAAM+CA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Eliot Lear <lear@cisco.com>, call-home@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: quoted-printable
Cc:
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

This is facing the opsec (Operational Security Capabilities for IP
Network Infrastructure WG) meeting. Any reason not to schedule it in the
slot before 1740 - 1840, which does not seem to hide any visible
conflict. 

Regards,

Dan


 
 

> -----Original Message-----
> From: call-home-bounces@ietf.org 
> [mailto:call-home-bounces@ietf.org] On Behalf Of Eliot Lear
> Sent: Wednesday, October 26, 2005 11:40 AM
> To: call-home@ietf.org
> Subject: [Call-home] BoF at IETF64
> 
> All,
> 
> A BoF has been scheduled for callhome.  I am working to 
> finalize the agenda.  If you wish to speak, please send me a 
> note.  We are currently slated to meet during the Tuesday 
> 18:50 - 19:50 session.
> 
> Eliot
> 
> _______________________________________________
> Call-home mailing list
> Call-home@ietf.org
> https://www1.ietf.org/mailman/listinfo/call-home
> 

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

v2.23.0 | Report a Bug | By Email