Re: [BEHAVE] IETF77 recharter / milestone discussion
"Dan Wing" <dwing@cisco.com> Tue, 09 March 2010 17:49 UTC
Return-Path: <dwing@cisco.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B12AC3A6969 for <behave@core3.amsl.com>; Tue, 9 Mar 2010 09:49:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.458
X-Spam-Level:
X-Spam-Status: No, score=-10.458 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N3OxBwfKMTPz for <behave@core3.amsl.com>; Tue, 9 Mar 2010 09:49:41 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id C75373A681D for <behave@ietf.org>; Tue, 9 Mar 2010 09:49:41 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwIAFIZlkurRN+K/2dsb2JhbACHVIESkk9zpRGZGoR5BIMX
X-IronPort-AV: E=Sophos;i="4.49,609,1262563200"; d="scan'208";a="216284870"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-3.cisco.com with ESMTP; 09 Mar 2010 17:49:46 +0000
Received: from dwingwxp01 ([10.32.240.195]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o29Hnk1r009399; Tue, 9 Mar 2010 17:49:46 GMT
From: Dan Wing <dwing@cisco.com>
To: 'behave' <behave@ietf.org>
References:
Date: Tue, 09 Mar 2010 09:49:46 -0800
Message-ID: <2cb201cabfb0$e8366a30$667a150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acq+MDzbR1eXJsDyRQuNScf9Uxy76wBgId2g
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To:
Cc: behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] IETF77 recharter / milestone discussion
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 17:49:42 -0000
The list of Problems we plan to discuss is now maintained at http://trac.tools.ietf.org/wg/behave/trac/wiki/WikiStart -d > -----Original Message----- > From: Dan Wing [mailto:dwing@cisco.com] > Sent: Sunday, March 07, 2010 11:56 AM > To: 'behave' > Cc: 'behave-chairs@tools.ietf.org' > Subject: IETF77 recharter / milestone discussion > > During Friday's BEHAVE session we will be discussing rechartering > and milestones for BEHAVE. Our current charter is available at > http://www.ietf.org/dyn/wg/charter/behave-charter and as soon > as we send the six IPv6/IPv4 translation documents to the IESG, > we will have completed many of those items. There is still > outstanding work, though, which needs to be discussed. > > > If you are presenting an individual draft in BEHAVE, which > you want to have the working group consider as a charter > item, it is your responsibility to use YOUR PRESENTATION > TIME to motiviate the working group. > > > During the rechartering discussion time, we do not want to > discuss particular SOLUTIONS. Rather, we want to discuss > particular PROBLEMS. Specifically, we want to determine > if the problem is important enough to add to the charter, > and if there is sufficient energy to work on a solution. > > > Below is what we intend to discuss around re-chartering > and milestones. If you see something missing from the list, > please reply to the chairs or the mailing list. > > > currently-chartered work, with milestones. We need to > decide new deadlines. > - SCTP NAT > * draft-ietf-behave-sctpnat > > currently-chartered work, without milestones. We need to > decide if there is interest and if can solve these: > - BEHAVE scenario 3 (An IPv4 network to IPv6 Internet) > * draft-liu-behave-nat46 > * draft-huang-behave-pnat > * draft-huang-behave-rfc2767bis > * draft-huang-behave-rfc3338bis > * draft-thaler-6man-unique-v4mapped > - BEHAVE scenario 4 (IPv4 Internet to an IPv6 network) > * draft-perkins-behave-dpinat > * draft-perkins-sourceipnat > * draft-xli-behave-dns46-for-stateless > * draft-wing-behave-http-46-relay > - multicast IPv6/IPv4 translation > (Scope: IPv6 senders and IPv4 listeners, or > IPv4 senders and IPv6 listeners? > SSM or ASM?) > * draft-venaas-behave-v4v6mc-framework > * draft-jiang-behave-v4v6mc-proxy > > > non-chartered work. We need to decide if there is interest, > and if we can solve these: > - IPv6-only hosts encountering IPv4 address literals > * draft-wing-behave-http-ip-address-literals > * draft-wing-v6ops-v6app-v4server > - avoiding NAT64 with dual-stack host > * draft-wing-behave-dns64-config > * draft-boucadair-behave-dns-a64 > * draft-boucadair-behave-dns64-discovery > * draft-cao-behave-dsdns64 > - high availability stateful NAT > * draft-chen-behave-rsnat > * draft-xu-behave-nat-state-sync > * draft-xu-behave-stateful-nat-standby > - NAT load balancing > * draft-chen-behave-olnat > * draft-wang-behave-nat64-load-balancer > - analysis against NAT-PT > * draft-penno-behave-64-analysis > > -d >
- [BEHAVE] IETF77 recharter / milestone discussion Dan Wing
- Re: [BEHAVE] IETF77 recharter / milestone discuss… Dan Wing
- Re: [BEHAVE] IETF77 recharter / milestone discuss… Dave Thaler
- Re: [BEHAVE] IETF77 recharter / milestone discuss… Brian E Carpenter