Re: [v6ops] I-D Action: draft-ietf-v6ops-design-choices-02.txt
Mikael Abrahamsson <swmike@swm.pp.se> Tue, 09 September 2014 13:12 UTC
Return-Path: <swmike@swm.pp.se>
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 138211A02E6 for <v6ops@ietfa.amsl.com>; Tue, 9 Sep 2014 06:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.303
X-Spam-Level:
X-Spam-Status: No, score=-3.303 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RP_MATCHES_RCVD=-1.652, 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 ZnzWde-iCpm2 for <v6ops@ietfa.amsl.com>; Tue, 9 Sep 2014 06:12:24 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32F881A02E5 for <v6ops@ietf.org>; Tue, 9 Sep 2014 06:12:23 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id B3BECA3; Tue, 9 Sep 2014 15:12:20 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1410268340; bh=mUwhE5dMjxpPelt6XKUocUPVOjWRKFGtnrDgqvV91gg=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=VVusR0jMtJp/9Qmkd7yOvgrET1rU+bppD8L98Hi39OTpgyuXJnqFssVqDefukK1fE WoE3XvlSHTeivzPHPLvYRtAMf21nUWX7JLEY7WQhPkOn96265vGD9+yxwjj8v3Fk9Q 5Fv0c+5JAls8V/iGj1xvi/Y5cRxSjuuuLUdvRk+o=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id AF12EA2; Tue, 9 Sep 2014 15:12:20 +0200 (CEST)
Date: Tue, 09 Sep 2014 15:12:20 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Victor Kuarsingh <victor@jvknet.com>
In-Reply-To: <540EF884.6000000@jvknet.com>
Message-ID: <alpine.DEB.2.02.1409091511040.14735@uplift.swm.pp.se>
References: <20140905015058.25008.89518.idtracker@ietfa.amsl.com> <6F628257-7830-4824-A56B-DA54F61E3193@magma.ca> <alpine.DEB.2.02.1409090930240.14735@uplift.swm.pp.se> <540EF884.6000000@jvknet.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/kvG_ahVJsXWq8qJWgUIlyFbOYFA
Cc: v6ops list <v6ops@ietf.org>, Victor Kuarsingh <vkuarsingh@dyn.com>, Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-design-choices-02.txt
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: Tue, 09 Sep 2014 13:12:27 -0000
On Tue, 9 Sep 2014, Victor Kuarsingh wrote: > Mikael, > > The top portion of the text (in section 2.1.1) describes the concept of using > two links or two Vlans to separate traffic. Well, from end system point of view, it's a single vlan, it doesn't need to understand the two vlans. So this is somewhat of in-between. > The option of separating IPv4 and IPv6 on links (logical or physical) is set > as option (b). We have a brief discussion on the last paragraph on some > reasons to choose this. Now before we action any changes, there is > discussion in the last paragraph which talks about limitations on network > equipment and device-specific limitations. > > If you don't feel that this text is sufficient, then which of the following > approaches do you think would best get the point across. > > (1). Have a new paragraph(s) which highlight option (b) more and then > provide a listing of pros/cons (where the pros can then point to items you > wanted addressed) I think this is the approach I would prefer. Try to give examples how it can be done and pros and cons so the implementor can make an informed choice. -- Mikael Abrahamsson email: swmike@swm.pp.se
- [v6ops] I-D Action: draft-ietf-v6ops-design-choic… internet-drafts
- Re: [v6ops] I-D Action: draft-ietf-v6ops-design-c… Philip Matthews
- Re: [v6ops] I-D Action: draft-ietf-v6ops-design-c… Heatley, Nick
- Re: [v6ops] I-D Action: draft-ietf-v6ops-design-c… Chettle, Nick
- Re: [v6ops] I-D Action: draft-ietf-v6ops-design-c… Philip Matthews
- Re: [v6ops] I-D Action: draft-ietf-v6ops-design-c… Philip Matthews
- Re: [v6ops] I-D Action: draft-ietf-v6ops-design-c… Philip Matthews
- Re: [v6ops] I-D Action: draft-ietf-v6ops-design-c… Mikael Abrahamsson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-design-c… Victor Kuarsingh
- Re: [v6ops] I-D Action: draft-ietf-v6ops-design-c… Mikael Abrahamsson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-design-c… Philip Matthews
- Re: [v6ops] I-D Action: draft-ietf-v6ops-design-c… Philip Matthews