IETF Logo Mail Archive

Re: [v6ops] new draft: draft-v6ops-pmtud-ecmp-problem

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 03 September 2014 01:15 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3FE1A892F for <v6ops@ietfa.amsl.com>; Tue, 2 Sep 2014 18:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kL8MQ-DFIhYh for <v6ops@ietfa.amsl.com>; Tue, 2 Sep 2014 18:15:49 -0700 (PDT)
Received: from mail-oa0-x243.google.com (mail-oa0-x243.google.com [IPv6:2607:f8b0:4003:c02::243]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D76FE1A0072 for <v6ops@ietf.org>; Tue, 2 Sep 2014 18:15:48 -0700 (PDT)
Received: by mail-oa0-f67.google.com with SMTP id m1so1760189oag.2 for <v6ops@ietf.org>; Tue, 02 Sep 2014 18:15:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=j3ysaTESvhzqmbHYjptbD2dx77Z3kCJ5gmLHJGi59/o=; b=pblfzlrPDvfcI2OO9YC6ObM6JAgHbbOFGvplrBEoz7BHKFXKyCzTioc8mW05J4bVJ2 obzNYWAb21uAGff9LAygWTcqsQJ6RH+IaL7cg7+oiSEe0lLRZbOeTH8MkbcbK5dSs9ax aIYhFwHToUAgUktYWT66BZjJ4pevrZcswore/el7BSqfRK0dph/fkqoTFQ/ZD00Bf4ki IBLBH6qhOKetGmXaWAqJPhrJHRvYHxlz4iI5rf1eIOilQsSRzezPnRrcwF7uUa9L0Vc4 4G3jEaSTE+gnWfvPzgkcAr6XzSAga6kYnLWUX/zDWLNAqoGElXes90ihVHGjyJWWnMlT QsSA==
X-Received: by 10.182.236.65 with SMTP id us1mr35494936obc.38.1409706948267; Tue, 02 Sep 2014 18:15:48 -0700 (PDT)
Received: from [130.216.38.108] (sc-cs-567-laptop.cs.auckland.ac.nz. [130.216.38.108]) by mx.google.com with ESMTPSA id wa1sm7337048oeb.1.2014.09.02.18.15.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Sep 2014 18:15:47 -0700 (PDT)
Message-ID: <54066BD7.4010000@gmail.com>
Date: Wed, 03 Sep 2014 13:16:07 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
References: <201408251147.s7PBl2b6010099@irp-lnx1.cisco.com> <301104B4-78F7-4B55-86EB-0712FFB7D4DD@cisco.com> <540585CE.8020701@globis.net> <D9841A05-2016-48FB-BC4E-43F6F400DD93@cisco.com>
In-Reply-To: <D9841A05-2016-48FB-BC4E-43F6F400DD93@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/i6-dxkJqKNlTphZ6YghvB8fumys
Cc: Ray Hunter <v6ops@globis.net>, IPv6 Ops WG <v6ops@ietf.org>, "draft-v6ops-pmtud-ecmp-problem@tools.ietf.org" <draft-v6ops-pmtud-ecmp-problem@tools.ietf.org>
Subject: Re: [v6ops] new draft: draft-v6ops-pmtud-ecmp-problem
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 03 Sep 2014 01:15:50 -0000

BTW the draft name is a bit schlonky. Isn't there supposed
to be an -ietf in there?

   Brian

On 03/09/2014 11:55, Fred Baker (fred) wrote:
> On Sep 2, 2014, at 6:54 PM, Ray Hunter <v6ops@globis.net> wrote:
> 
>> Would a draft summarizing the ICMP PTB problem, investigating potential alternative sources of path MTU information, and alternative signaling mechanisms for path MTU, fit within v6ops remit?
> 
> I think this draft is trying to be that. What would definitely be within our remit would be operational advice, as in "advice from operators to operators", and advice to other working groups of the form "X needs to be improved, we like Y, but it has problems {Z}". What would be outside our remit would be changes to protocols.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email