Re: [v6ops] Preparing an agenda
"Fred Baker (fred)" <fred@cisco.com> Thu, 13 November 2014 05:08 UTC
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BACE61A1B8E for <v6ops@ietfa.amsl.com>; Wed, 12 Nov 2014 21:08:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.095
X-Spam-Level:
X-Spam-Status: No, score=-115.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 2htsM4Yt2y1B for <v6ops@ietfa.amsl.com>; Wed, 12 Nov 2014 21:08:19 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7A691A1B86 for <v6ops@ietf.org>; Wed, 12 Nov 2014 21:08:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2881; q=dns/txt; s=iport; t=1415855299; x=1417064899; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Qjzjdcau/hYl45FbKHgvSODLpMlImeDioOh6HBjYWGo=; b=dh+suZYWjplBH3MZttFifpZMjNL1kJvSQ2wuyaAyp1AVBo81lqu1hzor CfVPhw38AY4ap0HSH+4NFs0Ly0wvkCyO+/i28B7NDKDwdkMv+Vd4DxZiN gpaw7R8pQ8PQQ2zqOAMPgxWJcN6Xqo7ynRei1BVXZOGDKAoiOKnSUhtaK I=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAEc8ZFStJA2E/2dsb2JhbABcgw5UWQTMVgyHTQKBHRYBAQEBAX2EAwEBAwEBAQFrEAsCAQhGJwslAgQTDogqCQ3PMwEBAQEBAQEBAQEBAQEBAQEBAQEBAReRG4MtgR4FkjqCGIFSaYckgXGUdoN8bYFIgQMBAQE
X-IronPort-AV: E=Sophos;i="5.07,374,1413244800"; d="asc'?scan'208";a="96140015"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-3.cisco.com with ESMTP; 13 Nov 2014 05:08:19 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id sAD58INm015494 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <v6ops@ietf.org>; Thu, 13 Nov 2014 05:08:19 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.248]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Wed, 12 Nov 2014 23:08:18 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] Preparing an agenda
Thread-Index: AQHP/v/W7E6IKRmCiE+NpzoxBahXeg==
Date: Thu, 13 Nov 2014 05:08:18 +0000
Message-ID: <314EC709-3716-4DC5-BDA1-B2904624B999@cisco.com>
References: <201411130505.sAD55IB3019305@irp-lnx1.cisco.com>
In-Reply-To: <201411130505.sAD55IB3019305@irp-lnx1.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.91.88]
Content-Type: multipart/signed; boundary="Apple-Mail=_B28A6604-65FF-48C4-B90E-C2F396BB10FA"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/cGNjVVyIUBShqutw25BDaBcR1G0
Subject: Re: [v6ops] Preparing an agenda
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Nov 2014 05:08:21 -0000
Apologies for these two messages. I’m scheduling a message, and it misfired. Oops, operational problem on my part. On Nov 12, 2014, at 7:05 PM, fred@cisco.com wrote: > Permit me to point out that the IETF will be meeting in Prague on July > 19-24. It is now six weeks before that date. If you have a draft that you > would like to discuss, we need for you to post the -00 version in enough > time that the list has a chance to comment on it, as we put things on the > agenda that are new or have been updated since the past meeting, and have > had supportive discussion on the mailing list. Time to start typing... > > Draft status as of today is: > > IESG: > > Sep 26 draft-ietf-v6ops-mobile-device-profile > Oct 19 draft-ietf-v6ops-ipv6-roaming-analysis > Nov 10 draft-ietf-v6ops-6to4-to-historic > > Exiting WGLC; on its way to IESG: > > Working Group Document NOT updated since IETF: > > Sep 18 draft-ietf-v6ops-design-choices > Oct 27 draft-ietf-v6ops-dhcpv6-slaac-problem > Oct 27 draft-ietf-v6ops-ula-usage-recommendations > > Individual Submission NOT updated since IETF: > > Jul 4 draft-sun-v6ops-xlat-multi > Jul 4 draft-yourtchenko-chown-rupik-v6ops-dad-3x > Jul 20 draft-wang-v6ops-flow-label-refelction > Aug 24 draft-v6ops-pmtud-ecmp-problem > Sep 10 draft-gont-v6ops-ipv6-ehs-in-real-world > Sep 15 draft-anderson-v6ops-siit-dc-2xlat > Sep 18 draft-elkins-v6ops-multicast-virtual-nodes > Sep 18 draft-wang-v6ops-xlat-prefix-discovery > Sep 25 draft-ybai-v6ops-ipv6-for-openstack > Oct 5 draft-anderson-v6ops-siit-dc > Oct 11 draft-liu-v6ops-running-multiple-prefixes > Oct 27 draft-chen-v6ops-nfv-ipv6 > Oct 27 draft-liu-v6ops-dhcpv6-slaac-guidance > Oct 27 draft-osamu-v6ops-ipv4-literal-in-url > Oct 27 draft-vyncke-v6ops-happy-eyeballs-cookie > > more data at http://datatracker.ietf.org/doc/search/?sort=status&activedrafts=on&name=v6ops > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops
- [v6ops] Preparing an agenda fred
- [v6ops] Preparing an agenda fred
- Re: [v6ops] Preparing an agenda Fred Baker (fred)
- Re: [v6ops] Preparing an agenda Lee Howard
- Re: [v6ops] Preparing an agenda Fred Baker (fred)