Re: [v6ops] draft-ietf-v6ops-tunnel-loops WGLC

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 05 April 2011 19:35 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 767CE3A6983 for <v6ops@core3.amsl.com>; Tue, 5 Apr 2011 12:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.043
X-Spam-Level:
X-Spam-Status: No, score=-6.043 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
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 zJNSX0G2wi25 for <v6ops@core3.amsl.com>; Tue, 5 Apr 2011 12:35:26 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 276DB3A698A for <v6ops@ietf.org>; Tue, 5 Apr 2011 12:35:26 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p35JaleF001702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 5 Apr 2011 14:36:50 -0500 (CDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p35JalCM021398; Tue, 5 Apr 2011 12:36:47 -0700 (PDT)
Received: from XCH-NWHT-01.nw.nos.boeing.com (xch-nwht-01.nw.nos.boeing.com [130.247.70.222]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p35Jaljb021391 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 5 Apr 2011 12:36:47 -0700 (PDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-01.nw.nos.boeing.com ([130.247.70.222]) with mapi; Tue, 5 Apr 2011 12:36:47 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joel Jaeggli <joelja@bogus.com>
Date: Tue, 05 Apr 2011 12:36:46 -0700
Thread-Topic: [v6ops] draft-ietf-v6ops-tunnel-loops WGLC
Thread-Index: AcvzUDRM2mOtkkiRQa2DEaX0IaAQ8gAdJI0g
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C691F0343@XCH-NW-01V.nw.nos.boeing.com>
References: <EA2927DA-41EB-44D6-9494-80150863AD15@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A65C69182053@XCH-NW-01V.nw.nos.boeing.com> <4D9AA4F5.3090409@bogus.com>
In-Reply-To: <4D9AA4F5.3090409@bogus.com>
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
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "v6ops-chairs@tools.ietf.org" <v6ops-chairs@tools.ietf.org>, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-tunnel-loops WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 05 Apr 2011 19:35:28 -0000

Hi Joel,

That's a good idea about filing an errata - the thought
hadn't occurred to me, so thanks for mentioning it.

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Joel Jaeggli [mailto:joelja@bogus.com] 
> Sent: Monday, April 04, 2011 10:13 PM
> To: Templin, Fred L
> Cc: Fred Baker; v6ops@ietf.org; v6ops-chairs@tools.ietf.org; 
> Ron Bonica
> Subject: Re: [v6ops] draft-ietf-v6ops-tunnel-loops WGLC
> 
> Seems like an application for an errata, if it indeed is simply an
> implmentation pitfall. the informational document should not 
> be wrongly
> be assumed to depricate any part of 5214 since it doesn't claim that
> from outset.
> 
> I'd prefer that we continue the last call with the document 
> that we have
> given this also in the form that has cleared the iesg once already.
> 
> On 4/4/11 2:08 PM, Templin, Fred L wrote:
> > Hi Fred,
> >  
> > It may seem unusual for an author to comment on their own document,
> > however in the case of ISATAP at least I am concerned that this new
> > version may encourage router vendors to build products that do not
> > provide necessary support for legacy hosts.
> >  
> > In particular, I have come to understand that legacy ISATAP hosts
> > depend on the router advertising non-link-local IPv6 prefixes on its
> > ISATAP interface. If a router vendor were to read the 
> recommendations
> > in this new version of the document, however, they might incorrectly
> > conclude that the use of non-link-local IPv6 prefixes on ISATAP
> > interfaces should be deprecated.
> >  
> > This seems like something that could be corrected with the addition
> > of 1-2 sentences. How would you like to proceed?
> >  
> > Thanks - Fred
> > 
> >     
> --------------------------------------------------------------
> ----------
> >     *From:* v6ops-bounces@ietf.org 
> [mailto:v6ops-bounces@ietf.org] *On
> >     Behalf Of *Fred Baker
> >     *Sent:* Thursday, March 31, 2011 2:30 AM
> >     *To:* v6ops@ietf.org
> >     *Cc:* v6ops-chairs@tools.ietf.org; Ron Bonica
> >     *Subject:* [v6ops] draft-ietf-v6ops-tunnel-loops WGLC
> > 
> >     This is to initiate a one week working group last call of
> >     draft-ietf-v6ops-tunnel-loops; it will close a week 
> from Friday. The
> >     IESG reviewed the document and asked for changes; we 
> need to be sure
> >     we are comfortable with the changes. The diff from the 
> version sent
> >     to the IESG last November is at http://tinyurl.com/6dhowhf
> > 
> >     Please read it now. If you find nits (spelling errors, minor
> >     suggested wording changes, etc), comment to the 
> authors; if you find
> >     greater issues, such as disagreeing with a statement or finding
> >     additional issues that need to be addressed, please post your
> >     comments to the list.
> > 
> > 
> > 
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> 
>