Re: [v6ops] Prep for v6ops IETF 84 agenda

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 10 July 2012 00:05 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 735FE11E80D1 for <v6ops@ietfa.amsl.com>; Mon, 9 Jul 2012 17:05:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.114
X-Spam-Level:
X-Spam-Status: No, score=-2.114 tagged_above=-999 required=5 tests=[AWL=-0.115, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qb-InZewg51L for <v6ops@ietfa.amsl.com>; Mon, 9 Jul 2012 17:05:21 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id AD0D221F86A5 for <v6ops@ietf.org>; Mon, 9 Jul 2012 17:05:20 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q6A05jw1001370 for <v6ops@ietf.org>; Mon, 9 Jul 2012 17:05:46 -0700
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [130.247.228.54]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q6A05ilE001361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 9 Jul 2012 17:05:45 -0700
Received: from stl-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q6A05iX1026037; Mon, 9 Jul 2012 19:05:44 -0500
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q6A05hS5026018 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 9 Jul 2012 19:05:44 -0500
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Mon, 9 Jul 2012 17:05:43 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Date: Mon, 09 Jul 2012 17:05:42 -0700
Thread-Topic: [v6ops] Prep for v6ops IETF 84 agenda
Thread-Index: Ac1WL5ycrhwC71jqR/+m8XEHfMnATgH/y8og
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65D8F24CE9B@XCH-NW-01V.nw.nos.boeing.com>
References: <8D73E1D6-A968-4397-A843-FE073197B7F1@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A65D376EDA9D@XCH-NW-01V.nw.nos.boeing.com> <C11C2C67-04A6-40DB-888B-3349CB82EB93@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A65D376EDF64@XCH-NW-01V.nw.nos.boeing.com> <4FEE0533.1060203@isi.edu>
In-Reply-To: <4FEE0533.1060203@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: No
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] Prep for v6ops IETF 84 agenda
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 10 Jul 2012 00:05:21 -0000

Hi Joe,

I have taken your suggestion and now have two separate
documents:

> I was expecting a differrent approach:
> 
> 	a) revise this doc to focus on ops issues that
> 	don't require any standards changes

Here is the original one that has now been revised to
focus on ops issues that don't require any standards
changes:

https://datatracker.ietf.org/doc/draft-generic-v6ops-tunmtu/

> 
> 	b) propose the problem of IPv6 downstream refragmentation
> 	in a separate doc in a different WG

and, here is a new one that addresses fragmentation
in a separate doc in the 6man WG:

http://www.ietf.org/id/draft-generic-6man-tunfrag-02.txt

Thanks - Fred
fred.l.templin@boeing.com