Re: Comments on draft-ietf-6man-default-iids-01.txt

Ralph Droms <rdroms.ietf@gmail.com> Mon, 24 November 2014 19:39 UTC

Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20BCD1A8980 for <ipv6@ietfa.amsl.com>; Mon, 24 Nov 2014 11:39:11 -0800 (PST)
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 X3XcwDGfiOrx for <ipv6@ietfa.amsl.com>; Mon, 24 Nov 2014 11:39:08 -0800 (PST)
Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F1531A886A for <ipv6@ietf.org>; Mon, 24 Nov 2014 11:39:08 -0800 (PST)
Received: by mail-qc0-f169.google.com with SMTP id w7so7424166qcr.14 for <ipv6@ietf.org>; Mon, 24 Nov 2014 11:39:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xw6+E8xqIVXAj2vQrT6y87hx+67Z2dI9hJiVhKEBX8s=; b=jPDy0UwT5YULKbDCyWUdnCZtYGfTq4TlSHjEd18wHaMP7PWZ+mZGFI12E4YuALEFro Ir+nPClDnHa0BtzQwA9NqtBbuhUn8kP0w15E9YYmSU15qtIt+VWefIuHy5s/G0ZAad92 UKZ/W8m8Fj81iGHRSH2Awp9o0LJrA+ZgwJlLx0DkF+/6MjzNjZrQnDzXWd32zQG4GuP+ VFAAAqfWFOt+eDDH2AjQJlNO7++h5R02XWlS/ipe5fgWCIWJApsqgCfXL+5oACVAJjjR jizd4DwxI0PSZRowhKRdl2llCceBM1Ih+K0hXFuBq5TQ2bUGucWmcW+fXJ623vEop1wc +6ow==
X-Received: by 10.229.120.198 with SMTP id e6mr30989956qcr.25.1416857947691; Mon, 24 Nov 2014 11:39:07 -0800 (PST)
Received: from [10.86.253.172] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id p106sm12642104qgd.36.2014.11.24.11.39.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Nov 2014 11:39:06 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Comments on draft-ietf-6man-default-iids-01.txt
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <54738269.8030607@gmail.com>
Date: Mon, 24 Nov 2014 14:39:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3AD80C27-EE59-4E69-9C9B-48C5BB30295B@gmail.com>
References: <8676AC11-85F1-4E58-9871-43FD04C89AB8@cisco.com> <234002BF-D879-46DF-B59F-1B9D7D76B581@gdt.id.au> <F2EFA1D3-EC86-4AD6-A0E4-7CF2CC175B9C@employees.org> <6267F947-1B59-47B6-BE69-9ABE9163E49C@gmail.com> <1CE9F644-3482-4F74-9624-A3373AC257FF@employees.org> <54738269.8030607@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/6REmp9x9b-WPoqG9BkSdusMhTK0
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Nov 2014 19:39:11 -0000

On Nov 24, 2014, at 2:09 PM 11/24/14, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> On 25/11/2014 00:34, Ole Troan wrote:
>> Ralph,
>> 
>>>> [...]
>>>> as far as I can see IPv6 over PPP is no different that IPv6 over any other multicast capable link-layer.
>>> Ole - In your opinion, does draft-ietf-6man-default-iids-01.txt give enough detail as written to be applied as an update to RFC 5072?
>> 
>> I don't know. I think we need to wait for an update of the draft with the changes discussed at the meeting.
>> 
>> then we need to look at the set of IPv6 over foo documents and decide if and what updates are required.
> 
> As a reminder, we already attempted to catalogue those documents in
> http://tools.ietf.org/html/draft-ietf-6man-why64-08#section-4.1 ,
> paragraph 3. We found 14 RFCs and 4 drafts.

Looks like there is pretty good overlap between the list of IPv6-over-foo documents in draft-ietf-6man-why64 and the list of RFCs updated by draft-ietf-6man-default-iids.  Authors of the two documents might want to coordinate their lists (I understand the lists won't necessarily match exactly).

These two documents listed in draft-ietf-6man-why64 - draft-brandt-6man-lowpanz-02 and draft-ietf-6man-6lobac-01 - have moved to 6lo, draft-ietf-6lo-lowpanz-08 and draft-ietf-6lo-6lobac-00, respectively.

If draft-ietf-6man-default-iids is published as an RFC, I assume documents published after that publication will be updated to reflect its requirements and we'll want to manage those affected drafts that are in process to make sure they coordinate with draft-ietf-6man-default-iids.

- Ralph


> 
>   Brian