Re: [mpls] Barry Leiba's Discuss on draft-ietf-mpls-ipv6-only-gap-03: (with DISCUSS and COMMENT)

Barry Leiba <barryleiba@computer.org> Mon, 24 November 2014 14:12 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE901A6F80; Mon, 24 Nov 2014 06:12:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 lE5qM_q5eda1; Mon, 24 Nov 2014 06:12:24 -0800 (PST)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D313A1A6F8E; Mon, 24 Nov 2014 06:12:23 -0800 (PST)
Received: by mail-la0-f45.google.com with SMTP id gq15so7730408lab.18 for <multiple recipients>; Mon, 24 Nov 2014 06:12:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=WLLaWtH84DjlYwOvhqeUMb49Yi0jX6x32K3gqCO4oe0=; b=oBwWCEROLXBrTT5G4eJ62j5vtKVumG3JP9Gz9K/RB+Y6ZNGPq7idH+zLpeJwAxYfYf 2XY43xMxmtPEkypUAB7RrTWdlpp73vnmkSVIu+7A5k13YE7+2ugmgcKxxJcMOMCTXhfd 0fBpnlJrPx9CRzjqsvalce3aIyMptvs5b0X1pB4J1SI2Rf2ZzKcZAqdEMpEMSJo8iiqi 7SU8fY5rYokLjZnWcBHyES5mVxFnOaPSh6DZVgqJuf2Rgiv9GHPXSjEpQYlzl1UcJ4UH hyNV/6asUJXWZKM63nNmYdAv5J3N9fIRloeD2LvHaTpKorqxn3pFfCmUOXyS+X/stYR8 aNgQ==
MIME-Version: 1.0
X-Received: by 10.152.18.130 with SMTP id w2mr8271512lad.1.1416838342400; Mon, 24 Nov 2014 06:12:22 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.152.127.168 with HTTP; Mon, 24 Nov 2014 06:12:22 -0800 (PST)
In-Reply-To: <5471F00D.8010401@pi.nu>
References: <20141123064914.2745.26911.idtracker@ietfa.amsl.com> <058901d006ec$2add7770$80986650$@olddog.co.uk> <5471F00D.8010401@pi.nu>
Date: Mon, 24 Nov 2014 04:12:22 -1000
X-Google-Sender-Auth: 1GX2Oj0Jzj4z6hfpFOmYGn3LVO0
Message-ID: <CALaySJLGW=KBusvKsQSGOLyHavdmQLovP2aHi1GyT9Od-gbSUg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Loa Andersson <loa@pi.nu>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/JtTzAlpPygk6oymp-cPMmehKxPw
Cc: The IESG <iesg@ietf.org>, "<mpls-chairs@tools.ietf.org>" <mpls-chairs@tools.ietf.org>, "draft-ietf-mpls-ipv6-only-gap@tools.ietf.org" <draft-ietf-mpls-ipv6-only-gap@tools.ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Barry Leiba's Discuss on draft-ietf-mpls-ipv6-only-gap-03: (with DISCUSS and COMMENT)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Nov 2014 14:12:25 -0000

Thanks, Adrian, Loa, and Mark, for the responses.

> I don't know how much more I have to after Adrian's mail, it seems
> cover the issues.

It does.  And, yet, your message does add a useful comment:

> We never had the ambition to find every gap, but believed that
> that documenting for the future that we made the effort and also that
> the gaps we found would be a good enough idea.
>
> I differ from Adrian on one point, I think it is very likely that we'll
> find new gaps, however they will be few and with low impact.

That's a good answer, and thanks for adding that.  Mark's comment is
also helpful:

> I would support a wiki, as that can be edited by the group
> at anytime, and anything in the wiki that makes sense to add
> into an IETF draft or RFC can help ensure the drafts/RFC's
> have the most pertinent information, and don't end up
> getting unnecessarily bloated.

That's a perfect use of the working group wiki, and that should take
care of the question entirely.

Off to change my ballot now...

> As for the references I agree that it is possible to take a pass on
> them

OK.  I'm sad about that, but not terribly so: as I said, I think it
would be helpful, but not so important for this document.  So carry
on, and thanks again for the good responses.

Barry