IETF Logo Mail Archive

[v6ops] Proposed agenda

"Fred Baker (fred)" <fred@cisco.com> Sat, 15 February 2014 01:44 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 F0BA91A0020 for <v6ops@ietfa.amsl.com>; Fri, 14 Feb 2014 17:44:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.049
X-Spam-Level:
X-Spam-Status: No, score=-110.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, 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 QHL4-96VCywB for <v6ops@ietfa.amsl.com>; Fri, 14 Feb 2014 17:44:57 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id AC1EE1A0018 for <v6ops@ietf.org>; Fri, 14 Feb 2014 17:44:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4299; q=dns/txt; s=iport; t=1392428696; x=1393638296; h=from:to:cc:subject:date:message-id:mime-version; bh=1rmoCYN1nd6EqrWcc3vCYvJPRwTtNOBMgI/fG8n8y1U=; b=BICwwAKPoCJLDC5nJ4VnI1kmc5PHrokIfOcUxxAfIkKOMEucXinMCuYk GtY2vLx8yFsvUkqcJUGSDuhywmiX/v5uYKqYleswEHJk45TNTgAIPrahI A8ZJeY66yc30Gp75Y2KbtXuvHUwr8Ppo+whqf4nIKq2jZSSsUUNhupwNE Q=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAC7G/lKtJV2d/2dsb2JhbABZgwY4V780gRcWdIIsZRQSAYEAJwQOBQ6Hdw3IYReOGREBUIMrgRQEkECBMoY6gTKQcYMtgXE5
X-IronPort-AV: E=Sophos; i="4.95,848,1384300800"; d="asc'?scan'208"; a="20644829"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP; 15 Feb 2014 01:44:55 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s1F1itZT006660 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 15 Feb 2014 01:44:55 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.202]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0123.003; Fri, 14 Feb 2014 19:44:55 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>
Thread-Topic: Proposed agenda
Thread-Index: AQHPKe+GQ54cQ4Ch+0GNXdWWzntzpw==
Date: Sat, 15 Feb 2014 01:44:55 +0000
Message-ID: <E40F2B19-A4C8-4DED-91B8-B6590224A268@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.119]
Content-Type: multipart/signed; boundary="Apple-Mail=_375DAD77-1839-4B5E-8A5A-8AF2269308C8"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/xtsPXRaCzMtqADZN-O_n2vMnlwA
Subject: [v6ops] Proposed 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: Sat, 15 Feb 2014 01:45:00 -0000

As usual, John and I spoke Wednesday and have been watching drafts posted today. The guideline we use, as usual, is that we want to look at drafts that are in the "I-D exists" state, have been updated since the previous IETF, and in which the working group has shown interest. As of 23:59 UTC, the drafts targeting our working group, and our analysis of them, include:

RFC Ed Queue:
    Feb 14  draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat

IESG:
    Oct  6  draft-ietf-v6ops-64share
    Jan 13  draft-ietf-v6ops-nat64-experience

Exiting WGLC; on its way to IESG:
    Jan 12  draft-ietf-v6ops-enterprise-incremental-ipv6

Working Group Document updated since IETF 88:
    Nov 26  draft-ietf-v6ops-dhcpv6-slaac-problem
    Dec  6  draft-ietf-v6ops-balanced-ipv6-security
    Jan 13  draft-ietf-v6ops-ipv6-roaming-analysis
    Feb  4  draft-ietf-v6ops-dc-ipv6
    Feb 14  draft-ietf-v6ops-ula-usage-recommendations

Individual Submission updated since IETF 88:
    Dec  3  draft-taylor-v6ops-fragdrop
    Dec 28  draft-byrne-v6ops-clatip
    Feb 14  draft-liu-v6ops-dhcpv6-slaac-guidance

Individual Submission updated since IETF 88 but little/negtive interest shown:
    Jan 11  draft-osamu-v6ops-ipv4-literal-in-url
    Feb 14  draft-cui-v6ops-lte-lw4over6
    Feb 14  draft-foo-v6ops-6rdmtu

Working Group Document NOT updated since IETF 88:
    Aug 14  draft-ietf-v6ops-monitor-ds-ipv6
    Sep 10  draft-ietf-v6ops-mobile-device-profile

Individual Submission NOT updated since IETF 88:
    Oct  3  draft-elkins-v6ops-ipv6-end-to-end-rt-needed
    Oct  3  draft-elkins-v6ops-ipv6-packet-sequence-needed
    Oct  3  draft-elkins-v6ops-ipv6-pdm-recommended-usage
    Oct 18  draft-ma-v6ops-router-test
    Oct 21  draft-moreiras-v6ops-rfc3849bis
    Oct 21  draft-rafiee-v6ops-iid-lifetime
    Oct 21  draft-sun-v6ops-openv6-address-pool-management
    Oct 21  draft-yang-v6ops-ipv6tran-select



By that logic, the drafts on our agenda will include

    draft-ietf-v6ops-dhcpv6-slaac-problem
    draft-liu-v6ops-dhcpv6-slaac-guidance
    draft-ietf-v6ops-balanced-ipv6-security
    draft-ietf-v6ops-ipv6-roaming-analysis
    draft-ietf-v6ops-dc-ipv6
    draft-ietf-v6ops-ula-usage-recommendations
    draft-taylor-v6ops-fragdrop
    draft-byrne-v6ops-clatip

This is of course open to change; that's why it's called a "proposed agenda". Please post to the list.

Our meetings are Wednesday morning and Thursday afternoon. With 8 drafts, I imagine we'll schedule 4 each day, or five and three. 

Implications for people speaking: plan on about half hour sessions, with ten or at most fifteen minutes in presentation and the difference in discussion. People usually use slides, although that's far from a requirement. Please email slides in ppt, pptx, or pdf format to v6ops-chairs@tools.ietf.org no later than Saturday March 1, and tell us who will be the speaker.

Implications for the rest of us: 

please read the drafts, and if you care to, comment to the list.

http://tools.ietf.org/html/draft-ietf-v6ops-dhcpv6-slaac-problem
http://tools.ietf.org/html/draft-liu-v6ops-dhcpv6-slaac-guidance
http://tools.ietf.org/html/draft-ietf-v6ops-balanced-ipv6-security
http://tools.ietf.org/html/draft-ietf-v6ops-ipv6-roaming-analysis
http://tools.ietf.org/html/draft-ietf-v6ops-dc-ipv6
http://tools.ietf.org/html/draft-ietf-v6ops-ula-usage-recommendations
http://tools.ietf.org/html/draft-taylor-v6ops-fragdrop
http://tools.ietf.org/html/draft-byrne-v6ops-clatip

The chairs have requested MeetEcho

v2.23.0 | Report a Bug | By Email