IETF Logo Mail Archive

Re: [v6ops] Prep for v6ops IETF 84 agenda

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 29 June 2012 20:10 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 CABF121F88D5 for <v6ops@ietfa.amsl.com>; Fri, 29 Jun 2012 13:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.091
X-Spam-Level:
X-Spam-Status: No, score=-2.091 tagged_above=-999 required=5 tests=[AWL=-0.092, 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 xAqe9qoZia0B for <v6ops@ietfa.amsl.com>; Fri, 29 Jun 2012 13:10:57 -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 536E121F85A0 for <v6ops@ietf.org>; Fri, 29 Jun 2012 13:10:57 -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 q5TKAuXt018016 for <v6ops@ietf.org>; Fri, 29 Jun 2012 13:10:56 -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 q5TKAsJ0018001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 29 Jun 2012 13:10:55 -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 q5TKAsnd011757; Fri, 29 Jun 2012 15:10:54 -0500
Received: from XCH-NWHT-06.nw.nos.boeing.com (xch-nwht-06.nw.nos.boeing.com [130.247.25.110]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q5TKAsVY011733 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 29 Jun 2012 15:10:54 -0500
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-06.nw.nos.boeing.com ([130.247.25.110]) with mapi; Fri, 29 Jun 2012 13:10:53 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Date: Fri, 29 Jun 2012 13:10:52 -0700
Thread-Topic: [v6ops] Prep for v6ops IETF 84 agenda
Thread-Index: Ac1WL5ycrhwC71jqR/+m8XEHfMnATgAA3mGw
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65D376EE116@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: Fri, 29 Jun 2012 20:10:57 -0000

Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Friday, June 29, 2012 12:43 PM
> To: Templin, Fred L
> Cc: Fred Baker (fred); v6ops@ietf.org WG; Ron Bonica
> Subject: Re: [v6ops] Prep for v6ops IETF 84 agenda
> 
> 
> 
> On 6/29/2012 9:14 AM, Templin, Fred L wrote:
> > Hi Fred,
> ...
> >>> OK Fred; I'll bite. Why are you listing 'draft-generic-v6ops-tunmtu'
> >>> as "#out of charter"?
> >>
> >> Because changes to section 4.5 of RFC 2460 ("a source node may divide
> the
> >> packet...") is a change to RFC 2460, and should be discussed by the
> folks
> >> maintaining RFC 2460.
> >
> > OK, I think I get your meaning now. You are concerned
> > that the draft in its current form seems to call for
> > an update to RFC2460 - right?
> >
> > I'd like to propose a second alternative. Rather than
> > taking this over to 6man, my draft could be revised to
> > become a problem statement only rather than a functional
> > specification. Then, the fact that "(only) a source node
> > may divide the packet" becomes a problem to be addressed
> > in a different document - and not something to be defied
> > by this document.
> 
> I was expecting a differrent approach:
> 
> 	a) revise this doc to focus on ops issues that
> 	don't require any standards changes
> 
> 	b) propose the problem of IPv6 downstream refragmentation
> 	in a separate doc in a different WG

That sounds like a reasonable approach that can be
accommodated within the draft cutoff date timeframe.

> Even a problem statement for (b) would need to be handled in a non-ops
> WG, AFAICT.

OK - Thanks.

Fred
 
> Joe

v2.23.0 | Report a Bug | By Email