IETF Logo Mail Archive

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

Fred Baker <fred@cisco.com> Mon, 04 April 2011 21:25 UTC

Return-Path: <fred@cisco.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 B65AB3A680F for <v6ops@core3.amsl.com>; Mon, 4 Apr 2011 14:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.467
X-Spam-Level:
X-Spam-Status: No, score=-110.467 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 Y4WbbJE-jsQw for <v6ops@core3.amsl.com>; Mon, 4 Apr 2011 14:25:10 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 266733A67EC for <v6ops@ietf.org>; Mon, 4 Apr 2011 14:25:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2057; q=dns/txt; s=iport; t=1301952413; x=1303162013; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=XWUmJE8A+WdjG+uQocpxpeOxBdkbddwyfG2FgTs2Mzw=; b=bp+DmI5hILQpw6Xxkbl2rZE1RjP9yw0K2VZzC9SwgTABB495y/BQaYAO xlbrcZ/ir5ZE5xESeAjXaqGyyyABtANrDp3PEGjIgCWmHip2xRG/Eip5H lDzArSHDFkGFHYBVQ6Ob3/FbCh17f0iOuts0YrQ4CcNou31PyTdrHftvs U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtMAAIo2mk2Q/khLgWdsb2JhbACYII1EFAEBFiYliHmeGpwTgwiCYwSNI4Nb
X-IronPort-AV: E=Sophos;i="4.63,299,1299456000"; d="scan'208";a="24406608"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 04 Apr 2011 21:26:51 +0000
Received: from Freds-Computer.local (dhcp-10-61-103-118.cisco.com [10.61.103.118]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p34LQlUp010676; Mon, 4 Apr 2011 21:26:51 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Mon, 04 Apr 2011 23:26:51 +0200
X-PGP-Universal: processed; by Freds-Computer.local on Mon, 04 Apr 2011 23:26:51 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65C69182053@XCH-NW-01V.nw.nos.boeing.com>
Date: Mon, 04 Apr 2011 23:26:39 +0200
Message-Id: <034350B5-9AD6-46DE-BD29-88B94BE4D1DA@cisco.com>
References: <EA2927DA-41EB-44D6-9494-80150863AD15@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A65C69182053@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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: Mon, 04 Apr 2011 21:25:11 -0000

For a change to a protocol specification? I would start by finding a working group chartered to work on protocols, and discuss it with the chair.

We've been over this, Fred, many many times. You knew the answer before you wrote the email. Act accordingly.

On Apr 4, 2011, at 11: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.

v2.23.0 | Report a Bug | By Email