IETF Logo Mail Archive

[eppext] Meeting at IETF-93?

"Hollenbeck, Scott" <shollenbeck@verisign.com> Mon, 08 June 2015 18:10 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E748E1A89ED for <eppext@ietfa.amsl.com>; Mon, 8 Jun 2015 11:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.1
X-Spam-Level:
X-Spam-Status: No, score=0.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mwA6I3lwdqw8 for <eppext@ietfa.amsl.com>; Mon, 8 Jun 2015 11:10:17 -0700 (PDT)
Received: from mail-oi0-f100.google.com (mail-oi0-f100.google.com [209.85.218.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 016721B3174 for <eppext@ietf.org>; Mon, 8 Jun 2015 11:10:13 -0700 (PDT)
Received: by oiav63 with SMTP id v63so7665168oia.0 for <eppext@ietf.org>; Mon, 08 Jun 2015 11:10:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:accept-language:content-language:content-type :content-transfer-encoding:mime-version; bh=lNo7UMA7XJufXe8Q3KMwUroxuEPWuD2NINOJl/tYgpQ=; b=VP5FWq+C81p5eGKTJg+z3PTV201tLw5DiSwvZAB3TNFTw3TwIQyBPbaryJs3H59qxB anQ1GRD9bs7T+SJ5yyta7UD2/DDQxBXbNuYPbShQ6HMJGhZt48w/YrtuJSD/7uevjEUb N0l4H7GDd37/1MWsTJs+YOxF+lGm5DUdQGz/lhLw/6MIdKJS5VXbTkC5PU/4r/K1ZYu9 V0/crZWEWVlD98eFGdwJXi1g4XpmGLsvxMnPFB3+6WsbGPNV97m7JXna7u5jnyfrBPT5 bR4Ecv6s+Smbg7tp+NSRPxCQqF/U7/t5qAElDcs5d5AHLgBbsKqcBY7Ic+PyeiUSxC/+ 10Cg==
X-Gm-Message-State: ALoCoQkG1nQlgU6zkQdaKJfjpJZ9OMbjZGlyDxPAucoIojQSoMWv0SPRexxxV9v0FeDi6PPTptdknYvqFEU3CNDVXxh/kUTqJw==
X-Received: by 10.55.19.140 with SMTP id 12mr34889135qkt.64.1433787013270; Mon, 08 Jun 2015 11:10:13 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by mx.google.com with ESMTPS id lx8sm925073qcb.2.2015.06.08.11.10.12 for <eppext@ietf.org> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 08 Jun 2015 11:10:13 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01 [10.173.152.255]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t58IACw3020605 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <eppext@ietf.org>; Mon, 8 Jun 2015 14:10:12 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 8 Jun 2015 14:10:12 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: Meeting at IETF-93?
Thread-Index: AdCiFlxIBlLW6ssnQbuUxRQYKlKenQ==
Date: Mon, 8 Jun 2015 18:10:12 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F49FEFDF7@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/v_pftgxbahhBWykisWErRh9bv0Y>
Subject: [eppext] Meeting at IETF-93?
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jun 2015 18:10:22 -0000

IETF-93 is rapidly approaching. Travel plans need to be made. Is this WG planning to request a meeting slot? If so, could we do that before we get a Friday afternoon slot again?

Scott

v2.8.7 | Report a Bug | By Email